USDV Statement of Work (SOW)_Draft.pdf

C-1

STATEMENT OF WORK

FOR THE INTERNATIONAL SPACE STATION

UNITED STATES DEORBIT VEHICLE

1.0 Introduction

1.1 Overview and Objectives

1.2 Scope

1.3 SOW Organization And Structure

1.4 Technical Direction

2.0 Overall General Requirements

2.1 Program Management

2.1.1 Program Management Review

2.2 Business Management

2.2.1 Scheduling

2.2.2 Business Other

2.3 Configuration Management

2.3.1 Configuration Status Accounting and Verification

2.3.2 Configuration Control/Change Management

2.4 Information Technology

2.5 Export Control Management

2.6 NASA Insight and Approval

2.7 Project Life-Cycle Reviews

2.8 Technical and Program Integration Meetings

2.9 Design, Development, Test, and Evaluation (DDT&E)

2.9.1 Design and Construction Standards

2.9.2 Design, Analysis, and Trades

2.9.3 Interface Management

2.9.4 Test and Verification (T&V)

2.9.5 Technical Performance Measures (TPM)

2.9.6 Test Facility Capability

C-2

2.10 Software Management

2.11 Safety, Reliability, Quality and Mission Assurance

2.11.1 Safety

2.11.2 Reliability

2.11.3 Probabilistic Risk Assessment (PRA)

2.11.4 Quality Assurance (QA)

2.11.5 NASA Advisories And Government Industry Data Exchange Program (GIDEP) Failure Experience Data Processing

2.11.6 Software Safety and Assurance

2.11.7 Safety and Health

2.11.8 Supplier Management

2.11.9 Anomaly Tracking and Reporting

2.11.10 Mishap

2.12 Risk Management

2.13 Launch Vehicle Integration

2.14 ISS Integration

2.15 Flight Operations

3.0 Design, Development, Test and Evaluation (DDT&E) Through Critical Design Review

(CDR) (CLIN 1)

3.1 Resource Management

3.2 Launch Vehicle Integration

3.3 Flight Operations Preparation

3.4 Avionics & Software Simulation and Test Preparation

3.5 Contract Kick-off

3.6 Mission Concept Review (MCR)

3.7 System Requirements Review (SRR)

3.8 System Definition Review (SDR)

3.9 Preliminary Design Review (PDR)

3.10 Critical Design Review (CDR)

4.0 Production, Assembly, Integration and Test (CLIN 2)

4.1 General Requirements

4.2 Milestone C2-2 System Integration

C-3

4.2.1 Launch Vehicle Integration

4.2.2 Flight Operations Preparation

4.2.3 Avionics & Software Simulation and Test Finalization

4.2.4 System Integration Review (SIR)

4.3 Milestone C2-3 AI&T Progress

4.3.1 Launch Vehicle Integration

4.3.2 Flight Operations Preparation

4.3.3 Assembly, Integration, and Test Progress Review (APR)

4.4 Milestone C2-4 System Acceptance

4.4.1 Launch Vehicle Integration

4.4.2 Flight Operations Preparation

4.4.3 Phase III Safety Review

4.4.4 Flight Operations Review (FOR)

4.4.5 System Acceptance Review (SAR)

4.5 Milestone C2-5 Shipment to Launch Site

4.5.1 Shipment to Space Station Processing Facility

4.5.2 Dwell Release Review (DRR)

4.5.3 Shipment to Launch Site Payload Processing Facility

5.0 Dwell (CLIN 3)

6.0 Launch Vehicle Integration and Sustaining (CLIN 4)

6.1 General Requirements

6.2 Pre-Launch

6.2.1 Ground Segment

6.2.2 Pre-Launch Ground Processing, Integration and Test

6.2.3 Launch Operations Preparation

6.2.4 Flight Operations Preparation

6.2.5 Delta FOR

6.2.6 Stage Operations Readiness Review (SORR)

6.2.7 Flight Readiness Review (FRR)

6.2.8 Launch Readiness Review (LRR)

6.3 Launch and Flight Operations

C-4

6.3.1 Launch Operations

6.3.2 Flight Operations

6.3.3 Deorbit Readiness Review (DORR)

6.3.4 Post Mission Support

6.4 Parts

7.0 Special Tasks And Studies (CLIN 5)

7.1 Special Studies (Sub-CLIN 5A)

7.2 Pre-Priced Evaluation of NASA Mission Requirements (Sub-CLIN 5B)

C-5

1.0 INTRODUCTION

1.1 OVERVIEW AND OBJECTIVES

The primary objective of this contract is to procure a safe, reliable, and cost-effective deorbit vehicle to meet NASA’s International Space Station (ISS) end-of-life deorbit mission requirements. This will require the Contractor to design, develop, manufacture, test, integrate, achieve NASA acceptance, deliver, and sustain its United States Deorbit Vehicle (USDV) such that the USDV can perform the final deorbit of the ISS.

1.2 SCOPE

This Statement of Work (SOW) and all applicable documents clauses, and Data Requirements Documents (DRDs) referenced herein define the requirements for the Contractor to meet NASA and Government safety, functional, performance, and interface requirements, , deliver to NASA, and sustain the USDV. This includes but is not limited to the scope for completion of the design, development, test, evaluation, production, assembly, integration, acceptance, delivery, and sustaining of a USDV capable of free flight, rendezvous, and docking with the ISS. The USDV shall perform ISS attitude control, ISS translational maneuvers, and the final ISS orbit shaping and reentry burns, while meeting all mission objectives as specified in this contract. The USDV contractor shall plan and perform all activities required to integrate the USDV with the launch vehicle (LV). The USDV contactor shall provide sustaining engineering from NASA acceptance through the end of mission operations. In addition, the Contractor shall provide special tasks and studies to the extent ordered under Contract Line Item (CLIN) 5, Special Tasks and Studies – Fixed Price of this contract.

The Contractor shall provide all the necessary management, personnel, facilities, equipment, materials, and supplies to deliver the products and services defined in this SOW. Government Task Agreements (GTAs) are available for selected functions to meet this intent in accordance with the Contract.

The scope of CLIN 1 includes SOW Section 2.0, General Requirements required to support CLIN 1, Design, Development, Test and Evaluation (DDT&E) Through Critical Design Review (CDR) activities and will conclude when Review Item Discrepancy/Request for Action (RID/RFAs) from CDR and previous reviews are jointly dispositioned and forward actions are jointly identified and agreed to.

The scope of CLIN 2, Production, Assembly, Integration and Test includes SOW Section 2.0, General Requirements required to support CLIN 2 activities, completion of the design, and includes the completion of forward actions identified in CLIN 1. The scope of CLIN 2 will conclude following completion of Milestone C2-4 System Acceptance and Milestone C2-5 Shipment to Launch Site, including completion of System Acceptance Review (SAR), Dwell Release Review (DRR), the shipment of the USDV System to the Launch Site Payload Processing Facility (LS PPF), and corrective actions and mitigations to address issues identified during shipment have been completed.

C-6

1.3 SOW ORGANIZATION AND STRUCTURE

This SOW is organized to align with five CLINs:

SOW

Section #

Title CLIN

1.0 Introduction Applicable to all CLINs

2.0 Overall General Requirements Applicable to all CLINs

3.0 Design, Development, Test and Evaluation

(DDT&E) Through Critical Design Review

(CDR)

CLIN 1 (Cost Reimbursable)

4.0 Production, Assembly, Integration and Test CLIN 2 (Firm Fixed Price)

5.0 Dwell CLIN 3 (Firm Fixed

Price)

6.0 Launch Vehicle (LV) Integration and

Sustaining

CLIN 4 (Firm Fixed Price)

7.0 Special Tasks and Studies CLIN 5 (Firm Fixed

Price)

C-7

1.4 TECHNICAL DIRECTION

a. The Performance of the work under this contract is subject to the written technical direction of the NASA Contracting Officer’s Representative (COR), who will be specifically appointed by the NASA Contracting Officer (CO) in writing. “Technical direction” means a directive to the Contractor that approves approaches, solutions, designs, or refinements; fills in details or otherwise completes the general description of work or documentation items; shifts emphasis among work areas or tasks; or furnishes similar instruction to the Contractor. Technical direction includes requiring studies and pursuit of certain lines of inquiry regarding matters within the general tasks and requirements in the contract SOW. All technical direction shall be issued in writing by the COR.

b. The COR does not have the authority to, and shall not, issue any instruction purporting to be technical direction that composes of the following:

1. Constitutes an assignment of additional work outside the SOW

2. Constitutes a change as defined in the “Changes” clause (contract Section I)

3. Constitutes a basis for any increase or decrease in the total estimated contract cost, the fixed fee (if any), or the time required for contract performance

4. Changes any of the expressed terms, conditions, or specifications of the contract

5. Interferes with the Contractor’s rights to perform the terms and conditions of the contract

c. The Contractor shall proceed promptly with the performance of the technical direction duly issued by the COR in the manner prescribed above and within the COR’s authority. If, in the Contractor’s opinion, any instruction or direction by the COR falls within any of the categories defined above, the Contractor shall not proceed, but shall notify the CO in writing within five (5) calendar days after receiving it. Additionally, the Contractor shall request the CO to either issue an appropriate contract modification within a reasonable time or advise the Contractor in writing within thirty (30) calendar days that the instruction or direction is rescinded in its entirety or respond that the technical direction is within the requirements of the contract and does not constitute a change under the “Changes” clause of the contract, and that the Contractor should proceed promptly with its performance.

d. A failure of the Contractor and CO to agree that the instruction or direction is both within the requirements of the contract and does not constitute a change under the “Changes” clause, or a failure to agree upon the contract action to be taken with respect to the instruction or direction, shall be subject to the Disputes clause of this contract.

e. Any action(s) taken by the Contractor in response to any direction given by any person other than the CO or the COR shall be at the Contractor’s risk.

C-8

2.0 OVERALL GENERAL REQUIREMENTS

Section 2 provides the scope of the work applicable to all CLINs and associated tasks required to manage and lead the USDV contract.

a. The Contractor shall design, develop, deliver, and sustain the USDV to meet the requirements in SSP 51101, USDV Systems Requirements Document (SRD).

b. NASA will provide a Medium Class LV and LV Integration.

c. The Contractor shall deliver a USDV spacecraft, that when fully fueled, is compatible with a Medium Class LV in accordance with USDV Launch Vehicle Summary.

d. The Contractor shall maintain readiness of the USDV and support personnel to support the planned launch date with 12 months of notification from NASA.

2.1 PROGRAM MANAGEMENT

a. The Contractor shall perform all program management functions required to provide the full scope of the USDV contract.

b. The Contractor shall flow down applicable requirements to all subcontractors, vendors, and teaming partners.

c. The Contractor shall provide all resources, tools, facilities, processes, and functions required to meet the requirements on this contract.

d. The Contractor shall provide NASA insight into all technical and programmatic activities performed under this contract.

e. The Contractor shall develop, implement, maintain, deliver, and operate in accordance with a Program Management Plan (PMP) per Program Management Plan (DRD

USDV-1).

f. The Contractor shall develop, maintain, and implement a process to verify flight certification and readiness in accordance with SSP 50108, ISS Program Certification of Flight Readiness Process Document. The Contractor’s auditable approach shall verify that all flight preparation responsibilities and requirements have been met and that all problems have been dispositioned. The Contractor shall provide objective evidence required to certify Contractor readiness for NASA certification of flight readiness.

g. The Contractor shall provide the USDV Contractor Certification of Flight Readiness (CoFR) endorsements in accordance with SSP 50108, ISS Program Certification of Flight Readiness Process Document, and SSP 50902, Transportation Integration Office Certification of Flight Readiness Implementation Plan. The Contractor shall provide technical and programmatic inputs and subject matter expertise to address issues and concerns at the Stage Operations Readiness Review (SORR), Flight Readiness Review (FRR), and Launch Readiness Review (LRR), including any pre-board meetings and activities.

h. The Contractor shall apply all Applicable documents and standards identified in Attachment J-05, Applicable and Reference Documents List.

C-9

i. The Contractor shall meet all applicable local, national, and international laws and regulations during contract performance. The Contractor shall be responsible for obtaining and maintaining all applicable licenses, permits, and agreements required to deliver the USDV contract.

j. The Contractor shall perform activities and implement internal processes that meet the contract requirements and Applicable Document List in order to conduct reviews, provide products, and provide verifications to confirm the USDV System is being implemented in a manner that satisfies the contract requirements including the USDV responsibilities documented in SSP 51105, U.S. Deorbit Vehicle Integration Plan.

k. The Contractor shall be responsible for safe transportation of the USDV, flight hardware, and ground hardware in accordance with the USDV Transportation and Logistics Requirements Plan (DRD USDV-29).

l. The Contractor shall manage NASA-Owned/Contractor-Held records in accordance with Title 36 of the Code of Federal Regulations, Chapter XII B, Records Management, and NPD 1440.6, NASA Records Management. The records shall be organized in accordance with the instructions in NPR 1441.1, NASA Records Management Program Requirements, and NRRS 1441.1, NASA Records Retention Schedule, as applicable. The contractor shall disposition records and non-records in accordance with NPR 1441.1, NASA Records Retention Schedule, which has been approved by NASA and the National Archives and Records Administration. All questions on records management issues shall be directed through the CO to the ISS Records Liaison Officer.

m. The Contractor shall maintain a records management program for all data/records produced as part of this contract and submit a plan to analyze, manage, administer and disposition Government owned and Contractor managed data in accordance with Program Management Plan (DRD USDV-1). The Contractor shall verify and validate their data and records management system through the Contractor’s internal audit process.

2.1.1 PROGRAM MANAGEMENT REVIEW

The quarterly Program Management Reviews (PMRs) provide NASA with insight into the Contractor’s, subcontractor’s, and vendors’ performance. The PMR provides NASA management an overall program status on technical, cost, and schedule performance.

a. The Contractor shall conduct quarterly PMRs for NASA and provide review products in accordance with Program Management Review (PMR) (DRD USDV-2).

2.2 BUSINESS MANAGEMENT

2.2.1 SCHEDULING

The Contractor shall develop, implement, maintain, deliver, report, and operate in compliance with the Integrated Master Schedule (IMS) in accordance with Integrated Program Management Report

(IPMR) (DRD USDV-7).

C-10

2.2.2 BUSINESS OTHER

a. The Contractor shall develop, implement, maintain, deliver, report, and operate in compliance with the Organizational Conflicts of Interest Avoidance and Mitigation Plan submitted in accordance with Organizational Conflicts of Interest (OCI) Plan

(DRD USDV-10).

b. The Contractor shall develop, implement, maintain, deliver, and operate in compliance with the Government Property Management Plan submitted in accordance with Government Property Management Plan (DRD USDV-16).

c. The Contractor shall deliver the required financial and logistics reports in accordance with Financial Reporting Contractor-Held Property (DRD USDV-17).

d. The Contractor shall develop, implement, maintain, deliver, and operate in compliance with the Diversity, Equity, Inclusion, and Accessibility (DEIA) Plan submitted in accordance with Diversity, Equity, Inclusion, and Accessibility (DEIA) Plan (DRD

USDV-12).

e. The Contractor shall develop, implement, maintain, deliver, and operate in compliance with the Small Business Subcontracting Plan and deliver required reports in accordance with Small Business Subcontracting Plan and Reports (DRD USDV-11).

2.3 CONFIGURATION MANAGEMENT

a. The Contractor shall develop, implement, and administer configuration management operations as specified in this contract and in accordance with SSP 41170, Configuration Management Requirements.

b. The Contractor shall develop, deliver, maintain, and implement a configuration management plan in accordance with Configuration Management Plan (DRD USDV- 13).

c. The Contractor shall maintain a single technical library that contains all USDV technical data, drawings, and documents maintained under a configuration management system by the Contractor and subcontractors. All data, drawings, and documents created, and configuration managed under this contract shall be maintained in electronic format in the technical library and the data shall be readily accessible to NASA and NASA support contractors, searchable and downloadable to support NASA insight.

2.3.1 CONFIGURATION STATUS ACCOUNTING AND VERIFICATION

a. The Contractor shall identify, establish, maintain, and provide NASA access to reconciled configuration baselines for all hardware in accordance with SSP 41170, Configuration Management Requirements.

b. The Contractor shall ensure that the application of Configuration Status Accounting (CSA) requirements and Contractor systems to maintain the USDV hardware and software product baselines are in accordance with SSP 41170, Configuration Management Requirements.

C-11

c. The Contractor shall develop, maintain, and implement a Configuration Hardware and Software Status Accounting system in accordance with SSP 41170, Configuration Management Requirements. This includes processes and provisions for reports and/or access to CSA data by NASA and ISS support contractors. The Contractor shall ensure that historical configuration data is properly retained in a closed-loop accounting and verification system. The Contractor shall reconcile the CSA data with operational procedures, drawings, and modifications.

d. The Contractor shall participate in NASA audits of compliance with Configuration Management requirements and processes by providing access to personnel, facilities, and data.

2.3.2 CONFIGURATION CONTROL/CHANGE MANAGEMENT

a. The Contractor shall review, process, and evaluate NASA changes in accordance with

SSP 41170, Configuration Management Requirements. The Contractor shall review and evaluate changes, originating from outside the contract, when required, to determine if those changes have potential impacts to the contract. The change management process shall be conducted in accordance with SSP 50123, Configuration Management Handbook. The USDV is an ISS Core System as defined in SSP 41170, Configuration Management Requirements.

b. The Contractor shall assess and provide a determination of the category a change falls into: Category A (no impact or administrative change only) or Category B (impact, further evaluation required). For Category B changes, the Contractor shall evaluate and respond, within 30 calendar days unless specified otherwise from initial change notification, with an impact assessment to include:(1) whether the change can be implemented, (2) when the change can be implemented, (3) an impact assessment for which USDV products are affected and (4) a qualitative Rough Order of Magnitude (ROM) determination required for implementation

c. The Contractor shall submit deviations and waivers in accordance with SSP 41170, Configuration Management Requirements. The Contractor shall review and evaluate Program deviations, waivers, and exceptions originating from outside the contract, when required, to determine if those deviations, waivers, or exceptions have potential impacts to the contract. The deviation and waiver process shall be conducted in accordance with SSP 50123, Configuration Management Handbook. The USDV is an ISS Core System as defined in SSP 41170, Configuration Management Requirements.

d. The Contractor shall use the ISS Program Configuration Status Management Operations System (COSMOS) data base to review and respond to ISS change requests, deviations, and waivers.

2.4 INFORMATION TECHNOLOGY

a. The Contractor shall perform all Information Technology (IT) functions required to execute the USDV contract. The Contractor shall develop, implement, deliver, maintain, and operate within the IT Security Management Plan and IT Security Plan(s) in accordance with Information Technology Security Management Plan (ITSMP)

C-12

(DRD USDV-14).

b. The Contractor’s IT and Operational Technology systems, which store, process, or disseminate NASA information shall comply with NPR 2810.1, Security of Information Technology.

2.5 EXPORT CONTROL MANAGEMENT

a. The Contractor shall develop, implement, maintain, deliver, and operate in compliance with the Export Control Plan submitted in accordance with Export Control Plan (DRD

USDV-15).

b. The Contractor shall perform all Export Control functions required for the USDV contract.

c. The Contractor shall ensure that only specific data that has been identified as Export Administrative Regulations (EAR) and international Traffic in Arms Regulations (ITAR) designations is marked with an appropriate Destination Control Statement that includes the export classification and corresponding export authority. Other data within deliverables that is not export controlled should not be globally marked as EAR or ITAR by default.

d. The Contractor shall ensure that products determined suitable for public release by the NASA and Contractor are labeled accordingly.

e. The Contractor shall establish cooperative relationships with ISS International Partners (IP) and ISS IP related entities to support the implementing arrangement between NASA and IPs for the decommissioning of the ISS.

f. The Contractor shall perform technical interactions with IPs and IP related entities that are necessary for exchange of data, hardware, and software. It shall be the responsibility of the Contractor to seek and obtain Technical Assistance Agreements for technical interactions with any international partners as required.

2.6 NASA INSIGHT AND APPROVAL

a. The Contractor shall develop, implement, maintain, deliver, and operate in compliance with an Insight Management Plan in accordance with Insight Management Plan (DRD

USDV-5).

b. The Contractor shall provide all NASA designated personnel (including support contractors) direct access to facilities, USDV flight hardware, Ground Support Equipment (GSE), personnel, and support services to accommodate the requirements as specified in the Contract. The Contractor shall provide access for all aspects of manufacture and processes, assembly, integration, test, evaluation, verification, training, sustaining, and operations of the USDV, including, upon request, those used on non-NASA missions of similar systems. The Contractor shall process and grant access to NASA designated personnel within 5 business days of the NASA request.

c. The Contractor shall provide all NASA designated personnel (including support contractors) direct access, both remotely and onsite, to data including, but not limited

C-13 to: management information, technical data, documentation, drawings, patterns, models, analyses, products, manufactured product information, documents, changes, issues, non-conformances, waivers, deviations, and operations data to accommodate the requirements as specified in the Contract. The Contractor shall ensure aspects associated with access to data include the following:

1. Be in a useable and readable format within the Contractor database that is accessible by NASA at all times from onsite and remote locations for three years post USDV mission completion

2. Provide this information for all aspects of the design, development, analysis, manufacture and processes, integration, test, evaluation, verification, acceptance, training, sustaining, and operations of the USDV, including, upon request, those used on non-NASA missions of similar systems

3. Organize and catalog these records so that they may be rapidly located and retrieved by NASA to support ground and on-orbit operation

4. Provide a method of sharing, reporting, collecting, recording, and accessing USDV data between NASA and NASA support personnel, the Contractor, and the Contractor’s safety critical subcontractors/vendors to enable immediate collaborative access

5. Retrieval from a single source of the Contractor’s IT systems

6. Access capability provided to NASA as soon as possible after contract award, but no later than 45 calendar days prior to the Mission Concept Review (MCR) kick-off and be maintained through the life of the USDV contract

7. Manufacturing process, quality records, and any other data for the Government to perform a successful risk-based analysis (RBA) that will facilitate the identification of high-risk areas and closure of identified Product Assurance Actions (PAAs)

d. The Contractor shall notify NASA within 24 hours of any identified major nonconformances and report a summary of minor nonconformances during PMR for nonconformances identified at the Contractor and subcontractor level.

e. The Contractor shall provide a Government Resident office at the Contractor’s major manufacturing and engineering facilities for the life of the contract.

f. The Contractor shall provide advanced notice of and allow Government attendance at all activities (e.g., tests, audits, test readiness reviews, pre-ship reviews (PSRs) of flight hardware).

g. The Contractor shall allow International Partner/Participant personnel attendance at designated events, when requested.

h. The Contractor shall provide the capability for NASA and its support service contractors to request, capture, and upload/download imagery of the USDV and ground support equipment for NASA use throughout all phases of the USDV contract.

C-14

i. NASA approval is required as specified in the contract, including the following:

1. The USDV System and subsystems (including software) requirements, baseline design and configuration, and verification and validation (V&V) plan for compliance with NASA requirements and any associated changes

2. Problem resolutions and deviations to the design through production, test, and acceptance; major nonconformances identified at Material Review Board (MRB);

anomaly resolutions plans and closures; non-conformances dispositions; failure analysis conclusion; and post-test reports

3. Hardware, software, interfaces, and operations that could impact NASA assets, NASA crew or NASA mission objectives including USDV mission

4. Interface requirements between the following:

i. USDV System and ISS

ii. USDV and Launch Vehicle

iii. USDV and Mission Control Center Houston (MCC-H)

iv. USDV to Near Space Network

v. USDV to Government Furnished Property

5. Category 1 and Category 2 Material Usage Agreements (MUAs) as defined in NASA-STD-6016, Standard Materials and Processes Requirements for Spacecraft

6. Waivers or equivalent that relieves the Contractor of meeting NASA level requirements

7. Use and implementation of all Alternate Standards and Tailoring

8. Entrance and exit criteria for all reviews and milestones; and confirmation that the Contractor has satisfactorily achieved each criterion for review and milestone completion

9. Hardware/Software Qualification and Acceptance Plan and Approach

10. Test Readiness Reviews, test plans/procedures, test results, and data packages for tests involving NASA property, facilities and/or personnel in accordance with NASA process and procedures

11. NASA-led Mishap and Failure Review Boards

12. NASA crew and flight control training, training products, mockup/simulator development, mission operations and operations products

13. Planned verification methods (Test, Analytical, Demonstration, and/or

Inspection), procedures, success criteria, assumptions, rationale, and comparisons to any similar proven designs

14. All Type 1 and Type 2 DRDs, including changes

C-15

j. NASA insight is required as specified in the contract, including the following:

1. Subsystem and component Specifications including performance requirements

2. Test Readiness Reviews and associated packages including description of test apparatus, test sequence and levels, configuration drawings and schematics, and test procedures

3. Subsystem and Component Level Design Reviews

4. Interface requirements between the USDV and GSE

5. Safety and Mission Assurance Compliance Evaluations (prime and subcontractor)

6. Specific production progress through reviews, plans, schedules, and risks resulting from non-USDV missions

7. Minor nonconformances identified through MRBs

8. Fabrication, assembly/integration, test, and packing/shipping/handling/transport plans and procedures that demonstrate control of risks to hardware integrity such as excess pressure, temperature, applied loads, voltage/current, humidity, contamination, corrosion, etc.

9. Category 3 deviations from Materials and Processes requirements using the MUA system in accordance with NASA-STD-6016, Standard Materials and Processes Requirements for Spacecraft

10. Observation of the Contractor’s non-USDV vehicle operations on a non-interference basis to support NASA training

2.7 PROJECT LIFE-CYCLE REVIEWS

The intent of the Project Life-Cycle Reviews is to provide data, materials, and a forum for open dialog between NASA and the Contractor with respect to USDV design, development, testing, verification, integration, acceptance, and operations.

a. The Contractor shall deliver a Project Life-Cycle Review Plan in accordance with Project Life-Cycle Review Plan and Data Packages (DRD USDV-3).

b. The Contractor shall include a formal Review Item Discrepancy (RID)/Request for Action (RFA) process for all Project Life-Cycle reviews.

c. The Contractor shall perform activities, conduct Project Life-Cycle reviews, and provide verifications according to their internal processes, to confirm that the USDV System and its subsystems are being implemented in a manner that satisfies the NASA requirements.

2.8 TECHNICAL AND PROGRAM INTEGRATION MEETINGS

a. The Contractor shall provide technical and programmatic subject matter expertise to

NASA Program meetings, boards, and reviews, and provide program and technical data to inform NASA decision-making, perform evaluations and support other

C-16 programmatic activities as requested by NASA, to include participating in NASA-led boards, meetings, System Problem Resolution Team meetings, Avionics and Software telecons, briefings, forums, working groups, and other activities.

b. The Contractor shall allow NASA participation in the Contractor’s, subcontractors’ and vendors’ technical meetings, boards, reviews, tests related to the design, development, testing, verification, certification, integration, and operations of the

USDV.

c. The Contractor shall lead an executive meeting every two weeks with NASA Program Management to review current USDV status, plans, anomalies, risks, mitigations, and issues.

2.9 DESIGN, DEVELOPMENT, TEST, AND EVALUATION (DDT&E)

The Contractor shall deliver, implement, and operate in accordance with the Design, Development, Test, and Evaluation (DDT&E) Plan (DRD USDV-25), which details the methods, processes and process controls used to evolve the USDV into flight ready hardware for delivery to NASA

2.9.1 DESIGN AND CONSTRUCTION STANDARDS

NASA standards provide a roadmap of how NASA requires the Contractor to design, build, test and sustain the USDV. Design and Construction and Safety standards are proven methods to improve safety for human spaceflight and there are critical requirements embedded in them.

a. The Contractor shall develop, implement, maintain, deliver, and operate in compliance with NASA Standards and Specifications Compliance and Tailoring in accordance with NASA Standards and Specifications Compliance and Tailoring (DRD USDV- 33). In the event any proposed alternate and/or tailored standards are not approved during the Initial DRD submission (MCR), they shall be approved through the final DRD submission (PDR), otherwise the NASA standard shall be applicable.

b. NASA will be responsible for a NASA-led adjudication process to approve alternate or tailored standards proposed by the Contractor.

c. The Contractor shall engage NASA for any alternate and/or tailored standards at any time during contract performance if any deviation, waiver, or update is proposed to an already approved DRD. Early engagement by the Contractor is encouraged to assure NASA acceptance prior to a DRD submission for approval.

d. NASA will lead adjudication of the Contractor proposed alternate and/or tailored standards and specifications. The Contractor shall identify a USDV Point of Contact (POC) for each proposed alternate and/or tailored standard. The USDV POC shall participate, provide timely submission of the requested information detailed below, and represent the USDV Contractor during the adjudication process. Adjudication will include information from both NASA and Contractor related to the following items:

1. An assessment of the estimated schedule, technical, and risk impacts associated with using the Contractor proposed versus NASA standard

2. An assessment of past and current efforts to meet the intent of the standard with

C-17 proposed alternate and/or tailored standards

3. Jointly (NASA and Contractor) documented key areas of disagreement

4. Jointly (NASA and Contractor) developed decisional package for presentation at a NASA Control Board

e. NASA will have primary responsibility for assessing “meets the intent” for each proposed alternate and/or tailored standard, prior to any approval date associated with NASA Standards and Specifications Compliance and Tailoring (DRD USDV-33), as well as following final adjudication after any NASA Control Board decisions.

f. NASA will have final approval authority for use of alternate standards and tailoring.

2.9.2 DESIGN, ANALYSIS, AND TRADES

a. The Contractor shall perform all engineering analyses necessary to develop and design a USDV that meets all system requirements, interface requirements, and lower-level requirements. The Contractor shall document the results of all analyses performed and make available for review by NASA throughout contract including at Project Life- Cycle Reviews and PMRs.

b. The contractor shall perform a Re-programmability trade study showing that the full list of avionics including logic devices (firmware, Field Programmable Gate Array (FPGAs), etc.) has been assessed for mission suitability to ensure that each device's mission criticality, complexity, risk, and likely need for updates was taken into account to determine the device selection, architecture and method required for update in accordance with the Software Management Plan (DRD USDV-24). The USDV provider shall indicate which devices require removal and replacement, approximate level of schedule or mission impact, whether the device requires crew reconfiguration to reprogram, special software to perform reprogram, and other limitations the designer deems important to point out.

2.9.3 INTERFACE MANAGEMENT

a. The Contractor shall provide technical support and USDV inputs required to develop

Interface Control Documents (ICDs) between USDV and external interfaces including:

1. USDV-to-LV ICD

2. USDV-to-ISS ICD(s)

3. USDV-to-ISS Software ICD(s)

4. USDV-to-Ground ICD

5. USDV Training Simulator to NASA Mission Training Center (MTC) ICD

6. Software Development and Integration Laboratory (SDIL) to USDV SDIL

Simulator ICD

7. Hardware/software ICD between USDV and Government Furnished Property

C-18

2.9.4 TEST AND VERIFICATION (T&V)

a. The Contractor shall perform T&V in accordance with SSP 51101, U.S. Deorbit

Vehicle Systems Requirements Document and SSP 41170, Configuration Management Requirements.

b. The Contractor shall provide the following T&V documents:

1. Verification and Validation Plan – Verification and Validation Plan (DRD

USDV-26), is a USDV document defining the requirements and approach to the USDV System, subsystem and component testing consistent with the U.S.

Deorbit Vehicle Integration Plan (SSP 51105).

2. Joint Integration Verification and Test Plan (JIVTP) – The JIVTP is a jointly developed document defining the requirements and approach for integrated testing of USDV with participation of NASA personnel.

c. For all joint test activities identified in the JIVTP, the Contractor shall conduct Joint Test Readiness Reviews (JTRR), co-chaired by NASA. The Contractor shall demonstrate overall readiness of the test articles, facilities, support equipment, test teams, and agreements (e.g., test hardware, software, procedures, and data exchanges), including the following:

1. Objectives of the testing have been defined and documented, and all the test plans, procedures, environments, and configurations of the test item(s) support those objectives.

2. Configuration of the system under test has been defined and agreed to. All interfaces have been placed under configuration management or have been defined in accordance with an agreed-to plan, and a software Version Description Document (where applicable) has been made available to TRR participants prior to the review.

3. Pass/Fail criterial are defined and agreed to.

4. GSE and interface simulators are in place and support the test objectives.

5. All applicable functional, unit-level, subsystem, system, and qualification testing has been conducted successfully.

6. All JTRR-specific materials such as test plans, test cases, and procedures have been made available to all participants at least three (3) working days prior to conducting the review.

7. All known system discrepancies have been identified and dispositioned in accordance with an agreed-upon plan.

8. All previous design review success criteria and key issues have been satisfied in accordance with an agreed-upon plan.

9. All required test resources people (including a designated test director), facilities, test articles, test instrumentation, and other enabling products have been identified and are available to support required tests.

C-19

10. Roles and responsibilities of all test participants are defined and agreed to.

11. Test and contingency planning have been accomplished, and all personnel have been trained.

12. Facility safety has approved all hazardous procedures and concurs with controls that are in place.

d. The Contractor shall perform Software V&V Re-verification and re-analysis when any of the following occur:

1. Requirement, Data Item/Element, and Interface changes affect operating software

2. Design changes affect operating software function or reliability

3. Software code changes occur that affect requirements or flight software capabilities

4. Inspection, test, mission change, or other data indicate a more severe environment or operating condition than originally verified and validated to.

2.9.5 TECHNICAL PERFORMANCE MEASURES (TPM)

The Contractor shall track and report TPMs performance budgets, current margins, and trending data at Project Life-Cycle Reviews and PMRs. The TPMs are metrics to evaluate design progress toward meeting system performance requirements. The Contractor’s TPMs shall include, but are not limited to:

a. Mass margin, including margin associated with compatibility with a Medium Class LV as required in Section 2.0

b. Power margins (free flight and docked)

c. Thermal margins

d. Propellant margins

e. Control system stability margins

f. Thrust versus predicted/specified

g. Computer & Software Processor, Command and Data Handling Busses and Memory

Utilization

2.9.6 TEST FACILITY CAPABILITY

a. The Contractor shall develop, maintain and operate a high-fidelity, integrated Hardware-In-The-Loop (HITL) configuration controlled test bed, exercising all necessary flight-like hardware and software components for the verification of flight-critical mission objectives in accordance with Specification for USDV Avionics and Software/Hardware-In-The-Loop (HITL) Test Bed (DRD USDV-46) and the following:

1. The HITL shall use flight-like hardware for all components needed to meet mission objectives.

C-20

2. The HITL shall have a complete complement of devices containing flight software (including firmware, programmable logic, and redundant strings).

3. The HITL shall have the capability to verify redundancy, including failover, Failure Detection and Isolation Response (FDIR), manual and automated recovery capabilities, and any vehicle architecture specific failures.

4. The HITL shall have the capability to verify the software loading process, including patch capability.

5. The HITL shall have the capability to perform flight-following of the USDV to follow on-orbit activities, reproduce and troubleshoot on-orbit issues, and allow for fast-turnaround mitigations for hardware or software issues found on-orbit, including patch mitigation.

6. The HITL shall have the capability to verify and validate the USDV functions, including but not limited to: Guidance, Navigation and Control (GNC); simulated and flight-like relative navigation sensors used for ISS rendezvous; navigation sensors used for mated attitude control, mated translational maneuvers;

propulsion controllers; command and data handling functions; and Radio Frequency (RF) communications for all telemetry and command paths.

7. The HITL shall have the capability to connect with MCC-H to provide telemetry and receive commands as per the USDV-to-Ground ICD to perform flight following, and MCC-H to USDV verification and operations testing.

8. The HITL devices shall have the ability to load and execute the actual flight software identically to the actual flight avionics hardware with regard to functionality, timing, and performance.

9. The HITL harnesses, cables and connectors shall be flight-like: lengths, wire-types, production breaks, connector locations, pinouts, and flight configuration.

10. The HITL models and simulations shall be assessed for flight realism in the relevant environment and certified to provide sufficient fidelity to perform verification (Model anchoring) in accordance with Models and Simulations

(DRD USDV-39).

11. The Contractor shall perform and deliver an assessment of the differences between the full list of actual USDV flight hardware and components used in the HITL Test Bed in accordance with Specification for USDV Avionics and Software/Hardware-In-The-Loop (HITL) Test Bed (DRD USDV-46). This assessment shall include Model anchoring, alternate test facilities and their scope, historical performance issues, supplier quality limitations, and exceptions to test-as-you-fly.

b. The Contractor shall develop, transfer, maintain and operate a configuration controlled USDV SDIL Simulator for use in the Houston ISS SDIL, for verification and validation of software requirements, ISS interface software development, certification and sustaining in accordance with Specification for USDV SDIL Simulator for ISS

C-21

Integration Testing (DRD USDV-47) and the following:

1. The USDV SDIL Simulator shall use flight-like hardware for all components needed to meet mission objectives.

2. The USDV SDIL Simulator shall have a complete complement for devices containing flight software (including firmware, programmable logic, and redundant strings) required to communicate with and through ISS, process commands and telemetry, and meet ISS interface requirements in SSP 51101, U.S. Deorbit Vehicle Systems Requirements Document.

3. The USDV SDIL Simulator shall provide a flight like interface with the SDIL test facility in accordance with the ISS SDIL ICD per Specification for USDV SDIL Simulator for ISS Integration Testing (DRD USDV-47).

4. The USDV SDIL Simulator shall have the capability to verify the software loading process, including patch capability through ISS.

5. The USDV SDIL Simulator shall have the capability to perform flight-following of the USDV with ISS as needed to follow on-orbit activities, reproduce and troubleshoot on-orbit issues in the ISS to USDV interface, and allow for fast-turnaround mitigations for hardware or software issues found on-orbit, including patch mitigation.

6. The USDV SDIL Simulator devices shall have the ability to load and execute the actual flight software identically to the actual flight avionics hardware with regard to functionality, timing, and performance.

7. The USDV SDIL Simulator models and simulations shall be assessed for flight realism in the ISS environment and certified to provide sufficient fidelity to perform verification (Model anchoring) and validation, including the ISS/USDV/Ground Segment End to End Test and the ISS integrated software stage test in accordance with Models and Simulations (DRD USDV-39).

8. The Contractor shall perform and deliver an assessment of the differences between the full list of actual USDV flight hardware and components used in the USDV SDIL Simulator in accordance with Specification for USDV SDIL Simulator for ISS Integration Testing (DRD USDV-47). This assessment shall include Model anchoring, alternate test facilities and their scope, historical performance issues, supplier quality limitations, and exceptions to test-as-you-fly.

2.10 SOFTWARE MANAGEMENT

a. The Contractor shall develop, implement, deliver, and operate per a SMP in accordance with Software Management Plan (DRD USDV-24).

b. The Contractor shall establish and deliver the USDV software in accordance with SSP

50482, ISS Software Management Plan and NPR 7150.2, NASA Software Engineering Requirements.

C-22

c. The Contractor shall perform Independent Verification and Validation (IV&V) of safety critical processes and software necessary to complete the USDV mission that include but are not limited to:

1. Functions needed for successful rendezvous and docking (Attitude control and

Translational maneuvers, GNC (including control laws and gains), Relative GNC, and associated support functions)

2. Functions needed for successful deorbit operations (Attitude control and Translational maneuvers, GNC (including control laws and gains), and associated support functions)

d. The Contractor shall provide data for NASA IV&V in accordance with Data Input for NASA Integration and Independent Verification & Validation (IV&V) (DRD USDV- 31).

e. Following CDR, the contractor shall communicate software issues, changes, and status to NASA as defined in the approved USDV Software Management Plan (DRD

USDV-24).

2.11 SAFETY, RELIABILITY, QUALITY AND MISSION ASSURANCE

The Contractor shall perform all safety, reliability, quality and mission assurance functions required to implement the scope of this contract.

2.11.1 SAFETY

a. The Contractor shall develop, implement, deliver, maintain, and operate in compliance with the Safety and Mission Assurance (S&MA) Plan submitted in accordance with Safety & Mission Assurance (S&MA) Plan (DRD USDV-20).

b. The Contractor shall develop, implement, deliver, and maintain a safety assessment in compliance with the Safety Data Package (SDP) in accordance with Safety Data Package (SDP) (DRD USDV-21).

c. The Contractor shall provide analysis for safety critical functions required to meet failure tolerance requirements in accordance with Safety Data Package (SDP) (DRD USDV-21) and SSP, 51101 USDV SRD Section 3.5.

d. The Contractor shall perform and deliver Hazard Analysis (HA) on all systems developed for the USDV mission in accordance with SSP 30599, Safety Review Process, NPR 8715.7, Payload Safety Program, NASA-STD-8719.24, NASA Payload Safety Requirements, and KNPR 8715.3, KSC Safety Procedural Requirements. HAs will be approved by the ISS Safety Review Panel (ISRP) or jointly with Launch Services Program (LSP).

e. The Contractor shall submit for NASA approval any Non-Compliance Reports (NCRs) identified via the HAs. NCRs will be processed in accordance with SSP 30599, Safety Review Process and approved by the appropriate NASA control board(s). For instances where only a single fault tolerant approach to a catastrophic hazard can be met, the Contractor shall provide acceptance rationale focused on the

C-23 reliability of the system and other mitigations. The Contractor shall substantiate acceptance rationale on testing in environments relevant to the USDV mission, margins of safety, flight heritage of components used, number and duration of qualification units tested, testing to failure, life tests, etc.

f. The Contractor shall participate in all safety working groups to support ISRP and LSP activities (i.e., ISRP safety working groups, LSP Payload Safety Working Group, etc.)

as the USDV safety representative with associated subject matter expertise to address issues and concerns.

g. The Contractor shall include all hardware, software, analysis, and support necessary to meet the applicable Range Safety Requirements (e.g., EWR-127-1, Range Safety Requirements, Range User Handbook, AFSPCMAN 91-710, Range Safety User Requirements Manual, or RSM-2002, Range Safety Requirements).

h. The Contractor shall provide data and subject matter expertise to support the development of integrated systems-level hazard assessment performed by the ISS Sustaining Engineering prime contractor.

2.11.2 RELIABILITY

a. The Contractor shall utilize reliability analysis techniques, jointly approved by NASA in accordance with Safety & Mission Assurance (S&MA) Plan (DRD USDV-20) to inform the design of their systems. The Contractor shall deliver the results of these analyses to NASA. The Contractor shall incrementally revise these analyses to reflect the current design and deliver these revisions to NASA.

b. The Contractor shall develop, implement, deliver, and maintain Failure Modes and Effects Analysis (FMEA) and Critical Items List (CIL) and deliver the results in accordance with Safety Data Package (SDP) (DRD USDV-21).

c. The Contractor shall ensure that the reliability analyses are implemented within the engineering design throughout the USDV design lifecycle.

d. The Contractor shall ensure that the critical items defined by the CILs are…