UNCLASSIFIED1

UNCLASSIFIED

Universal CoreOverview

June 2007

UNCLASSIFIED2

UNCLASSIFIED

DoD and IC Universal Core Data Schema

Constructing a universal core data schema that enables information sharing

– Ways to describe “when, where, what”

– Minimal set of terms in the core– Agreed to by DoD and Intel

Community– Appropriate use of open and

Federal standards– Extensible by COIs and systems

as needed– Extensible by COIs and systems

as needed

Strike Spiral 1 pilot is based on initial C2 common core (e.g., Task/Mission)

– Incorporates universal core

Increased Data Interoperability AND Agility

2

Log

Common

Core **

C2 Common Core

ISR Common

Core **

Financial Common Core **

EIE

Com

mon

Cor

e **

Universal Core

COI Extensions

DoD Component and IC Member Extensions

** With the exception of the C2 Common Core, the other Common Core’s are notional

UNCLASSIFIED3

UNCLASSIFIED

Start with just the most common

One system,info intersection

is everything

Two systems,much info less

is common

Three systems,Intersectiongets smaller

Universal Core starts here

with a core setof common info!

Typical approach: Add new information for each new system exchange... Model continues to get larger and larger

and difficult to manage

UNCLASSIFIED4

UNCLASSIFIEDMining the XML Registry for Common Elements

Identified “data nuggets” that represent common data concepts*

– Position (10199 candidate elements – 10.3%)

– Quantity (10035 candidate elements – 10.1%)

– Shape (7241 candidate elements – 7.3%)

– Time (14161 candidate elements – 14.3%)

– Type (15444 candidate elements – 15.6%)

Position Lattitude Longitude Elevation Location Total (unique elements)1842 745 742 180 6836 10199

Quantity Measure Length Range Measurement Meter Max Length Total (unique elements)3244 770 484 790 1699 3712 8 10035

shape Area Point Line Geographic Surface Dimension Total (unique elements)175 1969 2581 921 1209 737 330 7241

Type Aircraft Equipment Facility Materiel Personnel person Total (unique elements)10736 1578 1483 1295 1279 821 511 15444

Time Effective Date Date Day Total (unique elements)10032 126 5153 4860 14161

* From late 2005 - believe percentages are still valid

UNCLASSIFIED5

UNCLASSIFIED

Universal Core Background DoD Directive 8320.1

– Attempted to define a large data model for all DoD systems to adopt

– Too difficult to harmonize, implement, and scale

DoD Directive 8320.2– Define and implement interoperability around Communities of

Interest– Success harmonizing across the community and streamlining

implementation

Cursor on Target– Simple, small, and powerful exchange standard– Applied loose coupling strategy– Led to numerous implementations and real warfighter capabilities

Universal Core– Leverages the harmonization success of Communities of Interest– Simplicity and power of Cursor on Target– Application of commercial and DoD/IC standards

UNCLASSIFIED6

UNCLASSIFIED

Universal Core Key Principles

Key Principles – Build a strong foundation

Policy, Governance, Definition, and Test processes

– Build Joint from the start DOD and IC communities

– Harmonize across communities– Standards based– Small core with the following attributes

Suitability - include only a few critical objects Simplicity - for widespread adoption Extensibility - to meet individual community needs Leveragability - of existing standards, tools, and expertise Supportability - for long-term success

UNCLASSIFIED7

UNCLASSIFIEDGovernance Process – Senior Enterprise Services Governance Group (SESGG) Oversee Joint Data Strategy and Enterprise

Services Implementation

– Define the required measurement and control mechanisms to ensure DoD-wide and IC-wide implementation

– Identify and develop necessary policy changes, including measurement and control responsibilities, to ensure consistent implementation

– Establish oversight forums, as required, to enable the DoD CIO and DNI CIO to review implementation progress

UNCLASSIFIED8

UNCLASSIFIED

SESGG Members

Mr. Mike Krieger, co-chair, DoD CIOMr. John Brantley, co-chair, ADNI CIOMr. Ron Bechtold, Army, Mr. Brian Clingerman, Navy,Mr. Kent Werner, AFMr. David Green, USMCMs. Bobbie Stempley, DISAMr. Mac Townsend, DIAMr. Dennis Wisnosky, BTA

UNCLASSIFIED9

UNCLASSIFIEDUniversal Core Harmonization, Governance, Policy, Test

Four Working Groups, each containing participation from all the organizations that make up the SESGG

– DNI and Navy lead the methodology for describing and evolving the universal core schema

– AF leads the development of Governance processes

– JFCOM and Army lead the Test and Evaluation methodology

– DIA and DoD lead the Policy definition

UNCLASSIFIED10

UNCLASSIFIED

Standards-based Approach

GML 3.2.1 (ISO-19136) based on the ISO-19100 series– ISO-19103 – Conceptual Schema Language– ISO-19107 – Spatial schema (geometry and topology

objects)– ISO-19108 – Temporal schema (temporal geometry,

topology, temporal reference systems)– ISO-19109 – Rules for application schemas– ISO-19111 – Spatial referencing by

coordinates (coordinate reference systems)– ISO-19123 – Schema for coverage

geometry and functions Key XML standards

– W3C XML Schema– W3C XLink

Security Tagging– IC-ISM (Intel Community - Info Security Marking)

GML Profile- Logical Subset of GML Standard

GML ProfileLogical Subset of GML Data

Types/Subset of gml:elements/attributes

11

Universal Core – What, When, Where

Security Marking – IC ISM

Identification – gml:feature– gml:id– gml:name & gml:description

Time & Geo Bounding– gml:boundedBy

Object Type – cc:type– encoded via gml:dictionary

Operational Info

Association – cc:link (xlink)

12

Security Marking – IC-ISM

Approach– IC ISM tagging

Required classification, ownerProducer Other optional attributes

– Structure document to support “tear-lines”

““Low”Low”

Releasable SAReleasable SA

““High”High”

Situational Awareness InfoSituational Awareness InfoCross Domain Guard

13

Resource Linking

Generic linking to other documents– To other Universal Core-based

schemas– To other non-Universal Core-based

schemas

Utilize W3C xlink standards Utilize locator link

– xlink:type – “locator”– Xlink:href – link to object– Xlink:role – meaning of link– Xlink:title – (String) Description of

associations– Xlink:label – (String) – label for

referenced object– element property (xs:string) – used to

describe the hierarchical type code of referenced object

<uc:link

xlink:href="http://www.aoc.mil/missionXYZ" xlink:role="OBJ.TASK.PRIMARY“

xlink:title="Primary Mission" \>

14

UNCLASSIFIED15

UNCLASSIFIED

Dictionary

Dictionary – structure to define terms/vocabulary

– contains dictionaryEntries where each dictionaryEntry has a definition

gml:Definition

– identifier – unique identifier of the term

– name – synonyms for the term being defined

– description – textual definition of the term

– descriptionReference – link to definition of term

– remarks – additional clarifying comments about the term