80JSC026R0015 Final RFP Attachments.pdf

For the best experience, open this PDF portfolio in

Acrobat X or Adobe Reader X, or later.

Get Adobe Reader Now!

http://www.adobe.com/go/reader

Section J Page XX CLPS

80JSC026R0015

COMMERCIAL LUNAR PAYLOAD SERVICES (CLPS) 2.0

PART III-LIST OF DOCUMENTS, EXHIBITS, AND OTHER ATTACHMENTS

ATTACHMENT J-1

ORGANIZATIONAL CONFLICTS OF INTEREST (OCI) PLAN

(As proposed by Offeror)

Organizational Conflict of Interest (OCI) Plan

Data Requirements Description (DRD)

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

2. DRD No.: Attachment J-2 3. Data Type: 1 4.OPR: OP

5. Solicitation No.: 80JSC026R0015

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: The 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: Distribution must be as instructed by the contracting officer.

Initial Submission: Plan must be submitted with the initial proposal.

Submission Frequency: As needed with updates .

Format: Contractor’s format is acceptable.

Interrelationship: NASA Federal Acquisition Regulation (FAR) Supplement (NFS) NFS 1852.237-72, Access to Sensitive Information, NFS 1852.237-73, Release of Sensitive Information.

Applicable Documents: FAR Subpart 9.5, Organizational and Consultant Conflicts of Interest, NFS 1809.5, Organizational and Consultant Conflicts of Interest, NASA Guide on Organizational 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 OCI Plan must meet the requirements of FAR 9.5 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.

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 officer. Describe what processes the contractor will implement following any breach and indicate that final resolution of the corrective action must be approved by the contracting officer.

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. An OCI report must include (1) a description of the conflict, (2) the plan for resolving the conflict, and (3) the benefits/risks to contract performance associated with plan approval/acceptance. Specific resolution strategies shall be appended to the Plan upon approval by the Government.

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

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

10. Include an assertion from the offeror that to the best of its knowledge no OCIs exist currently, if applicable.

Provide a list of all the prime’s and proposed subcontractor(s)’s NASA contracts and subcontracts currently being performed and contracts performed within the last five years of the release of this solicitation, to provide the CO with a better understanding of other NASA work performed by the offeror that may give rise to an actual or potential conflict. For each prime contract and subcontract listed, the offeror must: (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.

11. The offeror must also list any non-NASA Federal contracts and subcontracts that it or its proposed subcontractors are currently performing or have performed in the five years preceding the release of the solicitation that may give rise to an OCI. For each and subcontract listed, the offeror must: (1) identify the contract by number and name; (2) identify the name, address and contact information of the customer(s); (3) describe the scope of work in sufficient detail to ascertain the likelihood of a conflict with performance of this contract; and (4) 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 must: (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 offeror must 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 interest on the performance of the statement of work.

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 paragraphs 1 through 12 above 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, (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. (Note: Specific plans to limit future competition are reflected in the clause at NFS 1852.209-71, Limitation of Future Contracting.)

Remarks: N/A

Maintenance: The contractor must review the OCI Plan with each task order competition to prepare any revisions as needed or as directed by the contracting officer. Revisions are subject to contracting officer approval and must be incorporated by change page or complete reissue.

Commercial Lunar Payload Services (CLPS) 2.0

ATTACHMENT J-3

Government Task Agreement (GTA)

Instructions and Form

VERSION 1.0

THIS ATTACHMENT APPLIES ONLY WHEN REQUESTED AT THE DELIVERY/TASK

ORDER LEVEL

5/15/2026

National Aeronautics and Space Administration Lyndon B. Johnson Space Center Houston, Texas 77058

Attachment J-3 Government Task Agreement Government Task Agreement Instructions and GTA Form

Government Task Agreement Instructions

Introduction While the majority of work to be completed under this task order is anticipated to be performed by the Vendor at the Vendor or its subcontractor facilities, the Vendor may propose to use resources that are on-site at a NASA facility as described in Request for Task Plan (RFTP), Section 5.14. In the event of a conflict between that clause and these instructions, the clause shall govern.

Instructions The purpose of this document, a Government Task Agreement (GTA), is to memorialize the Vendor’s requested approach to use the NASA on-site resources that are described in Section

5.14. The Vendor shall submit all GTAs with its proposal. GTAs shall have an agreed-upon cost provided to the Vendor by the NASA Performing Organization. The cost of all GTAs will be added to the Vendor’s firm fixed price for purposes of calculating a Total Evaluated Price for proposal evaluation purposes (reference the RFTP Pricing section). Vendors are advised that if awarded a task order for this effort, any GTA may be amended or revised during performance as agreed to by the NASA and the Vendor. During task order performance, the Parties may also agree to execute additional GTAs if they mutually determine such agreements are necessary to respond to new or changed circumstances that arise during performance. The Vendor shall be responsible for the cost of any such GTA, and the Parties shall effectuate the addition of new GTAs, and corresponding task order price adjustments, pursuant to FAR 52.212-4(c) – Changes as incorporated herein. To propose new GTAs during task order performance, the Vendor shall work with the Contracting Officer Representative (COR) and the Contracting Officer (CO).

The provision of any GTA shall be subject to a determination by the Government that any potential organizational conflicts of interest (OCIs) can be effectively avoided, negated, and/or adequately mitigated. If an OCI exists or the Government determines one exists, a mitigation approach must be provided to the Contracting Officer for determination and acceptance prior to executing the terms of any GTA.

For proposals that include hardware delivered to and/or tested at NASA centers, Vendors shall coordinate with the facility for any documentation requirements prior to delivery or testing.

Required documentation is dependent upon the hardware, identified hazards, and nature of the tests and facilities being exercised.

The Vendor shall indicate herein whether, as part of this GTA's performance, the Vendor is requesting to have any Vendor-provided “IT resources,” as that term is defined at NFS 1852.204- 76, interface with NASA IT resources. If so, the Vendor's IT resources shall comply with the requirements at NFS 1852.204-76 and FAR 52.204-21. In evaluating such GTA requests, NASA will perform an IT security assessment, in accordance with NIST 800-53 guidance, and identify any additional requirements in the final GTA before execution. The Vendor shall meet all the indicated requirements before its IT resources interface with NASA IT resources.

If the Vendor proposes to operate commercially owned Ground Support Equipment (GSE) at NASA owned facilities, the Vendor has the option of referencing NASA Standards, (NASA- STD-5005) to develop their GSE equipment:

• NASA-STD-5005 Standard for the Design and Fabrication of Ground Support Equipment

The Vendor shall use one GTA for each requested use of a facility, asset, or service except when the use of multiple on-site resources as part of a single overall endeavor is contemplated; for example, if a certain type of testing requires the use of three different NASA on-site resources, the Vendor may use one GTA for “testing” that indicates the use of three different on-site resources.

How to Inquire About NASA On-Site Resources To inquire about relevant, unique on-site resources at NASA Centers that may be available to Vendors, refer to Appendix J – GTA NASA Subject Matter Expert Collaboration Points of Contact List and Appendix K – GTA NASA Agency Facility Capabilities. To inquire about additional GTAs after task order award, the Vendor shall work with its Technical Manager.

Through a GTA, the Vendor shall only request NASA facilities, assets, services, or other specialized resources that are unique and not reasonably available commercially. The Government has the right to refuse any GTA request for any reason.

During any blackout period in which the Vendor is drafting a proposal, communications with the Government POCs must be limited to sharing information about the specific GTA requested. The Government POC communications with the Vendors will not include any assistance in preparing the Vendor’s proposal, advice, or opinions on the Vendor’s proposed design solution or approach for performing the work requested by the CLPS 2.0 solicitation or any information regarding the CLPS 2.0 competition or its technical requirements.

Data Rights All technical data, computer software, and computer software documentation (technical data (TD), computer software (CS), and computer software documentation (CSD)) developed pursuant to a GTA shall be delivered to NASA with Government Purpose Rights (“GPR”, as defined in contract clause FAR 52.227-14 – Rights in Data-General (May 2014) Alternate II (DEC 2007) and Alternate III (Dec 2007) as modified by NASA FAR Supplement 1852.227-14 (APR 2015). Assertions provided by the Vendor on its Assertion Notice that propose to deliver TD/CS/CSD developed pursuant to a GTA with less than GPR will be rejected by NASA and will not be incorporated into the task order at or after award.

Data Delivery At no additional cost to NASA, the Vendor shall deliver to NASA all technical data, computer software, and computer software documentation developed under work performed pursuant to a GTA no later than sixty (60) calendar days after performance of the GTA has concluded.

Cost Information The Appendix J – GTA NASA Subject Matter Expert Collaboration Points of Contact List and/or Appendix K – GTA NASA Agency Facility Capabilities POCs are responsible for providing the GTA Total Cost value in this template and reporting detailed cost information to https://standards.nasa.gov/standard/NASA/NASA-STD-5005?check_logged_in=1 https://standards.nasa.gov/standard/NASA/NASA-STD-5005?check_logged_in=1 the CLPS Project. The detailed cost information will delineate, per fiscal year: (1) FTE and (2) WYE annualized equivalent labor; (3) FTE and (4) WYE labor equivalent cost; (5) material costs; (6) other costs projected; and (7) total cost. The detailed cost table template enclosed is provided to the CLPS vendors to be used to coordinate and collect the applicable cost information from the NASA POCs and submitted with the CLPS vendor’s proposal.

Task Order Performance Upon task order award, all GTAs are subject to formal review and approval by the CLPS Project and Contracting Officer. Once funding has been secured and the Vendor has met all other requirements (e.g., standards applicable to GSE has been finalized and documented), the approved GTA(s) will become an attachment to the task order authorizing the Vendor to proceed with the GTA(s).

GTA Template The required Government Task Agreement template that Vendors shall use for each GTA is provided below on pages 4-7 of this Instruction.

Government Task Agreement CLPS2 Payloads (Task No.: CLPS2)

Section I – to be Completed by the NASA Points of Contact

Task no.

Task title

Date

Rev. Rev

Points of Contact

CLPS Vendor NASA POC Name Location Office# Cell #

Test Facility Name SME Title NASA Center Location

Section II – Task Agreement Description

(To be Initially Completed by the CLPS Vendor and Updated as Needed)

Overall Task Objective Describe the GTA effort in (at least) 1 – 2 sentences.

Portion of the Task to be Performed by the Government Describe the roles and responsibilities proposed to be completed by the Government as part of the GTA effort.

Describe any products to be delivered by the Government to the Vendor as part of the GTA effort (e.g., hardware produced, training, test data, reports, etc.). Include total number of hours (facility and/or labor) needed to complete the task.

Portion of the Task to be Performed by the Vendor Describe the CLPS Vendor’s roles and responsibilities to complete the GTA effort. Describe the items, labor support, and any additional provisions necessary (e.g., test hardware provided, Vendor labor support, test plans, etc.). Please include information about when and how the required TD/CS/CSD will be delivered to the Government (see “Data Delivery” above for more information).

Agreed Upon Schedule for Use of the On-Site NASA Resources

Detail the agreed-to schedule for GTA execution. Include milestones and Government product delivery dates.

Any Other Pertinent Information

Provide any additional information pertinent to this request. Additional information shall include, but is not limited to: assumptions for the cost and schedule estimates; justification for utilization of Government resources (see Instructions, above); details on the property the Vendor intends to bring on-site; approach to show commercial GSE compliance with NASA Center-specific design standards; approach to IT compliance, as applicable (see above).

• Justification for Utilizing Government Resources:

Section III – Costs (to be Completed by the NASA POC)

GTA Total Cost (Note: Detailed cost information must be provided by the NASA POC to be considered.)

Category FY24 ($K)

FY 25

FY 26

FY 27

Total Cost

NASA Labor (FTE) #

NASA Labor (FTE) $

NASA Civil Servant Travel Cost ($)

NASA Contractor (WYE) Labor Cost ($)

NASA Contractor Travel

Material/Procurement

Total Cost

Section IV - Signatures By signing this Agreement, the Vendor acknowledges that the on-site resources specified herein, if provided by NASA, is provided subject to the CLPS master contract and awarded task order applicable clauses, including but not limited to:

• CLPS RFTP Section 5.14 Government Task Agreement Clause

In accordance with 52.245-1(d)(2)(iii), any Government-furnished property, equipment, or information utilized by the Vendor while on-site at a NASA facility is provided in an “as-is” condition. The Vendor bears the risk of loss at any time the property or equipment is in the Vendor’s possession, or the possession of one of its subcontractors, suppliers, or agents.

GTA Approvals Approver Title Approver (Printed) Name Date Signature

Authorized CLPS Vendor Representative

NASA POC

CLPS Project Manager

CLPS Contracting Officer

GTA Form Glossary Section Category Description

SECTION I

Task Order Number The task order award number for the task. E.g., CLPS 2.0

Task Title Name of the Work that NASA will perform Date The current calendar date (mm/dd/yyyy).

Rev Revision of the GTA in the event changes are needed. To be filled out by CLPS Office Authorized

Vendor/Vendor Rep Name Commercial Vendor point of contact

Location Commercial Company Location (city, state, zip) Office# Work Telephone number (xxx) xxx-xxxx Cell # Cellular Telephone number (yyy) yyy-yyyy

NASA POC Name Commercial Vendor point of contact Location Commercial Company Location (city, state, zip) Office# Work Telephone number (xxx) xxx-xxxx Cell # Cellular Telephone number (yyy) yyy-yyyy Facility Name Name of the Test Facility (E.g., John Smith

Thermal Chamber) SME Title Subject Matter Expert title of expertise (E.g., Pyro Technics Expert) NASA Center

Location The name of the NASA Center (Name, City, State) (E.g., Johnson Space Center, Houston, Texas)

SECTION II To Be Filled-in by the CLPS vendor and coordinated with the NASA POC.

Overall Task

Objective Describe the GTA effort (the work to be accomplished) in (at least) 1 – 2 sentences. (E.g., To perform Acceptance Thermal Testing of Flight Hardware)

Portion of the Task to be performed by the Government

Describe the roles and responsibilities proposed to be completed by the Government as part of the GTA effort. Describe any products to be delivered by the Government to the Vendor as part of the GTA effort (e.g., hardware produced, training, test data, reports, etc.). Include total number of hours (facility and/or labor) needed to complete the task.

Portion of the Task to be performed by the Vendor

Describe the Vendor roles and responsibilities to complete the GTA effort. Describe the items, labor support, and any additional provisions necessary (e.g., test hardware provided, Vendor labor support, test plans, etc.). Please include information about when and how the required TD/CS/CSD will be delivered to the Government (see “Data Delivery” above for more information).

Agreed Upon Schedule for Use of the On-Site NASA Resources

Detail the agreed-to schedule for GTA execution.

Include milestones and Government product delivery dates.

Any Other Pertinent Information

Provide any additional information pertinent to this request. Additional information shall include, but is not limited to assumptions for the cost and schedule estimates; justification for utilization of Government resources (see Instructions, above); details on the

Section Category Description property Vendor intends to bring on-site; approach to show commercial GSE compliance with NASA Center-specific design standards; approach to IT compliance, as applicable (see above); as applicable.

SECTION III Costs To Be Filled-in by NASA: GTA Total Cost (Note:

Detailed cost information must be provided by the NASA POC to the CLPS Project Management for this GTA to be considered.)

SECTION IV Signatures Authorized Vendor

Representative CLPS Vendor POC who is authorized to approve the GTA Request

NASA POC NASA Point of Contact from NASA Center who is authorized to approve the GTA.

CLPS Project Manager

Commercial Lunar Payload Services Office Manager, Will be signed at task order award.

CLPS Contracting Officer

Commercial Lunar Payload Services government agent who is authorized to approve the task order.

Will be signed at task order award

Section J Page 1 CLPS 2.0

ATTACHMENT J-4

GOVERNMENT FURNISHED PROPERTY AND DATA/INFORMATION

THIS ATTACHMENT APPLIES ONLY WHEN REQUESTED AT THE

DELIVERY/TASK ORDER LEVEL

(End of Attachment)

Section J Page 3 CLPS 2.0

GOVERNMENT FURNISHED PROPERTY, SERVICES AND FACILITIES

The Government Furnished Property, Services and Facilities requested by the CLPS 2.0 Contractor for use in the performance of this Contract.

Due to the commercial approach for this contract, the Government does not intend to provide NASA IT assets (laptops/desktops, mobile devices, printers) during contract performance.

TABLE J-4-1: GOVERNMENT FURNISHED EQUIPMENT, MATERIALS AND SOFTWARE REQUESTED

Item No.

Description

Part Number Model Serial number

Quantity /Unit of Measure

Unit Acquisition

Return

Return Document Tracking Number (e.g., DD-number)

1 TBD TBD TBD TBD TBD TBD TBD TBD TBD TBD

Section J CLPS 2.0

TABLE J-4-2: GOVERNMENT SERVICES PROVIDED

Service Requested

Purpose Location of Service

Expected Need

Duration of

Request

Govt.

POC

and

Phone

Is this "Rent Free?"

(Yes/No)

Price if "Rent" were charged

Basis for Estimated

Price

Type of Agreement

TBD TBD TBD TBD TBD TBD TBD TBD TBD TBD TBD

TABLE J-4-3: GOVERNMENT FACILITIES PROVIDED

Facility Requested

Purpose Location of Facility

Expected Need

Duration of Request

POC

Phone

Is this "Rent Free?"

(Yes/No)

Price if were charged

Basis for Estimated

Price

Agreement

TBD TBD TBD TBD TBD TBD TBD TBD TBD TBD TBD

TABLE J-4-4: GOVERNMENT DATA OR INFORMATION PROVIDED

Description or Nomenclature

Need Date Applicable CLIN(s) or Task Order

Rationale Notes

1 TBD TBD TBD TBD TBD

(End of Item Lists)

End of Attachment)

Section J Page XX CLPS 2.0

PART IV - REPRESENTATIONS AND INSTRUCTIONS

ATTACHMENT J-5

DD FORM 254

Contractor to deliver DD Form 254 as requested at the delivery/task order level

Exploration Integration and Science Directorate

Commercial Lunar Payload Services (CLPS) 2.0

ATTACHMENT J-6

Anomaly, Mishap, Mission Failure Preparedness and Contingency Reporting

VERSION 1.0

5/15/2026

National Aeronautics and Space Administration Lyndon B. Johnson Space Center Houston, Texas 77058

Attachment J-6

DATA REQUIREMENTS DESCRIPTIONS (DRD)

1a. DRD Title:

Anomaly, Mishap, Mission Failure Preparedness and Contingency Reporting

2. Date of Current Version:

3a. DRD No.

J-6

3b. RFTP/ Task Order No.

TBD

4. Use (Define need for, intended use of, and/or anticipated results of data) See description/purpose.

Type: 2 For NASA’s review and approval

5. DRD Category X Technical

Administrative

6. References (SOW, Clause, etc.)

SOW CLINs 1, 2 and 3

7. Interrelationships (e.g., with other DRDs) N/A

8. PREPARATION INFORMATION: This DRD describes requirements for reports the Contractor must submit when anomaly, mishap, or mission failure occurs.

DESCRIPTION/PURPOSE:

This document defines conditions that require a report, requirements for notification to NASA, and documents NASA’s requirements for the Contractor to investigate and establish corrective action plans that occur while performing the work required in support of this task order.

Anomaly, mishap reporting, investigation, and corrective action requirements occurring on third-party property will be handled in the same manner as those occurring on Contractor property.

DATA REQUIREMENTS:

DEFINITIONS:

Anomaly: is an unexpected or out-of-spec event that can either happen to the NASA property (i.e., a procedural deviation such as mishandling or exposure to an out-of-spec condition) or happen from the NASA property (i.e., a performance deviation such as a test failure or unexpected response to a command). An anomaly is also defined as an unexpected or out-of-spec event that occurs with the lander regardless of known or possible solutions or results. If an event is unexpected or out-of-spec, it is an anomaly regardless of known or possible results. An anomaly may or may not be associated with actual damage, the potential of latent damage, or the uncertainty of state. If the results of an event include damage or injury, it is a mishap regardless of whether the precipitating event was anomalous.

3/24/2026

Mishap: is any incident, which may occur prior to, during, and post launch, that results in at least one of the following:

a) Destruction of, or damage to, NASA property or NASA equipment (including flight and non- flight GSE), NASA-sponsored payloads, or any other property provided pursuant to this contract

b) Injury to NASA personnel

c) Injury to non-NASA personnel associated with NASA-sponsored payloads

d) Damage to a NASA facility,

e) Exposure to chemicals, gas, radiation, or electromagnetic fields involving NASA personnel which could result in fatality; lost-time occupational injury; or occupational disease; or

f) Exposure to chemicals, gas, radiation, or electromagnetic fields involving NASA property, or NASA equipment, which could result in hardware failure, hardware contamination, systems malfunction, or affect mission success.

Mission failure: is any incident or series of incidents that prevents or interferes with achieving a soft landing on the lunar surface or prevents the Contractor’s ability to provide power and communications to at least two NASA payloads.

High Visibility Events: Those particular mishaps, regardless of the amount of property damage or personnel injury, that NASA judges to possess a high degree of programmatic impact, or public, media, or political interest including, but not limited to, mishaps that impact flight hardware, flight software, or completion of critical mission milestones. The Contractor may notify NASA of a high visibility event or NASA may identify to the Contractor if an event arises to the level of a high visibility event and any applicable anomaly or mishap processes to follow.

The following addresses the specific requirements for anomaly, mishap, mission failure, high visibility events, investigation, reports, and corrective actions:

1. ANOMALY:

1.1 The Contractor shall notify the CLPS Contracting Officer Representative (COR) and Contracting Officer (CO) as soon as the safety of personnel and hardware permits but no later than 6 hours after any known anomalies associated with the mission including the lander or any of the NASA-sponsored payloads during integration testing, while on the pad, and throughout the mission. Anomalies occurring on third-party property will be handled in the same manner as those occurring on Contractor property.

1.2 Contractor Final Report. After the Contractor completes its investigation of the anomaly and, when appropriate, has developed a plan of corrective action, the Contractor shall deliver this completed report to NASA within 30 days of any anomaly.

2. MISHAPS:

1.3 The Contractor shall notify the CLPS CO and COR as soon as the safety of personnel and hardware permits but no later than 6 hours after the mishap occurred while on the Contractor, third-party property, or other non-NASA government property.

1.4 In the event needed, the primary purpose for an investigation and corrective action is to prevent similar occurrences and thus improve the safety of operations. The emphasis for an investigation should be on discovering root cause-effect relationships from which remedial and corrective actions can be derived. The intent is not to place blame, but to determine how processes and responsibilities may be clarified or improved to eliminate errors. Additional purposes for investigations are to determine the nature and extent of the events and its impact; to improve standards and risk posture; to satisfy the taxpayer’s right to know; and to resolve any questions associated. The investigation process will commence in two phases, an investigative phase and a corrective action phase. Each phase results in a deliverable product as described below.

1.5 An initial investigation by the Contractor is required for all mishaps reported to NASA. NASA reserves discretionary authority to investigate mishaps that involve NASA personnel or resources 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.

1.6 Contractor Final Report. 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 30 days of any mishap. The report shall describe the mishap, how it occurred, the Contractor’s plan to recover from the mishap to include a timeline for resolution, and how the Contractor will ensure the mishap will not reoccur. This plan will also 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 or, if applicable, accomplished.

1.6.1 Corrective Action Plan (CAP) Process

A. The CAP shall include the following:

a. Corrective actions description and the estimated completion dates for each corrective action.

b. A matrix or other means of matching corrective actions to all findings and recommendations.

B. Corrective Action Plan Review and Approval

The CLPS Project Management shall review the CAP

b. Accept or reject the CAP.

c. Return a rejected CAP with comments to the contractor for revision and resubmission.

C. Contractor Corrective Action Plan Implementation

a. Implement the corrective actions.

b. Track the corrective action performance and completion and provide the CLPS Project Management with a status at intervals determined by the CLPS Project Management.

D. Corrective Action Plan Monitoring and Close Out

The Contractor shall:

a. Update the CLPS Project Management on the status of corrective action activities at least every 30 workdays until the CAP is closed.

b. Submit changes to the CAP after it has been approved (i.e., actions considered unwise or not feasible) to the CLPS Project Management for review and approval.

c. Once corrective actions are fulfilled, provide a Corrective Action Plan Closure Statement to the CLPS Project Management advising the CAP has been closed.

The CLPS Project Management shall:

a. Track corrective action activities to verify they are carried out according to plan and report non-compliance to the NASA Mission Directorate.

b. Verify corrective actions activities were implemented, completed, and closed.

c. Notify the NASA Mission Directorate that actions have been implemented, completed, and closed.

1.7 If a mishap occurs prior to launch, regardless of location, NASA will review the Contractor’s Final Report to ensure the corrective actions demonstrate an acceptable risk posture to NASA. If acceptable, then NASA will approve the Contractor to proceed with task order performance. As needed, Corrective Actions will be reviewed for applicability and implementation needed for any of the Contractor’s other CLPS task orders.

1.8 If a mishap occurs after launch, NASA will review the Contractor’s Final Report and any applicable Corrective Actions. Any Corrective Actions will be reviewed to ensure they demonstrate an acceptable risk posture to future NASA payloads and will be applied to the Contractor’s other CLPS task orders, as applicable.

3. MISSION FAILURE

3.1 In the event of a mission failure or an event that could lead to mission failure, the contractor shall notify the CO and COR as soon as the safety of personnel and hardware permits but no later than 6 hours after the contractor identifies the mission failure or event.

3.2 Following completion of all mission activities, the contractor shall convene a review board in accordance with contractor defined processes and within 30 days, or such other period as the parties agree to in writing, to investigate the mission failure. The contractor shall allow at least two NASA employees to participate in the investigation to:

a) observe,

b) monitor the progress of the investigation on a non-interference basis,

c) provide releasable, non-proprietary technical data,

d) provide subject matter expertise,

e) provide advice on interpreting data,

f) provide suggestions on what publicly available or Contractor-owned data would be most helpful to understand the mission failure,

g) analyze data, and

h) use NASA tools to produce analysis that advances the board activities.

NASA will not participate in the Contractor’s board recommendations or conclusions; advising on solutions or future Contractor actions; or otherwise providing direction to the Contractor.

3.3 The Contractor shall deliver a mission failure investigation report to NASA within 90 days of ending the mission, or such other period as the parties agree to in writing. The mission report shall identify the Contractor’s best assessment of what caused the mission to fail, a discussion of how the failure could have been prevented, and how the Contractor will ensure the failure will not reoccur. The report will also include any corrective actions to be implemented for future work by the Contractor or a third party, if applicable. The report and any other results of the board activity should be clearly labeled as a Contractor product (see Section 5 Rights in Data), and not a joint or co-authored report.

3.4 NASA may conduct its own investigation of the mission failure. The Contractor shall provide personnel, resources, and data, as necessary, to support a NASA investigation within 75 workdays, or such other period as the parties agree to in writing.

a) If there is a Mission Failure and a Mission Failure Investigation Report is required, then Mishap Reports related to the mission failure are not required.

3.5 Within two weeks of submission of the Mission Failure Investigation Report, or such other period as the parties agree to in writing, the

Contractor will hold a Lesson’s Learned meeting with NASA stakeholders to out brief the key points of the Mission Failure Investigation Report.

4. High Visibility Events

4.1. If NASA determines that an event, either prior to launch or during execution of a contractor mission, should be treated as a high visibility event, NASA will provide to the Contractor written instructions on which of the reporting processes described in sections 1, 2 or 3 shall be used by NASA and the Contractor in response to the high visibility event.

5. CONTRACTOR INVESTIGATIONS

If the Contractor investigates anomalies or mishaps not covered by Sections 1- 2 above that could impact the Contractor’s CLPS task order(s), the Contractor shall make available to NASA relevant data and resulting reports (e.g., anomalies/mishaps that have the potential to do harm to CLPS payloads or endanger successful lunar delivery).

6. RIGHTS IN DATA APPLICABLE TO DELIVERED REPORTS

The CLPS Master Contract includes 52.227-14 RIGHTS IN DATA-

GENERAL (MAY 2014)— ALTERNATE II (DEC 2007) AND

ALTERNATE III (DEC 2007) as modified by NASA FAR Supplement 1852.227-14.

For purposes of this DRD, ALT II is updated as follows:

(g)(3) Notwithstanding paragraph (g)(1) of this clause, the contract may identify and specify the delivery of limited rights data, or the Contracting Officer may require by written request the delivery of limited rights data that has been withheld or would otherwise be entitled to be withheld. If delivery of that data is required, the Contractor shall affix the following "Limited Rights Notice" to the data and the Government will treat the data, subject to the provisions of paragraphs (e) and (f) of this clause, in accordance with the notice:

LIMITED RIGHTS NOTICE (DEC 2007)

(a) These data are submitted with limited rights under Government Contract No. TBD and Task Order TBD. These data may be reproduced and used by the Government with the express limitation that they will not, without written permission of the Contractor, be used for purposes of manufacture nor disclosed outside the Government; except that the Government may disclose these data outside the Government to support service contractors and/or to other contractors participating in the Government’s program of which the specific contract is a part, provided that the Government makes such disclosure subject to prohibition against further use and disclosure:

i. The Government shall not release data to a contractor prior to receiving written permission from the CLPS task order awardee.

(b) This notice shall be marked on any reproduction of these data, in whole or in part.

7. OFFICE OF PRIMARY RESPONSIBILITY: CLPS Project Office

8. FREQUNCY OF SUBMISSION: Reports are to be delivered as needed based on the circumstances defined in this DRD.

9. FORMAT: When generating reports covered by this DRD, the Contractor’s format is acceptable.

10. EFFECTIVITY: This DRD is effective upon task order award and will remain in effect until the conclusion of the CLPS task order.

11. CHANGE AND REVISION SIGNATURE AUTHORITY: This document is revised whenever a change in method of operation or responsibilities is incorporated. The final approval and signature authority for revisions to this document rests with the CLPS Project Manager and COR.

11. COPIES/DISTRIBUTION: One copy of any reports created under this DRD are to be emailed to the NASA CO and COR.

A. The CAP shall include the following:

B. Corrective Action Plan Review and Approval

C. Contractor Corrective Action Plan Implementation

D. Corrective Action Plan Monitoring and Close Out

4. High Visibility Events

4.1. If NASA determines that an event, either prior to launch or during execution of a contractor mission, should be treated as a high visibility event, NASA will provide to the Contractor written instructions on which of the reporting processes descr...

5. CONTRACTOR INVESTIGATIONS

6. RIGHTS IN DATA APPLICABLE TO DELIVERED REPORTS

Rev.: 03/2026

1. DRD Title: Small Business Subcontracting Plan and Reports

2. DRD No.: DRD-Attachment 7 3. Data Type: 1 4. OPR: Office of Small Business Programs (BA)

5. Solicitation No.: 80JSC026R0015

6. Contract No.: TBD

7. Date Issued: May 15, 2026

8. Date Revised: January 2026 9. DRD Category:

Technical ☐ Administrative ☒

S&MA ☐

10. Description/Use:

This DRD defines the content, format, and submission requirements for the Contractor’s Small Business Subcontracting Plan and related small business subcontracting reports required under CLPS 2.0.

DRD will be used by the NASA Contracting Officer and the Office of Small Business Programs to: (1) evaluate the Contractor’s planned and actual utilization of small business concerns and designated small business subcategories; (2) determine compliance with FAR 52.219-8, FAR 52.219-9 (as deviated), NFS 1852.219-75, and the CLPS 2.0 solicitation; and (3) monitor performance against contract small business subcontracting goals throughout the period of performance.

11. Distribution:

The Contractor shall electronically submit all deliverables required by this DRD to the Contracting Officer.

Initial Submission:

Submission of a Small Business Subcontracting Plan (large businesses Only) in attachment J-7. This procurement is open to all offerors. Only offerors other than small businesses are required to submit a Small Business Subcontracting Plan in accordance with FAR 52.219‑9. Offerors with an approved Commercial Small Business Plan (reference clause I.6, 52.219‑9) shall include a copy of the approved plan in its proposal and ensure the approved goals are reflected in clause H.21, JSC 52.219‑90 Small Business Subcontracting Goals.

Submission Frequency:

a. Subcontracting Plan:

1. Approval – Prior to contract award.

2. Frequency –To be updated in accordance with FAR 19.302-1(d) or 90 days prior to expiration date of existing subcontracting plan

b. Reports:

1. The contractor shall submit subcontracting data semi-annually and at contract completion to the

Subcontracting Plan Reports (SPR).

2. All contractors are required to register and file both types of subcontracting reports using the SPR system.

through SAM.gov.

3. Per FAR 52.219-9(d)(10)(ii), the contractor shall submit an Annual Progress Report to the Contracting

Officer to address the extent of compliance with the Small Business Subcontracting Plan. The Annual http://www.sam.gov/

Progress Report is due within 15 days at the end of each contract year.

Format:

The Contractor’s format is acceptable for the plan. The plan shall be delivered in a compatible electronic format.

Reporting shall be in compliance with NFS 1852.219-75, Individual Subcontracting Reports. and FAR 52.219- 9(d)(10)(ii).

Interrelationship:

• J-7, Small Business Subcontracting Plan and Reports

Applicable Documents:

• FAR 52.219-8, Utilization of Small Business Concerns

• FAR 52.219-9, Small Business Subcontracting Plan

• NFS 1852.219-75, Individual Subcontracting Reports

Scope:

The Small Business Subcontracting Plan shall be in compliance with FAR 52.219-9, Small Business Subcontracting Plan. The Small Business Subcontracting Reporting shall be in compliance with NFS 1852.219-75, Individual Subcontracting Reports and FAR 52.219-9(d)(10)(ii). Upon approval, the Small Business Subcontracting Plan will become a part of the contract as Attachment J-7, Small Business Subcontracting Plan.

Contents:

1. Small Business Subcontracting Plan: (must ensure all elements below are addressed in Sec. L&M)

a. Provide the required content of FAR 52.219-9, Small Business Subcontracting Plan.

b. All plans shall provide information demonstrating the Extent of Commitment to utilize small business concerns and to support their development. The information provided must include a brief description of established or planned procedures and organizational structure for Small Business outreach, assistance, counseling, market research and Small Business identification, and relevant purchasing procedures. For Other than Small Business (Large Business), this information shall conform to applicable portions of the submitted Small Business Subcontracting Plan.

i. The plan shall include participation in the NASA Mentor Protégé Program and any planned commitment to enter into a NASA Mentor-Protégé agreement to provide appropriate developmental assistance to enhance the protégé’s ability to perform successfully under contracts and/or subcontracts.

ii. The plan shall include the approach the Contractor intends to use to meet the proposed subcontracting goals through the duration of the contract. Subcontractors whose bid is part of this proposal shall be identified. For each subcontractor, the percentage of the proposal and any small or small business subcategory classification shall be identified.

iii. If the subcontractor(s) is known, the plan must connect the work to the subcontractor and specify the extent of commitment to use the subcontractor (s) (enforceable vs. non- enforceable commitments).

iv. The plan shall outline proactive measures to be implemented during contract performance to increase participation among small businesses and across all designated small business subcategories.

v. The plan shall describe the management approach to subcontracting with small, small disadvantaged (SDB), 8(a), Women-owned (WOSB), HUBZone, Veteran owned (VOSB), and Service-disabled veteran owned (SDVOSB) and HBCU/MSI (Historically Black Colleges & Universities/Minority Institutions).

vi. The plan shall identify any work to be subcontracted that is considered “high technology.” High Technology is defined as research and development efforts that are within or advance the state-of-the-art in technology discipline and are performed primarily by engineers, scientists, and highly skilled and trained technicians or specialists.

vii. The plan shall include the Small Business Subcontracting Tables 1 and 2 below, which provides a breakdown of the subcontracting goals, by small business category, expressed in terms of both a percentage of TOTAL CONTRACT VALUE and a percent of TOTAL PLANNED

SUBCONTRACTS.

Offerors shall modify these tables to show the subcontracting goals for the basic contract requirement (Core and IDIQ during base contract period of performance) and any contract option separately. In addition, the plan shall show the phased approach by contract year to meet the overall contract total small business goals by end of the contract (separate tables for basic contract requirement and any options shown separately). This shall be expressed in terms of small business percentage goals by category and planned dollars spent by the end of each contract year (total dollars spent at contract level and total dollars spent by each small business categories). This shall be consistent with the proposed technical and schedule approach (see example table below).

TABLE 1: GOALS AS PERCENT OF CONTRACT VALUE AND AS PERCENT OF

SUBCONTRACTING

Total Contract Value $XX Column A Column B Column C Business Category Dollar Value to be subcontracted per Category

Goal as Percent of Subcontracting Value

Total Contract Value

Small Business Concerns

Large Business Concerns

Total Dollars to be Subcontracted

Subcategories of Small Business Concerns

Women Owned Small Business

Small Disadvantaged Business

Veteran Owned Small Business

Service-Disabled Veteran- Owned Small Business

HUBZone Small Business

Historically Black Colleges and Universities and Other Minority Institutions (HBCU/MI)

TABLE 2: LIST OF SMALL BUSINESS SUBCONTRACTORS

Company Name

UEI/Cage Code

Business

NAICS SOW Ref. Dollar Value

EXAMPLE CONTRACT $100M WITH ESTIMATED SUBCONTRACTS OF $50M

Total Contract Value $100,000,000

Column A Column B Column C

Business Category Dollar Value to be subcontracted per Category

Subcontracting Value

Goal as Percent of Total Contract Value

Concerns

$25,000,000

50 percent

25 percent

Large Business Concerns

$25,000,000

50 percent n/a

Total Dollars to be Subcontracted

$50,000,000

100 percent* n/a

Subcategories of Small Business Concerns

Women Owned Small

$9,000,000

18 percent

9 percent

Small Disadvantaged

$5,500,000

11 percent

5 percent

Veteran Owned Small

$2,500,000

5 percent

2.5 percent

Service-Disabled Veteran-Owned

$1,500,000

3 percent

1.5 percent

HUBZone Small Business

Historically Black Colleges and Universities and Other Minority Institutions

(HBCU/MI)

*Shall be 100% if any dollars are subcontracted.

**Zero percent does not constitute a goal. Omit any categories where a goal is not established and provide rationale why.

***The small business subcategories do not necessarily add up to the percentage and dollar amount in the “Small Business Concerns” category above, since some small businesses do not fall into any of the subcategories below, while others will fall into more than one subcategory below. It is recommended that Offerors first complete Column B by entering the dollar amount the Offeror proposes to subcontract to each business category and subcategory. To complete Column A, divide the dollar amount in Column B by the total offered price of the proposal (that is, total contract value). In the example above, Column A for Veteran Owned Small Business = $2,500,000 divided by $100,000,000, or 2.5%. To complete column C, divide the corresponding amount in Column B by the amount in the “Total Dollars to be Subcontracted” cell in Column B.