UNCLASSIFIED FOUO CIO/G6 Presentation to Army Configuration Control Board 24 Jan 07.

UNCLASSIFIED

FOUO

CIO/G6 Presentation toArmy Configuration Control Board

24 Jan 07

2 UNCLASSIFIED

Purpose/Agenda

• Provide information briefing to ACCB Stakeholders Group on CIO/G6 activities related to this forum

• US-JC3IEDM Configuration Management

• Spectrum Architecture

• Data Strategy

3 UNCLASSIFIED

Joint Command Control Consultation Information Exchange Data Model

4 UNCLASSIFIED

JC3IEDM “Common Data Framework” Enables Interoperability

Contains Architecture Products (e.g., OV7/SV 11) that can be reused

• Common Structure and Building Blocks• Extensible by Mission Area, Domain andCOIs• Common Core Links Extensions• Provides Framework for Information Sharing Agreements

Reporting Data

Object-Item

Capability

Object-Type

Location

Action Reporting Data

Object-Item

CapabilityCapability

Object-TypeObject-Type

Location

Action

OBJECT-TYPE OBJECT-ITEM

ORGANIZATION -TYPE

MATERIAL-TYPE

PERSON -TYPE

FACILITY-TYPE

FEATURE-TYPE

ORGANIZATION

MATERIAL

PERSON

FACILITY

FEATURE

OBJECT-TYPE OBJECT-ITEM

ORGANIZATION -TYPE

MATERIAL-TYPE

PERSON -TYPE

FACILITY-TYPE

FEATURE-TYPE

ORGANIZATION

MATERIAL

PERSON

FACILITY

FEATURE

Reporting Data

Object-Item

Capability

Object-Type

Location

Action Reporting Data

Object-Item

CapabilityCapability

Object-TypeObject-Type

Location

Action

OBJECT-TYPE OBJECT-ITEM

ORGANIZATION -TYPE

MATERIAL-TYPE

PERSON -TYPE

FACILITY-TYPE

FEATURE-TYPE

ORGANIZATION

MATERIAL

PERSON

FACILITY

FEATURE

OBJECT-TYPE OBJECT-ITEM

ORGANIZATION -TYPE

MATERIAL-TYPE

PERSON -TYPE

FACILITY-TYPE

FEATURE-TYPE

ORGANIZATION

MATERIAL

PERSON

FACILITY

FEATURE

Reporting Data

Object-Item

Capability

Object-Type

Location

Action Reporting Data

Object-Item

CapabilityCapability

Object-TypeObject-Type

Location

Action

OBJECT-TYPE OBJECT-ITEM

ORGANIZATION -TYPE

MATERIAL-TYPE

PERSON -TYPE

FACILITY-TYPE

FEATURE-TYPE

ORGANIZATION

MATERIAL

PERSON

FACILITY

FEATURE

OBJECT-TYPE OBJECT-ITEM

ORGANIZATION -TYPE

MATERIAL-TYPE

PERSON -TYPE

FACILITY-TYPE

FEATURE-TYPE

ORGANIZATION

MATERIAL

PERSON

FACILITY

FEATURE

Reporting Data

Object-Item

Capability

Object-Type

Location

Action Reporting Data

Object-Item

CapabilityCapability

Object-TypeObject-Type

Location

Action

OBJECT-TYPE OBJECT-ITEM

ORGANIZATION -TYPE

MATERIAL-TYPE

PERSON -TYPE

FACILITY-TYPE

FEATURE-TYPE

ORGANIZATION

MATERIAL

PERSON

FACILITY

FEATURE

OBJECT-TYPE OBJECT-ITEM

ORGANIZATION -TYPE

MATERIAL-TYPE

PERSON -TYPE

FACILITY-TYPE

FEATURE-TYPE

ORGANIZATION

MATERIAL

PERSON

FACILITY

FEATURE

Reporting Data

Object-Item

Capability

Object-Type

Location

Action Reporting Data

Object-Item

CapabilityCapability

Object-TypeObject-Type

Location

Action

OBJECT-TYPE OBJECT-ITEM

ORGANIZATION -TYPE

MATERIAL-TYPE

PERSON -TYPE

FACILITY-TYPE

FEATURE-TYPE

ORGANIZATION

MATERIAL

PERSON

FACILITY

FEATURE

OBJECT-TYPE OBJECT-ITEM

ORGANIZATION -TYPE

MATERIAL-TYPE

PERSON -TYPE

FACILITY-TYPE

FEATURE-TYPE

ORGANIZATION

MATERIAL

PERSON

FACILITY

FEATURE

DOMAIN

DOMAIN

Reporting Data

Object-Item

Capability

Object-Type

Location

Action Reporting Data

Object-Item

CapabilityCapability

Object-TypeObject-Type

Location

Action

OBJECT-TYPE OBJECT-ITEM

ORGANIZATION -TYPE

MATERIAL-TYPE

PERSON -TYPE

FACILITY-TYPE

FEATURE-TYPE

ORGANIZATION

MATERIAL

PERSON

FACILITY

FEATURE

OBJECT-TYPE OBJECT-ITEM

ORGANIZATION -TYPE

MATERIAL-TYPE

PERSON -TYPE

FACILITY-TYPE

FEATURE-TYPE

ORGANIZATION

MATERIAL

PERSON

FACILITY

FEATURE

DOMAIN

DOMAIN

5 UNCLASSIFIED

• Aim: Achieve international interoperability of Command and Control Information Systems (C2IS) at all levels:

– Corps to battalion, or lowest appropriate level

– Support multinational, combined and joint operations

– Advance digitization in the international arena including NATO

• Scope:

– War Ops, Crisis Response Ops, Defence Against Terrorism

– Joint, Interagency, Multinational, Non-governmental Organizations

– Tactical to Operational and Strategic levels

A Standard with an Aim ...

WHY JC3IEDM?WHY JC3IEDM?

Has Utility for the Joint and Multinational Communities

6 UNCLASSIFIED

• Command and Control Information Exchange Data Model (C2IEDM): In service until 2009 • Joint Consultation, Command, and Control Information Exchange Data Model (JC3IEDM): In service o/a 2010; development and testing ongoing • US-JC3IEDM: A U.S. configuration controlled version with approved changes and extensions not incorporated into the NATO/MIP JC3IEDM

InformationExchange Data Model

C2IEDM

US-JC3IEDM

JC3IEDM

Extensions

InformationExchange Data Model

C2IEDM

US-JC3IEDM

JC3IEDM

Extensions

C2IEDM

US-JC3IEDM

JC3IEDM

Extensions

What is the C2IEDM, JC3IEDM, & US-JC3IEDM?

7 UNCLASSIFIED

• Maximum reuse providing cost avoidance

• Relatively simple, understandable structure with broad applicability

• Central concepts have been stable for 12 years

• Multinational pedigree

• General, based on military experience (Army Tactical Command and Control Information System - ATCCIS); Easy to extend in response to operational data requirements

• Joint interfaces (Air Tasking Order (ATO)(NATO) Chemical Biological Radiological Nuclear (CBRN)(NATO) Maritime Mine Warfare (MMW)(NATO))

ADVANTAGES OF JC3IEDM

8 UNCLASSIFIED

ARMY ENDORSEMENTS

• G-3/5/7, CIO/G-6, & TRADOC have endorsed C2IEDM (JC3IEDM) as the standard for information exchange in Battle Command systems.

– 28 Sep 05, Office of the Deputy Chief of Staff, G-3/5/7, DAMO-SBB memo, subject: Command and Control Information Exchange Data Model

– 19 Aug 05, Office of the Secretary of the Army, Chief Information Officer / G-6 memo, subject: CIO/G-6 Endorsement of the Command and Control Information Exchange Data Model

– 22 June 05, U.S. Army Combined Arms Center and Fort Leavenworth, ATSL-CG memo, subject: Combined Arms Center Endorsement of Command and Control Information Exchange Data Model

9 UNCLASSIFIED

Business Case for Transforming to a Better Data Interoperability Solution

System-1

System-2

System-3

System-4

System-5

System-6

System-7

System-8System-9

System-10

System-11

System-12

System-13

System-14

System-15

Joint Interface Spec

Joint Domain Interface Spec

Joint Domain Interface Spec

JC3IEDM

System-1

System-2

System-3

System-4

System-5

System-6

System-7

System-8System-9

Service `

Service 2

Strike

GFM

BFT

MIP/Multinational Community

Current

Target

1995 study by the Air Mobility Command revealed that it spent $335,000/interface/year

Army will conduct study to validate cost savings in Implementing JC3IEDM

10 UNCLASSIFIED

Multinational Users of the JC3IEDM

FULL MEMBERS

CA LFCS

DA DACCIS

FR SICF, SIR

GE HEROS-2/1

IT SIACCON

NL ISIS

NO NORTaC/NORCCIS

SP SIMACET

TU TKKBS

UK ATacCS/ComBAT

US MCS

ASSOCIATE MEMBERS

AS JCCS, BCSS

AU PHOENIX

BE SICBEL

CZ GF-TCCS

FI FINACCIS

GR HARCCIS

HU HAVIR

LH TAVVIS

PL SZAFRA

PO SICCE

RO SIAAB

SI TBD

SW ISMARK, SLB

AFNORTH

ACT BiSC AIS

• 11 Full members• 15 Associate members

In use by32 Systems

And Organizations

11 UNCLASSIFIED

US-JC3IEDM Users & Stakeholders(Partial List)

• CIO/G-6: JC3IEDM foundation for US Army Data Strategy

• G3/5/7, CIO/G6, TRADOC CAC Cdr: Has officially endorsed the JC3IEDM for Battle Command

• USMC endorsement as basis for core vocabulary

• ABCS

– Current US MIP implementation program is Maneuver Control System

– Implementation on-going in MCS 6.4 GE

– Planned software reuse - other ABCS programs

• Army Future Combat Systems (FCS)

– MIP being leveraged to satisfy coalition interoperability requirements

– JC3IEDM integral to FCS data strategy (with extensions)

• Shared Tactical Picture - Ground (STP-G)

– Germany (GE), Italy (IT), Sweden (SW), and the United Kingdom (UK)

• Blue Force Tracking (BFT) COI

• Global Force Management (GFM)

• CIDNE/Fusion Net converting to JC3IEDM

• Chemical, Biological, Radiological, Nuclear Community

• DISA XML Registry: MIP XML in Coalition Namespace

• DMSO: JC3IEDM adopted as basis for Modeling & Simulation Data Strategy

• Strike COI investigating translator based on new Strike Schema

• Simulation to C4I Interoperability OIPT (5 Work Plans totaling $1.388M)

Goal is to leverage JC3IEDM throughout the Army for information exchange

12 UNCLASSIFIED

JC3IEDM Way Ahead

• Endorse development of Joint C2 Common Vocabulary

• Continue work with USMC to include CM

• Participate in DoD Data Model Core Working Group (Jan 07)

• Participate in JFCOM Technical Working Group (2nd Qtr FY07)

• Present at NECC Systems Engineering Working Group (TBD)

13 UNCLASSIFIED

CIO/G6 CONFIGURATION MANAGEMENT(JC3IEDM/US-JC3IEDM)

• JC3IEDM (Multilateral Interoperability Programme)

– CIO/G-6 is Deputy Chairman for the MIP Data Modeling Working Group responsible

for JC3IEDM Configuration Management

• ERwin Model and Information Resource Dictionary

• Documentation (5 Working Papers)

• Adjudication of Change Proposals

• US-JC3IEDM (Army Configuration Control Board)

– CIO/G-6 is responsible for US-JC3IEDM Configuration Management at the Army

CCB and WMA IWG level

– Same JC3IEDM Responsibilities listed above

14 UNCLASSIFIED

PrepareCP

Analyze/CoordinateCP

Defer

Approve

AdjudicationMIP-Joint / US

Inform JC3IEDM

implementersDiscuss CP

Valid Capability

Requirement

UpdateCP Doc Reg

UpdateCP Doc Register

Implement Release

DistributeNew

Version

Prepare/Verify NewVersion

Document withinCP Doc Reg

UpdateCP Doc Reg

Reject

Yes

No

Yes

Withdraw

Hold

No

Yes

MIP or Joint CCB

Stakeholder US-JC3IEDM Army ERB CM Action COI or System

Return to Preparer

Yes

No

No

Implementation Impact Minor

Yes No

Track and Follow up

Document withinCP Doc Reg

Track and Implement on future Version

Approve

Withdraw

No

Yes

Submitter Action

Hold pendingFinal Disposition

US-JC3IEDM CM Process

15 UNCLASSIFIED

Voting Members and Voting Rules

• Voting members are:

• TRADOC/TSM• CIO-G6• ASAALT/PEO

• Voting Rules:

• Unanimous approval is the goal

• In the event of a majority vote (non-unanimous) the results are submitted to the Warfighter Mission Area leadership for information

16 UNCLASSIFIED

Configuration Management Items(1 of 2)

Configuration Management Item Status

US JC3IEDM-Main-Edition_3.1_2006-12-09.doc BaselineUS JC3IEDM-Annex A-Glossary-Edition_3.1_2005-12-09.doc SupportingUS JC3IEDM-Annex B-Entities-Edition_3.1_2005-12-09.pdf SupportingUS JC3IEDM-Annex C-Attributes-Edition_3.1_2005-12-09.pdf SupportingUS JC3IEDM-Annex D-Relationships-Edition_3.1_2005-12-09.doc SupportingUS JC3IEDM-Annex E-Domain values-Edition_3.1_2005-12-09.pdf SupportingUS JC3IEDM-Annex F-Other domains-Edition_3.1_2005-12-09.doc SupportingUS JC3IEDM-Annex G-Business Rules-Edition_3.1_2005-12-09doc BaselineUS JC3IEDM-Annex H-Class words-Edition_3.1_2005-12-09.doc SupportingUS JC3IEDM-Annex I-Idef1X-Edition_3.1_2005-12-09.doc  Baseline – derivedUS JC3IEDM-Annex J-References-Edition_3.1_2005-12-09.doc SupportingUS JC3IEDM-Annex K-Logical view-Edition_3.1_2005-12-09.doc SupportingUS JC3IEDM-Annex L-Physical view-Edition_3.1_2005-12-09.doc SupportingUS JC3IEDM-Annex M-Ent attr diff-Edition_3.1_2005-12-09.doc Baseline – derivedUS JC3IEDM-Annex N-Dom value diff-Edition_3.1_2005-12-09.doc Baseline – derived

CRITICAL ITEMS FOR DEVELOPER

17 UNCLASSIFIED

Configuration Management Item Status

US JC3IEDM-Annex O-XML-Edition_3.1_2005-12-09.doc SupportingUS JC3IEDM-Annex O-XML-Edition_3.1_2005-12-09.xsd Baseline –

derivedUS-JC3IEDM Annex O Appendix A - OV7 view XXX.xsd Baseline –

derivedXML Message Schemas Baseline –

derivedDDMS Profiles Baseline –

derivedUS JC3IEDM-Annex P-Process to build an ER view and XSD from an OV7.doc SupportingUS JC3IEDM-MIRD-Edition_3.1_2005-12-09.mdb BaselineUS JC3IEDM-MODEL-Edition_3.1_2005-12-09.ER1 BaselineUS JC3IEDM-GuideToCP-Edition_3.1_2005-12-09.doc SupportingUS JC3IEDM-Processing of Operational Requirements-Edition_3.1_2005-12-09.doc HistoryUS JC3IEDM-Processing of Operational Requirements-Edition_3.1_2005-12-09.ER1 HistoryUS JC3IEDM-Overview-Edition_3.1_2005-12-09.doc SupportingUS JC3IEDM-CPDatabase-Edition3.1_2005-12-09.mdb HistoryDASG Configuration Management Plan.doc SupportingDASG Change Proposal Register SupportingChange Proposals Supporting

Configuration Management Items(2 of 2)

CRITICAL ITEMS FOR DEVELOPER

18 UNCLASSIFIED

Configuration Management Team

• Mr. Michael Morris, CIO/G6

– Email: [email protected]

– Phone: (703) 602-7023

• Dr. Gene Simaitis, IDA

– Email: [email protected]

– Phone: (703) 845-6873

19 UNCLASSIFIED

DRAFT New SSA Process

Criteria:

• Evaluate for Joint and Coalition

• Verify DD Form 1494 and EMC

• Assess Doctrinal/TTP Impacts

• Against Enterprise Architecture Guidance

Milestone

Decision

A/B/C

SubmitsSubmits

Program Manager CIO/G6

MDASpectrum Supportability

Assessment

• Determine RF requirements to fulfill the mission

• Frequency, bandwidth, throughput, power, antenna gain, host platform, geographic AOR, etc.

• DD Form 1494s must be submitted and certified

• Electromagnetic compatibility (EMC) analysis performed

• Consider operational environment

Increased Rigor in assessing Spectrum Supportability Assessmentwill increase Efficient C4 support to the Warfighter

CIO/G6

Feeds Enterprise

Architecture

Knowledge Base

Area of Responsibility

Technical View -1

COCOM J6

Disapproval: PM resolves feedback

New!

Increase Rigor and Rolefor CIO/G6

Emitters

EvaluatesEvaluates

Results:

20 UNCLASSIFIED

What is the Army doing to enhance Joint and Coalition Interoperability from a Data Perspective?

• Seven Data Strategy Goals

• Data Strategy Goals enabled by forming Communities of Interest (COIs)

– COI is a collaborative group of users who must exchange information in pursuit of their shared goals, interests, missions, or business processes.

– 60 Registered COIs since FY 03

DoD Net-Centric Data Strategy

Impact to Joint/Coalition

DoD Core C2 Vocabulary• ASD NII evaluating Common Core C2 Vocabulary

• Strike COI (1 of 60) registered COIs is developing a common Strike Community Vocabulary

• Common Core Task Force will develop evaluation criteria and metrics

Army Implementation• Army will evaluate proposed Common Core C2 Vocabulary

– Impacts to Joint Consultation Command Control Information Exchange Data Model (JC3IEDM) for Battle Command

• Basis for information interoperability for Command and

Control as endorsed by US Army and USMC – Army Data Harmonization and Integration Working Group to evaluate across Army Enterprise

• Will work with DoD and Services to develop a Core C2 Vocabulary

• Adherence to Core C2 Vocabulary

• Information Exchange Standards and Specification

• Increased Interoperability

• Enterprise wide Data Sharing

• Implementation Flexibility

6

21 UNCLASSIFIED

Summary

• US-JC3IEDM CM part of the ACCB

• Spectrum Architecture potential link to ACCB

• Output of Data Strategy may be potential link to ACCB

22 UNCLASSIFIED

Backup

23 UNCLASSIFIED

If you DO NOT implement JC3IEDM:

BASIC CONCEPT FOR INFORMATION SHARING

For every System, Additional Layers are added with associated cost, complexity and potential

errors!

Systems N+1System A

Information Transfer

Current Multinational Environment/COI:

Multiple TranslatorsUS Commander

Multinational Commanders/COIs

24 UNCLASSIFIED

If you DO implement JC3IEDM:

BASIC CONCEPT FOR INFORMATION SHARING

Saves $, Maximizes Reuse, and Facilitates Interoperability

JC3IEDMUS-JC3IEDM

Information Transfer

Common Interface StandardNo Translators

US Commander

Multinational Commanders

25 UNCLASSIFIED

Multinational Users of the JC3IEDM

FULL MEMBERS

CA LFCS

DA DACCIS

FR SICF, SIR

GE HEROS-2/1

IT SIACCON

NL ISIS

NO NORTaC/NORCCIS

SP SIMACET

TU TKKBS

UK ATacCS/ComBAT

US MCS

ASSOCIATE MEMBERS

AS JCCS, BCSS

AU PHOENIX

BE SICBEL

CZ GF-TCCS

FI FINACCIS

GR HARCCIS

HU HAVIR

LH TAVVIS

PL SZAFRA

PO SICCE

RO SIAAB

SI TBD

SW ISMARK, SLB

AFNORTH

ACT BiSC AIS

• 11 Full members• 15 Associate members

In use by32 Systems

And Organizations

26 UNCLASSIFIED

CIO/G6 CONFIGURATION MANAGEMENT(JC3IEDM/US-JC3IEDM)

• JC3IEDM (Multilateral Interoperability Programme)

– CIO/G-6 is Deputy Chairman for the MIP Data Modeling Working Group responsible

for JC3IEDM Configuration Management

• ERwin Model and Information Resource Dictionary

• Documentation (5 Working Papers)

• Adjudication of Change Proposals

• US-JC3IEDM (Army Configuration Control Board)

– CIO/G-6 is responsible for US-JC3IEDM Configuration Management at the Army

CCB and WMA IWG level

– Same JC3IEDM Responsibilities listed above

27 UNCLASSIFIED

Time

Users

JC3IEDM Vision

Today

100% JC3IEDM Adoption

28 UNCLASSIFIED

WAY AHEAD

• Continue to support JC3IEDM in Multinational (e.g., ABCA, MIP, etc) forums

• Promote JC3IEDM in joint data forums (e.g., DISR, NECC IPT etc)

• Mandate in AEA All View 1/2 (AV1/2)

• Support FOC of Army Net-Centric Data Strategy CoE

• Finalize Army Net-Centric Data Strategy Road Map

• Support G3 lead Warfighter Mission Area IWG – implement JC3IEDM no later than SWB IV

• Identify common suite of data management tools to implement JC3IEDM

• Conduct study to validate cost avoidance due to JC3IEDM implementation

29 UNCLASSIFIED

JC3IEDM Vision

• Use JC3IEDM as a common framework for information sharing across the joint & multinational community

– Achieve international interoperability of Command and Control Information Systems (C2IS) at all levels

– Promote the use of the JC3IEDM by the joint community

– Continue to support as DISR mandated standard

• Adopt JC3IEDM throughout the Army NLT Software Block IV

30 UNCLASSIFIED

Data Strategy Management

31 UNCLASSIFIED

Net-Centric Data Strategy Way Ahead

• Publish Army Net-Centric Data Strategy Implementation and COI Governance Documents NLT 2nd Qtr FY 07

• Conduct Army Harmonization and Integration Working Group on 9 Jan 07

• Evaluate impact of JFCOM Net-Centric Data Strategy• Participate in Joint Meta Data Tagging Pathfinder

Way Ahead• Address Service Oriented Architecture Impact • Include Data Strategy Concepts within AEA

(AV1/AV2)

32 UNCLASSIFIED

Army Community of Interest Formation and Execution Process

Army Community of Interest Formation and Execution Process

CO

I Lea

dD

omai

n Le

adM

issi

on A

rea

YES

YESData Products must beConfiguration Managed

Contains:1. Scope2. Products3. Timeline4. Responsibilities5. Resource Requirements beyond what COIparticipants are able to contribute

Creation of IESS captured in the COI Vocabulary Guide andcontaining:1. Logical Data Model2. Data Dictionary3. Domain Values4. Authoritative Data Sources5. Taxonomy6. Technical Standards Implementation Listing7. COI Core Schema8. COI DDMS extensions9. Mappings with other COI IESS as necessary.

NO NO

YES

COI Registered to theDoD Metadata Registry

NO

This may be done viaPrototype Testing. If so, itneeds to be reflected in thePOAM

This is to confirm thatdeveloped products are notin conflict with existing COIIESS under Domain AOR

No

YES

ReviewCOI Charter,

Check against MAprioritized List ofRequired COIs,

check forUniqueness

against DoD List Register COI

COI Approved?

Create PlanOf Action

and Milestones

Plan of Actionand

Milestones(POAM)

DraftCOI

Charter

COICharterPropose COI

DataEngineering

Products

V&VData Engineering

Products

DevelopData Engineering

Products

Compare DataEngineering

Products againstexisting Domain

Products

Products notin Conflict

POAMApproved

PostApprovedProducts

DataEngineering

ProductsApproved

Productsavailable in theDoD MetaData

Repository

ReviewPOAM

Domain Leadprovides

Domain IntegrationGuidance

Domain IntegrationGuidance and

Domain RelatedCOI List

Process Stopped

YES

Domain LeadIntegrates COIVocabulary intoDomain-levelVocabulary

Domain leadDetermines if COIServices should becommon Domain

Services

YES

YES

Develop/UpdateDomain Guidance

and COI List

Domain Guidanceand COI List

No

Input may come from MA and/or Domainbased on identified capability requirements.Possible sources for determining need are:- Army Strategic Planning Guidance (APSG)- The Army Plan (TAP)- QDR and Post QDR Strategy Processes- CDDs- Functional Control Boards- Joint Capabilities Integration andDevelopment System (JCDS)

Collect andPrioritize MissionArea CapabilityRequirements

EstablishCapability

RequirementsRepository

Prioritized list ofRequired COIs

CapabilityRequirements

Repository

DevelopImplementation

Plan

ImplementationPlan

YES

Implementation Plan captures thesynchronization of the specificationsinto the COI systems and allows forsynchronization of POM requirementsfor implementation.

COIs may want to start ImplemenationPlan development shortly after the"Develop Data Engineering Products"stage to get a head start on thesynchtonizaton effort between all theCOI participating systems.

CIO-G6, Technical Architecture Division, POC: Mr. James Blalock, James. [email protected]

• Mission Areas manage priorities • Domains manage COIs• COIs execute data engineering activities

Details in Army Implementation

Guidance and COI Guidance Document

33 UNCLASSIFIED

Center of Excellence (CoE) Overview

Data (COI) Admin Data Engineering Data Validation Configuration Management (CM)• Coordinate & Facilitate COI

activities/product (charter, POAM, IESS)

•Liaison between DS Policy makers and Programs/Systems of Record

•COI Collaboration

•COI Administration Templates

• IER Analysis (OV-3)

• Generate IESS components to include Data Architecture products (AV-2, OV-7, SV-11)

• Mapping against JC3IEDM

• Develop COI/Enterprise Ontology

• Identify Authoritative Data Sources

• Identify Enterprise Identifiers (EIDs)

• Data Engineering Practices Guide

• Validate data products

• Assist in resolving data interoperability issues• Support test and evaluation activities across COIs• Audit system implementations of data products• Validation Practices Guide

• CM COI Products (IESS, Data Models, Ontology, …)

• Support MA CM

• Support CM infrastructure across enterprise

• CM Template Guide

•US-JC3IEDM CM

33