C2 Core Technical Framework & Tools Sub-Working Group (TSWG) Status Report

1. C2 Core Technical Framework & Tools Sub-Working Group (TSWG)Status Report Dr. Scott Renner4 February 2009 For Release to All Sponsors

2. Background • C2 Core concept originates in 2007 • Envisioned as one of several domain-specific extensions to UCore • Both UCore and C2 Core are concerned with the content of information exchange • Syntax and semantics • No interest in systeminternals

3. Working Group Organizational Structure Configuration Control Board C2 Core Working Group C2 Core Operational Content Sub-Working Group Verification, Validation & Implementation Sub-Working Group Technical Framework and Tools Sub-Working Group UNCLASSIFIED

4. Applying UCore and C2 Core UCore Current Focus: How does a COI use core vocabulary artifacts in the information exchange specification (IES)? C2 Core C2 COI IES defines application application IEP information exchange package

5. IAT Report: C2 Core, In Four Parts • C2 Conceptual Data Model and Vocabulary • Concerned with semantics • Appropriately captured in OWL-DL • C2-Specific Extensions from UCore • Schema components & vocabulary added to UCore • C2 Core Service Specifications • Functional definition of mission services • Concerned with info exchange content, not plumbing • May include implementation-level definitions • C2 Information Sharing Framework (C2ISF) • Run-time data sharing environment • Plumbing, not content

6. Four Parts Of C2 Core C2 Conceptual Model & Vocabulary UCore C2-Specifc Extensions to UCore C2 Core C2 COI C2 Core Service Specifications C2 Information Sharing Framework IES defines application application IEP information exchange package

7. Feedback Process Four Parts Of C2 Core C2 Conceptual Model & Vocabulary UCore C2-Specifc Extensions to UCore C2 Core C2 COI C2 Core Service Specifications C2 Information Sharing Framework IES defines application application IEP information exchange package

8. Technical Framework & ToolsSub-Working Group C2 Conceptual Model & Vocabulary UCore C2-Specifc Extensions to UCore C2 Core C2 COI C2 Core Service Specifications C2 Information Sharing Framework IES defines application application IEP information exchange package

9. Current Focus UCore What sort of things belong in here? C2 Core C2 COI How does this junction work? How are they usedin these IESs? IES defines application application IEP information exchange package

10. Herman Kahn’sFour Orders Of Agreement • First order agreement is agreement on substance. • Second order agreement is agreement about what the argument is about. If A and B have achieved this, either should be able to explain the argument to C and each should be willing to accept the other's explanation. • Third order agreement is an understanding on why second-order agreement cannot be achieved. When third-order agreement is reached, each party can explain satisfactorily to a third why his opponent thinks the two cannot really come to grips on relevant issues and facts and eventually achieve a second-order agreement. • Fourth order agreement is the simple assertion by one or both parties that the other is too stupid or biased for further discussion to be worthwhile.

11. Sub-Working Group Structure • GOAL: Balance representation vs. size to ensure max productivity • Chair / Co-Chair provides for shared leadership responsibilities • Recorder is an important role to ensure accurate documentation and act as historian for SWG activities • Core working group of 5-8 members is the key to ensure max productivity. Staff members will be used to develop the majority of read- aheads and products • Review Group of ~10 members to vet and validate work of core working group and are less involved in development of products Chair Co-Chair Recorder Core Group 5-8* Review Group ~10 *May also include staff to develop products and read-aheads to be vetted and discussed by Core Group. UNCLASSIFIED

12. Status • Core team kickoff meeting – Jan. 28-29 • Established shared assumptions and objectives • IAT sanity check – Feb. 3 • Have we correctly understood the IAT report? Yes • Are the core team assumptions & plans OK? Yes • C2 Core Concept of Operations (DRAFT) • On or about Feb. 23 • About two weeks for review team study • About one week for core team to make changes • Results ready for DSSC meeting in March