Welcome to the

1

• Welcome to the
• CCEB Introductory Brief

2
CCEB Strategic Intent

• To enhance C4 interoperability and capability for
  the defence forces of its member nations and to
  provide leadership and influence across the wider
  C4 community

3

• To achieve its purpose the CCEB will, through a
  jargon-free approach
• Be user focused
• Collaborate and build trust amongst key
  stakeholders
• Focus on Interoperability, sharing experience and
  knowledge
• Share national level purposes, including
  experiences to the benefit of other CCEB nations,
  this will include data and lessons learned
• Define internal benefits to the CCEB and how the
  CCEB can influence final output
• Consider strategic, operational and tactical C4
  requirements with direct access to secure,
  accurate information for planning and decision
  making
• Carefully plan, prioritise and allocate available
  resources to meet tasks
• Review outcomes to assess value added
• Raise awareness of CCEB activities

4
CCEB Lines of Effort
5
CCEB GOALS STRATEGIES
6
(No Transcript)
7
CCEB Organization
8
Personnel
as at August 2008
PRINCIPAL
EXECUTIVE GROUP
WASHINGTON STAFF
RADM Peter Jones
Mr. Ewart Challis
LTCOL Sheldon Kidd

MGen Glynne Hines
MAJ Shawn MacArthur
Mr Bill Brittain
Mr Peter Thomas
SQNLDR Paul Drysdale
LTCOL Noel Rings
CAPT Guy Brocklebank (Chair)
AVM Carl Dixon (Chair)
Wg Cdr Tim Neal-Hopes
LTCOL Steve Tucker (Chair)
BG Michael Basla
CAPT John Dziminowicz
Lt Cdr, RN John Stott
9
Relationships with other Organisations
NATO
CFBL Net
CWID
MNE
NC3B
ACP WG
MIC
ACT
MIP
NOS WG
MNLOE
DSWG
MWAN TF
NET MIWG
MIT
CPO (G5E)
CCEB
ACP Users 110
Security WG
IAWG
ICCWG
FPDA
MULTI-FORA
CCIB
MSAB
ABCA
ASIC
A-Z NC4
TTCP
QLF
10
www.jcs.mil/j6/cceb/acps
11
Common Definitions

• National Domain - for example SIPRNET
• Internal sharing of information using the
  nationally provided and managed network
  infrastructure, applications and services.
• Allied Domain - for example Griffin
• Bilateral or MN domains permanently
  interconnecting national domains.
• Do not need a specific coalition operation to be
  formed
• Enable a permanent and protected environment for
  the sharing of classified or sensitive
  information.
• Coalition Domain - for example CENTRIXS
• Use (often stand-alone) networks and applications
  between coalition partners.
• A separate domain may be created for each
  operation or for a specific purpose.

12
Common Definitions contd

• Tier 1 Capabilities
• Those with Boundary Protection Services (Guards)
  for each application
• Interconnected national systems/domains via
  nationally controlled and accredited guards
• Tier 2 Capabilities
• Do not require Boundary Protection Services
• Not connected to national systems/domains
• Require additional separate infrastructure
  (terminals/workstations etc)

13
Griffin

• Tier 1 networking initiative
• Griffin is the name given to the framework that
  enables the exchange of information between
  classified national domains of participating
  nations.
• Griffin provides users with a permanent, managed
  and resourced capability that enables the
  exchange of up to and including Secret
  information.
• Services on Griffin currently limited to email
  plus attachments (specified list only) and basic
  web services

14
CDAWG

• CDAWG Focus will be on
• the adoption of an Architectural Approach to the
  development of future C4 capabilities
• Development of a consolidated Multi-National
  Capability Development Plan (based on national
  plans)
• Focussed Capability Development Teams will
  develop plans for the national delivery of
  capability, based on detailed user requirements

15
Griffin Architecture

• As-Is and To-Be architecture views are being
  developed that will
• Contain high level Operational, System and
  Technical views that documents the agreed
  multi-national solution or implementation
• Detailed lower level views will be maintained by
  individual nations (national implementation)
• Capability Development Teams will be responsible
  for developing the lower level views and feeding
  back that back into the As-Is architecture view
  set

BACK
16
CCEB Capability Development

• The Multi-national Capability Development Plan
  will
• Reflect individual national development and
  implementation plans
• Identify National milestones, resources,
  timelines, and high level requirements
• Enable alignment of national programs to deliver
  capabilities
• Capability development activities need not
  require all five nations to implement agreed
  solutions
• Three phase model for the development of C4
  capabilities
• Capability Initiation
• Capability Development
• Capability Implementation

17
Capability Initiation
User High Level User Requirement defined
EG - Direction to CDAWG develop a C4 capability

• CDAWG Relevant SME Refines Capability
  Definition
• Detailed Capability definition based on High
  Level User Requirements
• Evaluates CCEB Resources reqd for Capability
  Definition phase to define implementation
  options
• Skills sets, milestones, etc
• Identifies High level timelines for delivery
• Develops High Level AS-IS and TO-BE
  Architectural views

Capability Initiation Phase
EG - Endorse proposal for development of
implementation options
DP
Capability Definition Phase
18
Capability Development
Capability Definition Phase
CDAWG or Tiger Team - Scope the art of the
possible to develop implementation options
Capability Development Phase

• CDAWG validate implementation strategies
• against User Requirement/MCDP/architecture
• Rank strategies for EG endorsement

DP
EG endorse Preferred Implementation Strategy
CDAWG Refines Implementation Plan for
Capability Development Team User Acceptance
criteria
Tiger Team - Develops Multi-national agreed
solution, Capability Delivery Plan, cost and
resources estimates, schedules and milestones
DP
CCEB Principals Approval to implement agreed
solution
Capability Implementation Phase
19
Capability Delivery
Capability Implementation Phase
DP
CCEB Principals Approval
Nations Implement/Build against Agreed Solution
Requirements
Capability Delivery Phase
CDWG Coordinate User acceptance
DP
User Acceptance of delivered capability
CPO (GSM) Manage and Maintain
BACK
20
GSM

• Coalition Program Office (CPO) focus was on the
  development of capability as well as in service
  management of Griffin services through its close
  association with the CWAN WG
• Griffin in Service Management GSM WG has been
  stood up to provide
• In-Service Management of Griffin Services and
  Infrastructure,
• Commissioning of new services, and
• Development of In-service Mgmt Tools

21
SWG

• Following publication of STF report EG changed
  the name of the FPWG to Spectrum WG to reflect a
  wider responsibility for issues and policies
  relating to the management of not just frequency
  but spectrum in the coalition environment.
• STF have produced a first draft campaign plan
  for EG approval that proritises the
  recommendations from the STF report.
• EG have directed that STF concentrate on the
  following areas in priority order
• Implement a Common Data Exchange Format
• Develop a Coalition Spectrum Architecture
• Spectrum Management for Operations and
• Acquisition Process.

22
CCEB Meeting Schedule
23
Perm-Sec contact details john-stott_at_js.pentagon.m
il CCEB Public web-site www.jcs.mil/j6/cceb