IC2S Scoping Discussion

1
IC2S Scoping Discussion

• IC2S Background
• IC2S PM Lorna Palmer
• DPM Dave Campbell
• Sept 12, 2007

2
Contents(1)

• Objective
• IC2S Vision
• IC2S Scope Understanding
• Overview
• Approval History
• Option development
• IC2S Requirements for Success
• Questions on Preceding

3
Objective

• To provide background on the IC2S project
• How have we got here
• Findings
• Way ahead
• Synchronize understanding of background
• New members of IC2S extended team
• Establish common baseline of information

4
IC2S Vision

• IC2S 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.
• IC2S 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.

5
IC2S Project Scope/Interdependencies

• IOC Partial Roll-out of Operational and
  strategic SA (COP) and C2 Capabilities to support
  domestic and deployed Ops 09/10
• Included GCCS J acquisition for testing (existing
  projects to initiate FMS case), exploitation of
  new capabilities and gap analysis with LF model
• FOC Fully Integrated C2 platform with JIMP
  interconnectivity, integrated support,
  operational and strategic SA (COP) 13/14
• Key Interdependencies with

• PSEPC (SCIP)
• Allies (GRIFFIN)
• Corporate Info Systems (eg MASIS)
• Defence CMP

• ITSM
• DISB
• CFCS I
• AFCCIS
• JIIFC
• LCSS/ISTAR

• AGS
• MMHS
• EISE
• JSS
• MSOC
• UAV

• GCCS
• TBMCS
• CF Wide C2IS In-Service Support Orgs (DIMEI, CFCS
  Support, MCOIN, etc)

6
Project Scope Division between Tactical and
Operational is a Concern
National OGDs Agencies
NATIONAL
GOC Ops Cen
CDS Strat Joint Staff
Allied Strat HQ
ECS
NFC/NDCC
STRATEGIC
Allied Op Level HQ
CEFCOM CanadaCOM and Staff
SOFCOM and Staff
OPERATIONAL
Allied Regional HQ/JHQ
Regional OGDs Agencies
CanadaCOM Region HQs X6 CEFCOM JTF HQs SOFCOM
Dets
MSOC ATHENA TRINITY
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
Allied AF Unit
AF Unit
SOG Unit
Allied SOG Unit
7
IC2S Project FOC Targeted Solution
Multi-function Single Desktop - Integrated C2
Backbone
SECRET
Interagency (OGD)
Tactical Land
Tactical Maritime
IC2
desktop
Multi-national
Tactical Air
Common Decision Support Apps Critical C2 Apps
baseline Core GCCS JC2 Operational
SA/COP Strategic SA/COP CEO Backbone
Public
Top Secret
DND Corporate ERP
DND Corporate Secret
Interconnect includes - Sensors C2, Email,
Diode, Guard, Web services, Data Exchange (ERP)
8
IC2S Scope
9
Overview

• Pre 2005
• DJCP established 90M as budget for CFCSII
  (IC2S)
• 2005
• With an approved High level SOR and a common
  understanding of what IC2S should deliver, the
  IC2S team (PD and PM) developed plans
• Cost exceeded notional budget thereby making
  RAdm Thiffault reluctant to progress project
• 2006
• Asked to provide 2 options for consideration by
  4 Generals (LGen Leslie, MGens Hincke, Hines
  and Ward)
• Cost of preferred scope exceeded notional budget

10
Satisfaction of Commanders Deliverables
Appvd scope
Appvd cost
11
Option Development

• In deriving options IC2S
• Removed funding included to evergreen
  system/infrastructure
• Worked with the following to capture and address
  concerns
• Projects such as LCSS LE, LF ISTAR, GCCS M
  upgrade, JCS (AIR), NBCD etc
• DFPPC
• In service support groups
• Matrix groups such as architecture, IM security
• Sponsor
• Environments
• Commands

12
Stakeholder Feedback

• Navy (DGMEPM/DMRS) Comments
• Supports requirement for CFCS II project and
  integration of environmental systems at strat/op
  level
• There are specific tools that need to remain
  environmental responsibility
• DFPPC (Terry Melnyk)
• Supports direction of CFCS II project Tiger Team
• Project Thrusts too ambitious for 90M, consider
  De-scoping
• Other option - sub projects for each thrust
• Air Force (DGAEPM) Comments
• Supports CFCS II project scope and overall aim
  (integration and Cap Management framework)
• Decision Support is an overarching construct,
  IMRS is underneath
• Go with Best of Breed for common Apps
• Need a CEO backbone

• Army (DLCI/DGLEPM) Comments
• Agree on the long term CFCS II plan, need to
  agree on priority (of Thrusts)
• Need to address the Data model issue up front and
  look towards convergence of data models in
  2011/12 with C2IEDM model and JC2
• Cant support a field domain and a garrison
  domain of tools, need to use same tools in both
• Desktop integration, like DWAN, but with a
  governance structure
• Skill fade a problem, need training, centre of
  excellence, SOPs, rules on info management
• Priority must be Joint (internal to CF) and then
  Team Canada, not allies
• CFIOG (Col Turnbull)
• Focus on improving services and service delivery
• Recognizes that additional capital investment is
  required to improve ITI.

13
Overview contd (2006-2007)

• 2006
• C2 co-ordination office stood up
• Adopted IC2S approach to C2 get well
• Evergreening removed from options
• RAdm Thiffault stated that Capability Mgmt would
  look after this (late 2005)
• Project continues to progress with support of
  DGSP, IM Gp, CFD
• Continuing to pre-position for eventual approval
• 2007
• Capability Management office stood up
• IC2S Omnibus project concept adopted
• Break scope into smaller projects
• IC2S continues to provide co-ordination to
  fragmented C2 enterprise development

14
Key Features of Options

• Convergence to a common C2 core that
  accomodates/transitions LF data model and GCCS
  family
• Omnibus program/project to manage and co-ordinate
  all C2 related projects and matrix initiatives
  and activities
• Options development lab for full PRICIE options
  development and assessment
• Integrated Support Concept
• Analysis to ensure full exploitation (1) of
  existing C2 capability
• Process development rework
• Training in context, acquisition of differently
  skilled people
• (1) key observation was that a lot of capability
  had been delivered by projects such as CFCS and
  other initiatives but that the capability had not
  been fully exploited and many gaps could be
  filled using existing capability

15
IC2S Keys to Success

• Enterprise Architecture
• Capability Management Framework
• In context of SPOC managing an integrated C2IS
  capability
• Recapitalize existing network
• Expanded footprint
• Business continuity/archiving
• Integrated Training capability
• In Service Support
• In context of higher level capability
  prioritization
• Prioritized list of deficiencies/capabilities
• Co-ordination of C2 projects and initiatives to
  meet prioritized capabilities
• Governance
• Operational champions for each thrust
• Doctrine and concepts development and refresh

16
Section 1
17
Contents(2)

• IC2S Recent Work
• Courses of Action Analysis
• Order
• Potential Scope
• Questions on Preceding

18
IC2S Work

• Pre-definition reports and documents (37)
  (summaries of some areas will be provided)
• Senior management recognized that pre-definition
  work was necessary to advance IC2S and by
  inference IC2 while budget and scope issues were
  under discussion
• Studies widely distributed and providing
  excellent value to the stakeholders on functional
  and technical sides
• Enterprise architecture
• Support organizations
• Requirements development and management plan
  fully PRICIE enabled
• Identification of weaknesses and opportunities
• Requirements management enabled by DOORS
• Assistance to Capability Manager and IC2
  requirements capture
• Focused study on COP underway at direction of
  Capability Manager
• Capability Management Framework
• Enterprise Architecture Charter

19
Courses of Action

• IC2S looked at findings from pre-definition
  studies and consolidated them in DOORS
• Findings were consolidated in the following
  groupings

• Joint Situational Awareness
• Imagery Mgmt
• Strategic SA
• Op/Tact SA
• Fusion
• Reporting and Assessment
• Alerts
• Status reporting
• Information gathering
• Integrated CIS
• Access
• Tactical Comms
• Security and Integration
• Operational Communication
• Support

• Joint Planning
• Collaborative Planning
• Targeting
• Battle Planning
• Decision Support
• Req for Information
• Operational Order Preparation
• Course of Action
• Direction Development
• Strategic Development
• Order Preparation
• Dissemination
• PRICIE

20
Order of Action

• The following slides show that there is a
  precedence/dependency of actions
• Data first (can be parallel with Common
  enterprise svs)
• Standard format
• Metadata
• Authoritative source and steward
• Common enterprise services such as Security
• C2 support services such as GIS services
• Common C2 business services such as Track
  management
• Specific C2 business services such as Blue Force
  Tracking Alert service
• IC2S scope should address the foundations before
  the second floor

21
Modular Net-Centric Capability (shows foundation
elements and service dependencies)
Semantic Filter Semantic Products from User
Groups
SpecificBusiness Services

User Led Groups
WeaponTarget Pairing Service
Attack Analysis Service
Target Analysis Service
TST Conflict Detection Service
Comm LinkStatus Service
BFT Alert Service
C2 CommonBusiness Services

C2 Entity Management Services
Data Fusion Services
C2 Mediation Services
TrackManagement Services
GPS Nav Accuracy Service
AIS Aggregation Service
Common C2 Support Services

DataProvisioning Services
EventManagement Services
Orchestration Services
Visualization Services
GIS Services
ServiceDiscovery Services
ServiceSecurity Services
Enterprise ServiceManagement Services
Machine-to-Machine Messaging Services
Metadata Services
Mediation Services
Core EnterpriseServices
Authoritative Data

INTEL
METOC
SENSOR
SYSTEM STATUS
TRACK DB
GEOREF
Target Lists
User Led Groups
22
Modular Net-Centric Capability
Semantic Filter Semantic Products from User
Groups
23
COI User Led Group
24
Potential IC2S Scope (1)

• IC2S has a lot of requirements in its bucket
• Omnibus project, with sub-projects and role to
  co-ordinate C2 IS projects and initiatives
  proposed not approved (notes capture content of
  omnibus project)
• Propose breakup of IC2S, including rename, into
  smaller , better defined projects
• Requires good portfolio management and
  co-ordination of C2 and CIS projects and
  initiatives (enterprise wide)
• Architecture
• Processes
• Doctrine
• Concepts
• Testing
• requirements

25
Potential IC2S Scope (2)

• Implementing initial security solution
  Multi-caveat, possibly Multi-level (addresses
  Integrated CIS area)
• Foundation for other C2 priorities
• As an example, required for Integrated COP
• Ref need for CEO tracks on COP (CANUS based)
• CANCOM need for OGD interaction
• Note that US key to MNIS is to Develop a
  multi-level secure information environment that
  will allow coalition partners, on demand, to
  access the right information on a need to know
  basis
• Integrated Information baseline with Improved
  COP/SA (addresses Joint Situational Awareness and
  Joint Planning)
• Incorporating user defined pictures for
  functional areas (ROSP, CIS etc)
• Incorporating SPOC access to decision support,
  planning information and readiness management
• Use of existing Portal solutions

26
COA 1-MLS/MCSOur Utopia MLS/MCS Requirements

• same as everyone else
• a single multi level/caveat system that users
  access through a single user interface
• capable of being trusted to properly handle,
  process, store and control access to information
  iaw security policies across the full range of
  user clearance and information classification
  levels (all the way from TS to unclass) and
  across the full range of user and information
  compartmentalisation privileges/restrictions
• However the existing situation is a
  conglomeration of multiple separate networks

27
COA 1-MLS/MCSOur Practical MLS/MCS Requirements

• the ability to display at least two domains (S
  and U ) on the same workstation
• With the ability to need to move data back and
  forth iaw rights and privileges and security
  policy
• able to view multiple domain, and manipulate them
  in their own windows

28
Existing Networks in Question (COA 1-MLS/MCS))
...plus a handful of others not shown
29
COA 1-MLS/MCSSome Directed IC2S Characteristics

• operate at the secret level
• support separate caveats
• seamlessly retrieve info from lower levels
• interchange info with higher levels ltltless
  seamlesslygtgt
• be fully interoperable with Allies
  ltltpredominantly at a classified levelgtgt
• be interconnected with OGD (Other Government
  Department, means Canadian) partners
  ltltpredominantly at an unclass levelgtgt
• be based on a common user workstation

30
COA 1-MLS/MCSMCS Starting Point

• US Navy Cross Domain Solution
• CENTRIXS-M provides secure tactical and
  operational information sharing between U.S. and
  coalition maritime partners
• CENTRIXS-M forms the network backbone and global
  infrastructure for Coalition and Multinational
  C4I interoperability A key enabler to Maritime
  Domain Awareness
• CENTRIXS-M provides core data services including
  Secure E-Mail, Web Replication, Chat, and COP at
  the Secret-Releasable Level new services
  include Chat translation, Automated patching and
  Computer Network Defense
• The addition of multilevel thin clients (MLTC) to
  the CENTRIXS-M architecture significantly
  improves ability to share information
  simultaneously with partners in the global war on
  terror, and it was fielded with relatively little
  expense. MLTC allows Sailors to access several
  enclaves from the same terminal, reducing the
  number of workstations required onboard and the
  expense to maintain them..
• This COA would also include the CIS
  infrastructure, people, process and technology
  changes necessary for this new direction (to
  provide availability and service required to the
  users)

31
COA 2-COP/SACommon Operational Picture as a Base
Near Real Time Air Data
Near Real Time Ground Maritime Data
Near Real Time Threat/Warning Data
Naval Component Commander Ground Component
Commander
Tactical Data Links
Supporting Data Bases
Supporting Tools
Air Route Structure Airspace Mgmt.
Info Waterspace Mmgmt Data Collection
Management Environmental Data
Intel / Facilities (MIDB) Imagery (IPL) Targets
32
COA 2-COP/SA The Vision Integrated Information
Baseline Access to Integrated Information From
A Single Window
Information Integration is Our Future!!!
33
Other COAs

• Note that operational planning, linked to
  original Decision Support requirement, is being
  pursued by COPS project
• Remove operational planning from consideration by
  IC2S
• Decision Support also included managed readiness
• Is this part of Joint SA/Joint Planning COA
• Other efforts
• JIIFC Det deficiencies parallel many of the
  requirement areas identified in 23 thrusts
• The phase 2 Tiger team manages implementation of
  solutions to some of the original identified
  deficiencies/requirements
• DIMEI addressing evergreening
• DGIMST addressing service transformation
• Where is work best addressed?

34
Section 2
35
Contents(3)

• Development of requirements
• Risks
• Questions on preceding

36
Development of IC2 Requirements
OverviewShowing Flow to IC2 Projects and
Initiatives Such as IC2S (DOORS extracts to be
provided)
Project
CFD CM
Joint IC2 CFD
Joint IC2 CFD
37
Risks

• Lack of co-ordinated approach increases
  difficulty of integration
• Matrix initiatives
• Projects
• Functional groups
• Processes and concepts
• Procurement
• Timeline
• Lack of procurement resources
• Planning timeline
• If defined scope is far from existing plans
  then planning time will increase
• US and Allied direction
• Change in operational priorities

38
Section 3
39
Backup
40
Requirements background
41
IC2S Deficiencies (1)

• Limited ability to exercise effective (CF)
  Command and Control (C2) within an integrated
  environment in contribution to a Team Canada
  response to a situation.  
• Limited ability to adapt rapidly to new missions
  and situations. Limited common efficient and
  effective planning capabilities.
• Limited ability to generate common situational
  awareness across a group.
• Limited ability to determine the quality
  (timely, source, production) of information.
• Limited ability to determine existence of useful
  information to satisfy business or functional
  needs.
• Limited capability to access, share and use
  relevant data info and services as defined by
  commanders, decision makers and staff, to
  exercise C2.

42
IC2S Deficiencies (2)

• Limited ability to ensure the availability of the
  CF C2 capability, which includes access to data,
  information and services.
• Limited capability to establish relationships
  among interagency, multi-national and public
  bodies.
• Limited ability to conduct C2 while maintaining
  confidentiality and integrity
• Across Security Levels
• Across Caveats
• Across organizations
• Across Systems (Tech)
• Across Functional Areas (ISR, Ops, C2, Log)
• Across Cultures (Need to know vs. Share) 

43
IC2S Deficiencies (3)

• Limited ability to manage information assets
  throughout their life-cycle.
• Limited ability to develop C2 capabilities (eg.
  policies and doctrine) in a transformational
  environment.
• Lack of common understanding among Team Canada
  members of command Control concepts among all
  users of CFCS.
• Limited ability to manage a CF C2 capability as
  a capability (e.g. FASM, LCAM, LCMM).
• Inability to support evolving CF C2
  capabilities.
• Limited ability for continuous improvement of C2
  effectiveness in terms of timeliness, quality and
  accuracy.

44
Commanders C2 Requirements

• Strategic and Operational level
• Strategic and operational level C2
• Expand current C2 IS footprint
• User Definable Integrated Common Operating
  Picture(s)
• Integrated Support (One Stop Help) System
• Interoperability with the US Forces
• Seamless information flow across all levels of
  command in both domestic and international
• Archiving and Business Availability 24/7/365
• Interconnect to Multinational entities
• Multi-level security and Canadian Eyes Only
  capabilities
• Fusion and Decision Support capabilities
• Integrated Readiness through corporate
  interconnect (with SERP)
• Interconnect to Interagency and Public entities
  (dropped due to cost ceiling)

45
IC2S Project Issue

• Scope too large for funding envelope
• Included everything but the kitchen sink all
  things to all people
• Lack of decision resulting in stalemate
• Other initiatives, such as those from JIIFC Det,
  have sprung up to solve the pressing operational
  problems identified for IC2S solution
• Un-coordinated initiatives increase difficulty of
  C2 integration
• IC2S should be assigned a smaller scope, based on
  priority

46
Refined IC2S Objectives

• Establish C2 Capabilities on a single Secret CEO
  Network based on one common baseline/core system.
• Target one Trusted Work Station for C2 in the
  JIMP environment to provide one COP, messaging,
  email and collaboration (Chat, etc) and Decision
  Support.
• Establish a methodology that allows full
  exploitation of the cores inherent capabilities.
• Provide improved service delivery through ITIL
  practices and tools.
• Provide Standards for environmental tactical
  systems.
• Promote the introduction of a Capability
  Management Framework (CMF) to support C2
  Capabilities.

47
IC2 Issue

• Span the strategic, operational and tactical
  levels of command
• The IC2S interpretation of this is one where a
  free flow of information is enabled between all
  levels of command
• This requires definition of Information Exchange
  standards to enable unimpeded flows of
  information to meet the needs of all levels of
  command
• This requires co-ordination of tools and
  applications to ensure that an interoperability
  burden is not placed on the flow of information
  through the use of a tool or application at one
  of the levels of command.

48
IC2S Enablers

• Through the work of IC2S over the past 2.5 years
  these enablers have been identified as critical
• Enterprise Architecture for the SECRET Domain
• Target Architecture for C2 Integration
• Doctrine and Concepts Initiative
• SECRET Domain Service transformation
• Infrastructure rationalization
• Information exchange data models
• Test and development capability (both functional
  and technical)
• Program or managed approach to migrating to
  integrated C2 system

49
Capability Management Framework

• There is a need for an overall capability
  management framework to coordinate C4 ISR and
  mitigate integration risks.
• That capability must re-capitalize the existing
  network, migrate to new SA capabilities (GCCS),
  expand the footprint to regional HQ, provide
  support (ITSM) and deliver business
  continuity/archiving
• The Capability Management Framework should
  provide for
• Functional exploitation of capabilities
• Integrated Training capability
• In Service Support
• Examples of Specific C2 CM tasks
• Co-ordinate C2 classified support system through
  ITSM project
• Co-ordinate delivery of new messaging capability
  through IM Gp
• Leverage of DISB delivered portal capabilities
• Co-ordinate integration of sensors delivered by
  other projects eg AGS, CBRN

50
Proposed Major Thrusts

• Cycle 1 Support CF Transformation/ Stabilize 
• Cycle 2 Expand Command Control Capability 
• Cycle 3 Harden and Enhance

51
CFCS II Project Cycle 1 Support CF
Transformation/Stabilize

• Introduce capability management framework
• Desktop integration (in garrison)
• Server migration to common H/W and S/W suites,
  and increase ITI at regional Ops HQ
• Inter-agency ops (Olympic Focused)
• Public ops (Olympic Focused)
• Basic business recovery and basic data recovery
  (not security enabled)
• Tactical/Joint Operational Interconnectivity
• Deployed Fixed-base CF C2IS Capability
• Rationalization of classified support system
• Introduce decision support capabilities

52
CFCS II Project Cycle 2 Grow C2 Capability

• Complete desktop integration
• Integration of new capabilities from existing
  tool suites
• Caveat separation within the garrison domain
• Corporate interconnect capability
• Complete server integration
• Interagency ops
• Multinational ops
• Public ops
• Introduce decision support capabilities

53
CFCS II Project Cycle 3 Harden Enhance

• Caveat separation
• C2 business continuity in a hostile environment
• Introduce decision support capabilities
• Rapid deployed-mobile capability
• Multi-level security capability
• Archiving capability
• Corporate interconnect capability

54
Stakeholder Feedback

• Navy (DGMEPM/DMRS) Comments
• Supports requirement for CFCS II project and
  integration of environmental systems at strat/op
  level
• Allies are going down the same path nationally
• Navy will not build MCOIN 3
• There are specific tools that need to remain
  environmental responsibility
• DFPPC (Terry Melnyk)
• Supports direction of CFCS II project Tiger Team
• Project Thrusts too ambitious for 90M, consider
  De-scoping
• Other option - sub projects for each thrust
• Third option - Consider matrix working groups for
  each thrust

55
Stakeholder Feedback

• Air Force (DGAEPM) Comments
• Supports CFCS II project scope and overall aim
  (integration and Cap Management framework)
• Security Architecture will be addressed by CFCS
  II but delivered by ESE
• One C2IS Tech will maintain all functions for
  army, navy, airforce
• Business Recovery looks like ITSM ballpark
• Decision Support is an overarching construct,
  IMRS is underneath
• LCAM unique environmental Apps belong to the
  environments
• Go with Best of Breed for common Apps
• Need a CEO backbone

56
Stakeholder Feedback

• Army (DLCI/DGLEPM) Comments
• Agree on the long term CFCS II plan, need to
  agree on priority (of Thrusts)
• Need to address the Data model issue up front and
  look towards convergence of data models in
  2011/12 with C2IEDM model and JC2
• Cant support a field domain and a garrison
  domain of tools, need to use same tools in both
• Desktop integration, like DWAN, but with a
  governance structure
• Skill fade a problem, need training, centre of
  excellence, SOPs, rules on info management
• Priority must be Joint (internal to CF) and then
  Team Canada, not allies.

57
Stakeholder Feedback

• Transition Team (Capt(N) Bertrand)
• Supports requirement for CFCS II project
• Need to sort out the vision (commanders at all
  levels?)
• Need to consider Lead Nation Role
• Cap Manager ? Will be answered once force
  generation is decided, but will not be CANCOM,
  CEFCOM or SJS.
• CANCOM, CEFCOM, SOG will be our clients,
  Governance structure may take until Cycle 2 to be
  decided when restructuring is completed.
• CFIOG (Col Turnbull)
• Supports requirement for CFCS II project
• Focus on improving services and service delivery
• Recognizes that additional capital investment is
  required to improve ITI.

58
The envisioned endstate for IC2S is an omnibus
project to which all C2 projects are subordinate
even if sponsored by other groups. This would
provide an overall co-ordinated plan for C2 ISs.

59
Commanders Deliverables

• Ability to operate at the Strategic and Operation
  level, and to receive and pass information to
  tactical levels
• Develop common SOPs and policies
• Expand C2IS footprint
• Robust System available 24/7/365
• Bandwidth (identify and fix bottlenecks)
• access to data (server redundancy, data location,
  access points, data currency, archiving
  capability)
• No single point of failure
• Remote Access
• Access to support and support action 24/7/365
• Supportable/Maintainable
• Single C2 technician (vice MCOIN, AFCCIS, CFCS)
  responsible for all C2 systems
• Remote software maintenance capability
• Battle lab for rapid development
• Address change management procedures and issues
• Integral training capability (training releases)
• Only training facility currently at NDHQ for
  deployments
• Need operator, maintainer, and refresher training
  (continual training)
• Common help desk structure one stop shopping
  for inservice
• Simple Effective Interface to the user that masks
  complexity

60
Commanders Deliverables

• Secure system
• Canadian Eyes Only capability (caveat separation)
• Ability to operate with joint, interagency,
  multinational and public partners (ability to
  create communities of interest as required)
• Develop policies and agreements with Agencies,
  GOC departments, and allies
• Priority (Army) 1) Joint, 2) OGD (team Canada),
  3) Allies, 4) Public Agencies
• MLS capability
• Cross domain sharing of information
• Guards and crypto solutions
• User Authentication
• PKI, Role based
• User definable Integrated Operating Picture(s)
• Picture for SJS, CANADACOM, CEFCOM all required
  different information and different levels of
  information
• With ability to display data from various
  corporate sources as required (MASIS, FMAS,
  ITMIS, etc)
• Integration of the common data model (C2IEDM
  migrating to JC3IEDM)
• Provide red, blue, and neutral track information
• Provide ability to drill down to different levels
  of mission data (including Interagency and
  Multinational operations
• Provide maps and weather overlays
• Develop CONOPS for data stewardship of
  information displayed in the operating pictures
• Incident Management System (NBCD, information
  pertaining to an event)

61
Commanders Deliverables

• Fusion and Decision Support capabilities
• Links to corporate systems to provide information
  (MASIS, FMAS, ITMIS, IMRS, PeopleSoft, etc)
• Automated force employment and planning
• Ability to link with force generation
• Ability to link with force sustainment
• Operational planning tools
• Provide ability to modify plans collaboratively
• Provide ability to rapidly adapt to new missions
  and situations
• Readiness management tools
• Logistic support planning
• Collaborative tools
• Evaluate force structure alternatives
• Intel
• Capability to integrate information from sensors
  at all levels (provide standards)
• NBCD sensors
• Tactical sensors/UAVs
• Imagery (CAESAR/MAGIIC/AGS)
• SIGINT
• Space based sensors

62
Option 4 IC2S Project (Omnibus)
Common Resources for CM
PWGSC (3)
PD
Proposed Interim CM
63
Example of Operational/Functional Requirements
to TechnicalTime Sensitive Targeting (COI)
example
Guides service Development
Establishes Integration Environment
Operational construct For testing assessment
Vignette
Find, Fix, Track, Target, Engage, Assess
FIX
ENGAGE
FIND
WHAT
Vignette (def by COI)
TARGET
ASSESS
TRACK
Functional Services (OA/CM def)
HOW
Core Enterprise Services (IM/EAS)
Enterprise Service Management (ESM), Messaging,
Discovery , Collaboration , Application,
Mediation (includes Fusion), Storage, Information
Assurance (IA) / Security , User Assistance
CES
Infrastructure Services (IM/DGIMT))
Terrestrial comms, bandwidth, Routing, IP
addressing, Bandwidth Mgmt, Satellite Comms
CNET
64
Scope of IC2S (1)
   
65
Scope of IC2S (2)
66
Scope of IC2S (3)
67
Scope of IC2S (4)
68
Scope of IC2S (5)