1. OGC Interoperability Experiment Frank Klucznik Georgia Tech Research Institute January 2013

2. Objective Command and Control (C2) Core has been an emerging data exchange capability within Department of Defense over the past three years. DoD CIO is now moving toward adopting the National Information Exchange Model (NIEM). C2 Core, which is 93% aligned with NIEM technical standards, will be used as the foundation for developing a Military Operations (MilOps) Domain in NIEM. This experiment will demonstrate that the MilOps Domain model and NIEM v2.1 technical concepts work in combination with geospatial standards as defined by the Open Geospatial Consortium (e.g., GML, WFS, WCS, WMS, etc.). 2

3. Outcomes Successfully demonstrate that MilOps is fully compatible and supports in all of the areas of interest listed above, or If MilOps is not compatible attempt to develop a technical solution in MilOps to resolve the incompatibility and rerun that portion of the experiment to demonstrate MilOps compatibility and support for the areas previously shown not to be supported, or If incompatibilities previously identified are not resolved in MilOps, submit change request to OGC and recommend including them in a future test bed. 3

4. Initiators National Geospatial-Intelligence Agency (NGA) MITRE Georgia Tech Research Institute (GTRI) 4

5. Use Cases Extract content from a MilOps conformant IEP and transform it into an existing OGC standard (e.g., GML, KML, etc.) without losing precision or accuracy. Extract content from a MilOps conformant IEP and transform it into an existing OGC standard (e.g., GML, KML, etc.), and display the data in an OGC conformant mapping tool without losing precision or accuracy. Evaluate the use of GML in NGA’s Time Space Position Information (TSPI) specification in a MilOps conformant exchange (e.g., IES/IEP). Accomplish the experiment with commodity skills such as java, general programming, XML, XSLT, etc. (e.g., no specialty skills required). 5

6. Primary Experiments Experiment #1: Extract Information Exchange Package (e.g., XML instance document) content including geospatial data that includes GML and transform it into an OGC Standard format (e.g., KML, WMS, WCS, WFS, etc.) with symbology as appropriate, and then plot it on a map. Experiment #2: Extract geospatial data that includes GML content and add additional MilOps metadata (e.g., MilOps content specified as a feature) and then plot it on a map. Experiment #3: Expose MilOps data through a Web Feature Services interface and make content available in GML and/or KML. Vendor client tools will consume this content and display it on a map. Demonstrate no loss of precision when transforming embedded GML content (e.g., location). Experiment #4: Employ “GML Validator” currently being developed in OWS-9 to determine compliance of GML in a MilOps exchange to GML Encoding Specifications, if appropriate. 6

7. 7 Experiment NOTE: Dark blue colored artifacts provided by GTRI, brick colored artifacts provided by vendor participants MilOps IEP GTRI IEP Translator WFS (GTRI) Consuming Desktop Application WMS Consuming Desktop Application Geospatial Server Client 1Client 2Client n Low Bandwidth Client (e.g., mobile app) … Transmitter to tactical device Consuming Desktop Application Vendor IEP Translator Data Source Implementation Options

8. Timeline 8 Startup Activity Plan submission: Completed OGC Review Board approval: Completed December 11, 2012 Press Release (start of participation notification period): January 31, 2013 Execution Planned kickoff date: March 2013 (30-day post press release) Development, testing and bug fixing March – May 2013 Planned end date: May 2013 Wrap-up and Reporting Technology Demonstration June 2013 Final report submission August 2013

9. Back Ups 9

10. Technical Details 10 C2Core IEP IEP Translator WFS Consuming Application WFS/WMS DB getFeature response getFeature request Send to Sends extracted GML data in the Insert element of a Transaction element. The GML data is inserted into the database used by the WFS. uses database getMap request getMap response WMS