Draft SOW_80JSC023CMC4.pdf

80JSC023CMC4 Draft SOW

Cargo Mission Contract 4 Draft Statement of Work (SOW)

Table of Contents Cargo Mission Contract 4 Draft Statement of Work (SOW)

1.0 MANAGEMENT INTEGRATION AND CONTROL

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

3.0 SUSTAINING ENGINEERING & MAINTENANCE AND OPERATIONS

4.0 SYSTEMS ENGINEERIGN AND INTEGRATION

5.0 PRESSURIZED CARGO INTEGRATION

6.0 HARDWARE/SOFTWARE DEVELOPMENT, MODIFICATION AND RECERTIFICATION 41

7.0 DISCRETE TASKS

Appendix A. ISS PROGRAM STOWAGE PROVISION LABELING GUIDELINES

Appendix B. STOWAGE PROVISION “PICK-LIST”

FOREWORD

The Cargo Mission Contract (CMC) supports the National Aeronautics and Space Administration (NASA) International Space Station (ISS) Program; Artemis missions which are supported by the Orion, Human Landing System (HLS), and Gateway Programs; the EVA and Human Surface Mobility Program (EHP); as well as future Exploration efforts by providing analytical and physical processing activities to support cargo requirements and providing sustaining engineering, maintenance and operations for Flight Crew Equipment (FCE). CMC also develops, fabricates and certifies hardware as required to execute contract scope. Integration with International Partners and Commercial Visiting Vehicles (including Soyuz, Progress, HTV-X), Commercial Resupply Services (CRS), U.S. Crew Vehicle (USCV), and the Gateway Logistics Module) as well as the Orion Multi-Purpose Crew Vehicle (MPCV) 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 that the contractor shall:

• 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: 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

• Develop new hardware, modify, or recertify existing hardware or Commercial-off-the Shelf (COTS) hardware, as needed and to the applicable environment, to support the hardware categories listed above.

The following draft 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 by the contractor under this contract shall comply with contract requirements.

The SOW is organized as follows:

• Section 1, 2, 3. 4, and 5 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 require Contracting Officer (CO) authorization.

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

• Section 7 of the SOW and the DIL are for discrete tasks with a clear start and end date with products; are not part of core day-to day work covered in SOW Sections 1, 2, 3, 4 and 5; are executed per the CMC Buy and Fly (BNF) Process; implemented via the Underlimit Changes (Clause TBD), Indefinite Delivery/Indefinite Quantity (IDIQ), or Task Order; and authorized 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 TBD);

(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 cited in the SOW, Data Requirement Descriptions (DRDs), and contract clauses.

Applicable documents for work authorized via SOW Section 6 or the DIL, will 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) TBD, 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 TBD).

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 contractor workforce to implement the scope of this contract.

To accomplish this, 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 i]n 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 TBD, Performance Management Review (PMR), for the work performed on this contract.

At a PMR, the contractor shall provide each NASA Program insight into their scope of interest for the contractor's, subcontractors’, and vendors' overall technical, schedule, and cost performance for all work performed.

At a PMR, the contractor shall present 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.

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 TBD, Annual Work Plans.

1.3.5 BOARDS, PANELS AND WORKING GROUPS

The contractor shall provide and present briefing material, data, analyses and technical input for status and to support decision making at the various NASA Program reviews, control boards, panels, forums, working groups, and Technical Interchange Meetings (TIM), including but not limited to:

• Chartered ISS Program Boards, Panels and Working Groups are 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”).

• Orion Program Boards, Panels, and Working Groups are identified in MPCV 72008, MPCV Program Plan.

• HLS Program Boards, Panels, and working groups are identified in TBD.

• Gateway Program Boards, Panels, and working groups are identified in TBD.

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. The contractor’s materials and analyses shall include but are not limited to, contract technical, cost, and schedule status, specific safety or risk issues, and responses to external inquiries. These external inquiries may come from 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 TBD, NF533 Monthly Cost Reporting.

The contractor shall include financial reporting requirements in any subcontracts for all tiers of subcontracts as defined in DRD TBD.

1.4.2 CONTRACT WORK BREAKDOWN STRUCTURE (WBS)

The contractor shall develop, provide, and maintain a contract WBS Dictionary, in accordance with DRD TBD, 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.

The contractor shall establish separate WBS for each individual NASA program office.

1.5 CONFIGURATION AND DATA MANAGEMENT AND INTEGRATION

The contractor shall develop, implement and administer configuration management operations as outlined in the contractor’s Configuration Management Plan, as specified in this contract, and in accordance with the applicable NASA Program documentation below,

• SSP 41170, ISS Program Configuration Management Requirements; SSP 50010, Standards for ISS Program Documentation; and SSP 50123, Configuration Management Handbook.

• MPCV 72523 Orion Multi-Purpose Crew Vehicle (MPCV) Configuration and Data Management (CDM) Plan CDM

• HLS TBD

• Gateway TBD

The contractor shall develop and maintain a Configuration Management Plan in accordance with DRD TBD, Configuration Management Plan.

Additional responsibilities 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 Contract hardware and software product baselines in accordance with the applicable NASA Program documentation below,

• SSP 41170, ISS Program Configuration Management Requirements and SSP 50123, Configuration Management Handbook.

• MPCV 72523 Orion Multi-Purpose Crew Vehicle (MPCV) Configuration and Data Management (CDM) Plan CDM

• HLS TBD

• Gateway TBD

The contractor shall participate in audits of compliance with CM requirements and processes and provide access to accurate and timely information about a product and its configuration information throughout its lifecycle.

The product and configuration data shall be accessible to each respective NASA Program to support major milestones and flight readiness activities as dictated by each NASA Program.

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 the applicable NASA Program documentation below,

• SSP 41170, ISS Program Configuration Management Requirements and SSP 50123, Configuration Management Handbook.

• MPCV 72523 Orion Multi-Purpose Crew Vehicle (MPCV) Configuration and Data Management (CDM) Plan CDM

• HLS TBD

• Gateway TBD

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 applicable NASA Program documentation in this section.

The contractor shall use the electronic configuration management systems applicable to each NASA Program (ex. The ISS 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 Cargo Mission Contract work as the NASA Change Integrator (CI) per applicable NASA Program documentation in this section.

1.5.3 DATA MANAGEMENT

The contractor shall provide the following Data Management activities specific to this contract, in accordance with the applicable NASA Program documentation below,

• SSP 50010 - Standards for ISS Program Documentation, SSP 41170 - ISS Program Configuration Management Requirements, and SSP 50123 - Configuration Management Handbook.

• MPCV TBD

• HLS TBD

• Gateway TBD

1.5.3.1 ENGINEERING RELEASE UNIT (ERU)

The contractor shall provide an Engineering Release Unit to release approved documents, specifications, and other NASA Program-controlled documentation into the NASA Program approved repository per SSP 41170 and SSP 50123.

1.5.3.2 CONFIGURATION MANAGEMENT RECEIPT DESK

The contractor shall operate a Configuration Management Receipt Desk to process change paper per SSP 41170 and SSP 50123.

1.5.3.3 DATA QUALITY ASSURANCE (DQA)

The contractor shall 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 Human Space Flight Technical Integration Contract (HSFTIC) 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 HSFTIC 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 NPR 7120.7, NASA Information Technology 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.

• MPCV TBD

• HLS TBD

• Gateway TBD

The contractor shall develop and maintain software tools and applications required to implement the contract scope.

The contractor shall ensure redundancy and availability of software tools and applications needed to implement the contract scope.

All IT development unique to each individual NASA Program office shall be subject to the following NASA processes and procedures for application development:

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

• NPR 7120.7, NASA Information Technology 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;

• Revised Section 508 of the Rehabilitation Act Standards, 36 C.F.R. § 1194.1 & Apps. A, C &

D

• 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 TBD, 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 contractor’s IT Management Plan shall address the needs for both ground and on-board systems developed and sustained by this contract in accordance with DRD TBD 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:

Assessment & Authorization Document Identifier Document Title ITS-HBK-AASTEP0.v1.0.0 Step 0: Prepare Policy ITS-HBK-AASTEP1.v1.0.0 Step 1: Categorize Policy ITS-HBK-AASTEP2.v1.0.0 Step 2: Select Policy ITS-HBK-AASTEP3.v.1.0.0 Step 3: Implement Policy ITS-HBK-AASTEP4.v1.0.0 Step 4: Assess Policy ITS-HBK-AASTEP5.v1.0.0 Step 5: Authorize Policy ITS-HBK-AASTEP6.v.1.0.0 Step 6: Monitor Policy Combined Step Handbooks (Not authoritative source) ITS-HBK-2810.15-01A Access Control ITS-HBK-2810.16-02B Audit and Accountability ITS-HBK-2810.07-02B Configuration Management ITS-HBK-2810.08-01A Contingency Planning

ITS-HBK-2810.06-2B Cybersecurity and Privacy Awareness, Training, and Education

ITS-HBK-2810.17-02B Identification and Authentication ITS-HBK-2810.10-02C Maintenance ITS-HBK-2810.11-2C Media Protection and Sanitization ITS-HBK-2810.13-01B Personnel Security ITS-HBK-2810.12-02B Physical and Environmental Protection ITS-HBK-2810.03-02B Planning ITS-HBK-2810.18-02B System and Communications Protection ITS-HBK-2810.14-03D System and Information Integrity – System and Info

Integrity ITS-HBK-2810.05-2B System and Service Acquisition

The following A&A Role View documents are companion documents to the Assessment & Authorization process.

A&A Role View documents Document Identifier Document Title AA-Role-AODR Authorizing Official Designated Representative Summary AA-Role-AO Authorizing Official Summary AA-Role-CISO Center Chief Information Security Officer Summary AA-Role-CCRM Center Cybersecurity Risk Manager Summary AA-Role-CPM Center Privacy Manager Summary AA-Role-ISO Information System Owner Summary AA-Role-ISSE Information System Security Engineer Summary AA-Role-ISSO Information System Security Officer Summary AA-Role-SCA Security Control Assessor Summary Controlled Unclassified Information (CUI) Document Identifier Document Title ITS-HBK-CUI_v2.0.0 Controlled Unclassified Information Handbook Identity Credential and Access Management (ICAM) Document Identifier Document Title IT-HBK-2841-03A Identity, Credential, and Access Management (ICAM)

Services Incident Management and Response Document Identifier Document Title ITS-HBK-2810.09-03A Collection of Electronic Data (CUI) ITS-HBK-2810.09-01 Incident Response and Management ITS-HBK-2810.09-04 Incident Response and Management: Guidelines for Data

Spillage and Sanitization Procedures ITS-HBK-2810.09-02A NASA Information Security Incident Management (CUI)

Operational Technology Document Identifier Document Title ITS-HBK-2810.19-01 Operational Technology Privacy Document Identifier Document Title ITS-HBK-1382.03-01 Privacy – Collections, PTAs, and PIAs ITS-HBK-1382.08-01 Privacy Accountability ITS-HBK-1382.04-01 Privacy and Cybersecurity: Supporting and Integrated

Controls Framework ITS-HBK-1382.03-02 Privacy Annual Reporting Procedures: Reviewing and

Reducing PII and Unnecessary Use of SSN ITS-HBK-1382.07-01 Privacy Awareness and Training ITS-HBK-1382.05-01 Privacy Incident Response and Management: Breach

Response Team Checklist ITS-HBK-1382.06-01 Privacy Notice and Redress — Web Privacy and Written

Notice, Complaints, Access, and Redress ITS-HBK-1382.09-01 Privacy Rules of Behavior and Consequences Records Management Document Identifier Document Title IT-HBK-1440.01-01 Records Management Program and Records Life Cycle:

Chapter 1 — Overview IT-HBK-1441.01-01 Records Retention and Disposition: Chapter 1 — Overview Supply Chain Risk Management Document Identifier Document Title ITS-HBK-SCRM.v1.2.4 Information & Communications Technology Supply Chain

Risk Management (ICT SCRM) Vulnerability Management Document Identifier Document Title ITS-HBK-2810.15-02A Access Control: Managed Elevated Privileges (CUI) ITS-HBK-2810.04-01A-1 Risk Assessment, Vulnerability Scanning, and Expedited

Patching

The contractor shall facilitate, provision, and document requests for logical and physical systems access for the systems managed on this contract.

The contractor’s documentation and reporting of access requests and provisioning 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 the applicable NASA Program documentation below,

• SSP 50222, IT Capital Investment Process.

• MPCV TBD

• HLS TBD

• Gateway TBD

The contractor shall ensure that all IT delivered by, or directly charged to, be subject to IT capital planning processes.

The contractor shall ensure all products and vendors are approved through the OCIO's standard approval process.

This includes, but is not limited to,

• FITARA, Supply Chain Risk Management,

• IPv6,

• 508 compliance.

No purchase of commercial IT should be made prior to approval.

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 NDC 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 the following,

1) NASA- provided IT Security Awareness Training, and

2) ISS Program Guidance and Best Practices for Handling Sensitive Data Training.

3) MPCV TBD

4) HLS TBD

5) Gateway TBD

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 TBD, Certification of Flight Readiness (CoFR) Plan and the applicable NASA Program documentation below,

• SSP 50108, Certification of Flight Readiness Process Document

• MPCV 72555, Orion Multi-Purpose Crew Vehicle (MPCV) Program Certification of Flight

Readiness (CoFR) Implementation Plan.

• HLS TBD

• Gateway TBD

• JSC-28222, EVA Office Certification of Flight & EVA Readiness Requirements and

Implementation Plan (As applicable)

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 the applicable NASA Program documentation noted in this section.

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 TBD, Export Control Plan (ECP), and deliver results of the Export Control Audits per DRD C-II-02, Export Control Audit Results, as well as in accordance with the applicable TBD NASA Program documentation.

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 TBD, Government Property Management Plan.

The contractor shall report on NASA property in the custody of the contractor on both a monthly and annual basis per DRD TBD, Financial Reporting of Contractor-Held Property.

1.11 SECURITY CLASSIFICATION REQUIREMENTS

The contractor shall obtain National Security Facility Clearance Level (FCL) per Clause TBD, 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 by the contractor per the requirements within this section of the SOW (Reference Clause TBD, 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 TBD, Mission Assurance/Risk Management Plan.

The contractor developed MA&RM plan shall be consistent across all contractor sites and NASA Centers.

2.1.2 SAFETY AND HEALTH

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.

The contractor shall develop and implement a safety and health program and provide safety and health information, per a NASA-approved safety and health plan, in accordance with DRD TBD, Safety and Health Plan, in order to ensure compliance with applicable NASA policies, requirements, federal, state, and local regulations for safety, health, environmental protection, and fire protection. When on NASA property, contractor personnel shall follow the safety and health requirements of the local Center.

2.1.3 QUALITY ASSURANCE PLAN

The contractor shall develop, implement and maintain a quality assurance plan, as documented in DRD TBD, Mission Assurance and Risk Management Plan, and in accordance with the applicable TBD NASA Program documentation.

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 in accordance with the applicable TBD NASA Program documentation.

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.

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

The contractor shall develop a Launch Cargo Hazard Summary and deliver it to the Vehicle Provider Next Level Integrators (NLIs) 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 contractor assessments shall be developed in accordance with DRD TBD, Safety Analysis and Hazard Reports, and in accordance with the applicable TBD NASA Program documentation.

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

When necessary, the contractor shall update source data 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 AS9100D

The contractor shall establish and maintain a Quality Management System (QMS) that complies with the SAE Aerospace Standard AS9100D, Quality Management Systems – Requirements for Aviation, Space and Defense Organizations.

The contractor shall obtain AS9100D 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 the applicable TBD NASA Program documentation.

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 TBD, 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 any GIDEP notice that affect a NASA Programs within the scope of the Cargo Mission Contract, , 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 shall require a contractor 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) per DRD TBD, Acceptance Data Package (ADP) and in accordance with the applicable TBD NASA Program.

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

• Sustaining items for HLS

• Sustaining items for Gateway

• Sustaining items for EHP

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 contractor shall maintain the data previously developed for this hardware per the requirements within this section of the SOW (Reference Clause TBD, 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 .

The contractor shall define and maintain ground inventory levels required to support ISS, Orion, HLS, and Gateway flights 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”,

• “on HLS”

• “on Gateway” 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 panels and Crew Provisioning Working Groups as defined by the applicable TBD NASA Program documentation.

The contractor shall procure/prepare the type and quantity of crew clothing, hygiene, and personal item requirements to be flown as determined by each of the NASA Programs (reference SSP 50477, Joint Crew Provisioning Catalog), including but not limited to 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 NASA’s ISS and Artemis 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, Orion, HLS, and Gateway 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 with DRD TBD, 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.

The contractor shall document applicable anomalies per SOW paragraph 2.5.2, PROBLEM

RESOLUTION.

The contractor shall conduct anomaly resolution in accordance with the applicable TBD NASA Program documentation.

3.2.3 ENGINEERING DRAWINGS/DATA

The contractor shall maintain drawings for hardware sustained on this contract in accordance with DRD TBD, Engineering Drawings & Associated Lists.

For Engineering Drawings and Associated Lists, the contractor shall maintain engineering data on hardware sustained per DRD TBD, Vehicle Engineering Data.

For any released drawing transmitted to the VMDB, the contractor shall follow DRD TBD, Engineering Drawings & Associated Lists.

Note: Some of the drawings associated with GFP are currently stored in the NASA JSC Engineering Drawing Control Center (EDCC).

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 TBD, 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 and shall 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 team 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 NASA System/Subsystem team, 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 Program Board review, then, the contractor shall follow the applicable NASA Program Class I Change implementation process.

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 TBD, Performance Management Review Products.

3.2.8 CARGO INTEGRATION CERTIFICATION

The contractor shall perform the Hardware Provider function for items sustained per J-9, Hardware and Software List, in accordance with the applicable TBD NASA Program documentation.

3.2.9 BOOK COORDINATION

The contractor shall provide a book coordinator function, as defined in Contract Attachment J-1:

“Dictionary”, for 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).

• MPCV TBD

• HLS TBD

• Gateway TBD

3.2.10 SOFTWARE APPLICATIONS SUSTAINING

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 - Electronic Return Manifest Disposition Plan (eRMDP) is an application to consolidate and automate acquisition of flight specific RMDP…