6.__Attachment_C_-_Mission_Assurance_Requirements.pdf

Check <Project Library site> to verify that this is the correct version prior to use

RFP 80GSFC17R0018

ATTACHMENT C

Revision - November 2017

Mission Assurance Requirements (MAR) for the SENSE Contract

Mission Risk Classification – Ground System

National Aeronautics and

Space Administration

Goddard Space Flight Center Greenbelt, Maryland

RFP 80GSFC17R0018 p. 2/25

EXPLORATION AND SPACE COMMUNICATIONS

PROJECTS DIVISION

Mission Assurance Requirements Signature/Approval Page

Prepared by:

Date ESC Chief Safety & Mission Assurance Officer Code 383

Reviewed by:

<Enter Name Here> Date <Enter Position Title Here> <Enter Org./Code Here>

Approved by:

Date Chief, Exploration and Space Communications Projects Division

Code 450

Concurred by:

<Enter Name Here> Date <Enter Position Title Here> <Enter Org./Code Here>

RFP 80GSFC17R0018 p. 3/25

Preface This document is an Exploration and Space Communications Projects (ESC) Division signature-controlled document. Changes to this document require prior approval by the ESC Configuration Control Board (CCB) Chairperson or designee. Changes to this document will be made by complete revision.

All of the requirements in this document assume the use of the word "shall" unless otherwise stated.

Questions or comments concerning this document should be addressed to:

ESC Configuration Management Office Mail Stop: 450 Goddard Space Flight Center Greenbelt, Maryland 20771

RFP 80GSFC17R0018 p. 4/25

Change History Log

Revision Effective Date Description of Changes

RFP 80GSFC17R0018 p. 5/25

Table of Contents

Section Title Page 1 General

1.1 System Safety and Mission Assurance Program

1.2 Management

1.3 Flowdown

1.4 Suspension of Work Activities

1.5 Contract Data Requirements List (CDRL)

1.6 Surveillance

1.7 Use of Off-the-Shelf Products

2 Quality Management System

2.1 General

2.2 Supplemental Quality Management System Requirements

2.2.1 Control of Nonconforming Product

2.2.2 Failure/Anomaly Reporting and Disposition

3 System Safety

3.1 General

3.2 System Safety Deliverables

3.2.1 System Safety Program Plan

3.3. Hazard Analyses

3.3.1 Hazard Analysis

3.4 Lifting Safety Requirements

3.5 Safety Deviation and Waivers

3.6 Mishap Reporting and Investigation

4 Reliabilty, Maintainability and Availability (RMA)

4.1 Reliability, Maintainability and Availability Program Plan

4.2 Reliabiity, Maintainability and Availability Modeling

4.2.1 Performance Data

4.2.2 Maintainability

4.3 Failure Modes Effects and Criticality Analysis (FMECA)

4.4 Fault Tree Analysis

4.5 Limited Life Analysis

5 Software Assurance

5.1 Applicable Software Definitions

5.2 Software Assurance Program

5.2.1 Software Quality

5.2.2 Software Safety Analysis

5.2.3 Software Reliability Analysis

5.2.4 Reserved

5.2.5 Software Security

5.3 Reviews

5.4 Surveillance of Software Development, Maintenance, and Assurance

Activities

6 Verification and Validation Program

RFP 80GSFC17R0018 p. 6/25

Section Title Page

6.1 General

6.2 Documentation of Results

7 Workmanship

7.1 General

7.2 Handling, Packaging, Transporting, and Storage

7.3 Electrostatic Discharge Control (ESD)

7.4 Reserved

7.5 Reserved

7.6 Tin Whisker Control Measures

8 Component, Module, and Unit Control

8.1 General

8.2 Custom or Advanced Technology Devices

8.3 Parts Used in Off-the-Shelf (COTS) Assemblies

9 RESERVED

10 RESERVED

11 Metrology and Calibration

11.1 Metrology and Calibration Program

12 RESERVED

Appx. A Acronym List Appx. B Applicable Documents Appx. D Reference Documents

RFP 80GSFC17R0018 p. 7/25

1. GENERAL

1.1 Systems Safety and Mission Assurance Program

The Contractor shall develop, deliver, and implement a Mission Assurance Implementation Plan (MAIP) in accordance with DRD SMA-01. The MAIP shall cover:

- Ground system hardware and software that is designed, built, or provided by the Contractor and its subcontractors or furnished by the government, from project initiation through operational deployment and maintenance

- All processes

- Ground system facilities

- Simulation/modeling, availability and test tools

- Antennas and associated housing

- Failure/anomly review

The Contractor shall submit a waiver request (DRD SMA-05) for the use of alternative hardware, software, processes, procedures, and standards.

1.2 Management

The Contractor shall designate a manager for the MA program and all associated assurance activities.. The assurance manager shall have 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.

The Contractor shall ensure that review processes are in place at their level to certify the safety and operational readiness of hardware/software, mission- critical support equipment, hazardous facilities/operations, and high-energy ground-based systems.

1.3 Flowdown

The Contractor shall apply the system safety and mission assurance requirements in this document to subcontractors and suppliers to the extent necessary to ensure that the delivered product or service meets performance requirements.

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

1.4 Suspension of Work Activities

RFP 80GSFC17R0018 p. 8/25

The Contractor shall direct the suspension of any work activity that presents a hazard, imminent danger, or future hazard to personnel, property, or mission operations resulting from unsafe acts or conditions that are identified by inspection, test, or analysis.

2. QUALITY MANAGEMENT SYSTEM

2.1 General

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

The Contractor shall establish and maintain software engineering management processes on the effective date of the contract that, as a minimum, adhere to the requirements of CMMI®- DEV Capability Level 3, or higher, as measured by a Software Engineering Institute (SEI), in the following Process Areas: Requirements Management, Configuration Management, Process and Product Quality Assurance, Measurement and Analysis, Project Planning, Project Monitoring and Control, and Supplier Agreement Management. An SEI authorized lead appraiser from an external organization shall register the Contractor’s software engineering management processes to CMMI®-DEV Capability Level 3, or higher, no later than 15 months after the start of Phase-in.

2.2 Supplemental Quality Management System Requirements

2.2.1 Control of Nonconforming Product

The Contractor shall have a documented closed loop system for identifying, reporting, and correcting product nonconformances. The system shall ensure that the adequacy of corrective action is determined by audit or test, that objective evidence and artifacts are collected, and that preventive action is implemented to preclude recurrence.

2.2.2 Failure/Anomaly Reporting and Disposition

The Contractor shall have a documented process for failure/anomaly reporting and disposition. The Contractor shall establish a failure/anomaly review board (F/ARB) whose membership shall include a government representative as a voting member with approval authority for proposed actions on all major anomalies. The F/ARB shall consist of the appropriate functional and project representatives needed to ensure timely determination, implementation and close out of the recommended F/ARB disposition.

RFP 80GSFC17R0018 p. 9/25

The process shall require major failures/anomalies to be submitted to the F/ARB and the government (DRD SMA-03) The Contractor shall report major hardware or software anomalies beginning with acceptance testing of the first software/hardware release delivered to the government. Major anomalies are those that have resulted in hardware or software test failures and damage or potential damage to hardware. Failures critical to performance shall be referred to the F/ARB for disposition. All anomalies shall be classified in accordance to the level of impact to the functionality of the hardware/software release.The Contractor shall document and investigate operational failures or failures during production testing to determine the root causes, identify corrective actions, and evaluate corrective action effectiveness.

The Contractor shall obtain written authorization to disposition the nonconforming product, consistent with their quality management system. The F/ARB close-out shall include verifiable objective evidence of the effective corrective action. The Contractor shall complete all failure analyses on a unit or module that is critical to the performance, including failure mode, root cause analysis and recommended corrective actions, within 30 days.

3. System Safety

3.1 SYSTEM SAFETY DELIVERABLES

3.1.1 System Safety Program Plan

The Contractor shall prepare a System Safety Program Plan (SSPP) in accordance with (DRD SMA-06) 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.

3.2 HAZARD ANALYSES

3.2.1 Hazard Analysis

The Contractor shall perform a Hazard Analyses (HA) (DRD SMA-07) for any non-software related development items to obtain a risk assessment of the Ground System. The purpose of this task is to identify safety critical areas, to provide an assessment of non-software related hazards and to identify recommended hazard controls and follow-on actions. Software related hazard analysis will be performed as per section 5.2.2 Software Safety Analysis.

In the HA, the Contractor shall evaluate hazards associated with the proposed design or function for hazard severity, hazard probability, and operational constraint based on the best available data, including mishap data from similar systems and other lessons learned. In the HA the Contractor shall include safety provisions and alternatives needed to eliminate hazards or reduce their associated risk to an acceptable level. In the event that a System Level Hazard Analysis (Spacecraft, Instrument and Ground System Hazard Analysis) is

RFP 80GSFC17R0018 p. 10/25 performed, the Contractor shall participate and provide input into that system level hazard analysis.

3.3 LIFTING SAFETY REQUIREMENTS

When lifting operations occur state and federal requirements shall be followed. When operations take place outside of the USA local standards shall be followed with the concurrence of the Government.

Any critical lifts shall be evaluated on an individual basis with concurrence of the Government.

3.4 SAFETY DEVIATION AND WAIVERS

The Contractor shall follow the deviation and waiver process established in this contract.

3.5 MISHAP REPORTING AND INVESTIGATION

The Contractor shall include a Pre-Mishap Plan in the SSPP that describes appropriate mishap and close call notification, reporting, recording, and investigation procedures per NPR 8621.1 NASA Procedures and Guidelines for Mishap Reporting, Investigating, and Recordkeeping. The plan shall identify the processes and procedures to be followed to respond to and control a mishap or a close call, as well as identify the chain of individuals to be contacted in the event a mishap or close call occurs. All accidents or other mishaps or close calls shall be promptly investigated to determine the dominant root cause and corrective actions. Reporting and documentation of mishaps/close calls to NASA GSFC shall be done as soon as possible and no later than 24 hours after occurrence.

4. Reliability, Maintainability and Availability (RMA)

4.1 Reliability, Maintainability, and Availability Program Plan

For development activities, the Contractor shall prepare and implement a Reliability, Maintainability, and Sustaining Plan (DRD SUS-01) using both qualitative and quantitative techniques to support decisions regarding mission success and safety throughout system development. This plan shall include a detailed approach to the analysis of hardware and software for their contributions to system reliability and mission success. The Contractor shall present the implementation of these plans and related activities at milestone reviews beginning with the System Requirements Review.

The Contractor shall continue Reliability, Maintainability and Availability RMA activities throughout the period of Performance in accordance with the RMA Project Plan, replacing calculated data analysis with analysis of the actual reliability and maintainability statistics of the ground systems, as well as updating analyses to cover any changes in configuration, hardware, or software. The Contractor shall implement corrective actions whenever reliability, maintainability, and availability related requirements are not satisfied. The Contractor shall allocate RMA requirements to the component level as appropriate. The Contractor shall verify that equipment and components obtained from subcontractors, suppliers, and/or COTS vendors, meet allocated requirements and document and report any deficiencies to the Government.

RFP 80GSFC17R0018 p. 11/25

4.2 Reliability, Maintainability, and Availability Modeling

The Contractor shall perform numerical reliability and availability predictions considering design redundancies and common cause failures. The Contractor shall prepare and submit a Reliability, Maintainability, and Availability Model Report (DRD SE-01) using their numerical reliability and availability predictions as substantiated by maintainability (See 4.2.2) and configuration performance data/history (See 4.2.1). The Contractor shall document assumptions and data used for each prediction as well as document any design risks discovered.

4.2.1 Performance Data

The Contractor shall substantiate availability and RMA predictions with:

1. Reliability Block Diagrams/Functional Block Diagrams (showing design concept to sufficient depth to validate redundancies assumed)

2. Failure rate source data (e.g., Telcordia SR-332 Issue 2, MIL-HDBK-217, Reliability Prediction of Electronic Equipment, with updated failure rates, (e.g., “Handbook of 217 Plus”, “MIL-HDBK-472”) from the Reliability Information Analysis Center, or equivalent and/or Test data at the 95% confidence level (with concurrence of project management)).

3. The performance of similar items (with concurrence of project management) and/or trend data.

4. Measures of Mean Time Between Failure (MTBF) and Mean Time to Repair (MTTR) for all hardware and software configurations items (CIs)

5. Measures of/Estimates of logistics downtime, administrative downtime, and preventive maintenance downtime.

6. Failover times of redundant strings/items

4.2.2 Maintainability

The Contractor shall substantiate maintainability with evaluation and demonstration with:

1. Plans for preventive and corrective maintenance activities, such as, but not limited to, system and data level backups can be successfully executed and substantiate predictions.

2. Sparing plans that take into account the quantities and failure rates of line replaceable units, as well as logistics-related times such as replenishment times and processing times.

3. Simulated or test verified maintainablity as documented in Maintainability Demonstration Reports (DRD SE-01) with the following minimum acceptable maintainability parameters for all hardware and software not predicatable or ciritcal hardware:

a. Diagnostic time to detect and isolate fault to the defective components/sub-systems/applications.

RFP 80GSFC17R0018 p. 12/25

b. Time required to carry out appropriate corrective action (e.g. replacing, integrating updates, restoring data, restoring to previous stable software version or establishing workaround procedures) to defective components/sub-systems/applications that are necessary to return the affected components/sub-systems/applications to operational status.

c. Time required to complete checkout and to restore operational status.

4.3 FAILURE MODES EFFECTS AND CRITICALITY ANALYSIS (FMECA)

The Contractor shall perform a FMECA to determine failure mode severity category 1, 1R, 1S, 2, 2R, 3 and 4 per Table 4.1 (DRD SMA-08). The Contractor shall prepare and maintain a CIL for severity categories 1, 1R, 1S, and 2 per Table 4.1 (DRD SMA-08). With the exception of cross-strapping architecture, switching components that represent potential single point failures (a single point of failure is defined as a single item thats failure takes down the entire ground system or causes the permanent loss of data), and internally redundant boxes, failure modes shall be assessed at the component interface level (i.e., Line Replaceable Unit level). The Contractor shall review I&T anomalies to verify that corrective action has been implemented. The Contractor shall analyze single point failure modes resulting in severity categories 1, 1S, or 2 to determine the root cause, corresponding mitigation actions, and retention rationale. The Contractor shall address hardware and software that is designed, built, or provided by its organization or subcontractors, and shall maintain the FMECA so mission risks can be characterized from project initiation through refurbishment and decomissioning.

Detection, repair, and preventive maintenance/refurbishment (or prevention) of each failure mode shall also have an explanation of and a quantified ranking for its effectiveness at mitigating or avoiding the failure mode effects and assist in sparing needs identification. The values range from 1 to 5, corresponding to very unlikely to very likely that the effects will be avoided or mitigated.

RFP 80GSFC17R0018 p. 13/25

Table 4-1. Severity Categories

Category Severity Description 1 Catastrophic/ Critical Catastrophic failure modes are those that may cause death or a permanent disabling injury or the destruction of a major system or facility on the ground or of the vehicle during the mission. Critical failure modes those that may cause a severe injury or occupational illness to personnel or major property damage to facilities, systems, or flight hardware.

1R Catastrophic/ Critical Failure modes of identical or equivalent redundant hardware or software elements that could result in Category 1 effects if all failed.

1S Catastrophic/ Critical Failure in a safety or hazard monitoring system that could cause the system to fail to detect a hazardous condition or fail to operate during such condition and lead to Category 1 consequences.

2 Critical Failure modes that could result in loss of one or more mission objectives as defined by the GSFC project office.

2R

Critical Failure modes of identical or equivalent redundant hardware or software that could result in Category 2 effects if all failed.

3 Significant Failure Modes that could cause degradation to mission objectives.

4 Minor Failure Modes that could result in insignificant or no loss to mission objectives.

4.4 FAULT TREE ANALYSIS

The Contractor shall perform qualitative fault tree analyses to address mission failures and degraded modes of operation (DRD SMA-09). The qualitative fault tree analyses include software contributions to loss of mission scenarios. The Contractor shall quantify the tree analysis to identify risks.

4.5 LIMITED LIFE ITEMS ANALYSIS

The Contractor shall prepare a limited life items analysis (LLA). This analysis shall evaluate all potential life limiting items of the design. Each item shall be have its expected life (known or calculated life time or cycles) and its required life (full planned usage period or useage time until refreshed or returned to new by other means) identified so that a life margin can be produced. For any items that have a life margin below 2x the Contractor shall implement a plan to identify and manage limited life items, i.e. Technology refresh/Upgrade/Equipment obsolescence plan or design change and update the LLA accordingly. Any residual items that have less than a 2x life margin shall be identified as a failure risk and incorporated in the FMECA/Fault Tree Analysis (FTA) as appropriate. (DRD

SMA-10)

RFP 80GSFC17R0018 p. 14/25

5. SOFTWARE ASSURANCE

5.1 Applicable Software Definitions

When identifying, developing, verifying, and maintaining software, the Contractor shall apply the following definitions:

- Software is defined as computer programs, procedures, scripts, rules, and associated documentation and data pertaining to the development and operation of a computer system. Software includes commercial–off-the-shelf (COTS) software, government-off-the-shelf (GOTS) software, modified-off-the-shelf (MOTS) software, custom software, reused software, heritage software, auto generated code, and code executed on microprocessors.

- Mission-Critical Software - Software that can cause, contribute to, or mitigate the loss of capabilities that are essential to the primary mission objectives or can damage flight hardware under development.

- Safety-Critical Software - Software that can cause, contribute to, or mitigate human safety hazards or damage facilities.

Note: The above definitions for Mission and Safety Critical Software are derived from the definition of safety critical software in the NASA Software Standard. The delineation is to provide clarification for organizations with separate processes for assessing pre-separation and post-separation hazards and failures. Both categories of software shall comply with the NASA-STD-8719.13C Software Safety Standard, which requires assessment of the entire lifecycle for potential injury, major damage, or mission failure.

5.2 Software Assurance Program

The Contractor shall plan and implement a Software Assurance Program that complies with the definitions in 5.1 and:

- NASA-STD-8739.8 NASA Standard for Software Assurance

- NASA-STD-8719.13C Software Safety Standard

The Contractor shall identify the person responsible for directing and managing the software assurance program and interfacing with government assurance personnel.

For development activities, the Contractor shall document the software assurance program in the Software Development Plan (SDP) (DEV-03). The plan shall address the disciplines of Software Quality, Software Safety, Software Reliability, Software Security, Software Verification and Validation (V&V), and Independent Verification and Validation (IV&V) and detail the role of assurance and their activities in ensuring quality products and processes for each discipline. The plan will include the software assurance processes, procedures, RFP 80GSFC17R0018 p. 15/25 tools, and techniques to be used commensurate with the Software Classification Assessment.

The plan will address software assurance the necessary collaboration between software assurance, system safety, system reliability, and software engineering.

5.2.1 Software Quality

The Contractor shall evaluate software processes and products as defined by NPR 7150.2 and commensurate with the software classification. The Contractor shall identify and document noncompliance issues, communicate the results of quality assurance activities, maintain records, and ensure disposition of noncompliances.

5.2.2 Software Safety Analysis

For software development activities, the Contractor shall independently identify safety critical software modules and functions per the definitions provided in Section 5.1 and provide the following supporting analysis, design and test of the software in accordance with NASA-STD-8719.13C, Software Safety Standard:

a. Review hazard analysis for the completeness and accuracy in its identifying software contributions to hazards.

b. Verify traceability and identifying safety-critical requirements is an iterative process concurrent with development of the hazard analyses.

c. Ensure that changes to safety critical software or its interfaces are evaluated for impact to existing hazard analysis and associated controls and mitigations.

d. Verify that design controls, test plans and procedures, and operational constraints for safety critical software are consistent with controls and mitigations identified in hazard analysis and verification log and do not create new hazards.

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 Hazard Analysis (DRD SMA-07).

5.2.3 Software Reliability Analysis

The Contractor shall independently identify mission critical software modules and functions per the defintions provided in section 5.1, and provide the following support to the analysis, design and test of the software in accordance with NASA-STD-8719.13C, the NASA Software Safety Standard:

a. Review reliability analysis for the completeness and accuracy in its coverage of software

b. Verify traceability between software requirements and reliability analyses

c. Ensure that changes to mission critical software or its interfaces are evaluated for impact to existing reliability analysis and associated fault management specifications.

d. Verify that design controls, test plans and procedures, and operational constraints for mission critical software are consistent with corrective actions and retention rationale identified in the CIL.

RFP 80GSFC17R0018 p. 16/25

5.2.4 Reserved

5.2.5 Software Security

The Contractor shall ensure that all ground system deliveries and modifications comply with the governing information technology security plan. When any discrepanices are found during an IT security audit the Contractor shall respond with plan of action with milestones (POAM) document.

5.3 Reviews

In addition to the programmatic lifecycle and milestone reviews and reviews specified in NPR 7150.2B, the Contractor shall ensure the following:

- Software peer reviews

- Software test readiness reviews

- Software acceptance reviews

- System level safety reviews

The Contractor shall provide advance notification, as well as the review materials, prior to all reviews.

5.4 Surveillance of Software Development, Maintenance, and Assurance Activities

The Contractor shall provide access to the software engineering deliverables, process documentation, and work products defined in the Statement of Work, Software Acquisition Management Plan, or the project-approved tailoring of the NASA Software Engineering Requirements (NPR 7150.2B).

The Contractor shall provide access to the following software assurance artifacts:

- Schedule of software assurance reviews, audits, and assessments of the developer’s processes and products

- Software process and product standards and evaluation criteria

- Results from process and product audits performed

- Software Assurance Status Reports (DRD SMA-12)

6. Verification and Validation Program

6.1 General

The Contractor shall implement and verification and validation program based on the

RFP 80GSFC17R0018 p. 17/25 following principles.

• End-to-End Testing - System end-to-end testing shall be performed using actual flight hardware and software, wherever practicable, and shall apply from input to instrument(s), through the spacecraft, transmitted to receiving antennas, and through the ground system - reconciled against what is physically achievable before launch, and consistent with associated mission risk.

• Mission Critical Telemetry and Command Capability – Ground System shall be capable of receiving continuous telemetry coverage from spacecraft during all mission-critical events. Mission-critical events shall be defined to include separation from the launch vehicle; power-up of major components or subsystems; deployment of mechanisms and/or mission-critical appendages; and all planned propulsive maneuvers required to establish mission orbit and/or achieve safe attitude.

• Verification and Validation Program for Mission Software Systems - A thorough verification and validation process shall be applied to all Ground System software systems. This process shall trace customer/mission operations concepts and science requirements to implementation requirements and system design, and shall include requirements based testing of all Ground System elements, and end-to-end system operations scenario testing.

• Long Duration and Failure Free System Level Test of Ground System Software - Ground test of the fully integrated ground system shall include demonstration of error free operations-like scenarios over an extended time period. The minimum duration of uninterrupted system-level and ground system operations is 72 hours for Class A and B missions.

• Maintenance of Mission Critical Component -The updating of mission critical components during the mission operations phase (including any combination of hardware platforms, hardware devices, and software code) shall not compromise the capability of the system to meet mission requirements. Missions shall provide sufficient quantities of flight and ground resources to allow development, test, and operations activities to be conducted without compromising mission availability requirements.

• Command Procedure Changes – Ground System command procedures and/or scripts, and mission databases shall be controlled (treated with the same rigor as changes to flight critical software). This includes formal configuration management, peer review by knowledgeable technical personnel, and full verification with up-to-date simulations wherever possible.

6.2 Documentation of Results

The Contractor shall document results of software testing and include this information in the end-item-data package.

The Contractor shall document software discrepancy reports and participate in anomaly review boards to resolve outstanding software-related issues.

RFP 80GSFC17R0018 p. 18/25

7. Workmanship Standards

7.1 General

The Contractor shall plan and implement a Workmanship Program for 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.

For custom-build hardware, the Contractor shall use the applicable workmanship standards listed below.

• MIL-HDBK-454 General Guidelines for Electronic Equipment

• ANSI/IPC-J-STD-001C Requirements for Soldered Electrical and Electronic

Assemblies (Class 2)

• ANSI/IPC-J-STD-001E Class 3, conformal coating and encapsulation only for polymeric applications.

• IPC/WHMA-A-620B, Class 3 for cable/harness

• IPC-610 Class 2 for Acceptability of Electronic Assemblies

• IPC-610 Class 3 for Soldering for printed wiring assemblies

The Contractor shall purchase or manufacture cable types matching, at a minimum, the workmanship classification standards listed below.

• COTS Ethernet, USB, and power cables shall be manufactured per IPC/WHMA- A-620A class 1. This includes cables built on-site that are comprised of COTS cable and connectors.

• COTS RF, coaxial, twinax, microwave, and multi-wire (D-sub) cables shall be manufactured per IPC/WHMA-A-620A class 2.

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

Custom cable assemblies shall be manufactured per the following requirements:

o Custom cable assemblies with soldered connections shall be manufactured per

IPC/WHMA-A-620A class 2.

o Custom cable assemblies without soldered connections shall be manufactured per IPC/WHMA-A- 620A class 2.

o Custom Ethernet cables shall be manufactured per IPC/WHMA-A-620A class

1.

o NASA-STD-8739.5 Fiber Optic Terminations, Cable Assemblies, and

Installation

Commercially available-off-the-shelf (COTS) material shall be procured from qualified vendors using commercially available vendor catalog item numbers that satisfy the design and workmanship standards specified in the design documentation. The developer shall use the IPC-J-STD-001E (Class 2 Requirements) workmanship standard, for custom and custom portion hardware. The Contractor may propose the use of similar, but not identical, RFP 80GSFC17R0018 p. 19/25 workmanship standards, procedures and training, contingent upon Contracting Officer’s Representative (COR) approval.

7.2 Handling, Packaging, Transporting, and Storage

The Contractor shall document and implement a program that establishes the handling, packaging, transporting, and storage procedures for parts, materials, components and equipment. The program will address:

• Environmental controls, such as temperature, humidity and contamination as required.

• Measures and facilities to segregate and protect items routed to different locations (i.e., to the materials review crib, or to a laboratory for inspection, or returned to the manufacturer from unaccepted shipments).

• Facilities required for the interim storage of components or equipment.

• Protective packaging required for storage and transportation as required.

• Protective surfaces on which parts and materials are handled (i.e., test, assembly, inspection, and organizing kits).

• ESD control as required.

• Shipment data package requirements and vendor acceptance process reference.

7.3 Electrostatic Discharge Control (ESD)

The Contractor shall document and implement an ESD Control Program in accordancewith

ANSI/ESD S20.20.

7.4 Reserved

7.5 Reserved

7.6 Tin Whisker Control Measures

If tin whiskers are detected during the performance of routine maintenance or troubleshooting activities, appropriate measures should be taken to contain the problem.

Containment could include replacement with available spares and/or recommendations to replace with different equipment as a longer term solution.

8. Component, Module, and Unit Control

8.1 General

The Contractor shall provide detailed drawings and component detail for mission critical units and assemblies.

RFP 80GSFC17R0018 p. 20/25

The Contractor shall submit to a design review any modification to COTS products/components.

8.2 Custom or Advanced Technology Devices

The Contractor shall submit to a design review any custom technology devices such as custom microcircuits, hybrid microcircuits, Multi-Chip Module (MCM's), Application Specific Integrated Circuits (ASIC's), etc.

The Contractor shall fully identify in procurement documentation or specification custom devices being procured and include physical, mechanical, electrical, and environmental test requirements and quality assurance provisions necessary to control manufacture and acceptance.

8.3 Parts Used in Off-the-Shelf (COTS) Assemblies

The Contractor shall evaluate mission critical units and assemblies or antennas that are purchased as “off-the-shelf” hardware items.

8.4 Property Inventory List

The Contractor shall maintain a Property Inventory List (PIL) and deliver it.

The Contractor shall retain historical quality records.

The Contractor shall identify mission critical hardware in the PIL.

The Contractor shall include at a minimum the following information in the PIL: number, name or description, manufacturer, manufacturer's generic number, drawing number, specifications, comments as necessary to indicate problems, long lead times, additional testing imposed, and application unique notes.

9. RESERVED

10. RESERVED

11. METROLOGY AND CALIBRATION

11.1 Metrology and Calibration Program

For all equipment used to perform measurements of signals and parameters that require accuracy, the Contractor shall comply with one of the following standards for the calibration of measuring and test equipment:

• ANSI/NCSL Z540.1-1994 (R2002) Calibration Laboratories & Measuring & Test Equipment

- General Requirements

RFP 80GSFC17R0018 p. 21/25

• ANSI/NCSL Z540.3-2006 Requirements for the Calibration of Measuring and Test Equipment

• ISO 17025-2002 General requirements for the competence of testing and calibration laboratories

12. RESERVED

Appendix A. Acronym List

ARB – Anomaly Review Board ANSI – American National Standards Institute ASIC – Application Specific Integrated Circuit ASME – American Society of Mechanical Engineers ASNT – American Society for Nondestructive Testing CAF – Conductive Anodic Filament CCB – Configuration Control Board CDR – Critical Design Review CDRL – Contract Data Requirements List CFR – Code of Federal Regulations CI – Configuration Item CIL – Critical Items List CIT – Certified IPC Trainer CMMI – Capability Maturity Model Integration COR - Contracting Officer’s Representative COTS – Commercial off-the-shelf software CR – Change Request CSCIs – Computer software configuration items DRD – Data Requirements Description DR – Discrepancy Report EEE – Electrical, Electronic, and Electromechanical ELV – Expendable Launch Vehicle EOMP – End of Mission Plan ESC – Exploration and Space Communications ESD – Electrostatic Discharge Control F/ARB – Failure/Anomaly Review Board FAR – Federal Acquisition Requirements FBD – Function Block Diagram FMEA – Failure Modes and Effects Analysis FMECA – Failure Modes and Effects Criticality Analysis FRB – Failure Review Board FSC – Federal Supplier Code FTA – Fault Tree Analysis GFE – Government Furnished Equipment GIDEP – Government-Industry Data Exchange Program GOTS – Government off-the-shelf software GPR – Goddard Procedural Requirement

RFP 80GSFC17R0018 p. 22/25

GSE – Ground Support Equipment GSFC – Goddard Space Flight Center HA – Hazard Analysis I&T – Integration and Test ISAR – Instrument Safety Assessment Report ISS – International Space Station IV&V – Independent Verification and Validation JAXA – Japan Aerospace Exploration Agency LFCP – Lead-Free Control Plan LLA – Limited Life Analysis M&P – Materials and Processes MA – Mission Assurance MAIP – Mission Assurance Implementation Plan MAPTIS – Materials and Processes Technical Information System MAR – Mission Assurance Requirements MCM – Multi-Chip Module MOTS – Modified off-the-shelf software MRB – Material Review Board MTBF - Mean Time Between Failure MTTR - Mean Time to Repair MUA – Materials Usage Agreement MIUL – Materials Identification and Usage List NASA – National Aeronautics and Space Administration NCCCO – National Commission for the Certification of Crane Operators NDE – Nondestructive Evaluation NPD – NASA Policy Directive NPR – NASA Procedural Requirement OTS – Off-the-Shelf O&SHA – Operating and Support Hazard Analyses ODAR – Orbital Debris Assessment Report OHA – Operations Hazard Analysis PAL – Programmable Array Logic PAPL – Project Approved Parts List PCB – Parts control board PCP – Parts Control Plan PDR – Preliminary Design Review PHA – Preliminary Hazard Analyses PIL – Property Inventory List PLA – Programmable Logic Array POAM – Plan of Action with Milestones PPQA – Process and Product Quality Assurance PRA – Probabilistic Risk Assessment PSR – Pre-Ship Review PWB – Printed Wiring Board RMA - Reliability, Maintainability and Availability RMAPP - Reliability, Maintainability, and Availability Program Plan SAE – Society of Automotive Engineers

RFP 80GSFC17R0018 p. 23/25

SCM – Software Configuration Management SDP – Safety Data Package – STS missions only SMA – Safety and Mission Assurance SMA-D – Safety and Mission Assurance Directorate SOW – Statement of Work SQAP – Software Quality Assurance Plan SRP – Systems Review Program SSPP – System Safety Program Plan STD -- Standard V&V – Verification and Validation VDD – Version Description Documents VTL – Verification Tracking Log WCA – Worst Case Analysis WFF – Wallops Flight Facility

ESC MAR p. 24/25

Appendix B: Applicable Documents

Document Number Title

ANSI/ESD S20.20 Protection of Electrical and Electronic Parts, Assemblies and Equipment [Excluding Electrically Initiated Explosive Devices]

ANSI/NCSL Z540.1-

Calibration Laboratories & Measuring & Test Equipment - General Requirements

ANSI/NCSL Z540.3-

Requirements for the Calibration of Measuring and Test Equipment

ECSS-E-10 Space Engineering – System Engineering ECSS-Q-ST-40 Space Product Assurance: Safety ECSS-Q-ST-40-02 Space Product Assurance – Hazard Analysis ECSS-Q-ST-70-10 Qualification of Printed Circuit Boards

GEIA-STD-0005-1 Performance Standard for Aerospace and High Performance Electronic Systems Containing Lead-free Solder

GEIA-STD-0005-2 Standard for Mitigating the Effects of Tin Whiskers in Aerospace and High Performance Electronic Systems

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

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

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

ISO 17025-2005 General requirements for the competence of testing and calibration laboratories

NASA-STD-6016 Standard Materials and Processes Requirement for Spacecraft NASA-STD-8719.13 Software Safety Standard NASA-STD-8719.9 Standard for Lifting Devices and Equipment

NASA-STD-8739.1 Workmanship Standard for Staking and Conformal Coating of Printed Wiring Boards and Electronic Assemblies

NASA-STD-8739.4 Crimping, Interconnecting Cables, Harnesses, and Wiring

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

NASA-STD-8739.6 Implementation Requirements for NASA Workmanship Standards

NASA-STD-8739.8 NASA Standard for Software Assurance NPR 7150.2 NASA Software Engineering Requirements

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

NPR 8715.3 NASA General Safety Program Requirements

Part 46 Federal Acquisition Regulations, paragraphs Parts 46.103, 46.104, 46.202-2, 46.4, and 46.5

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

ESC MAR p. 25/25

Appendix C: Reference Documents

Document Number Title

GSFC 500-PG-

8715.1.2

AETD Safety Manual

GSFC-STD-1000 Rules for the Design, Development, Verification, and Operation of Flight Systems

IEEE Standard 730-

Software Quality Assurance Plans

MIL-HDBK-217 Department of Defense Military Handbook Reliability Prediction of Electronic Equipment

MIL-HDBK-454 Department of Defense Military Handbook General Guidelines for Electronic Equipment

MIL-STD 882E Department of Defense Standard Practice System Safety NASA Fault Tree Handbook

NASA Fault Tree Handbook with Aerospace Applications (http://www.hq.nasa.gov/office/codeq/doctree/fthb.pdf)

NASA-STD 8719.24 NASA Expendable Launch Vehicle Payload Safety Requirements

NASA-STD-8719.13 NASA Software Safety Standard NASA-STD-8739.8 NASA Standard for Software Assurance NPR 8715.3 NASA General Safety Program Requirements Sample Pre-Mishap Plan

Available from the Project Office upon request

SSP-50038 Computer-Based Control System Safety Requirements