NASA ENGINEERING NETWORK
Follow this link to skip to the main content
+ Contact LLIS
Go
ABOUT NASALATEST NEWSMULTIMEDIAMISSIONSMyNASAWORK FOR NASA

+ NASA Home
FIND ENGINEERING RESOURCES BY
LLIS HOME
NASA CENTERS
MISSION DIRECTORATE
TOPICS
BY YEAR


Public Lessons Learned Entry: 0656

Lesson Info:

  • Lesson Number: 0656
  • Lesson Date: 1999-02-01
  • Submitting Organization: JPL
  • Submitted by: Wil Harkins

Subject:

Hardware Review/Certification Requirement

Abstract:

Preferred Practice for Design & Test. Hardware Review/Certification Requirement (HR/CR) reviews are potentially capable of discovering hardware defects, deficiencies, or deviations prior to delivery of the hardware. Consequently, if the HR/CR review is not conducted, any defects, deficiencies, or deviations that may have been uncovered by the Review Board will either go undetected or will have to be detected by some other means at a time subsequent to delivery. If the hardware problems go undetected, then a mission failure may occur. If the hardware problems are detected late, then serious schedule impacts could result and the cost of correcting the hardware defect could be affected. Conduct an HR/CR review prior to the delivery of flight hardware and associated software to evaluate and certify that the hardware is ready for delivery and that it is acceptable for integration with the spacecraft.

Description of Driving Event:

This Lessons Learned is based on Reliability Practice No. PD-ED-1215.2; from NASA Technical Memorandum 4322A, NASA Reliability Preferred Practices for Design and Test.

Benefit:

The Hardware Review/Certification Requirement (HR/CR) provides a structured review process for assessing the status of flight hardware and screening for unresolved defects prior to delivery for integration.

Implementation Method:

After flight hardware has been designed, undergone unit level reviews, fabricated, integrated, and tested, a review board is convened to review the status of the hardware and to certify that the hardware is ready for delivery and is acceptable for mating with the spacecraft. The Project System Engineer/Instrument Manager is selected to chair the review. Other members of the review board include the Hardware Division Representative, the Quality Assurance Engineer, the Software Assurance Engineer, The Environmental/Reliability Engineer, and the Product Assurance Manager.

The agenda and the scope of the review board is generally defined by the HR/CR form shown as Figure 1.

Using the HR/CR form as a checklist, the design engineer responsible for the hardware being reviewed addresses the following:

  1. The hardware performance and requirements compliance status.
  2. That all requirements have been met, or that any requirements that have not been met are covered by approved waivers.
  3. That all documentation is current and complete, and includes all approved waivers and Engineering Change Requests (ECRs).
  4. That all analyses required to validate environmental requirements have been completed, documented, and approved.
  5. That all tests required to qualify the hardware have been successfully completed.
  6. That the hardware is acceptable for integration with the spacecraft.

If the members of the review board or other participants have any concerns about the flight readiness of the hardware, anyone may write a Request for Action (RFA) against the hardware. These RFAs are reviewed by the Project and a response is prepared. After all RFAs are closed, the board certifies that the hardware is ready for delivery and flight by signing the HR/CR form.

Technical Rationale:

A structured review following a predetermined checklist such as the HR/CR form provides a mechanism for the responsible design engineer to review the status of the hardware and verify that the hardware is in compliance and ready for delivery and spacecraft integration. This process is enhanced by having a review board whose members have not been responsible for the design, fabrication, and testing of the hardware. Board members from the reliability engineering area and the product assurance area can focus this expertise on the completed product. Additionally, the board is able to take a fresh look at the hardware production cycle and to ask questions until they are satisfied that all necessary steps have been completed and that the hardware is acceptable for integration.

Related Practices:

  1. Common Review Methods for Engineering Products, Reliability Preferred Practice No. PD-ED-1215.4.
refer to [D] description[D]

Figure 1. Hardware Review / Certification Requirement Form


Lesson(s) Learned:

Impact of Non-Compliance:

HR/CR reviews are potentially capable of discovering hardware defects, deficiencies, or deviations prior to delivery of the hardware. Consequently, if the HR/CR review is not conducted, any defects, deficiencies, or deviations that may have been uncovered by the Review Board will either go undetected or will have to be detected by some other means at a time subsequent to delivery. If the hardware problems go undetected, then a mission failure may occur. If the hardware problems are detected late, then serious schedule impacts could result and the cost of correcting the hardware defect could be affected.

Recommendation(s):

Practice:

A Hardware Review/Certification Requirement (HR/CR) Review is conducted prior to the delivery of flight hardware and associated software to evaluate and certify that the hardware is ready for delivery and that it is acceptable for integration with the spacecraft.

Evidence of Recurrence Control Effectiveness:

Programs That Certified Usage:

Voyager, Galileo, and all other JPL developed Class A, B, and C spaceflight hardware.

Documents Related to Lesson:

N/A

Mission Directorate(s):

  • Exploration Systems
  • Science
  • Space Operations
  • Aeronautics Research

Additional Key Phrase(s):

  • Aircraft
  • Configuration Management
  • Facilities
  • Flight Equipment
  • Ground Operations
  • Ground Equipment
  • Hardware
  • Launch Vehicle
  • Payloads
  • Risk Management/Assessment
  • Safety & Mission Assurance
  • Software
  • Spacecraft
  • Test & Verification

Additional Info:

    Approval Info:

    • Approval Date: 2000-03-03
    • Approval Name: Eric Raynor
    • Approval Organization: QS
    • Approval Phone Number: 202-358-4738


    FirstGov - Your First Click to the US Government
    + 2004 Vision for Space Exploration
    + FY 2005 Budget Request
    + 2003 Strategic Plan
    + Freedom of Information Act
    + The President's Management Agenda
    + FY 2003 Agency Performance and Accountability Report
    + NASA Privacy Statement, Disclaimer,
    and Accessibility Certification

    + Freedom to Manage
    NASA
    Curator:Celeste Merryman
    NASA Official: Gregory Robinson
    + Contact LLIS