anti-submarine warfare community of interest (asw coi) presented by colleen cannon (peo iws5se) to...
TRANSCRIPT
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
• ASW Data StrategyWhy, Who, What, Where (data environment)
• ASW Command and Control (C2) Pilot ImplementationFocus AreasAlignment Through Mediation
• Future Data Management Working Group EffortsNext StepsBroad “To Do” List
• Questions?
ASW COI Flag OversightASW CFB Chair-Lead
ASW Executive SteeringGroup (ESG)IWS5 Chair
ASW Systems Engineering Team (ASSET)IWS5SE Chair
NMAWC Advisory(Requirements)
System of Systems (SoS) Engineering
LCS SoS pilot
ASW SoS LevelRisk Management
ASW OA Pilot &Software Governance
ASW Mission Capability
Architectures (MCA)
PSDB
DMWG Data SharingDemos
C2 DataFusion
Overview of ASW COIOrganizational Structure
Alignment required with related COIs and Enterprise Services
Maritime Domain Awareness (MDA) COI (AIS)
Mine Warfare COI
MeteorologyOceanography(METOC) COI
MultilateralInteroperability
Programme (MIP) COI(JC3IEDM) Coalition
Joint Command and Control(JC2 CPM)
ConsolidatedNet-Centric Data
Environment (CNDE)Infrastructure
Anti-Submarine Warfare COI
DoD Universal Core & NCES
Overview of ASW COIRelationship to DoD and Coalition COIs
Overview of ASW COIAreas of Interest in FY08
Navy Enterprise Architecture and Data StrategyOpen Architecture – Data Strategy – Enterprise Architecture – Service Oriented Architecture
System of Systems Engineering
MissionCapability
Architecture
Data Strategy RiskManagement
OpenArchitecture
Common Data Vocabulary andPilot Demonstration Working Groups• Command and Control• Sensors• Sensor Performance Prediction• Implementation Driven
Metrics
• Software Reuse• Software Governance
• LCS ASW Pilot CEP• DNS Follow-On
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
Why Develop An ASW Data Strategy?
Next meeting 30-31 October @ BAE Systems 80 M St.
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
Data Management Working GroupWhat we are doing to realize the ASW Data Strategy
ASW COI
DMWG TeamsOperational Data Model Analysis
USW DSS
ATAS - TAML
ImplementationRequirements
Operational Concepts
Schedule
Sensor Systems
Interface Requirements
Operational Concepts
Data ModelData
Management
USW DSS POR
CANES – CNDE POR
OA-Fn Experiment Series
Fleet Experimentation
CNDE
METOC COI
MDA COI
Universal Core/NECS
DataModel
Data Management
POR Context Based Inventory of ASW COI data Assets
Define ASW COI Increment Context
Establish ASW core data baseline
Establish ASW core data management ruleset baseline
Implement Baseline in PORs
Implementation Baseline definitions and associated requirements
DoD Discovery Metadata Specification DDMS
DoD Metadata Registry
ASW COI CM Repository
Coordination with Related COIs
and Enterprise
Services
1
2
3
5
6
4
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
UniversalCore
Related
Elements
Associated
Elements
Logistics
Logistics
LegalLegal
Sensors
Sensors
Business
Business
Med
ical
Med
ical
Imag
ery
Imag
ery
Weather
Weather
USWUSW
MDAMDA
Data Strategy
Enterprise Data Management
Consolidated Net-Centric Data Environment (CNDE)
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/DiscoveryData Archive/Replication/Synchronization
UniversalCore
Related
Elements
Associated
Elements
USWUSW
ASW COI C2 Pilot Implementation(Proposed)
Goal: Define, implement and test Universal/Common Core and ASW COI Increment; Mediate effort with USW DSS Program of Record
ASW COI Proposed C2 Pilot – Focus Areas
C2 Pilot -Alignment Through Mediation
Where We Are
Universal Core, Common Core, ASW COI
USW DSS Capabilities
Data Mediation
SecurityRegistration/DiscoveryOrchestration
CANES NODES
National Sensors(JMIE/ELINT /SIGINT #1)
Local AIS
Surface Radar
OTH - G (OP Areas, WSM, Ovly, etc.)
METOC
Mission PlanMission Execution MetricsComposite Subsurface TrackGIS Features and Overlay
Link-11
Mission Plan DataMission Execution MetricsComposite Subsurface Track
USW DSSCommon Tactical Picture
Q89 Based Sensor Systems
External USW DSS NODES
C2 Pilot - Alignment Through Mediation
Where We Are Going
, ,
USW DSS Capabilities
/CANESNODES
National Sensors(JMIE/ELINT /SIGINT #1)
Local AIS
Surface Radar
METOC
Q89 SensorMission Plan
Mission Execution MetricsComposite Subsurface Track
GIS Features and Overlay
Link-11 ASW COI
Replication/Synchronization
Q
DSS NODES
Data Mediation
89 Based Sensor Systems
MissionPlans Mission
Execution
GISFeatures
USW DSSData Workspace
CapabilityCollaboration
Universal CoreCommon CoreASW COI
SecurityRegistrationDiscoveryOrchestration
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)
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
