LNEXT-SMA-REQ-0015 Rev A SCMAR 20250114.pdf

DOORS EXPORT

National Aeronautics and Space Administration

Goddard Space Flight Center Greenbelt, Maryland

LNEXT-SMA-REQ-0015, Revision A

Landsat Next, Code 426

Landsat Next Spacecraft Mission Assurance Requirements (SCMAR)

Risk Classification - C

Free Flyer Payload

LNext Reviewed – Not Subject to Export Control

1/14/2025

SCMAR LNEXT-SMA-REQ-0015 Revision A ii Use or disclosure of data contained on this page is subject to the restriction(s) on the title page of this document.

Landsat Next Spacecraft Mission Assurance Requirements

(SCMAR)

Signature/Approval Page Prepared by:

Electronic Signature in TDMS Approval Date in TDMS Samilet Lee Date Landsat Next Chief Safety and Mission Assurance Officer

NASA/GSFC, Code 383

Approved by:

Cagatay Aymergen Date Acting Landsat Next Project Manager / Landsat Next Deputy Project Manager

NASA/GSFC, Code 426

Cagatay Aymergen Date Acting Landsat Next Observatory Manager NASA/GSFC, Code 426

Evan Webb Date Landsat Next Mission System Manager NASA/GSFC, Code 599

Electronic Signatures available online at: https://ipdtdms.gsfc.nasa.gov iii Use or disclosure of data contained on this page is subject to the restriction(s) on the title page of this document.

CM Foreword This document is a Landsat Next Project Configuration Management (CM)-controlled document.

Changes to this document require prior approval of the applicable Configuration Control Board (CCB) Chairperson or designee. Proposed changes shall be submitted to the Landsat Next CM Office (CMO), along with supportive material justifying the proposed change. Changes to this document will be made by complete revision.

Questions or comments concerning this document should be addressed to:

NASA/Goddard Space Flight Center Landsat Next Project Office, Code 426 Attention: Configuration Management Office Greenbelt, Maryland 20771 iv Use or disclosure of data contained on this page is subject to the restriction(s) on the title page of this document.

Change History Log v Use or disclosure of data contained on this page is subject to the restriction(s) on the title page of this document.

Table of Contents SIGNATURE/APPROVAL PAGE ................................................................................................ II CM FOREWORD ..........................................................................................................................III CHANGE HISTORY LOG .......................................................................................................... IV

TABLE OF CONTENTS ................................................................................................................ V

LIST OF FIGURES ..................................................................................................................... VII LIST OF TABLES ....................................................................................................................... VII

1.0 GENERAL

1.1 Related Documents

1.1.1 Applicable Documents

1.1.2 Project Applicable Documents

1.1.3 Reference Documents

1.2 Systems Safety and Mission Assurance (SMA) Program

1.3 Management

1.4 Requirements Flowdown

1.5 Identification of Project-Level Critical Items (PCIs)

1.6 Suspension of Work Activities

1.7 Surveillance

1.8 Government Mandatory Inspection Points (GMIPs)

1.9 List of Suppliers

1.10 Use of Inherited Products/Items

1.11 Protection of Flight Hardware

1.12 Risk Management

2.0 QUALITY MANAGEMENT SYSTEM

2.1 General

2.2 Supplemental Quality Management System Requirements

2.2.1 Control of Nonconforming Product

2.2.2 Material Review Board (MRB)

2.2.3 Anomaly Reporting and Disposition

3.0 SYSTEM SAFETY

3.1 General

3.2 Mission Related Safety Requirements Documentation

3.3 System Safety Deliverables

3.3.1 System Safety Program Plan

3.3.2 Safety Requirements Compliance Checklist

3.3.3 Safety Data Package (SDP)

3.3.4 Hazard Analyses

3.3.4.1 Preliminary Hazard Analysis

3.3.4.2 Operations Hazard Analysis (OHA) and Hazard Verification Tracking Log (HVTL)

3.3.4.3 Operating and Support Hazard Analysis

vi Use or disclosure of data contained on this page is subject to the restriction(s) on the title page of this document.

3.3.5 Verification Tracking Log (VTL)

3.3.6 Hazardous Procedures for Payload I&T and Pre-launch Processing

3.3.7 Lifting Device Safety Requirements

3.3.8 Mishap Reporting and Investigation

3.3.9 NASA Expendable Launch Vehicle (ELV) Payload Safety Program Forms

4.0 RELIABILITY

4.1 Reliability Program Plan (RPP)

4.2 Analysis of Design

4.2.1 Failure Modes Effects and Criticality Analyses (FMECA) and Critical Items List (CIL)

4.2.2 Fault Tree Analysis (FTA)

4.2.3 Reliability Assessments and Predictions

4.3 Limited Life Analysis

4.4 Parts Stress Analysis

4.5 Worst-Case Analysis

5.0 SOFTWARE ASSURANCE

5.1 Software Assurance Program

5.2 Surveillance of Software Development, Maintenance, and Assurance Activities

6.0 WORKMANSHIP

6.1 General

6.2 Electrostatic Discharge Control (ESD)

6.3 Printed Circuit Boards (PCB)

6.4 Lead-Free Control Measures

7.0 EEE PARTS

7.1 General

7.2 Parts Control Board

7.3 Re-use of EEE Parts

7.4 Master EEE Parts List

8.0 MATERIALS AND PROCESSES

8.1 M&P Selection, Control, and Implementation Plan (MPCIP)

8.2 Materials Usage Agreement (MUA)

8.3 Materials Identification and Usage List (MIUL)

8.4 Life Test Plan and Final Report for Lubricated Mechanisms

8.5 Additive Manufacturing Control Plan (AMCP)

8.6 AM Part Production Plan (PPP)

9.0 CONTAMINATION CONTROL

9.1 Contamination Control Plan

9.2 Material Outgassing

9.3 Foreign Object Debris Program

10.0 METROLOGY AND CALIBRATION

vii Use or disclosure of data contained on this page is subject to the restriction(s) on the title page of this document.

10.1 Metrology and Calibration Program

10.2 Use of Calibrated and Non-Calibrated Instruments

11.0 GIDEP ALERTS AND PROBLEM ADVISORIES

11.1 Government-Industry Data Exchange Program (GIDEP)

11.2 Alert Disposition

11.3 GIDEP Reporting

11.4 Review Reporting

12.0 END ITEM ACCEPTANCE DATA (EIADP) PACKAGE

APPENDIX A ABBREVIATIONS AND ACRONYMS

APPENDIX B DEFINITIONS

List of Figures

No table of contents entries found.

List of Tables

Table 4.2.1-1 Severity Categories Table 4.2.1-2 Likelihood Rankings Table 4.2.1-3 Consequence Rankings

Use or disclosure of data contained on this page is subject to the restriction(s) on the title page of this document.

1.0 GENERAL

1.1 RELATED DOCUMENTS

1.1.1 Applicable Documents

Document Number Title Revision EEE-INST-002 Instructions for EEE Parts Selection, Screening, Qualification, and Derating

NASA-STD-6016

Standard Materials and Processes Requirements for Spacecraft

C

NASA-STD-8719.9 Lifting Standard B NASA-STD-8719.24 NASA Expendable Launch Vehicle Payload

Safety Requirements A

NASA-STD-8739.1 Workmanship Standard for Polymeric Application on Electronic Assemblies

B w/ Change 2

NASA-STD-8739.4 Workmanship Standard for Crimping, Interconnecting Cables, Harnesses, and Wiring

A w/Change 2

NASA-STD-8739.5 Workmanship Standard for Fiber Optic Terminations, Cable Assemblies, and Installation

A w/Change 2

NASA-STD-8739.6 Implementation Requirements for NASA Workmanship Standards

B

NASA-STD-8739.8 Software Assurance and Software Safety B NASA-STD-8739.12 Metrology & Calibration - w/Change 1 NPR 8715.7 Expendable Launch Vehicle Payload Safety

Program B

NPR 8735.2 Hardware Quality Assurance Program Requirements for Programs and Projects

C w/ CHANGE 1

GPR 7120.4 Risk Management Procedural Requirements E GSFC-STD-6001 Area Array Package Assembly and

Manufacturing Practices for Flight Hardware A

GSFC-STD-8001 Standard Quality Assurance Requirements for Printed Circuit Boards

KNPR 8715.3 KSC Safety Procedure Requirements L 48 CFR § 46.4 Code of Federal Regulations (CFR), Federal

Acquisition Regulations (FAR), Contract Management, Quality Management, Government Contract Quality Assurance

N/A

48 CFR § 46.5 Code of Federal Regulations (CFR), Federal Acquisition Regulations (FAR), Acceptance

N/A

48 CFR § 46.103 Code of Federal Regulations, Federal Acquisition Regulations (FAR), Contracting office responsibilities

N/A

48 CFR § 46.104 Code of Federal Regulations, Federal Acquisition Regulations (FAR), Contract administration office responsibilities

N/A

48 CFR § 46.202-2 Code of Federal Regulations, Federal Acquisition Regulations (FAR), Government reliance on inspection by contractor

N/A

Use or disclosure of data contained on this page is subject to the restriction(s) on the title page of this document.

Document Number Title Revision ANSI/ESD S20.20 Protection of Electrical and Electronic Parts, Assemblies and Equipment (Excluding Electrically Initiated Explosive Devices)

ASTM E595-15 Standard Test Methods for Total Mass Loss and Collected Volatile Condensable Materials from Outgassing in a Vacuum Environment

ECSS-Q-ST-70-10 Qualification of Printed Circuit Boards (15 November 2008)

C

GIDEP Operations Manual Government-Industry Data Exchange Program (GIDEP) Operations Manual

N/A

ANSI/IPC-2225 Sectional Design Standard for Organic Multichip Modules (MCM-L) and MCM-L Assemblies

N/A

IPC-6012

Space and Military Avionics Applications Addendum to IPC-6012F, Qualification and Performance Specification for Rigid Printed Boards

FS

IPC-6015 Qualification and Performance Specification for Organic Multichip Module (MCM-L) Mounting and Interconnecting Structures

N/A

IPC-6018 Qualification and Performance Specification for High Frequency (Microwave) Printed Boards

D

IPC/WHMA-A-620 Requirements and Acceptance for Cable and Wire Harness Assemblies

E

IPC/WHMA-A-620 Space and Military Applications Electronic Hardware Addendum to IPC/WHMA-A- 620E

E-S

IPC-J-STD-001 Requirements for Soldered Electrical and Electronic Assemblies

H

IPC J-STD-001 Space and Military Applications Electronic Hardware Addendum to IPC J-STD-001H Requirements for Soldered Electrical and Electronic Assemblies

HS

MIL-PRF-55110 Performance Specification: Printed Wiring Board, Rigid, General Specification For

J W/AMENDMENT 1

AS9100 Quality Systems - Aerospace - Model for Quality Assurance in Design, Development, Production, Installation and Servicing

D

In this document, citations are assumed to be the latest version unless otherwise noted.

This document table was generated from the Landsat Next Common Reference and Applicable Documents List (LNEXT-MGMT-DESC-0008) Rev E.

1.1.2 Project Applicable Documents

Document Number Title LNEXT-SC-PLAN-0055 Landsat Next Spacecraft Contract Data Requirements List

(CDRL) and Data Item Descriptions (DID) In this document, citations are assumed to be the latest version unless otherwise noted.

This document table was generated from the Landsat Next Common Reference and Applicable Documents List (LNEXT-MGMT-DESC-0008) Rev E.

Use or disclosure of data contained on this page is subject to the restriction(s) on the title page of this document.

1.1.3 Reference Documents

Document Number Title Revision NASA-STD-8739.10 Electrical, Electronic, and Electromechanical

(EEE) Parts Assurance Standard

In this document, citations are assumed to be the latest version unless otherwise noted.

This document table was generated from the Landsat Next Common Reference and Applicable Documents List (LNEXT-MGMT-DESC-0008) Rev E.

1.2 SYSTEMS SAFETY AND MISSION ASSURANCE (SMA) PROGRAM

SCMAR-3 The contractor shall implement a safety and mission assurance program that is consistent with contractual requirements.

SCMAR-324 The mission assurance program shall cover:

• Flight hardware and software that is designed, built, or provided by the contractor and its subcontractors or furnished by the government, from project initiation through launch and mission operations

• The ground support equipment that interfaces with flight items to the extent necessary to assure the integrity and safety of flight items

• Ground systems required for spacecraft communication, command and control, health and safety monitoring, and science data processing/distribution.

1.3 MANAGEMENT

SCMAR-8 The contractor shall designate a manager for assurance activities.

SCMAR-325 The assurance manager shall not be responsible for project costs and schedules other than those pertaining to assurance activities.

SCMAR-9 The contractor shall ensure that the assurance manager has direct access to upper management that is independent of project management, with functional freedom and authority to interact with all elements of the project.

Use or disclosure of data contained on this page is subject to the restriction(s) on the title page of this document.

1.4 REQUIREMENTS FLOWDOWN

SCMAR-11 The contractor shall ensure flow down of SMA requirements to all suppliers based on the work to be performed and establish a process to verify compliance, with the exception of those approved for relief via the Inherited Item Risk Assessment process (see Section 1.9 "Use of Inherited Products/Items").

SCMAR-12 The contractor’s contract review and purchasing processes shall indicate the method for documenting, communicating and reviewing requirements with sub-tier suppliers to ensure requirements are met.

SCMAR-13 The contractor shall ensure that quality plans, processes, procedures, hardware and software submitted by the contractor’s sub-tier suppliers are compliant with the requirements in this MAR, as applicable.

1.5 IDENTIFICATION OF PROJECT-LEVEL CRITICAL ITEMS (PCIS)

SCMAR-15 The contractor shall identify its critical items for incorporation into the project-level critical items (PCIs) developed in accordance with NPR 8735.2, Section 4.1.4 “Critical Items and Processes Determination”.

Identification of critical items and processes should include the results of system safety and reliability analyses.

1.6 SUSPENSION OF WORK ACTIVITIES

SCMAR-18 The contractor shall direct the suspension of any work activity that presents an unsafe work condition to personnel or imminent danger to property.

1.7 SURVEILLANCE

SCMAR-20 The contractor shall provide access to quality management system documentation, information systems and work products/artifacts to NASA representatives.

SCMAR-21 The work activities, operations, and documentation performed by the

Contractor and sub-tier contractors, or suppliers shall be subject to evaluation, review, audit, inspection, and survey by NASA representatives at various points over the program/project development lifecycle.

Use or disclosure of data contained on this page is subject to the restriction(s) on the title page of this document.

SCMAR-22 In accordance with Code of Federal Regulations, Federal Acquisition Regulations (FAR), Contracting office responsibilities, 48 CFR § 46.103, Code of Federal Regulations, Federal Acquisition Regulations (FAR), Contract administration office responsibilities, 48 CFR § 46.104, Code of Federal Regulations, Federal Acquisition Regulations (FAR), Government reliance on inspection by contractor, 48 CFR § 46.202-2, Code of Federal Regulations (CFR), Federal Acquisition Regulations (FAR), Contract Management, Quality Management, Government Contract Quality Assurance, 48 CFR § 46.4, and Code of Federal Regulations (CFR), Federal Acquisition Regulations (FAR), Acceptance, 48 CFR § 46.5, the contractor shall grant physical or remote access to NASA representatives to conduct an on-site and/or remote audit, assessment, or inspection upon notice. A 30-day notice will be provided to the supplier/contractor prior to the start of an assessment.

SCMAR-327 The supplier/contractor shall supply personnel, documents, records, equipment, and an acceptable work area within the contractor’s facilities to assist with the audit/assessments/inspections.

SCMAR-23 The contractor shall report the status of facility operations and quality metrics to NASA on a quarterly basis. This shall include the following data for 1st tier and 2nd tier suppliers of project-defined critical items:

• Quality escapes - Any product released by an internal or external supplier that is subsequently determined to be nonconforming to contract and/or product specification requirements.

• First Pass Yield - A measure of quality in a process that reflects the percentage of product made correctly without any rework or corrective activity.

• Supplier Defect Rate - The supplier defeat rate measures the percentage of materials or product received from suppliers that do not meet required or compliance specifications.

• Internal Audit results

1.8 GOVERNMENT MANDATORY INSPECTION POINTS (GMIPS)

SCMAR-29 For cost plus projects, the contractor shall provide a proposed GMIP plan, which will be used by the government in determining the final GMIPs that will be conducted. Hardware Quality Assurance Program Requirements for Programs and Projects, NPR 8735.2 may be used as a guide.

Use or disclosure of data contained on this page is subject to the restriction(s) on the title page of this document.

SCMAR-30 Prior to the start of manufacturing, the contractor shall provide work instructions, procedures, drawings, etc. that are required for performing the planned inspections.

1.9 LIST OF SUPPLIERS

SCMAR-344 The contractor shall provide a list of suppliers used for product produced under this contract (SA-02).

1.10 USE OF INHERITED PRODUCTS/ITEMS

Inherited items are components that will be build-to-print (BTP), or rebuilt with modification, or are available as commercial-off-the-shelf (COTS), or were previously developed and exist (e.g., spares). The contractor may choose to use the Inherited Item Risk Assessment (IIRA) process at their discretion for some components. The process can be initiated by providing a list of candidate inherited items to the CSO.

SCMAR-345 The contractor shall provide data for candidate inherited items as requested by the Standard Components Commodity Risk Assessment Engineer (SC CRAE). Data needed for a Phase 1a IIRA (which will determine acceptability of the item to be inherited) may include but are not limited to:

• Previous on-orbit usage history of the component (if applicable)

• Manufacturer

• Changes in the design since last usage

• Planned usage environment versus previous usage environments

• Validation that the component will be used within its specification sheet limits

The SC CRAE will review the candidate items, and if they are acceptable to the CSO as inherited items, certain SC MAR requirements are verified and CDRL deliveries are satisfied by the IIRA process.

Use of this process does not relieve the contractor from meeting contractual performance, functional and mission lifetime requirements for the Inherited Product.

1.11 PROTECTION OF FLIGHT HARDWARE

SCMAR-38 The contractor shall evaluate the potential for Ground Support Equipment

(GSE) to damage flight hardware and use appropriate means to prevent such damage from occurring.

Use or disclosure of data contained on this page is subject to the restriction(s) on the title page of this document.

SCMAR-39 The approach to obviate GSE damage to flight hardware shall be presented prior to the start of testing and at subsequent review milestones.

SCMAR-40 Prior to performing work on flight hardware, the performing organization shall Identify a list of items, if any, that are sensitive to normal handling environments, such as presence of light, presence of metal objects (magnets), or presence of humidity outside of normal cleanroom and workmanship limits.

SCMAR-41 The contractor shall hold a meeting on the day work is to be performed, prior to the start of each shift, that includes a discussion of the list of items defined in SCMAR-40.

1.12 RISK MANAGEMENT

SMA activities should be tightly linked with the project’s Risk Management processes. For example, risks that evolve from reliability analyses that affect overall mission objectives should be managed in the project’s risk database when not eliminated or mitigated to noncredible likelihood levels.

Use or disclosure of data contained on this page is subject to the restriction(s) on the title page of this document.

2.0 QUALITY MANAGEMENT SYSTEM

2.1 GENERAL

SCMAR-46 The contractor shall have a quality management system that is compliant with the requirements of Quality Systems - Aerospace - Model for Quality Assurance in Design, Development, Production, Installation and Servicing, AS9100.

2.2 SUPPLEMENTAL QUALITY MANAGEMENT SYSTEM REQUIREMENTS

2.2.1 Control of Nonconforming Product

SCMAR-49 The contractor shall have a documented closed loop system for identifying, reporting, and correcting product nonconformances.

SCMAR-329 The system shall ensure that the adequacy of corrective action is determined by audit, inspection or test, that objective evidence is collected, and that preventive action is implemented to preclude recurrence.

2.2.2 Material Review Board (MRB)

SCMAR-51 The contractor shall have a documented process(es) for the establishment and operation of an MRB to process major non-conformances, which are those that affect form, fit, function, require a software change, involve the presence of FOD, or those that the contractor determines involves elevated risk.

SCMAR-52 The contractor shall appoint a MRB chairperson who is responsible for implementing the MRB process and for appointing contractor representatives as MRB members.

SCMAR-53 The MRB process shall include a government representative as a participating member on MRB actions involving major nonconformances.

SCMAR-54 The government shall be provided notice within 24 hours of occurrence of a major non-conformance and applicable documentation in advance of scheduled MRB meetings.

SCMAR-55 The MRB shall use the following disposition actions:

Use or disclosure of data contained on this page is subject to the restriction(s) on the title page of this document.

• Scrap — the product is not usable

• Re-work/Re-test — the product will be re-worked/re-tested to conform to requirements (sometimes referred to as “return to print”)

• Return to supplier — the product will be returned to the supplier

• Repair — the product will be repaired

• Use as is — the product will be used as is

2.2.3 Anomaly Reporting and Disposition

SCMAR-62 The contractor shall have a documented process for the establishment and operation of an anomaly review board (ARB) to process (report and disposition) major anomalies, which are those that have resulted in hardware or software test failures and damage or potential damage to hardware.

SCMAR-63 Reporting of major anomalies shall begin with the first application of power at the component or board level, flight software acceptance testing and when interfacing with flight hardware, and the first mechanical operation.

SCMAR-64 The ARB shall include a government representative who will be a participating member.

SCMAR-65 The government shall be provided notice within 24 hours of occurrence of an anomaly and applicable documentation in advance of scheduled ARB meetings.

SCMAR-66 Failures that cannot be duplicated, have unknown root cause, or cannot be verified shall be assessed for residual risk, declared as red flag problem failure records (PFRs), and brought to the project risk board for disposition.

Use or disclosure of data contained on this page is subject to the restriction(s) on the title page of this document.

3.0 SYSTEM SAFETY

3.1 GENERAL

SCMAR-69 The contractor shall document and implement a system safety program, support the ELV Safety Review Process as defined in Chapter 3 of Expendable Launch Vehicle Payload Safety Program, NPR 8715.7, comply with launch service provider requirements, and comply with launch range safety requirements.

SCMAR-70 The contractor shall include the following specific safety requirements in the system safety program:

SCMAR-71 The contractor shall incorporate three independent inhibits in the design

(dual failure tolerant) if a system failure may lead to a catastrophic hazard. A prelaunch catastrophic hazard is a payload-related hazard, condition, or event occurring prior to launch that could result in a fatal injury to personnel or loss of a ground facility. A post-launch catastrophic hazard is a payload-related hazard, condition, or event occurring after launch and up to payload separation that could result in a fatal injury or loss of flight termination system.

SCMAR-72 The contractor shall incorporate two independent inhibits in the design

(single failure tolerant) if a system failure may lead to a critical hazard. A critical hazard is defined as a hazard, condition or event that may cause severe injury or occupational illness or major property damage to facilities.

SCMAR-73 The contractor shall adhere to specific detailed safety requirements, including compliance verification that must be met for design elements with hazards that cannot be controlled by failure tolerance. The process by which safety is incorporated into these design elements (e.g., structures and pressure vessels) is called "Design for Minimum Risk".

3.2 MISSION RELATED SAFETY REQUIREMENTS DOCUMENTATION

SCMAR-75 The contractor shall implement the launch range safety requirements that are applicable to the launch site.

Use or disclosure of data contained on this page is subject to the restriction(s) on the title page of this document.

SCMAR-331 The contractor shall implement the most stringent safety requirement in the event there are conflicting requirements. The sections below include the applicable requirements documents for the pertinent launch ranges:

ELV Eastern Test Range (ETR) or Western Test Range (WTR) Missions

• NASA Expendable Launch Vehicle Payload Safety Requirements, NASA-STD-8719.24

• KSC Safety Practices Procedural Requirements, KNPR 8715.3 (applicable at KSC property, KSC-controlled property, and offsite facility areas where KSC has operational responsibility)

• Expendable Launch Vehicle Payload Safety Program, NPR 8715.7

• Launch Site Facility-specific Safety Requirements, as applicable (e.g., Astrotech)

3.3 SYSTEM SAFETY DELIVERABLES

3.3.1 System Safety Program Plan

SCMAR-83 The contractor shall prepare a System Safety Plan (SSP) that describes the tasks and activities of system safety management and engineering required to identify, evaluate, and eliminate or control hazards to the hardware, software, and system design by reducing the associated risk to an acceptable level throughout the system life cycle, including launch range safety requirements

(SA-03).

3.3.2 Safety Requirements Compliance Checklist

SCMAR-85 The contractor shall document and implement a Safety Requirements

Compliance Checklist to demonstrate that the payload complies with NASA and range safety requirements (SA-04).

3.3.3 Safety Data Package (SDP)

SCMAR-88 The contractor shall prepare an integrated SDP to document the results of hazard analyses identifying the prelaunch, launch and ascent hazards associated with the flight system, ground support equipment, and their interfaces in hazard reports (SA-06).

Use or disclosure of data contained on this page is subject to the restriction(s) on the title page of this document.

3.3.4 Hazard Analyses

3.3.4.1 Preliminary Hazard Analysis

SCMAR-91 The contractor shall perform a Preliminary Hazard Analysis (PHA) to obtain an initial risk assessment and to identify safety critical areas of a concept or system. The PHA is based on the best available data, including mishap data from similar systems and other lessons learned.

SCMAR-92 The contractor shall evaluate hazards associated with the proposed design or function for severity, control approach (fault tolerance or design for minimum risk), and operational constraints.

SCMAR-334 The contractor shall identify safety provisions and alternatives that are needed to eliminate hazards or reduce their associated risk to an acceptable level.

SCMAR-93 The contractor shall deliver the PHA with SDP I (SA-06).

3.3.4.2 Operations Hazard Analysis (OHA) and Hazard Verification Tracking Log (HVTL) SCMAR-95 The contractor shall document, implement, and maintain an Operations

Hazard Analysis (OHA) and a Hazard Verification Tracking Log (HVTL) to demonstrate that hardware operations, test equipment operations, and integration and test (I&T) activities comply with the safety requirements of the facilities where the activities will be performed and that hazards associated with those activities are mitigated to an acceptable level of risk

(SA-05).

SCMAR-96 The contractor shall update and maintain the Hazard Verification Tracking

Log during I&T activities to track open issues.

Use or disclosure of data contained on this page is subject to the restriction(s) on the title page of this document.

3.3.4.3 Operating and Support Hazard Analysis

SCMAR-98 The contractor shall perform an Operating and Support Hazard Analysis

(O&SHA) to evaluate activities for hazards introduced during testing, transportation, storage, integration, and prelaunch operations at the launch site. The primary purpose is to evaluate the adequacy of procedures used to eliminate, control, or mitigate identified hazards so as to ensure implementation of safety requirements for personnel, procedures, and equipment during activities at the launch site.

SCMAR-99 The contractor shall submit the results of the O&SHA as a part of the SDP II and SDP III (SA-06).

3.3.5 Verification Tracking Log (VTL)

SCMAR-101 The contractor shall document and implement a VTL that documents a

Hazard Control and Verification Tracking process as a closed-loop system that ensures safety compliance has been satisfied per applicable launch range safety requirements.

SCMAR-102 The contractor shall document in the VTL the process of verifying the control of hazards by test, analysis, inspection, similarity to previously qualified hardware, or any combination of these activities.

SCMAR-103 The contractor shall ensure that verifications listed on the hazard reports refer to specific test, analysis, or inspection reports with a summary of the pertinent results.

SCMAR-104 The contractor shall make the results of these tests, analyses, and inspections available for government review.

SCMAR-105 The VTL shall identify hazard controls that are not verified as closed and shall be delivered with the SDP III (SA-06).

SCMAR-106 The contractor shall provide regular electronic updates of the VTL until all hazard controls are verified as closed.

Use or disclosure of data contained on this page is subject to the restriction(s) on the title page of this document.

3.3.6 Hazardous Procedures for Payload I&T and Pre-launch Processing SCMAR-108 The contractor shall document the hazardous procedures that will be implemented when integration and test activities and pre-launch activities are performed at processing facilities and the launch site (SA-06).

SCMAR-109 The contractor shall ensure that the procedures comply with applicable facility safety requirements.

SCMAR-110 The contractor shall provide safety support for the implementation of hazardous procedures.

3.3.7 Lifting Device Safety Requirements

A Critical Lift is defined as a lift during which failure/loss of control presents an elevated risk of serious injury, loss of life, or loss of one-of-a-kind articles, or high dollar items, whose loss would have serious programmatic or institutional impact.

SCMAR-113 The contractor shall implement the following safety requirements for lifting devices and equipment (LDE) when performing NASA work at non-NASA facilities:

SCMAR-114 • Overhead cranes, winches, and wire rope hoists shall have a dual hoist braking system installed per the Lifting Standard, NASA-STD-

8719.9. Chain hoists typically do not have dual brakes as standard equipment unless included in the manufacturer’s design when specifically requested by the user. A single hoist motor holding brake in combination with a Variable Frequency Drive (VFD) dynamic braking system is an acceptable dual braking system.

• Label and tag LDE per the Lifting Standard, NASA-STD-8719.9, Section 4.9 requirements with no more than its Working Load Limit (WLL) as determined by the original equipment manufacturer (OEM) or its current certified WLL if that value is lower than the OEM rated WLL.

• Perform an initial one-time proof load test per the following Lifting Standard, NASA-STD-8719.9, Section 4.5 requirements:

• 1.25X WLL for overhead cranes.

• 1.25X WLL for mobile aerial platforms that will be used near critical hardware.

• 1X WLL for mobile cranes and derricks (.95X to 1X is acceptable).

Use or disclosure of data contained on this page is subject to the restriction(s) on the title page of this document.

• 1.25X WLL for below-the-hook (BTH) lifting devices.

• Slings (i.e., wire rope, synthetics, chain, etc.,) should only be proof load tested beyond its WLL with OEM approval.

• 2X WLL for rigging hardware items used for critical lifts (i.e., shackles.

hoist rings. turnbuckles, etc.,).

• Perform a 1X WLL load test every four years after the initial proof test on all

LDE.

• In addition to visual inspection, perform a post load test non-destructive test (NDT) inspection (e.g., radiographic, ultra-sonic, magnetic particle, dye penetrant, etc.) on crane hooks and critical welds. A critical weld is one in which a failure would result in a failure of the hardware. The inspections will be performed by an American Society of Non-destructive Testing (ASNT) or equivalently trained inspector.

3.3.8 Mishap Reporting and Investigation

SCMAR-126 The contractor shall prepare a Pre-Mishap Plan that describes appropriate mishap and close call notification, reporting, recording, and investigation procedures (SA-08).

SCMAR-127 The contractor shall report accidents, test failures, or other mishaps and close calls promptly to NASA.

SCMAR-128 The contractor shall promptly investigate test failures, or other mishaps and close calls to determine the root cause of the mishap/close call.

3.3.9 NASA Expendable Launch Vehicle (ELV) Payload Safety Program Forms SCMAR-130 The contractor shall prepare NASA Expendable Launch Vehicle Payload

Safety Forms. The forms are available at URL https://kscsma.ksc.nasa.gov/PayloadSafety/forms.

https://kscsma.ksc.nasa.gov/PayloadSafety/forms

Use or disclosure of data contained on this page is subject to the restriction(s) on the title page of this document.

4.0 RELIABILITY

4.1 RELIABILITY PROGRAM PLAN (RPP)

SCMAR-133 The contractor shall document and implement an RPP that includes both qualitative and quantitative techniques to support decisions regarding mission success and safety throughout system development (SA-09).

SCMAR-134 The contractor shall include a detailed approach to the analysis of hardware and software for their contributions to system reliability and mission success.

The contractor should perform reliability analyses concurrent with design and maintain consistency between reliability analyses so that identified problem areas are addressed, and corrective action taken in a timely manner.

4.2 ANALYSIS OF DESIGN

4.2.1 Failure Modes Effects and Criticality Analyses (FMECA) and Critical Items List

(CIL)

SCMAR-138 The contractor shall perform and maintain Failure Modes and Effects

Criticality Analyses (FMECA) that address Spacecraft flight hardware and software, Spacecraft to Instrument Interfaces, and ground support equipment that interfaces with flight systems that are being designed, built, or provided from project initiation through launch and mission operations.

SCMAR-336 The contractor shall include likelihood, cause, detection and mitigation, and the effects of each failure mode at the local, subsystem, and system or mission levels. Components and systems designated as inherited items shall be analyzed at the interface level. All others shall be analyzed at the box or functional level. (SA-10).

SCMAR-139 The contractor shall prepare and maintain a Critical Items List for items with failure-mode severity categories 1SC (Safety Critical), 1, 1R (Redundant), 2S (Safety), and 2 per Table 4.2.1-1.

Use or disclosure of data contained on this page is subject to the restriction(s) on the title page of this document.

Table 4.2.1-1 Severity Categories

SCMAR-176 The contractor shall prepare and maintain a Single Point Failure (SPF) list for modes resulting in category 1 and 1SC severities per table 4.2.1-1 and document applicable failure causes, mitigations, and retention rationale.

SCMAR-177 The contractor shall identify and assess any known common cause failure modes and their causes for category 4T items.

SCMAR-178 The contractor shall estimate the likelihood score for each failure mode from

1-5 using the appropriate criteria from Risk Management Procedural Requirements, GPR 7120.4 (shown in Table 4.2.1-2) or another scale approved by GSFC Reliability. Each likelihood estimation can be based on qualitative assessment and/or failure rate data from other analyses (e.g., system calculations) in order to score each failure mode for the mission duration.

Use or disclosure of data contained on this page is subject to the restriction(s) on the title page of this document.

Table 4.2.1-2 Likelihood Rankings

SCMAR-181 The contractor shall identify the consequence for each failure mode using the appropriate criteria from Risk Management Procedural Requirements, GPR

7120.4 (shown in Table 4.2.1-3).

Table 4.2.1-3 Consequence Rankings

4.2.2 Fault Tree Analysis (FTA)

SCMAR-185 The contractor shall perform and maintain qualitative fault tree analyses

(FTA) (SA-11), as deemed necessary by the Chief Safety and Mission Assurance Officer (CSO) and the Mission Systems Engineer (MSE).

Use or disclosure of data contained on this page is subject to the restriction(s) on the title page of this document.

SCMAR-187 Fault trees shall address both hardware and software contributions at a level necessary to identify risks, verify mitigations, and assist in the development of fault management.

SCMAR-188 In the event the contractor or the project identifies a major mission risk contributor in the FMECA or FTA, the contractor shall quantify (and if necessary, expand) the appropriate FTA or the portions of the FTA necessary for detailed risk assessment, as deemed necessary by the CSO and the MSE.

FTA should also be considered for use to check the FMECAs for completeness.

4.2.3 Reliability Assessments and Predictions

SCMAR-191 The contractor shall perform comparative numerical assessments and/or reliability predictions (SA-12) to perform the following:

• Assist in trade studies by evaluating alternative design concepts, redundancy and cross strapping approaches, and part substitutions.

• Identify the elements of the design which are potentially the greatest detractors of system reliability.

• Identify those potential mission-limiting elements and components that will require special attention in part selection, testing, environmental isolation, and/or special operations.

• Evaluate the design in terms of mission success requirements.

• Evaluate the impact of proposed engineering changes and waiver requests on reliability.

• Mil-HDBK-217 is no longer part of the approved list of data sources SCMAR-198 Reliability prediction methods shall be verified with GSFC prior to analysis delivery.

SCMAR-199 The results of the reliability assessments shall be reported at all design reviews and associated Engineering Peer Reviews starting with System Peer Review (SPR).

SCMAR-200 The presentations shall include comments on how the analyses were used to perform design trade-offs or how the results were taken into consideration when making design or risk management decisions.

Use or disclosure of data contained on this page is subject to the restriction(s) on the title page of this document.

4.3 LIMITED LIFE ANALYSIS

SCMAR-202 The contractor shall perform and maintain Limited Life Item Analysis (LLA) that includes expected life, required life, and an assessment of life margin (including servicing and maintenance) and provides retention rationale for items with an expected life of less than 2x the required life and fosters a plan to manage limited life items (SA-13).

SCMAR-203 The risk assessment and mitigations plans shall factor in wear caused by atomic oxygen, solar and trapped radiation, shelf-life, extreme temperatures, thermal cycling, write/erase cycles and mechanical wear or fatigue, and include refurbishment and maintenance plans.

4.4 PARTS STRESS ANALYSIS

SCMAR-205 The contractor shall perform parts stress and derating analyses for electrical, electronic, and electromechanical (EEE) parts in accordance with Instructions for EEE Parts Selection, Screening, Qualification, and Derating, EEE-INST-002 (SA-14) or the contractor’s own established standard, unless specifically relieved of this requirement by the GSFC Inherited Items Risk Assessment process (See Section 1.10).

SCMAR-206 If alternate derating guidelines are requested to be used, they shall be submitted to the Parts Control Board and GSFC Reliability Engineering for approval.

4.5 WORST-CASE ANALYSIS

SCMAR-208 For designs that are new, significantly modified, or being used in an environment not covered by the existing analysis, the contractor shall perform worst-case analyses (WCA) (SA-15).

Use or disclosure of data contained on this page is subject to the restriction(s) on the title page of this document.

5.0 SOFTWARE ASSURANCE

5.1 SOFTWARE ASSURANCE PROGRAM

SCMAR-340 The contractor shall establish a software assurance program consisting of a planned and systematic set of activities and disciplines that ensures that software conforms to organizational and project-specific requirements and standards throughout the project lifecycle, where software is defined as:

• Computer programs, procedures, and possibly associated documentation and data pertaining to the operation of a computer system

• All or a part of the programs, procedures, rules, and associated documentation of an information processing system

• Program or set of programs used to run a computer

• All or part of the programs which process or support the processing of digital information Part of a product that is the computer program or the set of computer programs.

Note: The software definition applies to software developed by NASA, software developed for NASA, software maintained by or for NASA, COTS, GOTS, MOTS, OSS, reused software components, auto-generated code, embedded software, software used on ground support equipment, the software executed on processors embedded in programmable logic devices, legacy, heritage, applications, freeware, shareware, trial or demonstration software, and open-source software components.

SCMAR-218 The contractor shall ensure the independence of software assurance from software engineering.

SCMAR-219 The contractor shall document and implement a Software Assurance Plan and schedule compliant to Software Assurance and Software Safety Standard, NASA-STD-8739.8 (SA-16).

SCMAR-220 The plan includes the software assurance processes, procedures, tools and techniques to be used commensurate with the software classification and safety criticality assessment, with additional tailoring in accordance with guidance provided by Software Assurance and Software Safety Standard, NASA-STD-8739.8 for each category of software (new, reused, Off-the-shelf, auto-generated code, etc..).

Use or disclosure of data contained on this page is subject to the restriction(s) on the title page of this document.

SCMAR-221 The plan addresses both Software Assurance and Software Safety disciplines. This includes the necessary collaboration with relevant SMA and Engineering stakeholders (i.e., system safety, system reliability, hardware quality, system security, and software engineering), and the process by which traceability is established to their respective analyses and/or requirements.

5.2 SURVEILLANCE OF SOFTWARE DEVELOPMENT, MAINTENANCE, AND

ASSURANCE ACTIVITIES

SCMAR-223 Consistent with the general requirement for support of government surveillance (see Section 1.6 ""Surveillance""), the contractor shall provide on-request access to following:

• Software problem reports

• Software documentation (i.e., management plans, assurance plans, configuration management plans, requirements specifications, design documents, test plans, test cases, test procedures, test results, software review results, software engineering and assurance schedule, maintenance plans)

• Source code

• Findings and corrective actions from software process and product audits and assessments

• Software Assurance Status Report

Use or disclosure of data contained on this page is subject to the restriction(s) on the title page of this document.

6.0 WORKMANSHIP

6.1 GENERAL

SCMAR-230 The contractor shall implement a workmanship program to assure that electronic packaging technologies, processes, and workmanship meet mission objectives for quality and reliability per the requirements of the following standards:

• Workmanship Standard for Polymeric Application on Electronic Assemblies, NASA-STD-8739.1, excluding sections 8.1, 9.1, and 10.1

• Workmanship Standard for Fiber Optic Terminations, Cable Assemblies, and Installation, NASA-STD-8739.5

• Requirements for Soldered Electrical And Electronic Assemblies, IPC-J-STD- 001xS.

• Ceramic Column Grid Array Design and Manufacturing Rules for Flight Hardware, GSFC-STD-6001.

• Sectional Design Standard for Organic Multichip Modules (MCM-L) and MCM- L Assemblies, ANSI/IPC-2225.

• Qualification and Performance Specification for Organic Multichip Module (MCM-L) Mounting and Interconnecting Structures, IPC-6015

SCMAR-240 The contractor shall comply with one of the following standards for electrical cables and harnesses:

• Workmanship Standard for Crimping, Interconnecting Cables, Harnesses, and Wiring, NASA-STD-8739.4

• Requirements and Acceptance for Cable and Wire Harness Assemblies, IPC/WHMA-A-620 with Space and Military Applications Electronic Hardware Addendum to IPC/WHMA-A-620E, IPC/WHMA-A-620

6.2 ELECTROSTATIC DISCHARGE CONTROL (ESD)

SCMAR-244 The contractor shall prepare and implement an ESD control plan that conforms to the requirements of Protection of Electrical and Electronic Parts, Assemblies and Equipment (Excluding Electrically Initiated Explosive Devices), ANSI/ESD S20.20 (Excluding Electrically Initiated Explosive Devices)" (SA-17).

Use or disclosure of data contained on this page is subject to the restriction(s) on the title page of this document.

6.3 PRINTED CIRCUIT BOARDS (PCB)

SCMAR-246 The contractor shall comply with one of the following standards for rigid printed circuit boards:

• Space and Military Avionics Applications Addendum to IPC-6012F, IPC-6012

(the latest revision preferred, but older revisions acceptable based on inherited designs or contractor standard practices)

• MIL-PRF-55110H Performance Specification: Printed Wiring Board, Rigid, General Specification For

• Qualification of Printed Circuit Boards (15 November 2008), ECSS-Q-ST-70-10 SCMAR-251 In cases in which high-density interconnect (HDI) components (e.g., reconfigurable FPGAs, high-density SRAMs, etc.) or board population are present, the contractor shall consult with the GSFC Project and GSFC MPCB CRAE for a specification strategy to avoid extensive rebuilds or the incorporation of risky features solely in order to meet the spec. This consultation may result in deviations from the specifications above with no waiver required.

SCMAR-252 The contractor shall follow GSFC-STD-8001 section 6.5 for quality control

SCMAR-254 The developer shall deliver PCB coupon evaluation reports for information only before populating parts.

6.4 LEAD-FREE CONTROL MEASURES

SCMAR-258 The contractor shall document and implement a Lead-Free Control Plan

(LFCP) (SA-21).

SCMAR-259 The contractors shall submit uses of lead-free solder or surface finishes to the

NASA project office for approval before use.

Use or disclosure of data contained on this page is subject to the restriction(s) on the title page of this document.

7.0 EEE PARTS

7.1 GENERAL

SCMAR-262 The contractor shall document and implement a parts control plan (PCP) per

Level 3 requirements of EEE Parts Selection, Screening, Qualification, and Derating, EEE-INST-002 (SA-22).

SCMAR-351 The PCP shall address counterfeit parts using the guidelines of SAE AS5553.

Note: The contractor may use as is Class V, S, Q, B, M compliant microcircuits; JANS, JANTXV, and JANTX semiconductors.

7.2 PARTS CONTROL BOARD

SCMAR-264 The contractor shall establish a Parts Control Board (PCB) that is responsible for the planning, management, and coordination of the selection, application, and procurement requirements of EEE parts.

SCMAR-265 The contractor shall identify the person responsible for directing and managing the EEE parts program and interfacing with government assurance personnel.

SCMAR-266 The contractor shall include the GSFC Project Parts Engineer as a voting member of the PCB.

7.3 RE-USE OF EEE PARTS

SCMAR-268 The contractor shall require approval of the PCB to re-use EEE parts that have been installed.

7.4 MASTER EEE PARTS LIST

SCMAR-270 The contractor shall develop and deliver a Master EEE Parts List in accordance with SA-23 and maintain it for the duration of the project.

Use or disclosure of data contained on this page is subject to the restriction(s) on the title page of this document.

8.0 MATERIALS AND PROCESSES

8.1 M&P SELECTION, CONTROL, AND IMPLEMENTATION PLAN (MPCIP)

SCMAR-273 The contractor shall prepare and implement a Materials and Processes

(M&P) Selection, Control, and Implementation Plan (MPCIP) (SA-24).

SCMAR-338 Standard Materials and Processes Requirements for Spacecraft, NASA-STD-

6016 shall be used as a baseline, with contractor standard practices acceptable if associated command media are shared with NASA.

8.2 MATERIALS USAGE AGREEMENT (MUA)

SCMAR-275 The contractor shall prepare materials usage agreements (SA-25).

8.3 MATERIALS IDENTIFICATION AND USAGE LIST (MIUL)

SCMAR-277 The contractor shall prepare a materials identification and usage list (SA-26).

8.4 LIFE TEST PLAN AND FINAL REPORT FOR LUBRICATED MECHANISMS

SCMAR-279 The contractor shall prepare and implement a life test plan and final report for lubricated mechanisms (SA-27).

8.5 ADDITIVE MANUFACTURING CONTROL PLAN (AMCP)

SCMAR-281 The contractor shall prepare and implement an Additive Manufacturing

Control Plan (AMCP) for the design and manufacture of Additively Manufactured (AM) Parts (SA-28).

8.6 AM PART PRODUCTION PLAN (PPP)

SCMAR-283 The contractor shall prepare a Part Production Plan (PPP) for each AM part

(SA-29).

Use or disclosure of data contained on this page is subject to the restriction(s) on the title page of…