1. Urgent Operational Needs – Rapid Acquisition

2. Lesson Objectives
Describe Urgent Operational Need situations, procedures, and lessons learned
Recognize situations that call for a Rapid Response
List the differences between a Rapid Acquisition and Traditional Acquisition
Describe actions to transition a Rapid Response into a Program of Record (POR)

3. Urgent Operational Needs
Urgent needs are generated during a NCA-directed combat operation and if not met will result in loss of life or mission failure
COCOM/Joint Force Commanders use JUON process to rapidly acquire joint / theater-wide capabilities
Services use Service procedures to rapidly acquire Service-unique capabilities
Requirements Managers and Program Managers must work together to ensure success
Whoever writes the JUON becomes a de-facto Requirements Manager
The DOD 5000 and CJCS 3170 series acquire weapons systems using a traditional, deliberate process, usually taking a few years even when the system uses maximum streamlining.
Sometimes, the warfighters need a new capability as soon as possible. What does DOD and the JCIDS process do when warfighters need something NOW?
Each Service uses various methods to shorten the acquisition timelines to meet urgent and compelling needs during crisis and conflict, but service policies and procedures do not provide an opportunity to address theater-wide multi-Service combatant commander joint urgent operational needs.
The action officer or NCO who writes the JUON for the combat command becomes a de-facto Requirements Manager; however, Requirements Managers must be involved in follow-on actions for recurring or ongoing requirements.
Underline loss of life or mission failure………good bumper sticker

4. Traditional Acquisition vs. Rapid Acquisition Processes
6/11/2018
Traditional Acquisition
Future Focused, ACAT Programs
Very Structured Process
Evolved Requirements
Analysis of Alternatives
Lengthy Development
High Visibility on Program
Large Investment
Rapid Acquisition
Now-focused, ACAT II or below
Streamlined process
Specific, combat requirement
Quick assessment of alternatives
Limited development
High visibility on results
Limited investment
May transition to PoR

5. Joint Urgent Operational Needs
JUONs can be initiated by:
A COCOM / Joint Force Commander
A Service Component Commander through its COCOM
A COCOM commander’s delegated representative
COCOM-validated JUONs are submitted to the Joint Staff J8 and the Joint Rapid Acquisition Cell
JS Gatekeeper (VDJ-8) will assign JUON to appropriate FCB
Joint Rapid Acquisition Cell (JRAC) will work with Services for solutions / funding
Joint Improvised Explosive Device Defeat Organization (JIEDDO) will address IED issues
JUON format is on SIPRnet:
When warfighters report situations that put life at risk or risk mission failure, every service has its own Rapid Response procedure. When the situation is a joint problem, the joint Rapid Response procedure is the Joint Urgent Operational Needs (JUON).
JUON validation and resourcing involves:
The Gatekeeper
The Joint Rapid Acquisition Cell (JRAC)
Functional Capabilities Boards (FCBs)
The Joint Capabilities Board (JCB)
Working Groups, and
The Budget Office Director’s Board (BOD)

6. The Designated Service/Agency (DS/A)
Recommended by the Gatekeeper
Named by the JRAC
Sponsors the approved JUON solution
Develops the initial Course of Action
Implementation plan
Funding strategy
The Designated Service/Agency (DS/A) named by the Gatekeeper develops an initial course of action. The DS/A provides an implementation and funding strategy recommendation to the Functional Capabilities Board Working Group (FCB WG) and the JRAC. The DS/A subsequently becomes responsible for the overall management and execution of the approved JUON effort.

7. JUON Process
6/11/2018
FCB will:
Conduct triage of JUONs (assess and prioritize)
Convene a working group
Recommend initial sponsor and work with JRAC to identify sources of funding
DS/A (sponsor) will within 30 days submit a JUONs Management Document:
Plan to acquire the item(s) coordinated with COCOM and FCB
Will be approved at the Joint Staff level--by the FCB, J8 or JROC depending on importance and funding level
The DS/A must:
Develop an acquisition plan
Obtain service-level approval (ACAT II and below) to begin production
Lower case triage… no cap….triage = prioritize and assess
Bullets: Prioritize JUON, Determine level of effort required, Recommend initial sponsor… voice over “and work with JRAC…..…. “ buuuuut the services have the ultimate funding hammer. Important that a young RM to understand – bullet 2 second bullet

8. JUON Limitations JUONs are not intended to bypass DODI 5000.02
JUON materiel solutions must be ACAT II or below
Must be inherently joint in nature
No stand-alone funds are available to fund JUONs
JRAC must develop options to fund them from within existing budget line-items

9. Immediate Warfighter Need (IWN)
IWNs are a subset of JUONs
Designated IWNs by the JRAC
Enhanced visibility to OSD and to the DepSecDef
The goal is 120 Days or less
Immediate Warfighter Needs (IWNs) are a subset of JUONs, designated as IWNs by the Joint Rapid Acquisition Cell (JRAC). IWNs have a materiel or logistics solution that must be resolved within 120 days or less. This special category confirms an added emphasis on the timely resolution of this urgent operation need and enhanced visibility to the Office of the Secretary of Defense (OSD) and to the Deputy Secretary of Defense.

10. Urgent Solutions Must consider full-range of DOTMLPF solutions
Must be technologically feasible and affordable
Must be supported by viable CONOPs for fielding, training and sustaining
Cannot require extensive research, development and testing
Validated, resourced and fielded outside of established JCIDS and acquisition processes

11. JUON Approval J8 coordinates with the sponsoring COCOM
6/11/2018
J8 coordinates with the sponsoring COCOM
J8 advises the JROC of the validity of the JUON
If the JUON is valid, J8 provides a memo to the JRAC
Initial analysis of potential solutions
Recommendation for initial sponsorship
If the JUON is not valid:
The JRAC explains this position and recommends alternatives

12. Inherent Risks
6/11/2018
Solution Failure – rapid fielding may result in a solution that does not perform as planned
Short-term success may not meet longer-term needs
Inadequate sustainment planning:
May result in requirements for multiple upgrades or for more costly improvements
Issues if we must transition to a new sustainer other than the initial provider
Short learning curve
Transition to Program of Record (PoR) will require backward development of required DoD 5000 documentation
Perfect case of this is MRAP…. Talking point… great example.

13. Transition to Program of Record (PoR)
6/11/2018
Who decides if a solution to an Urgent Operational Need needs to enter the formal acquisition process?
ACAT I – Defense Acquisition Executive (DAE) makes the PoR decision
ACAT II or below – Component Acquisition Executive (CAE) / Service Acquisition Executive (SAE) makes the PoR decision
May need Material Development Decision (MDD) depending on:
Status of procurement
If the fielded solution needs additional development
Funding for additional quantities and sustainment is Service responsibility
Spell out acronyms… first time seeing a few of them
Last bullet is first bullet ACAT bullets as sub bullets…Move it
bullet key point is the May need to enter the formal acq and req process

14. Backup Slides

15. Military Service Rapid Response Procedures
Army: Operational Needs Statement (ONS). Initiated thru operational commander’s chain-of-command, endorsed by 06 or higher, submitted via SIPRNet to HQDA (DCS G-3/5/7) (AR 71-9)
Navy & Marine Corps: Urgent Need Process (UNP). Initiated via Service chain-of-command. Certified by Naval Component Commander or Marine Corps component commander of supported COCOM (SECNAVNOTE 5000).
Air Force: Urgent Operational Need from Warfighting Commander to lead MAJCOM (AFI )
Army (AR 71-9, 28 Dec 2009): Operational Needs Statement (ONS). Submitted through the operational commanders chain of command, endorsed by a O–6/Colonel or higher for DCS, G–3/5/7 validation and sourcing. ONS will be submitted using the equipment common operating picture (ECOP) collaborative planning information technology system. ECOP is a SIPRNET, collaborative web-based database and documentation library for requesting and sourcing materiel and nonmateriel solutions to urgent warfighter needs. Operational field commanders submit and track ONS and equipment sourcing documents (ESD) submitted.
Navy & Marine Corps (SECNAVNOTE 5000, DON Urgent Need Process, 12 March 2009): An urgent need is an exceptional request from a Navy or Marine Corps component commander for an additional warfighting capability critically needed by operating forces conducting combat or contingency operations. Failure to deliver the capability requested is likely to result in the inability of units to accomplish their missions or increases the probability of casualties and loss of life. Also, see MCO B, 10 Mar 2008, Urgent Universal Need Statement Processing.
Air Force (AFI , Rapid Response Process,12 June 2008): Urgent Operational Need (UON) process begins when a Warfighting Commander identifies a capability gap/ shortfall that could result in loss of life and/or prevent mission accomplishment and requests Air Force assistance. The lead MAJCOM validates the UON and determines the most expeditious and effective solution. UONs may be answered by the lead MAJCOM using any one of several different processes, of which Combat Capability Documents (CCD) and the Rapid Response Process (RRP) is only one. The MAJCOM usually documents UON requirements with an AF Form 1067, Modification Proposal, or a CCD; however, other requirements documents may be used. A CCD is used when the MAJCOM requires CSAF assistance with the reprogramming or identification of funds and/or PMD actions.

16. U.S. Special Operations Command Rapid Response Process
USSOCOM Combat Mission Need Statement (C-MNS) supports urgent new or existing materiel needs
Operational unit prepares the C-MNS
C-MNS endorsed by Theater Special Operations Command (TSOC) Commander and USSOCOM component
HQ USSCOM forms rapid response team to rapidly identify, validate, approve and field a solution.
Normally fields new or existing materiel within 180 days of C-MNS approval.
The USSOCOM Combat Mission Need Statement (C-MNS) process, documented in USSOCOM Directive 71-4, “Combat Mission Need Statement (CMNS) Process,” supports urgent and compelling new or existing materiel needs identified during preparation for or active special operations force (SOF) combat and/or contingency operations. A C-MNS must satisfy at least one of two criteria: (1) critical shortfall on the overall success of the mission (mission failure); or (2) critical combat survivability deficiency (loss of life). The C-MNS process supports expeditious acquisition of new or existing materials, normally fielded within 180 days of C-MNS approval. The solution must be sustainable through duration of combat or contingency operations. C-MNS materials are no longer maintained or sustained after the operation unless a capability document is approved in accordance with Directive C-MNS approval includes resourcing to finance a rapid capability solution affordably. A C-MNS is prepared by the operational unit in the field, endorsed by the theater special operation command (TSOC) commander and endorsed by the USSOCOM component for USSOCOM validation and approval. Although the process parallels the JCIDS process in format, the C-MNS does not substitute for this process. Upon C-MNS receipt, a HQ USSOCOM rapid response team is formed from subject matter experts in each USSOCOM staff directorate and applicable components to identify, validate, approve and field a solution rapidly.

17. What situations call for a rapid response?
Combat-related conflict or crisis
Unforeseen military requirements
Must resolve as soon as possible
Life Threatening or Mission Threatening Situations
All of the above

18. Who Initiates a JUON? A Service Theater Commander
A Joint Force Commander
A Theater Unit Commander
A Service Senior Acquisition Executive

19. What is the solution resolution goal for an IWN?
120 Days
180 Days
90 Days
240 Days