1. COMNAVMETOCCOM Brief to the CEISC CDR Dave Pashkevich CNMOC N51/N52 (228) 688-4326 pashkevichd@cnmoc.navy.mil 20 Jul 04

2. Navy Involved Efforts of Inter-Agency Interest Joint METOC Interoperability Board (JMIB) Joint METOC Broker Language Navy Enterprise Architecture Weather Research and Forecasting (WRF) Model Virtual Joint Program Management Office Transformation Efforts Other

3. Joint METOC Interoperability Board (JMIB) Chartered for “the implementation of a management structure with policy and procedures by which the services will improve joint usage of meteorology, oceanography, and space environmental architectures; standards; algorithms; models; databases; applications; and interfaces” Co-Chaired by CNMOC and AFWA; members include reps from all Services and OASD (NII). Two standing working groups: the Data Standardization Working Group and the C4ISR Interoperability Working Group; Ad hoc working groups are formed as required to support the standing groups and board directions.

4. Joint METOC Interoperability Board (JMIB) Recent efforts by JMIB have been to develop Joint METOC concept of operations (CONOPS) for C4ISR and mission planning system (MPS) support, data standards, and common access methods to support DoD Global Information Grid (GiG) Services with goal to make METOC data and information universally available for interoperable warfighter systems in standard formats and with common delivery methods across the DoD. Most visible success has been to establish XML-based Joint METOC Brokering Language (JMBL) to allow web services access to METOC information from any C4ISR or MPS in a common method regardless of the provider. To empower the JMIB, plans are for JS/JFCOM to Co-Chair in the interim with JFCOM lead as final end-state.

5. Joint METOC Broker Language Allows web services access to METOC information from any C4ISR or MPS in a common method regardless of the provider. Despite efforts, widespread implementation of JMBL standards has lacked as the JMIB does not have the authority to mandate compliance.

6. Navy Enterprise Architecture DoD Architecture Framework (DoDAF) defines a common approach for describing, presenting, and integrating DoD architectures - Enterprise management - Identification of operational requirements - Rationalization of IT investment decisions - Improvements to interoperability among various systems Navy METOC Enterprise Architecture efforts began in May 2000

7. Weather Research and Forecasting (WRF) Model WRF Executive Oversight Board participation Navy METOC funding programmed for FY05 and out years

8. Virtual Joint Program Management Office (VJPMO) Established to aid aligning the activities of the services’ program offices charged with acquiring, fielding and sustaining METOC systems and capabilities USAF, USA, USN, USMC, and USCG participation Specific goals: –Improve development, acquisition and sustainment efficiencies. –Coordinate focused technology transition efforts to ensure commonality. –Deliver fully interoperable, network-centric, operational environmental effects capabilities. –Support the operational requirements of Joint and Service warfighters. Initiatives –JET/ LEADS –Flight Weather Briefer –Upper-Air Profiler

9. Navy METOC Transformation CNO’s Vision –Seapower 21 –Recapitalize the Navy –50,000 manpower cut through FY09 METOC Program Reviews –Internal and External Results of Reviews and CNO mandates –Reorganize N096 staff N61 - FORCEnet N61M - Deputy Oceanographer with a staff of 4 N61R - ISR, the rest of the 096 staff –Realign CNMOC under Commander Fleet Forces Command (CFFC) Lead TYCOM concept Echelon 3 command

10. Navy METOC Transformation Results of Reviews and CNO mandates (cont.) –20% Manpower cut through the FYDP (1st cut FY06) Outsourcing Staff cuts Drawdown overseas Consolidate Maritime forecasting (OTSR/WEAX) –Norfolk (Feb 05) and Pearl Harbor (Dec 04) Aviation hub concept –Norfolk (Oct 05) and San Diego (Jan 05) –Minimal detachment manning OA divisions reduced –OA detachments formed (MET) –Surge capable based on Fleet Response Plan (FRP)

11. Aviation Support “Reduce Observers through Automation” “Centralize Forecasting Centers” The Current Navy Plan –Augment CONUS Airfield Observations with Automated Observation Systems (ASOS Normalization) –Medium/Large OPUPs at Hubs –Centralize CONUS Aviation Forecast at Two Sites Joint/Interagency Opportunities –CONUS Consolidation/Integration of Aviation Support with Air Force, Marine Corps and National Weather Service –Joint Planning and Development Office for an Integrated National Plan for Aviation Weather

12. Transformation Efforts FNMOC and AWFA Consolidation/Integration Discussion has been initiated with a goal of a Joint DOD Atmospheric Modeling Capability Navy and Air Force are also investigating consolidation/ integration of select Regional METOC Centers and Operational Weather Squadrons

13. Other Issues JAAWIN –AFWA creating web based template for observational data submission –Unclassified and classified observations Navy/Marine Corps Intranet, Base Level Information Infrastructure, IT-21 (NMCI/BL- II/IT-21) –Driving Navy’s Enterprise Services –Mandate for all legacy systems, networks, and components connected to the networks to be NMCI, BL-II, or IT-21 compliant

14. Questions?