DoD TRANFORMATION: NET-CENTRIC OPERATIONS & WARFARE

1. DoD TRANFORMATION: NET-CENTRIC OPERATIONS & WARFARE Mr. Michael Howland AFWA Technical Director/CIO 20 Jun 04

2. Overview • Need for Transformation • Information Age Transformation • Net-Centric Operations & Warfare (NCOW) • Old System-of-Systems Approach • Net-Centric Approach • Net-Centric Information Technology • Attributes • Enablers • Web Services • Data Strategy • Impacts on Meteorology and Oceanography (METOC) Community • Summary

3. Need for DoD Transformation • Driven by changing strategic environment (9-11 & Global War on Terrorism) • U.S. military superiority cannot be assumed in future • Information Age technologies proliferate • U.S. dominance will increasingly be challenged in novel ways • Growing asymmetric threats requires new thinking • Force-on-force challenges likely to increase • Adversaries seek to take advantage of changes in global power relations resulting from transition to Information Age • Tech changes make military transformation imperative • Opportunity to leverage U.S. competitive advantage

4. Information Age Transformation • Translates an Information Advantageinto a decisiveWarfighting Advantage • Information Advantage -enabled by the robust networking of well informed geographically dispersed forces • Characterized by: • Information sharing • Shared situational awareness • Knowledge of commander’s intent • Warfighting Advantage -exploits behavioral change and new doctrine to enable: • Self-synchronization • Speed of command • Increased combat power

5. Old System of SystemsApproach

6. System of SystemsN-squared Problem

7. The Solution:Net-Centric

8. The Solution: Net Centric Operations & Warfare (NCOW)

9. Key IT Desired NCOW Effects • Dynamic Battle Management: “human-supervised, automated C2” • Seamless Connectivity • Deliver Timely Actionable Information: “automated machine-to-machine” ops “thereby enabling force application in single-digit minutes from the decision to engagement” • “Our goal is to see first, understand first, and act first.” General John P. Jumper; Chief of Staff, United States Air Force

10. Key Net-Centric IT Attributes • Internet Protocol • Data packets routed across network, not dedicated circuits • Only Handle Info Once (OHIO) • Data posted by authoritative sources and visible, available, usable to accelerate decision making • Post in parallel • Business process owners make their data available on the net as soon as it is created • Smart pull (vice smart push) • Applications encourage discovery; users can pull data directly from the net or use value-added discovery services • Data centric • Data separate from applications; apps talk to each other by posting data

11. Key Net-Centric IT Transformational Enablers • Global Information Grid (GIG) - Bandwidth Expansion • Building the DoD IT Infrastructure • Connectivity to the “tip of the spear” • GIG Enterprise Services (GES) • Nine Core Enterprise Services (CES) • Community of Interest (COI) Enterprise Services • New DoD Net-Centric Data Strategy (COI based)

12. Key Net-Centric IT Enabler: GIG Enterprise Services • Nine Core Enterprise Services • User Assistant – user profilers • Discovery – search activities • Collaboration • Messaging – exchange of info • Mediation – transformation processing, situational awareness support, negotiation, & publishing • Storage – physical and virtual • Application – common enterprise apps & functions • Security – IA, system & net security • Enterprise Systems Management – keep it all running smoothly • COI Enterprise Services • Functionality unique to COI – examples within METOC COI • e.g. Grid interpolation & translation, METSAT projection conversion, units conversion, product format conversion, etc. • Web Services Based

13. Web Services Evolution XML HTML Technology TCP/IP Presentation Programmability Connectivity FTP, E-mail, Gopher Innovation Web Pages Web Services Browse the Web Program the Web

14. What are Web Services? • Standard way of integrating web-based applications • Based on standards: • IP: Standard internet backbone protocol • SOAP: Session control protocol • UDDI: Discovery protocol • WSDL: Description of services • XML: Tagging data

15. Why Web Services? • Break down the silo walls and enables standard application interoperability • Ideal for machine-to-machine communications • Web services are the ultimate in re-usable code • Integrate functionality of disparite systems into an integral system-of-systems

16. DoD’s Net-Centric Data Strategy • The Net-Centric Data Strategy (signed May 9, 2003) is key enabler of DoD’s transformation • The Strategy provides foundation for managing the DoD’s data in a net-centric environment, including: • Ensuring data are visible, accessible, and understandable when needed and where needed to accelerate decision making • “Tagging” of all data (intelligence, non-intelligence, raw, and processed) with metadata to enable discovery by known and unanticipated users in the Enterprise • Posting of all data to shared spaces for users to access except when limited by security, policy, or regulations • Organizing around Communities of Interest (COIs) that are supported by Warfighter, Business, and Intelligence Domains The Strategy addresses data environment barriers…

17. Key Goals Make Data Visible Make Data Accessible Enable Data to be Understandable Enable Data to be Trusted Enable Data Interoperability DoD Net-Centric Data Strategy Goals Key Actions: • Make Data Assets Available to the Enterprise: • Use metadata to describe & advertise data assets (e.g., documents, web pages, images, etc). • Create data asset catalogs & organize by community-defined structure (ontology). • Post data assets to shared space where Enterprise users can access it • Make System Data and Processes Available to the Enterprise: • Define & register format & semantics of system data & processes • Provide reusable/easy-to-call access services to make system data & processes available to the Enterprise

18. Net-Centric Data CONOPS Producers of data maketheir data visible by advertising their data in catalogs Producers ensure data is accessible by posting data to a secure, shared storage space Producer Consumer Streaming video available. “Tagged” with discovery metadata; video available in “shared space” via data access service. Metadata added to catalog. Automated search of sources using discovery metadata. Pull data of interest. Using registered format, definitions, and core services, translate into needed structure. Security Services Consumers of data search catalogs to discovery what data assets are visible Data is accessed from shared storage space Consumer understands what the data is because its context and structure are described (e.g., PKI, SAML) Metadata Global Information Grid Shared Data Catalogs Space Enterprise & Community Services Application Services (e.g., Web) Metadata Registries The structure and semantics of certain data assets are provided by developers increasing the ability to understand and use the data asset Developer Understands the data format to build applications that post, process, exchange, and display information.

19. Impacts on METOC Community • Data, products, and knowledge seamlessly integrated in the warfighters decision cycle • Family of Interoperable Picture (FIOP) overlays • Seamless machine-to-machine operations • Stand-alone systems gone with the dinosaurs • Data integration requires common mapping & geo-locatable data & products (Geospatial Information & Services (GI&S) • Requires a data-centric focus vs. product-centric • Should reduce bandwidth – warfighters get what they need not everything we have available • Tougher to plan communications bandwidth needs

20. Impacts on METOC Community (cont) • Data posted to the GIG ASAP • Distributed net-centric functionality required • Warfighter dynamically defines what they want through discovery of posted METOC data • Unit-level obs available to GIG at unit level? • Current METOC stovepipe, value-added functionality available on the GIG as METOC COI enterprise services • Domain authority, product style, formats, translations, interpolation, METSAT projection conversion, unit conversion, etc. • Weather Tactical Decision Aids (TDAs) integrated with other COI TDAs: not a stand-alone operation • TDAs - a METOC COI enterprise service on the GIG • TDAs apps will be integrated into warfighter systems

21. Summary • DoD Transformation is here! • Centered around NCOW • Maximizing capabilities of existing and planned systems • Dynamic, fast paced environment • DoD METOC must change to meet demands of NCOW • DoD NCOW implications for cross federal and international agency information sharing????? • Implications of Web Services • Implications of DoD Data Strategy and use of XML • How do we bridge DoD mandates with Agency policies, WMO, ICAO, and IHO?