1 / 34

Global Information Grid (GIG) Architecture and Reference Model

Global Information Grid (GIG) Architecture and Reference Model. Information Brief. Department of Defense. Terry Hagle, Office of DoD CIO/A&I 607-0235 terry.hagle@osd.mil. What Is The Global Information Grid?. The GIG Is. A transforming construct for managing DOD Information Technology

jlinder
Download Presentation

Global Information Grid (GIG) Architecture and Reference Model

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Global Information Grid (GIG)Architecture and Reference Model Information Brief Department of Defense Terry Hagle, Office of DoD CIO/A&I 607-0235 terry.hagle@osd.mil

  2. What Is The Global Information Grid? The GIG Is • A transforming construct for managing DOD Information Technology • Essential to the achievement of network-centric operations • Inherently a system of systems (federated and integrated processes) • An architectural balance between interoperability and security • In being today in an “as is” Enterprise architecture The GIG Is Not • A single program or service contract • A requirements bound Grand Design • An “all at once” implementation • An excuse for bigger budgets

  3. CIO does not determine the warfighting requirement, but is required to assess the impact of the warfighting requirement on the enterprise IT infrastructure CIO briefing to JROC, March 2000 Scope of CIO Responsibilities

  4. Version 1.0 -- AS-IS Architecture Version 2.0 -- TO-BE Architecture NCOW Reference Model – Transition Strategy Global Information Grid ArchitectureDoD’s Information Technology Architecture • DoD CIO • “Develop, maintain, and facilitate the implementation of a sound and integrated • information technology architecturefor the executive agency” • (40 U.S.C. Section 1425)

  5. GIG Architectures GIG ARCHITECTURE VERSION 1.0 GIG ARCHITECTURE VERSION 2.0 • An integrated Objective Architecture • C4ISR Arch Framework compliant • Timeframe: 20XX • Multiple AOR scenario (USNORTHCOM, USCENTCOM, CFC/USFK, SECDEF/OSD) • Multiple use cases (Tactical, Operational, and Strategic) • Architectural descriptions of Net-Centric concepts • Standards Technology Forecast (vs. Technical Architecture Profile) • Approved December 2003 • An integrated Baseline Architecture • C4ISR Arch Framework compliant • Timeframe: 2001 • Single AOR scenario (USCENTCOM) • Operational level (JTF operations) • First cut at describing PSA functions, the JOA, systems templates, and KIPs • Approved August 2001

  6. Global Information Grid Architecture Net-Centric Operations and Warfare Reference Model Transition Strategy

  7. Overview Reference Model Activity Decomposition Service Oriented Architecture Data Strategy Information Assurance Strategy (TBD) Reference Model Use Cases Systems View Technical View Reference Model Briefings

  8. Provide Program Managers (the target audience) acquisition guidance on what to make contractually binding beyond the Joint Technical Arch (JTA). Provide immediate utility without time-consuming analysis of the DoD Enterprise Architecture (GIG Architecture Versions 1 and 2) Overcome difficulty of relating and applying a broad Enterprise Architecture to specific programs. Provide common net-centric architectural constructs congruent with the DoDAF. Establish a common languageand taxonomy for NCOW concepts. Demonstrate and promote the TPPU Vision. Focus the GIG Arch compliance requirement Support evolution of the DoD Architecture Framework and the JTA Why Build a Reference Model? Building the Model is a collective DoD effort

  9. NCOW REFERENCE MODEL OVERVIEW AND SUMMARY INFORMATION NCOW REFERENCE MODEL INTEGRATED DICTIONARY • Identification • Name: NCOW Reference Model BETA 2.0 • Architect: OASD(NII), A&I • Organizations Involved: xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx • When Developed: xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx • 2. Purpose xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx Kangaroo: xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx xxxxx: xxxxxxxxxxxxxxxxxxxxxxxxxxxxx xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx xxxxx: xxxxxxxxxxxxxxxxxxxxxxxxxxxxx xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx xxxxx: xxxxxxxxxxxxxxxxxxxxxxxxxxxxx xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx High-Level Operational Concept Graphic OV-1 Activity Model and Activity Decomposition OV-5 Reference Model Version 1.0 Content Approved Dec 03 Overview and Summary Information AV-1 Integrated Dictionary AV-2 Version 1.0 Version 0.9 BETA 2.0 BETA 1.5 BETA 1.0 NCOW REFERENCE MODEL DATABASE Target Technical View Systems View SV-1 and SV-2 First description of Net-Centricity at the Enterprise Level

  10. Reference Model Activity Decomposition NET-CENTRIC OPERATIONS AND WARFARE REFERENCE MODEL Provide Net-Centric Information Environment A1 Interact with Net-Centric Information Environment A2 Perform Net-Centric User/Entity Services A3 Provide Net-Centric Services A4 Resource Service Requests A5 Manage Net-Centric Information Environment Activities conducted users to access the GIG and use the various services and capabilities provided within the GIG The interface to the GIG employed byall user architectures Activities are performed within the GIG to invoke appropriate services and provide intelligent assistance to the users Infrastructure Provided Services andCommunity of Interest (COI) Supplied Services Activities are performed within the GIG to provide enterprise services, capabilities, and environment controls Management of GIG Capabilities includingInformation Transport Activities performed within the GIG to provide management of the Net-Centric Environment Activities conducted to provision infrastructure resources for the requested services

  11. Reference Model Activity Decomposition “Provide Net-Centric Info Environment” Provide Net-Centric Services Interact With Net-Centric Information Environment Resource Service Requests Resource Service Requests Perform Net-Centric User/Entity Services Manage Net-Centric Info Environment

  12. Net-centric Data Strategy XML tagged data with appropriate infrastructure of registries and catalogues that makes data both visible and accessible Producer Consumer Streaming video available for use, tagged and stored in shared space. Metadata added to catalog based on registered format. Describes content using metadata Posts metadatain catalogs and datain shared space Automated search of data based on core metadata standard. Pulls data of interest. Based on producer registered format and definitions, translates into needed structure. Security Services (e.g., PKI, SAML) Searches metadata catalogs to find data (e.g., community andenterprise-wide search services) Analyzes metadata to determine context of data found Pulls selected data based on understanding of metadata Ubiquitous Global Network Metadata Catalogs Shared DataSpace Enterprise & Community Web Sites Application Services (e.g., Web) Metadata Registries Posts to and uses metadata registries to structure data and document formats for reuse and interoperability Developer Understand the data format to build applications that post, process, exchange, and display target information.

  13. Reference Model Systems View

  14. Reference Model Target Technical View Technical Areas by Core IT Category Hetergeneity-Aware P2P Services Description and Registration Services Access and Invocation Services Discovery and Integrtaion Web Service Security Processing Internet Protocol Security Policy (IPSP) Protocol Emerging Transport Services Tag Switching for IP Routing Internet Protocol Version 6 (IPv6) Interoperable Intelligent Agents Mobile Networking Content Storage Distribution and Mgt Inter-Domain Routing Multicast Networking HCI Transfer Mobile Cryptography High Assurance IP Interoperability Security Policy Framework/ (PCIM) Common Information Model (CIM) Schemas Directory Enabled Network (DEN) Protocol Common Open Policy Service (COPS) Protocol Survivability Scalability Service Level Agreements (SLA) Quality of Service (QOS) Class of Service (COS) Policy Other

  15. Service Architects Army G6, Air Force/XI&CIO, Navy/USMC (Office of CIO) Army Future Combat System (FCS) Transformational Communications Office Transformational Communications Architecture (TCA) DISA (NCES Program) GIG Enterprise Services (GES) AoA and CDD Reference Model Review and Coordination Business Management Modernization Program Business Enterprise Architecture (BEA) National Defense Industrial Association Net-centric Operations Industry Forum

  16. Version 1.0 Service Oriented Architecture Approved Dec 03 Version 1.1 Net-centric Data Strategy DoD and Industry (NDIA) comments Draft Version -- May 04 Version 1.2 Net-centric Information Assurance Strategy DoD and Industry (NDIA) comments Draft Version -- July 04 Net-centric Constructs Language/taxonomy Service Oriented Architecture Data strategy Information Assurance strategy Reference Model Versions

  17. GIG Architecture Compliance • Architecture products comply with Architecture Framework product definitions and purposes • Architecture data conform to the CADM • IT/NSS standards derived from the DoD JTA (or presents case for new or unique standards as necessary • Conforms to the GIG Net-Centric Operations and Warfare Reference Model: • Uses Reference Model definitions and vocabulary • Incorporates Reference Model OV capabilities and services in the materiel solution • Net-centric Data Strategy • Net-centric Information Assurance Strategy • Incorporates Reference Model TV IT/NSS standards in the TV products developed for the materiel solution Compliance is verified by inspection and analysis

  18. GIG Architecture Web Site https://disain.disa.mil/ncow.html

  19. Questions?

  20. Clinger-Cohen Act, 1996 (Information Technology Management Reform Act) Directs “Agency” (DoD) CIO to develop/maintain an Information Technology Architecture (ITA) OMB Directives Describe the Business Model/Processes and Arch Descriptors Federal Enterprise Architecture DoD Policy changes incorporating architecture DoDD 8100.1, Global Information Grid Overarching Policy CJCSI 3170.01C, Joint Capabilities Integration and Development System DoDD 5000.1, The Defense Acquisition System GIG Arch, Version 1.0 Approved by DoD CIO -- Aug 2001 GIG Arch, Version 2.0 Approval by DoD CIO -- Aug 2003 Net-Centric Operations and Warfare Reference Model Version 1.0 approved for use, Dec 2003 Background

  21. Warrior Components Global Combat Support System (GCSS) Global Applications Medical Business Applications Computing (Power Processing) Megacenter Services Information Management Network Operations Software Distribution from Central Files Electronic Mail Delivery Web Services Wireless Comm MSS SATCOM Communications Teleports RF Nets Commercial Fiber DISN Doctrine Policy Foundation Governance Engineering Spectrum Standards Architectures Global Information Grid GIG CRD GIG Architecture Implementation - Pilots, Programs and Legacy Mgmt Policy Overarching Information Assurance Networks Network Operations Computing Interoperability Wirelless Information Management FundingStrategies Governance

  22. Optical Mesh IP Network Integrated GIG Network TCA SATCOM Incorporates mobile/tactical users and global intelligence via optical cross links and EHF IP links Net-Centric Enterprise Services Provides information and data services to all GIG users Core Enterprise Services (9) + Application Program Interfaces Defense in Depth Op-IntelDataApplications Processes Key Net-Centric Initiatives Roadmap FY04 FY 05 FY 06 FY07 FY08 FY09 Policy & Architecture Guidance UCS Directive IPV6 Implementation Completed (Goal) Arch/NCOW Reference Model UCS Implementation Joint Tactical Radio System Software Communications Architecture Provides IP-based, self-managed, BLOS, mobile data and voice communications services Cluster 1 Vehicular & Army Rotary Wing Cluster 2 Handheld Cluster 3 Maritime & Fixed Station Cluster 4 Airborne Cluster 5 Handheld, Manpack, Embedded WNW IOC Cluster 3 IOC Cluster 2 IOC Clusters 1,4,5 GIG Bandwidth Expansion Optical Bandwidth to Ground Sites ELIMINATE BANDWIDTH CONSTRAINTS Provides ubiquitous, secure, robust optical IP foundation network Optical Bandwidth to STEP and Teleport sites IPV6 FOC IOC 1 2 3 4 TSAT (FY11 Launch) Wideband Gapfiller Optical IP Networking for Joint Operations Centers and ISR locations Optical Bandwidth Support for Additional Global Hawk UAVs Reachback Capabilities for Deployed Forces Wideband Networking for UAVs and Other ISR Block 2 (All CESs) in 3 Spirals Block 1 (All CESs) in 3 Spirals - Enterprise Systems Management - Messaging - Discovery - Mediation - Collaboration - User Assist - IA/Security - Storage Services - Application DEPLOY TRUSTED SERVICES Information Assurance Programs Enables trusted computer, networking, and data services to all GIG users CAC Fully Deployed 40 Gb Terrestrial HAIPE IP Identity Mgmt Infrastructure (PKI, Biometrics); Network Defense (Enterprise Sensor Grid) 10 Gb Terrestrial HAIPE IP 1 Gb Terrestrial HAIPE IP 40 Gb Space HAIPE IP(FY2010) Horizontal Fusion Portfolio Global Net-centric Surveillance and Targeting Multi-INT Fusion for Warfighters Automated Tagging of Selected Sensor and Combat Support Data Improved Strategic & Tactical C2 Collaborative Collection Management IMPROVE SENSEMAKING Improved Shared Access to Collateral ISR data Means/tools to enable the smart pull and fusion of data by users Improved Shared Access to Combat Support Data Net-Centric Enterprise Services ISR Battle Management Deployment of Collaborative Applications to Joint Commanders Power To The Edge ForceNet Deployable CJTF HQs Future Combat System (FCS) Net-Centric DCGS (examples)

  23. GIG ArchitectureVersion 1.0AS-IS Architecture

  24. OPERATIONAL TACTICAL SECDEF NATIONAL STRATEGIC THEATER STRATEGIC JCS CJCS MILITARY DEPTS J STAFF COMBATANT COMMANDER SERVICE COMPONENTS J STAFF CJTF J STAFF JFLCC JFMCC JFACC JFSOCC ARFOR MARFOR AFFOR NAVFOR SOFFOR Joint Task Force Model LEVELS OF WAR AND DECISION-MAKING

  25. “As-Is” - 2001 C4ISR Architecture Framework - compliant “To-Be” - 2010 GIG Arch V1.0One Integrated Architecture:Three Views Joint Operational Architecture (JOA) Integrate Extant Architectures Warfighting Focus Joint Mission Areas NetOps CINCArchitectures Service Enterprise LevelArchitectures TECHNICAL OPERATIONAL SYSTEMS Technical Architecture Profile High-Level Operational Concept Graphic System Interface Description Systems Communications Desc. • Functionals • Intell • Logistics • Health Affairs • Personal & Readiness • Finance Operational Node Connectivity Description Functional Architecture Data Standards Technology Forecast Systems2 Matrix Operational Information Exchange Matrix Systems Functionality Description Command Relationships Chart Operational Activity to System Function Traceability Matrix Activity Model Sys Information Exchange Matrix Operational Rules Model Sys Performance Parameters Matrix • All Views • AV-1: Overview • & Summary • AV-2: Integrated • Dictionary Operational State Transition Description CIO J6 National Level Architectures J3 System Evolution Description Operational Event/Trace Description Computing and Comms Templates System Technology Forecast Comm and Computing Systems View Systems Rules Model Logical Data Model System State Transition Description Systems Event/Trace Description Physical Data Model USCENTCOM AOR Model: Joint Task Force Joint Technical Architecture Mandated and Evolving Standards Operational Scenario Timelines Threats Joint Forces

  26. Unclassified Employ Fires (A3.1.2) x USED AT: AUTHOR: DATE: 08/01/00 WORKING READER DATE CONTEXT: PROJECT: REV: DRAFT RECOMMENDED NOTES: 1 2 3 4 5 6 7 8 9 10 PUBLICATION C2 ROE C3 OPLAN/CONPLAN Unit Readiness Info Assess Mission I4 I5 Unit Readiness Report O1 Target Status O2 A3.1.2.1 A1 ATC C1 Plan Mission Flight Schedule ATO I1 CSAR Info I6 Final Mission Plan O3 WEAX A3.1.2.2 I8 A2 Mission Sortie P. 3 Generate Aircraft Status Assessment Sorties A3.1.2.3 A3 Comm Plan I3 P. 4 Mission Recordings Flight Status Update Execute O4 Sorties GPS info A/C I7 A3.1.2.4 Organic BDA A4 P. 6 PHM Data (Includes WPN Intelligence Products I2 Expenditures) M1 Mission Acft Data Non-Organic BDA NODE: TITLE: NUMBER: Unclassified A0 Execute Strike Aircraft Ops P. 2 14 01/03/2001 Office of the Department of Defense Chief Information Officer GIG Architecture V1.0Driven By The DoD Enterprise Model Joint Mission Capability Focus • 2003 DoD Architecture Framework IT Capabilities and Interconnections (Overlays on Requirements) Functional/Information Requirementsand Relationships Systems Choices (‘Brand Names”) Crises, Missions, AORs ... Systems View • Combatant Cmd Headquarters • Major JTF Components • Selected Weapons Systems Operational View • Basis of Joint Ops Arch. • Joint Mission Areas • PSA Functional Areas Technical View Standards and Conventions (manditory and emerging) • Derived From JTA ref architecture • Major DoD and IC interfaces Building Codes

  27. GIG Architecture, V1.0 “Front Page”

  28. New Responsibilities ASD(NII) and DoD CIO

  29. Net-Centric Operations & Warfare …The Emerging Way of War An information Superiority-enabled concept of operations that generates enhanced combat power by networking sensors, decisions makers, and shooters with increased information sharing and collaboration to achieve shared awareness, increased speed of command, higher tempo of operations, greater lethality, increased survivability and a degree of self synchronization

  30. GIG ArchitectureVersion 2.0TO-BE Architecture

  31. Identify and describe required enterprise IT capabilities for Net-Centric Operations and Warfare Chart the policy course for building and acquiring Net-Centric systems capabilities Support DoD transformation to a Net-Centric enterprise GIG ARCHITECTURE v2 Purpose

  32. GIG Archictecture v2 SCOPE GIG ARCHITECTURE VERSION 2 1 2 SECDEF FORCE ALLOCATION (OBJECTIVE) SECDEF COOP (BASELINE) AOR-LEVEL FOCUS NATIONAL-LEVEL FOCUS 3 4 HOMELAND DEFENSE HOMELAND SECURITY (OBJECTIVE) SOUTHWEST ASIA WARFIGHTING (OBJECTIVE) STRATEGIC USE CASE STRATEGIC USE CASE 5 KOREA WARFIGHTING (OBJECTIVE) COMBINED USE CASE TACTICAL USE CASE OPERATIONAL USE CASE NET-CENTRIC OPERATIONS/WARFARE

  33. All View Operational View Systems View Technical View DoD CIO Policy Memoranda Reference Model Approval Process NCOW Reference Model Version 1.0 Review and Comment Reference Model Working Group “Community” and Stakeholders GIG Architecture Working Group Review and Comment Recommend Approval GIG Architecture Integration Panel DoD CIO Executive Board DoD Policy Evolution Recommend Approval Approve (As Required) (As Required)

  34. What is the Reference Model? • A distillation of GIG Architecture Version 2 • Easier to use reference for Architecture Developers, Capabilities Developers, and Program Managers • The “standard” for describing net-centricity • Built using the architecture constructs of the Framework • Operational, system and technical view products • Presented in a functional neutral form • Answers the question: “What’s different about net-centricity?” • Defines the core IT standards required for net-centricity • Contains a “Target” Technical View • No change to current JTA policy

More Related