Page 1 1 Stephen Turczyn 6 October 2005 CECOM Software Engineering Center Army Data Strategy.

1

Stephen Turczyn6 October 2005

CECOM Software Engineering CECOM Software Engineering CenterCenter

CECOM Software Engineering CECOM Software Engineering CenterCenter

Army Data Strategy

Agenda

• DoD Net-Centric Data Strategy

• SEC’s Role in Data Strategy

• SEC’s Team

• Net-Centric Warfare Challenges

• Net-Centric Implementation

• COIs/Working Groups

• SEC C4ISR Ontology effort

• DoD Net-Centric Data Strategy

• SEC’s Role in Data Strategy

• SEC’s Team

• Net-Centric Warfare Challenges

• Net-Centric Implementation

• COIs/Working Groups

• SEC C4ISR Ontology effort

DoD Net-Centric Data Strategy

DoD Net-Centric

Data Goals:

• Ensure data is: • Visible• Available• Understandable• Trusted• Interoperable• Responsive to users’ needs

• Institutionalize Data Management

UbiquitousGlobal Network

MetadataCatalogs

Enterprise &Community

Web Sites Application Services

(e.g., Web)

Shared DataSpace

Metadata Registries

Security Services(e.g., PKI,

SAML)

Consumer

COI / Developer

Posts to and uses metadata registries to structure data and document formats for reuse and interoperability

ProducerSearches metadata catalogs to find data

Analyzes metadata to determine context of data found

Pulls selected data based on understanding of metadata

Describes content using metadata

Posts metadata in catalogs and data in shared space

Strategy enabled by data forums (COIs, WGs, IPTs) , metadata, registries, catalogs and shared data spaces

Army Data Strategy

• Provide Army enterprise level oversight & direction• Develop and refine Army Net-Centric Data Strategy• Harmonize information sharing across Army Mission Areas and Domains • Promulgate Army Data Policy and Guidance• Ensure Compliance with DOD Net-Centric Data Strategy Policy and

Guidance• Support Army Mission Area’s net-centric data strategy responsibilities &

tasks • Support the development of the LandWarNet Architecture• Orderly migration of current force data to Army’s Data Centric

transformation.• Develop a Data Strategy and implementation approach to COI

development, systems developers and testing of emerging data model framework.

• Provide guidance and direction in development of Data Products and prototypes that implement the Army’s Data Strategy goals and objectives.

CIO/G6

Yesterday:Standards

Today:“Army Data Strategy”“Army Data Strategy”

VMF

USMTF

TDL

FutureStandardsWork

Configuration ControlConfiguration Control

ICPs

Position Papers/ Coordinated Papers

VID

CNR

Transitions to GIG NCES

Data Modeling& Products


COI AdministrationCOI Administration

Data System Engineering Data System Engineering

Data ValidationData Validation

Data Strategy

COI Administration

COI Administration

Data System Engineering Data System Engineering



Configuration Control

Configuration Control

Data Test Support

Data Test Support

Objectives

Near Term: Migrate from Development/CM of Messaging Standards to the development of common data products (Ontologies, meta-data registries, XML schemas, taxonomies, etc…) for the Army Warfighter and ensure interoperability with the JIM communities.

Far Term: Facilitate the execution of the Army Data Strategy and provide users with common and overarching data products and services to promote interoperability and faster access, retrieval, analysis and utilization of data.

• Provide Enterprise Data Assets

• Manage Data Infrastructure • Govern Data Activities

COI Administration• Army Data Strategy COI Policy• Chair/Participate in delegated COIs

Data Systems Engineering• Analyze Technology Gaps Related to Data Strategy• Analyze XML schema development and alignment• MetaData Requirements Analysis• Service Oriented Architecture analysis supporting GIG concepts of discovery and data visibility and accessibility• Migration Studies (VMF, USMTF, TDL)

Data Model & Products• Army Data Net-Centric Roadmap• Support Development of Data Policies• XML Schema Implementation Guidelines• Unified Modeling Language (UML) support• Develop and Update C4ISR Ontology• Investigate automated translation services between data products (IDEF1X, UML, XML)

Data Validation• Formulate concepts of data validation• Develop and Maintain Test and Compliance Tools

•C4ISR Data Ontology Validation Tool• Validate XML Schema Compliance

Configuration Management• Formulate and Execute Army Warfighter CM Strategy and Plan• Execute CM Activities

SEC Support to Implementation of theDoD Net Centric Data Strategy

• Data Planning

• The transformation of the DoD to a Net- Centric Warfare environment presents challenges to the Services/Agencies

• It presents even more challenges at the tactical level due to bandwidth limitations inherent at lower echelons

• Net-Centric capabilities can be achieved by extending existing tactical messaging capabilities

• The transformation of the DoD to a Net- Centric Warfare environment presents challenges to the Services/Agencies

• It presents even more challenges at the tactical level due to bandwidth limitations inherent at lower echelons

• Net-Centric capabilities can be achieved by extending existing tactical messaging capabilities

Net-Centric Warfare Challenges

Army Implementation of DOD Goals

DoD Goal

Visible

Available

Interoperable

Trusted

Institutionalized

Responsive

Understandable

Army Policy (AR 25-1)

Community of Interest (COI)

Extensible Markup Language (XML)

Authoritative Data Source (ADS)

Information Exchange Standard Specification (IESS)

Enterprise Identifier (EID)

Shared Data Spaces

Metadata Catalog

COIs

• Blue Force Tracking (Forming)

• Time Sensitive Targeting (Effective)

• NetOps (Forming)

• USMTF

• Anticipated Requirements: FCS Proposed COIs

• Blue Force Tracking (Forming)

• Time Sensitive Targeting (Effective)

• NetOps (Forming)

• USMTF

• Anticipated Requirements: FCS Proposed COIs

Communities of Interest

https://gesportal.dod.mil/sites/coidirectory/default.aspx

Software Blocking

• Serve as Chair to Data Sub-IPT

• Developed Draft Charter

• Purpose: – The SWB Data Sub IPT will coordinate the development, integration and assessment of data

products, tools, architecture, policies, plans and procedures in support of a net centric, joint and coalition capable Army. The Sub IPT will provide recommendations to the SWB and Battle Command (BC) working groups/IPTs. The goal for this Sub IPT is to manage and engineer the transition of data from the Army As Is (Army Battle Command Systems (ABCS), multiple data bases, Message based transport) position to the Army To Be (Future Combat Systems (FCS), Common Information Exchange Data Model, distributive data transport).

• Scope: – The SWB Data Sub-IPT will support the Net-Centric Data Strategy, inform and coordinate technical

discussions on data strategy (i.e. 7 DoD goals, leverage products from Communities of Interest, develop data asset products,), provide collaborative solutions for data issues with respect to SWB systems, and ensure technological and policy currency to effectively drive the migration of SWB systems to a net-centric environment. It will synchronize and facilitate timely implementation of DoD standards and executive directives that affect the Army data strategy.

• Serve as Chair to Data Sub-IPT

• Developed Draft Charter

• Purpose: – The SWB Data Sub IPT will coordinate the development, integration and assessment of data

products, tools, architecture, policies, plans and procedures in support of a net centric, joint and coalition capable Army. The Sub IPT will provide recommendations to the SWB and Battle Command (BC) working groups/IPTs. The goal for this Sub IPT is to manage and engineer the transition of data from the Army As Is (Army Battle Command Systems (ABCS), multiple data bases, Message based transport) position to the Army To Be (Future Combat Systems (FCS), Common Information Exchange Data Model, distributive data transport).

• Scope: – The SWB Data Sub-IPT will support the Net-Centric Data Strategy, inform and coordinate technical

discussions on data strategy (i.e. 7 DoD goals, leverage products from Communities of Interest, develop data asset products,), provide collaborative solutions for data issues with respect to SWB systems, and ensure technological and policy currency to effectively drive the migration of SWB systems to a net-centric environment. It will synchronize and facilitate timely implementation of DoD standards and executive directives that affect the Army data strategy.

Data Sub-IPT

WMA IWG

Requirements:• Common Information Exchange Data Model • Information exchange between Battle Command systems• Implementing the BC Migration Plan• Standing up the Data Initialization COI• Developing OV-7• Developing the XML Schemas

• SEC Chairs the Data Architecture Subworking Group

NESI

• Data Task Team Participation• NESI Background:

– NESI provides implementation guidance to facilitate the design, development and usage of information systems for net-centric warfare

• A Cross-Service effort – Air Force (ESC) and Navy (PEO C4I & Space) MOU– Extends Air Force and Navy net-centric initiatives

(RAPIDS/C2ERA)– Army and DISA are candidate members

• Data Task Team Participation• NESI Background:

– NESI provides implementation guidance to facilitate the design, development and usage of information systems for net-centric warfare

• A Cross-Service effort – Air Force (ESC) and Navy (PEO C4I & Space) MOU– Extends Air Force and Navy net-centric initiatives

(RAPIDS/C2ERA)– Army and DISA are candidate members

Net-Centric Enterprise Solutions for Interoperability

“Better, Cheaper Net-centric Applications to Field Earlier”

FCS DACAN

• Goal: Create a common database resulting from FCS ORD.

• Objectives: To provide an overview of the SSEI processes, a forum for discussion for FCS data related issues, visibility of the IPTs data related efforts, and review of customer expectations agreements.

• Goal: Create a common database resulting from FCS ORD.

• Objectives: To provide an overview of the SSEI processes, a forum for discussion for FCS data related issues, visibility of the IPTs data related efforts, and review of customer expectations agreements.

Data Architecture: Chief Architect’s Network

Return

Mapping of Proposed FCS COIs to Domains/COIs

NOTE - ACF = US, Allied & Coalition Forces

Note that scope of current COIs may not match scope needed for FCS-recommended COIs

Green - in OSD COI RegistryYellow - identified WG/COI Red - No mapping to WG/COI (new)

Army Implementation of DOD Goals

DoD Goal

Visible

Available

Interoperable

Trusted

Institutionalized

Responsive

Understandable

Army Policy (AR 25-1)

Community of Interest (COI)

Extensible Markup Language (XML)

Authoritative Data Source (ADS)

Information Exchange Standard Specification (IESS)

Enterprise Identifier (EID)

Shared Data Spaces

Metadata Catalog

• Ontologies enable data to be understandable by promoting semantic and syntactic understanding of data.

• Ontologies include data categorization schemes, thesauruses, vocabularies, key word lists, and taxonomies.

• Communities Of Interest (COIs) will be encouraged to develop an ontology that best reflects the community understanding of their

shared data.

• Any community that establishes an ontology will publish it to the DoD Metadata Registry to increase understanding across the Enterprise and promote possible reuse.

The Role of an Ontology WithinThe DoD Net-Centric Data Strategy

An Ontology:

• Defines the basic terms and relations comprising the vocabulary of a topic area, as well as the rules for combining terms and relations to define extensions to the vocabulary.

• Is an orderly formalization of concepts, definitions, relationships and rules that captures the semantic content of a domain in a machine-readable format.

What is an Ontology?

•Aid in the Chief Information Officer’s objective of creating a net-centric environment within the Department.

•Establish the C4ISR Data Ontology to Increase the understanding of captured data across the Enterprise for interoperability.

•Promote reuse of the C4ISR Data Ontology across Enterprises.

•Support the Integrated Data & Symantec Web Environment being

developed for the Warfighter.

•Aid system developers, integrators and architects in performing the following functions:

Information Exchange Standards Requirement RefinementArchitecture DevelopmentData Exchange Gap Analyses.

SEC’s Ontology Effort

C4ISR Data Ontology

Data Elements

DataModels

MessageStandards

COIs &Programs

C2IEDM SpecificConcepts

SpecificConcepts

MIP

UAIM

FCS VMF

SpecificConcepts

TDL

SpecificConcepts

TSTMTF

SpecificConcepts

BC

{ { {

C4ISR Data Ontology Functional Structure

Future Concept Domains

Implemented Concept Domains

C4ISR Data Ontology Scope

Ontology efforts focus on Warfighter Mission Area and Legacy System, data exchange. This effort includes mapping legacy/current information exchange standards to a core Data Element based on C2IEDM and identifying/adding extensions as necessary. Ontology component examples:

Data Models:• C2IEDM: Use as foundation for C4ISR Data Element Core• J3CIEDM: Migrate C4ISR Core by comparing and making necessary mods• Future Combat System (FCS): Assist PM data modelers to compare FCS DM to C4ISR

Core and identify deltasMessaging Standards• Variable Message Format (VMF): Joint/Army tactical bit oriented C2 & SA messaging

standard at Brigade and below• US Message Text Format (USMTF): Joint/Army tactical/theater character oriented

C2 messaging standard at Division and above• Tactical Data Links (TDL): Joint/Army tactical real time air/air defense

opearations fixed format messaging standardsApplications:• Data Acquisition Application: Performs automatically the functions of; converts legacy

system into OWL, compares the scope of each Ontology/Domain/Data Model to determine relationships, documents results, integrates data, and updates the baseline ontology.

Conclusion

• Promulgation of DOD Net-Centric Data Strategy is key to achieving future Interoperability

• Net-Centric Data Strategy critical to development & implementation of net-centric operation environment

• Army transforming to promulgate Data Strategy:– Established Army enterprise level Net-Centric Data Forum – Working with Army programs through Software Blocking and

Warfighter Mission Area forums– Working with other Services/DISA through NESI & joint forums

• PEOs/PMs need to identify their COI requirements

Page 1 1 Stephen Turczyn 6 October 2005 CECOM Software Engineering Center Army Data Strategy.

Documents

Transcript of Page 1 1 Stephen Turczyn 6 October 2005 CECOM Software Engineering Center Army Data Strategy.