11.16.26 SPARC DRFP Questions.Comments and Responses.xlsx

XLSX spreadsheet 43 KB Posted

Attached to
Space Power and Reactor Capabilities (SPARC) - Draft Request for Proposals (DRFP)
Solicitation number
80GRC026R0009
Issued by

About this file

This file contains the Draft Request for Proposals (DRFP) Questions, Comments and Responses for the Space Power and Reactor Capabilities (SPARC) solicitation issued by NASA Glenn Research Center. The document records 182 industry questions and NASA's responses regarding the SPARC IDIQ contract and the LR-1 Phase 1 Awardable Sample Task Order (ASTO). Key topics addressed include contract structure and terms, data rights, funding schedules, facility access, technical requirements for the lunar reactor system, safety standards, Environmental Test Unit (ETU) specifications, testing protocols, personnel qualifications, pricing structures, and proposal submission details. NASA confirmed that the LR-1 Phase 1 TO will be firm-fixed-price (FFP) without Earned Value Management requirements, that HALEU fuel is not required during Phase 1, that contractors are responsible for identifying needed facilities and organizing access, and that limited rights rather than government purpose rights will be used for data developed under the contract. The document notes that many responses reference modifications to be made in the Final RFP, which NASA indicated would be released on or around November 20, 2026, with the Final RFP taking precedence over any draft documents in case of discrepancies.

Specific technical clarifications included guidance on preventing inadvertent criticality using two independent hardware methods, definition of operating states and restart capabilities, radiator deployment alternatives for ETU testing, lunar surface environmental datasets, thermal and electrical interface testing requirements, and the distinction between three overlapping safety requirements (LR1-27 through LR1-29) that apply to different phases and regulatory frameworks. NASA also addressed concerns about small business participation, non-traditional contractor evaluation, certified cost and pricing data requirements, past performance assessment, teaming restrictions, subcontractor roles, and opportunities for contractors to on-ramp to the SPARC IDIQ after the initial Phase 1 TO award. Responses clarified that it is the contractor's responsibility to propose appropriate test campaigns, ConOps, design approaches, and ETU configurations to meet stated requirements within the 18-month Phase 1 performance period, with PDR serving as a hard gate milestone.

View the file

Other files

File Type Posted
11.16.26 Att J.2-1 - Instructions for Setting up a Box Account.pdf PDF
11.16.26 Att J.2-4 - LR-1 Phase 1 ASTO Model TO.pdf PDF
11.16.26 Att J.2-11 - GTA Instructions.pdf PDF
11.16.26 Att J.2-10 Price Volume Template.xlsx XLSX spreadsheet
11.16.26 Att J.1-5 - Government Task Agreement (GTA) Form.pdf PDF
11.16.26 Att J.2-9 - Past Performance Questionnaire - Instructions and Template.pdf PDF
SPARC Industry Day Q.A.pdf PDF
SPARC Industry Day Presentation.pdf PDF
SPARC Draft Request For Proposal (DRFP) Cover Letter - Amend 1.pdf PDF
SPARC Industry Day Information.pdf PDF
SPARC Draft Request For Proposal (DRFP) Cover Letter.pdf PDF
Att J.1-7 - NF533Q Template.xlsx XLSX spreadsheet
Att J.2-9 - PPQ - I&T.pdf PDF
Att J.2-8 - OCI Assertions Related to ASTO.pdf PDF
Att J.2-10 - ASTO Price Volume Template.pdf PDF
Att J.2-3 - SPARC Small Business Participation - I&T.pdf PDF
Att J.1-1 - SPARC Statement of Work.pdf PDF
Att J.2-2 - SPARC OCI Plan - I&T.pdf PDF
Att J.1-5 - GTAs - I&T.pdf PDF
Att J.2-5 - LR-1 Phase 1 ASTO SOW.pdf PDF
SPARC Draft RFP- 80GRC026R0009.pdf PDF
Att J.2-7 - Offeror R&I Regarding Business Systems.pdf PDF
Att J.2-6 - LR-1 Phase 1 ASTO DPD.pdf PDF
Att J.1-6 - NF533M Template.xlsx XLSX spreadsheet
Att J.2-1 - SPARC Security Requirements for Unclassified IT Resources - I&T.pdf PDF
Att J.2-4 - LR-1 Phase 1 ASTO Model TO.pdf PDF
Show all 26

On GovTribe

Work with this file

  • Download the original file
  • Contacts named in this file
  • Similar government files
  • Ask GovTribe AI about this file

Text version

DRFP RESPONSES

CountCommentNASA response
1Some overlapping terms in the MAIDIQ; intentional to ensure each TO scenario can be accomodated. FAR, NFS, and GRC terms are standard and should be tailored to final MAIDIQ and TO#1, removing self-deleting terms that are N/A. No exceptions taken to terms in RFP.

Can NASA share how funding will be scheduled over the course of TO#1? Would NASA consider using Agency Level terms (NFS) to supplement FAR vs. Center Level (GRC) Terms? This would remove unnecessary/costly redundant contract requirements. Has any of the RFO (Rev FAR overhaul been implemented into the solicitation? Is NASA willing to accept Government Purpose Rights on data first produced in the performance of this contract?

Are there any changes to the small business participation requirements due to the FAR provisions and clauses to Revolutionary FAR Overhaul requirements?

52.227-14 ALT II&III 52.227-14 RIGHTS IN DATA—GENERAL (MAY 2014), as amended by NFS 1852.227-14 (APR 2015), including ALTERNATE II (DEC 2007), AND ALTERNATE III (DEC 2007)

(May 2014) - The primary clause requests Unlimited Rights for technical data and software with provisions that allow for Limited and Restricted Rights when asserted. Would NASA consider revising the Data Rights clause by adding Government Purpose Rights (GPR) in addition to Unlimited Rights to account for data that may have been developed with a mix of USG and private funds? This has been done in some other NASA contracts previously.The Final RFP will reflect removal of redundant and conflicting clauses and a general clean up of all documents. The FAR Overhaul was utilized for references and clauses (through approved deviations) throughout the RFP. Funding information cannot be shared at this time. NASA utlizes Limited Rights rather than Government Purpose Rights. An offeror proposing to use data/software/etc. subject to Government Purpose Rights must clearly disclose those rights within its proposal.
2In Section 3.1.5.2 NASA will consider requests from contractor for use of Government-furnished resources…. Are FFRDC facilties/organizations like JPL in Pasadena, Calif. included/covered under this description. How about DoE facilities or mothballed/caretaker USG/NNSS or DoE Test facilities.
Does NASA make research reactor irradiation capacity available for the component-level radiation testing that ASTO Objective 3 requires?It is the responsibility of the contractor to identify needed facilities and to organize use of said facilites. See Final RFP for clarified process.
3In LR1-30 Requirements; DOE standards are listed for Authorization to Nuclear Facilities, Quality Assurance, Facility safety, and Satefy Analysis for DOE Reactor Facilties.

The content of this section doesn’t address any DOE (or NASA) standards concerning nuclear transportation logistics, nuclear reactor storage, or launch system integration that could impact the LR-1 design.

Is it the intent of NASA to address those design aspects as part of a future TO to be released later?

In Section 3.2.4 it is noted the contractor will work collaboratively to obtain nuclear launch authorization, launch licensing, and plan, and implement radiological contingency activities with NASA The content of this section doesn’t mention transportation, storage, or any logistical aspects for moving the LR-1 nuclear core/or system elements from assembly site or manufacturing to an assembly site and then to the launch site or a storage site before integrated with launch system. Can you clarify if transportation is to be included in the Task Order #1 planning? Transportation and launch site logistics are outside the scope of work for the LR-1 Phase 1 TO. Any regulations or standards concerning this topic would be levied in notional future phases. It is the responsibility of the contractor to identify the AIT and transportation processes for the LR-1 flight system.

LR1-30 itself lists only DOE standards for nuclear facility authorization, quality assurance, facility safety and safety analysis. But the SOW covers more of transportation, storage and launch integration than the comment suggests:

Table 1 (Applicable Documents) already imposes 10 CFR Part 71 (Packaging and Transportation of Radioactive Material), NASA-STD-8719.24 (Payload Safety) and NASA-STD-8719.25 (Range Flight Safety) on the flight design.

4Defined operating states are "full power, partial power, warm standby, and shutdown" as a minimum
Is the "initial startup" state intentionally excluded from this list?The operating states identified in the requirement are the minimum set NASA expects. Additional operating states may be identified by the contractor as necessecary for their design.
5"Customer to assess the need for restarts" is vague, as the system is specifcally designed for continuous operation.
Shall restart apply to the warm standby state and not to the shutdown state (as a minimum)?See modifications in the final RFP.
6What is meant by "unusual contract features or conditions"?See modifications in the final RFP.
7Column definitions were not included below the table. Please include those.See modifications in the final RFP.
8In the following sentence: "Realistic support elements should be provided to mimic critical thermal and electrical interfaces, including the nuclear aspects of the reactor and the downstream electrical attributes of a lunar power grid"

Can you provde clarification on the elements to be identified as "nuclear aspects" of the reactor for ground test?

ASTO Section 5.4 states that the ETU "may require only one full-scale string." Under what conditions does NASA accept a single-string ETU?

Is there an assumed ETU configuration (e.g. all subsystems working in concert) or can the components be tested separately with evidence to close as a whole system (SOW Sec 5.4 pg 16)?The SOW has been clarified to identify requirements for the ETU.
9Prior programs have used the DPAS rating system in order to secure priority of work within the Government and Contractor base. Will the LR1 Program Office assist to provide priority of services and/or NASA facilities for proposed uses and execution of GTAs due to availaility or conflict of use during program execution

Please clarify how NASA will allocate and ensure equitable access to Government test facilities and other Government resources when multiple offerors or contractors request the same or capacity-constrained resource.

The Draft RFP identifies the solicitation as a DPAS rated order with a DO-C9 rating. Does NASA anticipate that LR-1 or a subsequent Lunar Reactor Flight System task order could receive a different priority rating, including a DX rating?Certain Task Orders, including the LR-1 Phase 1 Task Order are expected to be include DPAS ratings. NASA will consider GTAs and may priortize facility use depending its prioritization of the competing needs.
10Scalable subsystems reduce cost and lead time for future systems.
Will scalability of subsystem designs be considered in NASA’s evaluation?See modifications in the final RFP.
11PLR may need to reject full load early in mission.
Can NASA clarify required PLR operating range for proper subsystem sizing?It is the responsibility of the contractor to identify the system design dissipation requirements to meet the LR-1 SOW requirements.
12Teams need validated lunar environmental datasets.

When will M2M‑30159 rev J be released, and what interim spec should be used?

Will NASA provide reference environmental assumptions (regolith thermal coupling, day/night durations, radiator view factors, etc.)?The spec to utilize is provided in Section 3 of the SOW.
13Surface operations introduce design-driving uncertainties.
Will NASA provide guidance or SMEs for lunar site ops and regolith mitigation?The contractor should have the needed SMEs to complete the LR-1 Phase 1 TO.
14Lunar surface conditions may differ significantly from TVAC chambers (sink temp, regolith dust, topography/slope, optical properties).

Can NASA clarify whether a TVAC chamber is sufficiently representative for HRS/ETU radiator performance?

Would NASA find value in supplementing test plans with additional conditions such as regolith dust and lunar topography?It is the responsibility of the contractor to identify the needed test campaign for the scope of the LR-1 Phase 1 TO. Please review RFP evaluation criteria.
15Full deployment of the Heat Rejection System in TVAC may be excessive and impractical; alternatives may achieve similar goals.
Will NASA allow partial or alternative radiator deployment configurations for ETU testing instead of full deployment inside TVAC?See responses to industry day questions.
16Full-scale HRS sized for multiple strings could oversize ETU hardware.
If LR‑1 uses parallel strings, will NASA accept a scaled or truncated HRS for ETU testing?See responses to industry day questions.
17SR‑1 heritage work may raise perceived OCI concerns.
Can NASA confirm SR‑1 participation does not create an OCI for LR‑1?It is the responsibility of the contractor to manage any company OCIs. Utilizing lessons learned, data, designs, etc. from prior or concurrent efforts (including SR-1) does not, by itself, constitute an OCI.
18Can NASA clarify whether an offeror may receive a SPARC IDIQ award without receiving a TO1 award, if so, which ASTO proposal requirements would apply? Or, would NASA prefer to onboard new bidders to the IDIQ after the ASTO award. Please also clarify whether contractors entering competition later would be eligible to compete for subsequent LR-1 phases.
The planned team structure may be more effective with one contractor as subcontractor in early phases of LR-1 with that contractor assuming a prime role later. In that case, the contractor would need to be awarded an IDIQ even if they did not get a TO1 award as a prime.See modifications in the final RFP.
19Contract type is unclear for Awardable Sample Task Order

While the SPARC SOW (2.1.2) notes that each TO request will either identify the contract type NASA intends to use or allow the contractor to choose, there does not appear to be any clarification as to what the guidance for ASTO will be.

Is the contractor able to decide whether to bid cost reimbursable or fixed price or will it be defined (as noted in section 2.1.2)?See modifications in the final RFP.
20Since PDR is defined herein to include successful closure/addressing of all action items, there must be some definition of how long after the actual PDR will be allowed to address actions. The period of performance is defined at 18 months, showing PDR at 18 months. This will not allow adequate time to address any actions. Recommend modifying language and/or PoP to allow for this issue.See modifications in the final RFP.
21Per the ASTO SOW, Kickoff is at 30days after ATP making both the preliminary and baseline NLAM document due the same day. Please clarify the submittal dates.See modifications in the final RFP.
22The rationale states that the radiation calculation should assume a flat surface with no geographic features. Please confirm if this statement was meant to eliminate the option of placing the reactor close to lunar terrain features to reduce shielding requirements.
Since radiation shielding is a significant contributor to total system mass (and therefore launch mass) and since mobility is likley required to avoid radioactive interactions with the lander, it would be very beneficial to use lunar terrain features - as enabled by the mobility system - to reduce the shielding requirements.The proposal should size the shield for worst-case conditions. The LR-1 system should not be dependant on terrain or landing site.
23Can NASA clarify what the $350M amount identified in both of the referenced sections represents?Review responses to Industry Day questions.
24The table in the beginning of Section B identifies the SPARC IDIQ as firm-fixed-price, however below the table there are several alternate contract type clauses listed. Can the Government clarify the anticipated contract type for the LR-1 Phase 1 task order or are bidders allowed to select amongst the types listed below the table?Please review the final RFP.
25As written there are terms for nearly all contract types. Depending on the ASTO contract type many of the clauses contained within SPARC solicitation would not be applicable.
Do we have to take exception to those clauses that don't apply to the ASTO contract type, but may apply to future TOs?Please review the final RFP.
26Concerning the statement “(4)(i) The Contractor agrees not to assert claim to copyright, publish or release to others any computer software first produced in the performance of this contract unless authorized by the Contracting Officer in writing.”

This would restrict the use of supplier generated computer software (unless NASA approval is obtained), which will require additional controls on the software and limit the benefit of reuse on other programs/other customers.

Inclusion of this language could add unecessary cost to the program.This language required by the NASA FAR Supplement Clause and will be included in the final RFP.
27The draft contract includes multiple versions of the Data Rights clauses that appear to cover the same subject matter. Can you clarify which clause is applicable?Please review the final RFP.
28The draft solicitation contains conflicting FOB terms, which will apply to the ASTO?Please review the final RFP.
29Will NASA be adding 52.250-1, Indemnification Under Public Law 85-804 to the list of applicable FAR Clauses.

What are the envisioned responsibilities and interfaces for receiving launch licensing and indemnification?

Section I - given that this project is nuclear and FAR 52.250-1 Indemnification Under Public Law 85-804 expressly covers nuclear projects, would NASA consider adding this clause to the IDIQ ?Indemnification may be addressed during potential future project phases.
30Given ASTO is a competitive procurement, is the level of requested cost-volume documentation applicable to this type of procurement given it qualifies for an exemption to certified cost and pricing data requirements?Please review the final RFP.
31Does NASA intend to fund every Phase 1 awardee through the Month 18 Preliminary Design Review (PDR), or does NASA reserve the right to terminate an awardee earlier?While any contract could be terminated, NASA does not have a particular intent to terminate one or more LR-1 Phase 1 TO.
32If NASA does not furnish a fueled reactor, does NASA expect the prime contractor to hold the Department of Energy High-Assay Low-Enriched Uranium (HALEU) application, or may a subcontractor hold that application?See responses to industry day questions.
33What schedule does NASA anticipate for the Department of Energy HALEU allocation, and how does that schedule align with the Month 18 PDR?See responses to industry day questions.
34Does NASA plan to release prior Fission Surface Power heritage design and test data to all offerors, and under what terms?
Heritage data access: What prior NASA Fission Surface Power (FSP) program data will be made available at contract award?NASA intends to release relevant FSP program data prior to the release of the Final RFP. If this is not possible, the data may be provided with the Final RFP.
35How does NASA treat data rights in contractor-developed balance-of-plant designs across later task orders and across multiple awardees?Limited and unlimited rights are addressed in the RFP.
36What portion of the $350 million ceiling does NASA allocate to LR-1 Phase 1, and what portion does NASA reserve for later task orders?See responses to industry day questions.
37Section M lists FAR 52.232-15, Progress Payments Not Included. Does NASA accept a Performance-Based Payment schedule under FAR 52.232-28, and does NASA impose a limit on the payment percentage or the number of events?See modifications in the final RFP.
38SPARC Statement of Work Section 3.1.2 states that Earned Value Management reporting "may be required for certain task orders." Does NASA plan to require Earned Value Management on LR-1 Phase 1?The LR-1 Phase 1 TO will not require EVM.
39How does NASA intend to use the on-ramp and off-ramp provisions, and does NASA plan to compete Phase 2 among Phase 1 awardees only?
Please provide the detailed onboarding process in the Final RFP, including the timing/frequency of onboarding opportunities, qualification criteria, proposal requirements, evaluation process, and whether newly onboarded contractors will have the same opportunity to compete for future task orders as original awardees.Please review the final RFP.
40The SPARC master contract is characterized as very broad (covering a wide range of tasks), however LR-1 Phase 1 is very specific. Is bidding task 1 as prime a requirement to being on-ramped to SPARC as a contractor/prime for future task orders?

Does bidding to be on-ramped to the IDIQ requiring bidding to Task Order 1?

Will NASA provide an avenue for on-ramping to SPARC without bidding Task Order 1 as a prime?NASA considers the LR-1 Phase 1 TO to be a baseline requirement for any SPARC contractor. It is NASA's intent that Offerors awarded a SPARC contract now or in the future (through on-boarding) will respond to the Phase 1 TO so that NASA can assess the Offeror's understanding of and competence in nuclear development requirements.
41Can you provide documentation/rationale for why you are requiring EVMS on a FFP Task Order and see this as a risk for future task orders? Why would this be evaluated for offers on the current task order as it does not apply (i.e., is out of scope)?See responses to industry day questions.
42What is the actual relationship between LR-1 and SR-1 as NASA has been routinely and publicly messaging a link between the two programs?See responses to industry day questions.
43Why is cost accounting and certified pricing required as there are multiples bidders (per the LR-1 presentation) and this not required by the FAR?

This proposal is considered competitive, can the requirement for Certified Cost or Pricing Data (CCoPD) and Defense Federal Acquisition Regulation Supplement (DFARS) checklist be removed?

If CCoPD is required, will the government make the CCoPD threshold $10M?Please review the final RFP.
45How are you planning to evaluate NTCs (non-traditional contractors) as opposed to traditional contractors who have government signed business system letters?Please review the final RFP.
46If EVMS and cost-accounting standards are required for the prime, can the government confirm whether EVMS and cost-accounting standards will not be required as flow downs to subcontractors?Please review the final RFP.
47Many of the anticipated offerors are Non-traditional Contractors. How does the Government intend to ensure adequate competition when current terms and conditions would restrict NTCs from bidding?Please review the final RFP.
48Request removal of 1852.242-73 NASA Contractor Financial Management Reporting (Deviation) Dec 2025 as it is not applicable to FFP.Please review the final RFP.
49Request removal of 1852.245-73 Financial Reporting of NASA Property in the Custody of Contractors (Dec 2025) (DEVIATION) as it is not applicable to FFP.Please review the perscription for this clause.
50Request removal of GRC 52.242-96 NASA Contractor Financial Reporting - Supplemental Requirements (Jun 2021) from TO #1 as it is not applicable to FFP.Please review the final RFP.
51Request removal of FAR 52.215-2 Audit and Records – Negotiation from TO #1 as its not applicable to FFP with adequate price competition.Please review the perscription for this clause.
52Request removal of FAR 52.215-10, -11, -12, and -13 from TO #1 as Certified Cost or Pricing Data is not applicable to FFP with adequate price competition.Please review the final RFP.
53Does the final RFP retain 15 metric tons as the mass requirement, or does NASA plan to impose the 8 metric ton figure that the SSN raised as a design trade?This requirement will not change.
54Requirement LR1-2 specifies at least 20 kilowatts-electric after a single failure. Does NASA expect parallel power conversion strings, an oversized single string, or does NASA leave that architecture to the offeror?It is up to the contractor to design and propose an LR-1 system to meet this requirement.
55What rationale supports the 3-kilovolt root mean square transmission cap in requirement LR1-3, and does NASA entertain a waiver?See modifications in the final RFP.
56Requirement LR1-6 states that operational life "can be verified through analysis." What analysis products and validation evidence does NASA expect?It is up to the contractor to propose a test and validation plan.
57Requirement LR1-18 specifies 5 rem per year at 1 kilometer including off-nominal conditions. How does NASA define the off-nominal cases?It is up to the contractor to design and propose an LR-1 system to meet this requirement.
58Does NASA intend the LR1-14 stowed envelope of 4.57 meters by 7.8 meters to accommodate a specific lander, and may offerors assume deployable structures extend beyond that envelope?See modifications in the final RFP SOW.
59Does NASA intend LR1-3 to define the power delivery as AC at 3kVRMS and if so is there a desired frequency/phase as this may impact PMAD architecture and design.See modifications in the final RFP SOW.
60Is NASA agnostic on working fluid (LR1-5; e.g. HeXe ratio) or is there a preferred mixture based on prior experience or known reactor interface requirements?See responses to industry day questions.
61Has NASA narrowed the trade space of the HALEU fuel definition (LR1-13; enrichment, form, chemistry) that can be used for early estimates of thermal design, safety analysis and fabrication timeline?See responses to industry day questions.
62Is full power required throughout the 354-hr lunar night (LR1-9)?See responses to industry day questions and see modifications in the final RFP SOW.
63In LR1-27 it seems to suggest that the nuclear regulatory framework is through INSRB now as the primary path; is that the only path or will there be collaboration with the NRC with NASA / DoE coordination? Is NASA confident that the regulatory pathway for LR-1 is well understood?The INSRB is the standard path which will be followed for current LR-1 activities.
64Does NASA permit an offeror to appear on more than one proposal team, either as prime or as subcontractor?See responses to industry day questions.
65Does NASA plan to furnish a reactor, a reactor design (i.e., build to print), or reactor design data as Government Furnished Equipment for LR-1? Section H defers Government Furnished Property clauses to the task order level, and the base contract contains none.NASA will not provide this data.
66Does NASA plan to release Space Reactor-1 technical data to LR-1 offerors?See responses to industry day questions.
67Will NASA accept a reactor-agnostic ETU design that defines the reactor thermal interface (consistent with the SR-1 rector design) without selecting a reactor vendor (assuming build to print of the SR-1 reactor design) at proposal?The proposal would be accepted as complete since an ETU design is presented.
68What is the anticipated use and/or customer for the power produced?Moon Base
69Should the technical approach for the preliminary design consider all surface CONOPS for deployment, emplacement, startup, nominal, and off-nominal operations – and all assets required?The preliminary design should address the requirements in the LR-1 P1 TO SOW. It is up to the contractor to develop a ConOps to address these requirements.
70What is the minimum acceptable TRL for each key subsystem at PDR exit? The SOW says "sufficient to proceed to flight system development" but provides no TRL floor.TRL values will not be defined or demanded for the LR-1 Phase 1 TO.
71Are all 11 PDR success criteria hard gates (must pass all) or is there a weighted/tiered structure?

For criterion (b) — "requirements agreed upon, finalized, stated clearly" — how are disagreements between contractor-derived and NASA-defined requirements adjudicated before PDR?

For criterion (k) — "procurement and supply chain risk management" — does this include HALEU supply chain, given the DOE acquisition dependency? The identified criteria are hard gates, within the structure of a Type 1 deliverable for associated content (e.g., LR1-SE-008).

For (b), a deviation process has been identified by LR1-SMA-001.

For (k), the procurement and supply chain risk management is inclusiive of all aspects of the LR-1 system. HALEU is out of scope for TO1, but should be considered for potential future activities. The contractor should document what they know for the process.

72Given the contractor is free to add requirements beyond those in Section 3, how will NASA evaluate contractor-proposed requirements that are more or less stringent than the SOW baseline?Please review the final RFP.
73Is there a preferred or baseline architecture, or is NASA truly technology-agnostic (e.g., would a heat pipe reactor instead of pumped-loop be acceptable)?The LR-1 architecture should meet the requirements in the final RFP.
74What are the minimum acceptable durations for ETU testing — steady-state only, or is a transient/endurance test required within Phase 1?The durations for ETU testing are what the contractor believes necessecary to prove the technology. It is the responsibility of the contractor to identify the needed test campaign for the scope of the LR-1 Phase 1 TO.
75Must the ETU demonstrate the full 20 kWe output, or is a reduced power level acceptable if analytical scaling is demonstrated? The SOW says components should be "full-scale" but is silent on output power level.See responses to industry day questions and see modifications in the final RFP SOW.
76For the reactor simulator, what level of fidelity is required for transient response matching — must it replicate the neutron feedback dynamics, or just the thermal mass and steady-state heat delivery?See responses to industry day questions.
77The ETU is now classified as a Federal Information System — what specific controls from NIST SP 800-53 are expected to be implemented on the ETU data acquisition and control software during the test campaign?Please review the final RFP.
78What are the specific neutron flux, gamma flux, and energy spectra that define the reactor-induced radiation environment? Without a reference reactor design, it is unclear what radiation dose components must survive.

What is the margin required above the expected mission dose to constitute a passing result?

Which components are considered radiation-critical and require physical testing vs. those that can be qualified by analysis? Is a NASA-approved criticality list available?

What is the assumed startup sequence duration, and is this driven by reactor physics (criticality approach), thermal constraints (Brayton minimum temperature), or both?This is based on the contractor's PDR design, which includes a reactor.
79For the natural lunar surface environment, is NASA providing a reference radiation specification, or should contractors use M2M-30159 directly?Refer to the final RFP SOW.
80Must radiation test articles be flight-representative, or are engineering-grade coupons/subassemblies acceptable?This is based on what is needed to inform engineering development of the design. It is up to the contractor to define details for the radiation test campaign.
81If a component fails radiation testing, does this trigger a redesign loop that could delay PDR, and what is the process for adjudicating that risk?Such an event may be addressed in engineering activities before PDR, or may be identified during PDR and addressed in continuing design activities leading up to CDR.
82Objective 1 vs. Objective 2 interdependency: The PDR design is supposed to represent the "flight system design," but the ETU may not fully match flight unit size, weight, and design life. How does NASA reconcile a PDR flight design with an ETU that is explicitly non-flight-representative?
What is the required fidelity of the EDU vs the PDR design of the Flight System? To meet the 18month delivery schedule it may not be possible for the ETU to be fully representative of all aspects of the PDR design. Is this acceptable to NASA?The contractor is required to provide traceability between flight and ETU requirements.
83The SOW explicitly states these ConOps events are "not within scope of Task Order 1" — yet V6 now requires the contractor to develop a candidate ConOps (Section 5, item g). What is the contractual relationship between the reference ConOps in 2.2 and the contractor-developed ConOps deliverable? Are they expected to align, or is the contractor free to diverge?

V6 added the caveat that "LR-1 has not been chosen for a particular mission." Does this mean the 7-step ConOps sequence in 2.2 is purely notional and non-binding for design purposes, or does it still define the design driving scenarios the contractor must accommodate?

Request NASA consider adding a CONOPS step after step 3 off-loading to have NASA connect the NASA provided power cable(s) to the LR-1 prior to reactor power up.

LR-1 Phase 1 ASTO SOW Section 2.2 CONOPS items 2 & 3. Request NASA add the CONOPS assumption that the lander will provide up to 2 kW electrical power to the LR-1 during flight, descent and landing through the completion of LR-1 surface deployment and that short periods of no landing provided power during descent are acceptable.

Please clarify whether offloading LR-1 from the lunar lander is a requirement or whether an offeror may propose operating LR-1 on or integrated with the landed vehicle if all LR-1 requirements and User interfaces are satisfied.The ConOps provided in the LR-1 SOW is notional. The contractor will be required to define a ConOps which aligns with their proposed flight design.
84What are the specific environmental loads (shock, vibration, thermal) the contractor should design to? Are NASA-provided launch vehicle and lander interface load specifications available, or must the contractor bound these themselves?Environment requirements are requested from the contractor as part of the DRD LR1-SE-001. See modifications in the final RFP SOW.
85"Fully safe state" implies subcriticality throughout launch and transit — what is the acceptable methodology for demonstrating this (LR1-28 requires two independent hardware methods)? Are specific approaches preferred or prohibited?It is up to the contractor to design and propose an LR-1 system to meet this requirement.
86The SOW says the contractor is not responsible for interface compatibility with rovers and utility systems — but deployment requires some physical interface. Where exactly does the LR-1 system boundary end and the lander/rover interface begin?The LR-1 boundary is idenfitied by the RFP. It is the responsibility of the contractor to control that interface via requirements.
87Is remote startup (Earth-commanded) the only required mode, or must the system be capable of autonomous startup without real-time ground contact (consistent with LR1-10)?
What communication assumptions should the contractor use for autonomous operation design?See modifications in the final RFP SOW.
88What defines "stable operating condition" — is it a specific Brayton speed, turbine inlet temperature, or electrical output threshold? This needs to be defined to establish ETU test success criteria.It is the responsibility of the contractor to identify the needed test campaign for the scope of the LR-1 Phase 1 TO. Please review RFP evaluation criteria.
89What constitutes a "demonstration" of functionality in the context of the actual lunar mission — is a single successful steady-state run sufficient, or must the system cycle through all states multiple times?It is the responsibility of the contractor to identify the needed test campaign for the scope of the LR-1 Phase 1 TO. Please review RFP evaluation criteria.
90How does the ETU demonstration (Objective 2) map to Step 5 of the ConOps? Is the ETU expected to replicate this operational sequence, and if so, does it need to demonstrate all operating state transitions?
Do any Table 1 standards apply to the ETU, its GSE, or ground test operations? If so, which?The contractor should identify how the requirements and ConOps for the flight design trace to ETU requirements.
91After permanent reactor shutdown (LR1-16), what are the decay heat management requirements? The reactor will continue generating decay heat for years after shutdown — is passive cooling assumed, and must this be demonstrated during Phase 1?Please review modification to the RFP SOW.
92LR1-17 requires depletion/control of all stored energy sources — for a Brayton system, this includes pressurized working gas. What are the acceptable passivation methods, and does NASA have a preferred approach?It is up to the contractor to design and propose an LR-1 system to meet this requirement.
93The SOW mentions "post mission disposal" but the reactor will remain on the lunar surface permanently. What is NASA's definition of "disposal" in this context, and does it have radiological consequence implications for future surface operations?In this context, "disposal" may be read as "passivation." Please review the the final RFP.
94Communications architecture: V6 changed LR1-10 to reference "intermittent communications from Earth" — but the ConOps does not define the communication link characteristics (latency, bandwidth, availability).The contractor will be required to define a ConOps which aligns with their proposed flight design.
95NASA states it does not intend to evaluate Major Subcontractors at the SPARC level and invites comment on whether that is appropriate. Inertia Tek LLC does not object to the burden reduction, but notes a consequence worth addressing.

If the team is not evaluated at the MAIDIQ level, team composition proposed at that level carries no evaluated weight, and the Small Business Utilization Plan submitted under Attachment J.2-3 can be restructured after award without consequence. Small businesses are then asked to commit capability and proposal effort at the stage where that commitment is least protected.

Recommendation: either evaluate Major Subcontractors at the SPARC level, or, if the current approach is retained, require that commitments made in the Small Business Utilization Plan be carried forward into task order proposals and reported against at the task order level. The second preserves the intended burden reduction while keeping the commitment real.Please review the final RFP.
96Accounting system adequacy under SF 1408 is normally determined in a pre-award survey conducted against a specific contract action. A company that has not previously held a costreimbursement contract has no route to obtain that determination in advance. The same pattern applies to Earned Value Management System validation, which is ordinarily established on a contract requiring it. Where system status is presented to the Source Selection Authority for consideration, a firm can therefore be disadvantaged for the absence of a determination it had no mechanism to obtain.
Recommendation: where system assessments are presented to the Source Selection Authority, distinguish between a firm found inadequate and a firm that has had no opportunity to be assessed. Alternatively, state that the absence of a determination will not be treated adversely where the offeror's proposed scope does not require the system in question.Please review the final RFP.
97Will a ROM pricing for full delivery of a lunar surface demo unit, beyond Phase 1 ETU, be requested?Please review the final RFP.
98Contract Line Item Numbers

We recommend providing the contract structure/requirement for the end solution as it is currently unclear as to the applicability of clauses or contract structure to the end goal versus the individual task orders. Number of task orders is still undefined as is the intent of each TO past PDR and how the current contract structure aligns to future task orders, i.e., how much separate negotiation, onboarding, and proposal effort will be required per task order?

We request clarity on how NASA intends to utilize the CLINs and recommend allowing suppliers to include a long-lead CLIN / line item / etc. for future potential task order support (i.e., for TO1, include long lead CLIN for procurements necessary to meet CDR timeline). We also recommend the consideration of costtype CLINs for high development efforts, and possible sub CLINs for study or support efforts.Please review the final RFP.
99NASA Reservation of Right to Modify Contract Terms to Facilitate Solicitation and Award Task Order for Lunar Reactor Flight System currently provides NASA the broad and openended ability to change contract terms to facilitate award of task orders. While we understand the need for this ability, it presents contractors with risk in the shape of possible changes to scope, schedule, period of performance, contract value, and contractual responsibilities. We seek clarity as to the limitations of this process, and how it is tied to each TO and the overall IDIQ. This should be explicitly tied to the Changes clause, and detail any possible notice and comment period to allow Contractors to determine possible impacts and provide proposals for equitable adjustment if necessary, or provide feedback for ways to solicit such task orders within the then current scope and terms of the contract. Limiting or eliminating task order related contract changes would limit uncertainty on future task orders and costing for those task orders.Please review the final RFP.
100Concerning 'NASA plans to require at least one performance and at least one delivery incentive to be proposed and evaluated at the ASTO-level. NASA is seeking feedback regarding reasonable performance and delivery incentives.'
1)We recommend a schedule/delivery incentive fee of a TBD percentage of Task Order FFP contract value or a set dollar value of incentive per milestone to incentivize faster delivery of artifacts. The FAR 52.211-11 Liquidated Damages – Supplies, Services, or Research Development presents a costing risk for contractors. In the event Performance-Based Payments or incentives are included, consider removal of this liquidated damages clause as payments will be tied to milestones or incentives.
2)Section L references Performance incentive fee and Delivery Incentive Fee. Is that intended to be included on the LR-1 Task Order bid or is that referenced to be proposed on future IDIQ Task Orders? Should we assume that LR-1 Task Order 1 is Fixed Price Incentive Fee?Please review the final RFP.
101Regarding attachment J.2-7, Financial reports appear to be standard for a Cost-Plus type contract. On a FFP Task Order, recommend that the financial deliverables and reporting requirements are minimal (schedule deliverable only). On Cost-Plus Task Orders, the financial reports are reasonable.Please review the final RFP.
102Is CLIN 1 set to be a FFP contract with a cap of $350MPlease review the final RFP.
103Please clarify the required safety requirements for preventing inadvertent criticality. The SOW lists compliance with NSPM-20 (no failure tolerance requirement, limit based on likelihood and consequence) (LR1-27), LR1-28 that requires 'at least 2 independent means' (1 failure tolerant), and NASA-STD-8719.24 Payload Safety Requirements that requires 3 inhibits against a catastrophic hazard (2 failure tolerant) (LR1-29). How should contractors interpret and apply the three differing requirements?

Please clarify whether single-failure-tolerance requirements permit a reliability-based exception where added redundancy or additional components can be demonstrated to reduce overall system reliability. We recommend permitting an offeror to demonstrate compliance through quantitative reliability and fault-tolerance analysis where appropriate. Design to at least two independent hardware methods (LR1-33), show by analysis that the NSPM-20 probability limits are met (LR1-32), and document both through a phased safety process modeled on NPR 8715.7 and NASA-STD-8719.24 (LR1-34).

The three requirements cover different things: one is the design requirement, one is the launch risk test and one is the safety process. They should be applied together, not treated as competing failure-tolerance rules.

1.LR1-33 is the design requirement for preventing criticality. LR-1 must prevent inadvertent criticality using at least two independent hardware methods, in both normal and accident conditions. This makes the design single-failure tolerant against inadvertent criticality, which matches LR1-19 ("at least single failure tolerance to catastrophic events"). Accident conditions include, but are not limited to, impact on dry land, burial in wet sand and immersion in water (ocean). Each method must keep the reactor subcritical on its own, with a margin the contractor proposes and justifies.
2.LR1-32 (NSPM-20) is the launch risk test. NSPM-20 sets no number of failures the design must tolerate. Its safety guidelines are probability-based limits on public exposure:

-Exposure above 25 mrem but below 5 rem TED: probability no greater than 1 in 100.

-5 to 25 rem TED: probability no greater than 1 in 10,000.

-Above 25 rem TED: probability no greater than 1 in 100,000.

These limits come from NSPM-20 Section 3. The "safety guidelines identified in NSPM-20" referenced in LR1-28 are these probability limits; NSPM-20 itself does not set a criticality design rule. The two-method design in LR1-28 is the minimum, and the contractor's safety analysis must show it meets the NSPM-20 limits. If the analysis shows two methods aren't enough for some accident scenario, more design measures are required. Launches of fission systems with potential for criticality fall in Tier II (low-enriched uranium) or Tier III (any other fuel), and get additional interagency safety review.trumpwhitehouse.archives

3. LR1-34 asks for a safety process, not a three-inhibit design. It requires a safety process "similar to" the Payload Safety Process in NPR 8715.7 and NASA-STD-8719.24: hazard analyses, hazard reports and data supporting the Government's phased safety reviews. It does not impose the NASA-STD-8719.24 Annex §3.2.1 requirement for three inhibits (dual failure tolerance) on reactor criticality controls. Secion 3.2 defines catastrophic hazard dual failure tolerant is for systems without specific design criteria. The Annex's rules for what counts as a valid inhibit may be used as guidance for showing the LR1-28 methods are independent and valid:

-Independence -Verifiability -Common-cause protection -Hardware only; software and operator controls don't count

4. DOE criticality safety (LR1-30) applies to ground activities. DOE O 420.1's criticality safety requirements, including the double-contingency principle, govern fissile material work outside the reactor: fuel fabrication, storage, transportation and ground test setups. They add to the LR1-28 flight design requirement but don't replace it.

104Please clarify the safety approval authority, applicable standards, and any safety reviews required for LR-1 lunar surface operations. Is the Preliminary Hazard Analysis (PHA) the only safety analysis required in TO1 addressing LR-1 lunar surface operations? Are any other NASA and/or DOE safety standards or safety reviews/boards be applicable to LR-1 lunar surface operations?This is outside the scope of the LR-1 Phase 1 TO.
105Please clarify the scope of the PHA. The DPD description states it covers manufacturing, assembly, launch, and in-space operation of the LR-1 system; however, other safety analyses also address those same phases (e.g. NRC licensing addresses reactor manufacturing, DOE standards/DSA address reactor processing at the launch site, MSAR/INSRB process addresses launch safety, etc.).Please review the final RFP.
106Instructions for the Mission Suitability Appendix provides a list of attachments to be included. The Government also referred to Attachment J.1-4 SPARC Small Business Subcontracting Plan in instructions for the Small Business Participation section of Volume I, but that attachment is not among the draft solicitation documents.
1)Is Attachment J.1-4 SPARC Small Business Subcontracting Plan intended to provide the same information as Attachment J.2-3 SPARC Small Business Participation?
2)Will Offerors be required to submit Attachment J.1-4 Small Business Subcontracting Plan with the proposal in addition to Attachment J.2-3 SPARC Small Business Participation?
3)Would the USG consider asking Offerors to submit Attachment J.1-4 Small Business Subcontracting Plan following contract award, rather than with the proposal? 4) Would the USG consider permitting Offerors to submit their own small business subcontracting plans in lieu of Attachment J.1-4?Please review the final RFP.
107We request clarity on “destination” for inspection and acceptance of deliverables. Currently inspection, acceptance, and by extension transfer of title and risk of loss are described as taking place at “destination”. Is this at KSC/Cape Canaveral, or is it on initial activation on the lunar surface, or another point of transfer? We request determination of when title and risk of loss transfers from Contractor to Government for each deliverable expected under the Contract and each task order.Please review the final RFP.
108Pursuant to the ASTO SOW, contractor is responsible for submitting the proper application through DOE to acquire HALEU fuel. Language is unclear as to contractor license requirements and what party maintains possession of HALEU fuel prior to integration.See responses to industry day questions.
109Since this program presents certain risks to Contractors, would it be possible to include FAR limitation of liability language, such as 52.246-24 Limitation of Liability High-Value Items and 52.246-25 Limitation of Liability – Services to provide standard protection for certain services and deliverables.Please review the final RFP.
110Please verify/confirm if 52.224-2 Privacy Act is applicable, as it applies to solicitations and contracts when the design, development, or operation of a system of records on individuals is required to accomplish an agency functionPlease review the final RFP.
111Request inclusion of PL 85-804 related language in addition to 952.250-70. 952.250-70 provide primary protection under a statutory regime for nuclear “public liability” whereas PL 85-804 can provide additional support with specific contractual risk definition, for unusually hazardous or nonnuclear risks that fall outside of Price-Anderson coverage. Combining the two indemnity mechanisms provides complete coverage across risk categories and does not double recovery on the same claim. 952.250-70 serves the mandatory, specialized framework for nuclear incidents and precautionary evacuations tied to contract work; Public Law 85-804 is a discretionary, approval-based tool for other contract-defined unusually hazardous risks that facilitate the national defense and energy sector. Together they close gaps neither closes alone. Furthermore, 85-804, as a contractual risk definition can help provide coverage over certain unclear definitions in 952.250-70, namely how risk protection extends to space and the lunar surface, given that the coverage definitions are limited to domestic and foreign geographies, and do not explicitly refer to space or lunar geographic areas.Indemnification may be addressed during potential future project phases.
112If TRL 5-6 for all subsystems is required at PDR, is additional HW development (build/test) beyond the ETU expected? If additional HW development (build/test) is required to get a subsystem to TRL 5-6, is that in scope for TO-1?The contractor should perform all hardware development needed to achieve the LR-1 Phase 1 TO activities as defined in the SOW. Please review the final RFP.
113Will Offeror have the opportunity to provide a Data Assertions list to outline data rights and restrictions as part of initial proposal, to be incorporated as an attachment to the SPARC contract or TO?This is solicited this as part of the contract. Please review the final RFP.
114How does NASA define “independent” in the preventing inadvertent criticality under all conditions requirement (LR1-28)? Does NASA require 2 fully dissimilar hardware means for preventing criticality, is similar redundancy acceptable as long as it’s separated/no common cause?Two independent dis-simlar means to prevent inadvertent criticality.

Two methods are independent when no single credible failure, event, error or environment can defeat more than one of them. This follows the NASA Annex to NASA-STD-8719.24 definition: "not capable of being influenced by other systems." It also follows the Annex rule that one failure cannot negate more than one inhibit. In practice:

-Each method works on its own. Each must keep the reactor subcritical by itself, in every normal and credible accident configuration.

-No shared failure path. The methods must not share a failure path through power, command or control circuits, actuators, release mechanisms, software, structural load paths or support structure.

-Common-cause failures are addressed. This includes accident environments that act on both methods at once, such as impact deforming the core geometry, or water entering the core and increasing moderation or reflection. It also includes common manufacturing, material or installation defects.

-Each method is hardware and verifiable. Software, operator actions and command logic are controls that operate an…

This is the start of the file's text. The full file is on GovTribe.

File details come from the government source that posted it. Updated .