Presentation is loading. Please wait.

Presentation is loading. Please wait.

Lessons Learned Stephen McCarthy Andy Wykurz

Published byKerry Arnold Modified over 5 years ago

Similar presentations

Presentation on theme: "Lessons Learned Stephen McCarthy Andy Wykurz"— Presentation transcript:

1 Lessons Learned 2007-04-30 Stephen McCarthy Andy Wykurz
Developing a Target Architecture for Integrated Command and Control Systems Lessons Learned Stephen McCarthy Andy Wykurz

2 CF Integrated Command and Control System
The primary purpose of C4ISR activity is to support the operational decision-making process… “…turning ideas into action” Vision The CF IC2S will provide Commanders and decision makers, at the operational and strategic levels, the ability to execute command and control within a collaborative Team Canada/JIMP environment. Aim The overarching aim of the IC2S project is to develop and implement an information system that will enable the CF to effectively conduct operations in the future global security environment. IC2S will provide information and data to the operational and strategic level commanders needed to make timely, effective and informed decisions.

3 IC2S Project Principles
IC2S will be based on a single, net-centric, services-based C2 architecture and provide the decision support infrastructure that will enable the Warfighter to access, display, and understand the information necessary to make efficient, timely, and effective decisions. IC2S as a project will be responsive to the Warfighter through tightly coupled capability needs, development, test, and user engagement processes. IC2S will leverage existing and evolving C2 capabilities and follow ABC: “Adopt-before-Buy, Buy-before-Create”. Key to ABC is adaptation of commercial best practices, architectures and standards for C2. IC2S will ensure that our C2 capability evolves towards increased net-centricity and Joint mission integration

4 Project Scope NATIONAL STRATEGIC OPERATIONAL TACTICAL National OGDs
Agencies NATIONAL GOC Ops Cen CDS Strat Joint Staff Allied Strat HQ ECS STRATEGIC NFC/NDCC CEFCOM CanadaCOM and Staff SOFCOM and Staff Allied Op Level HQ OPERATIONAL Regional OGDs Agencies Allied Regional HQ/JHQ MSOC ATHENA TRINITY CanadaCOM – Region HQs X6 CEFCOM – JTF HQs SOFCOM Dets Environmental Component Cmd MCC/ACC/LCC (CanadaCOM/CEFCOM) Allied Environmental Component Commander ASIC TACTICAL Navy Unit Allied Navy Unit Deployed OGDs Agencies Army Unit Allied Army Unit AF Unit Allied AF Unit SOG Unit Allied SOG Unit (not for reference, for situational positioning only)

5 NATIONAL DEFENCE HEADQUARTERS
specific IERs Allies Force Deploy CF Ready Situ Aware Force Sustain Intel Comms Ops Mgmt Force Protec Plan Lessons Learned Coalition HQ COALITION HQ Force Deploy CF Ready Sit Aware Force Sustain Intel Comms Ops Mgmt Force Protec Plan Lessons Learned JOINT FORCE HQ Force Deploy CF Ready Sit Aware Force Sustain Intel Comms Ops Mgmt Force Protec Plan Lessons Learned Strategic CFCS Operational service specific IERs with allies Msn Sustain Msn Sustain Msn Sustain MCOIN Ops Plan Force Deploy AFCCIS Ops Plan Force Deploy LFC2IS Ops Plan Force Deploy Operational Op Ready Op Ready Op Ready Situ Aware Msn Op Con Situ Aware Msn Op Con Situ Aware Msn Op Con Intel Svc Sp Intel Svc Sp Intel Svc Sp Ops Assess Force Protect Ops Assess Force Protect Ops Assess Force Protect Tactical service specific IERs with allies Information Exchange Requirements Information Exchange Requirements Msn Sustain Msn Sustain Msn Sustain Msn Plan Force Deploy Msn Plan Force Deploy Msn Plan Force Deploy Tactical Unit Ready Unit Ready Unit Ready Sit Aware Msn Exec Sit Aware Msn Exec Sit Aware Msn Exec ISR Liaison ISR Liaison ISR Liaison Interop Force Protect Interop Force Protect Interop Force Protect NAVY AIR FORCE ARMY

6 NATIONAL DEFENCE HEADQUARTERS
specific IERs Allies Force Deploy CF Ready Situ Aware Force Sustain Intel Comms Ops Mgmt Force Protec Plan Lessons Learned Coalition HQ COALITION HQ Force Deploy CF Ready Sit Aware Force Sustain Intel Comms Ops Mgmt Force Protec Plan Lessons Learned JOINT FORCE HQ Force Deploy CF Ready Sit Aware Force Sustain Intel Comms Ops Mgmt Force Protec Plan Lessons Learned Strategic IC2S Operational service specific IERs with allies Msn Sustain Msn Sustain Msn Sustain Ops Plan Force Deploy Ops Plan Force Deploy Ops Plan Force Deploy Operational Op Ready Op Ready Op Ready Situ Aware Msn Op Con Situ Aware Msn Op Con Situ Aware Msn Op Con Intel Svc Sp Intel Svc Sp Intel Svc Sp Ops Assess Force Protect Ops Assess Force Protect Ops Assess Force Protect Tactical service specific IERs with allies Information Exchange Requirements Information Exchange Requirements Msn Sustain Msn Sustain Msn Sustain Msn Plan Force Deploy Msn Plan Force Deploy Msn Plan Force Deploy Tactical Unit Ready Unit Ready Unit Ready Sit Aware Msn Exec Sit Aware Msn Exec Sit Aware Msn Exec ISR Liaison ISR Liaison ISR Liaison Interop Force Protect Interop Force Protect Interop Force Protect NAVY AIR FORCE ARMY

7 DoDAF Documentation Methodology
AV-2 OV-6c 3.1.2 OV-6b 3.1.1 OV-6a 3.1 AV-1 1.0 OV-1 2.0 OV-5 3.0 OV-2 4.0 OV-4 5.0 SV-4 6.0 SV-10a 6.1 SV-10b 6.1.1 SV-10c 6.1.2 SV-5 7.0 SV-1 8.0 SV-3 8.2 SV-2 8.1 SV-6 8.3 SV-7 8.4 SV-9 8.5 TV-1 10.0 TV-2 11.0 OV-3 4.1 OV-7 3.2 SV-11 3.2.1 Overview and Summary High-Level Op Concept Comd Relationships Activity Model Op Rules Op State Transition Op Event/ Trace Sys Rules Sys State Sys Event/ Logical Data Model Physical Data Model Op Activity to Sys Function Trace Sys Functionality Sys Evolution S2 Matrix Sys Info Exchange Sys Interface Op Node Connectivity Op Info Exchange Integrated Dictionary Sys Perf Parameters Sys Tech Forecast Stds Tech Tech Arch Profile Sys Comm SV-8 9.0

8 Target Architecture Development Strategy
AV-2 OV-6c 3.1.2 OV-6b 3.1.1 OV-6a 3.1 AV-1 1.0 OV-1 2.0 OV-5 3.0 OV-2 4.0 OV-4 5.0 SV-4 6.0 SV-10a 6.1 SV-10b 6.1.1 SV-10c 6.1.2 SV-5 7.0 SV-1 8.0 SV-3 8.2 SV-2 8.1 SV-6 8.3 SV-7 8.4 SV-9 8.5 TV-1 10.0 TV-2 11.0 OV-3 4.1 OV-7 3.2 SV-11 3.2.1 Overview and Summary High-Level Op Concept Comd Relationships Activity Model Op Rules Op State Transition Op Event/ Trace Sys Rules Sys State Sys Event/ Logical Data Model Physical Data Model Op Activity to Sys Function Trace Sys Functionality Sys Evolution S2 Matrix Sys Info Exchange Sys Interface Op Node Connectivity Op Info Exchange Integrated Dictionary Sys Perf Parameters Sys Tech Forecast Stds Tech Tech Arch Profile Sys Comm SV-8 9.0 Departmental Priorities Information Exchanges (IERs) Force Planning Scenarios Business Activities Capabilities System Functions/ Services Current & Future Systems

9 Target Architecture Development Strategy
AV-2 OV-6c 3.1.2 OV-6b 3.1.1 OV-6a 3.1 AV-1 1.0 OV-1 2.0 OV-5 3.0 OV-2 4.0 OV-4 5.0 SV-4 6.0 SV-10a 6.1 SV-10b 6.1.1 SV-10c 6.1.2 SV-5 7.0 SV-1 8.0 SV-3 8.2 SV-2 8.1 SV-6 8.3 SV-7 8.4 SV-9 8.5 TV-1 10.0 TV-2 11.0 OV-3 4.1 OV-7 3.2 SV-11 3.2.1 Overview and Summary High-Level Op Concept Comd Relationships Activity Model Op Rules Op State Transition Op Event/ Trace Sys Rules Sys State Sys Event/ Logical Data Model Physical Data Model Op Activity to Sys Function Trace Sys Functionality Sys Evolution S2 Matrix Sys Info Exchange Sys Interface Op Node Connectivity Op Info Exchange Integrated Dictionary Sys Perf Parameters Sys Tech Forecast Stds Tech Tech Arch Profile Sys Comm SV-8 9.0 Departmental Priorities Current & Future Systems Information Exchanges (IERs) Business Activities Force Planning Scenarios Business Activities Capabilities Services Services

10 Constraints NECC is the way ahead in C2 for the US. Canada is already using US technology (GCCS-M and TBMCS) for some of our C2 systems. It makes sense to ensure that we are able to map our new systems to the US development.

11 US Net Enabled Command and Control (NECC)
Operational Activities System Functions Cross-Function 9.0 Force Protection 8.0 Force Employment Maritime/Littoral Operations 7.0 Force Employment: Land Operations 6.0 Employment: Air/ Space Operations 5.0 Situational Awareness 4.0 Intelligence 3.0 Force Readiness 2.0 Force Projection 1.0 Operational Force Protection 1.9 Force Employment Maritime-Littoral Operations 1.8 Land Operations 1.7 Air-Space 1.6 Shared Situation Awareness 1.5 Intelligence JIPB - ISR Management - Targeting 1.4 Force Readiness 1.3 Force Projection Total Force Visibility 1.2 Joint Command and Control Planning & Execution 1.1

12 Approach Determine Future Systems 2 Year Target Architecture
To-Be Target Architecture Information Elements … Determine Future Systems SV-4 Services NECC SV-4 Service reference models … Departmental Priorities OV-5 (Activities) NECC OV-5 UJTL/CJTL … Force Planning Scenarios

13 Lesson Learned - Architectural Prerequisites
Before starting an architecture the following reference products must be in place: Reference set of Operational Activities Reference set of Services Reference set of Information Elements Departmental Priorities

14 Why Architectural Prerequisites
All of these products are used in the creation of “composite” architectural products such as the OV-3. The creation of composite products is simplified and stabilized by having reference data available before the composites are created. Also mapping AS IS systems to a stable set of Services allows the TO BE to be mapped to the same Services ensuring full system coverage.

15 Simplifies and Stabilizes OV-3 Discovery
Operational Activities Information Elements OV-3 Receiving Activity Sending Activity Information Content Other Attributes

16 Identify Future Systems
Services Readiness SA Information Elements COA

17 Lessons Learned - Lack of Standard Military Reference Operational Activities
How the Operational Activities organized hierarchically is highly “political” and therefore there are many versions of possible OV-5’s hierarchies. Identify the lowest level Operational Activities and allow each organization to roll them up as required. Operational Force Protection 1.9 Force Employment Maritime-Littoral Operations 1.8 Land Operations 1.7 Air-Space 1.6 Shared Situation Awareness 1.5 Intelligence JIPB - ISR Management - Targeting 1.4 Force Readiness 1.3 Force Projection Total Force Visibility 1.2 Joint Command and Control Planning & Execution 1.1

18 Lessons Learned – Lack of Standard Military Services Reference Model
IC2S is to take a Service Oriented Architecture approach DoDAF 1.0 is System Function Oriented DoDAF 1.5 introduces the concept of Service which it defines as: The distinct part of the functionality that is provided by a system on one side of an interface to a system on the other side of the interface to include those capabilities to execute a business or mission process or exchange information among both machine and human users via standard interfaces and specifications.

19 Lessons Learned – Lack of Standard Military Services Reference Model
Services and System Functions not the same thing Service System Function System Outlook Calendaring Outlook Calendaring Palm Calendaring Palm SOA/Target Architecture Approach DoDAF Documentation Approach Generic Specific Generic Specific

20 DoDAF 1.5 Services DoDAF 1.5 defines the SV-4b as a Services Functionality Description, the SV-5c as a mapping of Services back to Operational Activities and the SV-5d as the mapping of services back to systems. Services Operational Activities Services Systems Systems Operational Activities

21 SOA Services Need a definition and a framework for Service in an SOA environment OASIS definition of Service in Service Oriented Architecture is a good start. A mechanism to enable access to one or more capabilities, where the access is provided using a prescribed interface and is exercised consistent with constraints and policies as specified by the service description. (OASIS- Organization for the Advancement of Structured Information Standards)

22 Service Framework Capability: Electric Power Usage Service: Electric
Power Delivery Interface: three prong 110 volt outlet Operational Activities: make tea, cool food, cook food … Constraints: min max voltage, min max amperage … Policies: safety is users responsibility, utility will meter and bill for usage …

23 Service Framework (C2) Capability: Command and Control Service: Shared
Situational Awareness Interface: Specified imagery and graphics Operational Activities: plan operation, modify plan during engagement … Constraints: … Policies: accurate as of one hour, For use only in static site …

24 Why Standard Military Services Reference Model
Use the service as the reference point to determine Future Systems. Future US Systems Services Mapping Future Canadian Systems NECC MCPs helps define

25 TO BE Roadmap Development Approach
2 Year Target Architecture 4 Year Target Architecture To-Be Target Architecture Existing system enhancements Determine Future Systems SV-4 Services New Canadian Projects Departmental Priorities OV-5 (Activities) New US and Allies Projects External Drivers Force Planning Scenarios

26 Roadmap Challenges Traceability of Departmental Priorities
Strategic/Business Views Required Application of Priorities

27 Traceability

28 Discussion

Download ppt "Lessons Learned Stephen McCarthy Andy Wykurz"

Similar presentations

UJTL Ontology Effort TMCM Nelson And Marti Hall. Overview Vision for the UJTL and METLs Scenario Mapping Findings Proposed POA&M outline.

UJTL Ontology Effort TMCM Nelson And Marti Hall. Overview Vision for the UJTL and METLs Scenario Mapping Findings Proposed POA&M outline.
Navy Mission Essential Task Lists (NMETLs) and METOC MEASURES

Navy Mission Essential Task Lists (NMETLs) and METOC MEASURES
DoDAF V2.0 Community Update Overview

DoDAF V2.0 Community Update Overview
AF Aerial Layer Network Approach

AF Aerial Layer Network Approach
© 2009 The MITRE Corporation. All rights Reserved. Evolutionary Strategies for the Development of a SOA-Enabled USMC Enterprise Mohamed Hussein, Ph.D.

© 2009 The MITRE Corporation. All rights Reserved. Evolutionary Strategies for the Development of a SOA-Enabled USMC Enterprise Mohamed Hussein, Ph.D.
Navy’s Operational Authority for Naval Networks, Information Operations, and FORCEnet 2004 Strike, Land Attack & Air Defense Annual Symposium Vice Admiral.

Navy’s Operational Authority for Naval Networks, Information Operations, and FORCEnet 2004 Strike, Land Attack & Air Defense Annual Symposium Vice Admiral.
® DODAF CADM/AP233 Interoperability Project David Price OSJTF March 2006.

® DODAF CADM/AP233 Interoperability Project David Price OSJTF March 2006.
DoD Architecture Framework Overview

DoD Architecture Framework Overview
Dynamic Case Management for Military and Intelligence Departments Can Improve Their Enterprise Architecture Programs Dr. Brand Niemann Director and Senior.

Dynamic Case Management for Military and Intelligence Departments Can Improve Their Enterprise Architecture Programs Dr. Brand Niemann Director and Senior.
Connecting People With Information DoD Net-Centric Services Strategy Frank Petroski October 31, 2006.

Connecting People With Information DoD Net-Centric Services Strategy Frank Petroski October 31, 2006.
NATO Network Enabled Capabilities

NATO Network Enabled Capabilities
1 How Semantic Technology Can Improve the NextGen Air Transportation System Information Sharing Environment 4th Annual Spatial Ontology Community of Practice.

1 How Semantic Technology Can Improve the NextGen Air Transportation System Information Sharing Environment 4th Annual Spatial Ontology Community of Practice.
Network Enabled Capability Through Innovative Systems Engineering Service Oriented Integration of Systems for Military Capability Duncan Russell, Nik Looker,

Network Enabled Capability Through Innovative Systems Engineering Service Oriented Integration of Systems for Military Capability Duncan Russell, Nik Looker,
Preparing the Way for NATO Network Enabled Capability J. Troy Turner C4 Interoperability Standardization ACT C4I Division.

Preparing the Way for NATO Network Enabled Capability J. Troy Turner C4 Interoperability Standardization ACT C4I Division.
Army Doctrine Publication (ADP) 3-37; and Army

Army Doctrine Publication (ADP) 3-37; and Army
1 Universal Core Executive Briefing Paul Shaw COI Forum October 16, 2007.

1 Universal Core Executive Briefing Paul Shaw COI Forum October 16, 2007.
Technical Integrity Assurance For Product Development W. Henson Graves Lockheed Martin Aeronautics Company 817.777.1856 Russ Campbell.

Technical Integrity Assurance For Product Development W. Henson Graves Lockheed Martin Aeronautics Company Russ Campbell.
JT4A July 2010 Part II - Use of Architecture Products for Evaluating Info Exchange A Combat Support Agency Defense Information Systems Agency.

JT4A July 2010 Part II - Use of Architecture Products for Evaluating Info Exchange A Combat Support Agency Defense Information Systems Agency.
Overview of DoDAF (based on Deskbook)

Overview of DoDAF (based on Deskbook)
1 Process Engineering A Systems Approach to Process Improvement Jeffrey L. Dutton Jacobs Sverdrup Advanced Systems Group Engineering Performance Improvement.

1 Process Engineering A Systems Approach to Process Improvement Jeffrey L. Dutton Jacobs Sverdrup Advanced Systems Group Engineering Performance Improvement.

Similar presentations

Ads by Google