# Presentation: 185748

## AF Weather Issues for

**CEISC 04-1**

**Mr. Michael Howland**
**AFWA Technical Director/CIO**
**20 Jun  04**

## Overview

**AF CIO Issues Relevant to CEISC **
**AF Architecture Tied to Federal Enterprise Arch **
**AFW Operational Architecture**** **
**Interagency Cross Cutting Issues **
**Agency Interoperability Initiatives**
**JMIB Background**
**Notional METOC Operational Concept**** **
**Joint METOC Proposed Ops Architecture**

## AF CIO, Mr. John Gilligan, actively engaged in full oversight of all IT initiatives for AF
Clinger-Cohen Act (All IT initiatives need full OMB 300)
Built AF Enterprise Architecture, enforces use of architecture
AF Portal 
All applications web enabled and run on AF Portal servers 
End user only needs desktop system and browser
Network and server consolidation initiative
Implement Global Information Grid (GIG)  to extend network to all AF users both fixed sites and deployed (includes platforms) 
Standardize and centralize common IT purchases  
Tight enforcement of information assurance/C&A processes
Supports DoD Public Key Infrastructure (PKI) initiative
Implements DoD Community of Interest (COI) data strategy

**Clinger-Cohen Act (All IT initiatives need full OMB 300)**
**Built AF Enterprise Architecture, enforces use of architecture**
**AF Portal **
**All applications web enabled and run on AF Portal servers **
**End user only needs desktop system and browser**
**Network and server consolidation initiative**
**Implement Global Information Grid (GIG)  to extend network to all AF users both fixed sites and deployed (includes platforms) **
**Standardize and centralize common IT purchases****  **
**Tight enforcement of information assurance/C&A processes**
**Supports DoD Public Key Infrastructure (PKI) initiative**
**Implements DoD Community of Interest (COI) data strategy**

***Relevant ******AF CIO Issues***

## Implications for AF Weather (AFW)
AFWA CIO needed to track compliance with AF CIO initiatives
CIO approval needed for AFW server consolidation plan
Capital Investment Reports needed on all AFW IT funds
DoD Architecture Framework enforced for investment planning, acquisition, and interoperability with AF Ent Arch
 Manage business case to move applications to AF Portal H/W
Dedicated circuits phase out in favor of GIG/Common-User Comm
H/W for regional and unit level support not provided by AFW (we become a software application provider for these levels)
Applications - must be web-enabled and integrated with DoD GIG
External agency interfaces - may need to have PKI certificates
Homeland Security - may need to sponsor non-DoD agencies to have access to DoD networks 

**AFWA CIO needed to track compliance with AF CIO initiatives**
**CIO approval needed for AFW server consolidation plan**
**Capital Investment Reports needed on all AFW IT funds**
**DoD Architecture Framework enforced for investment planning, acquisition, and interoperability with AF Ent Arch**
** ****Manage business case to move applications to AF Portal H/W**
**Dedicated circuits phase out in favor of GIG/Common-User Comm**
**H/W for regional and unit level support not provided by AFW (we become a software application provider for these levels)**
**Applications - must be web-enabled and integrated with DoD GIG**
**External agency interfaces - may need to have PKI certificates**
**Homeland Security - may need to sponsor non-DoD agencies to have access to DoD networks **

***Relevant ******AF CIO Issues (cont)***

## AF Chief Architect’s Office reports to AF CIO
AF embraced use of DoD Architecture Framework
Mandated by Clinger Cohen Act for IT programs
Used in Capabilities Planning - Part of AF Requirements Process
Tracked by CIO and OMB in Capital Investment Reporting
Mapped to Federal Enterprise Architecture
AFW is a formally recognized warfighting mission area Architecture council - cross cuts all warfighting domains
See AFWA brief from 2 Dec 03 CEISC 
AFW actively using Architecture to guide acquisitions and roadmap migration to target end-state

**AF embraced use of DoD Architecture Framework**
**Mandated by Clinger Cohen Act for IT programs**
**Used in Capabilities Planning - Part of AF Requirements Process**
**Tracked by CIO and OMB in Capital Investment Reporting**
**Mapped to Federal Enterprise Architecture**
**AFW is a formally recognized warfighting mission area Architecture council - cross cuts all warfighting domains**
**See AFWA brief from 2 Dec 03 CEISC **
**AFW actively using Architecture to guide acquisitions and roadmap migration to target end-state**

***AF Architecture Tied to Federal Enterprise Arch***

## AFW Operational ArchitectureTo-Be Operational View (OV-1): Enterprise

***AFW Operational Architecture******To-Be Operational View (OV-1): Enterprise***

**UE**

**JFSOCC**

**CWT**

**UA**

**UA**

**CWT**

**WOC/EOC**

**CWT**

**CWT**

**JFMCC**

**JFLCC**

**JFACC**

**JFC**

**SOF**

**CWT**

**WST**

**WST**

**WST**

**WST**

**WST**

**Comm Degradation**

**GPS – Positioning Errors**

**Optical Turbulence**

**Airfield Impacts**

**Spacecraft Charging**

**Orbital Drag**

**Ground****Maneuver****Trafficability**

**Target****Acquisition / Lock-on**

**C2 Planning /****Execution**

**Maritime Impacts**

**Surveillance****Impacts - BDA**

**Hi-Res Models,****Space WX, &**
**Climatology**

**GIG**

**Flight Hazards**

**OWS**

**AFWA**

**WOC**

**CWT**

**PBA**

**OWS**

**Notes:**
The warfighter is provided a single, accurate, timely, relevant, & actionable METOC answer from the virtual Joint METOC Data Base (JMDB) comprised of forecast data, climatology, observations, long-term weather outlooks, space weather, oceanographic, and ancillary Astro/Geophysical Information.  This one-stop, mud-to-sun access point provides 1) climatological data for Combat Plans, M&S 2) observed weather situational awareness (SA) data for Ops, Training, Combat Ops 3) Predictive Battlespace Awareness weather for Combat Ops & Plans, Mission Rehearsal 4) Environmental Impacts for Ops, Combat Ops & Plans and 5) resource protecting weather watches and warnings for Ops.  All the natural environmental data & knowledge in the JMDB will be accessed via a single, Joint METOC Access Point available from the GIG, web enabled, and with digital data accessed via a single Joint METOC web-services based interface.  The JMDB, accessed via in a reachback mode and built predominantly by regional Operational Weather Squadrons and METOC strategic centers, will be able to provide the warfighter with the portion of the JMDB required for any particular mission or operation.

The future is data-centric vs. product-centric and will directly support C4ISR & Mission Planning communities as articulated in the AF C2 constellation CONOPS and required for “human-supervised, automated C2” processes in near to real-time mode “(single digit minutes to seconds)”. The data & products built from the geospatially oriented JMDB will be visualized & manipulated in a similar manner using similar tools as the warfighter.  This supports more seamless integration of METOC data into COPs and warfighter data in METOC systems Operating in secret mode in any real-world operation.

Combat Weather Teams and Weather Support Teams co-located with the warfighter will provide environmental consultant services leading to optimized battlespace and predictive battlespace awareness.  Optimization will occur by determining force/unit-level environmental mission impacts and providing actionable alternatives to off-set environmental impacts to the maximum extent possible.

## Migration away from dedicated circuits to IP based networks; growing use of wireless technology
Network technology refresh is on track for IP6
Information Assurance and Public Key Infrastructure
DoD/AF actively migrating to XML for data exchange
Web sites/pages evolving to interactive web services
DoD Transformation to Net Centric Operations and Warfare 
Note:  Separate brief (21 Jul) covers last three bullets in more detail

**Network technology refresh is on track for IP6**
**Information Assurance and Public Key Infrastructure**
**DoD/AF actively migrating to XML for data exchange**
**Web sites/pages evolving to interactive web services**
**DoD Transformation to Net Centric Operations and Warfare **
***Note:  Separate brief (21 Jul) covers last three bullets in more detail***

***Interagency Cross Cutting Issues***

## DoD Transformation to Net Centric Operations and Warfare (NCOW) 
DoD/AF Enterprise Architecture
DoD Enterprise Services
DoD Information Strategy
Communities of Interest for Data Standards - Use of XML
Use of Web Services
Joint METOC Interoperability Board (JMIB)
Joint METOC recognized as DoD COI for data management
Affiliation of JMIB and CEISC?

**DoD/AF Enterprise Architecture**
**DoD Enterprise Services**
**DoD Information Strategy**
**Communities of Interest for Data Standards - Use of XML**
**Use of Web Services**
**Joint METOC Interoperability Board (JMIB)**
**Joint METOC recognized as DoD COI for data management**
**Affiliation of JMIB and CEISC?**

***Agency Interoperability Initiatives***

## JMIB Background	

**Chartered by XOW and NO96 under NAVY/AF METOC cooperation to improve METOC interoperability within DoD (XOW/NO96 Joint Msg, 181136Z DEC 01)**
**Purpose:  “Set a definitive course for interoperability of DoD METOC data and systems with current and future DoD C4ISR systems.  Broaden the scope of cooperation between the service METOC communities in support of JV 2010/2020 objectives and improve interoperability of METOC data and product delivery within the DoD.”**
**Co-Chaired by AFWA/OA and CNMOC N5**
**Members from each service, OASD (NII), J3 Staff, and JFCOM  **
**Supported by Standing and Ad-Hoc Working Groups**
**C4ISR and Data Standardization - Permanent working groups**
**Joint METOC Symbology - Ad Hoc**
***Note:  C4ISR = Command and Control, Communications, Computers, ******      Intelligence, Surveillance, and Reconnaissance**** *

## Notional METOC Operational ConceptSupporting C4ISR and Mission Planning

***Notional METOC Operational Concept******Supporting C4ISR and Mission Planning***

- User requests  METOC for X
- mission for time
- T-20 to T+10

- Warfighter’s single, accurate, timely, relevant METOC answer

- Domain Authority:
- Points Warfighter to the
- METOC Answer

## Joint METOCProposed Ops Architecture

** ****Joint METOC Database**** a.k.a “4-D Data Cube”**
-  Virtual DB made up of data   at all DoD METOC sites
-  All JMDB segments
-   -- Physically built or      logically mapped

**C4ISR/MP Systems**
- - Access METOC  info in standard way
-  METOC info  overlaid on COP

**   ****Middleware Service Tier**
- Gets operator only part of METOC cube required
- Domain authority derives METOC answer and single forecast of the day
- Virtual Natural Environment (VNE) becomes the logicalrepository

## Summary

**AF CIO Issues Relevant to CEISC **
**AF Architecture Tied to Federal Enterprise Arch **
**AFW Operational Architecture**** **
**Interagency Cross Cutting Issues **
**Agency Interoperability Initiatives**
**JMIB Background**
**Notional METOC Operational Concept**** **
**Joint METOC Proposed Ops Architecture**