UNCLASSIFIED Joint C 3 Information Exchange Data Model

UNCLASSIFIED Joint C 3 Information Exchange Data Model (JC 3 IEDM): Design and Content Prepared for IAM WG 10 May 2006 INSTITUTE FOR DEFENSE ANALYSES Dr. Gene Simaitis (esimaitis@ida. org), 703 -845 -6873 ES-10 May 2006 1

UNCLASSIFIED Briefing Outline • • • ES-10 May 2006 Basics Objective Exchange Concept Representative Data Technical Introduction Closing 2

UNCLASSIFIED JC 3 IEDM Basics • Encapsulation of structured data supporting C 2 functions • Complete logical and physical specifications for information exchange • Essentially, a C 2 data language ES-10 May 2006 3

UNCLASSIFIED Initial Objective of the Initiative To define the minimum operational and technical requirements to be included within system specification which will allow national C 2 systems to interoperate by the automatic exchange of data i. e. Level 5 of System Interconnection. 4

UNCLASSIFIED The Technical Exchange Concept Information Transfer Local Implementation Common Interface IEM System Database ES-10 May 2006 JC 3 IEDM IEM JC 3 IEDM System Database 5

UNCLASSIFIED The Operational Exchange Concept Effective C 2 For Operations Shared Picture Information Transfer Commander Local Implementation Commander Common Interface IEM Staff System Database JC 3 IEDM IEM JC 3 IEDM System Database Staff Common understanding ES-10 May 2006 6

UNCLASSIFIED Representative Data Locations Status of objects Plans & Orders Event reporting XXX II MNC XX XX II/1 (US) II/2 (GE) MND X X X 1/I(FR) II 1/II(CA) II II X 1/III (SP) 2/I (DA) X 2/II(NL) II II/1 II/2 II/3 II/4 ORBATs Unit holdings ES-10 May 2006 X 2/III (IT) Control measures Geographic features Weather features Battlefield capabilities 7

UNCLASSIFIED Short Technical Introduction to JC 3 IEDM ES-10 May 2006 8

UNCLASSIFIED Operational Requirements • General, based on military experience • 48 APP-9 messages (640 elements) • Crisis Response Operations (518 elements) • Joint interfaces (222 elements) • NATO Corporate Reference Model V 4 (+ CBRN, MMW, ATO, ACT requirements) • MIP- generated operational requirements ES-10 May 2006 9

UNCLASSIFIED Overview of Functional Content • Define objects in the universe of discourse • Describe state of the universe: past, present, and future • Use what you have via plans, orders, requests • Record events • Provide supporting structures as needed ES-10 May 2006 10

UNCLASSIFIED High Level View of JC 3 IEDM § Comprehensive § Allows for extension § Very well documented • Tables • Attributes • Relations • Extension rules § XML tags available Courtesy: ODU/VMASC ES-10 May 2006 11

UNCLASSIFIED OBJECT-TYPE Hierarchy ES-10 May 2006 12

UNCLASSIFIED AFFILIATION ES-10 May 2006 13

UNCLASSIFIED ORGANISATION-STRUCTURE ES-10 May 2006 14

UNCLASSIFIED ACTION – How to Specify Use of Objects Activities can be represented through the ACTION structure: instances or classes of battlefield objects serve as resources and are directed at instances or classes of battlefield objects that serve as objectives ES-10 May 2006 15

UNCLASSIFIED CONTEXT Structure and Use ES-10 May 2006 16

UNCLASSIFIED Counting by Group Characteristics ES-10 May 2006 17

UNCLASSIFIED High-Level View of JC 3 IEDM ES-10 May 2006 18

UNCLASSIFIED Advantages of JC 3 IEDM as a Reference Model for Data Exchange • Relatively simple, understandable, tightly integrated structure with broad applicability • Central concepts have been stable for 13 years • Multinational pedigree • Easy to extend in response to operational data requirements • Semantic content can be enriched to suit the needs of a community of interest (COI) ES-10 May 2006 19

UNCLASSIFIED Questions? ES-10 May 2006 20

UNCLASSIFIED Configuration Management of Data Specifications Prepared for Dr. Alberts, CCRP 10 May 2006 INSTITUTE FOR DEFENSE ANALYSES Dr. Gene Simaitis (esimaitis@ida. org), 703 -845 -6873 ES-10 May 2006 21

UNCLASSIFIED NATO/MIP Specific • • Change proposal generation Deliberation and voting Documentation updates Periodic release of specifications ES-10 May 2006 22

UNCLASSIFIED NATO/MIP Specific Change proposal generation • Unmet operational requirements • Specification “fixes” – Problem reports from implementers – Delegate suggestions ES-10 May 2006 23

UNCLASSIFIED NATO/MIP Specific Deliberation and voting • Proposals are discussed • Voted on – Approved – Deferred (generally for re-write) – Rejected ES-10 May 2006 24

UNCLASSIFIED NATO/MIP Specific Documentation updates • Model (logical and physical) • Main and annexes • MIP Information Resource Dictionary (MIRD) • Requirements databases • CP database ES-10 May 2006 25

UNCLASSIFIED NATO/MIP Specific Periodic release of specifications • Official version release – End of MIP block – End of MIP-approved increment • Made available at MIP Web site (www. mip-site. org) public area ES-10 May 2006 26

UNCLASSIFIED US Specific • Overall management structure for WMA (Col Whitehead will cover) • Procedures for CM of data specifications are under development ES-10 May 2006 27

UNCLASSIFIED US Specific Challenges • Determining JBCIEDM (or US)-unique requirements • Coordinating with NATO/MIP specification development • Involving joint participation ES-10 May 2006 28

UNCLASSIFIED Questions? ES-10 May 2006 29