Introduction to DOD Requirements generation System for Acquisition

1. Joint Capabilities Integration and Development
System
(JCIDS)

2. Agenda
• The Requirements Environment
• Capabilities Based Planning
o Capabilities Based Assessment (CBA)
o Non-Materiel solutions
o JCIDS documents
o KPP’s/KSA’s
• Requirements Approval Process
• Capability Development Tracking and Management Tool
• Rapid Response Lanes for JCIDS (JUON & JEON)
• Information Technology (IT) Box Process
• Questions

3. The Requirements Environment
Finding the balance between:
Combatant Commands near-term
requirements to support Contingency Plans
and current missions
and
Services’ long-range vision
&
investment plans
Versatile, joint systems and Systems optimized for service missions
Growing demands and Fiscal & political constraints
Geographic specificity and World-wide applicability
Ambitious requirements and Achievable acquisition strategy
Quantity matters and High-end capabilities
3

4. Capabilities-Based Planning
Tab 2 - JCIDS
4
Planning,
Programming,
Budgeting, and
Execution
(PPBE)
Fielded
Capabilities
Warfighter
Feedback
Acquisition
CBA Analysis
Set the Strategic
Stage
Set Priorities
Identify Needs
Materiel
Solutions
Non-Materiel
Solutions
Do Nothing

5. The JCIDS Process is …
Top driven by Joint Concepts and experimentation
A bottoms-up process fed by service-unique requirements
Stove-piped

6. Capabilities-Based Planning
Tab 2 - JCIDS
6
Planning,
Programming,
Budgeting, and
Execution
(PPBE)
Fielded
Capabilities
Warfighter
Feedback
Acquisition
CBA Analysis
Set the Strategic
Stage
Set Priorities
Identify Needs
JCIDS
Materiel
Solutions
Non-Materiel
Solutions
Do Nothing

7. Threat vs Capabilities-Based Planning
Requirements Generation System
~30 years of experience
7
Joint Capabilities Integration and
Development System (JCIDS) ~ Since 2003
Partially Interoperable Capabilities
Late Integration
Strategic Direction
Joint Warfighting Concept
Development
Joint Experimentation,
Assessment Analysis,
Validation, Selection of Solutions
Joint Capabilities
Services Build Systems
COCOMs, Services’
Unique Strategic Visions
Service Experimentation,
Assessment Analysis,
Validation, Selection of Solutions
Service Unique Strategic
Visions and Requirements

8. JCIDS is…
• A key supporting process for DoD acquisition and PPBE processes
o Supports “the statutory responsibility of the JROC to validate joint warfighting requirements”
o Supports the CJCS advising the Secretary of Defense for joint Military Requirements
• Identifying
• Assessing
• prioritizing joint military requirements
o Enables the Joint Staff to ensure Sponsors’ needs meet the Joint force needs)
• JCIDS is not –
o Entire “Integrated Defense Acquisition, Technology and Logistics Life Cycle Management System”
8
“Requirements”
(JCIDS)
Acquisition
PPBE

9. JCIDS and Acquisition
•Final Design
•Developmental
TE (DTE)
•Operational
Assessments
•Revise
KPPs/KSAs
•Acquisition
Strategy
•Acquisition
Program
Baseline (APB)
•TEMP
•SEP
Materiel
Development
Decision
Analysis of
Alternatives (AoA)
Competitive
Prototyping
President,
SECDEF
Chairman:
•Strategic
Guidance •JCTDs/JUON/JEON/
Experiments
•JIEDDO Initiatives
•Defense Business Sys
JROC action for JROC Interest programs (ACAT I IA)
Getting The Front End Right is Key
• LRIP
• FOTE
•Technology
Demonstrated
•Initial Key
Performance
Parameters/Key
System Attributes
(KPPs/KSAs)
•Acquisition
Strategy
•TE Master Plan
(TEMP)
•SEP
MS “B”
MS “C”
Develop, Test, Produce
Field
MS “A”
Evolutionary Acquisition
Materiel Solution
Analysis
Technology
Development
Engineering
Manufacturing
Development
Production
Deployment
CDD CPD
•Integrated
Security
Constructs
•Joint
Operations
Concepts
(JOpsC)
family
Activity
Select Joint
Concept
SECDEF
•Operational Planning
•CBAs Other Studies
•Exercises/Lessons
Learned
Capabilities-Based Assessment /
Other
Develop
CONOPS
Policy Identify Capability Requirements
Select Materiel
Solution
•Low Rate
Initial
Production
(LRIP)
•Initial
Operational
TE
(IOTE)
•Acquisition
Strategy
•APB
•TEMP
•SEP
Military Services
OSD/Joint Staff
•Analysis of
Alternatives
(AoA)
•Technology
Development
Strategy (TDS)
•Test Evaluation
(TE) Strategy
(TES)
•System
Engineering Plan
(SEP)
OSD (ATL, CAPE), Services and OSD (DOTE) -- Joint Staff (JROC)
Joint Staff / Joint Requirements Oversight Council / OSD
ICD
Draft
CDD
Identification of Capability
Requirements
CCMD
Outputs
•Mission Problem
•Capability Gaps
•Tasks
•Performance
•Conditions
•Operational Risk
•Non-Materiel
Approaches
•Materiel Approaches
•Recommendations
Validates
ICD
Reviews AoA
Results
Validates
CDD
Validates
CPD

10. An Approved Capabilities Development
Document (CDD) is needed at…
• LRIP
• FOTE
•Technology
Demonstrated
•Initial Key
Performance
Parameters/Key
System Attributes
(KPPs/KSAs)
•Acquisition
Strategy
•TE Master Plan
(TEMP)
•SEP
•Final Design
•Developmental
TE (DTE)
•Operational
Assessments
•Revise
KPPs/KSAs
•Acquisition
Strategy
•Acquisition
Program
Baseline (APB)
•TEMP
•SEP
MS “B”
MS “C”
Competitive
Prototyping
JROC action for JROC Interest programs (ACAT I
Develop, Test, Produce
Field
MS “A”
Evolutionary Acquisition
Materiel
Development
Decision
Materiel Solution
Analysis
Technology
Development
Engineering
Manufacturing
Development
Production
Deployment
Activity
Capabilities-Based Assessment /
Draft
CDD
Select Joint CDD CPD
Concept
Other
Develop
CONOPS
Analysis of
Alternatives (AoA)
ICD
Validates
Select Materiel
Solution
•Low Rate
Initial
Production
(LRIP)
•Initial
Operational
TE
(IOTE)
•Acquisition
Strategy
•APB
•TEMP
•SEP
Military Services
•Analysis of
Alternatives
(AoA)
•Technology
Development
Strategy (TDS)
•Test
Evaluation (TE)
Strategy (TES)
•System
Engineering Plan
(SEP)
OSD (ATL, CAPE), Services and OSD (DOTE) -- Joint Staff (JROC)
ICD
Reviews AoA
Results
Validates
CDD
Validates
CPD
IA)
Milestone A
Milestone B (Pre-EMD Review)
Milestone C

11. Capabilities-Based Assessment (CBA)
11
NEEDS
GAPS
SOLUTIONS
Existing
Guidance
The problems
and the risks
What we need
for the mission
What should we
do about it?
Where does this
need rank?
How soon do we
need it?

12. Capability-Based Assessment (CBA)
Output Documents
• Joint DCR – DOTmLPF-P Change Recommendation
o When DoD Decides a Joint Non-Materiel Solution is appropriate
o Non-Materiel Solutions
• Change doctrine
• Reorganize
• Train and educate DOD personnel differently
• Acquire commercial or non-developmental items
• Acquire more quantities of existing items
• Add or reassign personnel
• Move or realign facilities
• Change policy
o Sometimes Called DOT_LPF-P
12

13. CBA Output Documents
Initial Capabilities Document (ICD)
o Required at Material Development Decision (MDD)
o Initiates the acquisition process of material developers
o Documents Capabilities-Based Assessment (CBA) Results
• specifically Capability Gaps
o Identifies relevant operational performance attributes
o Documents the recommendation on the need
• Materiel solution
• potential non-material solutions
o Predecessor for the Capabilities Development Document
o Key review question: How to prioritize war-fighting gaps?
13

14. Capabilities Development Document
Operational Performance Attributes
• Establishes attributes necessary to design a proposed system
• Establishes a Performance Baseline
• Guides development and demonstration
• Guides development of Key Performance Parameters (KPPs) to Include in Capabilities
Development Document
14

15. Key JCIDS Development Documents
Capability Development Document (MS B)
o Defines Performance Requirements to Achieve Capability
• Identifies KPPs, KSAs, and additional attributes
• Attributes should be authoritative, measurable and testable
o Describes DOTmLPF-P Policy Constraints for the solution
• May describe multiple increments
o Provides operational capabilities for
• Acquisition strategy
• Acquisition Program Baseline (APB)
o Inserts verbatim into the APB
• All Key Performance Parameters (KPP)
• Sustainment Key System Attributes (KSA)
15

16. Key Performance Parameters
(KPPs)
• Performance Attributes of system
• Critical to develop an effective military capability
• KPPs Must
o Be measurable
o Be testable
o Be quantifiable in a practical and timely manner
o Enable feedback from Test Evaluation
o Support decision making
• Mandatory KPPs
o Force Protection
o Survivability
o Sustainment
o Net Ready
o Training
o Energy
• Validated by the JROC for JROC Interest Documents
• Failure to meet a KPP results in program reevaluation or reassessment
16

17. Key System Attributes
(KSAs)
• Attributes/characteristics essential to achieve a balanced solution
• Not critical enough to be selected as a KPP
• KSAs must
o Be measurable
o Be testable
o Be quantifiable
• Identified by the Sponsor; should be kept to a minimum
• Sponsor Senior Leadership can change KSA
17

18. Mandatory
Key Performance Parameters (KPP)
Key System Attributes (KSA)
• Force Protection KPP (all manned systems)
• Survivability KPP (all manned systems; unmanned maybe)
• Sustainment KPP (all ACAT I )
o Materiel Availability
o Operational Availability
o Supporting KSAs
• Materiel Reliability
• Operation Support Costs
• Net Ready KPP (all IS NSS)
• Training KPP (all ACAT I)
• Energy KPP
o Provisions of energy impact operational reach
o Protection of energy infrastructure or energy resources is required

19. Key JCIDS Development Documents
Capability Production Document (CPD) (MS C)
o Supports production and development of one increment
o Documents authoritative and testable capabilities
o Supports
• Production
• Testing
• Deployment
o Describes incremental production and deployment
o Provides no new requirements
o Must meet operational performance attributes
19

20. CDD and CPD Differences

21. JCIDS Gatekeeper
J8 Deputy Director, Requirements, (2-star)
• Performs initial review of all JCIDS proposals
• Determines:
• Joint Staffing Designator
• JROC Interest
• JCB Interest
• Joint Integration
• Joint Information
• Independent
• Lead and supporting Functional Capabilities Boards (FCB)
• Formal Staffing begins after Gatekeeper decisions
21

22. A Streamlined Deliberate Process
22
Sponsor Gatekeeper
Functional
Capability
Board
•SME inputs
from DoD
•Prep for
JCB/JROC
Termination
Joint Capabilities
Board
Joint Requirements
Oversight Council
Acquisition
(and/or DCRs)
Phase 1
Staffing
•O-6 level coord
from across DoD
Sponsor Gatekeeper
Phase 2
Staffing
•GO/FO lvl
coord from
multiple
agencies
FCB Chair:
Phase 2?
FCB
Draft
•Prep
for
mtg
4 days 21 days Variable
Total:
45+ days 4 - 40 days 15 days 26 – 35 days
95 – 160+ days
DJ8
Prep
Brief
Est. 21 days Commenting/30 days
Adjudication/7 days to FCB Chair
4 days Est. 7 days to JCB/14 days to JROC Total:
83 days
Sponsor Gatekeeper
Functional Capability
Board
•SME inputs from DoD
•Prioritization within this
portfolio
•COCOM Inputs
•Allied/Partner Nation
equity
•Non-material
recommendations
FCB Chair:
Ready
Validation
Discussion?
Termination
JCB JROC
Acquisition
(and/or DCRs)
Combined
“Staffing”

23. 23
CDTM
Capability Development Tracking and Management
• IT system - transforms JCIDS capability tracking from
document-centric to data-centric process
– Developed and deployed on NIPRNet and SIPRNet
– Mandated for all JCIDS documents (ICD, CDD, CPD, DCR)
Traces capability gaps
Inserts process metrics
Enhances ease of use
Improved search capability
Improved document creation
Input standardization
Shares data with other DoD applications

24. 24
CDTM
CDTM
Traceability of Capability Gaps Tracks reports individual gaps from entry to fielded capability
Process metrics Tracks benchmark data workflow to time complete documents
Search capability Searches specific document areas and data categories to get
relevant results
Ease of use Searches for relevant gaps at all JCA tier levels
Document creation standardization Prompts via “Turbo-tax” wizard interface for inputs
Automatically creates and formats document
Standardizes JCIDS document formatting length
Interoperability Shares common data with other DoD applications

25. Deliberate JCIDS Process
• Materiel Solutions
– Initial Capabilities Document (ICD)
– Capability Development Document (CDD)
– Capability Production Document (CPD)
• Non-Materiel Solutions
• Joint DOTmLPF-P Change Recommendation (DCR)
• Operational Requirements Development
• Team Effort
• All Stakeholders should be involved
• User involved in technical requirements development
25

26. Rapid Response Situations
• Urgent compelling needs during crisis and conflict
• Each Service has Policies and Procedures, but …
• Service-unique approaches do not address Theater-Wide Joint Urgent and Emergent
Operational Needs
• Requirements managers need to stay engaged in process
26

27. Three Requirements “Lanes”
• Deliberate Requirements
– Service, CCMD or Agency Driven
– Traditional route capabilities that require significant tech
development and/or are not urgent or compelling in nature
• Emergent Requirements
– CCMD-driven
– Supports accelerated acquisition of capabilities needed for
an anticipated or pending contingency operation
– VCJCS verifies, JCB or JROC validates
• Urgent Requirements
– CCMD-driven
– Urgent compelling to prevent loss of life and/or mission
failure during current operations
– Require little tech development can be resolved in less
than two years
– DDR validates
“Keep right, except to pass”
D
E
L
I
B
E
R
A
T
E
E
M
E
R
G
E
N
T
0 – 2
YRS
U
R
G
E
N
T
0+ to
5 YRS
CONFLICT
LANE
ONLY
POTENTIAL
CONFLICT
LANE
2-6+
YRS
27

28. Urgent Emergent Operational Needs
Definitions
• Urgent Operational Need (UON):
o Capability requirements identified by DOD Component as impacting an ongoing/anticipated
contingency operation. If left unfulfilled, UONs result in capability gaps potentially resulting
in loss of life or critical mission failure. DoD Components may use a different name for a
UON.
• Joint Urgent Operational Need (JUON):
o UONs that are identified by a Combatant Command as inherently joint and impacting an
ongoing contingency operation.
• Joint Emergent Operational Need (JEON):
o UONs that are identified by a Combatant Command as inherently joint and impacting an
anticipated or pending contingency operation.

29. Joint Urgent Emergent Operational Needs
• Every Service has a Rapid Response Procedure
• Joint Rapid Response Lanes
o Joint Urgent Operational Needs (JUON)
o Joint Emergent Operational Needs (JEON)
• JUON/JEON Validation and Resourcing Involves
o VCJCS/JCB/JROC
o Gatekeeper (J8 Deputy Director for Requirements (DDR))
o Joint Rapid Acquisition Cell (JRAC)
o Functional Capabilities Boards (FCBs) and Working Groups
o Military Services, Defense Agencies, ISR TF
Joint Improvised Explosive Device Defeat Organization (JIEDDO)
29

30. Urgent Situations
• Urgent Situations (Current Guidance)
o Ongoing conflict or crisis
o Unforeseen military requirements
o Must resolve as soon as possible
• These Situations Would Result in:
o Direct enemy-action related loss of life and/or
o Critical mission failure
• Validation Authority is J8, DDR (Gatekeeper)
• Staffing in 15 calendar days
30

31. Emergent Situations
• Emergent Situation
o Supports accelerated acquisition of capabilities needed
• Anticipated contingency operation
• Pending contingency operation
o JUONs process variation
• Driven by “pending” or “imminent” operations
• Require capability in short timeframes
• Avoid loss of life and/or mission failure when operations commence
o VCJCS verification required prior to staffing as emergent candidate
• Validation at the JCB or JROC
• Staffing goal = 31 days
31

32. Who Initiates an Urgent/Emergent Need?
• An Urgent/Emergent Request Must Come from:
o Joint Force Commander
o Service Component Commander
o Commander’s delegated representative
• Service/Services must validate Unique Urgent/Emergent Need
• JUONs/JEONs
o Endorsed by the Combatant Commanders
o Validated by the Joint Staff
32

33. Urgent/Emergent Staffing
33

34. JUON / JEON Process Flow
Generation to Delivery for Assessment
Warfighter
Originates
Joint Rapid Acquisition Cell
(JRAC)
• Determines Resourcing Strategy
• Assigns to JIEDDO or
Service/Agency for sponsorship
COCOM CoS
Certifies
Services/Agencies
Non C-IED Solutions
Joint IED Defeat Office
C-IED Solutions
FCB
Triages
JS J-8/RMD
Receives
JS J-8 DDR or
JCB/JROC
Validates
Senior Integration
Group (SIG):
Oversight Body for
DoD Urgent Needs
Assessment of
Operational Utility

35. Rapid Response Framework
35
The JUON / JEON Process Consists of Four Phases:
GENERATION
PHASE
VETTING
PHASE
EQUIPPING
PHASE
OPERATIONS
SUPPORT PHASE
Force Commander Identifies
Urgent /Emergent Need
COCOM Staff determines the
most suitable process
COCOM CoS certifies and submits
to Joint Staff (J-8 RMD)
J-8 RMD Receives and verifies
that
JUON / JEON meets submission
criteria
Joint staff reviews and validates
JUON or JEON
Identify solutions
JRAC determines a resourcing
Strategy and assigns Sponsor
Sponsor creates a
Simplified Acquisition Plan
Procures and delivers solution
to the Warfighter
Provide Progress Reports
On Performance, Cost, and
Schedule
Sponsor sustains solution
and monitors performance for
twenty- four months
Sponsor, COCOM, and
FCB prepare Capability Review to
address final disposition of fielded
system
Speed is Life

36. Rapid Acquisition Challenge
36
Future-focused
Very structured process
Evolved requirements
Analysis of alternatives
Lengthy development
High Program visibility
Large Investment
Now-focused
More ad-hoc process
Broad requirement
Quick assessment of alternatives
Limited development
High visibility on results
Limited investment
Very Limited Feedback
Transition to Program of Record
Deliberate Acquisition
Rapid Acquisition

37. Rapid Response Summary
• An Urgent / Emergent Situation that Results in
o Direct enemy-action related loss of life and/or
o Critical mission failure
• Each Service has Its Own Approach to Urgent Needs
• JUONs / JEONs Support Joint Urgent / Emergent Needs
• Initiating JUONs / JEONs is a Requirements Process
• Requirements Managers will Need to be Involved with Follow-On Activities
37

38. The “IT Box”
• Describes IS program overall bounds to reduce return trips to JROC to approve improved capabilities.
• Provided to FCB/JCB/JROC as part of IS program’s ICD approval process
• Only applies to programs that do not develop hardware systems (leveraging COTS/GOTS hardware).
• Once ICD is approved, no need to return to JROC with CDD/CPD, unless IS ICD results in a MDAP.
38
Applications System Software
Development Acquisition
Hardware Refresh System
Enhancements Integration
Requirements Organization Oversight
Capabilities
Required
JROC
Approved
IS ICD $

39. IS Requirements/Acquisition Process
Component
Approved Specific implementation
CD
CD
CD
RDP
RDP
RDP
CD
JROC
Approved
IS
ICD
CD
CD
CD
CD
CD
Capabilities
Based
Assessment
RDP
MS B
OS
MD
D
Engineering
Analysis/
Design
ICD
(NF) Rapid Delivery
Fielding Decisions
Agile
Development
RDP
guidance on document
content approval
process provided by
Component
CD
Acquire Decision
RDP – Requirements Definition Package
CD – Capability Drops

40. IS Requirements/Acquisition Process
Joint
Concepts
Capabilities
Based
Assessment
Strategic
Guidance
MS A/B
OS
MD
D
Engineering
Analysis/
Design
Full
Deployment
Decisions
CD
CD CD CD CD CD CD CD CD
IS
ICD Rapid Delivery
IOC
Agile
Development
RDP
A very streamlined process for truly agile IS development
• ICD is developed in a format tailored to IS capabilities
• Post-MDD, one or more RDPs developed to further refine requirements for needed capabilities
• RDP is broken down into CDs to deliver individual capability “widgets”
• CD results released incrementally via Full Deployment Decisions

41. Summary
• The Requirements Environment
• Capabilities Based Planning
o Capabilities Based Assessment (CBA)
o Non-Materiel solutions
o JCIDS documents
o KPP’s/KSA’s
• Requirements Approval Process
• Capability Development Tracking and Management Tool
• Rapid Response Lanes for JCIDS (JUON JEON)
• Information Technology (IT) Box Process
• Questions

42. Background Information

43. Force Protection (FP) KPP
• For Manned Systems Systems designed to enhance personnel survivability
• Force Protection Attributes:
o Protect personnel by preventing or mitigating hostile actions
o Protect system operator, rather than the system itself
o Offensive attributes intended to defeat enemy not force protection attributes
o Not Force Protection Attributes
o Protection against accidents, weather, natural environmental hazards
o Protection against disease (except when related to a biological attack)
• Protection FCB assesses FP KPP for JROC/JCB interest Programs
• If not used must explain why not in CDD/CPD
• Examples:
o Radar Cross Section
o Ability to Withstand hit/blast/flood/shock
o Jam Resistance
o Tactics

44. Survivability KPP
• All Manned Systems and may be used for Unmanned Systems
• Survivability attributes contribute to survivability
• Joint Staff (J-3) Protection FCB must concur if not used
• Examples:
o Speed
o Maneuverability
o Armor
o Electromagnetic Spectrum Control
o Redundancy of Critical Subsystems
o Protection from Chemical, Biological and Radiological Effects

45. Sustainment KPP KSAs
• Applies to All ACAT I Programs.
• ACAT II Below programs include Sustainment KPP or Sponsor-defined
sustainment metrics
• Three Elements:
o Availability KPP
• Materiel Availability
• Operational Availability
o Reliability KSA
o Operations Support Cost KSA
• Reviewed /Analyzed
o Joint Staff (J-4)
o Deputy Assistant Secretary Defense (Materiel Readiness)

46. Net Ready (NR) KPP
• Information Systems (IS) National Security Systems (NSS):
o Automated acquisition, storage. manipulation, management
o Movement, control, display
o Switching, Interchange, Transmission, reception
o of DOD data or information regardless of classification or sensitivity
• Not for systems that do not communicate with external systems
• C4/Cyber FCB
o Assesses NR KPP or Sponsor justification
o Provides NR KPP Certification

47. Net-Ready KPP
Continued
• Net-Ready KPP Consists of Three Attributes:
o Supports Military Operations
o Is Entered and Managed on the Network, and
o Effectively Exchanges Information
• Three-Step Development Process
1. Mission Analysis – Determines attribute details to supports military operations
2. Information Analysis – Determine attribute details entered managed on network and effectively exchange
information
3. Systems Engineering Architecture – Supports all 3 attributes

48. Training (T) KPP
• Applies to All ACAT I Programs
• Attributes Include (among others):
o Proficiency Level
o Time to Train
o Training Retention
o Associated Metrics
• Ensure training requirements addressed at beginning of acquisition process through
Program’s Acquisition life-cycle.
• J-7 with USD(Personnel Readiness) assesses Training KPP or why KPP is not applicable for
JROC/JCB Interest Programs

49. Energy KPP
• Systems where energy provision, including fuel/electric power:
o Impacts Operational Reach
o Requires protection of energy infrastructure/resources in Supply Chain
• May be expressed as
o Units of Energy Used per Period of Time (e.g. gallons per hour)
o Number of Refuelings Required (e.g. tankings per hour).
• Logistics FCB, with J-4/ED Defense Energy Board assesses KPP or why KPP is not
applicable for JROC/JCB interest programs

50. JCIDS Document Tracks
FCB review
prioritization
JROC JROC
Interest
JCB
Interest
Joint
Integration
Joint
Information
KM/DS staffing
comment
Independent
FCB review
prioritization
KM/DS staffing
comment
FCB review
prioritization
KM/DS staffing
comment
FCB review
prioritization
KM/DS staffing
comment
FCB
prioritization
JCB
Review
Validation
Authority
JCB
Sponsor
Joint Staffing
Designator (JSD)
ACAT I/IA programs
Joint DCRs
ACAT II below with impact
on interoperability
ACAT II below that require
endorsements certifications
ACAT II below that do not require
endorsements certifications
All others
KM/DS: Knowledge Management/Decision Support tool

52. Functional Capability Boards (FCB)
Sponsoring Organizations
C4/Cyber
Includes NC and
C2 JCAs
Battlespace Logistics
Awareness
Force
Application
Force
Support
Protection
FCB Membership: (O-6 level)
Services
Combatant Command Reps
OSD (ATL)
OSD (I)
USecAF (Space)
DOD CIO OSD(Comptroller)
D/CAPE
DIA Rep (Threat)
ODNI/IRB
Other DoD Agencies as necessary
Additional JCAs:
• Building Partnerships
• Corporate Management
Support

53. CDTM Wizard
Automated Document Creation
53
Document is created with data
filled in from wizard entries

54. Overview of Updated JCIDS Manual
54

55. The Designated Service/Agency (DS/A)
• Service/Agency
o Recommended by Gatekeeper
o Named by JRAC
• DS/A develops an initial course of action
o Implementation recommendation
o Funding strategy recommendation
• DS/A manages approved JUON / JEON effort
55