Semantic Enhancements for DoD Information Sharing, Enterprise Architecture, and Standards Dr. Brand Niemann Director and Senior Enterprise Architect – Data Scientist Semantic Community http://semanticommunity.info/ AOL Government Blogger http://gov.aol.com/bloggers/brand-niemann/ April 20, 2012 http://semanticommunity.info/Build_DoD_in_the_Cloud

Semantic Community Our Mantra is: Data Science Precedes the Use of SOA, Cloud, and Semantic Technologies! We use data science to help marketing and business development efforts. Our Mission is like Googles: Organize the world’s information and make it universally accessible and useful. Our Method is like Be Informed 4: Architectural Diagrams and Questions and Answers are not enough, you need Dynamic Case Management! Our Sound Byte: It is not just where you put your data (cloud), but how you put it there! Our Work: Semantically enhancing your data and writing data science stories about it.

Defense Department Bets Big on Big Data http://gov.aol.com/2012/03/30/defense-department-bets-big-on-big-data/

Has NIEM Reached A Choke Point With Big Data http://gov.aol.com/2012/03/22/has-niem-reached-a-choke-point-with-big-data/

Put Federal Dashboard Into Motion (and Memory) Mine Their’s http://gov.aol.com/2012/03/14/put-federal-it-dashboard-into-motion/

Invitation Topics should be within Mr. Okon’s scope of the DoD CIO and Federal CIO Council. Specific topics could include: Next Generation of Information Sharing and Exchange Next Generation of Enterprise Architecture (exploiting the accomplishments IDEAS and DoDAF and UPDM) Evolution or Development at IT Standards Development Organizations (OMG, ISO, etc.)

Questions How Does the Following Slide Relate to: DoD Architecture Framework (DoDAF) and OMG UPDM (Unified Profile for DoDAF and MoDAF)? The spatial-temporal ontology in IDEAS or DoDAF? DARS (DoD Architecture Registry System)? “Upgrade” with semantic web? BEA as a subset of DoD Architectures?

DoD Architecture Progression http://semanticommunity.info/@api/deki/files/16066/=JonathanUnderlySlide6.png

Semantic Enhancements DoD Information Sharing: NCOIC-NGA Pilot: A Quint-Cross Information Sharing and Integration App Enterprise Architecture: DoD DCMO Pilot: A DoD DCMO Enterprise Information Web Standards: OMG: Semantics and Ontologies for the Intelligence Community Working Toward Standards, March 19-23, and June 18-22, 2012.

A Quint-Cross Information Sharing and Integration App http://semanticommunity.info/A_Quint-Cross_Information_Sharing_and_Integration#Spotfire_Dashboard

A DoD DCMO Enterprise Information Web http://semanticommunity.info/A_DoD_DCMO_Enterprise_Information_Web#Spotfire_Dashboard

Semantics and Ontologies for the Intelligence Community Working Toward Standards http://semanticommunity.info/AOL_Government/Semantics_and_Ontologies_for_the_Intelligence_Community_Working_Toward_Standards#Spotfire_Dashboard

Len Levine’s Interests Slide 3 (OMG): How semantic technologies could add value by “analytic transformation” of existing DoD registries named below: Please address how such an Analytic Transformation could draw on the DISR, GIG Technical Profiles, DARS, DITPR, etc. Sound Byte: “Spotfire makes registries analytic” Slide 8 (Be Informed): Above the line architecture complements multiple existing approaches to enterprise architecture (e.g. DoDAF, TOGAF, Zachman, etc.). Also, it integrates with existing change management software practices: Please address DoDAF and its data model / taxonomy Sound Byte: “Be Informed is the architectures of architectures”

My Reply I have addressed how semantic enhancements of DoD Architectures and Registries add value in past presentations to Walt Okon and have moved on now to semantic service apps that Analytic Transformation Tools like Spotfire and Be Informed can build that use linked data and data science, go in libraries where they can be readily used and reused, and are federated and managed by Dynamic Case Management.

My Post Script I found that DoD Architectures and Registries have content that limits the value of semantic enhancements and that apps using the actual data and Analytic Tools are more valuable. See for example: http://semanticommunity.info/Army_Weapon_Systems_Handbook_2012 http://gov.aol.com/2011/12/29/lessons-from-armys-weapon-systems-handbook-and-galls-law/

Army Weapon Systems Handbook: The DoD Systems of Systems http://semanticommunity.info/Army_Weapon_Systems_Handbook_2012#Spotfire_Dashboard_2

Army Weapon Systems Handbook: Gall’s Law http://gov.aol.com/2011/12/29/lessons-from-armys-weapon-systems-handbook-and-galls-law/

Has NIEM Reached A Choke Point With Big Data http://gov.aol.com/2012/03/22/has-niem-reached-a-choke-point-with-big-data/

The Semantic Community Process for Building DoD in the Cloud Repurpose Information and Data from DoD Architectures and Registries. Unstructured information gets well-defined URLs E.g. Vocabulary Unstructured information becomes a predicate database for semantic network analysis E.g. Large number of documents Structured data gets reusable structure E.g. Tables in Web pages Links are made meaningful E.g. “Word Wheel” of best choices for links Content container supports standards E.g. Web-oriented architecture, Sitemap and Schema Protocols, etc. Content is federated with crowd sourcing E.g. Wiki-like environment Work environment is self-service on mobile devices E.g. iPhone – iTunes App Store

Build DoD in the Cloud: “Spotfire makes registries analytic” See next slide http://semanticommunity.info/Build_DoD_in_the_Cloud

Build DoD in the Cloud: MindTouch Federates Content 2011 DOD IG Semiannual Report to Congress A Workshop on Semantic Interoperability Business Enterprise Architecture Congressional Report 2011 on Defense Business Operations Data Analysis and Collaboration Tool to Support the DOD OIG TIBCO Spotfire Develop 8330.XX 1st Draft* DISA Campaign Plan 2010 DOD IG DoD Information Enterprise Architecture Information Enterprise Architecture Version 1.2 DoD IT Portfolio Registry* Enterprise Information Web for Semantic Interoperability at DoD Acquisition Policy for Defense Business Systems (DBS) DOD looks to semantics for better data-sharing, cost savings Enterprise architects must prove their worth in reducing duplication Enterprise Information Web (EIW) RFI Industry Day Letter from Dennis Wisnosky Spotfire Data Federation Spotfire Information Designer Use of End-to-End (E2E) Business Models and Ontology in DoD Business Architecture Joint Capability Areas Note: Most of these are Public, but some of these are Private*.

Build DoD in the Cloud: DoD Information Enterprise Architecture I finished the Interactive Hierarchical Activity Model for you! This is now ready for Dynamic Case Management with Be Informed where DoDAF and its data model / taxonomy would become a knowledge model on top of a knowledge base! http://semanticommunity.info/Build_DoD_in_the_Cloud/DoD_Information_Enterprise_Architecture

Build DoD in the Cloud: “Be Informed is the architectures of architectures” http://semanticommunity.info/AOL_Government/Be_Informed_4_-_They_really_got_it Also see Training Materials: http://semanticommunity.info/Be_Informed_4

Build DoD in the Cloud: Be Informed Dynamic Case Management A recent paper describes the formalism and rationale that Be Informed applies to business process modeling. It explains how and why goal-oriented modeling differs from more conventional business process modeling which is procedural. In the near-term, there is applicability for many government agencies, especially for those exploring semantic approaches. For example, Dennis Wisnoski advocates semantic web (RDF & OWL) standards for modeling data integration, and a dialect of BPMN for modeling processes. The metaphor for processes is an electronic circuit specification that uses standard building blocks. "We all know what those primitives mean." Previous, costly attempts at business process modeling were failures in part because there was no standard at the primitive level. However, as this paper makes clear, just having unambiguous primitives is only part of what is needed to specify and manage complex and dynamic business processes. Modeling flow in swim lanes is less agile than modeling goals, activities, and pre and post conditions. Source: Mills Davis, Project10x, July 5, 2011.

Build DoD in the Cloud: Be Informed Dynamic Case Management Fig. 1. Summary of the Meta Model for Capturing Business Processes Source: Specifying Flexible Business Processes using Pre and Post Conditions, Jeroen van Grondelle and Menno Gulpers, Be Informed BV, Apeldoorn, The Netherlands, 13 pp. Paper available at URL in Slide 23.

Build DoD in the Cloud: Be Informed 4 Studio Modeling Note: Military Person Register.model for February 6th DCMO Presentation. Note: This is the NCOIC-NGA Demonstration Metamodel Work.