Post on 08-Jul-2015
description
transcript
Joint Capabilities Integration and Development
System
(JCIDS)
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
The Requirements Environment
Finding the balance between:
Combatant Commands near-term requirements to support Contingency Plans
and current missionsand
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
Capabilities-Based Planning
Tab 2 - JCIDS4
Planning, Programming, Budgeting, and
Execution(PPBE)
Fielded Capabilities
WarfighterFeedback
Acquisition
CBA Analysis
Set the Strategic Stage
Set Priorities
Identify Needs
Materiel Solutions
Non-Materiel Solutions
Do Nothing
The JCIDS Process is …
� Top driven by Joint Concepts and experimentation
� A bottoms-up process fed by service-unique requirements
� Stove-piped
Capabilities-Based Planning
Tab 2 - JCIDS6
Planning, Programming, Budgeting, and
Execution(PPBE)
Fielded Capabilities
WarfighterFeedback
Acquisition
CBA Analysis
Set the Strategic Stage
Set Priorities
Identify NeedsJCIDS
Materiel Solutions
Non-Materiel Solutions
Do Nothing
Requirements Generation System ~30 years of experience
Threat vs Capabilities-Based Planning
7
Joint Capabilities Integration and Development System (JCIDS) ~ Since 2003
Late Integration
Joint Capabilities
Strategic Direction
Joint Warfighting ConceptDevelopment
Joint Experimentation, Assessment & Analysis,
Validation, Selection of SolutionsServices Build Systems
COCOMs, Services’ Unique Strategic Visions
Service Unique Strategic Visions and Requirements
Service Experimentation, Assessment & Analysis,
Validation, Selection of Solutions
Partially Interoperable Capabilities
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
PPB&E
Getting The Front End Right is Key
JCIDS and Acquisition
• LRIP• FOT&E
•Technology Demonstrated
•Initial Key Performance Parameters/Key System Attributes (KPPs/KSAs)
•Acquisition Strategy
•T&E Master Plan (TEMP)
•SEP
MS “B”
•Final Design•Developmental T&E (DT&E)
•Operational Assessments
•Revise KPPs/KSAs
•Acquisition Strategy
•Acquisition Program Baseline (APB)
•TEMP
•SEPMS “C”
Develop, Test, Produce &Field
MS “A”
Evolutionary Acquisition
Materiel Solution Analysis
Technology Development
Engineering & Manufacturing Development
Production & Deployment
CDD CPD
SECDEF
Select JointConcept
Activity
Capabilities-Based Assessment /Other
Policy Identify Capability Requirements
Develop CONOPS
Select MaterielSolution
•Low Rate Initial Production (LRIP)
•Initial Operational T&E (IOT&E)
•Acquisition Strategy
•APB•TEMP•SEP
Military Services
OSD/Joint Staff
•Analysis of Alternatives (AoA)
•Technology Development Strategy (TDS)
•Test & Evaluation (T&E) Strategy (TES)
•System Engineering Plan (SEP)
OSD (AT&L, CAPE), Services and OSD (DOT&E) -- Join t Staff (JROC)
Analysis ofAlternatives (AoA)
CompetitivePrototyping
Joint Staff / Joint Requirements Oversight Council / OSD
•Integrated Security Constructs
•Joint Operations Concepts (JOpsC) family
ICD
MaterielDevelopment
Decision
DraftCDD
Identification of Capability Requirements
CCMD
•Operational Planning•CBAs & Other Studies•Exercises/Lessons Learned
Outputs•Mission & Problem•Capability Gaps•Tasks•Performance•Conditions
•Operational Risk•Non-Materiel Approaches
•Materiel Approaches•Recommendations
President, SECDEF & Chairman:•Strategic Guidance •JCTDs/JUON/JEON/
Experiments•JIEDDO Initiatives•Defense Business Sys
Validates ICD
Reviews AoA Results
Validates CDD
Validates CPD
JROC action for JROC Interest programs (ACAT I & IA)
An Approved Capabilities Development
Document (CDD) is needed at…
• LRIP• FOT&E
•Technology Demonstrated
•Initial Key Performance Parameters/Key System Attributes (KPPs/KSAs)
•Acquisition Strategy
•T&E Master Plan (TEMP)
•SEP
MS “B”
•Final Design•Developmental T&E (DT&E)
•Operational Assessments
•Revise KPPs/KSAs
•Acquisition Strategy
•Acquisition Program Baseline (APB)
•TEMP
•SEPMS “C”
Develop, Test, Produce &Field
MS “A”
Evolutionary Acquisition
Materiel Solution Analysis
Technology Development
Engineering & Manufacturing Development
Production & Deployment
CDD CPDSelect JointConcept
Activity
Capabilities-Based Assessment /Other
Develop CONOPS
Select MaterielSolution
•Low Rate Initial Production (LRIP)
•Initial Operational T&E (IOT&E)
•Acquisition Strategy
•APB•TEMP•SEP
Military Services
•Analysis of Alternatives (AoA)
•Technology Development Strategy (TDS)
•Test & Evaluation (T&E) Strategy (TES)
•System Engineering Plan (SEP)
OSD (AT&L, CAPE), Services and OSD (DOT&E) -- Join t Staff (JROC)
Analysis ofAlternatives (AoA)
CompetitivePrototyping
ICD
MaterielDevelopment
Decision
DraftCDD
Validates ICD
Reviews AoA Results
Validates CDD
Validates CPD
JROC action for JROC Interest programs (ACAT I & IA)
Milestone AMilestone B (Pre-EMD Review)
Milestone C
Capabilities-Based Assessment (CBA)
11
NEEDS
GAPS
SOLUTIONS
ExistingGuidance
The problemsand the risks
What we need for the mission
What should wedo about it?
Where does this need rank?
How soon do we need it?
Capability-Based Assessment (CBA)
Output Documents
• Joint DCR – DOTmLPF-P Change Recommendationo When DoD Decides a Joint Non-Materiel Solution is appropriateo 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-P12
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
Capabilities Development DocumentOperational 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
Key JCIDS Development DocumentsCapability 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
Key Performance Parameters(KPPs)
• Performance Attributes of system• Critical to develop an effective military capability • KPPs Must
o Be measurableo Be testableo Be quantifiable in a practical and timely mannero Enable feedback from Test & Evaluationo Support decision making
• Mandatory KPPso Force Protectiono Survivabilityo Sustainmento Net Readyo Trainingo Energy
• Validated by the JROC for JROC Interest Documents• Failure to meet a KPP results in program reevaluation or reassessment
16
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
MandatoryKey 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
Key JCIDS Development DocumentsCapability 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
CDD and CPD Differences
• 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
JCIDS GatekeeperJ8 Deputy Director, Requirements, (2-star)
21
22
A Streamlined & Deliberate Process
Sponsor Gatekeeper
Functional Capability
Board
•SME inputs from DoD•Prep for JCB/JROC
Termination
Joint RequirementsOversight Council
Acquisition(and/or DCRs)
Joint CapabilitiesBoard
Phase 1Staffing
•O-6 level coord from across DoD
Phase 2Staffing
•GO/FO lvl coord from
multiple agencies
Sponsor Gatekeeper
FCB Chair:Phase 2?
21 days4 days Variable
Total: 95 – 160+ days45+ days 4 - 40 days
FCBDraft
•Prep for mtg
15 days 26 – 35 days
DJ8PrepBrief
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 CapabilityBoard
•SME inputs from DoD•Prioritization within this portfolio•COCOM Inputs•Allied/Partner Nation equity•Non-material recommendations
FCB Chair:Ready
ValidationDiscussion?
Termination
JROCJCB
Acquisition(and/or DCRs)
Combined“Staffing”
23
CDTMCapability 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
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 inputsAutomatically creates and formats documentStandardizes JCIDS document formatting & length
Interoperability Shares common data with other DoD applications
CDTM
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
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
• 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”
DELIBERATE
EMERGENT
URGENT
0 – 2YRS
0+ to 5 YRS
CONFLICTLANEONLY
POTENTIALCONFLICT
LANE
2-6+YRS
Three Requirements “Lanes”
27
Urgent & Emergent Operational NeedsDefinitions
• 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.
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
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
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
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
Urgent/Emergent Staffing
33
JUON / JEON Process FlowGeneration to Delivery for Assessment
Warfighter
Originates
Joint Rapid Acquisition Cell (JRAC)
• Determines Resourcing Strategy
• Assigns to JIEDDO or Service/Agency for sponsorship
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
COCOM CoS
Certifies
Assessment ofOperational Utility
Rapid Response Framework
35
The JUON / JEON Process Consists of Four Phases:
GENERATIONPHASE
VETTINGPHASE
EQUIPPINGPHASE
OPERATIONS &
SUPPORT PHASE
Force Commander Identifies Urgent /Emergent Need
COCOM Staff determines themost suitable process
COCOM CoS certifies and submitsto Joint Staff (J-8 RMD)
J-8 RMD Receives and verifies that JUON / JEON meets submission criteria
Joint staff reviews and validatesJUON or JEON
Identify solutions
JRAC determines a resourcing Strategy and assigns Sponsor
Sponsor creates a Simplified Acquisition Plan
Procures and delivers solutionto the Warfighter
Provide Progress Reports On Performance, Cost, and Schedule
Sponsor sustains solutionand monitors performance fortwenty- four months
Sponsor, COCOM, andFCB prepare Capability Review to address final disposition of fieldedsystem
Speed is Life
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
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
The “IT Box”
38
• 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.
Applications & System SoftwareDevelopment & Acquisition
Hardware Refresh & System Enhancements & Integration
Requirements Organization & Oversight
CapabilitiesRequired
JROCApproved
IS ICD $
IS Requirements/Acquisition Process
CD
CD
CD
RDP
RDP
RDP
CD
ISICD
JROCApproved
CD
CD
CD
CD
CD
CapabilitiesBased
Assessment
MS B
O&SEngineering Analysis/ Design
MDD
ICD(NF) Rapid Delivery
Fielding Decisions
Agile Development
RDP
ComponentApproved Specific implementation
guidance on document content & approval process provided by Component
CD
Acquire Decision
RDP
RDP – Requirements Definition PackageCD – Capability Drops
IS Requirements/Acquisition Process
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
Joint Concepts
CapabilitiesBased
Assessment
Strategic Guidance
MS A/B
O&SEngineering Analysis/ Design
MDD
ISICD Rapid Delivery
Full Deployment
Decisions
IOC
CDAgile
Development
CD CD CD CD CD CD CD CDRDP
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
Background Information
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
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
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)
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
Net-Ready KPPContinued
• 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 Process1. 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
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
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
JCIDS Document Tracks
JROCJROCInterest
JointIntegration
JointInformation
JCBInterest
KM/DS staffing & comment
FCB review & prioritization
Independent
KM/DS staffing & comment
FCB review & prioritization
KM/DS staffing & comment
FCB review & prioritization
KM/DS staffing & comment
FCB review & prioritization
FCB prioritization
JCBReview
ValidationAuthority
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 othersKM/DS: Knowledge Management/Decision Support tool
Functional Capability Boards (FCB)Sponsoring Organizations
C4/CyberIncludes NC and
C2 JCAs
LogisticsBattlespace Awareness
Force Application
Force Support
Protection
DOD CIO OSD(Comptroller)D/CAPEDIA Rep (Threat)ODNI/IRB Other DoD Agencies as necessary
FCB Membership: (O-6 level)ServicesCombatant Command RepsOSD (AT&L)OSD (I)USecAF (Space)
Additional JCAs: • Building Partnerships• Corporate Management& Support
CDTM Wizard Automated Document Creation
53
Document is created with data filled in from wizard entries
Overview of Updated JCIDS Manual
54
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