army data strategy status update

18
1 ARMY Data Strategy Status Update Manickam Neelakandan 19 APRIL 2006 ARMY Data Strategy Status Update Manickam Neelakandan 19 APRIL 2006

Upload: datacenters

Post on 17-Jul-2015

837 views

Category:

Technology


3 download

TRANSCRIPT

Page 1: ARMY Data Strategy Status Update

1

ARMY Data StrategyStatus Update

Manickam Neelakandan

19 APRIL 2006

ARMY Data StrategyStatus Update

Manickam Neelakandan

19 APRIL 2006

Page 2: ARMY Data Strategy Status Update

2

Agenda

• DoD Net-Centric Data Strategy• Data Strategy Update• SEC Data Strategy Center of Excellence• Add US-JC3IEDM to Army CCB

• DoD Net-Centric Data Strategy• Data Strategy Update• SEC Data Strategy Center of Excellence• Add US-JC3IEDM to Army CCB

Page 3: ARMY Data Strategy Status Update

3

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

Page 4: ARMY Data Strategy Status Update

4

Data Strategy Update

• Army Net-Centric Data Strategy Roadmap in development• COI Guidance Document in Review• US-JC3IEDM Endorsements• WMA IWG to become a COI

– Developing Charter– Developing a CM Plan

• WMA IWG DASG and the SWB Data Sub-IPT to merge

• Army Net-Centric Data Strategy Roadmap in development• COI Guidance Document in Review• US-JC3IEDM Endorsements• WMA IWG to become a COI

– Developing Charter– Developing a CM Plan

• WMA IWG DASG and the SWB Data Sub-IPT to merge

Page 5: ARMY Data Strategy Status Update

5

DATA STRATEGY CENTER OF EXCELLENCE

PURPOSE

• Enable the understandability of data• Assist with the establishment of COIs and develop their data

products • Use common/enterprise tools/products to efficiently produce

tailored data products

PURPOSE

• Enable the understandability of data• Assist with the establishment of COIs and develop their data

products • Use common/enterprise tools/products to efficiently produce

tailored data products

Page 6: ARMY Data Strategy Status Update

6

Army Data StrategyCenter of Exce l l ence (CoE)

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

meetings and product development schedules

• Perform administrative activities

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

•COI Collaboration

•COI Administration Templates

• IER Analysis (OV-3)

• Data Architecture products (AV-2, OV-7, SV-11)

• Develop COI/Enterprise Ontology

• List 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

6 Software Engineering Center

Perf orme d b

y :

Fort Monmouth, NJ

Reporting Data

Object-Item

Capabil ity

Ob ject-Type

Location

Actio n Reporting Data

Object-Item

Capabil ityCapabil ity

Ob ject-TypeOb ject-Type

Location

Actio n

O BJECT-TYPE OBJECT-IT EM

ORGANIZAT ION -T YPE

M ATERI AL-TYPE

PERSON -TYPE

FACILIT Y-TYPE

FEATURE-T YPE

ORG ANIZAT ION

MAT ERIAL

PERSON

FACILITY

F EAT URE

O BJECT-TYPE OBJECT-IT EM

ORGANIZAT ION -T YPE

M ATERI AL-TYPE

PERSON -TYPE

FACILIT Y-TYPE

FEATURE-T YPE

ORG ANIZAT ION

MAT ERIAL

PERSON

FACILITY

F EAT URE

Reporting Data

Object-Item

Capabil ity

Ob ject-Type

Location

Actio n Reporting Data

Object-Item

Capabil ityCapabil ity

Ob ject-TypeOb ject-Type

Location

Actio n

O BJECT-TYPE OBJECT-IT EM

ORGANIZAT ION -T YPE

M ATERI AL-TYPE

PERSON -TYPE

FACILIT Y-TYPE

FEATURE-T YPE

ORG ANIZAT ION

MAT ERIAL

PERSON

FACILITY

F EAT URE

O BJECT-TYPE OBJECT-IT EM

ORGANIZAT ION -T YPE

M ATERI AL-TYPE

PERSON -TYPE

FACILIT Y-TYPE

FEATURE-T YPE

ORG ANIZAT ION

MAT ERIAL

PERSON

FACILITY

F EAT URE

Reporting Data

Object-Item

Capabilit y

Ob ject -Type

Location

Action Reporting Data

Object-Item

Capabilit yCapabilit y

Ob ject -TypeOb ject -Type

Location

Action

O BJECT-T YPE OBJECT-ITEM

O RGANIZATION -TYPE

MATERIAL-TYPE

PERSON -TYPE

FACILITY -T YPE

FEATURE-TYPE

O RGANIZAT ION

M ATERIAL

PERSON

F ACILITY

F EATURE

O BJECT-T YPE OBJECT-ITEM

O RGANIZATION -TYPE

MATERIAL-TYPE

PERSON -TYPE

FACILITY -T YPE

FEATURE-TYPE

O RGANIZAT ION

M ATERIAL

PERSON

F ACILITY

F EATURE

Reporting Data

Object-It em

Capability

Object-Type

Location

Act ion Reporting Data

Object-It em

CapabilityCapability

Object-TypeObject-Type

Location

Act ion

OBJECT-TYPE OBJECT-ITEM

ORGANIZATION -TYPE

MATERIAL-TYPE

P ERSO N -TYPE

FACILITY-TYPE

FEATURE-TYPE

ORGANIZA TION

MATERI AL

PERSON

FACILITY

FEATURE

OBJECT-TYPE OBJECT-ITEM

ORGANIZATION -TYPE

MATERIAL-TYPE

P ERSO N -TYPE

FACILITY-TYPE

FEATURE-TYPE

ORGANIZA TION

MATERI AL

PERSON

FACILITY

FEATURE

COI COI

Report ing Data

Object-Item

Capabilit y

Ob ject-Type

Location

Act ion Report ing Data

Object-Item

Capabilit yCapabilit y

Ob ject-TypeOb ject-Type

Location

Act ion

OBJECT-TYPE OBJECT-ITEM

O RGANIZATIO N -T YPE

MATERIAL-TYPE

PERSON -TYPE

FACIL ITY-TYPE

F EAT URE-TYPE

ORGANIZ ATION

M ATERIAL

PERSON

FACILITY

FEATURE

OBJECT-TYPE OBJECT-ITEM

O RGANIZATIO N -T YPE

MATERIAL-TYPE

PERSON -TYPE

FACIL ITY-TYPE

F EAT URE-TYPE

ORGANIZ ATION

M ATERIAL

PERSON

FACILITY

FEATURE

COI

COI

CoECoE

Page 7: ARMY Data Strategy Status Update

7

US-JC3IEDM

• Need to incorporate the CM of the US-JC3IEDM into the Army CCB• Charter & TOR Review• Add Attendees to support technical understanding of the JC3IEDM

• Need to incorporate the CM of the US-JC3IEDM into the Army CCB• Charter & TOR Review• Add Attendees to support technical understanding of the JC3IEDM

Page 8: ARMY Data Strategy Status Update

8

Add US-JC3IEDM to Army CCB

• 1. PROBLEM/ISSUE: Request addition of the US-JC3IEDM CM into the Army CCB.• 2. BACKGROUND: The Army has endorsed the use of the

JC3IEDM for Battle Command systems. To ensure continued interoperability as the extensions are developed for this model, the Army requires centralized oversight of the extensions to enable US harmonization in its development.

• 3. IMPACT:– a. TECHNICAL: System Non-interoperability– b. SCHEDULE: See US-JC3IEDM Development Schedule– c. COST: The cost of re-engineering the systems’

implementation of the model will be great if harmonization is not embedded in the extension process. Also, coalition non-interoperability will cost lives on the battlefield.

• 1. PROBLEM/ISSUE: Request addition of the US-JC3IEDM CM into the Army CCB.• 2. BACKGROUND: The Army has endorsed the use of the

JC3IEDM for Battle Command systems. To ensure continued interoperability as the extensions are developed for this model, the Army requires centralized oversight of the extensions to enable US harmonization in its development.

• 3. IMPACT:– a. TECHNICAL: System Non-interoperability– b. SCHEDULE: See US-JC3IEDM Development Schedule– c. COST: The cost of re-engineering the systems’

implementation of the model will be great if harmonization is not embedded in the extension process. Also, coalition non-interoperability will cost lives on the battlefield.

Page 9: ARMY Data Strategy Status Update

9

Add US-JC3IEDM to Army CCB

• 3. IMPACT (Continued)– d. EFFECT ON INTERFACING SYSTEMS: The US-JC3IEDM

Implementation Plan, currently being developed, will address systems and their migration to using the US-JC3IEDM as a baseline standard.

• 4. SUPPORTING INFORMATION/MATERIAL: – WMA IWG DASG Briefings– JC3IEDM Endorsement Memos– MIP Website: www.mip-site.org

• 3. IMPACT (Continued)– d. EFFECT ON INTERFACING SYSTEMS: The US-JC3IEDM

Implementation Plan, currently being developed, will address systems and their migration to using the US-JC3IEDM as a baseline standard.

• 4. SUPPORTING INFORMATION/MATERIAL: – WMA IWG DASG Briefings– JC3IEDM Endorsement Memos– MIP Website: www.mip-site.org

Page 10: ARMY Data Strategy Status Update

10

Proposed US-JC3IEDM CM Roadmap

US-JC3IEDM Development Schedule(Incorporating Extension)

US-JC3IEDM Development Schedule(Incorporating Extension)

2006 20XX

WMA IWGFCS BCTPEO C3T

WMA IWGFCS BCTPEO C3T

Who Executes CMWho Executes CM

GFM COICBRN COIOther COIs

GFM COICBRN COIOther COIs

Army PMsArmy PMs COIsCOIs Joint PMsJoint PMs

DISAG-6WMA IWG DASG

Phase I Phase II Phase III

Page 11: ARMY Data Strategy Status Update

11

Short-Term (Phases I & II)US-JC3IEDM CM Approaches

WMA IWG

G-6 (TAD)

CM Admin Staff CM Engineers CM Manager CCB

DMWG

G6 SEC

DMWG CIE

G6/SEC Army CCB*

BC CCB*+/Army CCB*

NATO/MIP

* Include MIP Rep+ To be established

SupportAuthority

Page 12: ARMY Data Strategy Status Update

12

Long-Term (Phase III)US-JC3IEDM CM Approaches

DISADISA Support

CM Admin Staff CM Engineers CM Manager CCB

Joint CCBDISA Support

NATO/MIP Service CCBs

Page 13: ARMY Data Strategy Status Update

13

US-JC3IEDM Way Ahead

1. Add US-JC3IEDM to Army CCB Charter/TOR

2. Add Attendee(s) to support US-JC3IEDM incorporation– Currently, C-E LCMC would like to nominate Mike Morris,

CIO/G-6

3. Add US-JC3IEDM to:– Phase I: WMA IWG DASG role/responsibility– Phase II: G6 role/responsibility– Phase III: DISA role/responsibility

1. Add US-JC3IEDM to Army CCB Charter/TOR

2. Add Attendee(s) to support US-JC3IEDM incorporation– Currently, C-E LCMC would like to nominate Mike Morris,

CIO/G-6

3. Add US-JC3IEDM to:– Phase I: WMA IWG DASG role/responsibility– Phase II: G6 role/responsibility– Phase III: DISA role/responsibility

Page 14: ARMY Data Strategy Status Update

14

Conclusion

• Support of DOD Net-Centric Data Strategy is key to increased survivability of the Warfighter

• The Army CCB’s inclusion of emerging data standards supports the Army's migration to a Net Centric environment

• SEC provides expertise as the Data Strategy Center of Excellence in support of COIs, Domains and Mission Areas.

• Recommend the Army CCB consider increasing its role to support the DoD’s Data Strategy by becoming the CCB for the US-JC3IEDM.

• Support of DOD Net-Centric Data Strategy is key to increased survivability of the Warfighter

• The Army CCB’s inclusion of emerging data standards supports the Army's migration to a Net Centric environment

• SEC provides expertise as the Data Strategy Center of Excellence in support of COIs, Domains and Mission Areas.

• Recommend the Army CCB consider increasing its role to support the DoD’s Data Strategy by becoming the CCB for the US-JC3IEDM.

Page 15: ARMY Data Strategy Status Update

15

Army CCB Charter Discussion

Objective: To develop and provide a coordinated Army position on joint/combined message standards and procedural interface documents for US Message Text Format, Tactical Digital Information Links, and Variable Message Formats and on other joint/combined C3I interoperability issues.

Army CCB Membership: may be modified with a two-thirds vote of the entire Army CCB membership.

Army CCB Responsibilities: drafting, approving, and implementing procedures necessary to efficiently carry out its functions.

Page 16: ARMY Data Strategy Status Update

16

TOR Discussion

• “This document constitutes the Terms of Reference (TOR) to be applied for organizing, convening, and operating the Army Configuration Control Board (CCB) for supporting the configuration management (CM) of procedural interoperability standards and other procedural documentation regarding joint/combined command, control, communications, computers, and intelligence (C4I) systems.”

• “…processing CM transactions regarding joint/combined interoperability standards”

• “This document constitutes the Terms of Reference (TOR) to be applied for organizing, convening, and operating the Army Configuration Control Board (CCB) for supporting the configuration management (CM) of procedural interoperability standards and other procedural documentation regarding joint/combined command, control, communications, computers, and intelligence (C4I) systems.”

• “…processing CM transactions regarding joint/combined interoperability standards”

Page 17: ARMY Data Strategy Status Update

17

Backups

Page 18: ARMY Data Strategy Status Update

18

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

• 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