1 / 10

Interim Implementation Guidance for Net-Centric Data Strategy in the C2 Capability Portfolio

Interim Implementation Guidance for Net-Centric Data Strategy in the C2 Capability Portfolio. COL Carl Porter OASD NII/DoD CIO C2 Programs and Policy Directorate 8 April 2009. Purpose and Agenda. Provide context/summary and highlight key actions in DoD CIO interim guidance memorandum

knox
Download Presentation

Interim Implementation Guidance for Net-Centric Data Strategy in the C2 Capability Portfolio

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. Interim Implementation Guidance for Net-Centric Data Strategy in the C2 Capability Portfolio COL Carl Porter OASD NII/DoD CIO C2 Programs and Policy Directorate 8 April 2009

  2. Purpose and Agenda • Provide context/summary and highlight key actions in DoD CIO interim guidance memorandum • COI Responsibilities • Near-term way ahead • Bounding the way ahead The overarching implementation goal is to enable operators at all levels of command to publish, discover, use, and manipulate data dynamically. Achieving this goal will increase operational agility and allow technical innovation in support of military operations, including missions combining traditional and non-traditional partners. -- DoD CIO, 11 March 2009

  3. Interim Guidance Context • Interim Implementation Guidance Memo • Focused on NCDS implementation – not a separate data strategy • Address data needs necessary to support net-enabled C2 capabilities across the DoD C2 capability portfolio • Data for C2 comes from largely outside of the portfolio • Situational dependent to meet commander’s requirement • UCore basis for needed extensions is the way ahead for DoD • C2 Core creation is logical codification of common C2 extensions

  4. Interim Guidance Summary1 of 2 • Advocates the use of the Universal Core (UCore) version 2.0 • Directs development/configuration management of C2 Core • Directs development of a strategy for addressing legacy and coalition data models, vocabularies and info exchange specs • Emphasizes collaboration between Components, PEO/PM, COI and CPMs to achieve NCDS objectives • Establishes the Information Support Plan as the preferred method to assess NCDS implementation plans

  5. Interim Guidance Summary2 of 2 • Sets Objectives for C2 CPM/DoD Components • Identify data sharing requirements • Prioritize data sharing requirements • Synchronize data availability (exposure) • Synchronize data services • Define data utilization metrics; developing a plan to instrument operational/pilot/testing environments for their collection • Encourage PEO/PM and COI to use Core Enterprise Services (CES) to maximum extent possible

  6. Interim Guidance ActionsC2 CPM • Directs the C2 CPM • Develop a C2 Core consisting of 4 elements • C2 Extensions from Universal Core (UCore) - 30 Jun 09 • C2 data model and vocabulary - 30 Jun 09 • C2 Information Sharing Framework - ~Mar 10 • POA&M in progress • C2 Core Service specifications - ~Sep 09 • POA&M in progress • Develop and publish a Configuration Management (CM) Plan for the C2 Core elements - 1 May 09 • Develop strategy for addressing legacy and coalition data models in C2 Core - ~Mar 10 • Commence Information Support Plan (ISP) reviews - 1 Jul 09

  7. COI ResponsibilitiesHow you can engage • Assist the C2 CPM/C2 Community • Developing C2 Core and COI specific extensions consistent with Universal Core (UCore) • Publish those artifacts to appropriate registries/repositories • Defining data utilization metrics for the development, pilot and operational environments • Developing plans for the instrumentation (automated collection capability) necessary to gather the metrics • Document shortfalls in available/candidate CES to enable run-time implementation within all pilot programs

  8. 2QFY09 3QFY09 4QFY09 1QFY10 2QFY10 3QFY10 In Progress Proposed Start/Duration Expected Start/Duration Near-Term Way Ahead Today 12 mos Actions In Progress CM Process C2 Core Baseline ISP Reviews C2 Core WG C2 Core WG-TFTSWG Testing of Core Artifacts C2 CPM Lead: JFCOM Actions Over Next 12 Months • Use of Core Enterprise Services • C2 Core Service Specifications • C2 Core Legacy/Coalition Plan OASD NII/DoD CIO • Data Sharing Requirements • Identification & Prioritization • Synchronization of data exposure • Define Data Utilization Metrics • Development, pilot & operational environments • Instrumentation of the environments • C2 Information Sharing Framework (C2ISF) • Identify component elements & gaps C2 CPM Lead: JFCOM C2 CPM Lead: OASD NII/DoD CIO C2 CPM Lead: OASD NII/DoD CIO C2 CPM Lead: JFCOM

  9. Bounding the Way Ahead • No intent to establish a “monolithic” model for all exchanges • Focus on common elements, reusable components and standards • COI extensions to UCore/C2 Core remain essential elements • We won’t get it completely “right” the first time • Incremental improvements to update guidance and approach • Senior engagement to resolve the toughest issues • Sober assessments of the “value proposition” • Emerging thoughts on applicability • Evolutionary – not revolutionary • “Point of exposure” vice “machine to machine” vice “sensor to shooter” • Adoption by “non-C2” data sources

  10. Questions/Discussion NII C2 Programs and Policy Points of Contact COL Carl Porter, carl.porter@osd.mil, 703.607.0662 Mr. John Crooks, john.crooks.ctr@osd.mil, 703.607.0706 Mr. George McVeigh, george.mcveigh.ctr@osd.mil, 703.607.6012

More Related