Joint C2 Integrated Architectures Providing Operational Context Strategy - PowerPoint PPT Presentation

1 / 42
About This Presentation
Title:

Joint C2 Integrated Architectures Providing Operational Context Strategy

Description:

Joint C2 Integrated Architectures Providing Operational Context Strategy – PowerPoint PPT presentation

Number of Views:207
Avg rating:3.0/5.0
Slides: 43
Provided by: edwin68
Category:

less

Transcript and Presenter's Notes

Title: Joint C2 Integrated Architectures Providing Operational Context Strategy


1
Joint C2 Integrated Architectures Providing
Operational Context Strategy Execution
Unclassified
June 2007
Ken Williams J89 Integrated Architectures
Systems Engineering Division 757-836-9784 kenneth
.williams_at_jfcom.mil
Unclassified
2
OVERVIEW
  • JFCOMs architectural responsibilities
  • Need for underlying re-usable authorative data
  • Operational relevance of architectures
  • Architectures must answer five questions for
    the Operational Commander
  • JTF Core Architectures
  • Systems interoperability - Problem and Solution
  • JC2 Portfolio Management Overview

3
USJFCOM Responsibilities for Joint Integrated
Architecture
  • USJFCOMwill lead the development of joint
    warfighting, C2 capabilities, architectures, and
    operational concepts.
  • --DOD Directive 5100.30 05 Jan 2006
  • In coordination with the Chairman, leading the
    development of joint doctrine, concepts,
    requirements, and integrated architectures for
    joint command and control to ensure integration
    and interoperability from the tactical level
    through the interface with the global level.
  • --Unified Command Plan 2006, 05 May 2006
  • The Joint Capability and Integration Development
    System (JCIDS) methodology requires a
    collaborative process that utilizes joint
    concepts and integrated architectures to identify
    prioritized capability gaps and integrated
    DOTMLPF solutions (materiel and nonmateriel) to
    resolve those gaps.
  • --CJCSI 3170.01E, 11 May 05

4
Increasing Requirements for JTFHQ
25 20 15 10 5
24
24
19
19
16
Number of JTF Headquarters
11
10
10
7
6
5
2
1
1
2000
2001
2002
2003
5
The Nature of Todays Problem
  • JTF Headquarters do not receive key joint
    expertise until after initial planning is
    completed
  • Full complement of joint expertise arrives after
    execution
  • (or not at all)

JTF Capability
Execute Order (EXORD)
Conducting Operations
Alert Order (ALERTORD)
Warning Order (WARNORD)
Time
6
Reduced Time to Full Capability
Legacy JTF Headquarters Stand-up
JTF Capability
Execute Order (EXORD)
Conducting Operations
Alert Order (ALERTORD)
Warning Order (WARNORD)
Time
JTF HQ templates and data are enablers that
reduce time to reach full JTF HQ capability
UNCLASSIFIED
7
Five Critical Architectural Questions
A useful Architecture provides a Commander
answers in five critical areas
  1. What is my mission ?
  2. How am I task organized to support the mission ?
    (to include JMD billets necessary for
    Supported/Supporting Commands)
  3. Who do I have to communicate with ?
  4. What equipment do I have ?
    (how much
    and how is it normally employed)
  5. Who needs training ?

8
Integrated Architecture Methodology of Building
DoDAF Relationships
3
5
9
1
10
2
4
7
3
8
6
11
9
DoDAF Products Being Produced
OASD(NII)Architecture Developmentand Analysis
Survey1 Nov 05
10
Integrated Architecture Mapping
Harnessing the complexity of a Joint Enterprise
that encompasses Service Enterprise,
Multinational and Interagency requirements
Integrated View (IV) Must be capable of
demonstrating how one area is effected/ mapped to
each of its parts based on authorative data
sources.
Boards, Bureaus, Centers, Cells, Offices, and
Elements
11
Integrated Architecture products support MOPs/MOEs
Information Needs
Information Needs
Information Needs
Information Needs

Precepts

Precepts
AV
-
1
AV
-
1
AV
-
1
AV
-
1

Nodes, Needlines Activities

Nodes, Needlines Activities

Organizational Relationships

Organizational Relationships
OV
-
5
OV
-
2
OV
-
4
OV
-
5
OV
-
2
OV
-
4

Systems Information Exchanges

Systems Information Exchanges
OV
-
5
OV
-
2
OV
-
4
OV
-
5
OV
-
2
OV
-
4

Activities Process Flow

Activities Process Flow

Data Flows

Data Flows
SV
-
4
SV
-
4
SV
-
5
SV
-
5
SV
-
6
SV
-
6
SV
-
4
SV
-
4
SV
-
5
SV
-
5
SV
-
6
SV
-
6

Capability to Systems Trace

Capability to Systems Trace
Information Timeliness
Information Timeliness
Information Timeliness
Information Timeliness

Required Systems Information Exchanges

Required Systems Information Exchanges

Performance Attributes

Performance Attributes
gt
Periodicity
Availability
gt
Periodicity
Availability
gt
gt
SV
-
5
OV
-
6c
SV
-
6
SV
-
5
OV
-
6c
SV
-
6
SV
-
5
OV
-
6c
SV
-
6
SV
-
5
OV
-
6c
SV
-
6
gt
Timeliness
Throughput
gt
Timeliness
Throughput
gt
gt

Time Ordered Nodal Information Exchanges

Time Ordered Nodal Information Exchanges

Capability to Systems Correlation to Meet

Capability to Systems Correlation to Meet
Timeliness Requirements
Timeliness Requirements
Information Assurance
Information Assurance
Information Assurance
Information Assurance

Required Systems Information Exchanges

Required Systems Information Exchanges

Performance Attributes

Performance Attributes
Accuracy
Accuracy
gt
gt
Information Criticality
gt
gt
Information Criticality
SV
-
4
SV
-
4
OV
-
5
OV
-
5
OV
-
5
SV
-
4
OV
-
5
SV
-
4
gt
Availability
Integrity
gt
Availability
Integrity
gt
gt

Data Flows/Formats

Data Flows/Formats

Information Sequencing

Information Sequencing
SV
-
6
SV
-
5
SV
-
6
SV
-
5
Architectures must undergo an assessment process
SV
-
6
SV
-
5
SV
-
6
SV
-
5

Capability to Systems Correlation to Meet

Capability to Systems Correlation to Meet
Information Assurance Requirements
Information Assurance Requirements

Node
Connectivities
and Information Needs

Node
Connectivities
and Information Needs

Capability to Systems Correlation

Capability to Systems Correlation

Mapping to NCOW Activities Model

Mapping to NCOW Activities Model

Data Flows/Formats

Data Flows/Formats

Technical Standards Required to Implement

Technical Standards Required to Implement
Capability
Capability

Information Sequencing

Information Sequencing

SV
-
TV Bridge

SV
-
TV Bridge
12
(No Transcript)
13
Desktop Analysis/Assessment feeds DoD Process
Desktop Analysis
Feedback and follow-up analysis as needed
4a. DOT_LPF analysis (FSA)
4d. JC2 BoD endorse-ment of proposed solution
ID purpose and scope of assessment
ID analysis and JTA objectives
ID JCF and focus areas
2. JCF development validation (FAA)
5. Prepare staff DCRs / ICDs or CDD mods
1. Baseline capability information
3. Analyze JCF for gaps and shortfalls (FNA)
4b. SoSE analysis (FSA)
If new capabilities required
5a. Impact, affordability exe-cutability
analysis
4c. JTA (AMA)
3a. Prepare JCD
JCIDS approval of JCD
Assessment and Planning
Execution
FAA Functional Area Analysis FNA Functional
Needs Analysis FSA Functional Solution
Analysis AMA Analysis of Material Approaches
9a. Solutions development and implementation
7a. JCIDS approval
10. Final reviews by C2CIB and DAWG
6. C2CIB endorse-ment
11. Fielding
8. Funding (PPBE)
9b. Solutions integration
7b. C2CIB or DAWG approval
9c. Solutions TE
14
JTF Core Architectures Incremental Development
Functional Component Commanders (FCCs)
(Increment II)
  • JTF HQ Core Architectures Increment I
  • JTF HQ Core Architecture - Version 1
    Completed Signed Jul 05
  • JTF C2 Baseline Templates Architectures
  • Major Combat Operations (MCO) v1.0
    Completed Signed Mar 06
  • Humanitarian Assistance/Disaster Response
    (HA/DR) (OCONUS) and
  • DSCA for Disaster Relief (CONUS) v1.0 Draft
    Completed Jun 06
  • Stability Operations Completed Jan 07

Interagency Multinational (Increment III)
Increment I Notional, scaleable, tailorable JTF
HQ architecture, including 18K activities, traced
to overarching requirements, linked to equipment,
manning, and training needs for
certification Increment II Service-developed
Joint Forces Land Component Commander (JFLCC),
Joint Forces Air Component Commander (JFACC),
Joint Forces Maritime Component Commander
(JFMCC), Joint Special Operations Task Force
(JSOTF), and Joint PsyOps Task Force
(JPOTF) Increment III Multinational and
Interagency Modules will be developed, with COCOM
Support Target Date for Completion December
2008
15
Template Joint Task Force Headquarters
Billets
Tasks
Systems and Applications
16
JTF J3 Joint Operations Center Integrated View
17
JTF J-3 Air Operations Cell
Capabilities that Must be Included In
Service-Oriented Architectures (SOAs)
Billets Tasks Systems and Applications
CENTRIXS
JTF J-3 JOC Air Operations
Cell - JTF03302
PC Desk Top
PC Desk Top
Standard Applications
GCCS-J Global Command and Control System - Joint
MS Office
NT Toolbox
TBMCS Theater Battle Management Core Systems
Anti-Virus Software
Adobe Acrobat Reader
(PFPS)/ Falcon View
Portable Flight Planning Software
Classify for Outlook
C2PC Client Command and Control Personal Computer
Zip File Compression
ADOCS Automated Deep Opns Coordination System
Collaborative Tools
AMHS Automated Message Handling System
CD Creator
18
How JTF Architectures Are Being Used
C2 Capabilities Assessment
JTF Improvement
How Do New/Changed Capabilities Fit In?
  • Capability Portfolio
  • Management
  • Capability Integration
  • Gap Overlap Analysis
  • Dependencies
  • Redundancies
  • JTF As A Weapons System
  • Rapid, Efficient, Effective
  • Organizing
  • Equipping
  • Training
  • Certification

Common Data
Reusable Components
Common Methodology
Must be (1) Simple to use (2) based on
authorative data (3) reliable (4) operationally
relevant
It is All About How Enriched Data/Data
Relationships Can Improve Interoperability
19
Strategic to Tactical Integrated View Draft
Version 1.0
26 Feb 2007
THEATER COCOM
NATIONAL (INTEL)
COALITION
INTEL
C2
INTEL
C2
DOD/ SERVICES/ AGENCIES
CIA
JIC/JAC
JOC
NSA
DGS 1/2/3/4/5
DIA
NGA
RSOC(s)
IBS
GBS
TADIL LINKS
CDL/ABIT
LOS- RF Radio Nets
BLOS (SATCOM/HF)
MCO/HA/DR/SR
JTF-
CJTF
JFLCC
CFMCC
JSOTF
CFACC
INTEL
C2
INTEL
C2
INTEL
C2
INTEL
C2
INTEL
C2
CJTF JOC
JISE
JOC
JISE
CVIC
MOCC
JISE
NIST
JOC
AIS
JAOC/ AOC
CJTF JCCC
CJTF JLSC
Command Control Nodes
JLFCC
JTF HQ
JFMCC
JACC
JSOTF
IBS
IBS
GBS
GBS
TADIL LINKS
TADIL LINKS
CDL/ABIT
CDL
LOS- RF Radio Nets
LOS- RF Radio Nets
BLOS (SATCOM/HF)
BLOS (SATCOM/HF)
1 MEF Organization
101st Organization
1st CAV Organization
1st Mar Div Organization
MQ-1 Predator w/HELLFIRE)
FIXED WING
ROTORY WING
INTEL
C2
  • MH-60L (SOF)
  • MH-47D/E (SOF)
  • AH-6J (SOF)
  • F-14
  • AV-8
  • B-1
  • B-2
  • B-52

DIV TOC
ACE
CIC
DIV COC
DIV TOC
ACE
ROTORY WING
  • CH-46
  • CH-53
  • UH-1

1 IBCT TOC
S-2
1 IBCT BSA
1 BCT TOC
ACT
CIC
REG COC
BN TOC
BN S2
BN TOC
BN S2
ISR Assets
S2
BN COC
FIXED WING
Space Assets
41st ARNG Organization
STRYKER SBCT Organization
  • F-15
  • F-16
  • F-117
  • A-10

INTEL
C2
FIXED WING
SBCT TOC
ACT
NSFS
DIV TOC
ACE
  • DESTROYERS
  • FRIGATES
  • CRUISERS

BN TOC
BN S2
1 BCT TOC
ACT
Maritime
Ground
BN TOC
BN S2
FORCE Application
20
Division Headquarters Headquarters Battalion
207 Officers
Modular Division 8.0 Design as of 4 JAN 2007
DIV HQ
DIV HQ
41 Warrant Officers
625 Enlisted
1018
216/42/760
207/41/625/873
873 Total Soldiers
STB
S2/S3 SEC
CMD SEC
S1 SEC
CHAPLAIN
MAINT SEC
S4 SEC
Staff Section
1/1/10/12
1/0/1/2
1/1/1/3
1/1/4/6
5/0/6/11
2/0/2/4
PAGE 137
PAGE 133
PAGE 135
PAGE 158
C Company 18/7/173/198 (includes C Co HQ) 198
Person Co
A Company 125/11/127/263 (includes A Co HQ) 263
Person Co
B Company 48/20/170/ 238 (includes B Co HQ) 238
Person Co
MAIN MAINT SEC 0/0/47/ 47
TAC MAINT SEC 0/0/20/ 20
PAGE 148
PAGE 139
MAIN FEED SEC 0/0/15/ 15
TAC FEED SEC 0/0/6/ 6
Sections C4 (G6)
SECTIONS CMD GRP MCG LNOS CHIEF OF
STAFF Personal Staff PROTECT FIRES MANEUVER
PLANS
Sections Sustain (G1/4) Intel
MAIN MED TM 2/0/6/ 8
TAC MED TM 1/0/3/ 4
HQ NET DET 2/1/30/33
MAIN TRANS SEC 0/0/6/ 6
TAC TRANS SEC 0/0/11/11
Note Re-aligned company structure
PAGE 158
CP SPT DET 3/0/83/ 86
SENT RADAR 0/0/12/ 12
STB Staff 11/3/24//38
PAGE 119
PAGE 157
PAGE 159/160
21
Main and TAC organized by G-Staff (when
consolidated)
MAIN CP (includes TAC consolidation) 168/37/333/
538
(Slide 1 of 2)
CHIEF OF STAFF 2/0/1/3
Dotted line boxes reflect TAC elements
G1 5/1/22//28
G2 15/14/101//130
G3 64/10/78//152
G3 Main 49/8/58/115
G3 TAC 15/2/20/37
G2 Main 11/12/87//110
G2 TAC 4/2/14//20
G1 HQ 2/0/2/ 4
G2 2/0/1/3
ACE Chief 1/0/1/ 2
ISR G2 2/0/1/ 3
PAGE 45
G3 CUR OPS 4/0/4/8
CBRN 1/0/1/2
PAGE 65
PAGE 23
PAGE 95
PAGE 30
G1 CUR OP 1/0/1/ 2
FUSION 0/2/16/18
FUSION 1/1/4/ 6
PAGE 103
PAGE 46
PAGE 110
PAGE 75
PAGE 24
PAGE 97
EN OPS 3/1/3/7
AIRSPACE 2/1/7/10
AIRSPACE 0/1/1/2
ENG 2/0/2/4
PAGE 31
PAGE 66
HAC 0/1/3/4
G1 HR DIV 1/1/0/ 2
PAGE 47
PAGE 50
PAGE 104
PAGE 106
PAGE 25
PAGE 31
EN Prot Cell 1/0/1/2
AVN 2/0/2/ 4
PAGE 67
ISR TGT DEV 1/0/1/2
G1 OP/CAS 0/0/4/ 4
PAGE 105
PAGE 48
PAGE 76
PAGE 55
PAGE 26
PAGE 27
PAGE 96
GI S 0/1/8/9
FSE 5/2/9/16
FSC 3/0/3/6
PAGE 68
ISR DCGS-A (DTES) 0/1/4/5
PAGE 101
G1 EPS 0/0/4/ 4
PAGE 51
PAGE 41
SPACE 2/0/2/4
PMO 4/0/3/7
FAIO 0/2/0/2
PMO 1/0/2/3
PAGE 99
PAGE 28
PAGE 69
PAGE 28
COMM INTEG 0/2/9/ 11
ISR COMM INTEG 0/0/4/4
G1 PIM 0/0/3/ 3
PAGE 42
PAGE 53
PAGE 77
PAGE 109
EW 2/0/1/3
AMD 3/1/4/8
AMD 1/1/4/ 6
PR 3/0/2/5
PAGE 33
PAGE 98
PAGE 70
PAGE 32
USAF ISR
G1 PASR 1/0/6/ 7
HOC 0/1/3/4
PAGE 52
PAGE 43
PAGE 78
PAGE 111
FUOPS 5/0/2/7
PSYOP 1/0/1/2
USMC OPS
SJA 1/0/1/2
PAGE 71
PAGE 36
G2 X 1/1/4/6
CICA 0/1/3/4
G1 MWR 0/0/2/ 2
PAGE 54
PAGE 43
PAGE 107
TACP
PAGE 35
PAGE 72
PAGE 34
22
MCP/Movement and Maneuver Current Operations
Integrating Cell Headquarters Element
MAIN
Major Equipment MCS(x2) IP Phone
(x4) SCANNER PSC-5 GCCS-Laptop Iridium JTRS VRC-92
F(x2) 15 KW GEN C2PC 6 KW GEN BFT AN/VRC 104(V3)
  • Functions
  • Execute Tactical Operations
  • Execution Decision Making
  • Conduct Command Post Operations
  • Assess Tactical Situation and Operations
  • Conduct Update Briefings
  • Maintain Current Status of Forces
  • Receives/actions incoming messages, orders, RFIs,
    taskings
  • Informs G-5 on the current situation during MDMP
  • Coordinates actions of the Current Ops Cell with
    other functional and integrating cells.
  • Executes actions as assigned by the Chief of Staff

23
Modern Information Exchange
Operator
Operator
Operational
System
Display
Display
Host
Host
Decision- Quality Information
Decision- Quality Information
Information
Information
Data
Data
Data
Man to Machine Interface
Brain-to-Brain
The ability of systems, units or forces to
provide services to and accept services from
other systems, units, or forces and to use the
services so exchanged to enable them to operate
effectively together. Source Joint Pub 1-02
24
Interoperability Gaps
Aircraft and Ground Systems
Application Message Level
Network Data Link Level
Physical Signal Level
Physical/ Signal level
Application Message level
Network Link level
25
Interoperability Enhancement Process Case Study
  • Standards are not enough
  • L-16, VMF, MTS, AFAPD, etc
  • Translation standard
  • Limited to messages specified by MIL-STD-6020
  • Link 16 to VMF gateways translators are
    critical enablers.
  • Bit Level implementation
  • Multi-Service examples
  • CONOPS and TTPS effected

26
Standards Interoperability
J3.5I
J3.5I
J3.5I
J3.5I
J3.5E0
J3.5E0
J3.5E0
J3.5E0
J3.5C1
J3.5C1
J3.5C1
J3.5C1
J3.5C2
J3.5C2
J3.5C2
J3.5C2
J3.5C3
J3.5C3
J3.5C3
J3.5C3
27
Standards Interoperability
Actual Implementation
J3.5I
J3.5I
J3.5I
J3.5I
18 Elements
9 Elements
8 Elements
16 Elements
J3.5E0
J3.5E0
J3.5E0
J3.5E0
8 Elements
5 Elements
3 Elements
5 Elements
J3.5C1
J3.5C1
J3.5C1
J3.5C1
9 Elements
9 Elements
5 Elements
10 Elements
J3.5C2
J3.5C2
J3.5C2
J3.5C2
2 Elements
2 Elements
2 Elements
2 Elements
J3.5C3
J3.5C3
J3.5C3
J3.5C3
12 Elements
2 Elements
2 Elements
11 Elements
28
Joint Command and Control (JC2)Capability
Portfolio Management
June 2007
29
How we got here
  • These challenges
  • No designated, empowered Joint Advocate cradle
    to grave for joint capabilities
  • We organize, train and equip C2 at the Service
    level but fight at joint level
  • Lack of prioritization and balance across the
    entire joint capability area
  • Joint management activities not well
    defined/aligned with primary DoD processes
  • Unable to view joint C2 across the entire
    portfolio of contributing investments
  • Begat this approach
  • CPM capability-based planning and management
    efforts to better enable strategic choice and
    improve ability to make capability tradeoffs
  • Manage groups of like capabilities from across
    the enterprise to improve interoperability,
    minimize capability redundancies and gaps, and
    maximize capability effectiveness
  • Integrate requirements/capabilities, acquisition
    and programmatics - across DOTMLPF spectrum
  • Four capability areas selected as test cases
  • Joint Command and Control (JC2).Commander
    USJFCOM
  • Joint Net-Centric Operations (JNO)
    .ASD(NII)/Commander USSTRATCOM
  • Battlespace Awareness (BA) ....USD(I)
  • Joint Logistics (JL) )..USD(ATL)/Commande
    r USTRANSCOM

30
Capability Portfolio Management (CPM)
  • Focus on capability-based planning and management
    efforts to better enable strategic choice and
    improve ability to make capability tradeoffs
  • Manage groups of like capabilities from across
    the enterprise to improve interoperability,
    minimize capability redundancies and gaps, and
    maximize capability effectiveness
  • Integrate requirements/capabilities, acquisition
    and programmatics - across materiel and
    non-materiel (DOTMLPF)
  • Objectives
  • Balanced portfolio with optimum capability mix
  • Streamlined, collaborative integrated process
  • Framed choices for senior leader decision making
  • Unified resource-informed strategic portfolio
    direction
  • Ensure strategic direction is translated in
    budget process

C2 Capability Portfolio Manager (CPM) Commander
USJFCOM
31
JC2 Enterprise - Capability Mix
Joint C2
Employ Shared Situational Awareness and
Understanding
Communicate Commanders Intent Guidance
Operational Planning
Synchronize Execution Across All Domains
Leverage Mission Partners
Monitor Execution, Assess Effects Adapt
Operations
Establish/Adapt Command Structure Enable both
Global Regional Collaboration
Exercise Command Leadership
JC2 Enterprise
Establish/ Promulgate ROEs
Organize Staff to align w/ Mission
Incorporate Strategic Mission Guidance
Into Commanders Intent
Assess Compliance w/ CDRs Intent
Communicate MSN Objectives, Rationale,
intentions support/action
Access/Share Info on Adversary/ Neutral/ Non-comba
tants
Develop/ Analyze/ Select COAs
Enable Self- Synchronization of Subordinate Forces
Set Priorities Guidance Standards
Refine JTF Component Org Integrate Capabilities
Develop Joint/ Coalition Campaign Plan
Assess Achievement of Planned Effects
Access/Share Blue Force Situational Awareness
Coordinate w/MSN Partners to
Gain Actionable Commitment
Conduct Mission Analysis
Synch Operations w/MSN partners other agencies
Cultivate Relationships w/MSN Partners
Develop Plans Across Full ROMO
Refine Command Relationships
ID/Assess Implications of Unplanned Effects
Develop/ Promulgate Initial CDRs Intent/Guidance U
pdate as Reqd
Synch Execution Between/Across Phases
Establish/Identify Collaboration Mechanisms
Access/ Integrate Geospatial Info
Assess Plan Effectiveness Prepare for Execution
Adapt Operations To Changing Situations
Manage Risk
Reach-back for SME
Direct Action Through Mission Type Orders
Develop Strategy
Validate Targets
Determine Achievement of Desired
Objective, End-State, or Phase Points
Display tailored, Relevant SA info -UDOP-
Cohesive joint integration throughout DOTMLPF-P
32
JC2 CPM Mapping and Analysis
Policy
Standards
Policy
Networks
Standards
Capabilities (JCAs)
Applications
Policy
Systems Functions
Tier I
JC2 Portfolio
Technical
JBM CSFL
Standards
Databases
Systems 1. COCOMs 2. Services 3. PAE 4. FITs 5.
Other
Policy
Platforms
Standards
Policy
Accreditations
SVC System Functions
Standards
Standards
Policy
Standards
Architectures
Joint Tasks
Policy
UJTLs X.X X.X.X X.X.X.X X.X.X.X.X
OperationalActivities / Tasks / Sub-tasks
Standards
Policy
Standards
AUTLs, MCTL, NTTL, AFTL
Service Tasks
Programmatic
Where possible, use authoritative sources
Leads to interoperability and technical policy
observations
TOR
33
JC2 Capability to System Mapping
System Functions
Capabilities (JCAs)
UJTLs
Tasks
Systems
Tier I
21
X.X X.X.X X.X.X.X X.X.X.X.X
8
653
Joint System Functions
290
OperationalActivities
JC2 Portfolio
OperationalTasks
OperationalSubtasks
986
USN
33
USMC
61
PR 09 FIT interest
USA
USAF
96
Best of Breed
NCES
AUTLs, MCTL, NTTL, AFTL
Misc
33
PAE Warehouse C2
COCOM Issues
61
Leadership -directed
C2 functions mapped
?
C2 JIC
CJCSM 3500.04C
CJCSM 3500.05A
JBM CSFL 0.4
APOM 09 Focus
POM 10 Focus
C2 JCD
Out-year Focus
34
Operation Planning Capability Mix Vignette
JTF HQ Baseline Arch
Node
Performs
Joint Task
System
Supports
Uses
Node
Activity
Sys Function
Staff Supported
CCDR
Operation Planning
J
-
1, J
-
2, J
-
3
Activities
J
-
5 OPG, J
-
6, JIACG
J
-
4
CJTF
-
Prepare Plans and Orders.
System
J
-
5
-
Conduct vertical and horizontal parallel planning.
Functions
J
-
5 Joint Planning Group
-
Develop Staff Estimates.
JTF Collective Staff
-
Develop Courses of Action.
Generate Input to Mission
System
-
Develop Staff Estimates.
Plans
-
Analyze Course of Action.
Systems/
Simulate
COAs
Joint Task
-
Compare Courses of Action.
Applications
Prepare Deployment
-
Select/Modify a Course of Action.
VTC
Estimates
OP 5.3.9 Prepare
-
Review the applicable theater strategic concept
Collaborative Tool
campaign or major
and
Calculate probabilities for
C2PC
potential actions
operations and related
recommended COA.
GCCS
-
J
plans and orders
-
Develop planning considerations for logistics.
Allocate manage and
JOPES
collaborate
-
Prepare the theater OPLAN.
GCCS
-
I3
ST 5.3.4 Prepare and
-
Modify and/or update the theater strategy.
GCSS
Initiate collaboration
coordinate theater
-
Develop
COAs
for the crisis situation with the
CFAST
Perform collaborations
strategy, campaign plans
Secretary of Defense, allies and coalition
partners,
MAT
or operation plans, and
Communicate Force
component commands, and combatant command
STE/STU
-
III
Information
orders
staff planners.
-
Develop planning considerations for a campaign.
ST 7.1.1 Provide
-
Develop planning considerations for limited
OPLANS for Mobilization
contingency operations, or stability operations,
etc.
Due to space limitations not all
and Deployment
-
Develop and review mobilization plans.
functions were listed.
Planning and Execution
-
Develop and review deployment plans.
35
Summary
Integrated Architectures must
  • be operationally relevant
  • support the Commander

JFCOM has provided/is providing
  • JTF HQ baseline for Joint Integrated Arch
  • JC2 Portfolio Manager C2 Best of Breed
  • CENTCOM C2 Best of Breed
  • Turnkey C2 C2F JTF HQ Certification
  • C-IED
  • JCAS
  • ACT NATO

36
Back-up Slides
37
Architecture Products Supporting JC2 CPM
ID Purpose and scope of assessment
4a. DOT_LPF Analysis (FSA)
ID JC2 Focus areas
ID analysis and JTA objectives
4b. SoSE Analysis (FSA)
3. Analyze JCF for gaps and shortfalls (FAA,FNA)
1. Baseline capability information
2. JCF development validation
4c. JTA
Products from 1 3 provide baseline.
OV-5 OV-2 OV-3 OV-4 OV-6C
AV-1 OV-1
AV-1 OV-1 OV-5 OV-2 OV-3 OV-6C OV-7
Products from 4a and 4b identify solutions and
define MOEs and MOPs to test against.
SV-1 SV-2 SV-3 SV-4
SV-1 SV-2 SV-3 SV-4 SV-5 SV-6 SV-7 SV-11
20 Views Not all required
38
Architecture Product Availability for JC2 CPM
Deployable C2 FIT (Recommended architecture
products for all FITS)
39
Architecture Building Blocks Inform DOTMLPF
D O T M L P F
OV OV-2, OV-5, OV-4, OV-6C OV-4, OV-2 OV-4, OV-2 OV-5, OV-3, OV-2, OV-7, OV-6C OV-4, OV-2 OV-4, OV-2, OV6c OV-2
OV Building Blocks Op Nodes, Activities, Roles, IERs, IEs Roles, Op Nodes Roles (Billets) Activities, Operational Nodes, IERs, IE, Logical Schema, Sequence Roles, Nodes (Warfighter, Organization, Location) Roles, Billets Op Nodes
SV SV-1,2 SV-2, SV-4, SV-3 SV-1, SV-2, SV-4, SV-3, SV-5, SV-6, SV-7, SV-8, SV-9, SV-10a, SV-10b, SV-10c, SV-11 SV-2, SV-4 SV-1, SV-2
SV Building Blocks Systems, Sys Nodes Systems, System Functions, Networks Systems, System Functions, System Nodes (Facilities, Platforms), Networks, Data Exchanges, Interfaces, Physical Schema System Sys Nodes (Facilities), Networks
Outcomes Doctrinal realignment to process, Process optimization Organizational structure analysis. System to task optimization Assessment / Satisfaction of Training Requirements Net-Centric Service Functions, Interface definitions/Service granularity, MOEs, MOPs, System to Systems String Definition, DES Modeling Chain of command optimally organized in view of tasking and systems Personnel Resource optimization, Personnel rerourcing Optimal alignment of Facilities to Operational Topology
40
Department of Defense Architecture Framework -
Architecture Views
41
DODAF - Architecture Views (cont)
42
Summary
  • Operational relevance using Joint Integrated
    Architectures data developed from various sources
    in support of JC2 CPM requires
  • Governance
  • Configuration Management
  • Data taxonomy
  • Repeatability / Reusability
  • Joint Doctrine / Publications other
    authorative data
  • Joint Manning Documents
  • UJTLs / Service Tasks / Master Training Guide
  • System requirements
  • JCIDS documents (JCD, ICD, CDD, CPD)
  • Lessons Learned / best practices
  • Program Managers directives
  • Reusable architectural artifacts based on
    authorative data sources
Write a Comment
User Comments (0)
About PowerShow.com