The Role of Information Elements in Net

Centric Data Management

Presentation to the Sixteenth Systems and Software

Technology Conference, April 2004
By Silver Bullet Solutions, Inc.

Briefing Outline

Definition of Information Elements

Roles in

Architecture
System Engineering
Information Requirements Description
Systems Analysis
Capabilities Definition

Net Centric Data Strategy

Goals and Elements
IE Roles in the Elements

April 2004

COI Determination and Interaction

Understanding and Discovery
Ontologies
Taxonomies
Harmonization and Mediation
Metadata Attributes

Working Definitions

Information Element

From information --data in context

e.g., Electronic Order of Battle for KP, SPAWAR Execution Year Budget (OMN), Landing
Gear part number for F/A-18 E/F
Language of humans: operators, engineers, designers can communicate

Data Element

An entity, attribute, or relationship or equivalent

e.g., FACILITY, FACILITY-TYPE, FACILITY-GEOLOCATION, FACILITY-MATERIEL-ITEMESTABLISHMENT-NORM, MATERIEL-ITEM-RF-EQUIPMENT, etc. (for EOB)
Language of machines: computer knows what to access

Entity

Class
Diagram
Class

Attribute

Attribute

E-R Model

Equivalences:

Domain Value
April 2004

XML DTD /
Relational
Object DBMS
Schema
Database
Table
Class
Element
Child Element
Field /
Attribute
or Element
Column
Attribute
Instance,
Value

TADILs

MTF

Message

Message

DFI

FFIRN / FFN /
FUDN

DUI

FUD
3

Roles in Architecture
Operational Nodes

Six
important
roles

Data

Operational Activities

Information

System Functions

Systems
Physical Nodes

[9] adapted from [7]

Performance
Technologies
Standards

Notes:
1.
Conceptual view of Core Architecture Data Model (CADM) [9] in DoDAF 1.0 [7]
2.
crows feet means many; on both ends means many-to-many
3.
All entities have recursive many-to-many with themselves (not shown)
April 2004

Roles in Architecture (Reports)

APPLICABLE ARCHITECTURE DATA ELEMENT SETS

TAXONOMY TYPES

Operational Nodes
Organizations, Types of Organizations,
and Occupational Specialties

STRUCTURE

Composition

Generalization &
Composition

Generalization &
Composition

z z z z z

z z

z z

Generalization &
Composition

z z z z z z z z z

System Functions

Composition

Triggers / Events

Generalization &
Composition

Performance Attributes

Generalization &
Composition

Generalization &
Composition

Generalization &
Composition

Systems
Families-of-Systems, Systems-ofSystems, Networks, Applications,

Technical Standards
Info Processing, Info Transfer, Data,
Security, and Human Factors

Technology Areas
Systems and Standards

z = Taxonomy element plays a primary role

= Secondary role

Facilities, Platforms, Units, and

Locations

April 2004

System View (SV)

Physical Nodes

Adapted from [7]

Operational View (OV)

Generalization &
Composition

Operational Activities (and

Tasks)
Information Elements and Data
Elements

Tech
View
(TV)
1 {2} 1 {2} {3} {4} {5} {6} {7} {1} {2} {3} {4} {5} {6} {7} {8} {9} {10 {11 {1}
{2}
AV

z z z

z z z z

z z

z z z z

z z

z z

z z

blank = element not part of this datase

Roles in System Engineering

3.3.1

TDS Interfaces
(2)

Example from AADC

System Spec.

TDS

A D A sse ts
A E G IS
PAC
THAAD
HAW K
CV
CAP

A A D C S y s te m

(U) The AADC system shall receive the TDS track file through an interface to the host TDS including:

P la tfo rm P ro v id e d
V o ic e C irc u its

Jo in t C o m m a n d s
& A D A sse ts

Jo in t In te llig e n c e N e t

JF C
JF A C C
TAOCs
AAMDC
CRC
JE C G
RADCs
JIC O
ADAs
e tc .
A E G IS
PAC
THAAD
HAW K
CV
CAP

L in k 1 1

L in k 1 6
J o in t A ir C o o rd in a tio n N e t

CEC
C om m and N et

P la tfo rm D e p e n d e n t

E a rly W a rn in g T M D N e t

P la tfo rm
P ro v id e d
JD N /JC T N
C irc u its

Jo in t
C m d s,
In te l C e lls
and
A D A sse ts
v ia th e ir
GCCS/
TBM CS
S y ste m s

In te rfa c e C o o rd in a tio n N e t

D a ta L in k C o o rd . N e t

G C C S /T B M C S
S IP R N E T
T A D IX S

T ra c k S u p e r v is io n N e t

IT 2 1
V o ic e P ro d u c t N e t

The AADC system shall be capable of interfacing with multiple TDS

systems.including, but not limited to, AEGIS and Advanced Combat Decision
System (ACDS).

O T C IX S

2.1.1.1
2.1.1.2
2.1.1.3
2.1.2
2.1.3
2.1.4
2.1.5
2.1.6
2.1.7.1
2.1.7.5
2.1.7.6
2.1.7.7
7.1
7.2
7.3
7.4
7.6

Position
Velocity
Acceleration
PVA Confidence
Time
Identification
Threat Intentions
Attributes
ESM/ELINT
Navigation
Radar
EO/IR
Data Exchange Controls
Identification Management
Parametric Data Coordination
Correlation/Association Management
Reporting Coordination

IEs

(V) The AADC system shall provide digital force orders to Air Defense assets over Link 11, Link 16 or
CEC via the host TDS, depending on host TDS implementation of these functions, including:
5.1

Target Data; Offensive / Integrated Prioritized Target List

5.2
5.4
5.7
5.8
6.1
6.3
6.3.4

Surveillance/Sensor Plans
Communications Plans
Defensive/Force Protection
Movement
General Tasking
Tactical Orders
Direct Employment of Communications, Sensor, and Weapon

6.3.6
6.3.7
6.3.8
6.3.9

Engaging Unit/Target Dynamics

Third Party Targeting Data
Platform Resource Allocation
Tactical Order Responses

O th e r N e ts a s r e q u ire d

C U D IX

P la tfo rm C o m m a n d
P la tfo rm T a c tic a l N e ts

P la tfo rm
P ro v id e d
S H F /JP N
C irc u its

K ey
O n B o a rd
O ff B o a rd

April 2004

T A C IN T E L N e ts

TAO
AAW C
SESS

A A D C T ac O ps
A A D C P ln C e ll

A A D C T a c tic a l N e t

Role in Information Requirements

Description (EEIs)
10000

Multi-INT Study EEI Sources

(~3700)
ASOC

CINA

Analysis
Analysis
Map

CINF
Urban
GIRH
J2-USFK

Map

SSC
SpaceWar

OB (Mobile)
Infrastructure (Fixed) ...
Geospatial ...
Networks ...
Political ...

From [15]

SAR

8000

Locate
Track ...
Identify ...
Activity/Status ...
Capability ...
Intent ...

Navy
CINC
Worksheets

WMD
StratSA

9000

Proliferation
Political
OOTW

7000

NEO
Migration

INDB Info Needs Actions

ATNDB

Result
Result

IntlCrime

6000

HumanAssist
Health
ForceMod

5000

Environ
Economic
D&D

4000

CounterTerror
CounterNarc
CounterIntel

3000

StratLift
OvrSeasPresence & ForceProj

(based on comprehensive analysis

of many EEI sources)

InfoSuperiority

2000

FullD-Protect
FocusedLog
Deploy/Redeploy

1000

PrecisionEngage
JSEAD

April 2004

DomManeuver

17 Jan 01 database

Role in Systems Analysis

Existing EEIs
Existing EEIs

Create Multi-INT
Information Needs
database

Devise Multi-INT
Metrics for EEI
satisfaction

Build
Models

Multi-INT Fusion
Multi-INT Fusion
Options
Options

Evaluate
knowledge
matrix
Metric

Information Needs
Information Needs
Database Document
Database Document
plus
plus
Evaluation Results
Evaluation Results

From [15]
Combat
Outcome
Metric

Combat Outcome
----------- C4ISR
April 2004

Data
----------- C4ISR

Knowledge
----------- Data

C2
----------- Knowledge

Combat Outcome
----------- C2
8

Role in Capabilities Definition

JBMC2 -- what information?

Information Categories and Examples

Object
Categories

Examples

Location Movement

Identify

Status

Activity

Intent

OOB

Units, vehicles, sites,

facilities, aircraft,
lat/long
ships, satellites

spd/hdg

country /
alliance,
type/class

Infrastructure

Comm, power,
transportation,
water/sewer

network, grid

throughput,
flow rates,
amps

name, part-of BDA, op

relationships levels

Sociological

Culture, religion,
economic, ethnic,
government, history,
languages

temples,
historic
structures

relocations

names and
associations

political or
stability,
religious
vulnerabilities
activities

religious or
political plans

Geophysical

Terrain, weather,
climatology,
oceanography,
astrometry

feature
lat/long,
alt/dpth

flowraters,
tides

names

sea and river

levels,
temperature

forecasts

readiness

targeting,
reconitering

COA

repair,
broadcasts

expansion
plans

storms,
volcanos

Working papers from [14]

April 2004

Example Service IE Taxonomy

C4ISR INFORMATION
ELEMENTS

ACTION INFO

SITUATION
INFO

GEOPHYSICAL
INFO

MEASUREMENT
INFORMATION

SYSTEM INFO

Generalization to fundamental
semantics allowed mapping across
diverse representations such as:
TADILs
VMF
USMTF

PLATFORM /
FAC / UNIT INFO

IBS
MIDB
C2 Core

Recognition of the equivalent or

similar semantics in the differing
representations would be a first
step toward harmonization or
mediation
A way to manage isSimilarTo [8]

April 2004

11.8 - Kinematics
11.8.1 - Pos / Vel / Acc (PVA)
From [17]
11.8.1.1 - Acceleration
11.8.1.1.1 - Angular
11.8.1.1.2 - Linear
11.4 - Classification
11.8.1.2 - Estimate Type
11.4.1 - Category
11.8.1.2.1 - Estimated
11.4.1.1 - Confidence Level
11.8.1.2.2 - Observed
11.4.1.2 - Estimate Type
11.8.1.2.3 - Predicted
11.4.1.2.1 - Alternative
11.4.1.2.2 - Evaluated Decision 11.8.1.2.4 - Smoothed Data
11.8.1.3 - Position
11.4.1.3 - Value
11.8.1.3.1 - Bearing Angle
11.4.1.3.1 - Air
11.8.1.3.2 - Location; 2D Horizontal
11.4.1.3.2 - Land
11.8.1.3.3 - Vertical
11.4.1.3.3 - Space
11.8.1.4 - Velocity
11.4.1.3.4 - Subsurface
11.8.1.4.1 - Horizontal
11.4.1.3.5 - Surface
11.8.1.4.2 - Vertical
11.4.2 - Platform / Point / Feature Type
11.8.2 - PVA Confidence
11.4.3 - Specific Type
11.8.2.1 - Bearing Angle
11.4.4 - Type Modifier
11.8.2.2 - Bearing Angle Rate
11.4.5 - Unit
11.8.2.3 - Covariance Matrix
11.8.2.4 - Elevation
11.8.2.5 - Elevation Angle Rate
11.8.2.6 - Horizontal AOP
11.8.2.7 - Horizontal Circular
11.8.2.7.1 - TQ
11.8.2.8 - Range
11.8.2.9 - Vertical

Matching The data elements are equal

Mapping The data elements are equivalent

10

Elements of Net-Centric Data Strategy

April 2004

Goals

CO I

M od

el ( s
truct
ure)
X ML
Regi
Re gi
st ry
s try
Disc
ov er
y Se
rvice
Cont
s
ent M
e
tada
Tran
ta
sf orm
a
ti on
GI G
Serv
Polic
ices
ie s
Onto
l ogie
s
Taxo
nom
ie s
Pedi
gr ee
Mod
el
Secu
rity M
odel
NC E
S

Elements

Visible
Accessible
Governance
Understandable
Trusted
Interoperable
Responsive

9 9 9 9
9
9 9 9
9
9
9
9
9
9
9 9 9
9 9
9
9
9 9 9
9 9 9
9 9
9
9
9

Derived from [2],

[3], [4], [6], and
[8]

11

A Spectrum of Data Mgmt

Human filtered
Mitigated by other information
Opportunity for correction
Log

COP
Weather

Examples
Examples

CTP

Working
papers for
[14]

Coupling and deep integration

Ultra-high reliability
Irreversible sudden operational
consequence

April 2004

Automatic
Carrier
Landing
System
signals

Fly-by-wire
guidance
system
data

Selfdestruct
message
data

12

COI Topologies

Types of COIs

Expedient
Institutional
Functional
Cross-Functional
+ others yet to be determined
From [3]

COI Intersections

Working
papers
for [14]

April 2004

13

COIs and Architecture

COIs represent clustering of needs to share information by

Op Nodes

Organizations
Types of organizations
Operational Roles
Occupational Specialties
Operational Activities or Tasks
System Functions
Systems
Physical Nodes
others?

The means by which they interact is the grid

In Architectures these would be clusters of:

April 2004

Working
papers
for [14]

Needlines (Op Nodes)

Activitylines (Op Activities / Tasks)
Functional Interfaces (System Functions)
System Interfaces

14

IEs Support Discovery and Understanding

Top
Top Level
Level

(Reconcile
(Reconcile- -Map)
Map)

Mid
Mid Level
Level

(Bridge
(Bridgebetween
between
Architecture,
Architecture,SoSE,
SoSE,Info.
Info.Rqmts
Rqmts
and
andImplementation
ImplementationDesign)
Design)

Lower
LowerLevel
Level
(Reconcile
(Reconcile- -Map)
Map)

April 2004

TADIL A/B/C/J
IBS
OTH-T Gold
MIDB / GMI NS
VMF
NATO Link-1
ATDL-1
USMTF
CEC

JTAMDO IEs
Navy IEs
GIG Arch IEs
C2 FCB Arch IEs
SIAP IEs
INDB EEIs
etc.
The
The middle
middle
looks
looks like
like aa
taxonomy
taxonomy
child-parent can be:
is-a-part-of
is-a-type-of
C2 Core/JCDB/C2IEDM
JMCDM
USIGS
FDL
SHADE
NID/Mer Ship DB
MEPEDS
EPL/EWIR/NERF
etc.

Human communication
Broad audience
Shorthand meaning

Machine communication
Software Engineers only
Explicit meaning

15

IEs Support Ontology Development

C2 Core [10] (C2IEDM [11] / JCDB) Concepts

From [16]

April 2004

16

IE - DE Mappings Support Mediation and

Harmonization Management
Existing Databases:

Message Standards:
* Tactical Digital Information Link (TADIL)

Variable Message Format (VMF)

United States Message Text Format (USMTF)
Integrated Broadcast System (IBS)
FAAD Data Link
CEC Datalink
Over the Horizon Targeting, Gold (OTH-T Gold)
TACINTEL II
IDS / IRS / ICD

Data Standards:

E
xa

XML Registry
Defense Data Dictionary System (DDDS)

Standard Models:

National source for order of battle, facilities, etc.

Frequency, PRI, PW, etc. for all radars
Commonly used reference data p/o Net-Centric metadata registry
Technical data on ships, aircraft, etc.
Planning data
Readiness data
Frequency, carriers, nodes and links
From w hich COP arises

m
N pl
ot e s
C fo
om r
pl C 4
et IS
e R

Modernized Integrated Data Base (MIDB)

EW Integrated Reprogramming (EWIR)
GCCS Shared Data Environment (SHADE)
Military Characteristics and Performance data (MEPEDS)
Joint Operations Planning and Evaluation System (JOPES)
Status and Operational Readiness and Testing System (SORTS)
Common Cryptologic Data Base (CCDB)
GCCS Track File (TBDM)

Command and Control Core Data Model

Joint METOC Conceptual Data Model
Unmanned Aerial Vehicle / Joint Airborne Surveillance Architecture
Defense Data Architecture models

Standard for command and control

Part of TADIL-J family
Standard for planning messages
Standard for intelligence surveillance data
Forw ard Area Air Defense data link
CEC
COP datalink
Primary datalink for SIGINT systems
Interfaces betw een systems

Namespaces for Ground Ops, GMI, COP, etc.

Legacy registry p/o Net-Centric metadata registry

Data model used in JCDB and C2IEDM

Oceanographic and meterological
Datalinks for UAVs
Funtional area models p/o Net-Centric metadata registry

Visions and Architectures

Fn / FCS / MC2C information requirements
NCOW Ref Model ICOMS
April 2004

Future service architectures

DoD level architecture
17

IEs are a Tool for Object Semantics

Transportation
Size:
Packaged_weight:
Pick_up_location:
Destination:

Mission Planning
Desired_impact_point:
Time_on_target:
Lethality_characteristics:
Applicable_aircraft:

Whats a bomb?

Attachment_time_required:
Wing_placement:
Assembly_instructions:
Arming_instructions:

Ground Operations

Finance
Unit_cost:
Number_required:
Funding_program:
Contract_number:

(Answer all)

Weight:
Minimum_drop_altitude:
Approach_type:
Drop_angle:
Drag_coefficient:

Intended_target:
Casing_thickness:
Detonation_mechanism:
Attachment_mechanism:
Explosive_type:

Flight Planning

Engineering

Adapted
from
MITRE
Corp

IEs
IEsprovide
providetractable
tractablevisibility
visibilityand
andconcurrence
concurrencemechanisms,
mechanisms,inincontext
contextand
and
ininsucceeding
succeedinglevels
levelsof
ofdetail
detailininintegrated
integratedarchitectures
architectures
April 2004

18

Correct IERs Support Net Centric Data

Management

IERs are defined as materiel independent descriptions of

information sharing needs for operations
Op Node that needs the information
To do what
Op node that produces the info
In the course of what
What kind of info
With any special attributes?
How fast?
How secure?
How much?
How protected?
How accurate?
etc.

(org, org type, op role, occupational

specialty)
(op activity, task, process, )
(org, org type, op role, occupational
specialty)
(op activity, task, process, )
(information element)
(timeliness)
(security)
(size)
(IA)
(accuracy)

IERs
IERs Do
Do NOT
NOT Address
Address Communications
Communications ---- Point-toPoint-toPoint,
Point, GIG,
GIG, or
or otherwise
otherwise
April 2004

19

Summary

IEs support many elements of Net-Centric Data Strategy

Exchanges,
Requirements, and
Interfaces
IE Taxonomies
Data Element Mappings
Exchange and Interface
Attributes
IE-Level Conceptual
Models
April 2004

M od

Elements

CO I

Information

el ( s
truct
ure)
X ML
Regi
Re gi
st ry
s try
Disc
ov er
y Se
rvi ce
Cont
s
ent M
e
t
ada t
Tran
a
sf orm
a
tion
GIG
Serv
Polic
ices
ie s
Onto
logie
s
Taxo
nom
ie s
Pedi
gr ee
Mod
el
Secu
ri ty M
odel
NC E
S

Net Centric Data Strategy Elements

9
9 9
9
9

9
9 9

9
9

9 9
9 9
20

References
1)
2)
3)
4)
5)
6)
7)
8)
9)
10)
11)
12)
13)
14)
15)
16)

17)

April 2004

DoD Data Administration, DODI 8320.1, OASD (NII) / DoD CIO, 26 Sept 1991
Department of Defense Net-Centric Data Strategy, OASD (NII) / DoD CIO, 20 April 2003
Communities of Interest in the Net-Centric DoD Frequently Asked Questions (FAQ), Draft, OASD (NII) /
DoD CIO, 13 March 2004
The DoD Net- Centric Data Strategy And Discovery & Mediation Enterprise Services, briefing by OASD
(NII) / DoD CIO, 3 Nov 2003
DoD Net-Centric Data Management Strategy: Metadata Registration, memorandum, OASD (NII) / DoD
CIO, 3 April 2003
Department of Defense Discovery Metadata Specification (DDMS), Version 1.0, Deputy Assistant
Secretary of Defense (Deputy Chief Information Officer), 29 September 2003
Department of Defense Architecture Framework, Version 1.0, OASD (NII) / DoD CIO, 9 Feb 2004
DoD XML Registry at http://diides.ncr.disa.mil/
CADM documentation and model at https://pais.osd.mil/enterprisearchitectures)
C2 Core documentation and model at http://www-datadmn.itsi.disa.mil/datadmn/dda/c2core.html
C2IEDM documentation and model at Multilateral Interoperability Program: http://www.mip-site.org/
Defense Data Architecture (DDA), documentation and models available at http://diides.ncr.disa.mil/
Information Integration for Concurrent Engineering (IICE), IDEF5 Method Report, Armstrong Laboratory
(AL/HRGA), Wright-Patterson Air Force Base, Ohio, 21 Sept 1994
Joint Battle Management Command and Control (JBMC2) Roadmap, OUSD (AT&L) / JFCOM, Feb 2004
Keithley, H., Multi-INT Fusion Performance, Joint C4ISR Decision Support Center, OASD(C3I),
Washington, D.C., 2001
Ontology and Fusion (McDaniel, D., Multi-Hypothesis Database for Large-Scale Data Fusion, Proceedings
of the Fifth International Conference on Information Fusion, International Society of Information Fusion,
Sunnyvale, CA, 2002)
Naval C4ISR Operational Architecture, Space and Naval Warfare Systems Command (SPAWAR), 1997

21