SE Engine & Life Cycle Reviews Flashcards
Purpose of Pre-Phase A: Concept Studies
To produce a broad spectrum of ideas and alternatives
for missions from which new programs/projects can be
selected. Determine feasibility of desired system, develop
mission concepts, draft system-level requirements, assess
performance, cost, and schedule feasibility; identify
potential technology needs, and scope
Purpose of Phase A: Concept and Technology Development
To determine the feasibility and desirability of a suggested
new system and establish an initial baseline compatibility
with NASA’s strategic plans. Develop final mission concept,
system-level requirements, needed system technology
developments, and program/project technical management
plans.
Purpose of Phase B: Preliminary Design and Technology Completion
To define the project in enough detail to establish an initial
baseline capable of meeting mission needs. Develop
system structure end product (and enabling product)
requirements and generate a preliminary design for each
system structure end product.
Purpose of Phase C: Final Design and Fabrication
To complete the detailed design of the system (and its
associated subsystems, including its operations systems),
fabricate hardware, and code software. Generate final
designs for each system structure end product.
Purpose of Phase D: System Assembly, Integration and Test, Launch
To assemble and integrate the system (hardware, software,
and humans), meanwhile developing confidence that it
is able to meet the system requirements. Launch and
prepare for operations. Perform system end product
implementation, assembly, integration and test, and
transition to use.
Purpose of Phase E: Operations and Sustainment
To conduct the mission and meet the initially identified
need and maintain support for that need. Implement the
mission operations plan.
Purpose of Phase F: Closeout
To implement the systems decommissioning/disposal plan
developed in Phase E and perform analyses of the returned
data and any returned samples.
Outcome of Pre-Phase A: Concept studies
Feasible system concepts in the form of simulations, analysis, study reports, models, and mock-ups
Outcomes of Phase A: Concept and Technology Development
System concept definition in the form of simulations, analysis, engineering models and mock-ups, and trade study definition
Outcomes of Phase B: Preliminary Design and Technology Completion
End products in the form of
mock-ups, trade study results,
specification and interface
documents, and prototypes
Outcomes of Phase C: Final Design and Fabrication
End product detailed designs,
end product component
fabrication, and software
development
Outcomes of Phase D: System Assembly, Integration and Test, Launch
Operations-ready system
end product with supporting
related enabling products
Outcomes of Phase E: Operations and Sustainment
Desired system
Outcomes of Phase F: Closeout
Product closeout
Key Decision Points
KDPs are the events at which the decision authority determines the readiness of a program/project to progress to the next phase of the life cycle (or to the next KDP). Phase boundaries are defined so that they provide natural points for“go” or “no-go” decisions.
Give 5 examples of key decision points
Mission Concept
Review (MCR)
The MCR will affirm the mission
need and evaluates the proposed
objectives and the concept for
meeting those objectives.
System
Requirements
Review (SRR)
The SRR evaluates the functional and performance requirements defined for the system and the preliminary program or project plan and ensures that the requirements and selected concept will satisfy the mission.
System
Definition
Review (SDR)
This review evaluates whether the proposed architecture is responsive to the functional and performance requirements and that the requirements have been allocated to all functional elements of the mission/system.
Preliminary
Design Review
(PDR)
The PDR demonstrates that the preliminary design meets all system requirements with acceptable risk and within the cost and schedule constraints and establishes the basis for proceeding with detailed design. It shows that the correct design options have been selected, interfaces have been identified, and verification methods have been described. The PDR should address and resolve critical, system-wide issues and show that work can begin on detailed design.
Critical Design
Review (CDR)
The CDR demonstrates that the maturity of the design is appropriate to support proceeding with full scale fabrication, assembly, integration, and test. CDR determines if the technical effort is on track to complete the system development, meeting mission performance requirements within the identified cost and schedule constraints.
Production
Readiness
Review (PRR)
A PRR is held for projects developing or acquiring multiple or similar systems greater than three or as determined by the project. The PRR determines the readiness of the system developers to efficiently produce the required number of systems. It ensures that the production plans; fabrication, assembly, and integration-enabling products; and personnel are in place and ready to begin production.
System
Integration
Review (SIR)
An SIR ensures segments, components, and subsystems are on schedule to be integrated into the system. Integration facilities, support personnel, and integration plans and procedures are on schedule to support integration.
System
Acceptance
Review (SAR)
The SAR verifies the completeness of the specific end products in relation to their expected maturity level and assesses compliance to stakeholder expectations. It also ensures that the system has sufficient technical maturity to authorize its shipment to the designated operational facility or launch site.
