Attachment J.8 Ground Services Mission Assurance Requirements (GSMAR).pdf

Effective Date: May 30, 2025 Expiration Date: May 30, 2030

Check the SWGS CM tool Server at https://ipdtdms.gsfc.nasa.gov/frontmenu_dsp.cfm to verify that this is the correct version prior to use.

SWGS-SMA-REQ-0002, Revision A Space Weather Ground Services (SWGS), Code 492.0

Space Weather Ground Services (SWGS) Ground Services Mission Assurance

Requirements (GSMAR)

GSFC SWGS CMO

06/02/2025 Released

SWO Reviewed – Not Subject to Export Control https://ipdtdms.gsfc.nasa.gov/frontmenu_dsp.cfm

SWGS MAR SWGS-SMA-REQ-0002, Revision A Effective Date: May 30-, 2025 iii

Check the SWGS CM tool Server at https://ipdtdms.gsfc.nasa.gov/frontmenu_dsp.cfm to verify that this is the correct version prior to use.

Preface

This document is under Space Weather Ground Services (SWGS) configuration control. Once this document is approved, SWGS approved changes are handled in accordance with Class I and Class II change control requirements as described in the SWGS Configuration Management Procedures, and changes to this document shall be made by complete revision.

Any questions should be addressed to:

SWGS Configuration Management Office

NASA/GSFC

Code 492.0 Greenbelt, MD 20771 iv

Check the SWGS CM tool Server at https://ipdtdms.gsfc.nasa.gov/frontmenu_dsp.cfm to verify that this is the correct version prior to use.

Change History Log

Revision Effective Date

Description of Changes (Reference the CCR & CCB/ERB Approval Date)

Revision - 02/26/2025 Baseline Release following the approval of SWGS-CCR-0015 Revision A 05/30/2025 Updated following the approval of SWGS-CCR-0018 v

Check the SWGS CM tool Server at https://ipdtdms.gsfc.nasa.gov/frontmenu_dsp.cfm to verify that this is the correct version prior to use.

Deviations/Waivers Record

Section # / Requirement #

Deviation / Waiver #

CCR # Date Approved Title Mission

None vi

Check the SWGS CM tool Server at https://ipdtdms.gsfc.nasa.gov/frontmenu_dsp.cfm to verify that this is the correct version prior to use.

Table of Contents

1 INTRODUCTION

1.1 Purpose and Use

1.2 Requirement Identification and Application

1.3 Applicable Documents

1.4 Terms and Definitions

2 GENERAL REQUIREMENTS

2.1 Safety and Mission Assurance Program

2.2 SMA Management

2.3 Flow-Down of Requirements

2.4 Suspension of Work Activities

2.5 Surveillance of the Contractor

2.6 Risk Management

2.7 Mission Assurance Implementation Plan (MAIP)

3 QUALITY MANAGEMENT SYSTEM

3.1 Supplemental Quality Management System Requirements

3.1.1 Control of Nonconforming Product

3.1.2 Material Review Board

4 SYSTEM SAFETY

4.1 Safety Deliverables

4.1.1 Hazard Analysis

4.1.2 Software Safety Analysis

4.1.3 Verification Tracking Log

4.1.4 Safety Non-Compliance/Waiver Requests

4.1.5 Mishap Reporting and Investigation

5 RELIABILITY, MAINTAINABILITY, AND AVAILABILITY (RMA)

5.1 RMA Program

5.2 RMA Analyses

5.3 Spare Parts and Limited Life Items

6 SOFTWARE ASSURANCE

6.1 General

6.2 Verification and Validation

7 WORKMANSHIP STANDARDS

7.1 Training and Certification

7.2 Documentation

7.3 Acceptance Testing

7.4 Handling, Packaging, Transportation, and Storage

7.5 Electrostatic Discharge (ESD) Control

8 CALIBRATION

9 GIDEP ALERTS AND PROBLEM ADVISORIES

APPENDIX A REQUIREMENT APPLICABILITY MATRIX

APPENDIX B ACRONYMS AND GLOSSARY

SWGS MAR SWGS-SMA-REQ-0002, Revision - Effective Date: February 26, 2025

Check the SWGS CM tool Server at https://ipdtdms.gsfc.nasa.gov/frontmenu_dsp.cfm to verify that this is the correct version prior to use.

1 INTRODUCTION

1.1 Purpose and Use

“Ground Segment” is a general NOAA-NASA term used to refer to the collection of requirements and associated capabilities that support a mission, complementing the Flight and Launch Segments. Within Space Weather Observations (SWO), Space Weather Ground Services (SWGS) exists to provide the ground services that satisfy Ground Segment (GS) requirements of each SWO project. Depending on the project scope, the GS requirements may span antenna services, mission operations services (control center), and product services. The SWO Programs Division follows the NPR 7120.5 guidelines for technical authority, supported by NASA’s Safety and Mission Assurance (SMA) organization which provides appropriate mission assurance expertise. A Ground Services Chief Safety and Mission Assurance Officer (CSO) will be designated.

SWGS will seek to satisfy SWO project requirements through the use of NOAA enterprise infrastructure and common services, the use of partner-provided services, and the development of new capabilities. New capability development may be through contracts with industry. This SWGS GS Mission Assurance Requirements (MAR) document contains the full set of requirements that could be applied to any SWGS development contract to define the SMA activities that a SWGS Contractor is required to perform to assure the integrity and safety of work performed. GSMAR Sections 2.0 - 9.0 contain the SMA requirements to be applied to contracted activities.

The MAR address SMA in the following areas:

• Quality Management

• System Safety

• Reliability, Maintainability, & Availability (RMA)

• Software Assurance

• Workmanship Standards

• Calibration

• GIDEP (Government-Industry Data Exchange Program)

1.2 Requirement Identification and Application

The requirements use the identification convention GSMAR - ### or GSMAR - ####, with sequential numbers based on the SMA discipline MAR Section number. Three-digit requirements are applicable to all task order efforts, while four-digit requirements are allowed to be tailored by SWGS as appropriate for the SWO project or task order. There is a 4-digit Requirement Applicability Matrix in Appendix A of this document.

Tailoring may include edits or the determination that a requirement does not apply to a task order effort.

SWGS will use this GSMAR, with tailoring, to generate a task order MAR document that will become part of each technical package for procured work to specify the requirements applicable to that contracted effort.

The following two requirements direct the usage of three-digit and four-digit requirements in this GSMAR document:

GSMAR-100: Unless specifically stated otherwise, requirements GSMAR-(100-999) shall apply to each task order.

GSMAR-101: Requirements GSMAR-(1000-9999) in this GSMAR document shall be directed in specific task order efforts. Performance Work Statements (PWS) or Statements of Work (SOW) can tailor applicable documents or process standards to specify a subset of requirements, as determined by SWGS, together with the Ground CSO.

Check the SWGS CM tool Server at https://ipdtdms.gsfc.nasa.gov/frontmenu_dsp.cfm to verify that this is the correct version prior to use.

1.3 Applicable Documents

Below is the list of documents applicable to requirements in this MAR:

Document Number Title

392-WI-7150.4.1 Procedure for Planning and Implementing Software Assurance and Software Safety Programs

ANSI Z359 Fall Protection Code ANSI/ESD S20.20 Protection of Electrical and Electronic Parts, Assemblies and Equipment ANSI/IPC-J-STD-001 Requirements for Soldered Electrical and Electronic Assemblies As Applicable Material Safety Data Sheets DAO 209-3 Injury, Illness, Accident, and Fatality Investigation and Reporting FAR Part 46 Federal Acquisition Regulations, Parts 46.103, 46.104, 46.202-2, 46.4, 46.5 GPR 1700.1 Occupational Safety Program at Goddard Space Flight Center GPR 8621.4 GSFC Mishap/Close Call Preparation and Response GPR 8715.8 Fall Protection Requirements for GSFC GSFC 20-4 Transfer/Shipping Request (Government Property) (https://nef.nasa.gov/) GSFC 23-14 GSFC Mobile Crane Lift Plan Worksheet GSFC 23-8 GSFC Lifting Device Equipment Permit Application GSFC Form 4-56 GSFC Software Classification Form (https://nef.nasa.gov/)

IEEE C95.1 Standard for Safety Levels with Respect to Human Exposure to Radio Frequency Electromagnetic Fields, 3 kHz to 300 GHz

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

IPC-A-610 Acceptability of Electronics Assemblies

IPC-A-640 Requirements for Optical Fiber, Optical Cable, and Hybrid Wiring Harness Assemblies

IPC-J-STD-001FS Joint Industry Standard, Space Applications Electronic Hardware Addendum (except Chapter 10 of IPC-J-STD-001F)

ISO/IEC 17025-2017 General requirements for the competence of testing and calibration laboratories

NASA-STD-8719.11 NASA Safety Standard for Fire Protection and Lift Safety NASA-STD-8719.9 Standard for Lifting Devices and Equipment NASA-STD-8739.12 NASA Metrology and Calibration NASA-STD-8739.8B NASA Software Assurance and Software Safety Standard National Fire Protection Association (NFPA) 70 National Electric Code

NFPA 70E Standard for Electrical Safety in the Workplace NAO 209-1 NOAA Occupational Safety and Health

NPR 6000.1 Requirements for Packaging, Handling, and Transportation for Aeronautical and Space Systems, Equipment, and Associated Components

NPR 7150.2D NASA Software Engineering Requirements

NPR 8621.1D Requirements for Mishap and Close Call Reporting, Investigating, and Recordkeeping

NPR 8715.1 NASA Safety and Health Programs

NPR 8735.2 Hardware Quality Assurance Program Requirements for Programs and Projects

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

Check the SWGS CM tool Server at https://ipdtdms.gsfc.nasa.gov/frontmenu_dsp.cfm to verify that this is the correct version prior to use.

1.4 Terms and Definitions

The following terms and definitions apply throughout this document:

• Shall - Compliance by the Contractor is mandatory. Any deviation from these contractually imposed mandatory requirements requires the approval of the contracting officer

• Can - Denotes a discretionary privilege or permission

• May - Denotes a discretionary privilege or permission

• Should - Denotes a good practice and is recommended, but not required

• Will - Denotes an expected outcome and does not constitute a requirement

• Are/Is - Denotes descriptive material

• Assure - Used when mission assurance practitioners make certain that the specified mission assurance, management, and engineering activities have been performed by others.

• Ensure - Used when mission assurance practitioners themselves perform the specified activities.

• (CDRL MA - ##) - Refers to Mission Assurance items in the Contract Data Requirements List (CDRL)

• Government personnel - Anyone designated by Project Manager to act on behalf of the Government

• Days - Refers to business days unless specified as a calendar period (e.g., “1 month”), calendar days after contract award (DACA), or explicitly identified as calendar days

• Mission Critical - Item or function that must retain its operational capability to assure no mission failure (i.e., for mission success). [2] An item or function, the failure of which may result in the inability to retain operational capability for mission continuation if corrective action is not successfully performed. (Source NASA-STD-8729.1)

• Critical - A condition that may cause severe injury or occupational illness, or major property damage to facilities, systems, or ground hardware

• Safety-Critical - A term describing any condition, event, operation, process, equipment, or system that could cause or lead to severe injury, major damage, or mission failure if performed or built improperly or allowed to remain uncorrected. (Source NPR 8715.3)

• Safety-Critical Software - Software is classified as safety-critical if it meets at least one of the following criteria:

o Causes or contributes to a system hazardous condition/event o Provides control or mitigation for a system hazardous condition/event o Controls safety-critical functions o Mitigates damage if a hazardous condition/event occurs o Detects, reports, and takes corrective action if the system reaches a potentially hazardous state

Check the SWGS CM tool Server at https://ipdtdms.gsfc.nasa.gov/frontmenu_dsp.cfm to verify that this is the correct version prior to use.

2 GENERAL REQUIREMENTS

2.1 Safety and Mission Assurance Program

GSMAR-200: The Contractor shall implement a Safety and Mission Assurance (SMA) program that is consistent with contractual requirements. The SMA program shall cover ground systems that are designed, built, or provided by the Contractor and its subcontractors for satellite communication, command and control, health and safety monitoring, and data processing/distribution. This program should cover all applicable phases of the project lifecycle from project initiation through operational deployment, maintenance, and final decommissioning/disposal.

2.2 SMA Management

GSMAR-201: The Contractor shall designate a manager for SMA activities. The SMA manager shall not be responsible for project costs and schedules, other than those pertaining to assurance activities.

GSMAR-202: The Contractor shall ensure that the SMA manager has direct access to upper management that is independent of project management and shall have the functional freedom and authority to interact with all elements of the project.

GSMAR-203: The Contractor shall identify a primary SMA point of contact (SMA POC) with responsibility for leading the Contractor’s SMA activities.

2.3 Flow-Down of Requirements

GSMAR-204: The Contractor shall apply the system SMA requirements in this document to subcontractors and suppliers based on the work to be performed to ensure that the delivered product or service meets performance requirements. This includes flow down of any applicable 4-digit requirements contained in individual task orders.

GSMAR-205: The Contractor shall establish the processes for documenting, communicating, and reviewing requirements with sub-tier suppliers to ensure MAR requirements are met.

GSMAR-206: 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.

2.4 Suspension of Work Activities

GSMAR-208: The Contractor shall direct the suspension of any work activity that presents an unsafe work condition to personnel or imminent danger to property.

2.5 Surveillance of the Contractor

GSMAR-209: The work activities, operations, and documentation performed by the Contractor and sub-tier contractors or suppliers shall be subject to evaluation, review, audit, and inspection by the Government.

This includes access for designated Government representatives to conduct selected announced and unannounced reviews of Contractor operations.

GSMAR-210: The Contractor and/or suppliers shall grant access for Government representatives to conduct SMA assessments/surveys upon notice.

GSMAR-211: The Contractor shall provide resources to assist with SMA assessments/surveys.

GSMAR-212: The Contractor shall, upon request, provide Government SMA representatives with documents, records, and equipment required to perform their assurance and safety activities.

Check the SWGS CM tool Server at https://ipdtdms.gsfc.nasa.gov/frontmenu_dsp.cfm to verify that this is the correct version prior to use.

GSMAR-213: The Contractor shall maintain documentation required by its internal configuration management process for the products or services delivered to the government throughout the project lifecycle. The documents shall be available for review upon request.

GSMAR-214: The Contractor shall provide the Government SMA representative(s) with an acceptable work area within contractor facilities, including access to the internet.

GSMAR-215: The Contractor shall report the status of quality metrics to the Government on an agreed-upon basis (no less than monthly). The reports should include:

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

This could be number or open/closed RCCA investigations, open/closed Discrepancy Reports, etc.

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

• Internal Audit Results

• Software Quality Assurance Metrics

• Other Quality Metrics (as determined by the Government)

2.6 Risk Management

GSMAR-216: SMA activities should be tightly linked with the Contractor’s Risk Management processes.

For example, risks that evolve from reliability analyses that affect overall mission objectives should be managed in the Contractor’s risk database when not eliminated or mitigated to noncredible likelihood levels.

2.7 Mission Assurance Implementation Plan (MAIP)

GSMAR-217: The Contractor shall develop, deliver, and implement a Mission Assurance Implementation Plan (MAIP) in accordance with CDRL MA-01.

GSMAR-218: The MAIP shall cover all ground system hardware and software that is designed, built, or provided by the Contractor and its subcontractors or furnished by the Government, from contract initiation through operational deployment, maintenance, and final decommissioning/disposal.

GSMAR-219: The MAIP shall include quality assurance surveillance processes and activities to allow for the systematic monitoring and evaluation of the performance of contracted services, products, or processes to ensure compliance with specified quality standards as well as contract and MAR requirements.

NOTE: The Quality Surveillance activities should be dynamic, allowing for adjustments based on performance trends, changes in requirements, or emerging issues. Regular reviews and updates of surveillance priorities should be conducted with the Government and the Contractor to maintain its relevance and effectiveness throughout the contract period.

GSMAR-220: The Contractor shall submit and maintain a MAR compliance matrix with the MAIP that identifies how the contractor meets all MAR requirements. This document should be updated/amended per new requirements and to include how sub-tier suppliers meet applicable requirements.

Check the SWGS CM tool Server at https://ipdtdms.gsfc.nasa.gov/frontmenu_dsp.cfm to verify that this is the correct version prior to use.

3 QUALITY MANAGEMENT SYSTEM

GSMAR-300: The Contractor shall have a documented Quality Management System that meets the intent of SAE AS9100 Quality Management Systems - Requirements for Aviation, Space, and Defense Organizations, or ISO 9001 Quality Management Systems Requirements.

3.1 Supplemental Quality Management System Requirements

3.1.1 Control of Nonconforming Product

GSMAR-301: The Contractor shall have a documented closed loop system for identifying, reporting, and correcting product nonconformances. The contractor shall apply a documented process for identifying, reporting, and dispositioning product nonconformances and major anomalies (i.e., Material Review Board (MRB), Anomaly Review Board (ARB), or equivalent function), which are those that have resulted in hardware or software test failures and damage or potential damage to hardware.

GSMAR-302: The Contractor shall ensure that the adequacy of corrective action is determined by audit, test, analysis, or inspection that objective evidence and artifacts are collected, and that preventive action is implemented to preclude recurrence. A non-conformance is defined as an observed condition of an item or material or software in which one or more characteristics do not conform to drawings or specifications. It includes failures, problems, malfunctions, discrepancies, deficiencies, and defects.

3.1.2 Material Review Board

GSMAR-3000: The Contractor shall establish, document, and facilitate an MRB to disposition nonconformances that have a direct effect on system availability, cybersecurity, or the ability to have full two-way communication with a spacecraft.

GSMAR-3001: The MRB shall use the following disposition actions:

• Scrap — the product is not usable

• Re-work — the product will be re-worked to conform to requirements

• Replace — the product will be returned to the supplier for replacement

• Repair — the product will be repaired using a repair process approved by the MRB

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

GSMAR-3002: The Contractor shall appoint an MRB chairperson who is responsible for facilitating the MRB process and functions.

GSMAR-3003: For non-commercial buys, the MRB process shall include a government representative as a voting member on MRB actions involving major nonconformances. For commercial buys, a procurement that does not include government design requirements, but involves only end-item requirements, the Government will be a participating member, but may or may not be a voting member depending on the government role as specified by the contract.

GSMAR-3004: The Contractor shall provide the Government with notice and applicable documentation 24 hours in advance of scheduled MRB meetings.

GSMAR-3005: The Contractor shall provide the Government with a written determination/MRB recommendation as matter of record.

GSMAR-3006: The Contractor shall ensure the MRB close-out includes verifiable objective evidence of the effective corrective action.

GSMAR-3007: The Contractor shall complete all MRB activities on a unit or module that is critical to the performance of the affected system, including failure mode, RCA, and recommended corrective actions, within 30 days.

Check the SWGS CM tool Server at https://ipdtdms.gsfc.nasa.gov/frontmenu_dsp.cfm to verify that this is the correct version prior to use.

4 SYSTEM SAFETY

GSMAR-400: The Contractor shall document and implement a System Safety Program (CDRL MA-03) in accordance with the following documents:

• NPR 8715.1B, NASA Safety and Health Programs

• NAO 209-1, NOAA Occupational Safety and Health

• GPR 1700.1, Occupational Safety Program at Goddard Space Flight Center

The system safety program should describe 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.

GSMAR-401: The Contractor shall implement the most stringent safety requirement in the event there are conflicting requirements.

4.1 Safety Deliverables

4.1.1 Hazard Analysis

GSMAR-4000: The Contractor shall perform and document a Preliminary Hazard Analysis (PHA) (CDRL MA-05) to obtain an initial risk assessment and to identify safety critical areas of a concept or system. The developer will base the PHA on the best available data, including mishap data from similar systems and other lessons learned. The purpose of this task is to perform and document a PHA to identify hazards, to provide an initial assessment of the identified hazards including software, and to recommend hazard controls and follow-on actions.

NOTE: If the TO is performing work/augmenting an existing operational system, the contractor will perform a delta Hazard Analysis to identify any new hazards as well as recommend any new hazard controls or other actions. The contractor will also ensure that any upgrades or system augmentation will not mitigate existing safety controls.

GSMAR-4001: In the PHA (CDRL MA-05), the Contractor shall identify hazards associated with the proposed system augmentation throughout the lifecycle including design, operation, service, and maintenance. The PHA process includes the timing and sequence of tasks with respect to the equipment/hardware/software design, human engineering provisions, assembly, test, and operating procedures, and the facility environments for each specific operation being performed.

GSMAR-4002: In the PHA (CDRL MA-05), the Contractor shall evaluate hazards associated with the system augmentation for hazard severity, hazard probability, and constraints based on the best available data, including mishap data from similar systems and other lessons learned.

GSMAR-4003: In the PHA (CDRL MA-05), the Contractor shall include safety provisions, alternatives, controls, and methods of verification needed to eliminate hazards or reduce their associated risk to an acceptable level. The Lead Mission Systems Engineer and the NASA CSO determine the acceptable level.

GSMAR-4004: The Contractor shall document the controls and methods of verification for each hazard listed in the PHA [CDRL MA-05].

GSMAR-4005: The Contractor shall submit the PHA [CDRL MA-05] at preliminary design review (PDR) and update and resubmit at each design milestone for the project.

Check the SWGS CM tool Server at https://ipdtdms.gsfc.nasa.gov/frontmenu_dsp.cfm to verify that this is the correct version prior to use.

4.1.2 Software Safety Analysis

GSMAR-4006: The Contractor shall perform a Software Safety Analysis per NPR 7150.2D, NASA Software Engineering Requirements, to identify hazards caused by software as a part of the nominal hazard analysis process; their controls will be verified prior to acceptance per NASA-STD-8739.8B, NASA Software Assurance and Software Safety Standard.

GSMAR-4007: The Contractor shall incorporate the results from the Software Safety Analysis, including references to the associated software requirements, into hazard reports and deliver as part of the Preliminary Hazard Analyses (CDRL MA-05).

4.1.3 Verification Tracking Log

GSMAR-4008: The Contractor shall document and implement a closed loop process for tracking all hazards to acceptable closure through the use of a Verification Tracking Log (VTL).

GSMAR-4009: 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.

GSMAR-4010: 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.

GSMAR-4011: The Contractor shall make the results of tests, analyses, and inspections available for Government review.

GSMAR-4012: The Contractor shall provide regular electronic updates of the VTL until all hazard controls are verified as closed, as agreed by the Government.

GSMAR-4013: Individual closures shall be complete and documented in the VTL prior to first operational use.

4.1.4 Safety Non-Compliance/Waiver Requests

GSMAR-402: When a specific safety requirement cannot be met, the Contractor shall submit an associated safety noncompliance/waiver request that identifies the hazard and shows rationale for waiver approval.

GSMAR-403: The Contractor shall deliver Safety Noncompliance/Waiver Requests in accordance with the project’s waiver process.

4.1.5 Mishap Reporting and Investigation

GSMAR-404: The Contractor shall incorporate a Pre-Mishap Plan into the contractor’s System Safety Program [CDRL MA-03] that describes appropriate mishap and close call notification, reporting, recording, and investigation procedures in accordance with:

a. DAO 209-3, DOC Injury, Illness, Accident, and Fatality Investigation and Reporting

b. NPR 8621.1D, NASA Procedural Requirements for Mishap and Close Call Reporting, Investigating, and Recordkeeping

GSMAR-405: The Contractor shall notify the Government within the notification period for the mishap type, as listed below:

a. For NASA Type A or Type B Mishap and high visibility close calls: notification within 1 hour

b. For NASA Type C or Type D Mishap and close calls: notification within 24 hours

GSMAR-406: The Contractor shall report accidents, test failures, or other mishaps and close calls promptly to the Government.

GSMAR-407: The Contractor shall promptly investigate to determine the root cause.

Check the SWGS CM tool Server at https://ipdtdms.gsfc.nasa.gov/frontmenu_dsp.cfm to verify that this is the correct version prior to use.

NOTE: If the incident is a NASA reportable close call/mishap, the following requirements apply:

GSMAR-408: The Contractor shall submit an initial report in NASA’s Mishap Information System (NMIS) within 24 hours of occurrence.

GSMAR-409: The Contractor shall include a Description, Time and date of the occurrence, list of injuries to personnel or damage to hardware, and points of contact if further information is needed as a part of each notification.

GSMAR-410: The Contractor shall update the NMIS report with the investigation findings, causal factors, and corrective actions.

GSMAR-411: The Contractor shall document close call investigations directly in NMIS unless otherwise directed.

Check the SWGS CM tool Server at https://ipdtdms.gsfc.nasa.gov/frontmenu_dsp.cfm to verify that this is the correct version prior to use.

5 RELIABILITY, MAINTAINABILITY, AND AVAILABILITY (RMA)

5.1 RMA Program

GSMAR-5000: The Contractor shall develop and implement an RMA Program Plan (CDRL MA-09) using both qualitative and quantitative techniques to support decisions regarding mission success and safety throughout the stages of project life cycle. This includes updating analysis with actual RMA statistics to cover any changes in configuration, hardware, or software (as appropriate).

GSMAR-5001: The Contractor shall ensure that equipment vendors, subcontractors, and suppliers provide data (e.g., MTBF, MTTR, design life) to the Contractor for execution of the RMA Plan (CDRL MA-09).

GSMAR-5002: The Contractor shall verify and assure that software, equipment, and components obtained from subcontractors, suppliers, and COTS/GOTS providers meet allocated reliability, maintainability, and availability requirements.

GSMAR-5003: The RMA Program Plan shall document the plan to perform the analyses specified in the remainder of this section in order to evaluate safety and mission risks and if additional reliability analysis techniques will be used to supplement these.

GSMAR-5004: The Contractor shall track the operational availability metrics as cumulative downtime metrics on a monthly and annual basis.

GSMAR-5005: The Contractor shall perform maintainability evaluation and demonstration tests to verify that all preventive and corrective maintenance activities, such as system and data level backups, can be successfully executed. These demonstrations should be performed in the operational environment (as available) or an environment that duplicates the operational environment as closely as possible.

5.2 RMA Analyses

GSMAR-5006: The Contractor shall prepare and maintain a Trend Analysis Report (CDRL MA-18), as deemed necessary by the Chief Safety and Mission Assurance Officer (CSO) and the Mission Systems Engineer (MSE). The list of subsystem and components to be assessed, parameters to monitor, and trend analysis reported are to be defined in the Trend Analysis Report (CDRL MA-18).

GSMAR-5007: The Contractor shall document and report the analysis of test information, trend data, and failure investigations with respect to reliability and maintainability, and report the results in the Trend Analysis Report (CDRL MA-18).

GSMAR-5008: The Contractor shall complete a reliability analysis, such as Failure Modes, Effects, and Criticality Analysis (FMECA) and Critical Items List (CIL) to identify and evaluate risks (i.e. having a potential for injury or illness, loss of life, damage, or unexpected loss of equipment, as well as those affecting the ability to reliably meet mission objectives (e.g., due to equipment failure)) that may impact inherent or operational availability or system safety. This analysis should also identify failure or fault conditions that would result in either a loss of service or impact to mission success that should be alerted with an audible alarm and/or remote signaling to initiate corrective action. The output of this effort shall identify all single-point failures and be captured in the FMECA (CDRL MA-08).

GSMAR-5009: The Contractor shall perform reliability analyses concurrent with design so that identified problem areas are addressed, and corrective action taken in a timely manner.

GSMAR-5010: The Contractor shall complete, maintain, and deliver to the Government, the reliability and ground-system availability calculations to identify design weaknesses, support design trades, and demonstrate impact of critical items. The results of this effort will be captured in the RMA Predictions Report (CDRL MA-10).

Check the SWGS CM tool Server at https://ipdtdms.gsfc.nasa.gov/frontmenu_dsp.cfm to verify that this is the correct version prior to use.

5.3 Spare Parts and Limited Life Items

GSMAR-5012: As part of the RMA Predictions Report (CDRL MA-10), the contractor shall provide a top-down breakdown to the Line Replaceable Units (LRU) level and shall define the LRU sparing required to achieve the required operational availability. This review should consider the quantities and availabilities (i.e., MTTFs and MTTRs) of LRUs, as well as logistics-related times such as replenishment times and processing times.

GSMAR-5013: The Contractor shall provide a sparing plan in accordance with CDRL TO-08 for contractor-procured and developed hardware and software, and/or as deemed necessary by the CSO and

MSE.

GSMAR-5014: The Contractor shall ensure that spares manufacturing and repair processes meet the same quality and reliability standards as in the manufacturing of original hardware.

GSMAR-5015: The Contractor shall conduct appropriate regression or re-verification testing if a mission critical item is removed for reasons of failure and is then repaired and re-designated as a spare.

SWGS MAR SWGS-SMA-REQ-0002, Revision - Effective Date: February 26, 2025

Check the SWGS CM tool Server at https://ipdtdms.gsfc.nasa.gov/frontmenu_dsp.cfm to verify that this is the correct version prior to use.

6 SOFTWARE ASSURANCE

6.1 General

GSMAR-600: The Contractor shall comply with the following requirements and standards for software, databases, and firmware, hereafter collectively referred to as software:

• NPR 7150.2D, NASA Software Engineering Requirements (or most current version)

• NASA-STD-8739.8B, NASA Software Assurance and Software Safety Standard (or most current version)

GSMAR-601: 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 the Government, software developed for the Government, software maintained by or for the Government, 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.

GSMAR-602: The Contractor shall document and implement a Software Assurance Plan (CDRL MA-17) compliant to NASA-STD-8739.8B, NASA Software Assurance and Software Safety Standard . 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 NASA-STD-8739.8B for each category of software (new, reused, Off-the-shelf, auto-generated code, etc..).

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.

GSMAR-603: The Contractor shall ensure the independence of software assurance from software engineering.

GSMAR-6000: Consistent with the general requirement for support of government surveillance (see Section 3.1 "Surveillance"), the Contractor shall provide on-demand 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

Check the SWGS CM tool Server at https://ipdtdms.gsfc.nasa.gov/frontmenu_dsp.cfm to verify that this is the correct version prior to use.

GSMAR -6001: The Contractor shall utilize its discrepancy reporting (DR) system to provide software problem reporting, corrective action reporting and tracking, that addresses reporting, analyzing, and correction of software nonconformance and software test failures throughout project lifecycle, starting at Preliminary Design Review (PDR) or at the equivalent milestone as defined in the contract.

GSMAR-6002: The Contractor shall establish a corrective action process that track software nonconformances to its final disposition.

6.2 Verification and Validation

GSMAR-6003: The Contractor shall document and implement a process for monitoring, inspecting, evaluating, and auditing the Validation & Verification activities for the project.

GSMAR-6005: The Contractor shall ensure that all defects and non-conformances are documented in its DR system.

Check the SWGS CM tool Server at https://ipdtdms.gsfc.nasa.gov/frontmenu_dsp.cfm to verify that this is the correct version prior to use.

7 WORKMANSHIP STANDARDS

GSMAR-700: The Contractor shall plan and implement a Workmanship Program for mission critical hardware to assure that workmanship, electronic packaging technologies, and process activities are selected and applied to meet the quality and reliability requirements in this document.

GSMAR-7000: The Contractor shall ensure that hardware pulled for repair or replacement are evaluated against the workmanship requirements below, where possible.

• Latest revision of ANSI/IPC-J-STD-001 Requirements for Soldered Electrical and Electronic Assemblies (Class 2)

• Latest revision of IPC/WHMA-A-620 (Class 2)

• IPC-A-640 Acceptance Requirements for Optical Fiber, Optical Cable, and Hybrid Wiring Harness

Assemblies (Class 2)

• Latest revision of IPC-610 Acceptability of Electronic Assemblies (Class 2)

GSMAR-7001: If the Contractor is required to purchase or manufacture custom-built hardware or cabling, the Contractor shall use the applicable workmanship standards listed below.

• Latest revision of ANSI/IPC-J-STD-001 Requirements for Soldered Electrical and Electronic Assemblies (Class 2)

• Latest revision of IPC/WHMA-A-620 (Class 2)

• IPC-A-640 Acceptance Requirements for Optical Fiber, Optical Cable, and Hybrid Wiring Harness

Assemblies (Class 2)

• Latest revision of IPC-610 Acceptability of Electronic Assemblies (Class 2)

NOTE: The Contractor may propose the use of similar, but not identical, workmanship standards, procedures, and training, contingent upon Contracting Officer’s Representative (COR) approval.

7.1 Training and Certification

GSMAR-7002: The Contractor personnel working on the project mission critical hardware or antenna weldment structures hardware shall maintain certification of successful training appropriate to their involvement.

GSMAR-7003: The Contractor shall verify that certification includes successful completion of formal training and demonstrated performance in the appropriate discipline as defined in the Contractor’s applicable requirements.

7.2 Documentation

GSMAR-7004: The Contractor shall document the procedures and processes that will be used to implement the referenced workmanship and design.

7.3 Acceptance Testing

GSMAR-7005: The Contractor shall verify and document the readiness for test, including test plan, test procedures, test equipment, and test facility, in accordance with the Contractor's approved Quality Management System (QMS). This also includes ensuring that reviews for correctness and completeness are accomplished, of all L3 - L6 test procedures. This is all accomplished prior to commencing any formal test event.

Check the SWGS CM tool Server at https://ipdtdms.gsfc.nasa.gov/frontmenu_dsp.cfm to verify that this is the correct version prior to use.

GSMAR-7006: During the Site Acceptance Test (SAT) of any system with safety features, the Contractor shall conduct thorough testing, in a methodical and/or clear manner of all system safety features to demonstrate they function as required/designed.

GSMAR-7007: Each system safety feature shall be tested and verified independently, not simultaneously with other safety features.

GSMAR-7008: The Contractor shall document results from all tests related to all the system safety features, if any, in an official test data record.

GSMAR-7009: SAT safety feature tests shall be conducted with the Chief Safety and Mission Assurance Officer (CSO) or safety designee witnessing the tests. Other Government observers may be required to witness the tests of the system’s safety features, based on the system being accepted/tested.

7.4 Handling, Packaging, Transportation, and Storage

GSMAR-701: The Contractor shall document and implement a program that establishes the handling, packaging, transporting, and storage procedures for parts, materials, components, and equipment in accordance with NPR 6000.1, NASA Requirements for Packaging, Handling, and Transportation for Aeronautical and Space Systems, Equipment, and Associated Components.

7.5 Electrostatic Discharge (ESD) Control

GSMAR-702: The Contractor shall prepare and implement an electrostatic discharge (ESD) control plan, unless deemed otherwise by the SWGS CSO or MSE, that conforms to the requirements of ANSI/ESD S20.20, "Protection of Electrical and Electronic Parts, Assemblies and Equipment (Excluding Electrically Initiated Explosive Devices)" (CDRL MA-07).

NOTE: If Contractor already has an existing plan that conforms to the requirements of ANSI/ESD S20.20, and it is applicable to the project, they may make this Available For Review to the government in lieu of the CDRL.

Check the SWGS CM tool Server at https://ipdtdms.gsfc.nasa.gov/frontmenu_dsp.cfm to verify that this is the correct version prior to use.

8 CALIBRATION

GSMAR-800: Metrology and Calibration services shall be established, implemented, and monitored in accordance with NASA-STD-8739.12, Metrology and Calibration.

NOTE: Only Measuring and Test Equipment used to take measurements that have documented requirements for accuracy and traceability, or that are specifically referenced for measurement accuracy or calibration from another document, such as a safety program plan, are subject to calibration requirements.

Check the SWGS CM tool Server at https://ipdtdms.gsfc.nasa.gov/frontmenu_dsp.cfm to verify that this is the correct version prior to use.

9 GIDEP ALERTS AND PROBLEM ADVISORIES

GSMAR-900: The Contractor shall support the evaluation and disposition GIDEP ALERTS, GIDEP SAFE-ALERTS, GIDEP Problem Advisories, GIDEP Agency Action Notices, and NASA Advisories to determine if they affect the contractors’ products produced for GSFC Code 450 in accordance with the following applicable documents: S0300-BT-PRO-010, GIDEP Operations Manual, and S0300-BU-GYD- 010 Government Industry Data Exchange Program Requirements Guide.

Check the SWGS CM tool Server at https://ipdtdms.gsfc.nasa.gov/frontmenu_dsp.cfm to verify that this is the correct version prior to use.

APPENDIX A REQUIREMENT APPLICABILITY MATRIX

4-Digit Requirement Applicability

4-Digit Requirement

Antenna Services (AS)

Mission Operations Services (MOS) Product

Services (PS) TO-01 SOL-A Reuse

TO-03

SOL-A GSaaS

3 QUALITY MANAGEMENT SYSTEM

3.1.2 Material Review Board

GSMAR-3000 x x x GSMAR-3001 x x x GSMAR-3002 x x x GSMAR-3003 x x x GSMAR-3004 x x x GSMAR-3005 x x x GSMAR-3006 x x x GSMAR-3007 x x x

4 SYSTEM SAFETY

4.1 Safety Deliverables

GSMAR-4000 x x x GSMAR-4001 x x x GSMAR-4002 x x x GSMAR-4003 x x x GSMAR-4004 x x x GSMAR-4005 x x x GSMAR-4006 x x x GSMAR-4007 x x x GSMAR-4008 x x x GSMAR-4009 x x x GSMAR-4010 x x x GSMAR-4011 x x x GSMAR-4012 x x x GSMAR-4013 x x x

5 RMA

5.1 RMA Program

GSMAR-5000 x x x GSMAR-5001 x x x GSMAR-5002 x x x GSMAR-5003 x x x GSMAR-5004 x x x GSMAR-5005 x x x

Check the SWGS CM tool Server at https://ipdtdms.gsfc.nasa.gov/frontmenu_dsp.cfm to verify that this is the correct version prior to use.

4-Digit Requirement

Antenna Services (AS)

Mission Operations Services (MOS) Product

Services (PS) TO-01 SOL-A Reuse

TO-03

SOL-A GSaaS

5.2 RMA Analyses

GSMAR-5006 x x x x GSMAR-5007 x x x x GSMAR-5008 x x x GSMAR-5009 x x x GSMAR-5010 x x x

5.3 Spare Parts and Limited Life Items

GSMAR-5012 x x GSMAR-5013 x x GSMAR-5014 x x GSMAR-5015 x x

6 SOFTWARE ASSURANCE

6.1 General

GSMAR-6000 x x x GSMAR-6001 x x x GSMAR-6002 x x x

6.2 Verification and Validation

GSMAR-6003 x x x GSMAR-6005 x x x

7 WORKMANSHIP STANDARDS

GSMAR-7000 x x GSMAR-7001 x x

7.1 Training and Certification

GSMAR-7002 x x GSMAR-7003 x x

7.2 Documentation

GSMAR-7004 x x

7.3 Acceptance Testing

GSMAR-7005 x x GSMAR-7006 x x GSMAR-7007 x x GSMAR-7008 x x GSMAR-7009 x x

Check the SWGS CM tool Server at https://ipdtdms.gsfc.nasa.gov/frontmenu_dsp.cfm to verify that this is the correct version prior to use.

APPENDIX B ACRONYMS AND GLOSSARY

Abbreviation / Acronym Definition ANSI American National Standards Institute ASQC American Society for Quality Control COTS Commercial Off The Shelf CDR Critical Design Review CDRL Contract Data Requirements List ESD Electrostatic Discharge FRB Failure Review Board FMEA Failure Modes and Effects Analysis FMECA Failure Mode, Effects, and Criticality Analysis FTA Fault Tree Analysis GIA Government Inspection Agency GIDEP Government Industry Data Exchange Program GOES Geostationary Operational Environmental Satellite GOTS Government Off The Shelf GSP Ground Segment Project GSFC Goddard Space Flight Center IAC Independent Assurance Contractor IPC Association Connecting Electronics Industries ISO International Standards Organization LRU Line Replaceable Unit MAIP Mission Assurance Implementation Plan MAR Mission Assurance Requirements MIL Military MOTS Modified Off-the-Shelf MRB Material Review Board MTBF Mean Time Between Failures MTTR Mean Time To Repair NASA National Aeronautics and Space Administration NOAA National Oceanographic and Atmospheric Administration OHA Operations Hazard Analysis PDR Preliminary Design Review PHA Preliminary Hazard Analysis POC Point Of Contact PSM Project Safety Manager PVM Performance Verification Matrix PWS Performance Work Statement

Check the SWGS CM tool Server at https://ipdtdms.gsfc.nasa.gov/frontmenu_dsp.cfm to verify that this is the correct version prior to use.

Abbreviation / Acronym Definition QMS Quality Management System RCA Root Cause Analysis RCCA Root Cause Corrective Action RMA Reliability, Maintainability, & Availability SAT Site Acceptance Test SMA Safety and Mission Assurance SOW Statement of Work SQA Software Quality Assurance STD Standard SWGS Space Weather Ground Services SWO Space Weather Observations SWOPD SWO Programs Division