80JSC027R0004 Attachment J-02_CLDC Final RFP DRD.pdf

Request for Proposal (RFP) Commercial Low Earth Orbit (LEO) Destination Contract (CLDC)

PART III – ATTACHMENTS

SECTION J – LIST OF ATTACHMENTS

ATTACHMENT J-02 DATA REQUIREMENTS DESCRIPTIONS (DRDs)

CONTRACT DATA REQUIREMENTS LIST

National Aeronautics and Space Administration Johnson Space Center

1.0 INTRODUCTION

This document defines the requirements for contractual data to be delivered by the contractor to the Government. The data requirements are set forth in each Data Requirements Description (DRD) and shall govern that data required by the contract. The contractor shall furnish data defined by the DRDs as listed on the Contract Data Requirements List (CDRL) by category of data, attached hereto, and made a part of this contract. Such data shall be prepared, deliver, and maintain to NASA in accordance with the requirements set forth within this document.

This document sets forth the data requirements in each DRD and shall govern the data required under this contract. The Contractor shall furnish data defined by the DRDs listed by category of data. Such data shall be prepared, maintained, and delivered to National Aeronautics and Space Administration (NASA) in accordance with the requirements set forth herein. NASA-Owned/Contractor-Held records shall be managed by the Contractor in accordance with Title 36 of the Code of Federal Regulations, Chapter XII B. Records Management and NPD 1440.6, NASA Records Management. The records shall be organized in accordance with the instructions in NPR.1441.1, NASA Records Management Program Requirements as applicable. The Contractor shall disposition records and non-records in accordance with NPR 1441.1, which has been approved by NASA. All questions on records management issues shall be directed through the Contracting Officer or the Contracting Officer Representative.

2.0 ORGANIZATION OF CONTRACT DATA REQUIREMENTS LIST

Throughout the performance of the contract, the Contract Data Requirements List (CDRL) provides a listing by number, data type, title, and Office of Primary Responsibility (OPR).

Each DRD included in this CDRL prescribes content, format, and submittal requirements.

2.1 DRD NUMBERING

For the purpose of classification and control, the individual data deliverables in the CDRL are grouped into the following categories:

0XX series DRDs applicable to all contract activities 1XX series DRDs applicable to Contract Line-Item Number (CLIN) 1 Initial Development, CLIN 2 CLDS Development & Certification, Certification maintenance, and any re- Certification

2XX series DRDs applicable to CLIN 3 Mission Services

2.2 DATA TYPES

Each DRD is classified by data type as defined below:

TYPE DESCRIPTION

1 That information and documentation which requires NASA approval prior to release. Approved Type 1 information and documentation shall be controlled, and deviations from or changes to the concepts, techniques, and/or requirements stated therein shall require NASA approval prior to implementation. All work under this contract covered by Type 1 documents shall be performed in accordance with those approved documents. The Contracting Officer’s Representative has approval authority and signs the data prior to its release.

2 That information and documentation for which NASA reserves a time-limited right to disapprove. Type 2 has the same authority and control as listed for Type 1, however, the data shall be submitted to designated repository for review not less than 45 calendar days prior to its release for use or implementation. The Contractor shall clearly identify the target release date in the ‘submitted for review’ transmittal. If the Contractor has not received any comment prior to the target released date, the document may be released for appropriate use. Any NASA comment received shall be appropriately dispositioned and resubmitted prior to implementation, restarting the 45-day review period.

3 That information and documentation which does not require formal NASA review and approval. Information in this category would include statuses, analyses, test results, handbooks and other designated lists, reports, etc. While type 3 deliverables do not require NASA approval, the deliverable must satisfy all applicable contractual requirements.

2.3 DATA FIDELITY

In addition to the required frequency for data deliverable submittals, the DRD also defines the level of readiness/fidelity, which applies to the submission of DRDs:

Draft (D) - A preliminary version of a delivery for NASA review. Draft versions may contain some To Be Determined (TBD) items.

Baseline (B) - The Contractor’s internally approved version of the product. It must be of sufficient fidelity to permit NASA disposition in accordance with the DRD Type. Baseline submittals may contain some To Be Determined (TBD) items but are of higher fidelity than a Draft version.

Final (F) - A Final version of a delivery shall reflect the Contractor’s internally approved final version of the product and is ready for NASA disposition in accordance with the DRD Type.

No TBDs may be included.

3.0 STATEMENT OF GENERAL REQUIREMENTS

3.1 SUBCONTRACTOR DATA REQUIREMENT

The prime contractor is responsible for flowing down any specific data requirements that apply to subcontracts and vendor agreements.

Reference to subcontractor data in the contractor’s responses is permissible and a copy of the referenced subcontractor data must be supplied with the response document at time of delivery to NASA.

3.2 DATA DISTRIBUTION AND TRANSMITTAL

For DRD types 1, 2, and 3, the contractor shall electronically deliver DRDs to the CDO Program Authorized Repository as identified by the Contracting Officer. The contractor shall notify the distribution recipients when DRDs have been submitted to the CDO Program Authorized Repository. Distribution recipients are identified within each DRD Section 11.

Alternatively, for DRD types 1, 2, and 3, the contractor may propose alternative delivery methods or approaches aligned with their commercial processes subject to NASA approval.

All DRDs delivered through this method shall satisfy all applicable contractual requirements.

For each DRD, the transmittal package shall include:

1. Contract number

2. Task Order number (if applicable)

3. DRD number

4. DRD data type

5. Submission date

6. Milestone being satisfied (if applicable)

7. Document number, date and revision

8. Document title

9. File names of all files being delivered; file naming convention shall clearly identify the document being delivered; multiple files per document must be clearly related to the document

10. Distribution (Notification list as defined by the DRD distribution field)

11. Targeted release date

All Type 1 documentation shall be marked “PRELIMINARY PENDING NASA APPROVAL,” and once approved shall be reissued with “APPROVED BY NASA” and the date and approval authority annotated on the cover.

3.3 DATA FORMAT

Existing Contractor internal documents may be used to meet the data requirements of the DRD to the extent practicable. The DRDs will call out any special format requirements if they are required.

The data delivered shall include machine-readable metadata compliant with NASA-STD-2831, Metadata Standard for Data Discoverability. Any metadata element which applies a data rights classification shall apply the classification consistently with the data rights clauses in the contract, including applicable marking requirements. Data shall be versioned such that the Government can identify, retrieve, and reconcile any prior delivered state. The Government will ensure markings and data persist with the data through any export, transformation, or programmatic access.

The Contractor’s submittal in response to the DRDs shall be provided in an electronic format that meets four basic requirements: “Readable,” “Printable,” “Searchable,” 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 four basic requirements.

3.4 DATA RESTRICTION DETERMINATION AND MARKING REQUIREMENTS

The contractor shall properly mark data in accordance with the data rights clause(s) included in the contract. The contractor shall mark data deliverable sections with appropriate data restrictions and export classifications. The contractor shall not apply the most restrictive classification to the entire data delivery if only applicable to one section. If NASA does not agree with the contractor applied data restriction, the CO shall request supporting rationale for applied data restrictions. If NASA does not agree with the rationale, the CO 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 and per U.S. export laws.

The contractor shall ensure all Controlled but Unclassified Information (CUI) is marked in accordance with NASA Procedural Requirements (NPR) 2810.7, Controlled Unclassified Information and ITS-HBK-CUI, Controlled Unclassified Information Handbook.

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:

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

International Traffic in Arms Regulations (ITAR) Notice

This document contains information which falls under the purview of the United States (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 nationals, in the U.S. or abroad, without specific approval of a knowledgeable NASA export control official, and/or unless an export license/license exemption is obtained/available from the United States Department of State. Violations of these regulations are punishable by fine, imprisonment, or both.

4.0 DRD MAINTENANCE PROCEDURES

4.1 CONFIGURATION MANAGEMENT OF DRDs

The Contractor shall employ a system for organizing, identifying, and tracking all submittals of DRDs, to include any changes or revisions. Updates to DRDs shall be incorporated by resubmission of the document. Changes shall be incorporated by complete reissue with a change log in the front matter of the document.

If the DRD is a Type 1 or Type 2 DRD, DRD deliverable submittals shall include two versions 1) a clean copy with redlines incorporated 2) and Redlined version showing the updates made since the last submittal.

4.2 CDRL OR DRD CHANGE PROCEDURES

Revisions to the CDRL or DRDs will be identified by NASA in the Document Change Log. The date of the revision, DRD number, title, and revision description will be annotated in the Document Change Log. Revision descriptions will include the modification number, which implements the change, and a brief description of the portions of the CDRL and/or DRD affected within the “Revision” column of the Document Change Log.

5.0 REFERENCE TO OTHER DOCUMENTS AND DATA DELIVERABLES IN

DATA SUBMITTALS

The Contractor’s submittal of a DRD deliverable may refer to other documents and/or other DRD deliverables. At the time of submission of the DRD deliverable, any referenced document within the DRD deliverable 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 deliverable that is required separately by the contract, shall include the DRD number of and location of the data within the referenced DRD deliverable.

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 nationals in the U.S. or abroad without specific approval of a knowledgeable NASA export control official, and/or unless an export license/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.

Insert Destination Control Statement that includes export classification and corresponding export authority.

6.0 DATA REQUIREMENTS LIST (DRL)

DRD # DRD Title Ty pe

O

PR

Pr op os al

C on tr ac t A w ar d

C

BR PD

R

C D

R

M

TR

R

SS

R

SI

R

A

PR

D C

R

SC

R

M

BR

/V

BR

(L -1

8m

M

IR

(L -1

2m

U

IR

(L -6 m

FO

R

(L -4 m

C

IR

(L -3 m

M C

R (L

-3 m

O R

R (L

-1 m

FR

R

(L -1 w

PF

R

PI

R

(I +6

0d

Notes:

D=Draft

B = Baseline F = Final

CA = Contract Award m=months; w=weeks;

d=days CLDC-001 Integrated Master Schedule 3 CDO D CLDC-002 Commercialization Plan 2 CDO B CLDC-003 Organizational Conflicts of Interest (OCI) Plan 1 CDO B F+30d

CLDC-004 RESERVED

CLDC-005 Export Control Plan 2 CDO B+30d CLDC-006 Configuration Management Plan 2 CDO B F CLDC-007 Environmental Compliance Reports 3 CDO If applicable CLDC-008 Small Business Subcontracting Plan and Reports 1 CDO F CLDC-009 Commercial Activities Management Plan 1 CDO B F CLDC-010 Government Property Management Plan 2 CDO F+30d If applicable

CLDC-011 RESERVED

CLDC-012 Information Technology (IT) Capital Planning and Investment Control (CPIC) 2 CDO CLDC-013 Commercial IT Authorization Report 3 CDO B+90d CLDC-014 Security Requirements for Unclassified IT Resources 2 CDO CLDC-015 Program Management Plan 2 CDO F

CLDC-101 Systems Engineering Management Plan 2 CDO B

F+60d CLDC-102 Verification, Validation, and Certification Plan 1 CDO D B F CLDC-103 NASA Standards and Specifications Compliance and Tailoring 1 CDO D B F CLDC-104 Insight and Collaboration Implementation Plan 1 CDO B F CLDC-105 Integrated Performance Analysis and Integrated Testing Plan 1 CDO B F CLDC-106 Verification Closure Notice (VCN) 1 CDO F F CLDC-107 Software Management Plan 1 CDO B B F CLDC-108 Human Systems Integration (HSI) 2,3 CDO

CLDC-108.1 HSI Plan 2 CDO B F CLDC-108.2 Task Analysis 3 CDO B F CLDC-108.3 HITL Summary Report 3 CDO F

CLDC-109 Human Error Analysis 2,3 CDO CLDC-109.1 HEA Plan 2 CDO B F CLDC-109.2 HEA Results and Reports 3 CDO B F

CLDC-110 Acoustics Noise Control Plan 3 CDO F CLDC-111 Medical Operations Plan 1 CDO B F CLDC-112 Food and Nutrition Plan 1 CDO B F CLDC-113 Health Stabilization Program (HSP) Plan 2 CDO B F CLDC-114 Medical and Crew Health System Plan 2 CDO B F

Delivery/Update Frequency

IMS Monthly; SRA at CLIN 1 and CLIN 2 Certification milestones Updated Quarterly

Reviewed and Updated Annually, if Required

See DRD

Annually by Dec 1st See DRD

See DRD Monthly on the 15th of each month

DRD # DRD Title Ty pe

O

PR

Pr op os al

C on tr ac t A w ar d

C

BR PD

R

C D

R

M

TR

R

SS

R

SI

R

A

PR

D C

R

SC

R

M

BR

/V

BR

(L -1

8m

M

IR

(L -1

2m

U

IR

(L -6 m

FO

R

(L -4 m

C

IR

(L -3 m

M C

R (L

-3 m

O R

R (L

-1 m

FR

R

(L -1 w

PF

R

PI

R

(I +6

0d

Notes:

D=Draft

B = Baseline F = Final

CA = Contract Award m=months; w=weeks;

d=days CLDC-115 Safety & Mission Assurance (SMA) Plan 1 CDO

CLDC-115.1 Destination SMA Plan 1 CDO D B F CLDC-115.2 Crew Visiting Vehicle (CVV) SMA Plan 1 CDO F CLDC-115.3 Cargo Visiting Vehicle (CaVV) SMA Plan 1 CDO F

CLDC-116 Risk Management Plan 2 CDO D B F CLDC-117 Mishap Preparedness and Contingency Plan (MPCP) 2 CDO B F CLDC-118 Safety Data Package 1 CDO CLDC-119 Micrometeoroid Orbital Debris (MMOD) Report 1 CDO

CLDC-119.1 Destination MMOD Report 1 CDO B^ F ^ Baseline six months prior to CDR; UAR at CDR

CLDC-119.2 CVV MMOD Report 1 CDO B^ F ^ Baseline six months prior to CDR; UAR at CDR

CLDC-119.3 CaVV MMOD Report 1 CDO B^ F ^ Baseline six months prior to CDR; UAR at CDR CLDC-120 Jettison Plan 1 CDO B F

CLDC-121 Non-Conformance (NC) Reporting 3 CDO CA+ 90d Contract Award +90 days;

Quarterly thereafter CLDC-122 Supply Chain Visibility (SCV) Reporting 3 CDO CA+ 30d CLDC-123 Destination Disposal Plan 1 CDO B F CLDC-124 Utilization Integration Plan 1 CDO B F CLDC-125 Payload Users Guide 3 CDO B F CLDC-126 Science Data Management Plan 1 CDO B F CLDC-127 Mission Systems Plan 1 CDO B F CLDC-128 Operations and Training Plan 1 CDO B CLDC-129 Crew Code of Conduct 1 CDO D B F CLDC-130 Crew Selection and Evaluation Plan 1 CDO B F CLDC-131 Pre-Launch and Post-Landing Operations 1 CDO B F CLDC-132 Vehicle Interface Definition Document (IDD) 3 CDO

CLDC-132.1 Destination Vehicle IDD 3 CDO B F CLDC-132.2 Crew Visiting Vehicle (CVV) IDD 3 CDO B F CLDC-132.3 Cargo Visiting Vehicle (CaVV) IDD 3 CDO B F

CLDC-133 Integrated Logistics and Maintenance Support 1,3 CDO CLDC-133.1 ILMS Plan 1 CDO B F CLDC-133.2 ILMS Data 3 CDO B F

CLDC-201 Mission Integration and Operations Management Plan (MIOMP) 2 CDO CLDC-201.1 Destination Mission Integration and Management Plan (MIMP) 2 CDO D B F CLDC-201.2 Crew Transportation MIOMP 2 CDO B F CLDC-201.3 Cargo Transportation MIOMP 2 CDO B F

Delivery/Update Frequency

Thirty (30) days prior to each Safety Review

Quarterly

Every 6 months thereafter

Final due one year prior to start of crew training of first mission

DRD # DRD Title

T yp e

O

PR

Pr op os al

C on tr ac t A w ar d

C B

R

PD

R

C D

R

M T

R R

SS

R

SI

R

A

PR

D C

R

SC

R

M B

R /V

B R

(L -1

8m

M

IR

(L -1

2m

U

IR

(L -6 m

FO

U

R (L

-4 m

C

IR

(L -3 m

M C

R (L

-3 m

O R

R (L

-1 m

FR

R

(L -1 w

PF

R

PI

R

(I +6

0d

Notes:

D=Draft

B = Baseline F = Final

CA = Contract Award m=months; w=weeks;

d=days CLDC-202 Mission Resource Allocation Document (MRAD) 2,3 CDO

CLDC-202.1 Crew Visiting Vehicle MRAD 2,3 CDO See DRD for addt'l deliveries CLDC-202.2 Cargo Visiting Vehicle MRAD 2,3 CDO

CLDC-203 Tactical Increment Execution Report (TIER) 2,3 CDO B F CLDC-204 Imagery Plan 2/3 CDO B F CLDC-205 Post Increment Report 2 CDO CLDC-206 Visiting Vehicle Post Flight Report 2 CDO

CLDC-206.1 CTS Post Flight Report 2 CDO CLDC-206.2 CaTS Post Flight Report 2 CDO

CLDC-207 Utilization Feasibility Assessment 2 CDO CLDC-207.1 Individual Payload Feasibility Assessment 2 CDO F B: See DRD CLDC-207.2 Payload Complement Feasibility Assessment 2 CDO B F

CLDC-208 Payloads Interface Requirements Document (IRD) 1 CDO

CLDC-208.1 Payloads/Destination Interface Requirements Document 1 CDO B F F B Applicability Matrix 6 weeks after payload kickoff meeting

CLDC-208.2 Payloads/CVV Interface Requirements Document 1 CDO B F F B Applicability Matrix 6 weeks after payload kickoff meeting

CLDC-208.3 Payloads/CaVV Interface Requirements Document 1 CDO B F F B Applicability Matrix 6 weeks after payload kickoff meeting

CLDC-209 Unique Payload Interface Control Document (ICD) 1 CDO

CLDC-209.1 [Unique Payload] to [Destination] Interface Control Document (ICD) 1 CDO F Baseline ICD 3 mo. after the payload kickoff meeting;

Final at MIR

CLDC-209.2

[Unique Payload] to Crew Visiting Vehicle (CVV) Interface Control Document

(ICD)

1 CDO F

Baseline ICD 3 mo. after the payload kickoff meeting;

Final at MIR

CLDC-209.3

[Unique Payload] to Cargo Visiting Vehicle (CaVV) Interface Control Document

(ICD)

1 CDO F

Baseline ICD 3 mo. after the payload kickoff meeting;

Final at MIR

CLDC-210 Crew Specific Activities 2,3 CDO CLDC-210.1 Crew Selection Evaluation 2 CDO CLDC-210.2 Crew Mission Evaluation 2 CDO CLDC-210.3 Signed Crew Code of Conduct and Informed Consent 3 CDO

CLDC-211 Destination to Visiting Vehicle (VV) Integration (DVVI) Documentation 1,2,3 CDO CLDC-211.1 DVVI Plan 1 CDO B F CLDC-211.2 DVVI Interface Requirements Document (IRD) 1 CDO B F CLDC-211.3 DVVI Data Set 3 CDO CLDC-211.4 DVVI Interface Control Document (ICD) 2 CDO B F

CLDC-212 Crew Accommodations Plan 2 CDO B F

Delivery/Update Frequency

See DRD See DRD

To be negotiated

See DRD

See DRD

Baseline 14d after Increment; Final 45d after Increment

See DRD

1. DRD Title: Integrated Master Schedule (IMS)

2. DRD No.: CLDC-001 3. Data Type: 3 4. OPR: CDO

5. Solicitation No.: 80JSC027R0004

6. Contract No.: (Insert contract number)

7. Date Issued: Insert the date the baseline was issued.

8. Date Revised: Include the revision date (if this DRD has been revised)

9. DRD Category:

Technical ☐ Administrative ☒

S&MA ☐

10. Description/Use: To provide NASA the Contractor’s integrated program schedules using established standard processes, data structures and reporting conventions to plan, manage, and report the work required in the performance of this contract.

11. Distribution:

One (1) Electronic Copy to the Commercial Destination Office (CDO) Program Authorized Repository Send a Program Authorized Repository Upload Notification to:

1. NASA Contracting Officer (CO)

2. NASA CDO Contracting Officer Representative (COR) and Alternate COR

Initial Submission: The Draft IMS shall be due at proposal with the contents below:

• Native Schedule File, referred to as Integrated Master Schedule (IMS) through the full period of performance

• Native Schedule File Data Dictionary

• Schedule Assumptions

• Summary Master Schedule

• Schedule Risk Assessment (SRA)

Submission Frequency: The Integrated Master Schedule (IMS) shall be delivered monthly and no later than the 5th Government working day of the month. An updated Native Schedule Data Dictionary and Schedule Assumptions are required for any change following the initial submission due with the first affected IMS deliverable.

Subsequent SRA shall be delivered:

• As part of CLIN 1 and CLIN 2 Certification milestones

Format: Native Schedule File and the Schedule Risk Assessment shall be delivered in Microsoft Project format and/or NASA approved format. For other data item deliverables, the Contractor’s format is acceptable and shall be in accordance with the Data Format section at the beginning of this attachment.

Interrelationship: Statement Of Work (SOW) Section 2.4 Schedule Management

Applicable Documents:

• Government Accountability Office (GAO) Schedule Assessment Guide o https://www.gao.gov/assets/690/687052.pdf

Scope: The Integrated Master Schedule data contains:

1. Schedule: Integrated Master Schedule (IMS)

2. Native Schedule File Data Dictionary - Lists all defined fields, definitions, and code https://www.gao.gov/assets/690/687052.pdf structures used within the Native Schedule File

3. Schedule Assumptions – Lists all major assumptions used to develop the IMS

4. Summary Master Schedule - A one-page, top level, Gantt-type schedule chart traceable to the

IMS that summarizes the contracted effort including major milestones, critical path, and schedule margin

5. Schedule Risk Assessment (SRA) - Provides probability of meeting contractual delivery dates

Contents:

1. Schedule:

a. The IMS is an integrated, logically driven, network-based schedule that is vertically and horizontally traceable. Tasks should be at a level of detail to allow for discrete progress measurement and shall include visibility into the overall development flow which typically includes design, fabrication, assembly, integration, test, and delivery phase of each end item delivery. (Note – Task/milestone titles should be clear, concise, and reflect the scope and output (i.e., deliverable) so that the task content can be understood as standalone data without its associated summary level task also being shown.) Expectation for schedule quality is to follow GAO schedule best practices and schedule health checks.

b. Tasks and milestones from subcontractors and the commercial transportation vehicle providers shall be included within the prime contractor’s IMS with sufficient detail to develop a realistic critical path. Their data shall be consistent, statused monthly, and based on the same cutoff date to enable a realistic critical path.

c. The IMS shall have traceability to a Contractor specified Work Breakdown Structure (WBS) (or equivalent), subcontractor activity, and the Performance Work Statement.

This traceability should be accomplished by using data fields provided within the scheduling tool.

d. Custom/User-Defined Fields: Contractor shall reserve 7 schedule fields for the purpose of helping the Government navigate, analyze, and health-check the IMS. Fields shall include Schedule Margin, Lifecycle Review, Payment Milestones, Government Task Agreements (GTA)/Government Furnished Equipment (GFE), Critical Path, Mission Critical items (as defined by NASA), and Major Supplier Activity.

e. The IMS shall clearly identify tasks or activities which have a dependency on a NASA delivery or approval (for example, delivery of a GFE), and the availability of a NASA facility.

f. If schedule margin is included in the IMS, it shall be as a defined task and clearly labeled as “Schedule Margin” or “Contingency”. (Note - Schedule margin is a determined amount of time that has been added to the schedule by the management team and is to be used and controlled by the project manager to buffer against future impacts that are impossible to predict.)

g. The IMS should contain Level of Effort (LOE) identification. If LOE tasks (i.e., management, miscellaneous support, monitoring, etc.) are included within the IMS they should be clearly labeled as such. If LOE tasks are included, they shall be added in a manner that does not impact discrete tasks/milestones.

h. Critical Path: The schedule tool shall automatically calculate the longest path in the Native Schedule File. If multiple critical paths are identified, the primary, secondary, and tertiary critical paths should be identified using a custom field for Critical Path.

i. Constraints: The IMS should use minimal constraints. However, if constraints are used, the IMS shall identify the constraints (including any deadlines) applied to tasks.

Provide justification for all constraints external to the Native Schedule file.

j. Leads/Lags: The IMS should minimize use of leads/lags duration. However, if leads/lags are used, the IMS shall provide justification.

k. Fixed Unique Identifiers (UIDs) for activities (Text field if needed) shall be traceable from month to month; UIDs should not change or be reused for another activity.

l. Maximum activity durations should not exceed 60 calendar days. If an activity exceeds 60 calendar days, provide justification.

2. Schedule Risk Assessment (SRA)

Report shall include:

a. The SRA shall be accomplished using a standard probabilistic management tool with

Monte-Carlo functionality. The results of the SRA must include the probability of meeting contractual deliveries and milestones in histogram/S-curve formats.

b. The SRA results should include rank order of both the risks and tasks affecting the completion of contractual milestones and deliverables.

Maintenance: Updates to this document shall be incorporated by resubmission of the document. Changes shall be incorporated by complete reissue with a change log in the front matter of the document.

1. DRD Title: Commercialization Plan

2. DRD No.: CLDC-002 3. Data Type: 2 4. OPR: CDO

9. DRD Category:

Technical ☐ Administrative ☒

S&MA ☐

10. Description/Use: The purpose of the Commercialization Plan is to describe the approach the Contractor plans, if any, to engage with commercial entities in partnerships for the purposes of creating additional revenue streams for the completion of the Commercial Low Earth Orbit (LEO) Destination Contract (CLDC). Additionally, the plan intends to better understand the Contractor’s overall financial health and business plan. The CLDC Commercialization Plan will provide details necessary to ensure the proposed plan and financial status is reasonable and is in line with the proposed mission cost and cost levied to NASA.

11. Distribution:

One (1) Electronic Copy to the Commercial Destination Office (CDO) Program Authorized Repository Send a Program Authorized Repository Upload Notification to:

Initial Submission: Baseline with Proposal (Section 1, 2d, 5, 6, 8-11).

Submission Frequency: All Sections Submitted and Updated Quarterly; unless otherwise noted

Format: The Contractor’s format is acceptable and shall be in accordance with the Data Format section at the beginning of this attachment.

Interrelationship: Statement Of Work (SOW) Section 2.1 Program Management

Applicable Documents: None

Scope: The Commercialization Plan describes the Contractors’ financial status, CLD Market Opportunities, the financial assumptions/requirements, how the contractor is going to provide the service to the Market Opportunities and the revenue forecast from non-NASA entities.

Contents:

The Commercialization Plan establishes measurable performance goals and metrics measured against the contractors overall commercial segment business plan and defines the following:

1. Finance Plan that executes the scope of the CLDC contract in addition to payments made by NASA under the CLDC contract. Includes:

a. Explanation of financial goals or fund raising (venture capital, partnerships, etc.)

b. Sources of planned funding, including breakdowns of planned debt and equity sources, and details on the level of commitment(s), if any, obtained from these sources.

c. Explanation of risks assumed by this financing plan and the planned approach to mitigating these risks to ensure continued successful performance under the contract.

d. Finance Plan Milestones and schedule of milestone completion

e. Complete Company Ownership Structure, including parent company ownership above the contracting entity.

2. Financial Due Diligence documentation:

a. Officer-certified balance sheets, income and cash flow statements, changes in equity

b. Capital expenditures plans and performance to plan

c. Liquidity runway to outline available cash, including committed but undrawn capital, and monthly burn rate/(24-month outlook)

d. Workforce Overview

i. Summary level staffing plan vs. actuals, by quantity and discipline/skill mix mapped to each major system or milestone.

ii. Summary level is defined as not requiring subcontractor or partner level specific identification within the plan, but requires the total allocated headcount

3. Performance-to-plan for stated goals and metrics as defined by actual performance to plan which includes supplier and investor commitments, contracts, revenue, investments, financing, expenditures, and obligations. Revenue shall be broken down and at least include details associated with number of seat sales and payload service sales, and their respective pricing. This should contain monthly and cum-to-date performance.

4. Variance analysis, including narrative explanation for major contributors, for planned vs. actual performance.

5. Forecasted plan for the next year, including expected supplier and investor commitments, contracts, revenue, investments, financing, expenditures, obligations, and variance recovery plans. Forecasts shall map to and explain how they are in alignment with the IMS. The forecast shall have the functionality to be mapped by module (if using a multi module architecture).

6. Revenue Forecast for 10 years

a. Revenue Generation Forecast for CLD Commercialization Opportunities (non-NASA)

i. Including secured, probable and at risk/speculative revenue

b. Correlation between Revenue Generation Forecast and Finance Plan

i. To fully understand its risk posture, NASA needs to understand the correlation between the Revenue Generation Forecast and the fund raising/financial goals of the CLD Contractor.

7. Year-end financial report (format provided to investors/shareholders). Submitted annually.

8. Significant or impacting updates, changes, and risks to life-cycle planning, including finances, schedule, vendor selection, revenue strategy, major expenditures, etc.

9. Portfolio of products and services to be demonstrated and offered, including timing, and pricing strategy (if updated). In addition to the overall pricing strategy, nominal/generic pricing tables shall be provided outlining general mission services pricing. This pricing shall be utilized to evaluate fair market pricing in accordance with H.33 American Taxpayer Protections. Pricing tables may include differential pricing based on the type of services provided for crew seats/accommodations, cargo/payload services, mission specific deliverables or other differences. The Contractor shall propose process and frequency for providing NASA insight on working level details associated with negotiated agreements or barters with sovereign nations and third parties required to mitigate concerns with meeting H.33 American Taxpayer Protections.

10. Business Development progress in capturing and creating growth in non-NASA markets including a status of commercial opportunities including direct sales to 3rd party operators. Status should include information on signed contracts, Letters of commitment, etc. but may omit customer identities or contract terms and conditions.

11. List of all major subcontractors, vendors, suppliers and partners, including barters and trades, performing work with a value over $100M or lower level submissions are required if scope is in the critical path, describing the scope of agreement, and status of signed contracts and agreements with each, as well as Subcontracting and Partnership forward plans.

Remarks: To the extent permitted by law, NASA will protect information submitted within this DRD as confidential financial information. Access will be strictly limited to the Contracting Officer, Contracting Officer Representative and personnel with a need-to-know.

For completeness, please ensure the following metrics are highlighted in your financial statements:

Metric Source Revenue Income Statement Cost of Goods Sold Income Statement Gross Margin (Contribution) Income Statement Net Income Income Statement Current Assets Balance Sheet Current Liabilities Balance Sheet Total Assets Prior Year Balance Sheet Total Assets Balance Sheet Total Liabilities Balance Sheet Long Term Debt Balance Sheet Operating Cash Flow Cashflow Statement/Income Statement Diluted Shares Outstanding Balance Sheet Retained Earnings Balance Sheet Market Capitalization Balance Sheet Total Equity Balance Sheet Working Capital Balance Sheet EBITDA Income Statement

Maintenance: Updates to this document shall be incorporated by resubmission of the document. DRD deliverable submittals shall include two versions 1) a clean copy with redlines incorporated and 2) Redlined version showing the updates made since the last submittal or the Contractor may submit delta/change-page submissions with a change log in lieu of complete quarterly reissue.

1. DRD Title: Organizational Conflicts of Interest (OCI) Plan

2. DRD No.: CLDC-003 3. Data Type: 1 4. OPR: CDO

7. Date Issued: To be filled in by CO at contract award

8. Date Revised: To be filled in by CO at first revision of this DRD after contract award

9. DRD Category:

Technical ☐ Administrative ☒

S&MA ☐

10. Description/Use: The OCI Plan will communicate the Contractor’s approach to identify and resolve OCIs. The Contractor will be held accountable for identifying, dispositioning, and reporting OCIs during contract performance.

11. Distribution:

One (1) electronic copy to the Commercial Destination Office (CDO) Program Authorized Repository Send a Program Authorized Repository Upload Notification to:

Initial Submission: Baseline Plan shall be submitted with the initial proposal.

Submission Frequency: Final Plan shall be delivered 30 calendar days after Contract Award.

Subsequently, if updates are required.

Update when contractor teaming arrangements change and when new or potential OCI issues occur.

Respond to CO with each Task Order Proposal whether update to the plan is required.

Updated when requested by CO.

Format: The Contractor’s format is acceptable and shall be in accordance with Data Format section at the beginning of this attachment.

Interrelationship:

• Statement Of Work (SOW) Section 2.1 Program Management

• Clause NFS 1852.237-72, Access to Sensitive Information (DEC 2025) (DEVIATION)

• Clause NFS 1852.237-73, Release of Sensitive Information (DEC 2025) (DEVIATION)

• Clause FAR 52.203-13, Contractor Code of Business Ethics and Conduct (NOV 2021)

Applicable Documents:

• Federal Acquisition Regulation (FAR) Subpart 9.5, Organizational and Consultant Conflicts of Interest

• NASA FAR Supplement (NFS) 1809.500, Organizational and Consultant Conflicts of Interest.

Scope: The OCI Plan describes the contractor’s comprehensive approach to identify, avoid, mitigate, neutralize, and report potential OCI issues, including conflicts described in the solicitation and those discovered during contract performance.

Contents: The Organizational Conflicts of Interest (OCI) Plan shall meet the requirements of FAR Subpart 9.5, Organizational and Consultant Conflicts of Interest and include the following:

1. Point of contact for OCI issues and reports.

2. Demonstrate an understanding of (1) OCI principles and (2) the full breadth of OCI issues and the types of harm that can result. The Plan at a minimum addresses the three primary types of OCIs (i.e., biased ground rules, unequal access to information, and impaired objectivity).

3. Define company roles, responsibilities, and procedures for (1) screening (i.e., identifying/recognizing, analyzing/evaluating, resolving, and reporting) existing and new business opportunities for actual/potential OCIs and (2) monitoring and reporting all potential/actual OCIs that arise, resolving conflicts, and reporting previously unidentified OCIs or potential OCIs to the Government.

4. Describe how employees are notified of the Plan’s requirements and how this notification will be documented. Describe the training to be provided to Contractor and subcontractor personnel regarding potential OCIs on this contract. Establish and require entrance training for new employees, refresher training for existing employees, and exit training for departing employees. Describe how completion of this training will be documented, including a copy of any training certification template that the contractor will use to document that its employees have completed training.

5. Describe how the contractor will report breaches of the protective measures in the Plan to the Contracting CO. Describe what processes the contractor will implement following any breach and indicate that final resolution of the corrective action must be approved by the CO.

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

7. Address the process for reporting all potential/actual OCIs that arise during performance of the contract to the CO. An OCI report shall include:

a. a description of the conflict,

b. the plan for resolving the conflict, and

c. the benefits/risks to contract performance associated with plan approval/acceptance.

8. Specific resolution strategies shall be appended to the Plan upon approval by the CO.

9. Explain how the contractor will flow down the provisions of this Plan to any subcontractor that may have a conflict with regard to performing the requirements of this contract. Discuss affected subcontractors’ OCI program as it relates to this contract and specifically explain how affected subcontractors will identify, resolve, and report actual/potential OCIs associated with this contract.

10. Define organizational and employee sanctions for violations of established OCI procedures/requirements/guidelines.

11. Include an assertion from the Contractor that to the best of their knowledge no OCIs exist currently, if applicable. Provide a list of all the prime and subcontractor’s current contracts and subcontracts (NASA and non-NASA) with a description of the work performed, which would provide the CO a better understanding of other work performed by the Offeror that may give rise to an actual or potential conflict.

For each prime contract and subcontract listed, the offeror shall: (1) identify the contract number; (2) describe the scope of work in sufficient detail to ascertain the likelihood of a conflict with performance of this contract; and (3) discuss any conflicts that may arise from performance of the listed contracts and award of this contract.

12. For financial or other interests or relationships beyond Federal contracts or subcontracts that may give rise to an OCI, the offeror shall (1) address the nature and extent of the interest(s) or relationship(s); (2) list any entity or entities involved in the interest(s) or relationship(s) and award of this contract.

13. The Contractor shall address how it will avoid, neutralize, or mitigate each potential OCI listed above. Sufficient information must be provided to allow a meaningful evaluation of the potential effect of the interest on the performance of the SOW.

14. Include a requirement to update this plan as necessary to address specific OCIs. All updates to the plan must be approved by the contracting officer and the updates/changes must be incorporated in the contract to be effective.

15. Require periodic self-audits to ensure compliance with established OCI procedures/requirements/guidelines.

16. Define records related to the OCI plan (e.g., training and audit records) that will be made available to the Government upon request. Note: The OCI Plan as outlined in this DRD is not for the purpose of addressing other very important contractual obligations such as (1) the contractor’s obligation to protect sensitive information in accordance with NFS 1852.237-72, Access to Sensitive Information (DEVIATION) (DEC 2025), (2) the contractor’s obligation to conduct business in an ethical manner in accordance with FAR 52.203-13, Contractor’s Code of Business Ethics and Conduct, and (3) the contractor’s obligation to prevent personal conflicts of interest in accordance with FAR 52.203-16, Preventing Personal Conflicts of Interest.

17. In an appendix to the OCI Plan identify the strategy (e.g., mitigation, limitation on future contracting) for resolving each OCI that is either identified in the solicitation or created by the requirements of the solicitation/contract and explain the effect of such strategy on performance of the contract. If using a firewall, explain how these actions will operate to successfully address the conflict without adversely affecting performance of the contract.

Remarks: The final plan, as approved, shall be incorporated in the contract as Attachment J-07, Organizational Conflicts of Interest (OCI) Plan.

Maintenance: Updates to this document shall be incorporated by resubmission of the document. DRD deliverable submittals shall include two versions 1) a clean copy with redlines incorporated and 2) Redlined version showing the updates made since the last submittal.

1. DRD Title: RESERVED

2. DRD No.: CLDC-004 3. Data Type: 4. OPR: CDO

9. DRD Category:

Technical ☐ Administrative ☐

S&MA ☐

10. Description/Use:

11. Distribution:

Initial Submission:

Submission Frequency:

Format:

Interrelationship:

Applicable Documents:

Scope:

Contents:

Remarks:

Maintenance:

1. DRD Title: Export Control Plan

2. DRD No.: CLDC-005 3. Data Type: 2 4. OPR: CDO

9. DRD Category:

Technical ☐ Administrative ☒

S&MA ☐

10. Description/Use: Describes the Contractor’s approach for Export Control activities that involve the transfer of commodities, software, technical data, technology, defense services, and/or technical assistance to foreign entities related to the performance of contract requirements. Export Control transactions are regulated by export control laws to protect U.S. national security interests and to further U.S. foreign policy objectives. These are primarily codified in the International Traffic in Arms Regulations (ITAR) 22 CFR pts.

120-130 and the Export Administration Regulations (EAR), 15 CFR pts. 730-774, that are administered by the Departments of State and Commerce, respectively.

11. Distribution:

One (1) Electronic Copy to the Commercial Destination Office (CDO) Authorized Repository.

Send a Program Authorized Repository Upload Notification to:

Initial Submission: Baseline due thirty (30) calendar days after contract award

Submission Frequency: The plan shall be reviewed annually for currency and submitted by September 30th if updates are required to reflect changes to the plan. If no changes to the plan are required, the Contractor shall submit a delivery Notice to indicating this.

Format: The Contractor’s format is acceptable and shall be in accordance with Data Format section at the beginning of this attachment

Interrelationship: Statement Of Work (SOW) 2.6 Export Control NFS 1825.603-70 Export Control NFS 1852.225-70 Export Licenses

Applicable Documents:

• NPR 2190.1, NASA Export Control Program

• NPD 2190.1, NASA Export Control Program

• NAII 2190.1, NASA NASA Export Control Program Operations Manual

• JWI 2190.1, JSC Work Instruction, JSC Export Compliance

• JAII 2190.1, JSC Advisory Implementing Instruction, Export Services Team (EST) Operations

Manual

Scope: The plan shall describe export control activities related to performance of contract requirements.

Contents:

The Contractor shall prepare and submit an Export Control Plan (ECP), describing the Contractor’s planned approach for accomplishing contract functions while adhering to export laws, regulations, and directives, including International Traffic in Arms Regulations (ITAR) and Export Administration Regulations (EAR).

The plan shall include an explanation of expected exports, approval process and authorities used, and managing of foreign nationals in complying with export control laws.

The ECP shall address these elements of their export control program:

Element 1: MANAGEMENT COMMITMENT Element 2: RISK ASSESSMENT Element 3: EXPORT AUTHORIZATION Element 4: RECORDKEEPING Element 5: TRAINING Element 6: AUDITS Element 7: HANDLING EXPORT VIOLATIONS & TAKING CORRECTIVE ACTIONS

Remarks: None

Updates to this document shall be incorporated by resubmission of the document. DRD deliverable submittals shall include two versions 1) a clean copy with redlines incorporated and 2) Redlined version showing the updates made since the last submittal.

1. DRD Title: Configuration Management Plan

2. DRD No.: CLDC-006 3. Data Type: 2 4. OPR: CDO

5. Solicitation No.:80JSC027R0004

9. DRD Category:

Technical ☐ Administrative ☒

S&MA ☐

10. Description/Use: This plan shall describe the assignment of responsibility organizationally and the procedures used in the accomplishment of the specific Configuration Management (CM) requirements, processes, and procedures, as stated in the Statement Of Work (SOW).

11. Distribution:

One (1) Electronic Copy to the Commercial Destination Office (CDO) Authorized Repository.

Send a Program Authorized Repository Upload Notification to:

Initial Submission: Baseline (B) at Certification Baseline Review (CBR)

Submission Frequency: Final (F) at Critical Design Review (CDR). Update as required to reflect changes that affect CM implementation.

Format: The contractor’s format is acceptable and shall be in accordance with the Data Format section at the beginning of this attachment

Interrelationship: Statement Of Work (SOW) Section 2.8 Configuration Management

Applicable Documents:

• SAE-EIA-649-2A Configuration Management Acquisition Requirements for Aeronautics and Space

• SAE AS9100 Quality Management System Requirements for Aviation, Space, and Defense

Organizations

Scope: The CM Plan defines the requirements, responsibilities, and processes and procedures for the Contractor's CM system pursuant to SAE-EIA-649-2A Configuration Management Acquisition Requirements for Aeronautics and Space and SAE AS9100 Quality Management System Requirements for Aviation, Space, and Defense Organizations. The CM plan shall describe in relation to the elements below to the Contractor’s CM organization, policies, procedures, implementation approach, and control systems that are to be used to ensure proper performance of CM activities. The CM plan shall also describe the configuration management activities, policies, and systems to be employed to support the NASA change evaluation and control process for the approval of program requirements as well as for the submission of Variances.

Contents: The Configuration Management (CM) Plan shall address, at a minimum, the following:

1. Management Organization

a. Responsibility and authority for CM including roles in configuration control boards and technical reviews.

b. Interface between contractor’s CM organization and NASA, subcontractors, and other contractor’s/contracts, including remote access for NASA and NASA support contractors.

2. Configuration Identification

a. Selection of Configuration Items (CIs) (hardware, Computer Software Configuration Items [CSCIs], and firmware).

b. Establishment of the functional, allocated, and product baselines for hardware and software.

c. Assignment of configuration identifiers including serial numbers, part numbers, lot codes, software, and firmware identifiers.

3. Configuration Control

a. Establishment of internal configuration and contractual baselines.

b. Implementation of internal configuration control.

c. Establishment of configuration control boards and processes.

d. Identification of processes to control changes, and variances to program baselines.

4. Configuration Status Accounting

a. Hardware/Software configuration Status Accounting processes and provisions for reports and/or access to Configuration Status Accounting data.

b. Description and methods of processes and tools to provide:

i. Identification of current approved configuration documentation and configuration identifiers associated with each CI.

ii. Status of proposed engineering changes from initiation to implementation.

iii. Variance status and processing.

iv. Results of configuration audits; status and disposition of discrepancies.

v. Traceability of changes and confirmation of change incorporation.

vi. Methods of access to information.

c. Retention of historical data.

d. Systems and tools (including data elements).

5. Configuration Verification/Audits

a. Audit conduct, policies, procedures, documentation, access, and support.

b. Processes, plans, schedules for internal CM audits and subcontractor CM audits.

6. Data Management

a. Development, approval, release, and submittal of configuration data/documentation (including drawings) in relation to program and contractual events (DRDs, technical reviews, Certification of Flight Readiness, etc.).

b. Plan for subcontractor data management deliveries/control access.

c. Establishment and operation of Engineering Release Unit and CM receipt desk.

d. Process for documentation control (i.e., Document…