20250227 SWGS GSMAR.pdf

Effective Date: February 26, 2025

Expiration Date: February 26, 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 -

Space Weather Ground Services (SWGS), Code 2.0

Space Weather Ground Se vices (SWGS)

Ground Services Mis on Ass rance

Requirements (GSMAR)

GSFC SWGS CMO

02/27/2025

Released

Reviewed – Not b t to Export Control

DRAFT

SWGS MAR SWGS-SMA-REQ-0002, Revision -ii

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.

Space Weather Ground Services (SWGS)

Ground Services Mission Assurance Requirements (GSMAR)

Signature/Approval Page

Prepared by:

Aaron Bush

Reviewed by:

Ken Jensen

Katherine Spotz

Eric Tai

Scott Schnee

Susan Jacobs

Ava Afghahi

Laura Dunlap

David Donovan

David Nguyen

Approved by:

Jill Taylor 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 wit Class I and

Class II change control requirements as described in the SWGS Configurati 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 D te)

Revision - 02/26/2025 Baseline Release following the approval of SWG CCR-0015 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 (MAI

3 QUALITY MANAGEMENT SYSTEM

3.1 Supplemental Quality Management System Requirem t

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 Tra king Log

4.1.4 Safety Non mpl e/Waiver R ests

4.1.5 Mishap R porting an vestigation

5 RELIABILIT MAINTAINA LITY, AND A ILABILITY (RMA)

5.1 RMA gram

5.2 Trend An sis

5.3 Analysis of ign

5.4 Spare Parts and mited Life Items

5 Procurem s

5.6 Non-An na Procur nts

6 SOFTWARE A URANCE

6.1 General

6.2 Verification a Validation

WORKMANSHIP TANDARDS

Training an ertification

7.2 ocumen ion

7.3 A p ce Testing

7.4 Han ng, Packaging, Transportation, and Storage

7.5 Electrostatic Discharge (ESD) Control

8 CALIBRATION

9 GIDEP ALERTS AND PROBLEM ADVISORIES

vii

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

APPENDIX B ACRONYMS AND GLOSSARY

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 re ements and associated capabilities that support a mission, complementing the Flight and Launch S ments. Within

Space Weather Observations (SWO), Space Weather Ground Services (SWGS) exists t ovide the ground services that satisfy Ground Segment (GS) requirements of each SWO project. D ing on the project scope, the GS requirements may span antenna services, mission operations ser s ( rol center), and product services. The SWO Programs Division follows the NPR 7120.5 guid es for tec al authority, supported by NASA’s Safety and Mission Assurance (SMA) organization which provide propriate mission assurance expertise. A Ground Services Chief Safety and Mis n Assurance Officer O) will be designated.

SWGS will seek to satisfy SWO project requirements through use of NOAA enterprise infrastructu and common services, the use of partner-provided services the developme f new capabilities. New capability development may be through contracts with in ry. This SW S GS Mission Assurance

Requirements (MAR) document contains the full set of require ts tha uld be applied to any SWGS development contract to define the SMA activities that a SWGS C r is required to perform to assure the integrity and safety of work performed. GSMAR Sections 2.0 - ontain the SMA requirements to be applied to contracted activities.

The MAR address SMA in the following area

• Quality Management

• System Safety

• Reliability, Maintainability & Availability (RM

• Software Assurance

• Workmanship Stand s

• Calibration

• GIDEP (Gove ment-Industry Da Exchange Progra

1.2 Requireme dentif tion and App ion

The requirements use th ntification convention GSMAR - ### or GSMAR - ####, with sequential numb d on the SMA cipline MAR Section number. Three-digit requirements are applicable to all act effort ile four-di equirements are allowed to be tailored by SWGS as appropriate for the

WO project or ract. Ther a 4-digit Requirement Applicability Matrix in Appendix A of this document.

Tailoring may include s or the determination that a requirement does not apply to a contracted effort.

WGS will use this GS AR, with tailoring, to generate a Contract MAR document that will become part o ch procurement p age to specify the requirements applicable to that contracted effort. The following two uirements dir the usage of three-digit and four-digit requirements in this GSMAR document:

GSMAR 0: U ess specifically stated otherwise, requirements GSMAR-(100-999) shall apply to each contract.

GSMAR-101: Requirements GSMAR-(1000-9999) in this GSMAR document shall be directed in specific contracted 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.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 requiremen

• Are/Is - Denotes descriptive material

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

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

• (CDRL MA - ##) - Refers to Mission Assurance items in th ontract Data Requirements List (CDR

• Government personnel - Anyone designated by Projec anager to act on half of the Government

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

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

• Critical - A condition that may cause se e injury upational illnes major property damage to facilities, systems, or ground hardware

• Safety-Critical - A term describing any con on, even perati ess, equipment, or system that could cause or lead to severe injury, major da ge, o mission failure if performed or built improperly or allowed to remain un d (Source NPR 7 .3)

• Safety-Critical Sof re - S are is classi d as safety-critical if it meets at least one of the following criteria o Causes or ntributes to a sy m hazardous co tion/event o Provid ntrol or mitigat for a system haza ous condition/event o Controls s y-critical o Mitigates dam e if azardous condition/event occurs o Detects, reports 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 th are designed, built, or provided by the Contractor and its subcontractors for satellite communicat command and control, health and safety monitoring, and data processing/distribution. This prog should cover all applicable phases of the project lifecycle from project initiation through nal deployment, maintenance, and final decommissioning/disposal.

2.2 SMA Management

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

GSMAR-202: The Contractor shall ensure that the SMA m ger has direct ac ss to upper management that is independent of project management and shall have t unctional free m and authority to interact with all elements of the project.

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

2.3 Flow-Down of Requirements

GSMAR-204: The Contractor shall app the system A requireme ts in this document to subcontractors and suppliers based on the wor o be perfo d re that the delivered product or service meets performance requirements. This in des fl down of any applicable 4-digit requirements contained in individual task ord rs

GSMAR-205: The Co ctor sh establish th processes for documenting, communicating, and reviewing requiremen with sub-tier ppliers to ens MAR requirements are met.

GSMAR-206: T Contractor sha ensure that qua plans, processes, procedures, hardware, and software submit by the Contrac s b tier suppliers are compliant with the requirements in this MAR, as applicable.

GSMAR-207: The C or shall provide oversight of their subcontractor’s quality control programs includi nitoring, p mance, reporting and documenting poor performance, and reviewing su ntracto rrective a n plans to remedy performance concerns/issues. The Contractor shall ovide a copy of ir Quality rance (QA) Plan (CDRL MA-01) to the government.

2.4 Suspension of Work Activities

GSMAR-208: The Co ctor shall direct the suspension of any work activity that presents an unsafe work dition to personnel mminent danger to property.

2.5 rveillan f the Contractor

GSMAR : he work activities, operations, and documentation performed by the Contractor and sub-tier contracto 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.

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-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.

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

GSMAR-214: The Contractor shall provide the Government SMA representa (s) h 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 o agreed-upon basis (no less than monthly). The reports should include:

• Quality Escapes - Any product released by an internal xternal supplier or process th is subsequently determined to be nonconforming to contract /or product specification requiremen

This could be number or open/closed RCCA investigati open/closed Di epancy Reports, etc.

• Supplier Defect Rate - The Supplier Defect Rate me es the perce ge of materials or product received from suppliers that do not meet required or compl e speci ations

• Internal Audit Results

• Software Quality Assurance Metrics

• Other Quality Metrics (as determined b he Government)

2.6 Risk Management

GSMAR-216: SMA activities should be tightly nked with th C or’s Risk Management processes.

For example, risks that evolve from reliability lyses th affect ov l mission objectives should be managed in the Contractor’s risk database when t minated or mitigated to noncredible likelihood levels.

2.7 Mission Ass ance Implem ntation Plan MAIP)

GSMAR-217: T Contractor shal evelop, deliver, an mplement a Mission Assurance Implementation

Plan (MAIP) in a rdance with

GSMAR-218: The M P sh l cover all ground system hardware and software that is designed, built, or provided by the Contrac d its subcontractors or furnished by the Government, from contract initiation thro onal deploy t maintenance, and final decommissioning/disposal.

SMAR-219: T MAIP shall lude quality assurance surveillance processes and activities to allow for the systematic moni g and eval on of the performance of contracted services, products, or processes to ensure compliance h specified quality standards as well as contract and MAR requirements.

NOTE: The Quality veillance activities should be dynamic, allowing for adjustments based on formance trends, c nges in requirements, or emerging issues. Regular reviews and updates of su llance prioritie hould be conducted with the Government and the Contractor to maintain its relev and effec ness throughout the contract period.

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

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 f dentifyin eporting, and correcting product nonconformances. The contractor shall apply a docume ted process f dentifying, reporting, and dispositioning product nonconformances and major anom lies (i.e., Material Re Board

(MRB), Anomaly Review Board (ARB), or equivalent function), w h are those that have res d in hardware or software test failures and damage or potential damag hardware.

GSMAR-302: The Contractor shall ensure that the adequac corrective acti n is determined by audit, test, analysis, or inspection that objective evidence and arti are collected that preventive action is implemented to preclude recurrence. A non-conformance is d ed as an ob ved condition of an item or material or software in which one or more characteristics do no for drawings or specifications. It includes failures, problems, malfunctions, discrepancies, deficienci d defects.

3.1.2 Material Review Board

GSMAR-3000: The Contractor shall est ish, nt and facilita n MRB to disposition nonconformances that have a direct effect on tem availa ybersecurity, or the ability to have full two-way communication with a spacecraft.

GSMAR-3001: The MRB shall use the followin ispo on actions:

• Scrap — the product is le

• Re-work — the pro t will be worked to co rm to requirements

• Replace — the p uct will be r ned to the sup er for replacement

• Repair — the oduct will be re red using a repa process approved by the MRB

• Use as-is — e product will b sed as is

GSMAR-3002: Th ontrac shall appoint a RB chairperson who is responsible for facilitating the

MRB process and func

GSM For non-c ercial buys, the MRB process shall include a government representative as ting memb MRB acti involving major nonconformances. For commercial buys, a procurement hat does not incl governme design requirements, but involves only end-item requirements, the

Government will be articipating member, but may or may not be a voting member depending on the government role as sp ied by the contract.

SMAR-3004: The C ractor shall provide the Government with notice and applicable documentation

2 ours in advance of heduled MRB meetings.

GSM 3005: Th Contractor shall provide the Government with a written determination/MRB recomm ation matter of record.

GSMAR-30 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 syste afety nagement and engineering required to identify, evaluate, and eliminate or control hazards t he hardwar ftware, and system design by reducing the associated risk to an acceptable level throughout the system lif cle.

GSMAR-401: The Contractor shall implement the most stringent s y requirement in the event th are conflicting requirements.

4.1 Safety Deliverables

4.1.1 Hazard Analysis

GSMAR-4000: The Contractor shall perform and document a Pre Hazard Analysis (PHA) (CDRL

MA-04) to obtain an initial risk assessment and to identify safety crit areas of a concept or system. The developer will base the PHA on the best avail ble data, including mish data from similar systems and other lessons learned. The purpose of this t i erform and documen PHA to identify hazards, to provide an initial assessment of the identif d hazar luding software, d to recommend hazard controls and follow-on actions.

NOTE: If the TO is performing work/augmen g an sting operati nal system, the contractor will perform a delta Hazard Analy i identify any ne az ds as well as recommend any new hazard controls or other actions. The cont r w o ensure that upgrades or system augmentation will not mitigate existing safety control

GSMAR-4001: the PHA (CDR MA-04), the Co ctor shall identify hazards associated with the proposed syste ugmentation ou h t the lifecycle including design, operation, service, and maintenance. The HA pro includes ng and sequence of tasks with respect to the equipment/hardware/s wa design, human engineering provisions, assembly, test, and operating procedures and the facil nvironments for each specific operation being performed.

G AR-400 n the PHA DRL MA-04), the Contractor shall evaluate hazards associated with the stem augmenta for hazard verity, hazard probability, and constraints based on the best available data, including mish data from s ar systems and other lessons learned.

GSMAR-4003: In the HA (CDRL MA-04), the Contractor shall include safety provisions, alternatives, ontrols, and methods verification needed to eliminate hazards or reduce their associated risk to an ptable level. The L d Mission Systems Engineer and the NASA CSO determine the acceptable level.

GSM R-4004: Th ontractor shall document the controls and methods of verification for each hazard listed i PHA DRL MA-04].

GSMAR-4 The Contractor shall submit the PHA [CDRL MA-04] 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-87 8B, NASA

Software Assurance and Software Safety Standard.

GSMAR-4007: The Contractor shall incorporate the results from the Software Safet Analysis, including references to the associated software requirements, into hazard reports and deliver f the Preliminary

Hazard Analyses (CDRL MA-04).

4.1.3 Verification Tracking Log

GSMAR-4008: The Contractor shall document and implement a ed loop process for tra g all hazards to acceptable closure through the use of a Verification Tra ng Log (VTL).

GSMAR-4009: The Contractor shall document in the VTL th ocess of verifying the control of hazar s by test, analysis, inspection, similarity to previously qua d hardware, or y combination of these activities.

GSMAR-4010: The Contractor shall ensure that verifications lis on hazard reports refer to specific test, analysis, or inspection reports with a summary of the pertinent r s.

GSMAR-4011: The Contractor shall make results of tests, analys and inspections available for

Government review.

GSMAR-4012: The Contractor shall provi regular el updates of the VTL until all hazard controls are verified as closed, as agreed by the vernment

GSMAR-4013: Individual closures shall be comp e an ocumented in the VTL prior to first operational use.

4.1.4 Safety Non-C mpliance/W ver Request

GSMAR-402: W n a specific safet equirement cann be met, the Contractor shall submit an associated safety noncomp ce/waiver requ hat identifies the h zard and shows rationale for waiver approval.

GSMAR-403: The ntracto hall deliver Sa Noncompliance/Waiver Requests in accordance with the project’s waiver pr

4 1 Reporting d Investigation

SMAR-404: T Contractor ll incorporate a Pre-Mishap Plan into the contractor’s System Safety

Program [CDRL MA ] that descr s appropriate mishap and close call notification, reporting, recording, and investigation proc res in accordance with:

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

NPR 8621.1D, NA Procedural Requirements for Mishap and Close Call Reporting, Investigating, d Recordkeepin

GSMA 405: Th ontractor shall notify the Government within the notification period for the mishap type, as l d b w:

a. For NAS 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 occur e, list of injuries to personnel or damage to hardware, and points of contact if further information is n d as a part of each notification.

GSMAR-410: The Contractor shall update the NMIS report with the investi on findings usal factors, and corrective actions.

GSMAR-411: The Contractor shall document close call investigatio directly in NMIS unless o wise 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-05) using both qualitative and quantitative techniques to support decisions regarding mission su ss and safety throughout the stages of project life cycle. This includes updating analysis with actua MA statistics to cover any changes in configuration, hardware, or software (as appropriate).

GSMAR-5001: The Contractor shall ensure that equipment vendors, subcontra s, an ppliers provide data (e.g., MTBF, MTTR, design life) to the Contractor for execution of the R A Plan (C L MA-05).

GSMAR-5002: The Contractor shall verify and assure that software, equipment, and compone btained from subcontractors, suppliers, and COTS/GOTS providers meet allo d reliability, maintainab and availability requirements.

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

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

GSMAR-5005: The Contractor shall perform intainability evaluation d demonstration tests to verify that all preventive and corrective maintenan ac such as system a data level backups, can be successfully executed. These demonstration hould b f rmed in the op ational environment (as available) or an environment that duplicates th perational en nt as closely as possible.

5.2 Trend Analysis

GSMAR-5006: The Cont all prepare an ntain a list of subsystem and components to be assessed, parameters to m nitor, an nd analysis r rted, as defined in the RMA Plan (CDRL MA-05).

GSMAR-5007: Th ontractor shal ocument and r rt the analysis of test information, trend data, and failure investigat s with respect to liability and mai inability, and report the results as defined in the

RMA Plan (CDR MA-05).

5.3 Analysis of D ign

GSMAR 5008: The Con tor shall complete a reliability analysis, such as Failure Modes, Effects, and

Cri y sis (FMEC Failure Mode and Effects Analysis (FMEA), Fault Tree Analysis (FTA)

/or a Probab ic Risk As ment (PRA) to identify and evaluate risks (i.e. having a potential for injury or illness, los f life, dama or unexpected loss of equipment, as well as those affecting the ability to reliably meet missi bjectives ( .g., due to equipment failure)) that may impact inherent or operational availability or system s y. This analysis should also identify failure or fault conditions that would result n either a loss of servi r impact to mission success that should be alerted with an audible alarm and/or ote signaling to ini e corrective action. The output of this effort will be captured in the Analysis of

De Report (CDRL MA-06).

GSMA 5009: T Contractor shall perform reliability analyses concurrent with design so that identified problem a addressed, and corrective action taken in a timely manner.

GSMAR-5010: The Contractor shall perform and maintain, and deliver to the Government, reliability and ground-system availability calculations to identify design weaknesses, support design trades, and demonstrate impact of critical items.

GSMAR-5011: The Contractor shall incorporate the results of the availability calculations into the

Analysis of Design Report (CDRL MA-06).

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.4 Spare Parts and Limited Life Items

GSMAR-5012: As part of the Analysis of Design Report (CDRL MA-06) 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 an availabilities

(i.e., MTTFs and MTTRs) of LRUs, as well as logistics-related times such as replenis ent times and processing times.

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

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

5.5 Antenna Procurements

GSMAR-5015: The Contractor shall provide the following procurements m ged under this contract:

a. Recommended sparing plan describing how sparing will ccomplish for the serviceable antenna lifetime.

b. The sparing plan should consider the quantities and availability LRUs, maintenance and logistics-related down times such as scheduled maintenance, replenishment s and processing times.

c. A critical spare list (a critical spare repr en rt required on-site t ickly restore redundancy or reduce downtime) including price, non-c ical sp d consumable i s required for equipment maintenance.

d. The critical spare list shall include the Origi Equipm Manuf r (OEM) descriptions and part number for each line item.

e. The Contractor shall i y ems that are o escence risks or may have issues due to “vanishing subcontractors”, m l upgrade c.

f. Identification o ems requiring intenance and licensing agreements required through transition to operation esponsibility.

GSMAR-5016: All res parts required to operate antennas managed under this contract shall be available for the duratio he antenna lifetime.

G AR-50 If any spar known to become obsolete due to reasons beyond the contractor’s control, e contractor sh

a. Provide a five-y warning

b. Recommend the nu er of spares required for antenna operation for the remaining antenna lifetime.

Identify all antenn ystem electro-mechanical, electronic, and electrical components that routinely must be replaced b re the 15-year serviceable life period expires.

d. P ide a form otification process to the Government for notification of End of Life and End of

Sup notif tions as part of the proposal.

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.6 Non-Antenna Procurements

GSMAR-5018: The Contractor shall provide the following for hardware managed under this contract:

a. Recommended sparing plan describing how sparing will be accomplished for the expected mission life of the system.

b. The sparing plan should consider the quantities and availability of LRUs, mainten e and logistics-related down times such as scheduled maintenance, replenishment times and pro sing times.

c. A critical spare list (a critical spare represents a part required on-site to quic re redundancy or reduce downtime) including price, non-critical spares, and consumable i s requir r equipment maintenance.

d. The critical spare list shall include the Original Equipment Manuf rer (OEM) description d part number for each line item.

e. The Contractor shall identify all items that are obsolescence ks or may have issues due to “vanish subcontractors”, model upgrades, etc.

f. Identification of items requiring maintenance and or lic g agreeme equired through transition to operational responsibility.

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 versi

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

GSMAR-601: The Contractor shall establish a software assurance program consisting of nned and systematic set of activities and disciplines that ensures that software conf ms to organizational a roject-specific requirements and standards throughout the project lifecycle ere software is defined as:

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

• All or a part of the programs, procedures, rules, an sociated docum tation 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 process of digital information

• Part of a product that is the computer program or the set of comput ograms

NOTE: The software definition applies to s ware loped by the Gover nt, software developed for the Government, software maintained by or r the Go nt COTS, G S, MOTS, OSS, reused software components, auto-generated code, bedded so ftware used on ground support equipment, the software executed on processors e edded i ogramm logic devices, legacy, heritage, applications, freeware, shareware, trial or demons ion ftware, and open-source software components.

GSMAR-602: The Con ctor shal cument and i lement a Software Assurance Plan (CDRL MA-07) compliant to NASA D-8739.8B, N SA Software surance and Software Safety Standard (DID SW-

1). The plan inclu s the software surance proces procedures, tools, and techniques to be used commensurate w the software cl fication and safety iticality assessment, with additional tailoring in accordance with g ance provi D 8739.8B for each category of software (new, reused, Off-the-shelf, auto-g rated e, etc..).

The plan ddresses both ware Assurance and Software Safety disciplines. This includes the necessary col h relevant MA and Engineering stakeholders (i.e., system safety, system reliability, dware quality stem secu and software engineering), and the process by which traceability is established to their ective ana s and/or requirements.

GSMAR-603: The tractor shall ensure the independence of software assurance from software ngineering.

GS R-6000: Con ent with the general requirement for support of government surveillance (see

Sectio 1 "Surve nce"), the Contractor shall provide on-demand access to following:

• Softw lem reports

• Software ocumentation (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 th rack software nonconformances to its final disposition.

6.2 Verification and Validation

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

GSMAR-6004: The Contractor shall ensure that the Contractor alidation and Verification acti s are in accordance with the Contractor's Capability Maturity Mo Integration (CMMI) processes.

GSMAR-6005: The Contractor shall ensure that all defects d non-confor nces 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 repla ent are evaluated against the workmanship requirements below, where possible.

• Latest revision of ANSI/IPC-J-STD-001 Requirements for Soldered ectrica d Electronic

Assemblies (Class 2)

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

• IPC-A-640 Acceptance Requirements for Optical Fiber, Optical ble, and Hybrid Wiring ness

Assemblies (Class 2)

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

GSMAR-7001: If the Contractor is required to purchase or ufacture cust built hardware or cabling, the Contractor shall use the applicable workmanship standards ed below

• Latest revision of ANSI/IPC-J-STD-001 Requirements fo ered Electrical and Electronic

Assemblies (Class 2)

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

• IPC-A-640 Acceptance Requirements f Opt Fiber, Optical Cabl d Hybrid Wiring Harness

Assemblies (Class 2)

• Latest revision of IPC-610 Acceptability of ectronic As (Class 2)

NOTE: The Contractor may propose the use sim , but not identical, workmanship standards, procedures, and training, co upon Contract fficer’s Representative (COR) approval.

7.1 Training an ertification

GSMAR-7002: he Contractor pe nnel working on e project mission critical hardware or antenna weldment struc hardware sh i certification of successful training appropriate to their involvement.

GSMAR 7003: The Co ctor shall verify that certification includes successful completion of formal trai monstrated formance in the appropriate discipline as defined in the Contractor’s licable requi nts.

7.2 Documentati

GSMAR-7004: The ntractor shall document the procedures and processes that will be used to plement the referenc workmanship and design.

7.3 cceptance sting

GSMAR 05 he Contractor shall verify and document the readiness for test, including test plan, test procedures, 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 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 multaneously with other safety features.

GSMAR-7008: The Contractor shall document results from all tests related t he 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 Missi ssurance

Officer (CSO) or safety designee witnessing the tests. Other Govern nt observers may be r red to witness the tests of the system’s safety features, based on the system ing accepted/tested.

7.4 Handling, Packaging, Transportation, and Stor

GSMAR-701: The Contractor shall document and implem a program establishes the handling, packaging, transporting, and storage procedures for parts, m rials, mponents, and equipment in accordance with NPR 6000.1, NASA Requirements for Packag ndling, and Transportation for

Aeronautical and Space Systems, Equipment, and Associated Comp ts.

7.5 Electrostatic Discharge (ESD) C tr

GSMAR-702: The Contractor shall prepare a impleme lectrostatic di harge (ESD) control plan that conforms to the requirements of ANSI/E S20.20, "P f Electrical and Electronic Parts, Assemblies and Equipment (Excluding Electrica Initiate xplosive ices)" (CDRL MA-08).

NOTE: If Contractor alrea xisting plan t nforms to the requirements of ANSI/ESD S20.20, and it is applicable to th roject, th may make th 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 h documented requirements for accuracy and traceability, or that are specifically referenced for meas ment accuracy or calibration from another document, such as a safety program plan, are subject to ca ion 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 accor ce with the following applicable documents: S0300-BT-PRO-010, GIDEP Operations Manual, and 00-BU-GYD-

010 Government Industry Data Exchange Program Requirements Guide.