CMC3_SOW_80JSC017C0015.pdf

80JSC017C0015

SECTION C - Cargo Mission Contract Statement of Work (SOW)

Table of Contents

I. FOREWORD

1.0 Management Integration and Control

1.1 Technical Direction

1.2 Applicable Documents

1.3 Cargo Mission Management and Administration

1.3.1 Management Plan

1.3.2 Human Resource Management

1.3.3 Performance Management Reviews (PMRs)

1.3.4 Annual Work Plans

1.3.5 Boards, Panels, and Working Groups

1.3.6 External and Internal Reviews

1.4 Business Management and Administration

1.4.1 Contract Financial System

1.4.2 Contract Work Breakdown Structure

1.5 Configuration and Data Management and Integration

1.5.1 Configuration Status Accounting (CSA) and Verification

1.5.2 Configuration Control/Change Management

1.5.3 Data Management

1.5.3.1 Engineering Release Unit (ERU)

1.5.3.2 Configuration Management Receipt Desk

1.5.3.3 Data Quality Assurance (DQA)

1.6 Information Technology (IT)

1.6.1 IT Management and Security

1.6.2 IT Capital Planning and Investment

1.6.3 Data Sharing

1.6.4 Employee IT Security Awareness and Sensitive Information Training

1.7 Certification of Flight Readiness

1.8 Export Control

1.9 NASA Reimbursable Space Act Agreements

1.10 Government Property

1.11 Security Classification Requirements

2.0 Safety and Mission Assurance/Risk Management (S&MA/RM)

2.1 Management

2.1.1 Mission Assurance and Risk Management Plan

2.1.2 Safety and Health Plan

2.1.3 Quality Assurance Plan

2.2 Risk Management

2.3 Safety

2.3.1 Assessments

2.3.2 Mishap Investigation and Reporting

2.4 Reliability and Maintainability (R&M)

2.4.1 Failure Modes and Effects Analysis/Critical Items List

2.4.2 R&M Allocations, Assessments and Analysis

2.4.3 R&M Source Data

2.5 Quality Assurance

2.5.1 AS9100C

2.5.2 Problem Resolution

2.5.3 Government-Industry Data Exchange Program (GIDEP)

2.5.4 Acceptance Data Packages (ADPs)

3.0 Sustaining Engineering and Maintenance and Operations

3.1 Maintenance and Operations (M&O)

3.1.1 Storage

3.1.2 Inventory Management

3.1.3 Crew Provisioning

3.1.4 Maintenance and Repair

3.1.5 Hardware Processing

3.1.6 M&O Schedules

3.2 Sustaining Engineering

3.2.1 Performance Analysis

3.2.2 Anomaly Resolution

3.2.3 Engineering Drawings/Data

3.2.4 Computer-Aided Design (CAD) Models

3.2.5 Obsolescence Management

3.2.6 Standard Repair Procedures (SRPs)

3.2.7 Sustaining Engineering Schedules

3.2.8 Cargo Integration Certification

3.2.9 Book Coordination

3.2.10 Applications Sustaining

4.0 Pressurized Cargo Integration

4.1 Cargo Mission Planning

4.1.1 Manifest Assessments

4.1.2 Flight Schedules

4.1.3 Visiting Vehicle Integrated Product Team (VVIPT)

4.2 Cargo Planning and Inventory

4.2.1 Cargo Integration Planning

4.2.2 Cargo De-Integration Planning

4.2.3 Inventory Management System (IMS) Bar Code Tracking

4.2.4 IMS Containment Data

4.3 Stowage Integration

4.3.1 Cargo Layouts

4.3.2 Mass Properties Analysis

4.3.3 On-Orbit Operations

4.4 Physical Cargo Processing

4.4.1 Facilities Requirements

4.4.2 Inventory Control

4.4.3 Hardware Verification

4.4.4 Labeling

4.4.5 Cargo Imagery

4.4.6 Foam Services

4.4.7 Water Fill Services

4.4.8 Cargo Packing

4.4.8.1 NASA Kennedy Space Center (KSC) Cargo Packing

4.4.8.2 Hardware Environmental Limits

4.4.8.3 Stowage Provisions

4.4.9 As-Built Data Delivery to Next Level Integrator (NLI)

4.4.10 Hardware Shipment

4.4.11 Return Cargo Processing

4.4.12 Early Destow

4.5 Decals, Placards, and Graphics

4.5.1 Flight and Non-flight Decals, Placards, and Graphics

4.5.2 Product Delivery Schedule

4.5.3 Delivery Report

5.0 Hardware/Software Development, Modification and Recertification

5.1 Design Requirements

5.2 IT Development

5.3 Hardware/Data Deliveries

5.4 Engineering Drawings/Data

5.5 CAD Models

5.6 Safety and Reliability and Maintenance Assessments

5.7 Development Schedules

5.8 ADPs

6.0 Discrete Tasks – To be Authorized

Appendix A, ISS Program Stowage Provision Labeling Guidelines Appendix B, Engineering Release Unit (ERU) Process Flow Appendix C, Stowage Provisions “Pick-List”

I. FOREWORD

The Cargo Mission Contract (CMC) supports the National Aeronautics and Space Administration (NASA) International Space Station (ISS), Orion, Human Landing System (HLS), Gateway and future Exploration Programs by providing analytical and physical processing activities to support cargo requirements and providing sustaining engineering and maintenance and operations for Flight Crew Equipment (FCE). Additionally, the CMC develops and fabricates hardware as required to execute contract scope. Integration with International Partners and Commercial Visiting Vehicles (including Commercial Resupply Services (CRS) and U.S. Crew Vehicle (USCV)) and HLS is required to accomplish the required scope.

The purpose of the ISS is to conduct physical, engineering, and life sciences research for the benefit of life on Earth and to advance exploration of our solar system and enable commerce in Space. NASA’s Orion spacecraft will serve as the exploration vehicle that will carry the crew to space, provide emergency abort capability, sustain the crew during the space travel, and provide safe re-entry from deep space return velocities. The HLS vehicle will serve as an exploration vehicle that will carry crew to and from the lunar surface. The Gateway space station will be an outpost orbiting the Moon that provides vital support for a sustainable, long-term human return to the lunar surface, as well as a staging point for deep space exploration. In order to effectively support, operate and utilize NASA program offices, NASA requires the contractor to:

• Perform analytical integration and physical processing activities to support pressurized cargo requirements including:

– Cargo/Stowage Mission Planning

– Integration with hardware providers and/or launch vehicle providers

– Stowage Integration

– Cargo/Stowage Physical Processing

– International Shipping

– Decal, Placard and Graphic Production

• Perform Maintenance and Operations (M&O) and Sustaining Engineering (SE) functions for the following types of hardware (see definitions in contract Attachment J-1 and hardware list in contract Attachment J-9):

– Pressurized and unpressurized cargo processing and transportation hardware:

including (but not limited to):

– Structural, soft goods, and foam Flight Support Equipment (FSE), etc., such as Extra- Vehicular Activity protective cover/housing, Pump Flow Controller Subassembly FSE (compatible with robotics/EVA, the launch vehicle and on-board interfaces), and Life Science Glovebox launch accommodation hardware and analysis

– FCE: including (but not limited to):

– Crew Clothing and Personal Hygiene Items

– Housekeeping Items

– Audio/Video Equipment and Associated Cabling

– Laptop Computers and Support Equipment

– Batteries

– Supplemental items for ISS systems: including (but not limited to):

– Portable monitoring devices (combustion products, ammonia, gas, etc.)

– Medical crew health equipment

– Portable fire extinguishers

– Data Loggers

– Air Save Pump

– Water, or other liquid transfer bags

– Simple Payload Facilities: including (but not limited to):

– ISS Lockers and drawers

– Animal transporters

– Payload Hardware: including (but not limited to):

– Wearable health monitoring devices

– Tunable diode laser environmental sensing devices

– Virtual reality to human interface hardware

– Payload Support Items: including (but not limited to):

– Disposable syringes

– Wipes

– Bags

– Fuels

– Bogan Arms

– Mounting Hardware

– USB Hubs

– Memory Devices

– Environmental data recorders (accelerometer, temperature, shock, etc.)

– Unique Launch and Return Mission Requirements: including (but not limited to):

– Hardware Mass Simulator

– Shims

• Development of new hardware, modification or recertification of existing hardware, or flight certification of Commercial-off-the Shelf (COTS) hardware, as needed, to support the hardware categories listed above.

The following Statement of Work (SOW) defines the tasks to be performed by the contractor. The contractor shall be responsible for the overall performance of the contract and provide all necessary resources to meet contract requirements. The contractor shall be responsible for all training and certifications required to accomplish contract requirements. All work completed under this contract shall comply with contract requirements.

The SOW is organized as follows:

• Section 1, 2, 3 and 4 are considered “core” tasks which are required on a day-by-day basis to support the NASA Programs and are required to be performed for the entire contract Period of Performance (PoP). Contract changes to core tasks will be implemented via the Changes Clause (contract Section I) or the Underlimit Changes (Clause H.13) and require Contracting Officer (CO) authorization.

• Section 5 is a listing of requirements applicable to hardware or software development/modification or recertification. The specific SOW for these tasks will be listed in SOW Section 6 and/or the Deliverable Items List (DIL).

• Section 6 of the SOW and the DIL are for discrete tasks (clear start and end date with products; not part of core day-to day work covered in SOW Sections 1, 2, 3 and 4) which will implemented via the Underlimit Changes (Clause H.13) or Indefinite Delivery/Indefinite Quantity (IDIQ) Task Orders (Contract Section B and Clause H.3, Task Ordering Procedure) and issued by the CO.

1.0 MANAGEMENT INTEGRATION AND CONTROL

1.1 TECHNICAL DIRECTION

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

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

(1) Constitutes an assignment of additional work outside the Statement of Work;

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

Underlimit Changes (Clause H.13);

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

All technical direction shall be issued in writing by the COR. 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 5 working days after receiving it and shall request the CO to either issue an appropriate contract modification within a reasonable time or advise the contractor in writing within 30 calendar days that the instruction or direction is rescinded in its entirety or 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.

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.

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.

1.2 APPLICABLE DOCUMENTS

The Applicable Document List (ADL) for work performed under this contract is per Contract Section J- 7, which contains the applicable version and dates of documents called out in the SOW, Data Requirement Descriptions (DRDs), and contract clauses. Applicable documents for work authorized via SOW Section 6 or the DIL, shall be the latest revision of the document at the time the work is authorized or per the specific Task Order.

1.3 CARGO MISSION MANAGEMENT AND ADMINISTRATION

The contractor shall conduct management and administration activities to develop and deliver the required products and services as defined within this contract. The contractor shall provide for the planning, organization, control, and reporting of all activities required by this contract to ensure accomplishment of all outcomes and deliverable products required by this contract.

The contractor shall maintain flexibility in performing the contract scope to accommodate multiple and frequent manifest changes resulting from launch delays, requirement changes, anomalies, etc. This includes the need to accelerate hardware and accept late hardware outside nominal template dates.

The contractor shall perform the activities in the most cost-effective and efficient manner while supporting the Government’s priorities for safety, mission success, and customer satisfaction.

1.3.1 MANAGEMENT PLAN

The contractor shall develop, maintain and implement a Cargo Mission Management Plan in accordance with Data Requirements Description (DRD) CMC-PM-01, Cargo Mission Management Plan. The contractor shall describe in the plan the contractor’s management structure that integrates all related plans and systems, including those of major subcontractors and vendors. (Major subcontractor and vendors are defined in DRD CMC-PC-01). The contractor shall address in the plan the contractor’s management of all systems, functions, and data requirements described in this SOW.

1.3.2 HUMAN RESOURCE MANAGEMENT

The contractor shall provide a qualified contractor workforce to implement the scope of this contract. The contractor shall:

• Provide fully trained, qualified, and certified (as required) contractor personnel in sufficient numbers to manage, supervise, and perform the work under this contract per required NASA Program schedules,

• Ensure no mission impacts due to position vacancies or personnel qualifications,

• Preclude staffing that may introduce single point failures,

• Support surge demands in staffing or workloads dictated by mission, operations, or maintenance demands.

1.3.3 PERFORMANCE MANAGEMENT REVIEWS (PMRs)

The contractor shall conduct Performance Management Reviews (PMRs) for the Government and provide monthly PMR products in accordance with DRD CMC-PM-02, Performance Management Review (PMR), for the work performed on this contract. The reviews shall provide the NASA Programs insight into the contractor's, subcontractors’, and vendors' overall technical, schedule, and cost performance for all work performed. Metrics that indicate the level of success in the execution of contract requirements and the status of the contractor’s achievement against the performance standards contained within this SOW or elsewhere in this contract shall be presented at the PMR. The PMR presentations shall depict performance measurement, accomplishments, issues and corrective actions, company financial status (including rates), and all other data necessary to status the NASA Programs.

1.3.4 ANNUAL WORK PLANS

The contractor shall develop annual work plans per DRD CMC-PM-03, Annual Work Plans.

1.3.5 BOARDS, PANELS AND WORKING GROUPS

The contractor shall provide data, analyses and input (including presentations), to provide status to, and support decision making at, the chartered ISS Program Boards, Panels and Working Groups as identified in Space Station Program (SSP) 50200-01, Station Program Implementation Plan (SPIP) Volume 1, Station Program Management Plan (Figure 5.0-1 “ISS Program Control Boards and Panels”). The contractor will also support the decision making at Orion Program Boards, Panels, and Working Groups as identified in MPCV 72008, MPCV Program Plan. The contractor shall perform services that support decision making at the HLS Program Boards, Panels, Forums, and Working Groups as identified in HLS Program Plan, HLS Programs System Requirements Document, and HLS Governement Furnished Property Management Plan. That contractor shall perform services that’s support decision making at the Gateway Program Boards, Panels, and Working Groups.

1.3.6 EXTERNAL AND INTERNAL PROGRAM REVIEWS

The contractor shall develop and deliver briefing materials and analyses for NASA Program presentations and meetings with internal and external review groups. Materials and analyses include but are not limited to, contract technical, cost, and schedule status, specific safety or risk issues, and responses to external inquiries. These groups include, but are not limited to: the Aerospace Safety Advisory Panel (ASAP), Space Flight Advisory Committee (SFAC), Inspector General (IG) and United States (U.S.)

Government Accountability Office (GAO), and Cost Assessments Teams.

1.4 BUSINESS MANAGEMENT AND ADMINISTRATION

The contractor shall provide business management and administration for this contract. The contractor shall perform all business and administrative functions and integrate these functions across all areas of performance. The contractor’s on-going business analysis shall support the NASA Program business’ process.

1.4.1 CONTRACT FINANCIAL SYSTEM

The contractor shall utilize a contract financial system which discretely tracks resources by fund source, contract Work Breakdown Structure (WBS), and elements of cost including labor, overhead, other direct costs (i.e. travel and subcontracts), and indirect costs. The contractor shall provide financial planning to the Government budget process (i.e. Planning, Programming, Budgeting, and Execution [PPBE] budget calls), and special requests for budget impacts. The contractor shall provide financial reporting in accordance with DRD CMC-PC-01, NF533 Monthly Cost Reporting. The contractor shall include financial reporting requirements in any subcontracts for all tiers of subcontracts as defined in DRD CMC-

PC-01.

1.4.2 CONTRACT WORK BREAKDOWN STRUCTURE (WBS)

The contractor shall develop, provide, and maintain a contract WBS Dictionary, in accordance with DRD CMC-PC-02, Work Breakdown Structure (WBS) and Dictionary. The contract WBS shall serve as the framework for contract planning, budgeting, cost reporting, schedule resource loading, and schedule status reporting to NASA. Separate WBS shall be established for each individual program office.

1.5 CONFIGURATION AND DATA MANAGEMENT AND INTEGRATION

The contractor shall develop, implement and administer configuration management operations in accordance with SSP 41170, ISS Program Configuration Management Requirements; SSP 50010, Standards for ISS Program Documentation; and SSP 50123, Configuration Management Handbook. The contractor shall develop and maintain a Configuration Management Plan in accordance with DRD CMC- PC-03, Configuration Management Plan. Additionally, the contractor shall be responsible for contract specific functions as described below:

1.5.1 CONFIGURATION STATUS ACCOUNTING (CSA) AND VERIFICATION

The contractor shall ensure that the application of Configuration Status Accounting requirements and systems results in, and maintains, required Cargo Mission hardware and software product baselines in accordance with SSP 41170.

The contractor shall provide access to accurate and timely information about a product and its configuration information throughout its lifecycle. The data shall be accessible to each respective to support major milestones and flight readiness activities in accordance with SSP 41170.

1.5.2 CONFIGURATION CONTROL/CHANGE MANAGEMENT

The contractor shall develop and/or evaluate and respond to Change Requests (CRs) that impact the Cargo Mission Contract in accordance with SSP 50123. The contractor shall review and evaluate Program changes originating from outside this contract to determine if those changes have potential impacts to this contract, in accordance with SSP 50123. The contractor shall use the electronic Configuration Status Management Operations System (COSMOS) database to process CRs and Change Directives (CDs), assign CR numbers, and track/status changes.

The contractor shall provide timely (per schedule) and quality CDs (or inputs to CDs) with clear, thorough and accurate contract direction (e.g., proposed SOW updates, Deliverable Items List (DIL), Authority to Proceed (ATP) dates, and SOW Evidence of Completion). The contractor shall process CRs that contain a majority of CMC work as the NASA Change Integrator (CI) per SSP 50123.

1.5.3 DATA MANAGEMENT

The contractor shall provide the following Data Management activities specific to this contract, in accordance with SSP 50010 and SSP 41170. The contractor shall:

1.5.3.1 ENGINEERING RELEASE UNIT (ERU)

Provide an Engineering Release Unit to release approved documents, specifications, and other NASA Program-controlled documentation into the NASA Program approved repository per SOW Appendix B, ERU Process Flow.

1.5.3.2 CONFIGURATION MANAGEMENT RECEIPT DESK

Operate a Configuration Management Receipt Desk to process change paper per Appendix B, ERU Process Flow.

1.5.3.3 DATA QUALITY ASSURANCE (DQA)

Provide DQA for all NASA controlled Program documentation developed or sustained under this contract to verify complete and accurate documents for release.

1.6 INFORMATION TECHNOLOGY (IT)

The Mission and Program Integration (MAPI) contractor will provide common IT infrastructure architecture for use by the ISS participants to support the mission of the ISS Program. The contractor may choose to utilize the ISS Program IT infrastructure provided by the MAPI contractor when common products and services provide for increased supportability, promote commonality, or provide cost efficiencies.

Any of the existing ISS Program IT tools provided as Government Furnished Data (GFD) or Government Furnished Property (GFP) are available for utilization by the contractor to fulfill the requirements of this contract. Any modifications to GFD/GFP tools shall be in accordance with NID 7120.99, NASA Information Technology and Institutional Infrastructure Program and Project Management Requirements.

SSP 50013, Information Systems Plan describes the current and the planned capabilities of the ISS Program Information Systems (IS). Additionally, the document describes the ISS Program IS providers and describes the processes by which the ISS Program participants can request services, report problems and identify improvements to the ISS Program IS.6.0.

The contractor shall develop and maintain software tools and applications required to implement the contract scope. All IT development unique to each individual program office Programs shall be subject to the following NASA processes and procedures for application development:

• NASA Procedural Requirements (NPR) 2830.1, NASA Enterprise Architecture Procedures;

• NID 7120.99, NASA Information Technology and Institutional Infrastructure Program and Project Management Requirements;

• NPR 7123.1, NASA Systems Engineering Processes and Requirements;

• NPR 7150.2, NASA Software Engineering Requirements.

Additionally, all unique Program IT development shall be subject to the following NASA Web policies:

• 29 United States Code (U.S.C.) 794d, Section 508 of the Rehabilitation Act of 1973;

• Title 14 of the Code of Federal Regulations (14 CFR), Subpart 1221.1 — NASA Seal, NASA Insignia, NASA Logotype, NASA Program Identifiers, NASA Flags, and the Agency’s Unified Visual Communications System;

• 16 CFR Part 312, Children’s Online Privacy Protection Act;

• National Institute of Standards and Technology Special Publication (NIST-SP)-800-53, Security and Privacy Controls for Federal Information Systems and Organizations;

• 5 U.S.C. 552a, Records Maintained on Individuals;

• NASA Policy Directive (NPD) 2800.1, Managing Information Technology.

• NPR 1382.1, NASA Privacy Procedural Requirements

1.6.1 IT MANAGEMENT AND SECURITY

The contractor shall develop and implement an IT Management Plan per DRD CMC-PC-04, which includes a security plan which describes the policy, processes, and procedures that will be followed to ensure appropriate security of IT resources that are developed, processed, or used under this contract. The IT Management Plan shall that addresses both ground and on-board systems developed and sustained by this contract in accordance with DRD CMC-PC-04 and the following:

• NASA FAR Supplement (NFS) 1852.204-76, Security Requirements for Unclassified IT Resources;

• NPR 2810.1, Security of Information Technology,

• NIST SP-800-18, Guide for Developing Security Plans for Federal Information Systems

The Contractor shall configure and manage the security configuration of existing systems and services per:

• Information Technology Handbook (ITS-HBK)-2810.02-01, Security Assessment and Authorization;

• ITS-HBK-2810.02-04, Security Assessment and Authorization: Continuous Monitoring;

• ITS-HBK-2810.05-01, System and Services Acquisition;

• ITS-HBK-2810.06-01, Security Awareness and Training;

• ITS-HBK-2810.08-01, Contingency Planning;

• ITS-HBK-2810.09-01, Incident Response and Management;

• ITS-HBK-2810.14-01, System and Information Integrity.

The Contractor shall facilitate, provision, and document requests for logical and physical systems access for the systems managed on this contract. Documentation and reporting of access shall be done via the Government-provided NASA Account Management System (NAMS) when possible.

1.6.2 IT CAPITAL PLANNING AND INVESTMENT

The contractor shall develop and implement an IT Capital Investment Process in accordance with SSP 50222, IT Capital Investment Process. All IT delivered by, or directly charged to, this contract shall be subject to IT capital planning processes.

1.6.3 DATA SHARING

The contractor shall implement an architecture that enables bi-directional digital data sharing and web-based access to CMC tools and information and data products with the Government and authorized users of the JSC network domain, including transmission of information across firewalls with the required security access.

1.6.4 EMPLOYEE IT SECURITY AWARENESS AND SENSITIVE INFORMATION

TRAINING Contractor employees performing work under this contract shall annually complete both 1) the NASA- provided IT Security Awareness Training and 2) ISS Program Guidance and Best Practices for Handling Sensitive Data Training. The Contractor shall provide evidence that these training activities have been met for all employees subject to this contract. The Contractor shall submit periodic reports (as required by CO) detailing the overall status of the annual training program. The annual training program is defined as the period from October 1 through September 30. Each of these two training modules are delivered via desktop workstation and each take approximately 1 hour to complete.

1.7 CERTIFICATION OF FLIGHT READINESS

The contractor shall develop, maintain, and implement a Certification of Flight Readiness (CoFR) Plan in accordance with DRD CMC-PM-04, Certification of Flight Readiness (CoFR) Plan, SSP 50108, Certification of Flight Readiness Process Document, and MPCV 72555, Orion Multi-Purpose Crew Vehicle (MPCV) Program Certification of Flight Readiness (CoFR) Implementation Plan. The contractor shall develop and implement an auditable approach to verify and ensure that flight preparation responsibilities and requirements are met and all problems dispositioned in accordance with SSP 50108 and CV 72555.

1.8 EXPORT CONTROL

The contractor shall export hardware, software and data distributed in any format in the execution of contract responsibilities in accordance with NPR 2190.1, NASA Export Control Program. The contractor shall establish export control procedures that are compliant with NASA policy and export regulations, and perform self-audits of their established export control procedures per DRD C-II-01, Export Control Plan (ECP), and SSP 50223, “ISS Export Control Plan” and deliver results of the Export Control Audits per DRD C-II-02, Export Control Audit Results.

The contractor shall identify contacts at Department of Homeland Security/Transportation Security Administration to aid cargo transport through US airports and expedite issue resolution.

1.9 NASA REIMBURSABLE SPACE ACT AGREEMENTS

The contractor shall accomplish all work necessary to accommodate commercial customers to the ISS.

The work will be the same or similar scope already required elsewhere in this contract SOW but may be performed in support of a NASA Reimbursable Space Act Agreement (SAA).

1.10 GOVERNMENT PROPERTY

The contractor shall manage and perform property management for all property acquired as a direct charge to this contract, whether contractor-acquired or Government-provided, in accordance with the Government property clauses identified this contract.

The contractor shall describe the method of administering and controlling Government property per DRD CMC-PR-01, Government Property Management Plan, and shall report on NASA property in the custody of the contractor on both a monthly and annual basis per DRD CMC-PR-02, Financial Reporting of Contractor-Held Property.

1.11 SECURITY CLASSIFICATION REQUIREMENTS (Per Mod 57) (CMC-BNF- 000108)

The Contractor shall obtain National Security Facility Clearance Level (FCL) per Clause I.19, SECURITY CLASSIFICATION REQUIREMENTS up to TOP SECRET and as identified by the Government, obtain TOP SECRET security clearances for personnel supporting functions identified by NASA as requiring these levels of clearance. NASA will sponsor TOP SECRET clearances.

2.0 SAFETY & MISSION ASSURANCE/RISK MANAGEMENT (S&MA/RM)

For hardware sustained within the scope of this contract, the S&MA analyses (e.g., Failure Mode and Effects Analysis (FMEAs), Acceptance Data Packages (ADPs), hazards, etc.) previously developed for this hardware shall be maintained per the requirements within this section of the SOW (Reference Clause H.19, Transitioned Hardware Data Acceptability).

2.1 MANAGEMENT

2.1.1 MISSION ASSURANCE & RISK MANAGEMENT PLAN

The contractor shall develop, maintain, and implement a Mission Assurance & Risk Management (MA&RM) Plan in accordance with NPR 8715.3, NASA General Safety Program Requirements, and DRD CMC-SA-01, Mission Assurance/Risk Management Plan. The plan shall be consistent across all contractor sites.

2.1.2 SAFETY AND HEALTH PLAN

The contractor shall perform tasks to ensure the protection of personnel, property, equipment, and the environment in contractor products and activities generated in support of this contract. To ensure compliance with applicable NASA policies, requirements, federal, state, and local regulations for safety, health, environmental protection, and fire protection, the contractor shall develop and implement a safety and health program per a NASA-approved safety and health plan, in accordance with DRD CMC-SA-02, Safety and Health Plan.

2.1.3 QUALITY ASSURANCE PLAN

The contractor shall develop, implement and maintain a quality assurance plan, as documented in DRD CMC-SA-01, Mission Assurance and Risk Management Plan, and SSP 41173, Space Station Quality Assurance Requirements.

2.2 RISK MANAGEMENT

The contractor shall identify risks and coordinate the abatement or acceptance of these risks in accordance with NPR 8000.4, Agency Risk Management Procedural Requirements and SSP 50175, Risk Management Plan.

2.3 SAFETY

2.3.1 ASSESSMENTS

The contractor shall develop and deliver safety assessments for all packed bags and for all hardware sustained and/or developed on this contract.

Additionally, the contractor shall develop Integrated Bag Level Hazard Assessments (IBLHAs) for cargo launching and returning to:

• Ensure that hardware packed together in a bag does not create any new hazards (i.e., material incompatibility).

• Ensure that all hazards are controlled within the bag (i.e., sharp edges/pinch points, frangible materials, fluid containment).

Additionally, the contractor shall develop a Launch Cargo Hazard Summary for CRS Next Level Integrators (NLIs) for cargo launching to:

• List cargo items with ground transportation hazards

• Include Material Safety Data Sheets (MSDS) and Safety Data Sheets (SDSs) for these cargo items.

• Imagery of hardware and packed imagery for these cargo items.

All assessments shall be developed in accordance with DRD CMC-SA-03, and DRD CMC-SA-03-O (for Orion) Safety Analysis and Hazard Reports, and the following documents:

• SSP 30599, Safety Review Process;

• SSP 30309, Safety Analysis and Risk Assessment Requirements;

• SSP 50021, Safety Requirements Document;

• SSP 51700 Payload Safety Policy and Requirements for the International Space Station.

• MPCV 72094, Orion Multi-Purpose Crew Vehcile (MPCV) Safety and Mission Assurance (S&MA) Plan (guidance only)

• MPCV 70046, Orion Multi-Purpose Crew Vehicle (MPCV) Program Hazard Analysis Requirements

• MPCV 70059, Orion Multi-Purpose Crew Vehcile (MPCV) Program Safety and Mission Assurance (S&MA) Requirements Appendix TBD

2.3.2 MISHAP INVESTIGATION AND REPORTING

The contractor shall investigate and report mishaps, in accordance with NPR 8621.1, NASA Procedural Requirements for Mishap and Close Call Reporting, Investigating, and Recordkeeping.

2.4 RELIABILITY AND MAINTAINABILITY (R&M)

2.4.1 FAILURE MODES & EFFECTS ANALYSIS/CRITICAL ITEMS LIST

The contractor shall develop, maintain and deliver the Failure Modes and Effects Analysis (FMEA) and Critical Items List (CIL) report and worksheets for hardware developed and/or sustained under this contract in accordance with DRD CMC-SA-04, and DRD CMC-SA-04-O (for Orion) Failure Modes and Effects Analysis and Critical Items List.

2.4.2 R&M ALLOCATION, ASSESSMENTS, AND ANALYSIS

The contractor shall develop, and deliver the R&M Allocation, Assessment, and Analysis (AAA) Report in accordance with DRD CMC-SA-05 and DRD CMC-SA-05-O (for Orion), R&M Allocations, Assessments, and Analyses Reports.

2.4.3 R&M SOURCE DATA

The contractor shall develop and, or maintain hardware R&M source data for hardware developed and/or sustained under this contract. Source data updates are required to reflect operational performance. The contractor shall utilize approved reliability block diagrams and data to perform quantitative R&M analyses. The contractor shall submit newly generated or updated source data and analyses to NASA for approval.

2.5 QUALITY ASSURANCE

2.5.1 AS9100C

The contractor shall establish and maintain a Quality Management System (QMS) that complies with the SAE Aerospace Standard AS9100C, Quality Management Systems – Requirements for Aviation, Space and Defense Organizations. The contractor shall obtain AS9100C certification within 18 months of contract start.

2.5.2 PROBLEM RESOLUTION

The contractor shall report, promote and participate in the investigation and resolution of applicable problems in accordance with SSP 41173, Space Station Quality Assurance Requirements, and SSP 30223, International Space Station Problem Reporting and Corrective Action (PRACA) System Requirementsand MPCV 70059 Appendix TBD.

2.5.3 GOVERNMENT-INDUSTRY DATA EXCHANGE PROGRAM (GIDEP)

The contractor shall be a member of, and participate in, the Government-Industry Data Exchange Program (GIDEP) in accordance with S0300-BT-PRO-010, GIDEP Operations Manual and S0300-BU- GYD-010, GIDEP Requirements Guide (available from the GIDEP Operations Center, PO Box 8000, Corona, California 92878-8000) per DRD CMC-SA-06, GIDEP and NASA Advisory Problem Data Sharing and Utilization Program Documentation and Reporting.

The contractor shall review all GIDEP ALERTS, GIDEP SAFE-ALERTS, GIDEP Problem Advisories, GIDEP Agency Action Notices, and NASA Advisories to determine if they affect the contractors products/services provided to NASA. For those that affect the ISS or Orion Programs, the contractor shall take action to eliminate or mitigate any negative effect to an acceptable level. Note: For COTS parts, only parts with an available bill of materials requires a response.

The contractor shall generate the required failure experience data report(s) (GIDEP ALERT, GIDEP SAFE-ALERT, GIDEP Problem Advisory) and enter into the JSC NASA Advisory/GIDEP Documents Status Tracking System, jarts-sma.jsc.nasa.gov, in accordance with NPR 8735.1, “Procedures for Exchanging Parts, Materials, Software, and Safety Problem Data Utilizing the Government-Industry Data Exchange Program (GIDEP) and NASA Advisories”, whenever failed or nonconforming items, available to other buyers, are discovered during the course of the contract.

2.5.4 ACCEPTANCE DATA PACKAGES

The contractor shall maintain hardware Acceptance Data Packages (ADPs) in accordance with SSP 30695, Acceptance Data Package Requirements Packages, MPCV 70059, Appendix TBD, DRD-SA-07, and DRD-SA-07-O (for Orion) Acceptance Data Package (ADP).

3.0 SUSTAINING ENGINEERING & MAINTENANCE AND OPERATIONS

The contractor shall sustain and/or maintain the following categories of hardware (see contract Attachment J- 1, Dictionary):

– Flight Crew Equipment (FCE)

– Pressurized and unpressurized cargo transport hardware, as specified in Attachment

J-9 (generally limited to hardware designed and/or built under this contract)

– Simple Payload Facilities

– Payload Hardware

– Payload Support Items

– Supplemental items for ISS Systems

– Hardware required to satisfy Unique Launch and Return Mission Requirements

– Ground Support Equipment (generally limited to hardware designed and/or built under this contract)

– Sustaining items for Orion (CMC-BNF-000130)

Specific hardware to be sustained and maintained is listed in contract Attachment J-9, “Hardware List”.

NASA will retain overall SE responsibility for hardware not required to be sustained under this contract.

NASA will retain System Management oversight for the hardware for which the contractor has SE responsibility.

For hardware sustained within the scope of this contract, the data previously developed for this hardware shall be maintained per the requirements within this section of the SOW (Reference Clause H.19, Transitioned Hardware Data Acceptability).

3.1 MAINTENANCE AND OPERATIONS (M&O)

The contractor shall acquire, warehouse, issue, track, maintain, and process all hardware identified in Attachment J-9, ”Hardware List”, to ensure availability for flight and training requirements.

3.1.1 STORAGE

The contractor shall provide and operate a total storage function, including controlled facilities, to implement the tasks associated with this SOW. The contractor shall receive, verify, and issue flight and non-flight property into a contractor provided and operated storage facility. The contractor shall segregate property in storage by flight or non-flight classification and as serviceable or non-serviceable.

The contractor shall control perishable, shelf-life, and limited-life equipment.

3.1.2 INVENTORY MANAGEMENT

The contractor shall develop, implement, and maintain an automated inventory control system and workflow tool for all contractor-held Government property.

The contractor shall define and maintain ground inventory levels required to support ISS and Orion flight and training requirements. For crew provisioning ground inventory, the contractor will utilize inputs from NASA. To maintain inventories, the contractor shall acquire and/or fabricate parts, materials, and replacement units.

The contractor shall maintain a current inventory of all non-consumable hardware by location with location identified as “on ISS”, “on a space transportation vehicle (and identify the transportation vehicle)”, “disposed of”, “on Orion”, or “on the ground”. For items identified as “on the ground” the contractor shall identify the location and status, i.e. “warehouse”, “shipped to training facility”, “under repair”, or “staged at launch site for contingency use”.

3.1.3 CREW PROVISIONING

The contractor shall perform Crew Provisioning Fit Checks/Reviews and participate in the Crew Provisioning Working Group as defined in SSP 50409, Crew Provisioning Management Plan. The contractor shall procure/prepare the type and quantity of crew clothing, hygiene, and personal item requirements to be flown as determined by the Crew Provisioning Working Group (CPWG) (reference SSP 50477, Joint Crew Provisioning Catalog). This includes the necessary Crew Preference apparel for ground training and public affairs events for ISS Increment crews and Orion crews.

3.1.4 MAINTENANCE AND REPAIR

The contractor shall maintain, repair, and test the hardware identified in Attachment J-9, “Hardware List” to maintain the required inventory to support ISS and Orion missions (reference SSP 50276, Depot/Manufacturing Facility Certification Plan). The contractor shall update required technical documentation including ADPs to maintain a record of the hardware’s history.

3.1.5 HARDWARE PROCESSING

The contractor shall perform processing required to make the hardware identified in Attachment J-9, ”Hardware List”, ready for flight or training per ISS and Orion Program schedules. The contractor shall update required technical documentation, including ADPs, to maintain a record of the hardware’s history.

3.1.6 M&O SCHEDULES

The contractor shall prepare and deliver schedules for all maintenance, repair, and processing activities to provide the Government with insight into overall project status in accordance in with DRD CMC- PM-02, Performance Management Review Products.

3.2 SUSTAINING ENGINEERING

3.2.1 PERFORMANCE ANALYSIS

The contractor shall monitor, analyze, and document hardware reliability and performance to determine actual versus expected performance, anomalous behavior, and required updates to repair, maintenance plans, check out plans, and operational procedures for hardware sustained on this contract. The contractor shall perform an analysis of the use, maintenance (preventive and corrective), replacement, and anomalies associated with the hardware to be used in inventory management for all the equipment for which the contractor has accountability.

3.2.2 ANOMALY RESOLUTION

The contractor shall identify, investigate, resolve, and document flight and ground hardware anomalies for all hardware sustained by this contract in support of the NASA Program’s anomaly resolution processes. Applicable anomalies shall be documented per SOW paragraph 2.5.2, PROBLEM RESOLUTION. The contractor shall conduct anomaly resolution in accordance with MPCV 70059, Appendix TBD and MGT-OA-019, On-Orbit Anomaly Resolution Process Work Instruction.

3.2.3 ENGINEERING DRAWINGS/DATA

The contractor shall maintain drawings for hardware sustained on this contract in accordance with DRD CMC-EN-01 and DRD CMC-EN-01-O (for Orion), , Engineering Drawings and Associated Lists and shall maintain engineering data on hardware sustained per DRD CMC-EN-02, ISS Vehicle Engineering Data.

Note: Some of the drawings associated with GFP are currently stored in the NASA JSC Engineering Drawing Control Center (EDCC). All drawing releases to the VMDB shall be made per DRD CMC-EN- 01 and DRD CMC-EN-01-O (for Orion), .

3.2.4 COMPUTER-AIDED DESIGN (CAD) MODELS

The contractor shall provide CAD models for all hardware sustained on this contract in accordance with DRD CMC-EN-03 and DRD CMC-EN-03-O (for Orion if required), Cargo Integration Cargo CAD Models for Launch, Return and On-orbit Configurations.

3.2.5 OBSOLESCENCE MANAGEMENT

The contractor shall perform obsolescence management for repair parts and COTS end items for hardware sustained on this contract, in order to ensure hardware is available to support maintenance or manufacturing activities. In the event that original materials and/or parts are no longer available, or desirable, the contractor shall notify NASA, certify new sources, and update engineering products per ISS Program processes. The contractor is authorized to make changes to drawings on Flight Crew Equipment without processing Program Change Paper for the following criteria:

A. The contractor has determined a proposed change will have no impact on the form, fit, or function of the end item’s design and no impact on the allocated or functional performance requirements.

Such changes may include: obsolete part replacement, make operable manufacturing changes, part supplier changes, and changes from proprietary specifications to equivalent industry standards.

B. The change has been coordinated with the appropriate NASA System/Subsystem Problem Resolution Team (SPRT) and NASA project engineer responsible for the affected hardware.

C. The contractor has ensured post-modification product functional equivalency will be maintained and the end item part number and/or dash number will not be affected. If necessary, NASA Configuration Management, with input from the contractor and appropriate SPRT, will determine that a planned change will not require a new part number.

If the contractor determines that an individual change does not meet one of the criteria above, or the contractor determines the individual change requires International Space Station (ISS) Program review, the standard ISS Class I Change implementation process shall be followed.

3.2.6 STANDARD REPAIR PROCEDURES (SRPS)

The contractor shall generate, review and approve SRPs for hardware within the sustaining engineering responsibility of this contract to expedite hardware repair when an SRP does not already exist for items that need frequent repair.

3.2.7 SUSTAINING ENGINEERING SCHEDULES

The contractor shall prepare and deliver schedules for Sustaining Engineering activities to provide the Government with insight into overall project status in accordance with DRD CMC-PM-02, Performance Management Review Products.

3.2.8 CARGO INTEGRATION CERTIFICATION

The contractor shall perform the Hardware Provider function as described in SSP 50835, ISS Pressurized Volume Hardware Common Interface Requirements Document (CIRD), for items sustained per J-9, Hardware and Software List.

3.2.9 BOOK COORDINATION

The contractor shall book coordinate, as defined in Contract Attachment J-1: “Dictionary”, the following program process and requirement documents:

• SSP 50007, Space Station Inventory Management System Label Specification;

• SSP 50200-11, SPIP, Volume 11: Cargo Integration Processes;

• JSC 64192, Requirements Verification Matrix for the Automated External Defibrillator

(AED);

• JSC 64267, ISS Think Pad T61pTM Laptop Hardware Interface Requirements Document;

• JSC 64268, ISS Think Pad T61pTM Laptop Hardware Project Technical Requirements

Specification;

• JSC 64270, ISS Think Pad T61pTM Laptop Computer Verification and Validation

Document (V&VD);

• JSC 64278, Pre-Delivery/Pre-Installation Acceptance Test Procedures for the Crew Health

Care System (CHeCS) Automated External Defibrillator (AED).

• CMC2-00471, ICWC to Commercial Orbital Transportation Services Visiting Vehicles

(VV) (Cygnus and Dragon) Interface Requirements Document (IRD).

• SSP 50849, MIDAS to JAXA HTV Cargo Integration System Interface Control Document

(ICD).

3.2.10 ISS APPLICATIONS SUSTAINING (CR 16504)

The contractor shall maintain the following Government provided (reference contract Attachment J-10, Table 2) software applications and associated data to provide the most current processes, procedures and data:

• eLRODS - Electronic Launch, Return and On-Orbit Data Set (eLRODS) is the mechanism for hardware providers to provide the NASA ISS and Orion cargo processing or cargo integration community a standard set of requirements to pack, handle, transport, and stow pressurized hardware launched to and returned from ISS and Orion. eLRODS are required for all launch and return United States Orbital Segment (USOS) and Orion hardware, as well as any Russian Segment hardware launching or returning on USOS Visiting Vehicles.

• eLabel - eLabel is a consolidated application to facilitate hardware providers’ coordination with (and approval from) multiple disciplines necessary for spaceflight hardware labels.

• eRMDP - eRMDP is an application to consolidate and automate acquisition of flight specific RMDP data from hardware providers.

The contractor shall sustain through September 30, 2024 any update made to the eLabel suite of tools based on changes required to meet Spiral 4 requirements.

The contractor shall sustain through September 30, 2024 the Label Picker application based on initial release of Label Picker and any change required to meet Spiral 4 requirements.

The contractor shall sustain through September 30, 2024 any update made to the Orion Stowage Assessment Tool application based on changes required to meet the initial infrastructure requirements.

The contractor shall sustain through September 30, 2024, any update made to the eLabel suite of tools based on changes required to meet RFID required changes.

3.3 Engineering Services

3.3.1 Support for ISS Vehicle Office Tasks

3.3.2 (CMC-BNF-136)

3.3.3 Fatigue life sustaining support for lockers (CMC-BNF-000183)

3.3.4 Exploration ECLS Support (CMC-BNF-000263)

3.3.5 Bag and Locker re-assessments (CMC-BNF-283)

3.3.6 EHP Scheduler Support (CMC-BNF-000312)

3.3.7 Rodent Research Hardware Development (CMC-BNF-000324) and Sustaining Support

(CMC-BNF-000325)

•Build to Print of Rodent Research Hardware

•Perform tasking necessary to clean, refurbish, retrofit, and repair Habitats and Transporters, including Ground Transporters

•Perform required mission support, verification, safety, and documentation tasks to support mission hardware deployment for both ground and flight research purposes

3.3.8 Logistical Support for ISS Vehicle (CMC-BNF-000360)

The contractor shall:

• Manage logistics resources such that hardware availability aligns with the overall risk posture of the Program as a whole and evaluates/evolves associated policies and strategies accordingly

• Interface with stakeholders and hardware providers, as necessary, to ensure that the ISS Program is employing a sound integrated logistics…