C2 Core Tutorial

Mr. Frank W. KlucznikData and Services DivisionUnited States Joint Forces Command

Content

C2 Core’s Objective

Historical Context

C2 Core Overview

C2 Core Developer Support Network (C2CDSN) Overview

Objective - Shard Understanding

Shared Understanding

Shared Operational Picture

Shared Tactical PictureCommander

CommunityCapability

CommunityCapability

Staff/ Watch Officers

Staff/ Watch Officers

Collaboration & Coordination

CommunityInformationSharing

Net-CentricInformation Sharing

CommonSemantics

CommonSemantics

Commander

3

Historical Context

System

Data Consumer

System

Message / Info Exchange Package /

Document

IEP

Data Source

defines

Message Format / Information Exchange Specification /

Document Schema

IES

4

Process

System

Data Source Data Consumer

System

Message /Info Exchange Package /

Document

XML(probably)

ConsumerVocabulary

ProducerVocabulary

If these aren’t

compatible

This won’t work

5

Pairwise Solution

application

Data Source Data Consumer

application

Message /Info Exchange Package /

Document

Vocabularynegotiate negotiate

Communityof Two

TRANS TRANS

Shared knowledge is embedded in translation software… very hard to get the knowledge back out for software maintenance, or for connecting with other partners

IEP

6

Pairwise Solution

The N2 problem15 applications

210 negotiationsTotal level of effort is O(n2)1 2

3

4

5

6

10

11

12

13

14

15

7

89 7

Does not scale in a large enterprise

Community of Everyone

1 2

3

4

5

6

10

11

12

13

14

15

7

89

Vocabularyfor

Everything

8

The mission of everyone

changes much faster than the

vocabulary can change

Community of Everyone

1 2

3

4

5

6

10

11

12

13

14

15

7

89

Vocabularyfor

Everything

Too much knowledge must be learned by too many people

A top-down approach ignores knowledge

people already have

This learning is expensive, and takes a long time

9

Communities of Interest

COIX

COIY

COIZ

VocabularyX

VocabularyY

VocabularyZ

If you can’t have one universal vocabulary understood by everyone,then you must have several vocabularies, each understood by some group

10

Communities of Interest

translate

COIX

COIY

COIZ

VocabularyX

VocabularyY

VocabularyZ

translate

X&Y Y&Z

When COIs must exchange data, we must translate between vocabularies(This by itself is an improvement: N2 is not so bad when N is small)

11

Optimizing COI Vocabularies

• Analysis indicates the best possible arrangement of COIs and vocabularies:– A small number of broad, shallow vocabularies:

few definitions, understood by many people– A larger number of narrow, deep vocabularies:

many definitions, understood by few people– Arranged in a rough hierarchy;

deep vocabularies adopt and extend the shallow

# people in community

# definitions in vocabulary

broad and shallow vocabulary

narrow and deep vocabulary

narrow and deep

vocabulary

specialized, extended vocabularies

12

• Partitioning knowledge between communities:– Achieve some of the most valuable interoperability– While retaining agility / flexibility in face of changing needs– Reducing cost and time to implement

• Universal and common core vocabularies improve interoperability while retaining agility and local autonomy

C2COI#1

C2COI#2

Universal Core

Common Core #1

Common Core

#2

C2 Core

Optimizing COI Vocabularies

Resulting Data Architecture

Universal Core

C2 Core

Common Core

Common Core

COI COI

COICOI

COICOICOI COICOICOI

What is C2 Core?

Open (XML based) Data Exchange Standard

First major implementation of UCore v2.0

Composition• Vocabulary and data model• Architectural Framework• Reusable XML Components

An evolving open standard built by the C2 Community for the C2 Community

Relationship to Others

Relationship analogous to Federal – State – City regulatory governance construct

UCore v2.0• ULEX Message Framework• 4Ws (who, what, when, where)• 5 methods of extension

C2 Core • C2 Vocabulary• Specs for Payload Extension• XML Naming & Design Rules• Info Exchange Specification

COI / POR

C2 Core Architecture

IES – Information Exchange SpecificationIEP – Information Exchange Package

C2 – Command and ControlCOI – Communities of InterestPOR – Programs of Record

IES

Technical Architecture Maturation

2008 2009 2010ULEX/UCore ULEX/UCore/C2

CoreImplementation

Options

Digest Focused Approach

Payload Focused Approach

Support broad range of exchange environments

C2 Core Today

V1.0 Content (ready for piloting)• Semantic Overlaps Across C2• Conceptual Data Model

V1.0 Technical Specifications • Development Concept & FAQ• Naming and Design Rules• Conformance Specification• IES Specification

Technical Analysis• XML Compression Analysis• Implementation Patterns Analysis• C2 Core Usage Patterns

Developer Tools & Support • C2 Core Developer Support Network • Schema Subset Generation Tool• Conformance Tool• Training (Levels I, II, III, IV)

Plans & Processes• Configuration Management Plan• Change Request Process

Guidance and Misc Documentation • Implementation Guidance• Value Proposition • IES Development Guide• C2 Core Version Architecture

Governance• C2 CPM DSSC• Configuration Control Board & Charter• C2 Core Work Group• Technical Evaluation Teams

Community Outreach & Training• C2 Core Training & Familiarization• New content development

(e.g. GFMDI, ASW COI, et al)• Conferences (e.g. DON IT, DoD

Enterprise Architecture, et al)• Technical Exchange (e.g. UCore)

Experimental Products• C2 Core-UCore Binding Specification• C2 Core Genericode Specification

Key Training Components

Topics

Lessons

48 Lessons covering 270+ topics

• C2 Core Level I, II, III Material• IES Development Guide• Data Modelers Guide• C2 Core NDR Guide• Schema Writers Guide• XML Tutorial• Tool User Guides

Designed to support roles of:

• Manager• Data Architect• Developer

Training Sample

1.0: C2 Core Subset Schemaappinfo: Metadata for C2 Core conformant objectsstructures: Defines how c2core objects are structuredexternal: External standardsproxy: Wraps XML simple types (e.g. int, bool, etc.) in a complex type to comply w/ C2 Core NDRadapters: C2 Core objects pointing to external standardsucore: UCore digest content*-extension.xsd: C2 Core conformant COI extensions to C2 Core objects & community defined data components. Non-conformant content may be imported in to a separate XSD for legacy support

Wantlist.xml: Defines root element of the exchange

NOTE: Black generated by SSGT Green added manually Red added manually

Subset

- c2core.xsd

- appinfo.xsd

- ic-ism-v2.1.xsd

- structures.xsd

c2core

1.0

appinfo

external

structures

- ies-extension.xsd- exchange.xsd

ucore

- xsd-proxy.xsdproxy

adapters

- wantlist.xml

- coi-extension.xsd

- ucore.owl- ucore.xsd- et al ucore schema

- tspi-adapter.xsd

IES Package Content

END