USING NASA QUALITY STANDARDS NASA Academy of Aerospace (AAQ) Quality Mini-Workshop

Ken CraneQuality Engineering Technical Discipline Team LeadNASA SAFETY CENTERMarch 22, 2012

disclaimer

The following slides are non PrescriptiveBut

Represent typical NASA Requirements and GuidelinesThat may be applied to

NASA grants and/or cooperative agreements

Herb Shivers NASA/MSFC

… mitigate risks associated with noncompliance. Risk considers the likelihood of noncompliance and the consequences associated with noncompliance, including the maturity, complexity, criticality, and value of work performed …

““

NASA Quality Policy

NPD 8730.5

NASA quality assurance programs shall

Herb Shivers NASA/MSFC

… attain confidence levels that are commensurate with the severity of consequences that would be incurred in the event of noncompliance.

“ “

Herb Shivers NASA/MSFC

… periodically reevaluated and adjusted based on changes to risk factors.“

“

NPR 8715.7 Expendable Launch Vehicle Payload Safety Program

This NPR applies to ELV payloads developed under a NASA grant or cooperative agreement NPR 5800.1, Grant and Cooperative

Agreement Handbook to ensure that the payload project

properly implements the safety requirements pertaining to use of NASA facilities and equipment

This NPR does not apply to payloads that will fly on suborbital launch vehicles Suborbital payloads are subject to the

policy and requirements of NPR 8715.3 and applicable local processes and requirements.

AS9003 Inspection and Test Quality System

Management Responsibility Quality System Contract Review Design Control Document and Data Control Purchasing Control of Customer-Supplied

Product Product Identification and

Traceability Process Control Inspection and Testing

Control of Inspection, Measuring, and Test Equipment

Inspection and Test Status Control of Nonconforming Product Corrective Action Handling, Storage, Packaging,

Preservation, and Delivery Control of Quality Records Internal Quality Assessment Training Servicing Statistical Techniques

WORKMANSHIP STANDARDS

Refer to contract/customer drawings Example (Not exhaustive) list MIL-HDBK-454B General Guidelines For Electronic Equipment IPC J-STD-001ES Space Applications Electronic Hardware Addendum to IPC J-

STD-001E Requirements for Soldered Electrical and Electronic Assemblies

SAMPLE LISTING OF NASA REQUIREMENTS AND GUIDANCE DOCUMENTS

NASA SP-2007-6105 NASA Systems Engineering Handbook

NASA-STD-8717.9 Standard for Lifting Devices and Equipment

NASA-STD-8719.11 Safety Standard for Fire Protection

NASA-STD-8719.13 NASA Software Safety Standard

NASA-STD-8719.7 Facility System Safety Guidebook

NASA-STD-8739.8 Software Assurance Standard

NPD 8730.1 Metrology and Calibration

NPR 7150.2 NASA Software Engineering Requirements

NPR 8715.3 NASA General Safety Program Requirements

NPR 8735.1 Procedures For Exchanging Parts, Materials, and Safety Problem Data Utilizing the Government-Industry Data Exchange Program and NASA Advisories

NPR 8735.2 Management of Government Quality Assurance Functions for NASA Contracts

NPD 8730.5 NASA Quality Assurance Program Policy

NPR 8715.6 NASA Procedural Requirements for Limiting Orbital Debris

EXAMPLEQuality Assurance Practices

1 Quality assurance (QA) personnel perform receiving and shipping inspections on all critical hardware whenever the hardware enters or leaves any facility. Critical hardware includes all flight hardware and any GSE that interfaces directly with flight hardware, or that is required to support launch readiness.

2 Final inspection of flight hardware is performed to formally released documents.

3 Projects define mandatory inspections for critical hardware (e.g., in-process and final) at *(your facility), subcontractors, and suppliers.

4 All personnel involved in handling or testing of flight hardware are certified to standards approved by the responsible QA organization.

5 Each project arranges for software quality assurance verification of the software traceability matrix to ensure that requirements are correctly applied and that critical mission software has been appropriately tested.

6 Each project develops a QA Plan (hardware and software).