Joint Capabilities Integration and Development System

Last updated

The Joint Capabilities Integration and Development System (JCIDS) is the formal United States Department of Defense (DoD) process which defines acquisition requirements and evaluation criteria for future defense programs. [1] JCIDS was created to replace the previous service-specific requirements generation system that allowed redundancies in capabilities and failed to meet the combined needs of all US military services. In order to correct these problems, JCIDS is intended to guide the development of requirements for future acquisition systems to reflect the needs of all five services (Army, Navy, Marine Corps, Space Force and Air Force) by focusing the requirements generation process on needed capabilities as requested or defined by one of the US combatant commanders. In an ideal implementation of the JCIDS process, regional and functional combatant commanders give early and continuous feedback into the acquisition and sustainment processes to ensure their current and evolving requirements are known and met.

Contents

History

JCIDS was developed under the direction of Secretary of Defense Donald Rumsfeld to address shortfalls in the United States Department of Defense (DoD) requirements generation system identified by the U.S. Joint Chiefs of Staff. These shortfalls were identified as: not considering new programs in the context of other programs, insufficiently considering combined service requirements and ineffectively prioritizing joint service requirements, and accomplishing insufficient analysis. The drive to create JCIDS was born out of a March 2002 Secretary of Defense memorandum to the Vice Chairman of the Joint Chiefs of Staff requesting a study on alternative ways to evaluate requirements. The Chairman of the Joint Chiefs of Staff (CJCS) approved the most recent JCIDS Instruction on 23 January 2015 [2] and its accompanying manual was released on 12 February 2015. CJCS Instruction (CJCSI) 3170.01I provides a top-level description of the process and outlines the organizational responsibilities. The JCIDS Manual defines performance attributes, key performance parameters, validation and approval processes, and associated document content. [3]

Methodology

The central focus of JCIDS is to address capability shortfalls, or gaps as defined by combatant commanders. Thus, JCIDS is said to provide a capabilities-based approach to requirements generation. The previous requirements generation system focused on addressing future threat scenarios. While understanding the risks associated with future threat postures is necessary to develop effective weapons systems, a sufficient methodology requires a joint perspective which can both prioritize the risk associated with future threats and consider operational gaps in the context of all the services. If requirements are developed in this joint context, there is simultaneously a smaller chance of developing superfluously overlapping systems and a greater probability that weapons systems would be operational with one another (i.e. common communication systems, weapons interfaces, etc.). The Joint Capability Areas were established in conjunction with JCIDS in order to provide for a common lexicon throughout the US Department of Defense. Another major emphasis of JCIDS is to consider whether a solution to a potential operational gap requires the development of a physical system (a materiel solution) or a procedural or training based solution (a non-materiel solution). In this sense, the JCIDS process provides a solution space that considers solutions involving any combination of doctrine, organization, training, materiel, leadership and education, personnel and facilities (DOTMLPF). The Joint Staff, J6, Joint Deployable Analysis Team (JDAT) supports JCIDS by providing recommendations based on quantifiable data. JDAT collects and analyzes data and provides observations, findings, conclusions, and recommendations to identify policy, Joint doctrine, tactics, techniques, and procedures (TTP); and materiel solutions and products that promote capability improvement. [4] Since combatant commanders define requirements in consultation with the Office of the Secretary of Defense (OSD), they are able to consider gaps in the context of strategic direction for the total US military force and influence the direction of requirements earlier in the acquisition process.

The JCIDS process starts with the development of joint integrating concepts and the capability they imply from the US Secretary of Defense (SecDef) and combatant commanders. From the joint integrating concepts, the joint chiefs of staff refine requirements and develop an integrated priority list via a joint quarterly readiness review. Military judgement is further applied by the Joint Requirements Oversight Council (JROC) (Composed of the Vice Chairman of the Joint Chiefs of Staff and other service vice chiefs) which validates requirement attributes and determines how to produce the required capability. From the JROC, the JCIDS process maps current programs against the standard as defined by JROC attributes to determine if gaps exist in providing the concepts defined by the SecDef and combatant commanders.

JCIDS analysis

In order to assess US capability to execute Joint Integrating Concepts there are three phases to capabilities-based assessment: a functional area analysis, a functional needs analysis, and a functional solutions analysis. The functional area analysis identifies operational tasks, conditions and standards needed to accomplish objectives. The Functional Needs Analysis assesses the ability of current and programmed capabilities to accomplish the tasks identified in the functional area analysis.

The end product of these first two levels of analysis is a list of capability gaps. Functional solutions analysis (FSA) evaluates solutions from an operational perspective across the DOTMLPF spectrum. The FSA results in a list of potential need-based solutions and is further divided into three subcomponents: non-materiel analysis (DOT_LPF), materiel solutions (ideas for materiel approaches, or IMA, analysis) and the Analysis of Materiel Approaches to determine the best materiel or combination of approaches to produce the best capability.

The final analysis is the Post-Independent Analysis which reviews the previous three functional analyses and selects an approach or approaches that best close the capability gaps. The original proposal sponsor documents a recommended change or produces an Initial Capabilities Document for a system.

A proposal receives one of three designations based on the degree in which it applies to all three services: "JROC Interest", "JCB Interest", or "Joint Information". "JROC Interest" programs apply to any program the JROC decides to review and all Acquisition Category (ACAT) 1/1A programs. [Based on 31 Aug 2018 JCIDS Manual.]

Army ACATs

The ASA(ALT) uses the Acquisition Category (ACAT) I, II, III, IV in its Weapon System Handbook. [5]

Output documents

Three documents are the output of the JCIDS analysis which together define needed capabilities, guide materiel development and direct the production of capabilities. Each of these documents supports a major design approval decision each with gradual improving design maturity A, B or C. The sponsor is the single focal point for all three documents. The Initial Capabilities Document (ICD) defines the capability need and where it fits in broader concepts, ultimately supporting the milestone A decision. (The Milestone A decision approves or denies a concept demonstration to show that a proposed concept is feasible). When the technology development phase is complete, a Capability Development Document (CDD) is produced which provides more detail on the materiel solution of the desired capability and supports Milestone B decisions. (The milestone B approval starts the engineering and manufacturing development phase). Most important, the CDD also defines the thresholds and objectives against which the capability will be measured. After approval, the CDD guides the Engineering and Manufacturing Development Phase of the acquisition process. The Capability Production Document (CPD) supports the Milestone C decision necessary to start the Production & Deployment Phase to include low-rate initial production and operational tests. The CPD potentially refines the thresholds from the CDD based on lessons learned during the Engineering and Manufacturing Development Phase.

Actors

The DoD component that oversees the JCIDS analyses acts as the sponsor. The sponsor also evaluates the affordability of various proposals and approaches determined in the study. Moreover, the sponsor coordinates with non-DoD departments and agencies on interagency capability matters.

The Joint Staff, J8, Vice Director (VDJ-8), is the gatekeeper of the JCIDS process. The gatekeeper assigns the Joint Potential Designation (JPD), and assigns lead and supporting functional capabilities boards FCBs, and performs an initial review. The gatekeeper initially reviews all proposals, and then designates the JPD, and which Functional Capability Board and Joint Warfighting Capability Assessment Teams will receive the proposal. The Joint Potential Designation is based on input from Joint Forces Command, each of the Joint Warfighting Capability Assessment teams, and other elements of the Joint Staff. The gatekeeper periodically reevaluates the Joint Potential designation throughout the process because changes in the proposed capability may require it to change as well.

When the gatekeeper has completed the initial review, she or he assigns the analysis to a functional capabilities board (FCB). This board replaces the joint requirements panel (JRP) from the previous system, with expanded responsibilities and membership. The FCB is responsible for ensuring that new capabilities are developed with a joint warfighting context; ensuring that proposals are consistent with the Joint Force as described in the Joint Operating Concepts; validating Joint Impact proposals; organizing, analyzing and prioritizing capabilities proposals; supervising development and updating of functional concepts; and ensuring that integrated architectures are reflective of their functional area.

The JROC now charters six FCBs (oversight authority is in parentheses):

  1. C4/Cyber (J6)
  2. Battlespace Awareness (J2)
  3. Force Application (J8)
  4. Logistics (J4)
  5. Protection (J8)
  6. Force Integration (J8)

The head of the FCBs will probably be at least the O-7 or equivalent level. Membership in an FCB goes beyond the traditional membership of the services under the previous system in the JRP. The FCBs include O-6 or GS-15 equivalent representatives of the Services, the combatant commanders, key OSD staff, and representatives from the space and intelligence communities. This expanded membership gives the FCB Chairman the tools to make better and more broadly informed recommendations on the capability proposals to the JROC. It also involves the entire acquisition community early in the process. Other FCBs can be created by the JROC to oversee capability development and integration in the other functional areas.

Joint warfighting capability assessment teams (JWCAs) coordinate with and aid the sponsor to prevent needless overlapping of proposals across components and to ensure that joint capability gaps are properly addressed. They support the gatekeeper in determining the Joint Potential Designation and the lead and/or supporting JWCAs for each JCIDS document in the process. They also work with other JWCAs to make sure that analyses do not overlook any joint aspects.

See also

Related Research Articles

<span class="mw-page-title-main">Requirements analysis</span> Engineering process

In systems engineering and software engineering, requirements analysis focuses on the tasks that determine the needs or conditions to meet the new or altered product or project, taking account of the possibly conflicting requirements of the various stakeholders, analyzing, documenting, validating and managing software or system requirements.

In product development and process optimization, a requirement is a singular documented physical or functional need that a particular design, product or process aims to satisfy. It is commonly used in a formal sense in engineering design, including for example in systems engineering, software engineering, or enterprise engineering. It is a broad concept that could speak to any necessary function, attribute, capability, characteristic, or quality of a system for it to have value and utility to a customer, organization, internal user, or other stakeholder. Requirements can come with different levels of specificity; for example, a requirement specification or requirement "spec" refers to an explicit, highly objective/clear requirement to be satisfied by a material, design, product, or service.

<span class="mw-page-title-main">United States Strategic Command</span> Unified combatant command based in Nebraska

The United States Strategic Command (USSTRATCOM) is one of the eleven unified combatant commands in the United States Department of Defense. Headquartered at Offutt Air Force Base, Nebraska, USSTRATCOM is responsible for strategic nuclear deterrence, global strike, and operating the Defense Department's Global Information Grid. It also provides a host of capabilities to support the other combatant commands, including integrated missile defense; and global command, control, communications, computers, intelligence, surveillance, and reconnaissance (C4ISR). This command exists to give "national leadership a unified resource for greater understanding of specific threats around the world and the means to respond to those threats rapidly".

<span class="mw-page-title-main">Department of Defense Architecture Framework</span> Enterprise architecture framework

The Department of Defense Architecture Framework (DoDAF) is an architecture framework for the United States Department of Defense (DoD) that provides visualization infrastructure for specific stakeholders concerns through viewpoints organized by various views. These views are artifacts for visualizing, understanding, and assimilating the broad scope and complexities of an architecture description through tabular, structural, behavioral, ontological, pictorial, temporal, graphical, probabilistic, or alternative conceptual means. The current release is DoDAF 2.02.

<span class="mw-page-title-main">The Research and Analysis Center</span> Agency of the United States Army

The Research and Analysis Center (TRAC), formerly the TRADOC Analysis Center, is an analysis agency of the United States Army. TRAC conducts research on potential military operations worldwide to inform decisions about the most challenging issues facing the Army and the Department of Defense (DoD). TRAC relies upon the intellectual capital of a highly skilled workforce of military and civilian personnel to execute its mission.

The Rapid Equipping Force (REF) was a United States Army organization headquartered in Fort Belvoir, Virginia. The organization was charged with quickly providing Army units deployed globally with innovative government off-the-shelf and commercially available solutions that address urgent requirements within 180 days or less. The REF was able to do this through unique authorities and by maintaining a presence near the point of need. REF personnel were positioned in Iraq, Afghanistan, and Kuwait and mobile laboratories are available for quick solutions. Additionally, the REF empowered the Army at a grassroots level, enabling individual soldiers to communicate needs directly through simple request forms.

<span class="mw-page-title-main">Asymmetric Warfare Group</span> Military unit

The Asymmetric Warfare Group was a United States Army unit created during the War on Terrorism to mitigate various threats with regard to asymmetric warfare. The unit was headquartered at Fort Meade, Maryland and had a training facility at Fort A.P. Hill, Virginia. The unit provided the linkage between Training and Doctrine Command (TRADOC) and the operational Army, and reported directly to the commanding general of TRADOC.

Capability management is a high-level management function, with particular application in the context of defense.

DOTMLPF is an acronym for doctrine, organization, training, materiel, leadership and education, personnel, and facilities. It is used by the United States Department of Defense and was defined in the Joint Capabilities Integration Development System, or JCIDS Process as the framework to design what administrative changes and/or acquisition efforts would fill a capability need required to accomplish a mission. Because combatant commanders define requirements in consultation with the Office of the Secretary of Defense (OSD), they are able to consider gaps in the context of strategic direction for the total US military force and influence the direction of requirements earlier in the acquisition process, in particular, materiel.

<span class="mw-page-title-main">Military acquisition</span>

Military acquisition or defense acquisition is the "bureaucratic management and procurement process", dealing with a nation's investments in the technologies, programs, and product support necessary to achieve its national security strategy and support its armed forces. Its objective is to acquire products that satisfy specified needs and provide measurable improvement to mission capability at a fair and reasonable price.

Live, Virtual, & Constructive (LVC) Simulation is a broadly used taxonomy for classifying Modeling and Simulation (M&S). However, categorizing a simulation as a live, virtual, or constructive environment is problematic since there is no clear division among these categories. The degree of human participation in a simulation is infinitely variable, as is the degree of equipment realism. The categorization of simulations also lacks a category for simulated people working real equipment.

A capability, in the systems engineering sense, is defined as the ability to execute a specified course of action. A capability may or may not be accompanied by an intention. The term is used in the defense industry but also in private industry.

<span class="mw-page-title-main">Fleet Electronic Warfare Center</span> Echelon IV component of the U.S. Navy

The Fleet Electronic Warfare Center (FEWC) is a subordinate organization of the Naval Network Warfare Command (NNWC), which was established in 2008 to be the center for US Navy fleet electronic warfare (EW) operational and tactical issues. It is currently located at Navy Information Dominance Forces (NIDF) Headquarters, in Suffolk, VA as an independent directorate.

The Analysis of Alternatives (AoA) in the United States is a requirement of military acquisition policy, as controlled by the Office of Management and Budget (OMB) and the United States Department of Defense (DoD). It ensures that at least three feasible alternatives are analyzed prior to making costly investment decisions. The AoA establishes and benchmarks metrics for Cost, Schedule, Performance (CSP) and Risk (CSPR) depending on military "needs" derived from the Joint Capabilities Integration Development System process. It moves away from employing a single acquisition source to the exploration of multiple alternatives so agencies have a basis for funding the best possible projects in a rational, defensible manner considering risk and uncertainty.

<span class="mw-page-title-main">Unmanned Carrier-Launched Airborne Surveillance and Strike</span> 2013–2016 United States Navy development program

The Unmanned Carrier-Launched Airborne Surveillance and Strike (UCLASS) was a United States Navy program to develop an autonomous carrier-based unmanned combat aerial vehicle providing an unmanned intelligence and strike asset to the fleet. After debate over whether the UCLASS should primarily focus on stealthy bombing or scouting, the Pentagon instead changed the program entirely into the Carrier-Based Aerial-Refueling System (CBARS) to create a UAV for aerial refueling duties to extend the range of manned fighters, which lead to the Boeing MQ-25 Stingray.

Key Performance Parameters (KPPs) specify what the critical performance goals are in a United States Department of Defense (DoD) acquisition under the JCIDS process.

<span class="mw-page-title-main">United States Army Futures Command</span> United States Army acquisition command

The United States Army Futures Command (AFC) is a United States Army command that runs modernization projects. It is headquartered in Austin, Texas.

The National Defense Strategy (NDS) is produced by the United States Office of the Secretary of Defense (OSD) and is signed by the United States Secretary of Defense as the United States Department of Defense's (DoD) capstone strategic guidance. The NDS translates and refines the National Security Strategy (NSS) (produced by the U.S. President's staff and signed by the President) into broad military guidance for military planning, military strategy, force posturing, force constructs, force modernization, etc. It is expected to be produced every four years and to be generally publicly available.

<span class="mw-page-title-main">United States Army Acquisition Corps</span> Officer / NCO corps of the U.S. Army Acquisition Workforce

The United States Army Acquisition Corps (AAC) is the officer / NCO corps of the United States Army Acquisition Workforce (AAW), a branch which includes civilians, officers, and NCOs. The Acquisition Corps is composed of army officers who serve in acquisition, a specialized form of product development, fielding, and support and Noncommissioned Officers who specialize in Contracting, Level I Program Management and Purchasing. These officers begin their careers in the other branches of the army for eight years, after which they may elect the Acquisition branch as their career as assistant program managers (APMs), program managers (PMs), and program executive officers (PEOs). The Noncommissioned Officers (NCOs) are reclassified in the Army Acquisition NCO Corps after serving 7-10 years in their respective enlisted career management fields, and serve primarily in the Army Acquisition Career Management Field - 51 and (MOS) 51C. 4% percentage of the Army Acquisition Officers serve among the 40,000 members of the army acquisition workforce, 6% in MOS 51C - Acquisition, Logistics and Technology Contracting Noncommissioned Officer, and the remainder 90% percentage consist largely of Department of the Army civilians.

In the US Army, Patrick Matlock is the Deputy Chief of Staff for Operations, Plans, and Training (G-3/5/7) serving on Army Staff for operations (G-3), plans (G-5), and training (G-7). Both G-8 and G-3/5/7 sit on the Army Requirements Oversight Council (AROC), chaired by the Chief of Staff of the Army (CSA).

References

  1. ↑ "Operation of the Joint Capabilities Integration and Development System", Chairman of the Joint Chiefs of Staff Instruction (CJCSI) 3170.01H, DoD, 10 January 2012 "Archived copy" (PDF). Archived from the original (PDF) on 2007-02-04. Retrieved 2007-02-04.{{cite web}}: CS1 maint: archived copy as title (link)
  2. ↑ "Joint Capabilities Integration and Development System (JCIDS)", CJCSI 3170.01I 23 January 2015
  3. ↑ "JCIDS Manual 12 February 2015, including errata as of 18 Dec 2015"
  4. ↑ RDT&E Budget Item Justification
  5. ↑ ASA(ALT) Weapon Systems Handbook 2018 update Page 32 lists how this handbook is organized. 440 pages.
    • By Modernization priority
    • By Acquisition or Business System category (ACAT or BSC). The Weapon systems in each ACAT are sorted alphabetically by Weapon system name. Each weapon system might also be in several variants (Lettered); a weapon system's variants might be severally and simultaneously in the following phases of its Life Cycle, namely — °Materiel Solution Analysis; °Technology Maturation & Risk Reduction; °Engineering & Manufacturing Development; °Production & Deployment; °Operations & Support
    • ACAT I, II, III, IV are defined on page 404
This page is based on this Wikipedia article
Text is available under the CC BY-SA 4.0 license; additional terms may apply.
Images, videos and audio are available under their respective licenses.