Jack Zavin Chief, Information Interoperability DoD CIO/A&I Directorate

1. Net-Centricity & Net Ready It’s More than Information/Data Interoperability Jack Zavin Chief, Information Interoperability DoD CIO/A&I Directorate (703) 607-0238, FAX (703) 607-0248 Jack.Zavin@osd.mil

2. Interoperability “ The ability of systems, units or forces to provide services to and accept services from other systems, units or forcesand use the services to enable them to operate effectively together.” Joint Publication 1-02 (emphasis added) ... the right information... at the right time ... in the right format ... to the right “warfighter” Interoperability is more than just information exchange: it impacts systems, process, procedures, organizations and missions over the life cycle; and it must be balanced with Information Assurance

3. Network-Centric or Net-Centric? • Network implies infrastructure • Net-centric supports non-linear relationships and increased tempo of operations

4. ASD(NII)/DoD CIO Vision Power to the Edge People throughout the trusted, dependable and ubiquitous net are empowered by their ability to access information and recognized for the inputs they provide. Three goals: • Build the net • Populate it • Protect it

5. Net-Centric Operations & WarfareA Transformation Enabler Net-Centricity is a transformation enabler that empowers all users with the ability to easily discover, access, integrate, correlate and fuse data/information that support their mission objectives. Netted force

6. Power to the Edge 1. Make information available on a net that people depend on and trust Department of Defense Transformation Planning Guidance April, 2003 2. Populate the net with new, dynamic sources of information to defeat the enemy 3. Deny the enemy advantages and exploit weaknesses Future Directions For Defense “Services will explicitly identify initiatives to improve … adoption of “post before process” intelligence and information concepts, achievement of data level Interoperability; and deployment of “net-ready” nodes of platforms, weapons and forces. From To Supplier Dominates Consumer Dominates Task Process Exploit Disseminate Task Post Process Use

7. NET CENTRIC ATTRIBUTES A work in process

8. B A R R I E RB A R R I E R B A R R I E R B A R R I E R End-User Producer End-User Consumer “What data exists?“ “How do I access the data?” “How do I know this data is what I need?” “How can I tell someone what data I need?” “How do I share my data with others?” “How do I describe my data so others can understand it?” User knows data exists and can access it but may not know how to make use of it due to lack of under- standing of what data represents User is unaware this data exists User knows this data existsbut cannot access itbecause of organizational and/or technical barriers ? Organization “A” Organization “B” Organization “C” Net-Centric Data StrategyDefining the Problem

9. DoD’s Net-Centric Data Strategy • The Net-Centric Data Strategy (signed May 9, 2003) is a key enabler of the Department’s transformation: • The Strategy provides the foundation for managing the Department’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.

10. Information Format & Content • Information Transfer • Information Processing • User Interface Information Exchange Requirement Activity 1 Node B Activity 1 Activity 2 Node A Activity 3 Interface, Speed, Security, Interoperability Level,... Activity 2 Node B System X System Y System X (Collaboration) Node A System Z Information Exchange Requirement Interface System Y InformationExchangeRequirement Activity 1 Network Paths Interface System Y Activity 4 Node C Interface Node C System X Integrated Architecture *(One Architecture - 3 Views)with Related Sources & Documents JOINT OPERATIONS, OPERATING, FUNCTIONAL & INTEGRATING CONCEPTs All View The Operational View describesand interrelates the operational elements, tasks and activities, and information flows required to accomplish mission operations. The Systems Viewdescribes and interrelates the existing or postulated technologies, systems, and other resources intended to support the operational view. * Functional Area & Organizational “AS Programmed ” & “T0 BE(s)” The Technical Viewdescribes the profile of rules, standards, and conventions governing systems implementation. • Information Security DOT_LP_ Documents (e.g. TTP, Doctrine) JOINT TECHNICAL ARCHITECTURE • The bottom line: keep this equation balanced:OV = SV + Non-Materiel

11. Trade Study: Preliminary Mammoth vs. Game Population Final Game Site Survey Tiger vs. Rabbit Selection Survey Selection Meat Meat Requirements Site Preparation Requirements Review Site Selection (MRR) Game Sightings Final Hunting Hunt Leader Plan Chosen Preliminary Hunting Plan Preliminary Hunter Preliminary Selection Hunting Weapon Trade Study: Review Selection Club vs. Spear Weapon (PHR) Development Weapons Obtain Blessing Meat Practice and Skill of Great God Distribution Final Hunter Qualification Thag Plan Selection Critical Hunting Site Forecast Review Inspection Schedule Weather (CHR) Hunt Weapons Inspection Examine Hunt Entrails Readiness Review Distribute Hunter (HRR) Transport to Meat Inspection Cave Catch Game KILL Game Yes, but Og assures me that Get Caught Chase Game this will improve By Game Choose New Hunt Leader our efficiency and keep us ahead of I don't know. It seemed those Lose Game Cro-Magnons in easier when we just the valley. went hunting.

12. The Global Information Grid DoDD 8100.1 The GIG supports all Department of Defense, National Security and related Intelligence Community missions and functions in war and in peace. The GIG encompasses the globally interconnected, end-to end set of information capabilities, associated processes and personnel for collecting, posting, distributing and managing information on demand by warfighters, policy makers and support personnel.

13. GIG Has A JTF Focus GIG Architecture V1.0 OV-1

14. Joint Capabilities Integration & Development And The GIG Architecture CJCSI 3170.01C “As they are developed, the integrated architectures will provide the construct for analysis to identify capability shortfalls, compare alternatives for improving joint warfighting capabilities, and associated resource implications.” The GIG Architecture represents information use and Information Technology in the capabilities process Fits Here

15. Force Application Force Protection Focused Logistics Command & Control Capability Roadmap 2004 2006 2008 2010 2012 2014 2016 task a task b task c Capabilities-Based Methodology Concepts Architectures Assessment National Military Strategy capability capability capability Dominant Maneuver Architecture task d task a task g task b task c task e task f DM DM Joint Operations Concepts Battlespace Awareness system 1 system 2 Service Concepts Joint Operating Concepts system 3 Functional Concepts system 4 system 5 Integrating Concepts system 6 Resource Strategy Sys 1 Block Upgrade New Sys FOC Sys 3 SLEP Sys 2 End of Svc Life capability capability 2008 2010 2012 2014 2004 2006 Training Change Field New Organization

16. Status OF JOINT CONCEPTS Joint Operating Concepts SecDef Joint Concepts Approval Authority Status Homeland Defense Strategic DeterrenceMajor Combat OperationsStability Operations Pending Signature Pending Signature Pending JCS-Tank directed changes Pending JCS-Tank directed changes Revision Plan Under Review Joint Functional Concepts JROC Force Application Force Protection Command and Control Battlespace Awareness Focused Logistics Net-Centric Capabilities and Attributes Validated Capabilities and Attributes Validated Capabilities and Attributes Validated Capabilities and Attributes Validated Capabilities and Attributes Validated Under Development Joint Integrating Concepts CJCS Joint Forcible Entry Operations Joint Undersea Superiority * Selection of FY04 JICs – April ’04 - CJCS Under revision Accepted, Capability Based Assessment underway

17. Where we are moving to: The Net-Ready KPP • Net-Ready Key Performance Parameter (NR-KPP). The NR-KPP assessesinformation needs, information timeliness, information assurance, and net-enabled attributes required for information exchange and use. The NR-KPP consists of measurable and testable characteristics and/or performance metrics required for the timely, accurate, and complete exchange and use of information to satisfy information needs for a given capability. The NR-KPP is comprised of the following elements: • Compliance with the Net-Centric Operations and Warfare (NCOW) Reference Model (RM) • Compliance with applicable Global Information Grid (GIG) Key Interface Profiles (KIPs) • Verification of compliance with DoD information assurance requirements • Supporting integrated architecture products required to assess information exchange and use for a given capability

18. Information needs … Information timeliness … Information assurance … Net-enabled … • Information Needs: A condition or situation requiring knowledge or intelligence derived from received, stored, or processed facts and data. • Information Timeliness: Occurring at a suitable or appropriate time for a particular condition or situation. • Information Assurance: Information operations that protect and defend information and information systems by ensuring their availability, integrity, authentication, confidentiality, and non-repudiation. • Net-Enabled: The continuous ability to interface and interoperate to achieve operationally secure exchanges of information in conformance with enterprise constraints. Required KPP Attributes

19. Architecture Products Required to Assess Information Exchange and Use Information needs … (AV-1, OV-2, OV-4, OV-5, SV-4, SV-5, SV-6) Information timeliness … (OV-6c, SV-5, SV-6) Information assurance …(OV-5, SV-4, SV-5, SV-6) Net-enabled … (OV-2, SV-4, SV-5, TV-1, NCOW RM)

20. Applicable KIP Compliance Supporting Architecture Metrics NCOW RM Compliance • Inspection • Analysis • Test • Inspection • Analysis • Inspection • Test IA Compliance • Inspection Measurable and Testable Net-Ready KPP Net-Ready KPP Synthesis & Verification

21. Organizing Construct for IA Information Operations Network Operations Computer Network Recon Exploit Attack Information Assurance Information Dissemination Management Computer Network Defense Network Management PSYOP EW, etc. Defense in Depth Strategy Protect, Detect, React Capabilities Supported by People, Technology & Operations

22. DODD 8530 DODD 8500 NIAP/CC DITSCAP IAVA NIPRNet SIPRNet CAP SABI Defense in Depth UCP/ SPACE JTF GNO DIAP UCP/ STRAT DISA CERT JTF CNO CIAO JTF CND NIPC PDD-67 PDD-62 Patriot Act PCCIP Sophistication of CND/IA PDD-63 Melissa Code Red Y2K NIMDA SNMP ER 97 SolarSunrise Moonlight Maze 95 96 97 98 99 00 01 02 03 Brief History of IA/CND

23. IASE – Your One Stop Shop • All Doc’s referenced in this course can be found here!!! • iase.disa.mil

24. DoD 8500 Series • 8500 series: Overarching IA guidance • 8510 series: Certification and accreditation • 8520 series: Protection of SCI material • 8530 series: Computer network defense (CND) • 8540 series: Interconnections between security domains • 8550 series: Network and web access content, privileges • 8560 series: IA monitoring and readiness testing • 8570 series: IA personnel training and certification

25. IA in GIG Architecture • Establish CND Baseline Architecture • Defense in Depth • Demilitarized Zones (DMZs) • Firewalls • Intrusion Detection Systems (IDSs) • Ports & Protocols Management • Configuration Management

26. The Confusion Factor Levels of Warfare Joint Mission Areas • As Is • Deployment/Redeployment • Movement and Maneuver • Strategic Deterrence • Overseas Presence • and Force Protection • Special Operations • Joint C2 • Focused Logistics • Multinational Ops and • Interagency Coordination • Employ Fires • Information Operations • Force Protection • MOOTW • ISR • Communications/Computer • Environment CM-1014-00; Joint Mission Areas to Organize the Joint Operational Architecture; 6 September 2000 • Strategic • Operational • Tactical Organizational Structure • Joint Task Force • JTF Standing Headquarters • COCOM • Military Service Functional Joint Operations Capability Joint Functional Capabilities (NC,C2,FA,FP,FL) Joint Operating Capabilities Joint Integrating Capabilities Missions or Mission Threads • To Be • Deployment/Redeployment • Dominant Maneuver • Strategic Deterrence • Overseas Presence • and Force Protection • Special Operations • Joint C2 • Focused Logistics • Multinational Operations • and Interagency Coordination • Precision Engagement • Information Superiority • Full Dimensional Protection • Close Air Support • Combat Search and Rescue • Theater Air and Missile Defense • Suppression of Enemy Air Defenses • Others • Enterprise • Community • of • Interest • Porfolios • BMMP Domains • Acquisition/Procurement • Finance Accounting Operations & Financial Management • Human Resource Management • Strategic, Planning, & Budgeting • Installations & Environment Operational Capability? • SIGINT • MASINT • Fire Support • Personnel • Logistics Enterprise Information Environment Mission Area

27. Concurrent • Responsive • Timely • Consistent Information • Sequential • Unresponsive • Untimely • Inconsistent Information Commander’s Guidance Combat Assessment Target Development Capabilities Assessment Mission Planning Commander’s Decision The Joint Targeting Cycle in a Net Centric Environment “As Is” “To Be”

28. Consumer Producer and Developer Make Data Accessible to and Usable by Known and Unanticipated Users Empowering Known and Unanticipated Users Shift Power to the User: • Bring data consumers, producers, and system developers closer together through Communities Of Interest • Guide data management activities through user-driven metrics, user ratings/feedback, and data sharing incentives • Provide the infrastructure and services (e.g., GIG B/E, NCES, Shared Spaces, Catalogs) to permit the user to find and retrieve data

29. Backup Slides

30. Joint Forces Commander (incl. Battle Staff) Nexus – The (Multinational) Joint Task Force Operations The Campaign for Achieving Information Interoperability Processes Organizations Senior Command Authorities Logistics & procurement Sustainment Operations Medical support Direct Support Elements JWAC Personnel support JIC/JAC CINC Staff Augmentation Teams NSOC JSC Non Government Organizations (NGOs) other Spec. Ops Component Commander Maritime Component Commander Air Component Commander Land Component Commander Verification Funding Integrated Architectures & Standards Balanced & Synchronized Doctrine Organization Training Materiel Leadership Personnel Facilities Solution Sets Across the life cycle from “new” to “fielded” DoDD 4630.5 & DoDI 4630.8

31. Supporting Architecture Metrics

32. MID 905 Clarification MID 905 requirement to register XML metadata by 9/30/03 3 Apr ’03 Accessibility—Posting Data to Shared Spaces Nov ’03 XML Registration Single Clearinghouse. 22 Apr ’02 DoD Net-Centric Data Directive Jan ’04 DoD Net-Centric Data Implementation Guides Details on “how to” 2004 How to Make Data Accessible Mar ‘04 How to Advertise Data Mar ‘04 How to RegisterMetadata Mar ‘04 Data Management Congressional Report Outlined data approach for moving to Net-Centric Environment 15 Mar ’03 Net-Centric Data Strategy Net-Centric vision, goals, and approaches for data 9 May ’03 DoD Discovery Metadata Specification (DDMS) Preliminary Review VersionApr ’03 Version 1.0Sept ‘03 GIG Enterprise Services Transition Plans from Components for FY 06 Program Reviews Guidance Memos Directives, Plans and Standards Implementation Guidance Evolution of Net-Centric Data Strategy Core Enterprise Services Implementation Plan for transitioning to CES May ‘03 Visibility—Advertising Data Assets with Discovery Metadata 24 Oct ’03 Usability—Registering All Structural Metadata Dec or Nov ’03 (Expands MID 905 Clarification) Dates in italics represent release for formal coordination • denotes completed