This section contains information for reference only.

The primary purpose of this document is to be specified by the government on space system development contracts as a compliance document. Therefore, the requirements herein are intended to be Contractor requirements. This document, however, can be used by the government as a guide to assist in systems engineering planning in terms of the required systems engineering efforts. Programs for which a government activity plays a "contractor" role should implement this standard under a "contract" to the tasking government activity. A single, integrated set of technical tasks should be developed. This can be accomplished by integrating all the tasks in the contract's Statement Of Work (SOW), tailoring this document to include tasks from other standards selected for contractual application, executing the complete, integrated task set via the Ssytems Engineering Management Plan (SEMP), or some appropriate combination of these alternatives. Regardless of the approach taken to place the tasks of this standard on contract, the SEMP should be the single integrated technical planning document.

This standard can be used by the government as follows:

a. For defining the government's requirements for systems engineering in a Request For Proposal (RFP) or Contract. Toward this end, the requirements in this section can be applied by tailoring the requirements in Subsection 4.2 and definitions in Section 3.0 consistent with the objectives and constraints of the program and contract, or by developing tailoring for additional government, NSS industry, or professional society systems engineering standards to bring them into compliance with Sections 4.2 and 3.0 below. The resulting document(s) should then be included in the list of compliance documents in the RFP.

b. To be incorporated by reference in Section M, "Evaluation Criteria and/or Source Selection Standards for evaluating either:

(1) Proposed alternative standards or corporate policies, or

(2) Further tailoring of a standard listed in the RFP.

The tailored standard that proves to be acceptable to the government should then be placed on contract as a compliance document.

c. As a "check list" for monitoring the Contractor's systems engineering processes and products.

This standard applies to all acquisition Phases of DODI 5000.2 and NSS 03-01, pre-Phase A, Phase A, Phase B, and Phase C. The requirements herein provide important steps in implementing DOD direction, including the following from the DOD acquisition policy:

Acquisition programs SHALL be managed through the application of a systems engineering approach that optimizes total system performance and minimizes total ownership costs.²

Effective sustainment of weapon systems begins with the design and development of reliable and maintainable systems through the continuous application of a robust systems engineering methodology.³

Many other directives and instructions in DoDD 5000.1 and DoDI 5000.2, such as those for affordability, safety, and human factors, also require "the continuous application of a robust systems engineering methodology." While all of the requirements in Subsection 4.2 collectively respond to these directives, those under Tradeoff Analyses and Effectiveness and Cost Analyses are specifically responsive.

Similarly, systems engineering is a core issue to be addressed at each major milestone review conducted under the National Security Space Acquisition Policy and DoDI 5000.2. NSSAP 03-01 states the following:

Assess the system engineering process used for requirements traceability and verification. Provide a requirements flow down. At KDP-C, provide a requirements verification matrix to show design to requirement traceability and the test method to verify.

^2. DoDD 5000.1, The Defense Acquisition System, May 12, 2003, Section E1.27

^3. DoDI 5000.2, Operation of the Defense Acquisition System, May 12, 2003, Section 3.9.2.2