1 / 18

ARMY Data Strategy Status Update Manickam Neelakandan 19 APRIL 2006

ARMY Data Strategy Status Update Manickam Neelakandan 19 APRIL 2006. 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 Goals:. Consumer. Producer.

helga
Download Presentation

ARMY Data Strategy Status Update Manickam Neelakandan 19 APRIL 2006

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

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

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

  3. DoD Net-Centric Data Goals: Consumer Producer Searches 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 metadatain catalogs and data in shared space Security Services (e.g., PKI, SAML) • Ensure data is: • Visible • Available • Understandable • Trusted • Interoperable • Responsive to users’ needs • Institutionalize Data Management Ubiquitous Global Network Metadata Catalogs Shared DataSpace Enterprise & Community Web Sites Application Services (e.g., Web) Metadata Registries COI / Developer Posts to and uses metadata registries to structure data and document formats for reuse and interoperability DoD Net-Centric Data Strategy Strategy enabled by data forums (COIs, WGs, IPTs) , metadata, registries, catalogs and shared data spaces

  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

  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

  6. COI COI CoE COI COI Army Data StrategyCenter of Excellence (CoE) One-Stop Shop for COI Product Development and Service Support 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 Software Engineering Center Performed by: 6 Fort Monmouth, NJ

  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

  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.

  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

  10. Proposed US-JC3IEDM CM Roadmap 2006 20XX US-JC3IEDM Development Schedule (Incorporating Extension) WMA IWG FCS BCT PEO C3T GFM COI CBRN COI Other COIs Army PMs COIs Joint PMs Who Executes CM G-6 WMA IWG DASG DISA Phase I Phase II Phase III

  11. Short-Term (Phases I & II)US-JC3IEDM CM Approaches Support Authority CM Admin Staff CM Engineers CM Manager CCB BC CCB*+/ Army CCB* DMWG WMA IWG DMWG CIE Army CCB* G6/SEC G-6 (TAD) G6 SEC * Include MIP Rep + To be established NATO/MIP

  12. Long-Term (Phase III)US-JC3IEDM CM Approaches CM Admin Staff CM Engineers CM Manager CCB DISA Support DISA Support DISA Joint CCB NATO/MIP Service CCBs

  13. US-JC3IEDM Way Ahead • Add US-JC3IEDM to Army CCB Charter/TOR • Add Attendee(s) to support US-JC3IEDM incorporation • Currently, C-E LCMC would like to nominate Mike Morris, CIO/G-6 • Add US-JC3IEDM to: • Phase I: WMA IWG DASG role/responsibility • Phase II: G6 role/responsibility • Phase III: DISA role/responsibility

  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.

  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 Responsibilities: drafting, approving, and implementing procedures necessary to efficiently carry out its functions. Army CCB Membership: may be modified with a two-thirds vote of the entire Army CCB membership.

  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”

  17. Backups

  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

More Related