US Space Command

DEPARTMENT OF DEFENSE USSPACECOM Regulation 57-1
Headquarters United States Space Command
Peterson Air Force Base Colorado 80914-5003 11 March 1992

Operational Requirements

OPERATIONAL REQUIREMENTS SYSTEM
This regulation implements the direction contained in Department of Defense Directive 5000.1
(DODD 5000. 1), Defense Acquisition; Department of Defense Instruction 5000.2 (DoDl 5000.2),
Defense Acquisition Management Policies and Procedures; and Department of Defense Manual
(DoD 5000.2-M), Defense Acquisition Management Documentation and Reports, which take
precedence in the event of conflict with this regulation. It assigns responsibility for preparation,
processing, review, and validation actions to United States Space Command (USSPACECOM)
and its service component commands. It applies to all personnel assigned to Headquarters (HQ)
USSPACECOM, the Joint Strategic Defense Planning Staff (JOSDEPS) and USSPACECOM
service component commands. It does not apply to communications-computer systems
requirements which are addressed in USSPACECOMR 700-1, Communications-Computer
Systems Requirements Document Processing.

1. References:

1.1. DepartrnentofDefenseDirective5OOO.l(DoDD5000.1),DefenseAcquisition.

1.2. Department of Defense Instruction 5000.2 (DoDl 5000.2), Defense Acquisition
Management Policies and Procedures.

1. 3. Department of Defense Manual 5000.2 (DoD 5000.2-M), Defense Acquisition Management
Documentation and Reports.

1. 4. Joint Publication 1-02, Department of Defense Dictionary of Military and Associated Terms.

1. 5. Joint Publication 0-2, Unified Action Armed Forces (UNAAF).

1.6. NORAD/USSPACECOM Regulation (NUR) 102-1, The NORAD/USSPACECOM
Integrated Command and Control System (NUICCS) Mission System Integration Process.

1. 7. USSPACECOMR 700- 1, Communications-Computer Systems Requirements Document
Processing.

1.8. USSPACECOMHO157-1,Processing0perationalRequirements.

No. of Printed Pages: 10
OPR: J5S (Major Richard L. Reaser, Jr., USAF)
Approved by: Colonel Joseph C. Garbrous, USMC
Editor: Susan E. Gillespie
Distribution: F; X, (USD(A)/AP&PI, Washington DC 20301-3000 . . . . . . . . . . . . . . . 2
Joint Staff/J7(ORD), Washington DC 20318-7000 . . . . . . . . . . . . . . . . . . . . . . 2
Joint Staff/J8(SPED), Washington DC 20318-8000. . . . . . . . . . . . . . . . . . . . . . 2
COMNAVSPACECOM/Code 00, Dahlgren VA 22448-5170 . . . . . . . . . . . . . . . . . . . 2
USARSPACE/MOSC-ZA, Stop 80, Peterson AFB CO 80914-5000 . . . . . . . . . . . . . . . 2

2 USSPACECOMR 57-1 11 March 1992

2. General. Complete descriptions and direction regarding the requirements and acquisition
process can be found in references 1. I through 1. 2.

3. Definitions. Definition of "user," "user representative" and "operator" are key to
implementation of the requirements process and the operator's role in the acquisition process. The
following definitions will be used by HQ USSPACECOM and its service component commands:

3. 1. User. An operational command that receives or will receive benefit from the acquired
system. USSPACECOM, other combatant commands, and or service component commands can
be users. There may be more than one user for a system.

3.2. User representative. A command that has been formally designated by proper authority
to represent multiple users or a single user in the requirements and/or acquisition process.
USSPACECOM and/or service component commands can be user representatives. Service
component commands may further delegate user representative responsibilities. There may be
more than one user representative for a system.

3. 3. Operator. An operational command or force whose personnel use or will use the acquired
system to support or conduct military operations. USSPACECOM, other combatant commands
and/or service component commands can be operators. There may be more than one operator for a
system.

3.4. Combatant Command (COCOM). "Non-transferable command authority established
by Title 10, United States Codes, Section 164, exercised only by the commanders of the unified or
specified combatant commands. Combatant Command (command authority) is the authority of a
Combatant Commander to perfon-n those functions of command over assigned forces involving
organizing and employing commands and forces, assigning tasks, designating objectives and
giving authoritative direction over all aspects of military operations, joint training, and logistics
necessary to accomplish the mission assigned to the command. Combatant Command (command
authority) should be exercised through the commanders of subordinate organizations; normally this
authority is exercised through the Service component commander. Combatant Command
(command authority) provides full authority to organize and employ commands and forces the
CINC considers necessary to accomplish assigned missions." (See Joint Publication 1-02
(reference 1.4).)

3.5. Validation Authority. A validation authority is the individual responsible for the
validation of a Mission Need Statement (MNS) and/or Operational Requirements Document
(ORD). As defined in DoDl 5000.2, Part 3 and Part 4, Section B (reference 1.2), validation of an
MNS or ORD by a validation authority confirms that the proposed concept or system will provide a
capability that satisfies the mission need and that a non-material solution is not feasible. A
validation authority also ensures adherence to the guidelines established in DODI 5000.2, Part 4,
Section B (reference 1.2). These guidelines are summarized as follows:

3.5.1. Systemperformanceobjectivesandminimumacceptablerequirementsaredeveloped
from, and remain consistent with, the initial broad statements of operational need.

3.5.2. Tbresholds,objectives,andperformanceparametersareproperlystatedassuch.

3.5.3. Useroruserrepresentativeparticipationhashelpedsynchronizeperfortnanceobjectives
with the acquisition community and performance objectives are operationally meaningful.

3.5.4. Allreasonableoptionsareopenandfacilitatecost-schedule-perfonnancetrade-offsearly
in the process.
USSPACECOMR 57-1 11 March 1992 3

3.5.5. Thereisnoprematurecommitinenttoasystem-specificsolution.

3.6. CapstoneORD. AcapstoneORDestablishestoplevelsystemrequirementsalevelof
detail below that of an MNS in those cases where multiple, independent acquisition programs
support a single system of systems. It contains system characteristics that transcend individual
acquisition program characteristics. Capstone ORD requirements are allocated to the ORDs for the
acquisition programs that provide capability for the overall system of systems. A capstone ORD
does not directly drive the acquisition management system except for system of systems testing.
The capstone ORD fonnat is the same as that specified for an ORD in DoD 5000.2-M.
3.7. USSPACECOM Combat Operations Staff (USSPACECOS). The
USSPACECOS is that function which provides direct support to HQ USSPACECOM by
performing day-to-day operations tasks. The USSPACECOS operates the Space Defense
Operations Center (SPADOC), Space Surveillance Center (SSC), Missile Warning Center (MWC),
Space Command Center (SPACC), and Mobile Consolidated Command Center (MCCC) and
supports special activities and operations and provides standardization/evaluation for these
functions. The USSPACECOS is jointly manned and under COCOM of USCINCSPACE.
3.8. NORAD/USSPACECOM Combined Intelligence Center (CIC). The CIC
performs substantive intelligence (operational, current, and production) for
NORAD[USSPACECOM, DoD users, and the intelligence community. It is the functionally
integrated aggregation of facilities, people, technical systems, and interfaces that performs
comprehensive, all-source, in-depth analysis of space operations and foreign strategic operations
relevant to NORAD and USSPACECOM missions. The CIC is jointly manned and under direct
control of the Commander in Chief, North American Aerospace Defense Command
(CINCNORAD), and Commander in Chief, United States Space Command (USCINCSPACE.
4. Policy. HQ USSPACECOM's involvement in the requirements process stems from
combatant command responsibilities assigned in Title 10, United States Code, Sections 164
through 166. USSPACECOM must ensure new and modified systems which are or will be under
Commander in Chief, United States Space Command (USCINCSPACE) COCOM are consistent
with USSPACECOM's vision of forces and capabilities to meet assigned tasks in the Joint
Strategic Capabilities Plan (JSCP) and responsibilities given to it in the Unified Command Plan
(UCP).
4. 1. USCINCSPACE as a User Representative. For present or future systems under the
COCOM of USCINCSPACE where other CINC forces, are or are envisioned to be, system users
or operators, the UCP designates USCINCSPACE as the user representative. In accordance with
the UCP, USCINCSPACE is responsible for "supporting other CINCs by ensuring that their
space operations and space and missile warning requirements will be supported, and advocating
their needed space support capabilities in coordination with each concerned operational
commander."

4.2. USSPACECOM Component Commands as User Representatives. Unless
otherwise directed by USCINCSPACE, USSPACECOM service component commands will be
the USCINCSPACE user representative, even in those cases where USCINCSPACE is a user
representative for other combatant commands. As the USCINCSPACE user representative, the
service component commands must work closely with HQ USSPACECOM on requirements
matters to ensure that USCINCSPACE-validated requirements and concepts of operation are
properly interpreted and fulfilled by service acquisition agents as specified in this regulation. This
close coordination will be especially critical in those cases where the USSPACECOS or the
NORAD/USSPACECOM CIC is the user or operator. When the service components are

4 USSPACECOMR 57-1 11 March 1992

USCINCSPACE user representatives, they will write the Operational Requirements Document
(ORD). In some cases, HQ USSPACECOM may elect to prepare a capstone ORD for multiservice
programs where no single lead service has been identified. This exception will be processed in
accordance with paragraph 8.
4.3. Program Documentation to be Submitted by the Component Commands to
HQ USSPACECOM for Review. (Acquisition program categories are defined in DODI
5000.2, Part 2 (reference 1.2).):

4.3. 1. All MNSS, ORDS, and System Threat Assessment Reports (STAR) and program
specific threat documents (acquisition categories I-IV) for systems which will be operated by
forces that are, or will be, under the COCOM of USCINCSPACE, including revisions.

4.3.2. Cost and Operational Effectiveness Analyses (COEA), A-level specifications (defined in
MIL-STD-490), system level test plans/procedures and system level interface control
documentation for systems which will be operated by forces that are or will be under the COCOM
of USCINCSPACE, including revisions.
4.3.3. B-level specifications (defined in MIL-STD-490) and detailed test plans/procedures for
programs which develop hardware/software for operation by the USSPACECOS or the space- and
missile-related portions of the NORADIUSSPACECOM CIC, including revisions.
4.3.4. Inthecaseofspecifications,testplans/procedures,interfacecontroldocumentation,and
program specific threat documentation, the HQ USSPACECOM functional office of primary
responsibility (OPR) will determine the level of detailed documentation required for HQ
USSPACECOM review in coordination and agreement with the service component command
functional OPR.

4.4. Communication by the Component Commands with Other Elements of the
Department of Defense on Requirements and Acquisition Matters. Consistent with
Title 10, United States Code Section 164(d)(4), USSPACECOM service component commands
will provide timely notification to HQ USSPACECOM of formal written correspondence or
briefings pertaining to requirements and acquisition to and from other elements of the Deparunent
of Defense that could affect current and future USSPACECOM operational planning. This
notification will be done in writing by either providing a courtesy copy of the correspondence or
through separate correspondence. In cases of emergency, initial oral notification is acceptable but
must be followed up in writing. Examples of communications that would require notification
include, but are not limited to, the following:

4.4. 1. Changes to operational capability dates and timing.

4.4.2. Changesinforcesize,structure,ororganization.
4.4.3. Changes in requirements validated by USCINCSPACE or the Joint Requirements
Oversight Council (JROC).

4.4.4. Programtradestudiesandanalysesthatcouldaffectoperationalcapability.
4.4.5. Proposed new space systems, concepts, or capabilities which could come under
USCINCSPACE COCOM.

USSPACECOMR 57-1 1 1 March 1992 5

4.5. Mission Needs Common to the Component Commands. When more than one
USSPACECOM service component command has a similar mission need that could result in a new
or modified system operated by forces over which USCINCSPACE does or will exercise
COCOM, USSPACECOM policy will be to consolidate the mission need into a single
USSPACECOM-prepared MNS. Components are not precluded from developing individual
MNSs for similar capabilities and submitting them to validation authorities; however, this would
not be consistent with UCP tasking described in paragraph 4. 1.

4.6. Resolution of Conflicts between USSPACECOM and its Component
Commands.

4.6. 1. For those needs where USCINCSPACE is the validation authority for the MNS or
ORD, the MNS or ORD will not be validated until all issues are resolved. U the service component
commander and USCINCSPACE cannot resolve the issue, the service component may elect to
elevate the matter to their respective service chief who in turn will attempt to resolve the matter with
USCINCSPACE. Failing that, USCINCSPACE and the service chief or deputy service chief will
take the matter to the JROC for resolution. This procedure is diagrammed in attachment 1.

4.6.2. For those needs where USCINCSPACE is not the validation authority, the following
procedures apply from Joint Publication 0-2 (reference 1.5). The service component commands
are obligated to consider the plans, objectives, advice, and recommendations of USCINCSPACE
with respect to weapon system programs. The first course of action is for the service component
commander and USCINCSPACE to attempt to resolve the issue. If the service component
commander elects not to modify an MNS or ORD as requested by HQ USSPACECOM, the
component will forward the USSPACECOM request and the rationale for not including the
modification along with the unmodified MNS or ORD to the validation authority. A copy of the
rationale for not including the modification will be sent by the service component command to HQ
USSPACECOM. USCINCSPACE may then elect to bring the matter to the attention of the
Chairman or Vice Chairman of the Joint Chiefs of Staff or the service chief. The service
components are obligated to allow time for USCINCSPACE to express his views before a final
decision is made on the matter. This procedure is diagrammed in attachment 1.

4.6.3. Mission system integration disagreements between HQ USSPACECOM and its service
component commands which arise as the result of MNSS, ORDS, specifications, test
plans/procedures and interface control documentation review will be resolved in accordance with
the procedures contained in NUR 102-1 (reference 1.6).

4.7. COCOM Establishment in MNSs and ORDS. CINCs are assigned COCOM of
operational forces by the Secretary of Defense in the "Forces for Unified and Specified
Commands," pursuant to Title 10 United States Code, Section 162(a)(1). COCOM assignment
can have significant bearing in the requirements definition process, but COCOM cannot be
assigned until the forces exist. In view of this situation, potential COCOM assignment should be
addressed in MNSs and ORDS.

5. Responsibilities:

5.1. HQ USSPACECOM and JOSDEPS:

5. 1. 1. Conduct internal HQ USSPACECOM MNS, ORD, COEA, STAR and other program
documentation review, coordination, and MNSIORD validation processes in accordance with
USSPACECOM HOI 57-1.

6 USSPACECOMR 57-1 11 March 1992

5.1.2. Provide a single, consolidated HQ USSPACECOM response to service component-
submitted MNSS, ORDS, COEAS, STARS, specifications, test plans/procedures, interface control
documentation and program threat documentation within 25 days after HQ USSPACECOM
receipt.
5. 1. 2. 1. Review MNSs and ORDs to ensure the requirements contained in them properly reflect
USSPACECOM policies, architectures, and mission concepts. The HQ USSPACECOM review
will also ensure MNS and ORD requirements are consistent with national and Department of
Defense space policy, the JSCP, and the UCP.
5.1.2.2. Review COEAs to ensure consistency with USSPACECOM policies, architectures,
mission concepts and operational threat scenarios. Assist in development of COEA evaluation
criteria and operational threat scenarios for systems which will be operated by forces that are or
will be under the COCOM of USCINCSPACE, including revisions.
5.1.2.3. Review STARs and program threat documentation to ensure the threat used in the
acquisition is consistent with the operational threat that drives USSPACECOM war plans.
5. 1. 2. 4. Review specifications and interface control documentation to ensure proper reflection
and interpretation of USSPACECOM requirements, policies, architectures, technical integration
standards, and mission concepts.
5.1.2.5. ReviewtestplansandproceduresforimpactonUSSPACECOMoperationaIcrewsthat
may be required to support testing and for impacts to current operations.
5.1.2.6. Through its functional OPRS, work with the component commands to establish the
precise level of documentation (specifications, test plans and procedures, interface control
documentation, and program threat documentation) required for review by HQ USSPACECOM.
5.1.3. Coordinate HQ USSPACECOM and USSPACECOM service component-prepared
MNSs and ORDs that affect other combatant commands with the affected combatant command's
headquarters staffs. In the case of component-prepared MNSs and ORDS, HQ USSPACECOM
will act on the behalf of its service components during this coordination and will include other
combatant command comments in the consolidated HQ USSPACECOM response. (This is not
intended to preclude or prohibit USSPACECOM service component commands from coordinating
with other combatant command service components.)
5.1.4. Coordinate MNSs and ORDs received from outside sources with USSPACECOM
component commands as appropriate.
5.1.5. Prepare MNSs for those systems that cross service boundaries or when deemed
appropriate by the HQ USSPACECOM functional OPR. Prepare capstone ORDs for systems in
accordance with the procedures of paragraphs 4.2 and 8.
5.1.6. Coordinate HQ USSPACECOM-prepared MNSs and capstone ORDs with
USSPACECOM service component commands.
5.1.7. Provide two copies of HQ USSPACECOM-prepared MNSs and ORDs to each
component command once submitted to the appropriate validation authority and again when
validated.

USSPACECOMR 57-1 11 March 1992 7

5.2. USSPACECOM Service Component Commands:
5.2.1. Coordinate service component-prepared MNSs and ORDs with the other
USSPACECOM service components prior to or coincident with submittal for HQ USSPACECOM
review. (Service components will conduct other internal service coordination in accordance with
their respective service regulations and instructions.)
5.2.2. Submit 10 copies of USSPACECOM service component-prepared MNSs and ORDs that
meet the criteria established in paragraph 4.3 to HQ USSPACECONVJ5S at least 25 calendar days
prior to component submittal to higher headquarters or validation authority. If USCINCSPACE is
the validation authority, submit 10 copies to HQ USSPACECOM, Director of Plans, Deputy
Directorate for Space Systems (HQ USSPACECOM/J5S) allowing at least 35 calendar days for
response.
5.2.3. Provide two copies of all USSPACECOM service component-prepared MNSs and
ORDs to HQ USSPACECOM/J5S once validated, including those where USCINCSPACE is the
validation authority.
5.2.4. Submit 10 copies of STARS, program specific threat documentation, COEAS,
specifications, system level test plans/procedures and system level interface control documentation
that meet the criteria established in paragraph 4.3 to HQ US SPACECOMIJ5 S and allow at least 25
calendar days for review. Work with HQ USSPACECOM functional OPRs to establish the
precise level of documentation required for review by HQ USSPACECOM.
5.2.5. Notify HQ USSPACECOM/J5 of communications that meet the criteria set forth in
paragraph 4.4.
5.2.6. Providetwocopiesofallservice-approvedAcquisitionProgramBaselinedocumentsto
HQ USSPACECOMIJ5S.
5.2.7. Coordinate program trade studies with HQ USSPACECOM in those cases where
operational capabilities in USCINCSPACE-validated MNSs and/or ORDs are impacted.
5.2.8. Work with HQ USSPACECOM to consolidate into a single USSPACECOM-prepared
MNS those mission needs where more than one service component has a similar mission need.
5.2.9. Obtain foreign disclosure approval through the Deputy Chief of Staff for Plans,
Directorate of Programs and International Affairs, Foreign Disclosure Division (HQ
AFSPACECOM/XPPF) for that documentation which HQ USSPACECOM is obligated to send to
other nations for review under this regulation. (HQ AFSPACECOMIXPPF is the official foreign
disclosure authority for HQ USSPACECOM.)
5.2. 1 0. Address COCOM assignment in service component-developed MNSs and ORDS.
6. Highly Sensitive Classiried Programs. The processes and responsibilities described in
this regulation will be tailored as necessary for highly sensitive classified programs to account for
special security considerations. Specific tailoring will be performed by the HQ USSPACECOM
directorate/deputy directorate who is the functional OPR.

8 USSPACECOMR 57-1 11 March 1992

7. Procedures. Specific processing flows, review, and validation procedures, as well as
timeliness are diagrammed in attachment 2.
8. Exceptions. In those cases where HQ USSPACECOM or one of its components determines
a need to deviate from the policies and/or procedures prescribed in this regulation, or is directed by
higher headquarters to deviate, USCINCSPACE will be apprised of and approve the deviation.
The functional OPR for the exception will publish explicit policies and procedures upon
USCINCSPACE approval and obtain coordination from all affected parties on the matter to include
the JROC for capstone ORDS. Instances where processing timelines need acceleration will be
agreed to between the reviewing and submitting parties on a case-by-case basis.

OFFICIAL DONALD J. KUTYNA
General, USAF
Commander in Chief

MICHAEL A. KLICH 2 Attachments
Lieutenant Colonel, USAF 1. Conflict Resolution Procedures
Director of Information Management 2. Processing Procedures

USSPACECOMR 57-1 Attachment 1 11 March 1992 7

10 USSPACECOMR 57-1 Attachment 2 11 March 1992