Attachment_A_-_Statement_of_Work_for_FF.docx

Statement of Work National Aeronautics and September 23, 2019 Space Administration

Johnson Space Center Houston, Texas

Next Space Technologies for Exploration Partnerships-2 (NextSTEP-2)

Broad Agency Announcement NNH16ZCQ001K-CDFF

Appendix K: Commercial Destination Development in Low Earth Orbit (LEO) Free Flyer

Attachment A Statement of Work

STATEMENT OF WORK

Contents

NextSTEP-2 BAA, Appendix K: Commercial Destination Development in Low Earth Orbit (LEO) Free Flyer – Attachment A

FF SOW ii

INTRODUCTION

Overview and Objectives The purpose of this contract is to enable the development of a Commercial Destination in Low Earth Orbit (LEO) Free Flyer (hereafter identified as FF). The primary objectives to be accomplished are:

1. Successfully deploy one or more habitable commercial elements in LEO and demonstrate the ability to provide products and services to a market of Government and commercial customers.

2. Transition to a long-term, sustainable, commercial, human spaceflight enterprise in LEO where NASA is one of many customers.

This Statement of Work (SOW) requires the Contractor to develop, launch, and operate a FF to conduct demonstrations of capabilities and services as a self-sustaining Commercial Destination in LEO. The Contractor will provide data deliverables and insight to demonstrate habitability, attitude control, orbit maintenance, accommodations for Visiting Vehicles (VV) to dock, sustainability, and research and technology development capabilities on the FF. This includes providing deliverables that establish the verification requirements, and providing the Government with appropriate insight into the development of the FF and the maturation of the contractor’s business plan for operation of a Commercial Destination. Purchase of services during the commercial operations phase are not within scope of this SOW.

This SOW, including all references herein, describes the requirements for the Contractor to accomplish the Milestones, establish and meet safety requirements, deliver a FF to LEO, activate and checkout the FF, and perform spaceflight demonstrations including but not limited to attitude control, orbit maintenance, and demonstration of capabilities and services.

The use of the words “will”, “should” and “shall” are as defined:

Shall – Requirement: is used to indicate a requirement, meaning it must be implemented, and evidence of implementation must be provided.

Will – Fact: is used to indicate a statement of fact, declaration of purpose, or expected occurrence.

Should – Expectation: denotes a statement of best practice or intent.

Definitions Commercial Element – any individual habitable module, external platform, or deployable structure, owned and operated by a U.S. Industry Entity to accommodate on-orbit activities.

Commercial Destination Free Flyer (herein referred to as FF) – permanently human-occupied or human-tended non-governmental platform in LEO, consisting of the sum of all Commercial Elements of the contractor, and all commercial business operations that are required to sustain the FF. At least one element shall be a habitable module.

Commercial Demonstration – conducting Commercial Destination Free Flyer demonstrations for a finite time to validate the proposed capabilities to enable:

1. Reliable performance of habitation capabilities

2. Spaceflight demonstration of attitude control and orbit maintenance capability

3. Supply and return of consumables and products

4. Crewed missions that exercise the contractor’s Business Approach

5. Proposed services targeting NASA’s needs as a customer

6. Proposed services targeting the contractor’s commercial market(s) Commercial Destination Free Flyer Crew – any Crew member who is approved for flight to the FF beginning upon assignment of the crew for a specific government or commercial mission and ending upon completion of the post-flight activities.

United States Government (USG) Astronaut - an individual who meets the definition of “government astronaut” under 51 USC 50902 (4)(A), (B), and (C)(i), which means an individual who is an employee of the U.S. Government, including the uniformed services, engaged in the performance of a federal function under authority of law or an Executive act and designated as a government astronaut by NASA in accordance with applicable NASA requirements.

Commercial Contractor Astronaut – a Commercial Destination Free Flyer Crew member who is an employee or customer of the contractor and is to be transported to/from the FF.

United States Industry Entity – any corporation, partnership, joint venture, association, or other entity that meets the requirements of 51 United States Code (U.S.C.) § 50101, excluding government entities such as NASA Centers, National Laboratories, and Federally Funded Research and Development Centers.

Roles and Responsibilities The roles and responsibility of the Contractor and the Government will reflect the stated objectives to leverage commercial products and processes to the maximum extent practical. NASA will rely on a focused insight approach reflective of a public-private partnership.

Contractor Responsibilities The Contractor is responsible for all activities associated with the design, development, manufacture, system verification, launch and spaceflight demonstration of the FF to include:

1. Registering the FF as a U.S. space object pursuant to Article II of the Convention on Registration of Objects Launched into Outer Space (reference United Nations Office for Outer Space Affairs (UNOOSA) Resolution 3235).

2. Obtaining and maintaining the necessary licenses, permits and clearances that may be required by the Department of Transportation, Department of Commerce, Department of Defense, Federal Communications Commission, NASA, or other Governmental agencies for performance of this contract, including a license or permit issued by the Federal Aviation Administration (FAA) in order to provide launch and re-entry services under this contract.

3. Implementing an Organizational Conflict of Interest Avoidance Plan (DRD-005).

4. Providing all facilities, personnel and resources to furnish all insight data in accordance with this SOW and the terms and conditions of the contract.

5. Implementing a Small Business Contracting Plan and Reports (DRD-006) Government Responsibilities

1. The Government will be responsible for validating that the content of the Contractor milestone reviews comply with the applicable criteria through participation in the reviews as described in Section 3.

2. NASA will be responsible for performing Probabilistic Risk Assessments (PRA), if deemed necessary, based on information provided by the Contractor through insight into the Contractor’s design and operational concepts with respect to applicable safety guidelines as described in Section 2.5.2.

PROCESSES AND METHODS

Section 2 of the SOW defines the processes and methods the Contractor will follow while satisfying the requirements defined in Section 3. NASA’s intent is to allow the Contractor to use industry best practices to satisfy requirements and execute program management, system engineering and safety processes, allowing the Contractor to tailor approaches to best address their commercial system. The Contractor’s progress developing the FF will be successively evaluated using insight into the processes following the Milestones outlined in Sections 3 of this SOW. NASA intends to invoke clause H.28 to gain insight into major areas of integration, including Visiting Vehicle integration with the FF, payload integration, Safety, Ground Services and Crew interface through review of applicable documentation Project Management Project Management and Administration This section includes the management functions necessary to assure accomplishment of activities described in this SOW including delivery of the data required by this contract. Details of the data to be delivered are provided in the Data Requirement Descriptions (DRDs) provided in contract Attachment D, Data Requirements List (DRL) and Data Requirement Descriptions (DRDs).

Project Management, Systems, Planning and Reporting

1. The Contractor will implement project management tools such as:

a. A framework for tracking and reporting program cost, schedule, and technical performance such as a work breakdown structure.

b. An organization chart identifying their management reporting structure and key personnel including major partners.

2. The Contractor shall develop an Integrated Master Schedule (IMS) (DRD002) that contains the logically networked tasks, milestones by work element and critical path beginning with contract award to the completion of the contract.

Information Technology Security The Contractor shall provide the following plans to ensure information technology security:

a. Information Technology Security Management Plan (DRD-011)

b. Information Technology Security Plan, if deemed required (DRD-012) Configuration and Data Management Configuration Management (CM) and Data Management (DM) systems ensure that configuration documentation is accurate and complete, design solutions are traceable to requirements, configuration changes are documented, controlled, and properly implemented, critical interfaces are defined and understood, there is consistency between the products and their associated documentation, and audit processes are defined. The Contractor will develop a documented CM plan that applies to hardware, firmware and software development, engineering drawings and lists.

Risk Management The Contractor’s approach to risk management shall be documented in a Risk Management Plan (DRD-010). Risk assessment and mitigation will be captured and managed throughout the contract life cycle and reviewed at milestones.

Design, Development, Test and Evaluation (DDT&E) The Contractor shall deliver a DDT&E plan (DRD013) which elaborates on the methods, processes and process controls used to evolve the FF concept into flight ready hardware.

Design and Construction Standards

a. NASA systems were built using design and construction standards developed over decades of human spaceflight; many of these standards are specified in NASA Systems Engineering Processes and Requirements document ref: NPR 7123.1 and further described in the NASA Systems Engineering Handbook ref: NASA SP-2016-6105. Recognizing that alternate industry standards may exist, which will provide an adequate level of product quality while furthering a more commercial implementation, the Contractor may use different standards for their processes.

b. Docking to the FF shall be compatible with U.S. commercial crew and cargo vehicles. To enable an open, flexible architecture extendable to future platforms, standardized interfaces should be employed where possible.

Software Management

a. The Contractor will develop a Software Management plan which provides insight into, and is a tool for monitoring the processes to be followed for software development, testing, change and release management, sustaining engineering, the methods to be used, and the approaches to be followed for each activity. As an example, ref: NPR 7150.2B, NASA Software Engineering Requirements is a governing document NASA uses to guide software development, management, and sustaining processes.

b. Safe and successful system performance shall be further assured by independent verification and validation (IV&V) of safety critical operations performed by an established Government or commercial entity and documented within the V&V plan per DDT&E DRD013.

Design and Analysis The Contractor shall provide insight into Engineering design and analyses as needed to meet contractual milestones, for example:

a. Thermal analysis

b. Structural analysis

c. Visiting Vehicle approach, rendezvous and docking analysis

d. Micrometeoroid and Orbital Debris (MMOD)

e. Communication analysis

f. Power analysis

g. Environmental Controls/Life Support Validation & Verification (V&V) Planning

a. The Contractor shall provide a Verification and Validation (V&V) plan as part of the DDT&E Plan (DRD013), which defines the Contractor’s approach for verifying compliance with their requirements, including detailed verification methods and objectives, and definition of necessary compliance data required for verification closures. For reference, NASA employs a Test Like You Fly approach. “Test Like You Fly” is defined as testing of all critical mission-operations elements as they will be flown to greatly reduce the risk of encountering negative impacts to mission success from partial to full loss of mission capabilities. This approach comprehensively validates system functionality. Ref: SSP 41172 is an example of environmental test standards.

Systems Engineering The Contractor shall develop a System Engineering plan as part of the DDT&E Plan (DRD013) that defines the Contractor’s approach to technically manage the engineering and integration processes and products throughout the project life cycle.

Safety and Mission Assurance

a. The Contractor shall deliver a Safety and Mission Assurance Plan (DRD-014). This plan covers quality assurance, definition of the safety and mission assurance process, and reliability and maintainability.

b. The Contractor shall implement a Safety and Health Plan (DRD-008) satisfying 48 CFR 1852.223-72.

c. The Contractor shall prepare a Mishap Preparedness & Contingency Plan (DRD-007) satisfying 48 CFR 1852.223-70.

Failure Propagation The FF should be designed and operated to control failures and ensure failure impacts do not propagate through the integrated FF system leading to catastrophic failure. For example, the NASA approach is to perform a Failure Modes and Effects Analysis (FMEA) and establish a Critical Items List (CIL) as documented in ref: SSP 30234.

Probabilistic Risk Assessment (PRA) The Contractor shall provide technical information and support PRAs to be performed by NASA, as deemed necessary. In addition to the Contractor’s DRD information, other support information may include, but not be limited to, a detailed description of the FF architecture, FF critical functions, component functions, and functional flow diagrams.

Mission Integration and Operations The Contractor’s approach to FF operations shall be documented in the Operations Management Plan (DRD-018), including the activities in this section, with the exception of sub-sections referencing an alternate DRD.

Mission Design The Contractor shall develop a Mission Design Plan per DRD-020, which includes the planning and approach to delivering the FF to LEO, identification of and insertion in the desired orbit, orbit maintenance, and management of the position of the spacecraft relative to other bodies.

Launch Operations The Contractor will be responsible for all Launch System interfaces, operations (flight and ground), range safety integration, processing and recovery elements, and obtaining all necessary licenses and permits necessary to execute the flight demonstration.

Flight Operations The Contractor will be responsible for all FF flight operations. Flight operations consists of all functions necessary to provide end-to-end flight control operations for the FF including ground segment interfaces, operating procedures, malfunction procedures, flight rules, timelines, simulation support, real-time support and crew training plans. Flight operations also addresses how the on-orbit and ground teams will view and interact with the FF operations products.

Mission Planning The Contractor will be responsible for FF mission planning. Mission planning is the function that provides schedules, plans for VV traffic, research logistics (supply and return), facility operations, command plans and crew timelines.

Mission Control Center Interface The Contractor will be responsible for communication between a FF control center and the FF. Additionally, the contractor shall provide a plan for communication with a payload operations and integration center to enable NASA and other payload providers to receive data, per DRD-018.

Training The Contractor will be responsible for the training of FF crew per DRD-018.

Capabilities and Services Interface The Contractor will develop and manage the payload interfaces and services offered throughout the FF. These capabilities and services shall be documented in an Interface Definition Document (IDD) (DRD-015) and will be available for use by payload customers.

REQUIREMENTS AND MILESTONES

Milestone reviews shall be conducted for the purpose of assessing programmatic and technical progress, business plans and contract performance at key decision points. The milestone data packages shall be released and made available for NASA review no later than 30 days prior to the milestone reviews. DRD submittals should be marked as initial, revised, or unchanged and any changes should be clearly marked. NASA will submit issues or concerns in a timeframe to be negotiated with the Contractor. The Contractor shall provide proposed action plans to address issues identified prior to the review and any additional issues raised during the review. At the beginning of each Milestone review, the Contractor will status any open actions from previous Milestones.

a. The Contractor will execute the milestones as defined in Sections 3.2 of this SOW.

b. Milestone reviews, with participation from NASA[footnoteRef:2], shall be conducted by the Contractor. [2: Herein to include NASA’s support and integration contractors]

c. Each milestone review will be considered complete when:

1) All review Issues/Actions are dispositioned and tracked

2) Design and supporting documentation is of acceptable maturity

3) Any significant design concerns, which impact the demonstration of capabilities of interest to NASA, have been identified and a forward action plan has been established

4) Evidence of Completion Package (DRD-021) is approved Engagement with NASA

a. The Contractor shall propose an approach in the Insight Management Plan (DRD-009) to establish an effective and collaborative partnership and working relationship with NASA.

b. The approach shall allow a lean NASA team to achieve risk-based focused insight into the Contractor’s efforts with access necessary to penetrate areas of greatest concern. The intended outcome is communication and engagement that ensures continuous dialogue and a level of candor enabling both parties to solve problems as a team, while allowing the contractor to maintain efficient and effective commercial processes.

Progress Reporting The Contractor shall conduct Quarterly Review meetings at mutually agreed upon locations (virtual meetings may be acceptable). Briefing packages shall be developed by the Contractor and should include, but not be limited to, schedule and technical/business performance status.

Required Milestones The Contractor shall execute the following Milestones, as described in this section:

i. M01 Mission Concept

ii. M02 System Requirements

iii. M03 Preliminary Design

iv. M04 Final Design

v. M05 Operational Readiness

vi. M06 Capability Demonstration Completion Milestone 01—Mission Concept The purpose of M01 is for the Contractor to present the critical management plans and tools needed for successful development of the FF and conduct of FF operations. The Contractor will define the concept of operations (ConOps) and approaches to manage the development of the FF. The overall system architecture for the FF will be reviewed for effectiveness to meet the technical and commercialization goals of the Commercial LEO initiative. For example, ref: NASA Systems Engineering Handbook, Appendix S: Concept of Operations Annotated Outline provides a framework for ConOps development.

The Contractor shall hold a review, or series of reviews, that presents and demonstrates:

1. Design/Insight Data and Related Activities – Mission Concept Data Package

a. Identification of FF services, capabilities, and interfaces

b. Description of FF functional and system requirements

c. Identification of standards to be used in design and construction of the FF

d. Identification of risks and mitigation approaches

2. Data Products Delivered The following products shall be delivered for the M01 Mission Concept milestone review:

a. Commercialization Roadmap (DRD-001)

b. Integrated Master Schedule (DRD-002)

c. Concept of Operations (DRD-003)

d. Risk Management Plan (DRD-010)

e. Information Technology Security Management Plan (DRD-011)

f. DDT&E Plan (DRD-013)

g. Safety and Mission Assurance Plan (DRD-014)

h. Mission Design Plan (DRD-020)

i. Evidence of Completion Package (DRD-021) Milestone 02—System Requirements The purpose of M02 is to baseline the governing requirements and to mature associated products so that preliminary design can commence.

The Contractor shall hold a review, or series of reviews, that presents and demonstrates:

1. Design/Insight Data and Related Activities – System Requirements Data Package

a. Description of the overall system architecture, associated specifications, and the approach to system and subsystem design, including capabilities/functional requirements, that satisfy mission needs.

b. Description of preliminary approaches for requirements verification and validation.

c. Identification of technical performance measures (e.g., mass, power, thermal) to be tracked throughout the project life cycle and approach to margin management.

d. Assessment of technology development maturity identifying low Technology Readiness Level (TRL) items and approaches for maturing to TRLs needed to meet mission requirements.

e. Identification of major technical, cost, schedule and safety risks and viable mitigation strategies.

f. Completion of preliminary Safety review which includes:

i. System Safety approach

ii. Acceptable approach to ensuring ground and flight safety, redundancy, reliability, criticality and quality assurance

iii. Identification of preliminary hazard assessment for deployment in LEO, VV rendezvous and docking, and hazards and causes

iv. Proposed approach for FF Payload Safety, for example ref: NASA SSP 51700

2. Data Products Delivered

a. Commercialization Roadmap (DRD-001)

b. Integrated Master Schedule (DRD-002)

c. Concept of Operations (DRD-003)

d. DDT&E Plan (DRD-013)

e. FF Capabilities and Services Interface Definition Document (DRD-015)

f. Operations Management Plan (DRD-018)

g. Human Rating and Habitability Plan (DRD-019)

h. Mission Design Plan (DRD-020)

i. Evidence of Completion Package (DRD-021) Milestone 03—Preliminary Design The purpose of M03 is to assess the design documentation of the FF at a level of maturity of approximately 10 to 25%. The status of the design and supporting activities (e.g., analysis, development testing) and functional allocation of system requirements to subsystems will be reviewed. Verification methods will also be identified.

The Contractor shall hold a review, or series of reviews, that presents and demonstrates:

1. Design/Insight Data and Related Activities – Preliminary Design Data Package

a. Description of preliminary design which meets the requirements at an acceptable level of maturity to proceed into the final design phase:

i. System architecture summary

ii. Adequate technical margins exist with respect to the technical performance measures (e.g., mass, power, thermal)

iii. Any required new technology has been developed to an adequate state of readiness, or backup options exist and are supported to make them a viable alternative

iv. Plan for Activation and Check Out and Commissioning

v. Capabilities and services objectives are supported (e.g., payload facilities)

b. Description of approach for ensuring requirements (e.g. power/thermal) are met regardless of operating mode (e.g. failures).

c. Evidence that S&MA (e.g., safety, reliability, maintainability and quality assurance) is adequately addressed in preliminary designs and in applicable S&MA products (e.g., hazard assessments, system safety analysis). An example of NASA’s approach to Safety Data Packages is documented in ref: SSP 30599.

d. Identification of approach for identifying failure modes and effects (see Section 2.5.1).

e. Assessment of TRL maturity.

f. Identification of top-level risks and mitigation plans.

g. Description for planned use of Government Furnished Property (GFP) and other Government Furnished Services, per Section 4.0.

2. Data Products Delivered

a. Commercialization Roadmap (DRD-001)

b. Integrated Master Schedule (DRD-002)

c. Concept of Operations (DRD-003)

d. DDT&E Plan (DRD-013)

e. FF Capabilities and Services IDD (DRD-015)

f. Operations Management Plan (DRD-018)

g. Human Rating and Habitability Plan (DRD-019)

h. Mission Design Plan (DRD-020)

i. Evidence of Completion Package (DRD-021) Milestone 04—Final Design The purpose of M04 is to assess the design documentation of the FF at a level of maturity of approximately 90%. The status of the final design and supporting activities (e.g., analysis, development testing) and functional allocation of system requirements to subsystems will be reviewed. Verification methods will also be identified and plans for verification will be reveiwed.

The Contractor shall hold a review, or series of reviews, that presents and demonstrates:

1. Design/Insight Data and Related Activities – Final Design Data Package

a. Documentation of design data (e.g., integrated schematics, drawings, CAD models) for FF and ground segment

i. Design Changes Summary since M03

ii. Status of Design Documentation and percentage complete for hardware and software

iii. Subsystem design summary (e.g. power, data, thermal, structures, EMI, MMOD)

iv. Supporting analysis validating design

b. Analysis of Logistics (reliability, maintainability, availability, initial spares estimate)

c. Evidence that capabilities and services objectives are supported (e.g., payload facilities)

d. Identification of operational limits and constraints

e. Status of Technical resource (e.g., mass, power, thermal) utilization estimates and margins

f. Identification of launch site operations plan

g. Identification of Activation and Checkout plan

h. Assessment of TRL maturity

i. Evidence that S&MA (e.g., safety, reliability, maintainability and quality assurance) is adequately addressed in final designs and in applicable S&MA products (e.g., hazard assessments, system safety analysis, verifications for controls)

j. Idenitication of approach for identifying failure modes and effects (see Section 2.5.1)

k. Identification of top-level risks and mitigation plans

l. Analysis of Integrated Vehicle Performance

m. Status of interfaces with external entities, including any international agreements, licenses from FCC, FAA, and NTIA, and launch and landing range safety approval

2. Data Products Delivered

a. Commercialization Roadmap (DRD-001)

b. Integrated Master Schedule (DRD-002)

c. Concept of Operations (DRD-003)

d. DDT&E Plan (DRD-013)

e. FF Capabililties and Services IDD (DRD-015)

f. Operations Management Plan (DRD-018)

g. Human Rating and Habitability Plan (DRD-019)

h. Mission Design Plan (DRD-020)

i. Evidence of Completion Package (DRD-021) Milestone 05—Operational Readiness The purpose of M05 is to ensure all verification activities are complete and that the FF is ready for launch and deployment into LEO. Hardware, software, safety, licensing, ground and flight operations planning, and range approval will be reviewed.

The Contractor shall hold a review, or series of reviews that presents and demonstrates:

1. Design/Insight Data and Related Activities – Operational Readiness Data Package

a. Status of analysis and test reports validating the results of verification closure and action plan for closure of any open verification.

b. Evidence that the delivered system meets the established objectives

c. Evidence that the system will perform properly in the expected operational environment

d. Identification of top-level risks and mitigation plans

e. Evidence S&MA (e.g., safety, reliability, maintainability and quality assurance) is adequately addressed in as-built designs and operational procedures, including VV rendezvous and docking.

f. Confirmation that the as-built FF has been developed in accordance with the Contractor’s design requirements, as evidenced by acceptance records, manufacturing instructions, and rationale for any nonconformances, deviations, or waivers.

g. Confirmation of completion of non-NASA agreements and approvals, including (as applicable):

i. Agreements involving Foreign countries and companies

ii. Launch Range Approval

iii. FAA Launch Approval

iv. FCC Approval

v. NTIA Authorization

h. Confirmation of completion of ground safety training and products in support of Launch vehicle integration.

i. Confirmation of completion of ground operator training, including contingency response.

j. Identification of Launch site operations plan

k. Identification of Activation and Checkout plan

l. Description of Operations products which support vehicle safing, crew, and payload activities (e.g. operations procedures, flight rules)

m. Description of Crew training methods and products

2. Data Products Delivered

a. Commercialization Roadmap (DRD-001)

b. Integrated Master Schedule (DRD-002)

c. Concept of Operations (DRD-003)

d. FF Capabilities and Services IDD (DRD-015)

e. Operations Management Plan (DRD-018)

f. Human Rating and Habitability Plan (DRD-019)

g. Mission Design Plan (DRD-020)

h. Evidence of Completion Package (DRD-021) Milestone 06 – Capability Demonstration Completion The purpose of Milestone 06 is to complete the demonstration objectives of the FF in LEO. The demonstrations include crewed operations and any proposed research and technology development capabilities as defined by the Contractor. The milestone is met with the completion of the last demonstration objective. A notional example of demonstration objectives are shown in Table 3.2.6-1.

The Contractor shall hold a review, or series of reviews that presents and demonstrates:

1. Design/Insight Data and Related Activities – Capability Demonstration Completion Data Package

a. Summary of results from demonstration objectives in Table 3.2.6-1, including lessons learned and any recommended design changes.

Table 3.2.6-1: Free Flyer Capability Demonstration Objectives

· Habitation

· Life Support

· Hygiene

· Exercise

· Logistics resupply

· Science

· Attitude control

· Orbit maintenance

2. Data Products Delivered

a. Human Rating and Habitability Plan (DRD-019)

b. Evidence of Completion Package, including post-demonstration report per DRD-021 Special Studies The Contractor shall perform Special Studies and analyses, provide materials, and/or fabricate incidental hardware in support of this contract, as required. Each task will be initiated by written direction from the NASA Contracting Officer. These tasks may include but are not limited to advance planning and feasibility studies in support of future contemplated capabilities; development, fabrication, and test of hardware/software to support special tasks; and unique demonstration studies.

GOVERNMENT FURNISHED PROPERTY/SERVICES

a. Use of Government Furnished Property (GFP) or Government Furnished Services (GFS) will be under separate agreements with NASA or contract update for major GFP items. GFS may include NASA ground services (e.g., Subject Matter Expertise, Docking mechanism 6-Degree of Freedom Testing).

b. The Contractor shall document their approach to administering and controlling GFP per DRD-016, Government Property Management Plan.

c. The Contractor shall submit an annual summary-level property management and financial data on Government-furnished and contractor-acquired NASA property per DRD-017, Financial Reporting Contractor-Held Property.

image1.png