Attachment_D_-_FF_Data_Requirements_List-9-24.docx

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

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 D Data Requirements List (DRL) and Data Requirement Descriptions (DRDs)

DATA REQUIREMENTS LIST DESCRIPTION

The DRL provides the Data Requirement Description (DRD) number, title, data type, and submittal frequency for each data deliverable item.

DATA TYPES

The types of data and their contractually applicable requirements for approval and delivery after contract award are:

In the cases where the DRL classifies a DRD with two data type requirements, the DRD will clearly identify the data type requirements as well as the delivery requirement associated with each type.

DATA REQUIREMENT DOCUMENT

This section provides a description of the fields of the Data Requirement Documents (DRDs).

Data Requirements

First Submission Date This field provides the detailed description of the required and/or expected content and scope of the deliverable(s) Initial due date

DATA TRANSMITTAL AND FORMAT

This section provides additional detail regarding the transmittal and format of the DRDs.

Data Transmittal DRDs shall be transmitted to NASA electronically to the Contracting Officer. The Contractor shall notify the Contracting Officer and the Contracting Officer Representative (COR) in writing of DRD delivery.

Data Transmittal For each DRD, the transmittal shall include:

a. Contractor transmittal memorandum that provides the following information:

1. Contract number

2. Contractor name

3. DRD number

4. DRD data type (specified in “Type” column of the DRL)

5. Submission date or milestone being satisfied

6. Document number and revision. Also, marked as “Initial”, “Revised” or “Unchanged”

7. Document title

8. File names of all files being delivered; multiple files per document must be clearly related to the document

9. Distribution (Notification list as defined by the DRD distribution field and the Contracting Officer’s letter)

10. Targeted release date

b. Electronic files submitted to the appropriate NASA or Contractor site

Data Format Existing Contractor internal documents may be used to meet the data requirements of the DRD to the extent practical. The DRD will call out any special format requirements, if required.

Electronic Format The DRDs shall be provided in an electronic format that meets three basic requirements: “Readable”, “Printable”, and “Downloadable” by NASA utilizing publicly available off-the-shelf software. If the electronic format is not supported by publicly available off-the-shelf software, the Contractor shall provide NASA with the necessary software and approach to support the three basic requirements.

DRDs shall be maintained electronically in the Contractor’s preferred format, unless a specified format is defined in the DRD. All electronic DRDs shall be submitted to an approved repository. The Contractor shall notify the Contracting Officer electronically of the DRD delivery.

DATA RESTRICTIONS AND MARKINGS

All data produced or delivered under this contract shall be governed by FAR 52.227-14 Rights in Data-General (MAY 2014), Alts. II & III, as modified by NFS 1852.227-14 Rights in Data-General (APR 2015). The Contractor shall determine the data restriction that applies to each data deliverable and mark the data restriction on the data coversheet, or indicate the data restriction in the data transmittal package if the data format precludes identification of data restriction directly in the data. The Contractor shall make a determination for each individual data deliverable item, and shall not apply a default or blanket data restriction marking to all data deliverables (e.g., “data may be export restricted”). If NASA does not agree with the Contractor applied data restriction, the NASA Contracting Officer shall return the data to the Contractor, cancel the markings, or ignore the markings consistent with the procedures set forth in the “data rights” clause(s) contained in the contract.

The Contractor shall consider the following data restriction categories, as a minimum, and utilize specified marking statements.

1. If data delivered under this contract is subject to the International Traffic in Arms Regulations (ITAR), the data shall contain an “ITAR Notice” as follows:

International Traffic in Arms Regulations (ITAR) Notice This document contains information which falls under the purview of the U.S. Munitions List (USML) as defined in the International Traffic in Arms Regulations (ITAR), 22 CFR §120-130, and is export-controlled. It shall not be transferred to foreign persons in the U.S. or abroad without specific approval of a knowledgeable NASA export control official, and/or unless an export license or license exemption is obtained/available from the Directorate of Defense Trade Controls, United States Department of State. Violations of these regulations are punishable by fine, imprisonment or both.

2. If data delivered under this contract is subject to the Export Administration Regulations (EAR), the data shall contain the “EAR Notice” as follows:

Export Administration Regulations (EAR) Notice This document contains information within the purview of the Export Administration Regulations (EAR), 15 CFR §730-774, and is export-controlled. It may not be transferred to foreign persons in the U.S. or abroad without specific approval of a knowledgeable export control official, and/or unless an export license or license exception is obtained/available from the Bureau of Industry and Security, United States Department of Commerce. Violations of these regulations are punishable by fine, imprisonment or both.

DRD MAINTENANCE PROCEDURES

Throughout the performance of the contract, the DRL provides a listing by data category of the DRDs.

Configuration Management of DRD The Contractor will employ a system for organizing, identifying, and tracking all submittals of DRDs, to include any changes or revisions. It is expected that this system will include the mapping of Contractor documents and files submitted in response to each DRD, and will include identification of the DRD Type per the DRL. All Type 1 and Type 2 submittals shall be marked as “Pending NASA Approval”, and once approved shall be delivered and marked as “Approved by NASA”.

Reference to Other Documents and DRDs in Data Submittals The Contractor’s submittal of a DRD may make reference to other documents and/or other DRDs. At the time of submission of the DRD, any referenced document within the DRD shall be made available to NASA. The Contractor shall provide NASA with access to any referenced document and the location of that data within the referenced document. Any reference made to data associated with another DRD that is required separately by the contract shall include the DRL number of and location of the data within the referenced DRD.

DATA REQUIREMENTS LIST (DRL)

Update at Milestone, as required

DATA REQUIREMENTS DESCRIPTION

(Based on JSC-STD-123) 1a. DRD Title:

Commercialization Roadmap

2. Date of Current Version

3a. DRD No.

3b. RFP/Contract No.

4. Use (Define used for, intended use of, and/or anticipated results of data) NASA will utilize the Roadmap to measure the Contractor’s progress in achieving stated goals of the overall commercialization strategy.

Type 2

5. DRD Category

Administrative

SR&QA

6. References (SOW Clause, etc.)

SOW 3.2.1, 3.2.2, 3.2.3, 3.2.4, 3.2.5

7. Interrelationships (e.g., with other DRDs)

8. PREPARATION INFORMATION: The Contractor shall prepare the deliverable as follows:

DESCRIPTION/PURPOSE:

The Commercialization Roadmap shall provide a description of the Contractor’s financial health and business plan with measurable performance goals and metrics to accomplish the development and demonstration of a Commercial Destination FF. NASA will utilize this data to measure the Contractor’s progress in achieving stated goals of the overall commercialization strategy.

DATA REQUIREMENTS:

The Commercialization Roadmap shall define the following and establish measurable performance goals and metrics to be met by the Contractor:

a. Portfolio of products and services to be demonstrated and offered, including timing and pricing strategy

b. Plan/strategy for accommodating NASA’s long term needs in LEO

c. Performance-to-plan for stated goals and metrics

d. The proposed schedule of performance milestones, including payment amounts, objective success criteria, rationale, and planned achievement dates

e. Business Development strategy to capture target markets, including plan to stimulate non-NASA demand (i.e. Demand Development Campaign)

f. Subcontracting and Partnerships plan, as applicable

g. Financing strategy including future financing goals, investment round results, and investor payback commitments/exit strategy

h. Corporate financial health FORMAT: The Contractor’s format is acceptable

1 electronic copy: Authorized Repository Authorized Repository Upload Notification: NASA Free Flyer Manager, NASA Contracting Officer, NASA FF Authorized Repository representative, others as negotiated

13. REMARKS: N/A

DATA REQUIREMENTS DESCRIPTION

(Based on JSC-STD-123) 1a. DRD Title:

Integrated Master Schedule

2. Date of Current Version

3a. DRD No.

3b. RFP/Contract No.

4. Use (Define used for, intended use of, and/or anticipated results of data) The Integrated Master Schedule is the primary means of communicating project schedule information between the Contractor and the Government.

Type 3

5. DRD Category

Administrative

SR&QA

6. References (SOW Clause, etc.)

SOW 2.1.2, 3.2.1, 3.2.2, 3.2.3, 3.2.4, 3.2.5

7. Interrelationships (e.g., with other DRDs)

To provide schedules using established standard processes, data structures and reporting conventions to plan, manage, and report the work required in the performance of the Statement of Work (SOW). Schedules typically include, at a minimum, an Integrated Master Schedule (IMS) and production schedules.

DATA REQUIREMENTS:

a. The Contractor shall provide schedules that clearly depict the interrelationships and constraints among related tasks and milestones. The Contractor is encouraged to utilize modern manufacturing resource planning, industrial engineering techniques and other approaches to ensure schedule stability, accuracy, reliability, predictability, and achievability.

b. The schedules shall be developed and updated to ensure a consistent, accurate, and stable scheduling approach that provides for the identification, coordination, sequencing, control, implementation and tracking of all required activities.

c. The approach shall provide the ability to fully identify, analyze, mitigate and control scheduling risks and impacts; accurately identify and analyze critical path activities and schedule reserve; and allow its users to easily measure the progress towards achieving the intended plan.

d. The approach shall not only represent the scheduled work for that activity, but also the requirements commitment from all interfacing organizations on the critical path.

e. Schedule consistency as used in this DRD defines the degree to which the Contractor utilized standardized scheduling approaches between similar processing activities and flows. Accurate scheduling as used in this DRD is defined as the accurate representation of work content and tasks duration (predicted vs. actuals).

FORMAT: Adobe PDF for the initial version submitted with the proposal, Contractor format for all subsequent updates.

1 electronic copy: Authorized Repository Authorized Repository Upload Notification: NASA Free Flyer Manager, NASA Contracting Officer, NASA FF Authorized Repository representative, others as negotiated

13. REMARKS: N/A

1a. DRD Title:

Concept of Operations

2. Date of Current Version

3a. DRD No.

3b. RFP/Contract No.

4. Use (Define used for, intended use of, and/or anticipated results of data) The Concept of Operations (ConOps) Document defines the overall high-level concept of how the FF will be used and operated. The ConOps establishes a framework for the FF requirements and defines the architecture of the spaceflight demonstration addressing both the Contractor’s spaceflight and business plan demonstration objectives.

5. DRD Category

Administrative

SR&QA

6. References (SOW Clause, etc.)

SOW 3.2.1, 3.2.2, 3.2.3, 3.2.4, 3.2.5

7. Interrelationships (e.g., with other DRDs) DRD-001, Commercialization Roadmap

The Concept of Operations Document will be used to document the planned operational concept addressing both the Contractor’s spaceflight and business plan demonstration objectives. The ConOps should cover all aspects of the operation of the FF, including any driving off-nominal cases.

DATA REQUIREMENTS:

The FF Concept of Operations should include at a minimum:

a. Sequential phases of the FF:

1. Approach for launch and orbital insertion and maintenance

2. Total number of commercial elements and approach for assembly and outfitting

3. Development of ground-segment capabilities that align with evolution of the FF

4. Maturation of system capability

5. Acceptance of Visiting Vehicles

6. Evolution of FF capabilities demonstrating the transition towards providing commercial services where NASA is one of many customers

b. Proposed systems and research capabilities of the FF, including research return

c. Planned number of FF crew and manning strategy (e.g. permanent or crew-tended)

d. Plan for Crew medical pre-flight certification and in-flight medical capabilities and requirements including food, water, and exercise

e. Plan to document a Crew Code of Conduct prescribing chain of command and expected behaviors

f. Identification of demonstration objectives to meet the Commercialization Roadmap (DRD-001) identifying the set of operations supporting demonstration objectives

g. Identification of off-nominal, contingency, or degraded-mode operational situations that could result in loss of the FF or inability to meet commercialization goals or NASA needs.

FORMAT: The Contractor’s format is acceptable

1 electronic copy: Authorized Repository Authorized Repository Upload Notification: NASA Free Flyer Manager, NASA Contracting Officer, NASA FF Authorized Repository representative, others as negotiated

13. REMARKS: N/A

1a. DRD Title:

Deleted

2. Date of Current Version

3a. DRD No.

3b. RFP/Contract No.

Technical

Administrative

SR&QA

6. References (SOW Clause, etc.)

7. Interrelationships (e.g., with other DRDs)

DATA REQUIREMENTS:

FORMAT:

DATA REQUIREMENTS DESCRIPTION

(Based on JSC-STD-123) 1a. DRD Title:

Organizational Conflict of Interest (OCI) Plan

2. Date of Current Version

3a. DRD No.

3b. RFP/Contract No.

4. Use (Define used for, intended use of, and/or anticipated results of data) To document the Contractor's comprehensive management approach and implementation methods for avoiding, neutralizing, and mitigating organizational conflicts of interest.

Type 1

5. DRD Category

Technical

SR&QA

6. References (SOW Clause, etc.) SOW 1.3.1 FAR Subpart 9.5, Organizational and Consultant Conflicts of Interest NFS 1852.209-71, Limitation of Future Contracting NFS 1852.237-72, Access to Sensitive Information NFS 1852.237-73, Release of Sensitive Information NASA Guide on Organizational Conflicts of Interest (March 2010)

7. Interrelationships (e.g., with other DRDs)

The OCI Plan describes the Contractor’s comprehensive management approach and implementation methods for avoiding, neutralizing, mitigating, or waiving organizational conflicts of interest. After approval, the OCI Plan will become part of the contract.

DATA REQUIREMENTS:

The OCI Plan shall discuss the following:

a. Purpose: A summary of the Contractor’s rationale for instituting and applying the OCI Plan;

b. Update Criteria: A description of the criteria and process for determining when an update to the plan is required;

c. Contractor’s OCI Assessment Methodology: A summary of the general methodology used to identify, avoid, neutralize, or mitigate OCI issues. Define company roles, responsibilities, and procedures for screening (i.e., identifying/recognizing, analyzing/evaluating, resolving, and reporting) existing and new business opportunities for actual/potential OCIs. Include any Contractor policies defining organizational or employee sanctions for violations of Contractor’s OCI procedures or requirements. Identify any Contractor recordkeeping or self-audit requirements related to Contractor’s OCI program. Identify any affiliated companies/entities (e.g., a parent company or a wholly owned subsidiary) and procedures for coordinating OCIs with such affiliated companies/entities. Explain how the Contractor will flow down the provisions of this mitigation plan to any subcontractor that may have a conflict with regard to performing the requirements of this contract;

d. Contractor’s OCI Response Procedures: A summary of the steps that the Contractor will take when an OCI has been identified or when circumstances have changed such that an OCI issue is probable. Include Contractor procedures for reporting of all potential/actual OCIs during performance of the contract and the point of contact for OCI reports;

e. Identified OCI Risks: A description of identified potential OCI risks, due to the Contractor’s relationships or potential relationships with the Government, other companies, and other contracts. The description shall characterize the risk and measures to avoid, neutralize, or mitigate each OCI threat. If using a firewall, explain how these actions will operate to successfully address the conflict without adversely affecting performance of the contract. Additionally, Contractor shall identify any potential OCIs created by the requirements of this RFP which the Contractor intended to resolve using methods other than mitigation;

f. Personnel Clearance Procedures: A description of the procedures the Contractor will use if needed to identify and partition Contractor personnel requiring access to or participation in activities that would otherwise create an OCI issue; and

g. OCI Training: A description of the training to be provided to a Contractor personnel regarding potential OCIs on this contract.

FORMAT: The Contractor’s format is acceptable

1 electronic copy: Authorized Repository Authorized Repository Upload Notification: NASA Free Flyer Manager, NASA Contracting Officer, NASA FF Authorized Repository representative, others as negotiated

13. REMARKS: N/A

DATA REQUIREMENTS DESCRIPTION

(Based on JSC-STD-123) 1a. DRD Title:

Small Business Subcontracting Plan and Reports

2. Date of Current Version

3a. DRD No.

3b. RFP/Contract No.

4. Use (Define used for, intended use of, and/or anticipated results of data) To describe the Contractor's planned approach to Small Business Subcontracting and their reporting against this plan.

Plan: Type 1, Report: Type 2

5. DRD Category

Technical

SR&QA

6. References (SOW Clause, etc.)

FAR 52.219-9, NFS 1852.219-75, SOW 1.3.1

7. Interrelationships (e.g., with other DRDs)

The Small Business (SB) Subcontracting Plan shall be in compliance with FAR 52.219-9. The SB Subcontracting Reporting shall be in compliance with NFS 1852.219-75.

DATA REQUIREMENTS:

The Subcontracting plan must include the approach that the Contractor intends to use in meeting the subcontracting goals. Subcontractors whose bid is part of this proposal should be identified. For each subcontractor, the percentage of the proposal and any small or small business subcategory classification should be identified. For areas of potential future subcontracting, the Contractor should identify the area of work, the percentage of contract that this is expected to encompass, potential subcontractors and their small business or small business subcategory classification. Describe the management approach to subcontracting with small, small disadvantaged 8(a), Women-owned, HUBZoned, Veteran owned, and Service disabled veteran owned companies and HBCU/MIs.

FORMAT: The Contractor’s format is acceptable

Frequency of Submission: In accordance with FAR 52.219-9 and NFS 1852.219-75.

Reports:

1. In lieu of submitting a paper copy of the SF 294 and SF 295 Subcontracting Report for Individual Contracts. The Contractor shall submit semi-annually and at contract completion to the NASA/JSC Contracting Officer electronically version of this data.

2. Contractors are required to submit subcontracting data in the Electronic Subcontracting Reporting System (eSRS) which has replaced the paper Standard Form 294 and SF 295 Summary Subcontracting Reports.

3. All Contractors are required to register and file both types of subcontracting reports using the eSRS system. The website to register is www.esrs.gov.

1 electronic copy: Authorized Repository Authorized Repository Upload Notification: FF Contracting Officer and FF Contracting Officer’s Representative

13. REMARKS: N/A

DATA REQUIREMENTS DESCRIPTION

(Based on JSC-STD-123) 1a. DRD Title:

Mishap Preparedness & Contingency Plan

2. Date of Current Version

3a. DRD No.

3b. RFP/Contract No.

4. Use (Define used for, intended use of, and/or anticipated results of data) To provide NASA with an understanding of the Contractor’s processes for mishap notification and corrective action plans.

5. DRD Category

Technical

Administrative

6. References (SOW Clause, etc.)

SOW 2.5, 48 CFR 1852.223-70, NPR 8621, NASA Procedural Requirements for Mishap and Close Call Reporting, Investigating, and Recordkeeping

7. Interrelationships (e.g., with other DRDs)

This plan provides NASA with an understanding of the Contractor’s processes for notifying NASA of mishaps, as well as how the Contractor plans to investigate and establish corrective action plans for mishaps that occur. Mishap reporting, investigation and corrective action requirements differ according to whether the specific mishap occurs on NASA property. Mishaps occurring on third party property will be handled in the same manner as those occurring on Contractor property. A reportable mishap is any unplanned event that results in damage to property or personnel which occurs during the performance of activities related to the contract.

DATA REQUIREMENTS:

a. Mishap classification shall occur as documented in NPR 8621.1, NASA Procedural Requirements for Mishap and Close Call Reporting, Investigating, and Recordkeeping.

b. Mishaps occurring on NASA property:

1. Immediate Notification and Reporting of Mishaps Occurring on NASA Property.

i. The Contractor shall immediately report the mishap to the local safety office in accordance with local reporting requirements for all Type A or B injury and/or property damage mishaps occurring on NASA property while performing work in support of this SOW.

ii. The Contractor shall immediately report all onsite emergencies, notifying both emergency response (e.g., 911, fire, ambulance, Center security office) and a supervisor, management official, or a safety/health staff member of the circumstance of the mishap in accordance with the local emergency reporting requirements. The Contractor shall ensure that contract employees on NASA property know and comply with local safety, health and emergency response requirements. The Contractor’s plan shall describe the processes required to accomplish this task.

c. Mishaps occurring on contractor property, third party property, other non-NASA government property, or during FF operations:

1. The contractor shall immediately report any mishaps occurring on Contractor property, Third Party property or other non-NASA Government Property. The Contractor shall immediately notify NASA FF Manager in the event that a Type A or B mishap occurs to NASA personnel or property while on Contractor, third party property or other non-NASA government property. The Contractor’s plan shall describe the process through which notification will take place.

2. Mishap investigation and corrective action for mishaps on Contractor property, Third Party property, or other non-NASA Government Property.

i. An initial investigation by the Contractor is required for all mishaps which have been reported to NASA. NASA reserves discretionary authority to investigate mishaps which involve NASA personnel or property regardless of location. The Contractor has the discretion to perform any collateral investigations. However, investigations implemented by NASA will take priority with regard to access to evidence, data, and witnesses. The proceedings of NASA investigations will remain confidential. The Contractor will have an opportunity to comment on the investigation report in accordance with NASA protocols.

ii. After the Contractor completes its investigation of the mishap and, when appropriate, has developed a plan of corrective action, the Contractor shall deliver this completed report to NASA within 15 days of completion. This plan will include any verification activities identified by the Contractor to ensure that corrective actions to be implemented by NASA or a third party have been implemented.

FORMAT: The Contractor’s format is acceptable

1 electronic copy: Authorized Repository Authorized Repository Upload Notification: NASA Free Flyer Manager, NASA Contracting Officer, NASA FF Authorized Repository representative, others as negotiated

13. REMARKS: N/A

1a. DRD Title:

Safety and Health Plan

2. Date of Current Version

3a. DRD No.

3b. RFP/Contract No.

4. Use (Define used for, intended use of, and/or anticipated results of data) To provide NASA with the Contractor’s plans for protecting the safety and health of the public, employees, property, and equipment.

5. DRD Category

Technical

Administrative

6. References (SOW Clause, etc.) SOW 2.5

NFS 1852.223-72

7. Interrelationships (e.g., with other DRDs)

A detailed Safety and Health Plan shows how the Contractor intends to protect the life, health, and well-being of the public, employees as well as property and equipment. The plan should include detailed discussions of the policies, procedures, and techniques for all anticipated working conditions that will be encountered throughout the performance of the contract.

If the Contractor will conduct work or be located on a NASA site or in a NASA facility, the Safety and Health Plan should discuss measures to be taken to ensure the protection of property, equipment, and the environment in the production of Contractor deliverables and/or in the pursuit of any of its activities.

DATA REQUIREMENTS:

The Safety and Health Plan should contain the following information:

a. Description of the Contractor’s approach to manage and operate in compliance with Occupational Safety and Health Administration (OSHA) standards.

b. Description of the Contractor’s approach to operate in compliance with NASA facility requirements for performance of any activities conducted at a NASA facility.

c. Description of the Contractor’s approach for emergency preparedness and contingency planning which addresses fire, explosion, inclement weather 29 CFR 1910.120 (HAZWOPER).

d. Description of the Contractor’s approach to provide safety and health training to NASA personnel prior to Contractor site visits as required.

FORMAT: The Contractor’s format is acceptable

1 electronic copy: Authorized Repository Authorized Repository Upload Notification: NASA Free Flyer Manager, NASA Contracting Officer, NASA FF Authorized Repository representative, others as negotiated

13. REMARKS: N/A

1a. DRD Title:

Insight Management Plan

2. Date of Current Version

3a. DRD No.

3b. RFP/Contract No.

4. Use (Define used for, intended use of, and/or anticipated results of data) The Insight Management Plan will ensure NASA personnel can perform insight into the Contractor’s design and approach.

5. DRD Category

Technical

SR&QA

6. References (SOW Clause, etc.)

SOW 3.1

7. Interrelationships (e.g., with other DRDs)

NASA will utilize the Contractor’s Insight Management Plan to ensure NASA personnel and its support services contractors can perform their insight as defined in clause H.28, NASA Insight and Approval.

DATA REQUIREMENTS:

At a minimum, the Contractor’s Insight Management Plan shall describe the partnering approach and establish a cooperative environment that ensures an effective working relationship between NASA and the Contractor dedicated to successful demonstration of a Commercial Destination FF. The Contractor’s Insight Management Plan shall describe the accommodations for providing Government personnel and its support services contractor(s) timely and open access necessary to obtain a working-level understanding into, but not limited to:

a. DDT&E for hardware and software

b. Safety

c. Configuration management

d. Verification

e. Commercial roadmap development

f. Ground services and operations

g. Flight operations and demonstrations

h. VV, crew, and payload interfaces

These accommodations include facility access, data, personnel availability and any other information, including design and analysis data, required to meet contract requirements and milestone acceptance criteria. The Contractor’s Insight Management Plan shall identify instructions or training required to allow for meaningful NASA insight and participation (e.g., facility and safety familiarization).

In addition, the Insight Plan shall address:

a. Accommodating clause H.28, NASA Insight and Approval and the following items:

1. The Contractor will provide the Government on-going access into activities and data used for achieving milestone acceptance, approving of Type 1 and 2 data deliverables, understanding the Contractor’s organizational structure and NASA interfaces, including the approach to communications and coordination with the Government throughout FF development and on-orbit demonstrations.

2. The Contractor will provide the Government on-going access to data, both remotely and on-site, in a useable and readable format. Also provide the Government the ability to locate and review all data used in performance of this contract and any other information related to the FF, to include technical data, supporting data/information, administrative and management information, with the exception of financial information. Whether the data accessed includes the ability of the Government to download or copy data; the Contractor’s proposed data restriction legends on accessed data; and mechanisms to ensure that access data is not confused with data delivered under the contract.

3. The timeframe the Contractor shall notify the NASA FF Manager of technical meetings, control boards, reviews, demonstrations, tests, and reportable anomaly investigations to permit meaningful Government participation through the entire event when appropriate.

4. The timeliness and ease by which the Contractor will provide access and make data available to address risks associated with, but not limited to, completing DDT&E, milestones, and on-orbit demonstrations.

5. Timely elevation of issues to NASA.

b. Establishing a cooperative environment between NASA and the contractor dedicated to successful development and on-orbit demonstration, including:

1. Establishing working relationships between Contractor and NASA personnel.

2. Ensuring open communication that mitigates risk by enabling a continuous dialogue.

c. Responding to and resolving, when appropriate, any concerns and issues identified by NASA’s insight effort

d. NASA may elect to have representation as a resident office at the Contractor’s major manufacturing and engineering facilities for the life of the contract. In addition to access to Contractor facilities for insight, the Contractor shall describe the NASA provisions for office space co-located on-site, badging, furniture, telephones, and use of easily accessible fax, data lines, Internet, and copy machines, for full-time and temporary Government insight and support services contractor personnel in performance of this contract, including training. This shall include:

1. Co-located on site accommodations clearly identified.

2. Innovative use of technology that enables effective participation for completing milestones and making progress toward FF development and on-orbit demonstration.

e. The process of providing the Government insight into all subcontractors and suppliers performing or supporting any safety critical work associated with this contract.

FORMAT: The Contractor’s format is acceptable

1 electronic copy: Authorized Repository Authorized Repository Upload Notification: NASA Free Flyer Manager, NASA Contracting Officer, NASA FF Authorized Repository representative, others as negotiated

13. REMARKS: N/A

1a. DRD Title:

Risk Management Plan

2. Date of Current Version

3a. DRD No.

3b. RFP/Contract No.

4. Use (Define used for, intended use of, and/or anticipated results of data) Provides a baseline document for planning, management, control, and implementation of the Contractor’s risk management throughout the contract life cycle.

5. DRD Category

Administrative

SR&QA

6. References (SOW Clause, etc.)

SOW 2.3, 3.2.1

7. Interrelationships (e.g., with other DRDs)

The purpose of risk management is to identify risks early in the project in order for the appropriate implementation of mitigations to reduce the consequences of the risk or likelihood that the risk will occur. A risk refers to anything that can prevent the Contractor from meeting contract objectives. All forms of risk shall be managed including safety, technical (hardware and software), programmatic, operational, cost, and schedule risks, with particular attention to ensuring safety of crewmembers and the public. Cost risks are not required to be reported to NASA.

DATA REQUIREMENTS:

At a minimum, the Risk Management Plan (RMP) shall include:

a. An introduction to specify the program/project risk objectives and policy toward risk and to explain the purpose, scope, assumptions, constraints, key ground rules, and policy pertaining to the project risk management process.

b. An overview of the risk management process, including how the risk management process continually integrates and relates to other project management and system engineering activities (e.g., lessons learned, safety, technical, business, cost and schedule risks which present threats to safe operations or commercialization objectives) and general risk mitigation strategies to be employed throughout project life cycle.

c. An overview of the organization, roles, and responsibilities of program, project, customers, and suppliers with regard to risk management.

d. An overview of the methods, tools, and metrics utilized, including a risk attributes scorecard that provides the criteria for establishing likelihood and consequence values of a risk.

FORMAT: The Contractor’s format is acceptable

1 electronic copy: Authorized Repository Authorized Repository Upload Notification: NASA Free Flyer Manager, NASA Contracting Officer, NASA FF Authorized Repository representative, others as negotiated

13. REMARKS: A risk status is required at Milestone Reviews per the Design/Insight Data Clauses of the SOW.

1a. DRD Title:

Information Technology Security Management Plan

2. Date of Current Version

3a. DRD No.

3b. RFP/Contract No.

4. Use (Define used for, intended use of, and/or anticipated results of data) See Description/Purpose below

5. DRD Category

Technical

SR&QA

6. References (SOW Clause, etc.) SOW 2.1.3, 3.2.1 FAR 52.204-21: Basic Safeguarding of Covered Contractor Information Systems NFS 1852.204-76: Security Requirements for Unclassified IT Resources NFS 1852.223-75: Major Breach of Safety or Security NFS 1852.237-72: Access to Sensitive Information NFS 1852.237-73L Release of Sensitive Information NPR 2810.1(series): Security of Information Technology.

OMB Circular A-130: Management of Federal Information Resources

7. Interrelationships (e.g., with other DRDs) DRD-012 Information Technology Security Plan

To provide Government insight into the Contractor’s methodology for managing all aspects of information security and to ensure critical components are addressed. The ITSMP will be in compliance with NFS 1852.204-76, Security Requirements for Unclassified Information Technology Resources (Jan 2011). The Government, after review of the ITSMP, will notify the Contractor of the need for an IT Security Plan (ITSP) and the associated due date.

DATA REQUIREMENTS:

The Contractor shall describe the processes and procedures that will be followed to ensure appropriate security of information technology (IT) resources that are developed, processed, or used under this contract.

Unlike the IT security plan, which addresses the IT system and the security control implementations, the ITSMP addresses how the Contractor will manage personnel and processes associated with IT security on the contract.

The ITSMP shall include, at a minimum, the following:

a. Contractor’s information security Points of Contact (POC(s)) including roles and responsibilities.

b. A description of policies, processes, and/or procedures for:

1. Meeting all applicable security assessment & authorization requirements, including but not limited to development and maintenance of IT Security Plans (ITSPs), including external IT systems; implementation and validation of security controls, security assessment, authorization, and continuous monitoring in accordance to NASA directives and guidance.

2. Addressing all applicable information security requirements, including vulnerability scanning and mitigation, maintaining secure operating system configuration, patch/configuration management, contingency planning, and protection of sensitive data in transit and at rest.

3. Information security, privacy, incident management and responses, including coordination with NASA Security Operations Center (SOC), Center Chief Information Security Officer (CISO), and Center Privacy Manager as required.

4. Ensure the Contractor employees meet information security requirements, such as information security awareness, rules of behavior, and elevated privilege training as required. Users are knowledgeable of NASA information security policies and procedures when handling NASA data.

FORMAT: The Contractor’s format is acceptable

1 electronic copy: Authorized Repository Authorized Repository Upload Notification: NASA Free Flyer Manager, NASA Contracting Officer, NASA FF Authorized Repository representative, others as negotiated

13. REMARKS: N/A

1a. DRD Title:

Information Technology Security Plan

2. Date of Current Version

3a. DRD No.

3b. RFP/Contract No.

4. Use (Define used for, intended use of, and/or anticipated results of data)

5. DRD Category

Technical

SR&QA

6. References (SOW Clause, etc.) SOW 2.1.3 FAR 52.204-21: Basic Safeguarding of Covered Contractor Information Systems NFS 1852.204-76: Security Requirements for Unclassified IT Resources NFS 1852.223-75: Major Breach of Safety or Security NFS 1852.237-72: Access to Sensitive Information NFS 1852.237-73L Release of Sensitive Information NPR 2810.1(series): Security of Information Technology.

OMB Circular A-130: Management of Federal Information Resources

7. Interrelationships (e.g., with other DRDs) DRD-011 Information Technology Security Management Plan

To provide Government insight into the Contractor’s methodology for managing all aspects of information security and to ensure critical components are addressed.

DATA REQUIREMENTS:

The Contractor shall develop, implement and maintain an ITSP for all systems provided or operated in performance of this contract as required in clause I.11, NFS 1852.204-76, Security Requirements for Unclassified Information Technology Resources.

The ITSP provides an overview of the security requirements of the system and describes the implementation details of the management, operational, and technical sec1urity controls in place or planned, and responsibilities and expected behavior of all individuals who access the system.

The ITSP, at a minimum, shall include the following:

a. Security categorization of the Information System

b. A description of the detailed implementation of the following classes of control:

1. Operational Controls - The security controls (i.e., safeguards or countermeasures) for an information system that are primarily implemented and executed by people (as opposed to systems).

2. Management Controls - Actions taken to manage the development, maintenance, and use of the system, including system-specific policies, procedures and rules of behavior, individual roles and responsibilities, individual accountability, and personnel security decisions.

3. Technical Controls - Security controls (i.e., safeguards or countermeasures) for an information system that are primarily implemented and executed by the information system through mechanisms contained in the hardware, software, or firmware components of the system. The controls can provide automated protection for unauthorized access or misuse, facilitate detection of security violations, and support security requirements for applications and data.

FORMAT: The Contractor’s format is acceptable

1 electronic copy: Authorized Repository Authorized Repository Upload Notification: NASA Free Flyer Manager, NASA Contracting Officer, NASA FF Authorized Repository representative, others as negotiated

13. REMARKS:

The DRD-011 ITSMP is required by Integration Milestone 01. The Government, after review of the ITSMP, will notify the Contractor of the need for an IT Security Plan (ITSP) and the associated due date. The ITSP will be in compliance with NFS 1852.204-76, Security Requirements For Unclassified Information Technology Resources (Jan 2011).

DATA REQUIREMENTS DESCRIPTION

(Based on JSC-STD-123) 1a. DRD Title:

Design, Development, Test, and Evaluation Plan

2. Date of Current Version

3a. DRD No.

3b. RFP/Contract No.

4. Use (Define used for, intended use of, and/or anticipated results of data) The Design, Development, Test, and Evaluation (DDT&E) Plan documents the contractor’s system level DDT&E methodology and processes, activities needed to develop and prove conformity with the technical specifications, perform design certification, and end item acceptance.

5. DRD Category

Administrative

SR&QA

6. References (SOW Clause, etc.)

SOW 2.4, 2.4.2, 2.4.4, 2.4.5, 3.2.1, 3.2.2, 3.2.3, 3.2.4

7. Interrelationships (e.g., with other DRDs)

The DDT&E plan documents the methods, processes, and process controls used to evolve the FF from design concepts into flight ready hardware.

DATA REQUIREMENTS:

The Contractor’s DDT&E plan shall contain, at a minimum the following:

a. Technical Overview, Objectives, and Constraints

1. System architecture description and phasing of subsystems

2. Identification of functions necessary for FF safety and mission success

3. NASA resources used, if any, and evolution of capabilities

b. Design and Development Processes

1. Design and construction standards

2. Materials selection

3. Supplier management approach identifying vendors, subcontractors, and partners

4. Use of COTS, heritage, and new component designs, tied to TRL maturity as applicable

5. Analysis in support of design verification

6. Technical plans for contamination control, parts management, environmental controls, and electromagnetic compatibility, as applicable.

c. Test, Evaluation, and Processes

1. Identification of system level test program requirements for testing of FF components

2. Description of the system level tests to be performed

3. Description of the Verification & Validation (V&V) plan to verify compliance with Contractor’s requirements, including:

i. Detailed verification methods and objectives

(a) Description of methods for hardware and software qualification, acceptance test plan and environmental testing;

ii. Approach for providing traceability of numbered verification closures to requirements and documenting the title, closure method, and completion date

iii. Software Independent Verification and Validation (IV&V) approach for software that directly controls safety critical operations performed by an established Government or commercial entity

4. Description of System Engineering plan defining the Contractor’s approach to technically manage the engineering and integration processes and products throughout the…