I-13. Approval

a. The USSOCOM SOCREB/CDB supports the DCINCSOC in exercising approval authority for all DOTML-P & F (SOF) requirements. As such, the SOCREB/CDB develops approval/disapproval and implementation recommendations.

b. Following approval, requirements containing PSAP, SAP, and FP information are integrated into the Strategic Planning Process (SPP) to compete for MFP-II resources and acquisition.

GLOSSARY

SECTION I--ABBREVIATIONS AND ACRONYMS

ACAT Acquisition Category

ADM Acquisition Decision Memorandum

ADPE Automated Data Processing Equipment

AFSOC Air Force Special Operations Command

AIS Automated Information Systems

AoA Analysis of Alternatives

APB Acquisition Program Baseline

BOD Board of Directors

BOIP Basis of Issue Plan

CBPL Capability Based Program List

CDB Center Directors Board

C4I Command, Control, Communications, Computer and Intelligence

C4IAS Command, Control, Communications, Computer and Intelligence

Automated Systems

C4ISR Command, Control, Communications, Computers, Intelligence, and

Strategic Reconnaissance

CAIV Cost as an Independent Variable

CRD Capstone Requirement Document

CIO Chief Information Officer

CJCS Chairman, Joint Chiefs of Staff

C-MNS Combat-Mission Need Statement

COE Common Operating Environment

CONOPS Concept of Operations

CORB Command Operations Review Board

COTS Commercial Off-The-Shelf

DCINC Deputy Commander in Chief

DOC Desired Operational Capability

DOD Department of Defense

DOTML-P & F Doctrine, Organization, Training, Materiel, Leadership Development,

Personnel, and Facilities

DPG Defense Planning Guidance

DTIC Defense Technical Information Center

ECP Engineering Change Proposal

FTR FAST TRACK REQUIREMENT

FOC Full Operational Capability

GIG Global Information Grid

ILS Integrated Logistics Support

IOC Initial Operational Capability

IPL Integrated Priority List

IPT Integrated Product Team

IT Information Technology

JPD Joint Potential Designator

JRB Joint Requirements Board

JROC Joint Requirements Oversight Council

JTA Joint Technical Architecture

JWCA Joint Warfighting Capabilities Assessment

JSOC Joint Special Operations Command

KPP Key Performance Parameters

LCCE Life Cycle Cost Estimate

MAA Mission Area Analysis

MDA Milestone Decision Authority

MFP Major Force Program

MTOE Modified Table of Equipment

MNA Mission Need Assessment

MNS Mission Need Statement

MOE Measures of Effectiveness

MS Milestone

NAVSPECWARCOM Naval Special Warfare Command

NDI Non-Developmental Item

N-MNS Non-materiel Mission Need Statement

NMS National Military Strategy

NSS National Security Systems

ORD Operational Requirements Document

P-IPT Program-Integrated Program Team

POM Program Objective Memorandum

PPBS Planning, Programming, and Budgeting System

P-RCL Prioritized Required Capabilities List

RD&A Research, Development and Acquisition

R-IPT Requirements-Integrated Product Team

RRT Rapid Response Team

SAM System Acquisition Manager

SIO Senior Intelligence Officer (SIO)

SME Subject Matter Expert

SO Special Operations

SOCREB Special Operations Command Requirements Evaluation Board

SO-peculiar Special Operations Peculiar

SOAE Special Operations Acquisition Executive

SOAL Special Operations Acquisition and Logistics Center

SOF Special Operations Forces

SOJA USSOCOM Staff Judge Advocate

SO-MGL Special Operations Mission Guidance Letter

SOOP Special Operations Plans and Policy Center (Add Requirements)

SOOR Command Operations Review Board

SORR Special Operations Force Structure, Resources, & Strategic Assessments

Center (Delete Requirements)

SPG Strategic Planning Guidance

SPP Strategic Planning Process

STA System Threat Assessment

TA Table of Allowance

TOE Table of Equipment

TSOC Theater Special Operations Command

USASOC U.S. Army Special Operations Command

USCINCSOC Commander in Chief, United States Special Operations Command

USSOCOM United States Special Operations Command

SECTION II--DEFINITIONS/TERMS

Acquisition Categories (ACAT). Categories established to facilitate decentralized decision making, execution, and compliance with statutory imposed requirements. The categories determine the level of review, decision authority, and applicable procedures.

Automated Information System (AIS). A combination of computer hardware and software, data, or telecommunications, that performs functions such as collecting, processing, transmitting, and displaying information. Excluded are computer resources, both hardware and software, that are physically part of, dedicated to, or essential in real time to the mission performance of weapon systems.

Basis of Issue Plan (BOIP). A requirements document that states the planned placement of quantities of new equipment, as well as the reciprocal displacement of equipment and personnel. The BOIP identifies mission essential wartime requirements for inclusion into organizations based on changes of doctrine, personnel, or materiel. BOIP are used as input for concept studies, life cycle cost estimates, and trade-off analyses. The BOIP is used to plan the equipment, facilities, initial provisioning, and personnel required to support new or improved materiel systems. (Adapted from U.S. Army Regulation 71-9)

Capstone Requirements Document. A document that contains capabilities-based requirements that facilitates the development of individual ORDs by providing a common framework and operational overarching requirements for a system-of-systems or a family-of-systems. (CJCSI 3170.01A)

Core Capability. The core capability includes the following: 1) The set of functions that define a significant, stand-alone, operationally effective, and suitable military capability such that, should no further development occur, the user will have received a significant capability, and 2) The integral characteristics of the system that, if altered in subsequent increments, would lead to significant redesign of the evolutionary system. (CJCSI 3170.01A)

Combat Mission Need Statement (C-MNS). An expedited process for documenting and staffing urgent, time-sensitive requirements. It is used to satisfy deficiencies that arise during combat or crisis operations or when the Commander of a USSOCOM Component Command, JSOC, TSOC, or theater CINC believes urgent and compelling acquisition procedures are necessary.

Commercial Off-The-Shelf (COTS). Commercial items that require no unique government modifications or maintenance over the life cycle of the product to meet the needs of the procuring agency.

Concept of Operations (CONOPS). A verbal or graphic statement, in broad outline, of a commander's assumptions or intent in regard to an operation or series of operations. The concept of operations frequently is embodied in campaign plans and operation plans; in the latter case, particularly when the plans cover a series of connected operations to be carried out simultaneously or in succession. The concept is designed to give an overall picture of the operation. It is included primarily for additional clarity of purpose. Frequently, it is referred to as commander's concept. (Joint Publication 1-02).

Concept Studies. Studies conducted to evaluate and define the feasibility of alternative concepts. They provide the basis for assessing the relative merits of alternative concepts at the Milestone B decision point.

Critical System Characteristics. A special category of characteristics including electromagnetic pulse hardening, transportability, interoperability, electronic counter-countermeasures, etc. These characteristics are historically design, cost, and risk drivers, and therefore, they require early identification for cost-performance tradeoffs. (DoD Regulation 5000.2-R.) Critical system characteristics are those design features that determine how well the proposed concept of system will function in its intended operational environment. Selected critical system characteristics in the ORD may be included in the APB as key performance parameters. (CJCSI 3170.01A.)

Desired Operational Capability (DOC). A concept-based statement of the ways and means to satisfy a Joint Force Commander’s capability requirements. A fully articulated DOC identifies subordinate tasks, associated conditions, and criteria for measurement (ref CJCSI 3010.02A).

Documentation. The formal preparation of the required and standardized documents as specified in CJCSI 3170.01A, and DoDI 5000.2.

Experimentation. An iterative approach involving the discipline of the Scientific Method that includes rigorous management of controls and variables to provide quantifiable, repeatable results. Experiments are part of the concept and capabilities exploration and assessment process. (Ref CJCSI 3010.02A)

Evolutionary Acquisition. Evolutionary acquisition is a streamlined acquisition strategy that fields a core capability, with a modular open structure and provides for additional future increments in capability upgrades.

Family of Systems (FoS) - A set or arrangement of independent systems that can be arranged or interconnected in various ways to provide different capabilities. The mix of systems can be tailored to provide desired capabilities dependent on the situation.

Integrated Product Team (IPT). Team composed of representatives from appropriate functional disciplines working together to build successful programs and enabling decision-makers to make the right decisions at the right time. USSOCOM uses two types of IPTs, Requirements-IPT (R-IPT) and Program-IPT. The type of IPT is dependent on nature, focus and type of decisions required. The R-IPT is formed following approval of a N-MNS, or MNS.

Its efforts are primarily focused on activities necessary to define and integrating a DOTML-P &F solution set and develop the ORD (and CRD, if appropriate) Following approval of the ORD, the IPT transitions to a P-IPT and efforts and activities focus on program acquisition and ORD updates. (adapted from DoDD 5000.1 for USSOCOM).

Integrated Priority List (IPL). An OSD-Directed document prepared by each CINC outlining the CINC's programming concerns for the upcoming programming and budgeting cycles; submitted biennially usually in October prior to beginning each programming cycle. It is an unconstrained list of the CINC's high priority needs, prioritized across service and functional lines and with consideration of reasonable fiscal constraints. IPLs are intended to provide visibility for those few key problem areas that, in the judgment of a CINC, require the highest priority attention by the Department of Defense in the development of future programs. USCINCSOC submits an IPL for those areas of concern for which he does not have programming and budget authority. (Non-MFP-11).

Joint Potential Designator (JPD). An indicator resulting from an evaluation of an MNS for applicability to USSOCOM component commands, JSOC and/or Service(s), used to describe the expected level of multi-component involvement.

Joint Program. Any acquisition system, subsystem, component, or technology program that involves formal management or funding by more than one USSOCOM component commands, JSOC and/or Service.

Key Performance Parameters. Capabilities and characteristics, including selected critical system characteristics, so significant that failure to meet the threshold is cause for the concept or system selection to be reevaluated or the program to be reassessed or terminated. Key performance parameters are extracted from the Operational Requirements Document (ORD) and included in the Acquisition Program Baseline (APB) at each milestone.

Lead Component. The component command or JSOC that has been formally designated as lead for a joint program. The lead component is responsible for all-common documentation, periodic reporting, and funding actions. May also be designated as the user representative.

Milestone Decision Authority (MDA). The individual designated in accordance with criteria established by the Under Secretary of Defense for Acquisition to approve entry of an acquisition program into the next phase. (DoD Directive 5000.1)

Military Requirement. An established need justifying the timely allocation of resources to achieve a capability to accomplish approved military objectives, mission, or tasks. Also called operational requirement. (Joint Pub 1-02)

Minimum Acceptable Operational Requirement. The value for a particular parameter that is required to provide a system capability that will satisfy the validated mission need. Also known as the performance threshold.

Mission Area Analysis (MAA). A process by which SOF warfighting capabilities by are assessed by identifying military objectives in the Defense Planning Guidance (DPG) and USSOCOM Strategic and Supplemental Guidance (SPG). SOF modernization objectives are identified with new or revised doctrine, training, organization, materiel, and/or leader development. The MAA uses a "strategy to task" methodology to analyze SOF’s ability to execute the core, essential, and supporting tasks of the USSOCOM Required Capabilities List and their descriptors. (CJCSI 3170.01A)

Mission Deficiency. The inability to accomplish an operational or support task required for the achievement of a military objective.

Mission Need. A deficiency in current capabilities or an opportunity to provide new capabilities (or enhance existing capabilities) through the use of new technologies. They are expressed in broad operational terms by the DoD components. (CJCSI 3170.01A)

Mission Need Analysis (MNA). An analysis designed to assess one's ability to accomplish the tasks identified during the MAA. The Analysis uses a task-to-need methodology to identify mission needs. It can also highlight technological opportunities and identify reliability and maintainability improvements that enhance warfighting capability.

Mission Need Statement (MNS). When a materiel acquisition program may be required, the MNS describes required operational capabilities and constraints to be studied during the Concept Exploration, and Definition Phase. It is a non‑system‑specific statement of operational capability need, written in broad operational terms. (CJCSI 3170.01)

Modification. The alteration, conversion, or modernization of an end item of investment equipment which changes or improves the original purpose or operational capacity in relation to effectiveness, efficiency, reliability or safety of that item.

Need. The identification of a mission need in any of the domains of doctrine, organization, training, leadership development, personnel and facilities that can be satisfied by a material or non-materiel solution. If a materiel solution is envisioned, it is normally documented in a Mission Need Statement (MNS).

Non-Developmental Item (NDI). Any item of supply that is available in the commercial marketplace; any previously developed item of supply that is in use by a department or agency of the United States, a State or local government, or a foreign government with which the United States has a mutual defense cooperation agreement.

Non-Materiel Mission Need Statement (N-MNS). A formatted statement describing a mission need in broad operational terms, that can be satisfied by a change in one or more of the non-materiel domains of doctrine, organization, training, leadership development, personnel, and facilities. The N-MNS is a three-part statement that describes the mission need, the proposed non-materiel solution set, and the impact to any other non-materiel domain.

Objective. An operationally significant increment above the threshold. An objective value may be the same as the threshold when an operationally significant increment above the threshold is not significant or useful.

Operational Requirements Document (ORD). A document describing pertinent quantitative and qualitative performance, operation, and support parameters, characteristics, and requirements for a specific candidate system intended to satisfy a mission need. The ORD documents how a system will be operated, deployed, employed, and supported. Prepared by the user or user's representative at each for each milestone decision beginning with MS B.

Operators. An operational command that employ the acquired system for the benefit of users. Operators may also be users.

Operational Test and Evaluation (OT&E). Testing and evaluation (divided into initial operational test and evaluation and follow-on operational test and evaluation, and generally associated with the first major production decision) conducted in as realistic an operational environment as possible to estimate the prospective system's military utility, operational effectiveness, and operational suitability. In addition, operational test and evaluation provides information on organization, personnel requirements, doctrine, and tactics. Also, it may provide data to support or verify material in operating instructions, publications, and handbooks.

Operational Validation Authority. Designated authority responsible for confirming the user’s identified need and operational requirement. USCINCSOC has designated the Director, Special Operations, Plans and Policy the Operational Validation Authority for all materiel and non-materiel requirements. (CJCSI 3170.01A)

Program Objective Memorandum (POM). A biennial memorandum submitted to the Secretary of Defense (SECDEF) from each Military Department and Defense Agency. It proposes total program requirements for the next 6 years. It includes rationale for planned changes from the approved Future Years Defense Plan (FYDP) baseline within the fiscal guidance issued by the SECDEF.

Proponent. An organization or staff agency that has primary responsibility for subject matter expertise and/or oversight for specified subject area(s) directly related to its primary area(s) of responsibility and interest, or for which it is charged.

Requirement. An established need that justifies the timely allocation of resources to achieve a capability to accomplish approved military objectives, missions, or tasks.

Special Operations (SO)‑peculiar. Equipment, materiel, supplies, and services required for SO Special Operations activities for which there is no Service-common requirement. These are limited to items and services initially designed for, or used by, SOF until adopted for Service-common use by other DoD forces; modifications approved by the Commander in Chief, U.S. Special Operations Command (USCINCSOC) for application to standard items and services used by other DoD forces; and items and services approved by the USCINCSOC as critically urgent for the immediate accomplishment of an SO activity. (DoDD 5100.3, 15 November 1999)

Special Operations (SO) Peculiar Mission Need. A statement of operational capability required to perform an assigned special operations mission or to correct a deficiency in an existing capability to perform the SOF mission. SO‑peculiar mission needs are restricted to those areas that will require Major Force Program‑11 (MFP‑11) funds.

System Capabilities. Measures of performance (such as range, lethality, maneuverability, etc.) needed for a system to accomplish approved military objectives, missions or tasks.

System Characteristics. Design features (such as weight, size, shape, etc.) needed for a system to accomplish approved military objectives, missions, or tasks.

System of Systems. A set or arrangement of systems that are related or connected to provide a given capability. The loss of any part of the system will degrade the performance or capabilities of the whole. (CJCSI 3170.01A)

System Threat Assessment (STA). The basic authoritative threat assessment, tailored for and focused on, a particular acquisition categories I through IV program. It describes the threat to be countered and the projected threat environment. The STA may be a stand-alone document or the threat assessment contained in the Operational Requirements Document (ORD). The threat information is based on Defense Intelligence Agency validated documents.

Threshold. A threshold is the minimum acceptable operational value below which the utility of the system becomes questionable. See Key Performance Parameters. (CJCSI 3170.01).

User Representative. A command or agency that has been formally designated by proper authority to represent single or multiple users in the requirements and acquisition processes. Acts as the focal point for developing, coordinating, and overseeing the detailed materiel and non-materiel needs of the operator.

Validation. The review of documentation by an operational authority other than the user to confirm the mission need in the case of a Mission Need Statement (MNS), and the operational requirement in the case of the Capstone Requirements Document (CRD) and Operational Requirements Document (ORD). As a minimum, the review of the MNS also confirms that a non-materiel solution (set) is not feasible, determines the potential for joint initiatives/programs, and forwards a recommendation to the USSOCOM approval authority. The review of the CRD/ORD confirms the operational capability will satisfy the mission need and includes an assessment of the impact on DOTML-P &F elements within the overall requirement. Review of non-materiel need statements confirms the mission need and assesses the impact to other requirement categories (DOTML-P &F). Validation is a necessary, step preceding approval, and is independent of resourcing considerations. (adapted from CJCSI 3170.01A for USSOCOM)

Weapon System. Items that can be used directly by the armed forces to carry out combat missions and that cost more than $100,000 or for which the eventual total procurement cost is more than $10,000,000. Such item does not include commercial items sold in substantial quantities to the general public (See Title 10, U.S. Code, Section 2403, "Major weapon systems: contractor guarantees")

SECTION III--REFERENCES

Title 10, United States Code (various sections).

CJCSI 3100.01, The Joint Strategic Planning System, 1 September 1999.

CJCSI 3137.01A, The Joint Warfighting Capabilities Assessment Process, 22 January 1999.

CJCSI 5123.01, Charter of the Joint Requirements Oversight Council, 2 May 1997.

CJCSI Instruction 3170.01A, Requirements Generation System, 20 August 1999.

CJCSI 6212.01B, Interoperability and Supportability on National Security Systems, and Information Technology Systems, 14 May 2000.

CJCS Manual, 3213.02A, Focal Point Communications Procedures, 31 January 1997.

DoD Directive 5000.1, Defense Acquisition, 15 March 1996.

DoD Regulation 5000.2-R, Mandatory Procedures for Major Defense Acquisition Programs (MDAP) and Major Automated Information Systems (MAIS) Acquisition Programs, 15 March 1996.

DoD Directive 5230.24, Distribution Statements on Technical Documents, March, 1987.

DoD Directive 5100.3, Support of the Headquarters of Combatant and Subordinate Joint Commands, 15 November 1999.

JROCM-032-97, JROC Administrative Guide, 31 March 97.

USSOCOM Directive 10‑1, Terms of Reference for Component Commanders, 7 May 93.

DoD Instruction 5205.11, Management, Administration and Oversight of DoD SAPs, 1 July 1997.

USSOCOM Directive 71-2, Force Development Action Plan, 26 February 1997.

USSOCOM Directive 1-9, Strategic Planning Process, 22 May 1997.

USSOCOM Directive 25-1, Information Technology Management, July 2000 (Draft).

USSOCOM Directive 37-8, New Start and Termination Procedures – HQ USSOCOM, July 2000 (Draft).

USSOCOM Directive 70-1, Acquisition Management, 24 November 1999.

USSOCOM Manual 380‑2, Standard Operating Procedures for Special Access Program Operations, 5 September 1997.

USSOCOM Directive 530‑1, Plans and Operations ‑ Operations Security, 12 September 1991 (Currently in revision.).

USSOCOM Directive 700-10, Special Operations Life Cycle Logistics, 13 April 2000.