DSMC POC: Systems Engineering Department; (703) 805-3465
The Systems Engineering (SE) Process controls the total system development effort for the purpose of achieving an optimum balance of all system elements. It is designed to translate operational need and/or requirements into a system solution that includes the design, manufacture, Test and Evaluation (T&E) and support processes and products. SE is used to establish a proper balance among performance, risk, cost, and schedule. It does this by recursively applying the subprocesses of requirements analysis, functional analysis and allocation and design synthesis and verification along with the systems analysis and control tools for balance.
A. Configuration Management (CM) Baselines -
- Functional Baseline -The technical portion of the program requirements (system performance
specifications) that provides the basis for contracting and controlling the
system design. It is normally established by the government at System
Functional Review (SFR).
- Allocated Baseline -Defines the performance requirements for each configuration item of the
system (item performance specifications). The contractor normally
establishes this early in the process [not later than the Preliminary Design
Review (PDR)]. Government control is typically deferred until System
Verification Review (SVR).
- Product Baseline -Established by the
detailed design documentation for each configurations item (item detail
specifications). It includes the process and materials baseline (process and
materials specifications). Government control depends on program
requirements but, if established, is typically done at PCA.
B. Preplanned Product Improvement (Pł I) -A deliberate decision delaying incorporation of a system capability but providing growth allocations for the capability.
C. Technical Management Plan (TMP) - The TMP defines the contractor's plan for the conduct and management of the fully integrated effort necessary to satisfy the general and detailed requirements as implemented by the Request for Proposal (RFP) or contract schedule, statement of work/objectives, and specifications.
D. Design Reviews and Audits
1. ASR -Alternative Systems Review - A formal review conducted to demonstrate the preferred system concept(s).
2. SRR -System Requirements Review - A formal, system-level review conducted to ensure that system requirements have been completely and properly identified and that a mutual understanding between the government and contractor exists.
3. SFR -System Functional Review - A formal review of the conceptual design of the system to establish its capability to satisfy requirements. It establishes the functional baseline.
4. SSR -Software Specification Review -
A formal review of requirements and interface specifications for computer software configuration items.
-Preliminary Design Review - A formal review which confirms that the preliminary design logically follows the SFR findings and meets the requirements. It normally results in approval to begin detailed design.
6. CDR -Critical Design Review - A formal review conducted to evaluate the completeness of the design and its interfaces.
7. TRR -Test Readiness Review
- A formal review of the contractors' readiness to begin testing computer software configuration items.
-Functional Configuration Audit - A formal review conducted to verify that all subsystems can perform all of their required design functions in accordance with their functional and allocated configuration baselines.
9. SVR -System Verification Review - A formal review conducted to verify that the actual item (which represents the production configuration) complies with the performance specification.
10. PCA -Physical Configuration Audit -
A formal review that establishes the product baseline as reflected in an early
production configuration item.
E. System/Product Definition - This is the natural result of the threat-opportunity-driven Requirements Generation System and the common thread (or area of common interest) among all acquisition disciplines.
1. Mission Need Statement (MNS) - A formal document, expressed in broad operational terms and prepared in accordance with Chairman of the Joint Chiefs of Staff Instruction (CJCSI) 13170.01A, that documents deficiencies in current capabilities and opportunities to provide new capabilities.
Program Definition - The process of translating broadly stated mission needs into a set of operational requirements from which specific performance specifications are derived.
Operational Requirements Document (ORD) - A formatted statement, which is prepared by the user or user's representative, containing operational performance parameters for the proposed concept/system that defines the system capabilities needed to satisfy the mission need. It is prepared at each milestone, usually beginning with Milestone B.
4. System Threat Assessment & Projections
- Prepared by a collaboration among the intelligence, requirements generation, and acquisition management
communities to support program initiation (usually Milestone B). It is maintained in a current and approved or validated status throughout the acquisition process.