Draft PWS_MAVIS.pdf

Mars Ascent Vehicle Integrated System (MAVIS) Draft Performance Work Statement

J-1

Attachment J-1

Performance Work Statement

Mars Ascent Vehicle Integrated System

(MAVIS)

DRAFT

J-2

Table of Contents

1.0 Introduction

1.1 Background

1.2 Scope and Objectives

1.2.1 Subsystems

2.0 Documents

2.1 Applicable Regulations, Procedures and Documents

2.2 Reference Documents

3.0 Management and Control

3.1 Project Management and Administration

3.2 Information Technology (IT) Management

3.3 Facilities

3.3.2 General Needs

3.3.3 ATLO at JPL

3.3.4 ATLO at KSC

3.3.5 Facilities at MSFC

3.4 Government Property Management

4.0 Safety and Mission Assurance

4.1 System Quality

4.2 System Safety

4.3 Reliability

4.4 Software Assurance

4.5 Safety, Health, and Environmental (SHE) Program

4.6 Limited Life Items

5.0 Systems Engineering and Integration (SE&I)

5.1 Configuration Management

5.2 Interface Management

5.3 Integrated Product Team

5.3 Requirements development

J-3

5.4 Perform SE&I Functions for the Design, Development, Testing, and Evaluation of the MAV Integrated Vehicles

5.5 Perform Integrated Systems Analyses

5.6 Products & Deliveries

5.5 Verification and Validation (V&V)

6.0 MAV Subsystem Efforts

6.1 DDT&E

6.2 Avionics

6.3 Reaction Control System (RCS)

6.4 Structures

6.5 Thermal Control System

6.6 Materials and Processing

7.0 Additional Hardware and Development Efforts

7.1 Ground Support Equipment (GSE)

7.1.1 Mechanical GSE

7.2 Electrical GSE

7.3 Special Test Equipment (STE)

8.0 MAV Assembly, Integration, and Test (MAIT)

8.1 Concept of Operations

8.2 Integrated Logistics Supports

8.2 Vehicle Assembly and Integration

8.3 Vehicle Tests and Test Support

8.4 AI&T Facilities

8.5 Vehicle Transportation & Logistics

8.6 RCS Assembly and Integration

8.7 Avionics Assembly and Integration

8.8 Thermal Control System Assembly and Integration

8.9 Earth Launch Operations Support

9.0 Products and Deliveries

9.1 MAV Hardware

9.1.1 Engineering Model (EM)

9.1.2 Flight Test (FT) Model

9.1.3 Assembly, Test, Launch Operations (ATLO)

J-4

9.1.4 Flight Model (FM)

9.1.5 Shipset Spares

9.1.6 Government Furnished Property

9.2 Records

9.2.1 Training Records

9.2.2 Videos, Photos and Visual Inspection Reports

9.2.3 Acceptance Data Package

10.0 Appendices

10.1 Acronyms

10.2 Nonconformance Report (example)

10.3 Notional AI&T Processing Flows

10.4 Government Furnished Property List (MAV Hardware, Spares, and STE)

10.5 Master Test List

J-5

1.0 Introduction

1.1 Background

The goal of the proposed Mars Sample Return (MSR) Campaign is to collect and send sample tubes of Martian rocks, soils, and atmosphere to Earth for detailed chemical and physical analysis. Elements of the MSR Campaign, as currently envisioned, include: 1) Mars 2020 Rover;

2) Sample Retrieval Lander (SRL); and 3) Earth Return Orbiter (ERO). Mars 2020 rover launched in July 2020 and will land in the Jezero Crater region to collect and cache sample tubes on the surface of Mars. The SRL will launch from Earth and place itself in close proximity to the Mars 2020 sample cache in order to collect and launch the cached sample tubes into a predetermined Mars orbit. The ERO will rendezvous with the orbiting sample and bring the samples tubes back to Earth for detailed analysis. Figure 1 illustrates the notional MSR Campaign.

Figure 1: Mars Sample Return Campaign Concept of Operations

The Mars Ascent Vehicle (MAV) will be a payload aboard the Sample Retrieval Lander (SRL), and will be launched as a payload from the SRL. Prior to its own launch from Mars, MAV will survive Earth launch, ~1000 day-cruise phase, Entry, Descent, and Landing (EDL) environments, and ~428 sols on the surface of Mars during the sample retrieval activities. Some of the greatest MAV challenges are the long duration exposure to the Mars environment and the performance required within constrained physical size limitations.

J-6

MAV mission objectives include: 1) receive sample tubes on Mars surface; 2) launch the

MAV and sample tubes to a predefined orbit; and 3) release the sample tubes (Orbiting Sample) into orbit. The scope and purpose of this Performance Work Statement (PWS) pertains to the design, development, integration, and test (DDT&E) responsibilities of the Contractor in support of the MAV Project Office in delivering the MAV to JPL for SRL integration, launch, and flight operations. This also includes the design, development, assembly, integration, and test of the multiple MAV units the Contractor will produce in support of the MAV Project: Engineering Model (EM); Flight Test (FT); Assembly, Test & Launch Operations (ATLO); Flight Model (FM), and FM spare hardware.

The Marshall Space Flight Center (MSFC) will be responsible for the successful delivery and operation of the MAV system including administration, performance, and authority of this contract effort. The Jet Propulsion Laboratory (JPL) will be responsible for the successful execution of the entire SRL mission, including integration of the MAV into the SRL. A management structure has been established to provide JPL insight into the MAV Project, including the effort described herein.

1.2 Scope and Objectives

This Performance Work Statement (PWS) describes the scope of work to execute DDT&E of multiple MAV units, and the design and development of Ground Support Equipment (GSE), including Mechanical (MGSE) and Electrical Ground Support Equipment (EGSE). Currently, the MAV is anticipated to be a two-stage solid rocket vehicle roughly 3 meters in length, 0.5 meters in diameter, and ~400 kg in gross liftoff mass. The first stage includes a thrust vector control (TVC) system. The interstage carries the bulk of the MAV avionics, as well as the hydrazine-based reaction control system (RCS) and the separation system. The second stage features a solid rocket motor, timers, spin-despin motors, battery, antenna, and a payload assembly for Martian soil samples. The Mars Payload Assembly (MPA) will be provided by JPL. The flight MPA will be integrated by JPL. Figure 2 shows a preliminary schematic of the MAV system.

Figure 2: Mars Ascent Vehicle (MAV)

It is expected that the Contractor and MSFC will work in a collaborative environment utilizing the MSFC preliminary design as a beginning point. The Contractor shall evaluate and

J-7 propose modifications to the existing designs to improve assembly, integration, and test. The Contractor shall be responsible for providing labor, cost, and schedule updates in compliance with Earned Value Management (EVM) requirements.

Assembly and integration of four (4) MAV units, plus a shipset of spare parts, shall consist of the following configurations, Figure 3.

Figure 3: MAV Vehicle Configurations

• MAV-EM: Engineering model unit used for integrated vehicle qualification testing. This vehicle unit will have inert motors and no ordnances/hazardous materials and require full forward Planetary Protection (PP), contamination, and Foreign Object Debris (FOD) controls and measures during its AI&T process.

• MAV-FT: Flight test models will be used to perform validation of the integrated vehicle design during flight tests on Earth. These vehicles will have live motors with ordnances/hazardous materials. These vehicles will have Developmental Flight Instrumentation (DFI) and a Flight Termination Systems (FTS). Acceptance testing will be performed prior to execution of the flight tests.

• MAV-ATLO: A combination of the MAV-FM’s interstage and forward structure element combined with the MAV-EM’s Solid Rocket Motor 1 (SRM1), Solid Rocket Motor 2 (SRM2), and MPA. This vehicle’s purpose is to support the SRL in performing integrated SRL/MAV acceptance testing where the MAV’s flight model avionics is necessary but, necessitating the exclusion of the live flight model motors. ATLO testing is performed at JPL and will be managed by the SRL program. The Contractor is expected to support ATLO testing at JPL and manage the transportation and logistics to and from JPL, as well as integration and de-integration into the ATLO configuration.

• MAV-FM: Flight model unit used to perform the Mars mission. This vehicle unit will

J-8 have live motors with ordnances/hazardous materials and will require full forward planetary protection, contamination, and FOD controls and measures during its AI&T process.

• Contamination and FOD controls and measures will be implemented as applicable.

Planetary protection requirements will not be levied on the MAV-FT.

• MAV-Spare: This unit will consist of a complete, unassembled shipset of spare parts.

Some of the parts will be assembled into major assemblies for rapid line replacement if needed. List of spare parts and assemblies will be coordinated with the Contractor.

1.2.1 Subsystems

This PWS will include scope to design, develop, test, and evaluate subsystems of the MAV integrated vehicles. Subsystems include Reaction Control System, Avionics, Structures, and Thermal. Systems Engineering and Integration, Project Management and Control, and Safety and Mission Assurance will also be included in the scope.

2.0 Documents

2.1 Applicable Regulations, Procedures and Documents

Applicable documents can be found in attachment J-4A.

2.2 Reference Documents

Reference documents can be found in attachment J-4B.

3.0 Management and Control

A key goal for the MAVIS contract is to minimize cost with effective and efficient project management. Moreover, the methodologies employed will support the needs of the Government.

The following sections describe methodologies and reporting that will be included in efforts to meet these needs.

3.1 Project Management and Administration

3.1.1 Government Insight/Oversight and Integration Model

The MAV Project will utilize a balanced NASA insight/oversight model that provides efficient interaction between NASA and the Contractor. The goal is to focus insight efforts in the areas and at the levels required to meet the needs of NASA. “Insight” means NASA gaining sufficient understanding of the Contractor’s activities and data in order to adequately assess technical progress, schedule performance, management of risks, and compliance with contract requirements. Areas open to insight include the DDT&E of all flight and ground hardware (including ground support equipment and test instrumentation), integration and tests activities, J-9 transportation and logistics activities, and mission operations planning.

This insight will be largely accomplished via the utilization of Integrated Product Teams

(IPTs). The MAVIS Contractor shall provide personnel to lead and conduct IPTs that will be identified by the MAV Project. Under the leadership of the Contractor, the IPTs will serve as an integrated and collaborative team involving Contractor personnel as well as NASA engineering and MAV Project personnel. The objective of the IPTs is to design, develop, test, and evaluate (DDT&E), manufacture, and produce development, qualification, and flight hardware for the MAV subsystems and system. The MAV Project will lead the effort to develop system requirements and specifications to be flowed down to the subsystem designs. The IPTs will develop plans, testing requirements, all design documentation, manufacturing and assembly process plans, and logistics and operations support planning. The IPTs shall be required for the entire length of the period of performance of the MAVIS contract. More requirements for each subsystem IPT can be found in Section 6.0 of the PWS.

The NASA members of the IPTs will use these forums to gain insight into the Contractor’s DDT&E plans. This will take the form of attending IPT meetings, reviewing material, asking clarifying questions, and making suggestions based on their experience. However, NASA members of the IPTs will not be authorized to provide contractual direction. All contractual direction must come from the MAV PM through the NASA COR. Issues that may arise due to differences of opinion between NASA and Contractor IPT personnel will be resolved via elevation through the normal programmatic channels, i.e. elevation to the MAV PM, the NASA Technical Authorities, and the MAVIS Flight System Manager as appropriate.

An exception to the IPT implementation described above will be the leadership of the IPTs for the Solid Rocket Motors (SRMs), GN&C, Flight Software, and Flight Tests. For these areas, for which NASA will retain design authority (SRMs, GN&C, and Flight Software) and planning/execution authority (Flight Tests), NASA will lead the IPTs with support from the Contractor, therefore maintaining the desired integrated and collaborative environment. The SRMs, GN&C, and Flight Software will be considered GFE to the Contractor for analytical and physical integration into the MAV system. The data from the Flight Tests will be used by the NASA SRM IPT and, as appropriate, by the Contractor to influence the design of the MAV system.

3.1.2 Integrated Product Teams

The MAVIS Contractor shall provide personnel to support Integrated Product Teams (IPTs) that will be established by the MAV Project. The IPTs will consist of an integrated and collaborative team involving NASA engineering, MAV Project, and the MAVIS Contractor to address design and development of MAV hardware. The objective of the IPTs is to design, develop, test, and evaluate (DDT&E), manufacture, and produce development and flight hardware for the Reaction Control, Avionics, Structures, Thermal Control Systems, and AI&T. MAV Project will lead the effort to develop system requirements and specifications of the subsystem designs.

The IPTs will develop plans, testing requirements, all design documentation, manufacturing and assembly process plans, and logistics and operations support planning.

J-10

The IPTs shall be required for the entire length of the period of performance of the MAVIS contract.

3.1.3 Earned Value Management Reporting

The Contractor shall:

2.1.3.1 Perform and report EVM metrics on the MAVIS contract in accordance with

DRD 1745MA-001.

2.1.3.2 Prepare and submit an Integrated Program Management Report in accordance with DRD 1745MA-004.

3.1.4 Work Breakdown Structure (WBS)

The Contractor shall:

3.1.4.1 Prepare and submit a Work Breakdown Structure (WBS) and WBS Dictionary in accordance with DRD 1745MA-002.

3.1.5 Integrated Master Schedule

The Contractor shall:

3.1.5.1 Prepare and submit an Integrated Master Schedule (IMS) in accordance with

DRD 1745MA-XXX.

3.1.6 Technical Performance Metrics (TPMs)

Technical Performance Metrics (TPMs), against contractually approved milestones, will be used to support the assessment of MAV technical progress and to provide an early warning of potential deficiencies before irrevocable technical, cost and schedule impacts occur.

The Contractor shall:

3.1.6.1 Track TPMs as specified by MAV Technical Metrics Plan, MAV-003.

3.1.6.2 Prepare and submit TPM reports in accordance with DRD 1745DE-008.

3.1.7 Risk Management Plan

3.1.7.1 Prepare and submit a Risk Management Plan in accordance with DRD

1745MA-XXX.

J-11

3.1.8 Participation in Meetings and Reviews

3.1.8.1 Support NASA MSR, SRL, and MAV major milestone reviews

3.1.8.2 Support technical interchange meetings, beginning shortly after awarding of the contract.

This includes all necessary travel, preparing and presenting data, and providing document and hardware deliveries in support of Section 9.0. Note: “Contract Award” is synonymous with the effective date of the contract. The MAV Review Plan can be found in Section 3.10 of the MAV-001 MAV Project Plan.

The Contractor shall:

3.1.8.3 Prepare and submit a Major Review Documentation in accordance with DRD

1745MA-003.

3.1.8.4 Attend and participate in the following meetings in support of the MAVIS contract:

Monthly Management Reviews Weekly AI&T Working Group Meeting Test Coordination Meetings Phase D & E Daily Scrums Pre-Installation Meetings Engineering Review Boards Failure Investigation Boards Project Control Boards Risk Management Boards Interface Meetings Hardware Integration Meetings

All related actions from meetings and boards will be directed from the MAVIS Contracting Officer Representative (COR) to the MAVIS Contract Project Manager.

3.1.9 Financial Management

The Contractor shall:

3.1.9.1 Prepare and submit Financial Management Reports (i.e., NF 533M and 533Q) in accordance with Data Requirements Description (DRD) 1745MA-005.

J-12

3.1.10 Integrated Baseline Review (IBR)

3.1.10.1 Conduct an Integrated Baseline Review (IBR), as required by NFS 1852.234- 2, within 180 calendar days of the effective date of the contract.

3.1.11 Organization Conflict of Interest (OCI)

The Contractor shall:

3.1.11.1 Prepare and submit an Organizational Conflict of Interest (OCI) Plan in accordance with DRD 1745MA-007.

3.1.12 Technology Reporting

The Contractor shall:

3.1.12.1 Prepare and submit technical information concerning any invention, discovery, improvement, or innovation made by the Contractor in the performance of work under this contract in accordance with DRD 1745CD-001. Copies of NASA Form 1679 and the NASA New Technology Summary Report (NTSR) Form (Interim and Final) may be obtained and/or filled out at:

https://invention.nasa.gov/.

3.1.13 Environmental/Sustainable Acquisition

The Contractor shall:

3.1.13.1 Conduct MAIT procurement activities in accordance with NPR 8530.1 to support NASA’s need for sustainable acquisition practices.

3.2 Information Technology (IT) Management

The Contractor shall:

3.2.1 TBD

3.3 Facilities

3.3.2 General Needs

The Contractor shall provide, or have appropriate access to, facilities that can be utilized for MAV AI&T. These facilities shall be able to handle inert and live SRMs, hydrazine processing, a clean room environment for PP/Contamination Control (CC), environmental test facilities (i.e.

thermal vacuum chamber, spin balance, random vibration, shock, Electromagnetic Interference https://invention.nasa.gov/

J-13

(EMI) /Electromagnetic Compatibility [EMC]), and lift capabilities.

3.3.3 ATLO at JPL

Facilities will be provided to the Contractor to allow support of the MAV-ATLO at JPL.

These facilities will allow use of appropriate MGSE/EGSE/STE, supply necessary lift capability, and provide clean rooms to support contamination control and planetary protection.

JPL ATLO activities will take place in a number of cleanroom facilities which will range anywhere from very stringent cleanroom conditions (i.e. ISO-5, Class 100) to test areas which do not comply with ISO-8, Class 100,000 cleanliness standards and are compatible with Class 300,000 cleanliness standards. Electrostatic Discharge (ESD) controls will be in place throughout all JPL ATLO activities.

Environmental testing at JPL will be carried out in dedicated test areas, which are not all restricted to Class 100,000 (i.e., ISO-8) cleanliness conditions. In instances where this threshold is not met, hardware will be protected from recontamination (biological and non-biological) by temporary shrouding, encapsulation, bagging, and/or other countermeasures. The Environmental Test Laboratories (ETL) may be biosampled prior to any testing to determine the bioburden levels of the environment. Upon re-entering the Class 100,000 assembly area, sampling and bioassays will be conducted on the tested hardware to determine whether any level of recontamination has occurred, which may consequently lead to remedial procedures, such as solvent wiping and/or selected disassembly, if necessary.

JPL will provide the Hi-Bay Cleanroom in the Spacecraft Assembly Facility (SAF, Building 179) to support ATLO activities integrated with PP biosampling of the hardware as the spacecraft is assembled. ISO 7 (Class 10,000) cleanliness conditions will be enforced – including detailed instructions for garment donning and doffing. Cleanroom supplies will be provided for by the Technical Inventory Management Section.

3.3.4 ATLO at KSC

Facilities will be provided to the Contractor to allow support of the MAV-FM assembly, test, and launch operations (ATLO) at KSC. These facilities will allow use of appropriate GSE/EGSE/STE, supply necessary lift capability, and provide clean rooms to support contamination control and planetary protection.

The ISO-8 (Class 100,000) cleanroom facilities required for assembly of the spacecraft and its subsystems will be provided by KSC. This area will be systematically monitored for fallout bioburden and inadvertent exposures in an effort to minimize the likelihood of biological or non-biological contamination of hardware. Prior to the commencement of assembly, a thorough facility survey will be conducted, and any necessary cleaning and/or additional controls will be instituted to reduce baseline bioburden and contamination levels. This area will be systematically monitored for contamination fallout and inadvertent exposures in an effort to minimize the likelihood of contamination of hardware. ESD controls will be in place throughout all KSC ATLO activities.

J-14

3.3.5 Facilities at MSFC

Facilities are available at MSFC that the Contractor may use for certain MAV AI&T operations. The capabilities of these facilities include the ability to handle (lift and store) inert or live SRMs, process hydrazine, and conduct some environmental testing. These capabilities are in addition to power, water, light, and standard temperature controls.

3.4 Government Property Management

The Contractor shall:

3.4.1 Prepare, implement, and maintain a Government Property Management Plan in accordance with DRD 1745LS-004.

4.0 Safety and Mission Assurance

The Contractor shall:

4.0.1 Prepare and submit a Product Assurance Plan in accordance with DRD 1745RM-001.

4.0.2 Identify and describe comprehensive details of their integrated product assurance (safety and mission assurance) process.

4.1 System Quality

The Contractor shall:

4.1.1 Perform quality assurance for all deliverable subsystem hardware and integrated MAV units, GSE, and any other support equipment that interfaces with qualification and flight hardware per the MAV-008, MAV SMA Plan.

4.1.2 Perform quality processes in accordance with AS9100, “Quality Systems - Aerospace - Model for Quality Assurance in Design, Development, Production, Installation and Servicing.” The Contractor shall be audited by MSFC for inclusion as an evaluated vendor in the NASA Supplier Assessment System (SAS). If the Contractor is already in the SAS at the initiation of the contract, MSFC will audit as needed to maintain that status throughout the MAV lifecycle.

4.1.3 Perform nonconformance reporting, and corrective action. Minor nonconformances that do not decrease mission mass, affect schedule or cost margin, or increase risk will be dispositioned at the MAV MRB. Major nonconformances that adversely affect mission mass margin, schedule, risk, or cost will be dispositioned at the MAV PCB. (Please refer to section 2.1 flow diagram, Figure 4.) A summary of all nonconformances dispositioned by the MAV MRB shall be presented each month at the MAV PCB.

4.1.4 Accommodate GMIPs implemented by MSFC Quality Assurance personnel or Defense Contract Management Agency (DCMA), as established by NPR 8735.2, Management of

J-15

Government Quality Assurance Functions for NASA Contracts GMIPs may be conducted at the Contractor’s facilities and/or their suppliers’ facilities.

The MRB and PCB will disposition recommendations and provide oversight resolution if necessary. Resulting decisions and direction will be transmitted to the Contractor through the Contracting Officer’s Representative (COR). If disposition results in a contract requirement change, it will be processed through the terms and conditions of the contract.

4.2 System Safety

The Contractor shall:

4.2.1 Be subjected to the scope of NPR 8715.7, “Payload Safety Program.” As such, the Contractor shall follow the Safety Review process that is concurrent with the project milestone review process as documented in NPR 8715.7. The scope of the Contractor system safety products shall include ground operations and launch at both KSC (MAV- FM, MAV-ATLO, and associated GSE and operations) and WFF (MAV-FT and associated GSE and operations). The safety products shall address the integrated MAV vehicle, including hardware, software, GSE and operations to support NPR 8715.7.

4.2.2 Design the MAV-FM, MAV-FT, and GSE to be compliant with NASA-STD-8719.24, “NASA Expendable Launch Vehicle Payload Safety Requirements.” When the Contractor cannot meet a requirement or has an alternate approach that meets the intent of the requirement, the Contractor shall coordinate tailoring efforts with MSFC SMA for approval by the Payload Safety Working Group.

4.2.3 Prepare and submit a detailed System Safety Plan (SSP) for NASA’s concurrence in accordance with DRD 1745RM-001, Product Assurance Plan. The details of the SSP shall contain documented processes, objectives, organization, responsibilities, and methods.

System Safety shall be designed into the system design through proactive participation of a design engineering team along with systems engineering, operations, and systems safety engineers. The plan shall describe the integration of system safety provisions into the total program based on early implementation, planned safety certification review/process, and total program life cycle support.

4.2.4 Perform, document, and submit an integrated MAV vehicle System Safety/Hazard Analysis Report (SSHAR) in accordance with DRD 1745SA-001. The SSHAR shall be submitted and updated to satisfy the requirements for Safety Data Packages I, II, and III identified in NPR 8715.7. Using a methodical approach, the analyses shall identify hazards, determine the methods used for controlling the hazards, support the program risk management process, and establish verification methods applicable to design, development, manufacturing and assembly, testing, inspection, integration, and flight (of subject systems) including any interfacing GSE, facilities, and ground operations. The analysis shall include flight systems (hardware and software), GSE, ground operations at the Range, and facilities. The Hazard analysis shall be in compliance with NASA-STD-

J-16

8719.24. The government will provide to the Contractor a SSHAR for the Solid Motors and TVC system. The government will provide to the Contractor a SSHAR for the flight software developed at MSFC. The Contractor shall integrate the Solid Motor/TVC and Flight Software SSHAR with the integrated MAV vehicle SS/HA to form the required Safety Data Packages.

4.2.5 Perform, document, and submit the tailored payload safety requirements for the integrated MAV vehicle as required by NPR 8715.7.

4.2.6 Perform, document, and submit the Ground Operations Plan for the MAV vehicle as required by NPR 8715.7 in accordance with DRD 1745LS-005.

4.2.7 Perform, document, and submit the MAV vehicle Safety Verification and Tracking Log as required by NPR 8715.7.

4.2.8 Support and participate in all Safety Reviews required by NPR 8715.7 by preparing presentations for the reviews, attending and presenting safety analysis and hazard reports at the reviews, and providing responses to comments on safety deliverables to the Payload Safety Working Group.

4.2.9 Participate in bi-weekly flight software safety meetings with MSFC Safety and Mission Assurance to coordinate flight software safety analysis and issues with the MAV vehicle safety analysis being developed by the contractor.

4.2.10 Perform, document, and submit required safety data requirements in support of the Wallops Range Safety Process and Flight Tests Missions. Provide MAV subsystem safety data submittals as required by NASA-800-PG-8715.5 and the NASA-GFSC-STD-8009 standards. Ground Safety Data submittals shall be submitted to the MAV System Safety Engineer thirty (30) days in advanced of each project readiness milestone date(s). MAV Flight Testing safety data updates shall be provided and submitted to the MAV System Safety Engineer as subject to Flight Testing safety requirements tailoring processes.

Provide system safety support for milestone reviews.

4.2.11 Perform, document, and deliver Fault Tree Analysis in accordance with DRD. SA-FTA.

4.3 Reliability

The Contractor shall:

4.3.1 Perform reliability allocation, predictions and analysis (including system level reliability analysis) to assess various flight risks to meet program requirements.

4.3.2 Provide a Reliability Allocation, Predictions and Analysis Report in accordance with DRD

1696RM-004.

Reliability Predictions shall document the reliability model(s) and its underlying ground rules and assumptions used in the Reliability Allocation, Predictions, and Analysis Report along with supporting justification and limitations in case any. These ground rules and assumptions shall be concurred by NASA before proceeding for the detailed analysis.

J-17

Failure Modes Effects Analysis and Critical Item List (FMEA/CIL) effort is one of the most important program tasks to facilitate enhance safety and mission success. A FMEA/CIL is used to identify failure modes, causes, and effects of those failure modes that will adversely affect the operation of the vehicle. FMEA/CIL also provides input to management of the risk assessment and rationale for accepting identified risks. FMEAs will be a functional analysis and as design matures and detail is added it will be expanded to include the increased level of detail. A CIL will be required at CDR with a baselined accepted document at DCR.

As design changes are made the analysis will be updated to include analysis of the new configuration. The FMEA report shall contain a description of the components evaluated as well as any ground rules and assumptions made in the performance of the FMEA. Critical Items List (CIL) analysis shall be performed for those failure modes that can lead to worst case failure conditions such as Loss of Vehicle (LOV), Loss of Mission (LOM) and/or other criticalities which are detrimental to the program per the applicable FMEA/CIL guideline document. The Contractor shall prepare Failure Modes and Effect Analysis and Critical Items List in accordance with DRD 1696RM-001.

The scope of the Contractor provided Reliability Allocation Predictions and Analysis Report and FMEA/CIL shall be the integrated MAV vehicle (hardware and software) over its entire mission life.

The Government will provide to the Contractor a FMEA and Reliability Allocation, Predictions, and Analysis Report for the MAV Solid Motors and TVC systems.

4.4 Software Assurance

The Contractor shall

4.4.1 Establish and implement a Software Assurance program that ensures that Contractor developed software (flight or GSE) complies with NASA software assurance and safety requirements/guidance documents including: NASA-STD-8739.8, "NASA Software Assurance Standard," NPR 7150.2, "NASA Software Engineering Requirements," and NASA-GB-8719.13, "NASA Software Safety Guidebook."

4.4.2 Comply with EWR 127-1, “Range Safety requirements”.

4.4.3 Meet NPR 7150.2 for the applicable software Classification level.

4.4.4 Document the findings and results of software process and product audits in accordance with DRD 1745QE-001, “Software Quality Assurance (SQA) Audit Report”.

4.5 Safety, Health, and Environmental (SHE) Program

The Contractor shall:

4.5.1 Establish and implement an industrial safety, occupational health, and environmental program in accordance with DRD 1745SA-002.

J-18

4.5.2 Prepare and submit an On-Site Safety, Health, and Environmental (SHE) Plan in accordance with DRD 1745SA-002. The SHE Plan shall address in detail each SHE Core Program Requirement (CPR), including their sub-elements identified as applicable to the contracted effort and provide the level of detail necessary to acknowledge the Contractor fully understands the SHE CPRs:

a. CPR 1 - Management Leadership and Employee Involvement.

b. CPR 2 - Worksite Analysis.

c. CPR 3 - Hazard Prevention and Control.

d. CPR 4 - Safety, Health and Environmental Training.

e. CPR 5 - Environmental Management System.

4.5.3 Prepare and submit mishaps and safety statistics reports to the MSFC Industrial Safety Branch in accordance with DRD 1745SA-003. The Contractor shall submit directly into the NASA Mishap Information System (NMIS) or shall use the forms listed in section 15.4 of DRD 1745SA-003 and or electronic equivalent to report mishaps and related information required to produce the safety metrics.

4.6 Limited Life Items

The Contractor shall:

4.6.1 Receive a Limited Life Items List (LLIL) from the MAV project for all hardware that is Government Furnished Property (GFP).

4.6.2 Develop and maintain a LLIL for all flight hardware and ground support equipment items to be provided by the Contractor in accordance with DRD 1745RM-002.

4.6.3 Document and maintain records of operations involving all limited life hardware, line replacement units, subsystems, and assembly materials (as appropriate), to meet NASA Safety and Mission Success policy, applicable product assurance (SMA) plan, and Verification and Validation Plan. Life limits shall be established based on shelf life, operational life, calibration life, and cycle life.

4.6.4 Document life limits for associated ground support equipment in baselined specifications that include the expected environmental conditions, operational constraints, or hardware failure which could cause loss or damage to vehicle systems and/or personnel.

5.0 Systems Engineering and Integration (SE&I)

5.1 Configuration Management

5.1.1 Implement Configuration Management (CM) on hardware, firmware, and software. The

J-19

Contractor’s CM program shall provide the following: (1) configuration identification; (2) configuration control; (3) configuration status accounting; and (4) configuration management verification and audits.

5.1.2 Prepare and submit a Configuration Management Plan (CMP) in accordance with DRD 1745CM-001, which defines the Contractor’s CM program and methods for implementation of the contract requirements. The CM plan shall also address data management of technical data generated, transmitted, and delivered as part of this contract.

5.1.3 Provide the workforce, facilities, and materials required to implement the CM program requirements, including the generation, updates, and maintenance of all technical documentation.

Engineering drawings and associated lists shall be provided to meet the requirements of the American Society of Mechanical Engineers (ASME) Y14.100 and ASME Y14.41 in accordance with DRD 1745CM-003. This documentation shall define the detail design of the hardware and firmware. Engineering drawings shall specify marking criteria and methods for identification of parts.

5.1.4 Perform configuration management of the MAVIS integrated vehicle specifications and ground support equipment specifications, including all interfaces to flight hardware (not controlled by the vehicle Internal Interface Control Document [IICD]). These specifications and related documentation (outlined above) shall be approved by the MSFC MAV Project Control Board (PCB) and will establish the Functional Baseline for Configuration Control. After PDR, any changes to the specifications baseline shall be reviewed and approved by the MAV PCB.

5.1.5 Perform configuration management of the integrated MAV, for all deliverable hardware.

The Contractor shall establish an approval authority (e.g., a Configuration Control Board [CCB]) to control and authorize baselines, changes, and variances to configuration products and documentation. Baseline design configuration of all deliverable hardware shall be approved by NASA at Critical Design Review (CDR). After CDR, changes to the design baseline that affect form, fit or function of deliverable hardware will be reviewed and approved by the MAV PCB. The Contractor shall support MAV PCB as required for hardware design baseline control.

5.1.6 Perform configuration management of the manufacturing materials and processing baseline for all deliverable hardware. The Contractor shall perform configuration control of the manufacturing materials and processing baseline. NASA will approve manufacturing materials and processing baseline of all deliverable hardware at CDR. After CDR, changes to the materials and processing baseline of deliverable hardware shall be reviewed and approved by the MAV PCB. The Contractor shall support MAV PCB as required for Materials and Processes (M&P) baseline control. Materials and processes used in interfacing GSE, test equipment, hardware processing equipment, hardware packaging, and hardware shipment shall be controlled to prevent damage to or contamination of flight hardware.

J-20

5.2 Interface Management

5.2.1 Define, document, and maintain the interface control requirements for which the Contractor is contractually responsible, including but not limited to, the MAV vehicle and interfaces with other vehicle external elements such as the SRL.

5.2.2 Support interface and logistics development through a generation of interface design data.

5.2.3 Develop a vehicle IICD to control the internal to internal interfaces among the subsystem element component units of the MAV, including but not limited to, interfaces with GSE.

The primary purpose of the vehicle IICD is to ensure integration compatibility and functional and environmental performance verification of all subsystem components, and to aid the Contractor in integrating subassemblies into the MAV unit. The MAV System Requirements Document (SRD) will specify the requirements including the responsibilit ies and all Physical, Functional, Fluid, Electrical (Power), Thermal and Environment interfaces.

5.3 Integrated Product Team

5.2.1 Lead, conduct, and support MAV SE&I Integrated Product Team (IPT), including MAV Design Team (MDT) members

5.2.2 Provide status, communication, and coordination with MDT members for insight into the design and analysis of the MAV Integrated Vehicles on a weekly basis

5.2.3 Present cost, schedule, and risk status on a monthly basis

5.2.4 Present technical performance metrics on a monthly basis in accordance with DRD

1745MA-XXX

5.2.5 Provide weekly status of project milestone products

5.3 Requirements development

5.3.1 Develop and manage the MAV End Item Specification (EIS)

5.3.2 Develop, manage, and track the verification and validation data for all subsystems and the

MAV design/units in accordance with the MAV V&V Plan

5.3.3 Receive and evaluate Level IV MAV system requirements

5.3.4 Support, through presentations, concurrence and closure of issues for the MAV V&V closure process and acceptance data packages

5.3.5 Perform a review of the MAV design and existing support documentation and provide an assessment report of the findings

J-21

5.4 Perform SE&I Functions for the Design, Development, Testing, and Evaluation of the MAV Integrated Vehicles

5.4.1 Evaluate, support maturation, and implement the:

5.4.1.1 MAV System Requirements Document

5.4.1.2 MAV Concept of Operations

5.4.1.3 MAV Functions and Functional Decomposition

5.4.1.4 MAV V&V Plan

5.4.1.5 MAV V&V Requirements and Success Criteria

5.4.1.6 MAV external interface control documents

5.4.1.7 MAV Mission/Flight Ops Plan(s)

5.4.2 Lead and perform the MAV design analysis cycles and verification analysis cycles in support towards each MAV milestone

5.4.3 Support requirements flowdown and maintenance of the MAV integrated vehicle and susbsystem requirement and specification documents

5.4.4 Evaluate, mature, and maintain MAV interface control documents

5.4.5 Provide component level design input to each MAV subsystem IPT, such as Avionics, Reaction Control System, Structures, Thermal, and AI&T

5.4.6 Support the development and submission of verification closure reports per MAV V&V plan in accordance with MAV-XXX V&V Plans

5.4.7 Support through presentation, concurrence and closure of issues for the MAV V&V closure process and data acceptance packages

5.4.8 Provide inputs into the Fault Tree Analysis in accordance with DRD 1745MA-XXX

5.4.9 Provide artifacts, charts, and support for MAV milestone reviews, including PDR, CDR, SIR, SAR1, and SAR2.

5.4.10 Use the NASA-provided comment tracking and dispositioning system for MAV milestone reviews.

5.5 Perform Integrated Systems Analyses

5.5.1 Support MBSE efforts for systems engineering integration with the MAV Project.

5.5.2 Perform mass properties control of the integrated MAV design

5.6 Products & Deliveries

5.6.1 System connectivity diagrams and end-to-end functional diagram schematics for all subsystems and the integrated vehicle

5.6.2 Update and maintain MAV-004 Concept of Operations

5.6.3 Generate and manage the MAV Master Equipment List (MEL) per DRD 1745MA -XXX

5.6.4 Provide an integrated mass properties report per DRD 1745MA-XXX

J-22

5.5 Verification and Validation (V&V)

5.5.1 Prepare and deliver a package of all test results, analysis reports, and related documentation to be used for Independent Verification and Validation (IV&V) in the format specified by

DRD 1745CM-002.

This list shall include all functional/physical interface testing at progressive levels of component integration up to and including the fully integrated MAV. Any verification results from form, fit and functional testing (inspection-based verifications), shall be included in this data package. Verification by similarity shall not be allowed without prior program approval.

6.0 MAV Subsystem Efforts

6.1 DDT&E

NASA/MSFC started the DDT&E efforts for the following MAV subsystems: Avionics, Reaction Control System, Structures, and Thermal. The NASA/MSFC efforts in these areas will continue through the System Requirements Review (SRR) and includes procurement of certain items (see Section 10.4) whose lead time puts them on critical path for the mission. Design Authority for these subsystems will transition to the Contractor following the effective date of contract award. The transition will be accomplished through a series of Technical Interchange Meetings (TIMs). To support this transition and the Government Insight/Oversight and Integration Model (Section 3.1.1) for each subsystem, the Contractor shall:

6.1.1 Establish, lead, conduct, and support subsystem-specific Integrated Product Teams (IPTs), which include NASA subsystem-specific membership.

6.1.2 Provide adequate support to the IPTs to address all pertinent aspects of design, analysis, producibility, manufacturability, and quality.

6.1.3 Communicate and coordinate with IPT membership in a timely manner. The suggested meeting frequency is weekly.

6.1.4 Provide inputs to NASA/MSFC to support the development of subsystem specifications.

Following transition of Design Authority, the Contractor shall be responsible for:

6.1.5 Receiving and maturing the design requirements for each MAV subsystem.

6.1.6 Documenting subsystem and vehicle hardware design by producing and releasing component and assembly level engineering drawings per DRD-XXX.

6.1.7 Producing design and performance specifications for MAV subsystem components.

J-23

6.1.8 Performing verification and validation of MAV subsystem component and assembly level requirements.

6.2 Avionics

The Contractor shall:

6.2.1 Provide MAV Avionics hardware for the development and qualification program delivered in time to meet critical DDT&E schedules.

6.2.2 Update and maintain MAV-022 Electrical, Electronic, and Electromechanical (EEE) Parts Management and Control Requirements in accordance with DRD 1745DE-002

6.2.3 Write and maintain MAV Avionics specification, with inputs from MDT members

6.2.4 Procure components, such as raw materials, batteries, EEE parts, wires and connectors, for development, qualification, engineering, and flight units. The MAV Project Control Board will provide final approval for procurement of EEE parts selected for the MAV design.

6.2.5 Perform battery selection, test, and analysis

6.2.6 Evaluate and produce the overall design of the Avionics subsystem

6.2.7 Produce and release engineering drawings in accordance with 1745CM-003

Engineering Drawing and Associated List.

6.2.8 Fit-to-form components and cable harnessing, as called out on engineering drawings.

6.2.9 Fabricate and assemble Avionics development, qualification, engineering, and flight units

6.2.10 Fabricate and assemble cables and wire harness development, qualification, engineering, and flight units

6.2.11 Load software onto hardware in development, qualification, engineering, and flight units

6.2.12 Plan and execute assembly and integration of shipset spare avionics components

6.2.13 Perform engineering qualification testing, such as, EMI/EMC, Thermal vacuum and cycling, including burn-in for electronics, and random vibration per Section 8.0 of the

PWS

6.2.14 Plan and perform the in-process and post-production inspections and tests of development, qualification, engineering, and flight units and their interfaces

6.2.15 Perform flight acceptance testing of the Avionics components and subsystem

6.2.16 Support Government acceptance and post-delivery checkout and test consistent with product assurance plans and qualified acceptance test procedures

6.2.17 Perform non-destructive evaluation of the Avionics system during and after assembly and integration.

6.2.18 Provide test equipment such as break-out boxes, unit testers, test cables, power supplies, and lab equipment. (EGSE – rack that connects to umbilical, lander simulator/emulator)

J-24

6.2.19 Provide antenna hat for RF testing

6.2.20 Perform voltage drop analysis of engineering and flight cables and wire harness assemblies in accordance with 1745DE-003 Electrical Integration System Analyses

6.2.21 Perform structural and stress analysis of Avionics mechanical components in accordance with 1745DE-004 Structural Strength and Fatigue Analysis Reports

6.2.22 Development and installation of the embedded instrumentation, electrical wiring, and connectors for power and data in for all subsystems

6.2.23 Perform board level stress analysis in accordance with 1745DE-004 Structural Strength and Fatigue Analysis Reports

6.2.24 Perform board level thermal analysis per DRD 1745DE-XXX

6.2.25 Perform worse case analysis of board designs for reliability per DRD 1745DE-XXX

6.2.26 Perform Electronics Parts Stress Analysis (EPSA) in accordance with MSFC-STD-

6.2.27 Perform Single Event Effects Analysis (SEEA) in accordance with MSFC-STD-3012

6.2.28 Produce and maintain the detailed acquisition, qualification, and certification of the

MAV Avionics subsystem in accordance with the NDT developed specification

6.2.29 Develop an Operations & Maintenance Manual for the separation system per DRD

1745DE-XXX

6.2.30 Maintain configuration control of the specifications and interface documents in accordance with PWS section 5.4.4.

6.3 Reaction Control System (RCS)

The Contractor shall:

6.3.1 Receive, Inspect, Assemble and integrate RCS components and subassemblies onto the primary structure of the MAV-EM, MAV-FTs 3 and 4, MAV-ATLO, and MAV-FM vehicles.

6.3.2 Plan and execute assembly and integration of shipset spare RCS components

6.3.3 Weld subassemblies of the RCS system

6.3.4 Fit-to-form components and cable harnessing, as called out on engineering drawings.

6.3.5 Perform leak and proof test of the RCS lines during sub-assembly integration activities.

6.3.6 Perform non-destructive evaluation of the RCS system during and after assembly and integration.

6.3.7 Perform pre-flight verification testing and general logistics associated with both GFE and non-GFE supplied RCS hardware.

6.3.8 Integrate the GFE RCS hardware into the MAV Interstage and participate in the technical oversight associated with the RCS GFE.

6.3.9 Develop an Operations and Maintenance Manual for the RCS subsystem in accordance with DRD 1745DE-XXX.

6.3.10 Develop and install the embedded instrumentation, electrical wiring, and connectors for power and data in all areas

J-25

6.3.11 Deliver the detailed acceptance data package in accordance to DRD 1745CM-002 for MAV RCS components

6.3.12 Perform development, qualification, and acceptance test of the RCS design per Section

8.0 of PWS

6.3.13 Provide RCS hardware required to manufacture, assemble, checkout, and test all MAV integrated test articles, simulation test articles including end effectors commanded by the MAV Avionics system, and the MAV flight units.

6.3.14 Provide a thermal analysis report for the RCS subsystem in accordance to DRD

1745DE-XXX.

6.3.15 Perform non-destructive evaluation of the RCS system during and after assembly and integration in accordance with DRD 1745MP-006

6.4 Structures

The Contractor shall:

6.4.1 Produce and release engineering drawings

6.4.2 Design and manufacture the Structural Test Articles (STAs) for development and qualification tests for MAV-EM and MAV-FTs.

6.4.3 Design and manufacture secondary structures

6.4.4 Design and deliver structural flight articles for MAV-ATLO and MAV-FM

6.4.5 Procure development, qualification, and flight separation systems hardware

6.4.6 Develop FEM and perform analysis in accordance with DRD 1745DE-007

6.4.7 Perform coupled loads analysis (CLA) for stress analysis

6.4.8 Perform modal pre-test analysis per NASA-STD-TBD

6.4.9 Perform modal test per DRD 1745DE-XXX

6.4.10 Perform post model test model correlation per DRD 1745DE-XXX

6.4.11 Perform component, assembly, and integrated vehicle level structural analysis in accordance with DRD 1745DE-001

6.4.12 Develop an Operations & Maintenance Manual for the separation system per DRD

1745DE-XXX

6.4.13 Develop design specification for the separation system

6.4.14 Develop design specification for the interstage, forward structure, and secondary structures

6.4.15 Maintain configuration control of the specifications and interface documents in accordance with PWS section 3.0.

6.4.16 Develop and install the embedded instrumentation, electrical wiring, and connectors for power and data in all areas

6.4.17 Conduct Structures subsystem test planning and procedure generation, test facility integration, engineering support for testing, data reduction, post-test data analysis and final test report, and problem resolution in accordance with Section 8.0.

J-26

6.4.18 Conduct test engineering and technician support as required to support test article preparation, installation, checkout, anomaly resolution, test article removal, and storage.

6.4.19 Provide hardware for the development program delivered in time to meet critical DDT&E…