JCA Baseline Reassessment Phase 2 decomposition In Progress Review

1
JCA Baseline ReassessmentPhase 2
(decomposition)In Progress Review
Joint Staff J-7 / JETCD LTC Rafael Torres 13 Aug
2007
2
Purpose

• Provide JCABR strawman development update
• Tier 2 and 3 JCAs
• Issues
• Proposed tier 1 JCA definition changes
• Solicit senior leader feedback in preparation for
  decomposition workshops

3
JCABR Phase 2 Schedule
Facilitates
Functional community staffing Early seam
identification
Senior leader involvement DJS mandated suspense
4
JROC Decision on JCAs
Logistics
NC
Command Control
Corporate Mgmt Spt
Force Support
Protection
BA
Force Application
Influence

• Criteria
• Functionally decomposed
• 100 of DOD capabilities
• Uniform decomposition
• Maximize mutual exclusivity

IRG ACP task 3.1.2 Use Top-Level JCAs for
Capability Portfolios, establish business
rules for binning resources
Joint Staff J-7 To conduct JCA
Decomposition Down to appropriate level
DAWG Action Endorse Top-Level JCAs as Integrated
Capability Portfolios
5
Binning Issues

• Functional vs. Usage
• Functional approach bins capability only once
• Usage approach (operations, organizations,
  portfolio management / governance) bins variants
  of a common capability in multiple JCAs
• Seams
• Where to bin the single capability where is the
  line

6
Functional vs. Usage Example
USAGE
FUNCTION DESCRIPTION
Operational Doctrine
Engineering
Functional Doctrine
Organizational Structures
7
Specific Binning Issues

• Functional vs. Usage
• Engineers
• Planning, Management, Collaboration
• Dissemination vs. Information Transport
• Seam
• Situational Awareness
• Knowledge Management
• Information Operation divergent capabilities

8
Engineering

• Issue The binning of Combat Engineer
  capabilities
• JCAs involved Force Application / Logistics

• Force Application
• Recommendation The ability to enhance friendly
  mobility and degrade the enemys mobility
  (counter-mobility). Mobility and Counter-mobility
  capabilities should fall under FA
• Rationale These capabilities are required for
  Maneuver (FA Tier 2). IOT Maneuver across the
  operational environment and gain a position of
  advantage, a force must have freedom of mobility.
  Therefore, those capabilities that enhance
  friendly maneuver and those capabilities that
  degrade enemy mobility should be binned with FA.
  Joint Doctrine 3-0 3-34 support this position
  as well as the functional decomposition approach
  and current force structure.
• Recommended business rule N/A

• Logistics
• Recommendation Align all Operational Engineer
  Capabilities under a single Tier II to facilitate
  portfolio management under a single CAM.
• Rationale Reduces complexity of governance and
  allows for better integrated Joint Engineer
  capabilities.
• Recommended business rule While functional
  decomposition is the logical first step, when
  feasible, consolidate closely related or dual use
  capabilities under a single Tier II JCA.

9
Planning

• Issue How to handle Planning and still
  maintain mutual exclusivity
• JCAs involved C2 / BA / FS / Inf / NC / CMS

• COA 1
• Bin all planning to C2
• Rationale The act of planning is the same
  regardless of the functional area conducting it.
  Planning is inherently a command and control
  function, thus C2 is the logical tier 1 JCA to
  bin all planning.
• Recommended business rule All capabilities tied
  to the core planning process (mission analysis
  through COA selection) reside in C2. Any
  planning related capabilities not specifically
  tied to the process of planning will be binned to
  the appropriate functional area.

• COA 2
• Bin operational planning to C2 and strategic
  planning to CMS
• Rationale This approach identifies two types of
  core planning processes that occur across the DoD
  enterprise. It identifies strategic planning as
  an activity that occurs at the corporate level
  and operational planning as a core command and
  control function. All planning activities would
  reside in these two JCAs.
• Recommended business rule Capabilities related
  to strategic planning would be binned to CMS
  while all operational planning activities would
  fall under C2

• COA 3
• Bin functional planning within the appropriate
  functional tier 1 JCA
• Rationale Planning is inherent in all
  functional capabilities across the tier 1
  structure. Any attempt to capture all planning
  as a single, generic activity results in the loss
  of specific capabilities within each functional
  area.
• Recommended business rule Bin functional
  planning capabilities within their appropriate
  tier 1 functional area.

10
Information Transport

• Issue Dissemination capability distinct from
  Information Transport

• Net-Centric
• Recommendation Drop Dissemination from BA tier
  2
• Rationale Dissemination is a transport
  capability in NC Information Transport.
  Intelligence info is managed by BA, but the
  transport, regardless of internal/external of
  DOD remains in the NC bin. (Leased lines from
  other agencies are considered a part of the NC
  environment.)
• Recommended business rule None

• Battlespace Awareness
• Recommendation Bin ISR dissemination on
  red/grey/neutral forces and the environment to BA
• Rationale
• BA information is frequently transferred
  throughout BA multiple BA capabilities before it
  is disseminated externally to enable battlespace
  awareness.
• BA dissemination capabilities are often unique
  due to classification or intrinsic links to
  national capabilities.
• Recommended business rule BA specific
  dissemination remains within BA in coordination
  with NC.

11
Knowledge Management

• Issue Where is the line between C2 and NC
  (Knowledge Management)

• Command Control
• Recommendation
• Core knowledge management tasks should be binned
  to C2
• Providing technical infrastructure/support to
  enable knowledge management belongs to NC.
• Rationale By definition knowledge management --
  the systematic process of discovering, selecting,
  organizing, distilling, sharing, developing and
  using information in a social domain context to
  improve warfighter effectiveness, is inherently
  a C2 process.
• Recommended business rule
• All capabilities that use and manage knowledge
  should be binned to C2.
• All capabilities that support the technical
  aspects of storing and transporting data should
  belong to NC.

• Net-Centric
• Recommendation Decision-making and planning is
  required across all the JCAs.
• Rationale NC provides the secure infrastructure
  including the transport, storing, etc and also
  the cognitive/social human concepts. C2 is a
  user, just as other JCAs.
• Recommendation Move to C2 or lower tier across
  all the JCAs.

12
Situational Awareness

• Issue Battlespace Awareness Situational
  Awareness (C2 Tier 4) / Blue Forces Information

• Command Control
• Recommendation Collection against red, white and
  grey providing situational awareness and
  assessment against all, including blue should be
  binned to BA. Applying knowledge management and
  fusion capabilities to exploit all-source
  information and develop the COP/UDOP should be
  binned to C2
• Rationale In the future battlespace, the ability
  to collect and fuse all-source information on
  red, blue, grey and white is critical to having
  battlespace awareness. Use of this information
  to inform the decision making process in the
  responsibility of C2.
• Recommended business rule All sensing of the
  battlespace belongs to BA. Fusion employment
  of the resulting information belongs to C2

• Battlespace Awareness
• Recommendation
• Bin blue forces information, BA fusion
  capabilities and COP/UDOP to C2.
• Organic system awareness capabilities should be
  addressed with its associated capability (e.g. an
  aircraft radar, submarine sonar).
• Rationale
• We do not normally collect Blue/Friendly Force
  info (ID, Status, location etc.). Blue force
  info is primarily reported as directed by a C2
  entity.
• Blue force reporting is inherent to controlling
  forces.
• Many types of information are aggregated to
  arrive at shared situational awareness - Control
  measures/ boundaries, logistics visibility
• Recommended business rule
• Shared Situational Awareness, Blue Force
  information and employment of the resulting
  information belongs to C2

13
Information Operations

• Issue Information Operations vs. Distinct and
  Unique Capabilities
• JCAs involved Force Application / Influence /
  Net-Centric

• Force Application
• Recommendation Electronic Attack, Electronic
  Warfare Support and Computer Network Attack are
  application of force capabilities and should be
  binned under FA
• Rationale These capabilities are required for
  Engage (FA Tier 2). As the department expands its
  definition of fires these capabilities become
  more important. This is in accordance with JP
  3-0 and JP 3-13

• Net-Centric
• Recommendation CND/CNE should be binned under
  Net-Centric Information Assurance
• Rationale Information Assurance (IA) The
  ability to provide the measures that protect and
  defend information and information systems by
  ensuring their availability, integrity,
  authentication, confidentiality, and
  non-repudiation. This includes providing for the
  restoration of information systems by
  incorporating protection, detection, and reaction
  capabilities. (DOD Directive 8500.1 Information
  Assurance)

• Influence
• Recommendation Military Deception and PSYOP
  remain in the Influence JCA
• Rationale Associated with Strategic
  Communications which is under Influence

14
Proposed Tier 1 Definition Changes

• Influence
• Protection
• Battlespace Awareness
• Force Support

15
Force Application Strawman
Tier 1 Definition The ability to integrate the
use of maneuver and engagement to create the
effects necessary to achieve mission objectives.

• Issue Information Operations (Mil Dec, PSYOP,
  CNO, EW, and OPSEC) is a set of capabilities that
  spans across several JCAs and must be decomposed
  in order to properly account for and bin
  appropriately the individual capabilities.
• Recommendation Electronic Attack, Electronic
  Warfare Support and Computer Network Attack are
  force application capabilities (Engagement) and
  should be binned under FA.
• Issue The ability to enhance friendly mobility
  and degrade the enemys mobility
  (counter-mobility) are critical capabilities for
  Maneuver.
• Recommendation These capabilities remain a Tier
  3 for Force Application.

16
Influence Strawman
Level 1 Definition The ability to shape the
decisions, action, and/or perceptions of key
foreign leaders and relevant populations by
delivering thematic messages and conducting
activities in order to advance the interests of
the USG and its key partners, while strengthening
key U.S. international relationships.
17
Protection Strawman
Tier 1 Definition The ability to
prevent/mitigate adverse effects of attacks and
contingencies designated by the President, on
personnel (combatant/non-combatant) and physical
assets of the United States, allies and friends.
18
Command Control Strawman
Tier 1 Definition The ability to exercise
authority and direction by a properly designated
commander over assigned and attached forces in
the accomplishment of the mission.
19
Net-Centric Strawman
Net-Centric The ability to exploit all human
and technical elements of the joint force and its
mission partners by fully integrating collected
information, awareness, knowledge, experience,
and decision making, enabled by secure access and
distribution.

• Issue Decision-making and planning is required
  across all the JCAs.
• Recommendation Move to JC2 or to a lower tier
  across all the JCAs.
• Issue JC2 recommends KM T2/T3 JCAs be moved to
  JC2.
• Recommendation JC2 is a user of the KM
  environment that NC provides. Cognitive and
  Technical aspects of KM all reside in NC. Remain
  in NC JCA area.
• Issue BA has Dissemination as a Tier 3
  capability. This is clearly a Info Transport
  capability that reside under NC JCAs.
• Recommendation Remove dissemination as a BA Tier
  3 capability
• Issue FA currently has CNA as a JCA.
• Recommendation NC provides the enabling
  capability for CNA/CND/CNE. There are specific
  non-kinetic capabilities that are NC and this
  also allows each area to be binned under one JCA.
  Place CNA under NC.

20
Battlespace Awareness Strawman
Tier 1 Definition The ability to understand the
adversary, neutral and non-combatant dispositions
and intentions operational environments
characteristics and conditions, including natural
and man-made effects, that enable timely,
relevant comprehensive, and accurate assessments
in support of national and military objectives as
well as the characteristics and conditions of the
operational environment that bear on national and
military decision making.

• Issue Change to Tier 1 Definition
• Recommendation Approve change. Rationale
  Clarity and eliminate attributes of a capability
  verbiage.
• Issue Decomposition vs. aggregation
• Recommendation Need a fundamental process
  decision on generic capabilities that enable or
  are internal to other capabilities

21
Logistics Strawman
Tier 1 Definition The ability to project and
sustain the operational readiness of the joint
force through deliberate sharing of National and
multi-national resources to support operations,
extend operational reach and provide the joint
force commander freedom of action necessary to
meet mission objectives.
22
Force Support Strawman
Tier 1 Definition The ability to establish,
develop, maintain and manage a mission ready
Total Force, and provide, operate and maintain
capable installation assets across the total
force to ensure needed capabilities are available
to enable the National Defense Strategy

• Issue Planning appears in other JCAs
• Recommendation One JCA should have ownership of
  the planning capability, recognizing that other
  JCAs include planning as a function

23
Corporate Management Support Strawman
Level 1 Definition The ability to govern and
administer activities which establish strategic
direction and provide common support to force
employers, managers and developers.

• Issues
• Formal strawman development effort on hold

24

• BACKUPS

25
Joint Capability Areas Integrated Capability
PortfoliosLanguage versus Management/Decision
Tool

• Integrated Capability Portfolios
• A Management Tool for Force Development Force
  Management
• To ensure that the capabilities provided are
  optimized to support strategy and meet joint
  warfighter need
• Enterprise-level focus
• JCAs serve as the organizing construct and are
  pretty well aligned
• Caveat there are a small set of capabilities
  that describe business operations and management
  functions are utilized by all capability
  portfolios
• For example strategic planning is described in
  Corporate Management Support JCA, but this
  capability is a part of all Capability Portfolio
  management efforts

• Joint Capability Areas
• Serve as the Departments common language
  spanning General Management ActivitiesEmploy,
  Manage, Develop, Corporate Support
• Describes 100 of Department Capability using a
  Functional View
• Warfighting
• Support to Warfighting, and
• Business Operations and Management
• Binned into Nine Categories
• Each capability is described and binned once
• Joint Capability Areas are not Capability
  Portfolios

25
Logistics
NC
Command Control
Corporate Mgmt Spt
Force Support
Protection
BA
Force Application
Influence
26
Integrated Capability Portfolios Integrating
Portfolios
Logistics (Mobility)
Synchronize DOTMLPF issues across portfolios
Cross-Portfolio DOTMLPF Issues
Command and Control
Use mission threads to identify and work
essential cross-portfolio dependency issues
Address DOTMLPF during capability analysis and
development
Net-Centric
Logistics
Foundational capabilities that support all
other capabilities
Force Support
Corporate Management and Support
27
Engineering
JP 3-34 Joint Engineer Operations CHAPTER I
JOINT ENGINEER FUNDAMENTALS (U) Paragraph 4
Engineer Functions a. Engineer functions
are categories of related engineer capabilities
and activities grouped together to help joint
force commanders (JFCs) integrate, synchronize,
and direct engineer operations. These functions
fall into three basic groups - combat
engineering, general engineering, and geospatial
engineering (see Figure I-1). e. Joint
functions and the engineer functions. There is
not a one-to-one relationship between the
engineer functions and the joint functions. Each
engineer function is associated with multiple
joint functions, but is more closely associated
with some than with others. Figure I-2 ( below)
illustrates the association between some of the
typical engineer functions and their
corresponding joint function.