Network Centric Operations Industry Consortium SCOPE Model Overview

1. Network Centric OperationsIndustry ConsortiumSCOPE Model Overview December 8, 2006 Hans Polzer Vice Chair, Services and Information Interoperability (SII) Working Group NCOIC Dec06-130

2. SCOPE Purpose • Describes the key elements of how a set of Systems supports a Capability, Operation, Program or Enterprise (SCOPE) over a network • Whether the set constitutes a family of systems, a system of systems, or just an ad hoc grouping is contextual and a matter of degree • Can involve multiple capabilities, programs, or enterprises • Helps define the scope and diversity of the systems in a given context • Highlights nature of issues affecting system interoperation • Helps identify how a given system could better support the larger context in a net-centric ecosystem (“scope creep”) How isolated or connected are the systems to each other and to their enviroment and what purposes do they support?

3. SCOPE Model Features • Net Readiness Dimension set • Measures how open and adaptable component systems are to working with each other over the network • Capability/Operational Scope Dimension set • Measures how broad, deep, and diverse the operational architectures are that the systems are designed to support • Technical Feasibility Dimension set • Measures how feasible it is to achieve desired operational capabilities, given the systems and their needed information exchanges over the network using established technical standards and infrastructure Net-centricity is not free, adaptability is purpose-driven, and the network is only somewhat transparent

4. Relating Systems of Systems, Capabilities, Operations, Programs, and Enterprises (SCOPE) Enterprise “Intergalactic Radiator” by Capt Yurchak For SCOPE illustration only Current Navy Warfare Sponsors EXW N75 SUW N76 USW N77 AW N78 Tactical C2 MCP Budgets allocated vertically ISR MCP Navigation MCP Individual Programs/Systems or System of Systems ASW N74 Missile Defense MCP Time-CriticalStrike MCP Systems of systems often aligned to these capabilities Operations (often in and out of page) Illustrates Complex Dependencies in Capability Acquisition

5. UJTLs Capability Scope Dimensions Technical Feasibility Dimensions Operational View Can capability be achieved with current stds & technologies? Are new standards needed? Is the information obtainable, Accurate, timely? Broad Open High Identifies Participant Relationships and Information Needs Which Systems interact? About what? How much? And why? To what effect? Battlespace Representation and Naming standards Closed Low Narrow Data element standards, Protocols, Environments Net-Ready Dimensions Data models, Process algorithms Technology readiness levels Technical View Systems View Prescribes Standards and Conventions Relates Capabilities/Characteristics to Operational Requirements What do systems say to each other? How is this information represented? How do systems interact? What standards are used? DODAF Views and the SCOPE Model

6. Capability Scope Dimensions Value Broader Scope Narrower Scope Dimension

7. Broader Scope Narrower Scope Value Dimension Program X Capability Scope Dimension Example

8. One Possible Enterprise Breadth “Hypercube” Army Operating Concepts ServiceConcepts Marine Corps Strat21 Naval Operating Concept Air Force CONOPS Joint Functional Concepts Enabling Concepts Joint Operating Concepts

9. Sample Capability-Specific Scope Dimensions More Capability Less Capability Value Example Dimensions

10. Sample Functional Capability Profile Narrower Scope Broader Scope Current X Proposed X C7 C8 C6 C5 C1 Actual MOP Threshold C2 Capability Scope Measures C4 Capability Specific Measures C3

11. Net Ready Dimensions and Levels Tighter Coupling / Less Net-Readiness Looser Coupling / More Net-Readiness Value Dimension

12. Technical Feasibility Dimensions Larger Risk Smaller Risk Value Dimension

13. Summary • SCOPE is a comprehensive, balanced approach to assessing SOS from a net centric operations perspective • Based on actual system use cases • Evolved through application against real programs • Yet has an overarching perspective on the problem space • SCOPE is being evolved through an open forum • NCOIC SII WG • External involvement in SCOPE is welcomed and encouraged • Mitre is an NCOIC member • SCOPE has potential to be a net-centric content-based complement to CMMI • But focused more on “best fit” to the problem domain rather than “maturity” or “level” based • Helps position programs/systems in the larger ecosystem of institutional goals and capabilities

14. Backup Slides

15. Encyclopedic Information, Public Info Models, And Open Source Data Strategy Development and Execution – Intention, Desired Effect Purpose, Situational Understanding People, Objectives, Perceptions, Intentions, Assessments Oplan Development and Execution Purpose, Situational Awareness Battlespace Information Models (S) Battlespace Information Models (O) Doctrine, OPCONS, Effects, Process Battlespace Information Models (T) “Sense-making” World Model Building Activities Data From Deployed/Tasked Data Collection Assets Phenomenology – Sensing the Real World Capability Information Domains

16. Net Enabling the Social and Cognitive Domains Through the Information Domain Social Domain Cultural Awareness Cognitive Domain Cognitive Advantage Process Advantage Conveyed Commander’s Intent Plan, Organize, Deploy, Employ and Sustain Cycle Compressed Operations Shared Awareness Network Centric Operations Physical Domain Force Advantage Position Advantage Information Domain Information Advantage Precision Force Speed and Access

17. Socializing the SCOPE Model • Network Centric Industry Consortium (NCOIC) • Primary framework for Services and Information Interoperability Working Group • Evolving the model with inputs from the Working Group • Tying the model to other NCOIC work products • Software Engineering Institute (SEI) • Tech Exchange held in Feb 06; interest in collaborating on CMMI applied to SoS • DoD NII, AF, Navy, JFCOM, DISA • Incorporated the NC Checklist in Net Ready dimensions • DISA interested in SCOPE model via NCOIC • Pushing SCOPE model and cross-domain integration via NCOIF Working Group participation • Provided input to AF AFIMM model, Navy Net Warfare Command, JFCOM J69

18. Evolving the SCOPE Model • NCOIC Services and Information Interoperability Working Group (SII-WG) revisions underway • Changes to all three dimension sets • Agreement on new top-level dimensions in each set • Working to define and refine the sub-dimensions • Developing measures and scale for each sub-dimension • Plan to adopt the revised SCOPE model dimensions in 4Q 06 and incorporate into NC Profile Assessments • Looking at “trigger” questions to facilitate selective depth along any one dimension in assessment process

19. Evolving the SCOPE Model • Revised Net Readiness Dimensions • Discovery • Service, Information • Information Model Pre-Agreement • Evolvability • Service, Application, Information • Information Assurance Capabilities • Architecture Dependency • Autonomics • Self Awareness, Composability, QOS, etc

20. Evolving the SCOPE Model • Revised Capability Scope Dimensions • Enterprise Type, Overall Scope and Cohesiveness • Enterprise/Capability Breadth • Enterprise/Capability Depth • Organizational Business Model and Culture • Enterprise/Capability Life-Cycle Dynamics • Semantic Congruence and Interoperability • Information Domain Scope • Physical, Information, Cognitive, Social, Inter-domain • Operational Context Flexibility/Diversity • Time Dimensions, Reality Dimensions, Context Types • Inter-Enterprise Adaptability

21. Evolving the SCOPE Model • Revised Technical Feasibility Dimensions • Inter-Element Time Binding Sensitivity • Transport Capacity Needed • Bandwidth, Latency, Availability • Service Capacity Needed • Run-Time Computing Resources Needed • Enterprise Service Management Feasibility • Dynamic Service Composition Feasibility • Dynamic Resource and Network Configuration Feasibility • Information Assurance Feasibility • QOS Feasibility • Interface Development Complexity • Technology Readiness Level for System Connections