© 2009 The MITRE Corporation. All Rights ReservedFor Limited External Release C2 Core: Problem, Approach, And Value Proposition Dr. Scott Renner 8 April 2009

© 2009 The MITRE Corporation. All Rights ReservedFor Limited External Release Context C2 Core concept originates in 2007, along with UCore Envisioned as one of several domain-specific extensions to UCore Responsibility of C2 Capability Portfolio Manager (C2 CPM) Active development begins in 2008 –Data/Services Steering Committee (DSSC) directs development of C2 Core –18-20 March kickoff meeting in Ft. Leavenworth 2

© 2009 The MITRE Corporation. All Rights ReservedFor Limited External Release C2 Core History And Status C2 Core version 1.0 presented to DSSCApr 08 –Large subset of JC3IEDM –No clear definition of scope or conformance –Not accepted Independent Assessment Team (IAT) createdJul 08 –Reviews issues re. C2 implementation of NCDSNov 08 New C2 Core effort startedJan 09 –Technical Framework & Tools Sub-WG stands upFeb 09 –Draft C2 Core CONOPS for reviewMar 09

USJFCOM J8 4 Technical Framework and Tools Sub-Working Group C2 Core Operational Content Sub-Working Group Verification, Validation & Implementation Sub-Working Group C2 Core Working Group C2 DSSC Working Group Organizational Structure UNCLASSIFIED

© 2009 The MITRE Corporation. All Rights ReservedFor Limited External Release application 5 Basic Problem C2 COI UCore C2 Core define PORs How do the programs within C2 COIs make use of UCore and C2 Core to define interoperable data exchanges? (Not pairwise – want many producers and consumers to use same message format) ProducerConsumer understand Shared vocabularies

© 2009 The MITRE Corporation. All Rights ReservedFor Limited External Release application 6 IEP Basic Approach C2 COI UCore C2 Core IES defines COIs and their member PORs design and implement the IES, using definitions from UCore and C2 Core information exchange package information exchange specification PORs

© 2009 The MITRE Corporation. All Rights ReservedFor Limited External Release 7 application IEP Four Parts Of IAT’s C2 Core UCore C2 Core defines C2 Conceptual Model & Vocabulary C2-Specifc Extensions to UCore C2 Information Sharing Framework C2 COI IES PORs C2 Core Service Specifications

© 2009 The MITRE Corporation. All Rights ReservedFor Limited External Release 8 application IEP Four Parts Of C2 Core UCore C2 Core defines C2 Conceptual Model & Vocabulary C2-Specifc Extensions to UCore C2 Information Sharing Framework C2 Core Service Specifications C2 COI IES PORs Feedback loop: Runtime metrics used to improve all four parts of IAT’s C2 Core

© 2009 The MITRE Corporation. All Rights ReservedFor Limited External Release 9 application IEP Which Parts Are We Working Now? UCore C2 Common Core defines C2 Conceptual Model & Vocabulary C2-Specifc Extensions to UCore C2 Information Sharing Framework C2 Core Service Specifications C2 COI IES PORs

© 2009 The MITRE Corporation. All Rights ReservedFor Limited External Release C2 Core Problem Statement COIs deal with understandability / interoperability in NCDS –COIs inevitably overlap –Will develop redundant, incompatible data components Universal and common core vocabularies –Capture the common definitions –Leave each COI to define just the data it alone needs UCore provides a small set of common definitions needed in almost all COIs –Who, what, where, and when –Doesn’t go deep enough for C2 domain –Commonalities among C2 COIs not defined in UCore Problem: Need a common core, extending UCore, and capturing overlaps among the C2 COIs 10

© 2009 The MITRE Corporation. All Rights ReservedFor Limited External Release Another Way To Look At It We can’t let everyone totally do their own thing We can’t get everyone to do everything the same So we want to converge on some things Some core data components needed in several COIs (out of the complete set of C2 data components) Some particular ways to use XML to represent data (out of all the possible ways of using XML) Reduce (not eliminate) diversity where this adds most value 11

© 2009 The MITRE Corporation. All Rights ReservedFor Limited External Release 12 C2 Core Development Concept Problem statement, value proposition, assumptions, architectural framework, and lifecycle CM concepts Enough detail to understand what the TFTSWG is doing, is not doing now, and won’t do at all Defines roles of the DSSC, C2 Core WGs, et al. Provides a baseline level of understanding and agreement to build upon –Solid enough to know what the concept is not –Detailed enough to agree what the argument is about –Good enough to justify further development

© 2009 The MITRE Corporation. All Rights ReservedFor Limited External Release Questions And Assumptions Target of conformance To what sort of Core things does an IES conform? Kind of conformance Semantic, representation, or runtime? Scope of conformance Who should conform, for which info exchanges? Size of conformance How big is the Core, in absolute and relative terms? Source of Core content Clean sheet, existing models, COIs, or current exchanges? Speed of creation and adoption –How long until we have a “complete” Core? –How long until our information exchanges conform? 13

© 2009 The MITRE Corporation. All Rights ReservedFor Limited External Release Technical Group Assumptions Target of conformance: –UCore 2.0 exchange specification –C2 Core (C2-specific extensions) reusable components –C2 Core IES framework and technical specifications Kind of conformance –Representation conformance expected –Semantic conformance possibly permitted Scope of conformance –Exchanges within C2 Capability Portfolio –Exchanges where producer is within portfolio –Only exchanges covered by C2 Conceptual Model 14

© 2009 The MITRE Corporation. All Rights ReservedFor Limited External Release Technical Group Assumptions Size of conformance –Right size determined from experience –No larger than necessary –Start “small” and grow as needed Source of C2 Core content –Important existing exchanges –Important producers outside C2 CPM Speed of creation and adoption –Expect rapid change at beginning –Old components changed or removed, new ones added –Stability means decreased rate of change (not zero) –Adopt in all new in-scope implementation –Adopt in existing in-scope services over time 15

© 2009 The MITRE Corporation. All Rights ReservedFor Limited External Release Approach Highlights Enterprise approach –Balance data interoperability & flexibility Layered data framework Reusable XML data components from COI overlaps COI / POR developed Information Exchange Specifications Semantic agreement and reuse drive C2 Core size C2 Core components developed through iterative process Harvest and harmonize data requirements and semantics from that which exists and is being operationally used Built with reuse and extensibility in mind – allow for composabilty Adoption over time through evolution not big bang 16

© 2009 The MITRE Corporation. All Rights ReservedFor Limited External Release C2 Core Value Proposition Over time, data components properly belonging to many / most COIs are designed once These components are used as “building blocks” in all new data exchanges When these new exchanges are designed, some / most of the data interoperability work is already done Resulting value –Reduced cost –Faster development –Improved agility / flexibility 17

Concept – FAQ Highlights 1. Problem statement and value proposition for C2 Core? 2. How does C2 Core align with UCore? 3. What is does extension mean in C2 Core? 4. What is an extension of an IES? 5. Will C2 Core have a taxonomy like UCore? 6. What will be the cost or cost savings of C2 Core? 7. Why do we need an NDR? 8. C2 Core support low-bandwidth tactical networks? 9. Is C2 Core mandating JC3IEDM? 10. How specifically will C2Core extend UCore? 11. What does C2 Core extension by COI look like in my XSD? 12. How can I use a schema that isn’t conformant in an IES? 13. Is every C2 Core conformance IES completely new work? 14. Why do we need tools, and what do we need them for? 15. What do we mean by engineering C2 Core for reuse? 16. What is the connection between a COI Vocabulary & C2 Core? 18 Unclassified

Concept – Guidance to OCSWG (harvesting existing data requirements) NOTE: “C2 Core” in this slide represents the resuable data components as developed by the OCSWG from the candidate models. 19 Unclassified

Concept – Guidance to OCSWG (data component development process) NOTE: “C2 Core” in this slide represents the resuable data components as developed by the OCSWG from the candidate models. 20 Unclassified

© 2009 The MITRE Corporation. All Rights ReservedFor Limited External Release Current Status & Future Plans DSSC endorses C2 Core Concept Document as good enough for further development –Wider staffing required, revised draft by September 2009 Next deliverables –Configuration management plan –Conformance specification, UCore extension rules, C2 Core Naming & Design Rules (NDR) –Tools for C2 Core content developers Demonstration objectives –Show a worked example of a C2 Core IES –Built with data components from C2 Core –Conforming to UCore and C2 Core specifications –Add the next layer of technical detail to the C2 Core development process and technical framework 21

© 2009 The MITRE Corporation. All Rights ReservedFor Limited External Release References C2 Core Development Concept C2 Core FAQ Technical Framework and Tools Sub-WG folder 22