| NODIS Library | Program Management(8000s) | Search |

NASA Ball NASA
Procedural
Requirements
NPR 8735.2C
Effective Date: March 12, 2021
Expiration Date: March 12, 2026
COMPLIANCE IS MANDATORY FOR NASA EMPLOYEES
Printable Format (PDF)

Subject: Hardware Quality Assurance Program Requirements for Programs and Projects (Updated w/Change 1)

Responsible Office: Office of Safety and Mission Assurance


| TOC | ChangeHistory | Preface | Chapter1 | Chapter2 | Chapter3 | Chapter4 | Chapter5 | Chapter6 | Chapter7 | Chapter8 | AppendixA | AppendixB | AppendixC | AppendixD | AppendixE | AppendixF | AppendixG | ALL |

Appendix D. Suggested Criteria for Supplier Records and Data Delivery Requirements

D.1 The records and data items listed below are suggested for inclusion in acceptance requirements that are flowed to suppliers of critical items. These records and data items are in addition to those required in paragraph 4.5.2 above.

D.2 It is recommended that the following records and data are required for delivery by suppliers when a formal, multidiscipline hardware acceptance review will be conducted for item or system acceptance and certification. When an item in the list below corresponds to a required data deliverable defined in Chapter 4, it is noted with "[ADP]."

a. Final inspection and acceptance test records showing unit acceptability [ADP].

b. Complete unit-level nonconformance reports, MRB actions, failure reports and test/failure review board actions, and associated analyses (e.g., overstress analyses, summary-level rework, and repair) [ADP].

c. Complete test history records with environments seen and sequence of testing.

d. Identification of any unverified failures encountered with an associated risk analysis, including analysis of worst-case repairs, as well as out-of-family test results.

e. Cumulative unit operating times/cycles, pressure, vibration, temperature, and any other testing exposure logs and data.

f. Unit as-built versus as-designed configuration records with appropriate reconciliation or any deltas [ADP].

g. All waivers and deviations requested and approved for the unit [ADP].

h. History of the unit from the time it is first integrated into its next higher assembly, including installation and removal data.

i. Complete storage history to include storage environment and length of storage if stored for longer than six months.

j. Complete unit build history starting at the lowest level of assembly.

k. Identification of manufacturing instructions and processes used to build the unit.

l. Complete chronological build, inspection, and test records, including physical and functional discrepancies, their resolution, and detailed repair and rework history.

m. Analysis of trend data across the unit being tested and comparison with other like units.

n. Complete identification of associated test equipment and test software along with critical calibration results.

o. Bill of materials or components/part trace records reflecting traceability of parts, materials, and subassemblies installed.

p. Complete storage history.

q. Product photographs and drawings.

D.3 It is recommended that the following records and data are required of suppliers of critical items, below the payload level of integration (i.e., subassemblies, components, subsystems), for product acceptance. When an item in the list below corresponds to a required data deliverable in the acceptance data package (ADP), per Chapter 4, it is noted with "[ADP]."

a. Design application notes, operational manuals, technical reports, and design analyses (e.g., FMEA).

b. Complete unit build history starting at the lowest level of assembly.

c. Identification of manufacturing instructions and processes used to build the unit.

d. Complete build inspection and test records, including physical and functional discrepancies, their resolution, and repair and rework history [ADP].

e. Material review board (MRB) actions, waivers, and deviations [ADP].

f. Test history, including environmental test exposure and related measurements; trend data across the testing; accumulative trend data across family of units; failures and anomalies during unit test; resolution; and retest.

g. Identification of associated test equipment and test software along with critical test calibration results.

h. Associated failure reports, including failure analyses leading to identification of root cause, disposition, and corrective action [ADP].

i. Identification of any unverified failure (a failure in which the root cause has not been clearly established) and analysis of worst-case repair. If, in subsequent testing, the failure never occurs again, rationale should be given for ascribing the failure to a cause other than flight hardware [ADP].

j. Cumulative operating time or number of cycles and accumulated pressure, vibration and temperature, and other exposures.

k. Unit as-built configuration description including a configuration status accounting for the as-built versus as-designed configuration at the time of unit delivery [ADP].

l. Records reflecting traceability of parts, materials, and subassemblies installed.

m. Storage history.

n. History of the unit from the time it is first integrated into a higher assembly, to include initial installation date; removal date(s); reason for removal; discrepancy and failure history; and traceability references to all inspection, discrepancy, failure, rework, repair, and retest paperwork.

o. High resolution of product photographs from before conformal coating, after conformal coating, and before enclosure closing [ADP].

D.4 It is recommended that the following records and data are required of suppliers delivering payloads. These are payload-level considerations.

a. Build log.

b. Inspection history.

c. Chronological test history, including all out-of-sequence operations.

d. Configuration status accounting of the as-built versus the as-designed configuration.

e. A record of failure, anomalies, variations, and deviations identified during vehicle-level or system-level test (including any retest) and their resolution, including root cause determination and corrective action.

f. Identification of any unverified failure (a failure in which the root cause has not been clearly established) and analysis of worst-case repair. If, in subsequent testing, the failure never occurs again, rationale should be given for ascribing the failure to a root cause other than flight hardware.

g. Test history, including environmental test exposure and related measurements, trend data across the testing, and accumulative trend data across family of vehicles.

h. Waivers, deviations, and vehicle-level MRB actions.

i. Component/equipment time recorded, status of on-time, or number of cycles for cycle-sensitive.

j. Modification history, including a list and description on any modification approved and scheduled for retrofit.

k. Installation history of traceable components, including removal and replacement history.

l. Connector mate/demate logs.



| TOC | ChangeHistory | Preface | Chapter1 | Chapter2 | Chapter3 | Chapter4 | Chapter5 | Chapter6 | Chapter7 | Chapter8 | AppendixA | AppendixB | AppendixC | AppendixD | AppendixE | AppendixF | AppendixG | ALL |
 
| NODIS Library | Program Management(8000s) | Search |

DISTRIBUTION:
NODIS


This document does not bind the public, except as authorized by law or as incorporated into a contract. This document is uncontrolled when printed. Check the NASA Online Directives Information System (NODIS) Library to verify that this is the correct version before use: https://nodis3.gsfc.nasa.gov.