NCOIC Geospatial Interoperability Task Team Presentation Dr. Brand Niemann Director and Senior Enterprise Architect – Data Scientist Semantic Community AOL Government Blogger February 17, 20, and 24, and March 1, It is not just where you put your data (cloud), but how you put it there!

Role of Semantic Interoperability and Ontologies Business Use Case: – Director Letitia Long – Put GEOINTT in the hands of users and do deeper analytics to support response – Keith Barber – Implementation of online/on-demand services – Todd Myers – Expeditionary architecture Stages: – Pilot NCOIC-NGA, Federal SOA CoP & MITRE, Semantic Community, etc. – Lab Sandbox CIA, Federal SOA CoP and MITRE, Semantic Community, etc. – Provision (instead of procure) Amazon, GSA Federal Acquisition Services, Semantic Community, etc. 2

Role of Semantic Interoperability and Ontologies LayersSemanticsStepsTools* Dynamic Management Ontologies, Rules, Agents MetaModels with semantic links to the knowledgebase Be Informed, SIRA, and Recorded Future AnalyticsFederated Search and Integration Dashboard library of multiple interactive data sets and visualizations Spotfire ContentLinked Data and Semantic Links Knowledgebase of linked unstructured and structured data MindTouch CloudWell-defined Web Addresses Provision platforms for layers above Amazon Web Services 3 * Examples that build interoperable apps for mobile devices (e.g. iPhone, iPad, etc.) Slide 37: Analytics and Agents move to the edge and begin to precede aggregation. Slide 40: Provide roadmap for Semantic and Linked Data enterprise ontology architectures.

Data Science is Part of My System of Systems Architecture 4 S Semantic Index of Linked Data (e.g. Excel) Dynamic Case Management (e.g. Be Informed) Data Science Library (e.g. Spotfire) Data Science Products (e.g. Spotfire) Our Mantra is: Data Science Precedes the Use of SOA, Cloud, and Semantic Technologies! 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 Purpose: To "ground" the NCOIC-NGA Pilot in the NCOIC Deliverables by building a database of those deliverables that is displayed and used in a Dashboard.

Best Content to a Knowledgebase 5 The Entire Fact Book as Linked Open Data: About (4) References (6) Appendices (7) FAQs (1) Country Profiles (277)

Knowledgebase to Spreadsheet 6

Spreadsheet to a Dashboard 7 Web Player See the Data Sort/Facet Search the Data Download the Data Share the Data (iPad) See Three CIA Tabs

Geospatial Images to a Dashboard 8 Note: This can be annotated with data points as a Background Map Image in Spotfire. Web Player

Data Federation and Search 9 Search Analytic Apps in the Cloud: About 150

10

NCOIC New Business Update: February 2012 “The NCOIC moved into the implementation phase of its operations at the direction of the Executive Council last September. This phase is designed to use and expand on the technical products developed by the NCOIC technical teams and will assist the customer community to implement interoperable solutions.” – Tip Slater, NCOIC Business Development Director 11

My Bottom Line NCOIC has done and is doing a lot of good work, but the NCOIC- NGA Pilot needs to be integrated and managed with related work. My Suggested Steps: – 1. Start with the SCOPE Overview: Case Study = Military Model + Commercial Model – 2. Adapt the Australian SCOPE Workshop Training Materials Scenario: Integrated Narrative of Background, Architecture, Use Case, Data Sets, etc. – 3. Adapt the All Hazards Alerts and Warnings (AHAW) Capability Pattern: Extend to include Cloud Platforms as a Service (PaaS). – 4. Populate PaaS’s with Specific Resources: Semantic Community and FacetApp Examples – 5. Ask and Answer SCOPE Questions: Map to DoD IEA and Use Dynamic Case Management 12

1. SCOPE Overview: Case Study 13

1. SCOPE Overview: Slide 21 Narrative SCOPE adds additional value when trying to interoperate across multiple systems. For example, imagine the military is facing a complex humanitarian disaster and wants to add a commercial system for emergency response. Will the military system be able to interoperate with that commercial system? A SCOPE analysis, (in red) for the military system and (in purple) for the commercial system, illustrates that in some areas, those systems can work together, but in other areas they are not aligned. This provides an insight to the interoperability requirements to make two systems, or classes of systems, interoperate. – Source: 14

2. Training Materials for Australian SCOPE Workshop Scenario 1 Outline 2 Background 2.1 Defenses Health Information System 2.2 UN Mission 3 Incident – 3.1 Narrative Text – 3.2 Information and Data Flows – 3.3 Formal Scenario Definition 15

2. Training Materials for Australian SCOPE Workshop 16

2. Training Materials for Australian SCOPE Workshop 17

2. Training Materials for Australian SCOPE Workshop 18

2. Training Materials for Australian SCOPE Workshop 19

3. Adapt the All Hazards Alerts and Warnings (AHAW) Capability Pattern 20

3. Adapt the All Hazards Alerts and Warnings (AHAW) Capability Pattern 21

3. Adapt the All Hazards Alerts and Warnings (AHAW) Capability Pattern 22

4. Populate PaaS’s with Specific Resources Semantic Community: – Intelligence Community Architecture and Pilot CIA World Fact Book Use Case and Data Set – NGA – NCOIC Architecture and Pilot Haiti Use Case and Harvard Data Set World Disaster Use Case and Reinsurance Data Set – DoD Enterprise Information Web Pilot Information Enterprise Architecture Knowledgebase Business Enterprise Architecture Knowledgebase DoD IEA Hierarchical Activity Model Data Set Note: All of these are federated! 23

4. Populate PaaS’s with Specific Resources FacetApp: – Robert Kruse presented some very interesting and useful NATO Use Case and Data Set Information in our OV1 and Central Node Subgroup Meeting earlier this week that I think we should discuss jointly at your meeting on Friday to help move this project along. I also have Use case and Data Set information that I would like to share as well. – Web Addresses From Robert Kruse:

4. Populate PaaS’s with Specific Resources We did receive authorization from NGA to proceed with obtaining input from NATO directly on any "pain points" or "hot buttons" they are dealing with related to disaster response. If members have ideas or contacts at NATO who could help with this, you are asked to collect any information you can and send it to the group. Todd Myers would like to see the data be made available via “one click.” 25

5. Ask and Answer SCOPE Questions 0. SCOPE Context 1. SCOPE NetReadiness 2. SCOPE Domain Independent 3. SCOPE Domain Dependent 4. SCOPE TechEcoFeasibility Source: Todd Schneider, February 15, 2012 We're in the midst of cleaning up the questions and value sets (aka answers) so the spreadsheet can be put on the Kavi site. This action was prompted by a request to reference SCOPE and the questions in an ISO standard. 26

5. Ask and Answer SCOPE Questions 27 Recall Slide 4 NCAT Spider Diagrams

5. Ask and Answer SCOPE Questions The Network Centric Operations Industry Consortium (NCOIC) Execution Plan DISA01: describes the collaborative work initiated between the Defense Information System Agency (DISA) and NCOIC. DISA signed a Cooperative Research and Development Agreement (CRADA) with NCOIC to enhance understanding, development, and refinement of relevant network-centric operations (NCO) principles and practices. Through this CRADA, the United States (US) Department of Defense Chief Information Officer (DoD CIO) is engaging NCOIC to develop an industry view of the Net-Centric Attributes (NCA) developed by the Assistant Secretary of Defense for Networks and Information Integration (ASD(NII))/US DoD CIO. The execution plan was developed by DoD and DISA to fit together with the existing evolving NCOIC Interoperability Framework (NIF); Systems, Capabilities, Operations, Programs, and Enterprises (SCOPETM) Model for Interoperability; Network Centric Analysis Tool (NCATTM); and other tools and products of the NCOIC functional teams (FT), working groups (WG), and integrated project teams (IPT). – Source: 28

5. Ask and Answer SCOPE Questions 29

5. Ask and Answer SCOPE Questions Network Centric Attributes Functional Team/ Net-Centric Attributes Content Work Group US DoD Net-Centric Attributes, Invited Review Paper, Version 2.0 February 16, 2011, Excerpts: – 6.5 Infrastructure and Processes to Support Evolution of NCA Continuous and dynamic feedback in support of NCA evolution is sought. In this way, the current review effort can transition from a static one-time review to a dynamic process by which the NCA are kept current, benefiting both government and industry. This also supports an industry evolution plan. Under the work of its Building Blocks Team, NCOIC is using the following design structure to organize, describe, and make available NCOIC data: – Pattern Repository—A metadata extract of key information about NCOIC deliverables. – Open Standards Registry—A metadata extract of the open standards used within various NCOIC patterns. – Building Blocks Database—A metadata extract of vendor-offered solutions that meet the requirements defined in NCOIC patterns along with specific information on how the product has met NCOIC requirements. One of the key features of this structure is the ability to capture feedback from the NCOIC user communities. To capture valuable insight into the relevance, effectiveness, and applicability to real-world NCO designs, users’ input about each repository is gathered and provided to the teams responsible for the specific pattern, standard, or product. This organization of repositories and feedback mechanism may provide a useful structure with which to align efforts to facilitate the evolution of the NCA. This review itself could be viewed as an early iteration of such an evolutionary process to improve the NCA. – 7 Follow-on Work As indicated in Sections 2.3.2, 3, and 5, NCOIC intends to pursue an extension of this review and related work to meet the intent of the NCA for the larger community interested in using them. In particular, the following items have been identified as follow-on work for NCOIC: – A candidate replacement for Social and Cognitive Integration. – A mapping of the NCOIC Core Net-Centric Principles to the recommended NCA along with explanation of the derivation(s). – Further development of assessment contexts together with application guidance. – Mapping from the NCA together with assessment contexts to the various NCOIC products, including SCOPETM and NCATTM. Source: 30 Dynamic Mapping

5. Ask and Answer SCOPE Questions Includes the Quint: CIA, DIA, NGA*, NRO, & NSA Todd Myers, Chief Technology Advisor to the Director of the National Expeditionary Architecture, is working on this. Two hour oral presentation to the DoD DCMO EIW on 2/6 on federating all of these! 31

NCOIC Deliverables-Excel Spreadsheet 32

NCOIC Deliverables-Spotfire Dashboard 33 PC Desktop Spotfire

NGA IT Services 34 GEOINTT Online and Ondemand Keith Barber Implementation Lead for Online/On-Demand Services National Geospatial-Intelligence Agency

NGA’s Mission 35

Technology 36

Road Map for Future Generations of Services 37 Note: Analytics and Agents move to the edge and begin to precede aggregation.

Understanding the world though data 38

NSG Cloud User Scenario 39

Global / Service Cloud 40 Note: Provide roadmap for Semantic and Linked Data enterprise ontology architectures

Challenges /Opportunities 41

Summary 42

Operational ViewPoint: Community Cloud 43 Note: NGA Slide 4 says they are going beyond this!

Operational View: Nodes and Roles 44 Note: This is not the Roadmap requested in NGA Slide 7.