Your SlideShare is downloading. ×

NCOIC SCOPE Executive Overview

787

Published on

An overview of the System-of-Systems, Capabilities, Operations, Programs, and Enterprises (SCOPE) Model …

An overview of the System-of-Systems, Capabilities, Operations, Programs, and Enterprises (SCOPE) Model

Published in: Technology, Business
0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total Views
787
On Slideshare
0
From Embeds
0
Number of Embeds
0
Actions
Shares
0
Downloads
5
Comments
0
Likes
0
Embeds 0
No embeds

Report content
Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
No notes for slide

Transcript

  • 1. SCOPE Executive Overview 23 April 2010 NCOIC Briefing Releasable to International NCOIC-SCOPE Exec Overview20100423 1
  • 2. Net-Enabled Capability (NEC, NCO, NCW, etc.)  Many benefits of Information Sharing via Net-Enabled Capability (desired outcomes of operations) – Across Warfighter, Logistics, Admin, & Intelligence domains – Interoperability of systems across Services & countries – Interoperability with non-military systems  Hard Questions: (in order to achieve desired outcomes of operations) – Across which systems? And how much is enough? Typical Constraints!  Cost  Schedule  Performance (especially of Legacy Systems)  Policy & Law  Personnel, etc. 2
  • 3. What is the value of using the SCOPE Model?  SCOPE Helps to Answer the Hard Questions! – System-of-Systems, Capabilities, Operations, Programs, and Enterprises (SCOPE) Model  Not a Computer Model – Structured Analysis using Subject Matter Experts (SMEs) – Not “One Size Fits All” • Tailored to meet stakeholder needs  Goal: Validated Needs for Net-Centricity – Not definitive “Shall” statements found in procurements! – Obtain consensus across multiple stakeholder viewpoints • With focus on interoperability • In a specific range of environments • Within constraints 3
  • 4. Where can SCOPE be used? Typical SCOPE applications  Specific System-to-System Interactions  Enhancing Legacy Systems  Analysis of Alternatives  Architectural Trade Studies  Federation-of-Systems (unplanned coalition participants)  System-of-Systems Environment Net-Enabled Capability (NEC) can leverage all of these 4
  • 5. SCOPE for NEC PROGRAM PROGRAM PROGRAM PROGRAM PROGRAM A B A B C COMMON ? Core Services COMMON ? ? Grow Common Core Services? PROGRAM PROGRAM PROGRAM PROGRAM ADMIN A B A B LOGISTICS PROGRAM PROGRAM D A B COMMON COMMON Modify Program A or B? Custom Bridge between A and B? WARFIGHTER INTELLIGENCE 5
  • 6. SCOPE is not just about Technology! Includes Policy, Includes Culture, Procedures, Processes People Behaviour, etc. Doctrine, etc. Example-- differences in: Technology  E-Mail, Chat  User Interfaces  DOTMLPF(I)  TTPs, etc. SCOPE Considers Interaction of People, Processes, and Technology in a Net-Centric Environment 6
  • 7. “Interoperability” Is Key… But A Complex Topic Political or Business Objectives Organizational Interoperability Harmonized Strategy/Doctrines People & Layers of Interoperability Process & Aligned Operations Applications NEEDS Aligned Procedures Knowledge/Awareness of Actions CONSTRAINTS Semantic/Information Interoperability Information Services Data/Object Model Interoperability Connectivity & Network Interop. Network Transport Technical Physical Interoperability Interoperability
  • 8. The Role and Value of the SCOPE Model Commercial Example Enterprise Objectives Domain Specific Node General Architectures Architectures On-time Cargo Delivery Architecture A The SCOPE Model measures RANGES of Enterprise a domain’s needs and capabilities in many Tailored Architecture dimensions that relate to interoperability QoS Cost Transfer Rate Net Awareness Security (Illustrative of a greatly simplified SCOPE analysis; actual SCOPE Model Autonomy covers many dimensions in more depth) Capability Service Orientation Scope 8
  • 9. The Role and Value of the SCOPE Model Commercial Example SCOPE gives SMEs a basis for achieving consensus The SCOPE Model measures needs Domain Specific Node Enterprise Objectives of each domain General Architectures in many Architectures On-time dimensions… Cargo Delivery Architecture A QoS Transfer Cost Rate Tailored Enterprise Architecture Net Awareness Security ? Tailored Interoperable? Autonomy Service Orientation Capability Scope Fuel Efficient Architecture Operations B … and each domain often has different needs, characterized SCOPE leads to solutions via the SCOPE Model (but does not directly provide them) 9
  • 10. SCOPE Model Dimensions  Net Readiness Dimension set – Measures openness and adaptability of component systems, people & processes when working with each other over networks  Capability/Operational Scope Dimension set – Measures breadth, depth, and diversity of operational capabilities that leverage the networks • Most are domain dependent, some are common across domains  Technical Feasibility Dimension set – Measures feasibility of achieving desired operational capabilities via the networks SCOPE is Tailorable to Common and Unique Needs In hundreds of Assessment Dimensions 10
  • 11. SCOPE Model Dimension Hierarchy Template A Starting Point that is Meant to be Tailored! (Based on Experience with Root Causes of Interoperability Failures) 11
  • 12. SCOPE Model Enables Practical Analysis of Enterprise Breadth Army Operating Concepts Service Concepts Marine Corps Ops Naval Operating Concept Air Force CONOPS Joint Functional Concepts Enabling Concepts Joint Operating Concepts 12
  • 13. SCOPE Model is Evolving  SCOPE Model will continue to Evolve – Changing Needs, Processes, and Technologies – Changing Behaviour of People using Networks  SCOPE has been successfully applied within NCOIC member organizations – Provides Stakeholders with a valuable means of determining & validating net-centric requirements for NEC – Provides NCOIC with valuable feedback regarding training of SCOPE practitioners • And valuable feedback regarding SCOPE Dimensions A “Win-Win” Interaction regarding SCOPE Model 13
  • 14. Typical SCOPE Workshop Flow SCOPE Workshop Domain Assessment Context, Sponsorship Dependent Purpose, & Workshop Goals Questions Finalized Completed SCOPE Team Document Review Primary Stakeholders Participant Scheduling Workshop Contacted Deconfliction Outbrief SCOPE Team Pre-Workshop Formation SCOPE Question Workshop Workshop Meeting Selection Meetings Summary Completed Report SCOPE Team Develops Draft Context & Domain Dependent Questions Timeline is Dependent on Expected Breadth and Depth of Stakeholder Objectives 14
  • 15. Net-Enabled Future SCOPE is useful in achieving Net-Centric Goals Today: Stovepiped SCOPE is focused on Interoperability Systems, and is a full-contact social sport! Point-to-Point Networks 15

×