Chain of Command. Chief of Naval Operations. Commander, U.S. Fleet Forces Command. COMNAVMETOCCOM (CNMOC) Stennis Space Center, MS

Transcription

1 1

2 Chain of Command Chief of Naval Operations Commander, U.S. Fleet Forces Command Fleet Numerical Meteorology And Oceanography Center (FNMOC) Monterey, CA Naval Oceanographic Office (NAVOCEANO) Stennis Space Center, MS COMNAVMETOCCOM (CNMOC) Stennis Space Center, MS Naval Oceanography Operations Command (NOOC) Stennis Space Center, MS U.S. Naval Observatory (NAVOBSY) Washington, DC Naval Meteorology and Oceanography Professional Development Center (NMOPDC) Gulfport, MS 2

3 3

4 Mission To provide an asymmetric war fighting advantage through the application of Oceanographic sciences. Enabling Asymmetric Advantage A Navy strength the ability to apply Oceanography to battle problems and challenges in order to leverage knowledge of the environment for an advantage Navy METOC an information supply chain The information supply chain is our enterprise. 4

5 Tier 3 the Decision Layer Options / Courses of Action Sensor Employment Asset Allocation / Timing Quantify Risk Tier 2 the Sensor Performance Layer Sensor Decision Tier 1 the observed and forecast Environment Layer Environment Data Fleet Data We must make better decisions faster than the adversary Initial and Boundary Conditions 5

6 Net-Centric Operations & Warfare = Process Transformation New collaboration, decision, information sharing processes SOA = IT Transformation New architectural layer New acquisition, development & integration processes New technologies & skills 6

7 Service encapsulation Service loose coupling Service contract Service abstraction Service reusability Service composability Service autonomy Service optimization Service discoverability Ref: 7

8 Civilian Production Partners and Consumers Joint/Coalition Production Partners and Consumers External Integration NAVO FNMOC Major Integration Points (external or internal): METOC Sensor Node Internal Integration Navy METOC Domain METOC On DoD Node Those data, logic, control, process capabilities that if exposed: would be useful to multiple users, at multiple locations, and/or in multiple contexts would support the composition of new capabilities across systems with heterogeneous implementation technologies would mitigate high changeability expectations between integration participants 8

9 Ref: 9

10 A Node is a collection of Components (i.e., systems, applications, services and other Nodes) A Node results from the alignment of organizations, technologies, process, or functions Example alignments METOC Production Center METOC Sensor Node Mission Impacts Node Mission Planning Node Core Enterprise Services Node etc A Node is actively managed and enables a common strategy for sharing the task of realizing net-centricity and interoperability A Node may span multiple physical locations; or there may be multiple nodes at a single physical location 10

11 METOC Sensor Node (Tier 1) Mission Planning Node METOC Production Center Node (Tier 1) P2P management of interactions: - Formats - Security - Transport - Use Policy - Interface Management & Monitoring C2 Node Mission Impacts Node (Tier 2/3) Weapon Node 11

12 METOC Sensor Node (Tier 1) Information User Node (IUN) Mission Planning Node Information User Node (IUN) METOC Production Center Node (Tier 1) Information User Node (IUN) Facilitated management of interactions: - via Published Interface Contracts - Formats Mediation CES - Security Mediation Node - Transport Mediation - Use Policy Management - Interface Management & Monitoring Net-Centric Information Domain Node (NCID) C2 Node Information User Node (IUN) Mission Impacts Node (Tier 2/3) Information User Node (IUN) Mission Planning Node Information User Node (IUN) 12

13 C o n c e r t e d D e s i g n E f f o r t s

14 1. It is relatively easy to develop and deploy a web service built around XML data representations 2. It is harder to build a web service that is discoverable, reusable, scalable, extensible for broader contexts 3. It is a significant technical and management challenge to develop and deploy a portfolio of reusable services; and to build capability from others portfolios of services this is the essence of a Service Oriented Enterprise and underpins the concept of the GIG/Fn 14

15 Pick the right pathfinder projects Incrementally develop and apply skills Manage Cost, Complexity & Risk (CCR) Ensure visible warfighter value Ensure ready services consumer Prepare for the enterprise solution Modeling the METOC Enterprise Service Integration Layer (MESIL) Concurrent development of enabling enterprise standards Service taxonomy, service naming/description, SLA elements, etc. Clarifying METOC ESB Strategy Find efficiencies Outsource to GIG/Fn infrastructure (an important given) Create effective alignment mechanisms reduce redundancy/maximize reuse Minimize costs for required non-core IT functionality Internal infrastructure hardware and software 15

16 Foundational GI&S Data (Static Characterization) Exposed COI Services & Spaces Common Operational Pictures Mission Planning Systems Weapon Systems GIG Enterprise Core Services User Agents ASW Mission Alerts NSW Mission Agents Data & Services Metadata Data Store Dedicated Sensors Thru The Sensor Data On scene Processing Geo-temporal Tags Dynamic Force and Threat Information Publish Data & Service Metadata Post Data Discover & Invoke COI Service Publish Data & Service Metadata DOD Centers Post Data Discover & Invoke COI Service Virtual COEs offer added-value data brokerage & knowledge services using posted data from METOC Centers & other COIs: Joint Virtual METOC Database Domain Authority Assessment Mission-specific Environmental Alerts Visualization Services

17 USGEO ADM Effort started late 2006 Approved as an OSTP Technical Resource Jan 2008 share diverse Integrated Earth Observation System (IEOS) data and information to reduce human and environmental risks in nine societal benefit areas a framework for data and information interoperability technical resource for enabling architecture and data interoperability via a Web-based architecture.... not a technical treatise on the larger topic of Service-Oriented Architectures useful for leveraging emerging Web services and associated standards and interfaces to enable a loosely-coupled framework for data system interoperability. 17

18 NAVO: Naval Oceanographic Office FNMOC: Fleet Numerical Meteorology and Oceanography Center CUS: Commander, Undersea Surveillance AFWA: Air Force Weather Agency MESIL: METOC Enterprise Service Integration Layer JMBL: Joint METOC Broker Language NOP: Naval Oceanography Portal NMDSF: Naval METOC Data Services Framework 18

19 Service Provider Node Service Provider Node 19

20 SOA data services based Guided by DoD and Navy policies for managing data in a net-centric environment Make data visible, available and usable where needed and when needed to accelerate decision making Tag data with metadata to assist with discovery Post to shared spaces except where limited by security, policy or regulation Promote interoperability by enabling many-to-many exchanges vice point-to-point 20

21 Ensures broad range of data interoperability Define and adopt data standards through the Joint METOC Board DMWG Navy, Air Force, Army, NOAA/NWS, FAA Adapt as necessary to meet needs of multiple communities of interest (COIs) Paces timeline for exposing services on the GIG Time and resources Demand signals from PORs, COIs and federal and international partners Applies correct data access standard where relevant and appropriate to demand signal Joint METOC Broker Language (JMBL) OGC/ISO Geographic Markup Language (GML) Web Map Service (WMS) Web Feature Service (WFS) Web Coverage Service (WCS) (where applicable and when ready) Filter Specification 21

22 Navy Battlespace on Demand Framework OGC JMBL 22

23 NAVO s Naval METOC Data Services Framework (NMDSF) 1 data service operational (JMBL-based) 36 information elements available (forecast and OAML) Single access point to Navy METOC data holdings FY 09 FNMOC s CAGIPS 1 data service operational (JMBL-based) 144 information elements (forecast) Legacy APIs exist OGC-based services WMS for ASW performance surface to become operational FY09 WFS prototype in FY09 should be operational FY10 Several others emerging e.g. - bottom characteristics - optimal routes 23

24 No Interoperability Net-centric Joint METOC DoDD WMO Data Exchange Standards Adopted Strategic Center Data Exchange JM JCD Unified JM Forecast Unit Forecasts JMCDM JMBL JM WSDL DoD MDR Registration DoDD JM Taxonomy/ Ontology Restructured JMB under Joint Staff JM CONOPS DISR Standard JM Business Rules FAA/NWS adopt JMBL UCore, GML and OGC JM Capabilities Access Point JM Domain Authority JM Services Definition Major DoD Programs FAA s NextGen 24

25 NAVO s Naval METOC Data Services Framework (NMDSF) 1 data service operational (JMBL-based) 36 information elements available (forecast and OAML) Single access point to Navy METOC data holdings FY 09 FNMOC s CAGIPS 1 data service operational (JMBL-based) 144 information elements (forecast) Legacy APIs exist OGC-based services WMS for performance surface to become operational to support USW-DSS FY09 WFS prototype in FY09 should be operational for USW-DSS FY10 25