Design review (U.S. government)

Last updated

In the United States military integrated acquisition lifecycle [1] [2] the Technical section has multiple acquisition "Technical Reviews". [3] Technical reviews and audits assist the acquisition and the number and types are tailored to the acquisition. [4] Overall guidance flows from the Defense Acquisition Guidebook chapter 4, [5] with local details further defined by the review organizations. [6] [7] [8] [9] Typical topics examined include adequacy of program/contract metrics, proper staffing, risks, budget, and schedule.

Contents

In NASA's engineering design life cycle, design reviews are held for technical and programmatic accountability and to authorize the release of funding to a project. [10] A design review provides an in-depth assessment by an independent team of discipline experts and managers that the design (or concept) is realistic and attainable from a programmatic and technical sense.

Design review is also required of medical device developers as part of a system of design controls described in the US Food and Drug Administration's governing regulations in 21CFR820. In 21CFR820.3(h), design review is described as "documented, comprehensive, systematic examination of the design to evaluate the adequacy of the design requirements, to evaluate the capability of the design to meet these requirements, and to identify problems". The FDA also specifies that a design review should include an independent reviewer.

Review process

The list of reviews done by an effort and the content, nature, process, and objectives any review uses vary enormously by the organization involved and the particular situation of the effort. For example, even within the U.S. Department of Defense, System Requirements Review cases include, for example, (1) a 5-day perusal of each individual requirement, or (2) a 2-day discussion of development plan documents allowed only after the system requirements have been approved and the development documents reviewed with formal action items required, or (3) a half-day powerpoint with content determined by the Project Manager with attendance limited to high-level (non-technical) stakeholders with no output other than the PM being able to claim "SRR done".

Some of the reviews that may be done on an effort include:

Mission Concept Review (MCR)

The MCR affirms the mission need and examines the proposed mission's objectives and the concept for meeting those objectives.

System Requirements Review (SRR)

The SRR examines the functional requirements and performance requirements defined for the system and the preliminary program or project plan and ensures that the requirements and the selected concept will satisfy the mission.

Mission Definition Review (MDR)

The MDR examines the proposed requirements, the mission architecture, and the flow down to all functional elements of the mission to ensure that the overall concept is complete, feasible, and consistent with available resources.

System Design Review (SDR)

The SDR examines the proposed system architecture and design and the flow down to all functional elements of the 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 will show that the correct design options have been selected, interfaces have been identified, and verification methods have been described. [11] [12]

The following are typical objectives of a PDR:

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 that the technical effort is on track to complete the flight and ground system development and mission operations, meeting mission performance requirements within the identified cost and schedule constraints. [13]

The following are typical objectives of a CDR:

Production Readiness Review (PRR)

A PRR is held for Flight System and Ground Support 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.

Test Readiness Review (TRR)

A TRR ensures that the test article (hardware/software), test facility, support personnel, and test procedures are ready for testing and data acquisition, reduction, and control. This is not a prerequisite for Key Decision Point entry.

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. The SAR examines the system, its end products and documentation, and test data and analyses that support verification. It also ensures that the system has sufficient technical maturity to authorize its shipment to the designated operational facility or launch site.

Operational Readiness Review (ORR)

The ORR examines the actual system characteristics and the procedures used in the system or end product's operation and ensures that all system and support (flight and ground) hardware, software, personnel, procedures, and user documentation accurately reflect the deployed state of the system.

The following are typical objectives of an ORR:

Flight Readiness Review (FRR)

The FRR examines tests, demonstrations, analyses, and audits that determine the system's readiness for a safe and successful flight or launch and for subsequent flight operations. It also ensures that all flight and ground hardware, software, personnel, and procedures are operationally ready.

The following are typical objectives[ citation needed ] of a FRR:

See also

Related Research Articles

<span class="mw-page-title-main">Configuration management</span> Process for maintaining consistency of a product attributes with its design

Configuration management (CM) is a systems engineering process for establishing and maintaining consistency of a product's performance, functional, and physical attributes with its requirements, design, and operational information throughout its life. The CM process is widely used by military engineering organizations to manage changes throughout the system lifecycle of complex systems, such as weapon systems, military vehicles, and information systems. Outside the military, the CM process is also used with IT service management as defined by ITIL, and with other domain models in the civil engineering and other industrial engineering segments such as roads, bridges, canals, dams, and buildings.

<span class="mw-page-title-main">STS-8</span> 1983 Space Shuttle Challenger mission

STS-8 was the eighth NASA Space Shuttle mission and the third flight of the Space Shuttle Challenger. It launched on August 30, 1983, and landed on September 5, 1983, conducting the first night launch and night landing of the Space Shuttle program. It also carried the first African-American astronaut, Guion Bluford. The mission successfully achieved all of its planned research objectives, but was marred by the subsequent discovery that a solid-fuel rocket booster had almost malfunctioned catastrophically during the launch.

<span class="mw-page-title-main">Henry Hartsfield</span> American astronaut (1933–2014)

Henry Warren Hartsfield Jr. was a United States Air Force Colonel and NASA astronaut who logged over 480 hours in space. He was inducted into the United States Astronaut Hall of Fame in 2006.

<span class="mw-page-title-main">Systems development life cycle</span> Systems engineering terms

In systems engineering, information systems and software engineering, the systems development life cycle (SDLC), also referred to as the application development life cycle, is a process for planning, creating, testing, and deploying an information system. The SDLC concept applies to a range of hardware and software configurations, as a system can be composed of hardware only, software only, or a combination of both. There are usually six stages in this cycle: requirement analysis, design, development and testing, implementation, documentation, and evaluation.

<span class="mw-page-title-main">Defense Support Program</span> US infrared satellite early warning system

The Defense Support Program (DSP) is a program of the United States Space Force that operated the reconnaissance satellites which form the principal component of the Satellite Early Warning System used by the United States.

<span class="mw-page-title-main">V-model</span> Graphic of a systems development lifecycle

The V-model is a graphical representation of a systems development lifecycle. It is used to produce rigorous development lifecycle models and project management models. The V-model falls into three broad categories, the German V-Modell, a general testing model, and the US government standard.

<span class="mw-page-title-main">Mobile User Objective System</span> US Space Force communications satellite system

The Mobile User Objective System (MUOS) is a United States Space Force narrowband military communications satellite system that supports a worldwide, multi-service population of users in the ultra high frequency (UHF) band. The system provides increased communications capabilities to newer, smaller terminals while still supporting interoperability with legacy terminals. MUOS is designed to support users who require greater mobility, higher bit rates and improved operational availability. The MUOS was declared fully operational for use in 2019.

Integrated logistics support (ILS) is a technology in the system engineering to lower a product life cycle cost and decrease demand for logistics by the maintenance system optimization to ease the product support. Although originally developed for military purposes, it is also widely used in commercial customer service organisations.

The Aerospace Corporation is an American nonprofit corporation that operates a federally funded research and development center (FFRDC) in El Segundo, California. The corporation provides technical guidance and advice on all aspects of space missions to military, civil, and commercial customers. As the FFRDC for national-security space, Aerospace works closely with organizations such as the United States Space Force and the National Reconnaissance Office (NRO) to provide "objective technical analyses and assessments for space programs that serve the national interest". Although the USSF and NRO are the primary customers, Aerospace also performs work for civil agencies such as NASA and NOAA as well as international organizations and governments in the national interest.

In software engineering, software system safety optimizes system safety in the design, development, use, and maintenance of software systems and their integration with safety-critical hardware systems in an operational environment.

Center of gravity (COG) is a military term that refers to the source of strength, balance, or stability necessary for a military force to maintain operation. Centers of gravity exist for all belligerents and at all tactical, strategic, and operational levels of war simultaneously. The concept was first developed by Carl von Clausewitz, a Prussian military theorist, in his work On War.

<span class="mw-page-title-main">Barry E. Wilmore</span> American astronaut

Barry Eugene "Butch" Wilmore is a NASA astronaut and United States Navy test pilot. He has had two spaceflights, the first of which was an 11-day Space Shuttle mission in November 2009, to the International Space Station. Wilmore was designated as pilot with five other crew members on Space Shuttle Atlantis for the mission STS-129. He most recently served as part of Expedition 41 to the International Space Station.

<span class="mw-page-title-main">Air Force Operational Test and Evaluation Center</span> Direct reporting unit of the United States Air Force responsible for test and evaluation

Located at Kirtland Air Force Base, New Mexico, the Air Force Operational Test and Evaluation Center is a direct reporting unit of Headquarters, United States Air Force. It is the Air Force independent test agency responsible for testing, under operationally realistic conditions, new systems being developed for Air Force and multi-service use.

<span class="mw-page-title-main">GPS Block III</span> Current generation of GPS satellites

GPS Block III consists of the first ten GPS III satellites, which will be used to keep the Navstar Global Positioning System operational. Lockheed Martin designed, developed and manufactured the GPS III Non-Flight Satellite Testbed (GNST) and all ten Block III satellites. The first satellite in the series was launched in December 2018.

<span class="mw-page-title-main">Landsat 8</span> American Earth-observing satellite launched in 2013 as part of the Landsat program

Landsat 8 is an American Earth observation satellite launched on 11 February 2013. It is the eighth satellite in the Landsat program; the seventh to reach orbit successfully. Originally called the Landsat Data Continuity Mission (LDCM), it is a collaboration between NASA and the United States Geological Survey (USGS). NASA Goddard Space Flight Center in Greenbelt, Maryland, provided development, mission systems engineering, and acquisition of the launch vehicle while the USGS provided for development of the ground systems and will conduct on-going mission operations. It comprises the camera of the Operational Land Imager (OLI) and the Thermal Infrared Sensor (TIRS), which can be used to study Earth surface temperature and is used to study global warming.

The Analysis of Alternatives (AoA) in the United States is a requirement of military acquisition policy, as controlled by the Office of Management and Budget (OMB) and the United States Department of Defense (DoD). It ensures that at least three feasible alternatives are analyzed prior to making costly investment decisions. The AoA establishes and benchmarks metrics for Cost, Schedule, Performance (CSP) and Risk (CSPR) depending on military "needs" derived from the Joint Capabilities Integration Development System process. It moves away from employing a single acquisition source to the exploration of multiple alternatives so agencies have a basis for funding the best possible projects in a rational, defensible manner considering risk and uncertainty.

<span class="mw-page-title-main">USA-273</span> United States military satellite

USA-273, also known as SBIRS GEO-3, is a United States military satellite and part of the Space-Based Infrared System (SBIRS).

<span class="mw-page-title-main">Space Weather Follow On-Lagrange 1</span>

Space Weather Follow On-Lagrange 1 (SWFO-L1) is a future spacecraft mission planned to monitor signs of solar storms, which may pose harm to Earth's telecommunication network. The spacecraft will be operated by the National Oceanic and Atmospheric Administration (NOAA), with launch scheduled for December 2025. It is planned to be placed at the Sun–Earth L1 Lagrange point, a location between the Earth and the Sun. This will allow SWFO-L1 to continuously watch the solar wind and energetic particles heading for Earth. SWFO-L1 is an ESPA Class Spacecraft, sized for launch on an Evolved Expendable Launch Vehicle Secondary Payload Adapter (ESPA) Grande ring in addition to the rocket's primary payload. The spacecraft's Solar Wind Instrument Suite (SWIS) which includes three instruments will monitor solar wind, and the Compact Coronagraph (CCOR) will monitor the Sun's surroundings to image coronal mass ejection (CME). A CME is a large outburst of plasma sent from the Sun towards interplanetary space.

<span class="mw-page-title-main">Sentinel-6 Michael Freilich</span> Earth observation satellite

The Sentinel-6 Michael Freilich (S6MF) is a radar altimeter satellite developed in partnership between several European and American organizations. It is part of the Jason satellite series and is named after Michael Freilich. S6MF includes synthetic-aperture radar altimetry techniques to improve ocean topography measurements, in addition to rivers and lakes. The spacecraft entered service in mid 2021 and is expected to operate for 5.5 years.

Human Systems Integration (HSI) is an interdisciplinary managerial and technical approach to developing and sustaining systems which focuses on the interfaces between humans and modern technical systems. The objective of HSI is to provide equal weight to human, hardware, and software elements of system design throughout systems engineering and lifecycle logistics management activities across the lifecycle of a system. The end goal of HSI is to optimize total system performance and minimize total ownership costs. The field of HSI integrates work from multiple human centered domains of study include training, manpower, personnel, human factors engineering, safety, occupational health, survivability and habitability.

References

  1. Integrated Defense AT&L Lifecycle Management Chart Archived February 13, 2013, at the Wayback Machine PD-icon.svg This article incorporates text from this source, which is in the public domain .
  2. "Integrated Defense Acquisition, Technology, & Logistics Life Cycle Management Framework chart" (PDF). Archived from the original (PDF) on 2017-01-06. Retrieved 2016-05-31.PD-icon.svg This article incorporates text from this source, which is in the public domain .
  3. Technical Review Definitions Archived 2013-02-20 at the Wayback Machine PD-icon.svg This article incorporates text from this source, which is in the public domain .
  4. Systems Engineering Technical Reviews slider Archived 2012-10-20 at the Wayback Machine PD-icon.svg This article incorporates text from this source, which is in the public domain .
  5. "Defense Acquisition Guidebook". Archived from the original on 2013-02-13. Retrieved 2013-04-11.PD-icon.svg This article incorporates text from this source, which is in the public domain .
  6. NAVSEA Technical Review Manual Archived 2015-09-01 at the Wayback Machine PD-icon.svg This article incorporates text from this source, which is in the public domain .
  7. "NAVAIR INST 4355.19D, Systems Engineering Technical Review Process" (PDF). Retrieved 2015-08-12.PD-icon.svg This article incorporates text from this source, which is in the public domain .
  8. "Everyspec NAVAIRINST 4355.19 Systems Engineering Technical Review (incl supplement B)" . Retrieved 2015-08-12.PD-icon.svg This article incorporates text from this source, which is in the public domain .
  9. Systems Engineering Fundamentals. Archived 2017-01-31 at the Wayback Machine , Ch. 11 Technical Reviews and Audits; App 16-a Schedules Defense Acquisition University Press, 2001 PD-icon.svg This article incorporates text from this source, which is in the public domain .
  10. NASA Procedural Requirements, Subject: NASA Systems Engineering Processes and Requirements, Appendix G Responsible Office: Office of the Chief Engineer, NPR 7123.1B, Effective Date: April 18, 2013, Expiration Date: April 18, 2018 PD-icon.svg This article incorporates text from this source, which is in the public domain .
  11. James Chapman. "Engineering Design Reviews".
  12. "Defense Acquisition Guidebook 10.5.3 Preliminary Design Review" . Retrieved 14 January 2016.PD-icon.svg This article incorporates text from this source, which is in the public domain .
  13. http://www.navair.navy.mil/nawctsd/Resources/Library/Acqguide/cdr.htm Archived 2015-05-27 at the Wayback Machine "Critical Design Review" Published 2013-4-4 Retrieved 2015-5-12 PD-icon.svg This article incorporates text from this source, which is in the public domain .