1 / 15

Anti-Submarine Warfare Community Of Interest (ASW COI)

Anti-Submarine Warfare Community Of Interest (ASW COI). Presented by Colleen Cannon (PEO IWS5SE) to the DoD COI Forum 16 October 2007. OUTLINE. Overview of ASW COI Organizational Structure Relationship to DoD and Coalition COIs Areas of Interest in FY08

lucillew
Download Presentation

Anti-Submarine Warfare Community Of Interest (ASW COI)

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. Anti-Submarine Warfare Community Of Interest(ASW COI) Presented by Colleen Cannon (PEO IWS5SE) to the DoD COI Forum 16 October 2007

  2. OUTLINE • Overview of ASW COI Organizational Structure Relationship to DoD and Coalition COIs Areas of Interest in FY08 • ASW Data Strategy Why, Who, What, Where (data environment) • ASW Command and Control (C2) Pilot Implementation Focus Areas Alignment Through Mediation • Future Data Management Working Group EffortsNext Steps Broad “To Do” List • Questions?

  3. Overview of ASW COIOrganizational Structure ASW COI Flag Oversight ASW CFB Chair-Lead NMAWC Advisory (Requirements) ASW Executive Steering Group (ESG) IWS5 Chair ASW Systems Engineering Team (ASSET) IWS5SE Chair System of Systems (SoS) Engineering ASW OA Pilot & Software Governance DMWG Data Sharing Demos ASW Mission Capability Architectures (MCA) ASW SoS Level Risk Management PSDB C2 Data Fusion LCS SoS pilot

  4. Overview of ASW COIRelationship to DoD and Coalition COIs Joint Command and Control (JC2 CPM) Consolidated Net-Centric Data Environment (CNDE) Infrastructure DoD Universal Core & NCES Maritime Domain Awareness (MDA) COI (AIS) Meteorology Oceanography (METOC) COI Anti-Submarine Warfare COI Multilateral Interoperability Programme (MIP) COI (JC3IEDM) Coalition Mine Warfare COI Alignment required with related COIs and Enterprise Services

  5. Overview of ASW COIAreas of Interest in FY08 Navy Enterprise Architecture and Data Strategy Open Architecture – Data Strategy – Enterprise Architecture – Service Oriented Architecture Metrics System of Systems Engineering Mission CapabilityArchitecture Data Strategy Risk Management OpenArchitecture • Common Data Vocabulary and • Pilot Demonstration Working Groups • Command and Control • Sensors • Sensor Performance Prediction • Implementation Driven • Software Reuse • Software Governance • LCS ASW Pilot CEP • DNS Follow-On

  6. Why Develop An ASW Data Strategy? Because it is DoD and Navy policy… • DoD Memo Net-Centric Data Strategy, 9 May 2003 • DoDD 8320.2 Data Sharing in a Net-Centric Department of Defense, 2 Dec 2004 • Navy Enterprise Architecture and Data Strategy Policy, 6 Apr 2007 Because it is at the heart of ASW interoperability… • Need it to effectively share data among network users • Net-centric systems require precise, and known data formats and vocabularies to accurately evaluate and manipulate information without human intervention • We have numerous ASW systems that can’t share similar data Because we have the opportunity… . . . to define and implement it as the design of choice in new developments . . . to simplify integration as we bring on new sensors Making ASW data visible, accessible, understandable and trusted, managed by ASW COI

  7. Who Will Develop The ASW Data Strategy? • The ASW Data Management Working Group (DMWG) has been established under ASSET to do this • Consistent with DoD terminology and intent • Initial meeting held 23-24 July – second meeting held 23 August • Over 30 participants from inside and outside the ASW community (POC list is 70+) • Core • ASW PEOs & Labs, NMAWC, CFT, USW-DSS, usw-xml WG, ONI, Industry • Identified related COIs and stakeholders • Mine Warfare, METOC and Maritime Domain Awareness (MDA) COIs, Consolidated Navy Data Enterprise (CNDE), NETWARCOM, Joint C2 Capability Portfolio Manager, Multilateral Interoperability Programme (MIP) • Pilot demonstration groups established for Command and Control, Sensors and Sensor Performance Prediction • Way Ahead plan developed for each group • Pilot demonstration efforts proposed by each group Next meeting 30-31 October @ BAE Systems 80 M St.

  8. Data Management Working GroupWhat we are doing to realize the ASW Data Strategy Other ASW Interfaces C2 Exposure Sensors

  9. Related Associated Medical Weather USW Logistics MDA Universal Core Legal Business Sensors Imagery Elements Elements Data Strategy Consolidated Net-Centric Data Environment (CNDE) Enterprise Data Management Universal Core - New data models can be extended from the core model with minimal effort and impact Data models are dynamic…they can be added and removed as needed Domain data model are “decoupled components” and do not impact each other Communities retain control of their own data and it’s access

  10. ASW COI C2 Pilot Implementation(Proposed) ASW COI Proposed C2 Pilot – Focus Areas Related • Universal Core • Common Core Implementations (JTM Based) • Data Requirements Based On USW DSS Use Cases • ASW COI Extensions (JTM and JC3 Based) • SOA Implementation • Security/Registration/Discovery • Data Archive/Replication/Synchronization Associated USW Universal Core Elements Elements Goal: Define, implement and test Universal/Common Core and ASW COI Increment; Mediate effort with USW DSS Program of Record

  11. C2 Pilot -Alignment Through Mediation Mission Plan Data Mission Execution Metrics Where We Are Composite Subsurface Track Security Registration / Discovery CANES NODES Orchestration Universal Core , Common Core , ASW COI USW DSS Capabilities Data Mediation External USW DSS NODES USW DSS Common Tactical Picture OTH - G Q 89 Based Mission Plan (OP Areas, WSM, Ovly, etc.) Mission Execution Metrics Sensor Systems Composite Subsurface Track GIS Features and Overlay Surface Radar METOC Local AIS Link - 11 National Sensors ( JMIE / ELINT / SIGINT # 1 )

  12. C2 Pilot - Alignment Through Mediation Where We Are Going Local AIS National Sensors ( JMIE / ELINT / SIGINT # 1 ) Surface Radar ASW COI Link - 11 Replication/Synchronization METOC Security Registration / Discovery CANES NODES Orchestration Universal Core , Common Core , ASW COI Q89 Sensor Mission Plan Mission Execution Metrics USW DSS Composite Subsurface Track GIS Features and Overlay Capabilities Data Mediation DSS NODES USW DSS Data Workspace Capability Collaboration Q GIS Features 89 Based Sensor Systems Mission Plans Mission Execution

  13. Data Management Working GroupNext Steps • Establish common ASW vocabulary and data format, using Mission Capability Architecture to analyze and develop the data and metadata models • ASW C2 • Reconcile existing ASW C2 data formats • Repeat process with other C2 communities • ASW Sensors • Identify sonobuoy data producers, users, formats and associated metadata • Reconcile format differences • ASW Sensor Performance Prediction (SPP) • Re-establish the Platform Sensor Database (PSDB)

  14. Data Management Working GroupBroad “To Do” List • Align with the Joint C2 Capability Portfolio Management process – JFCOM • Identify requirements for new data capabilities • Execute pilots for Sensor Data, Sensor Performance Prediction, and C2 • Participate in the DoD COI Forum • Best Practices and Lessons Learned from other COIs

  15. Questions?Colleen CannonIWS-5SEcolleen.cannon@navy.mil202-781-4462

More Related