Q_A 1.pdf
PDF 688 KB Posted
- Solicitation number
- N0001425SBC04
About this file
This is a Questions and Answers document addressing inquiries from offerors regarding a Office of Naval Research (ONR) contract opportunity for the development of a Large Underwater Vehicle Demonstrator (OEX).
The document clarifies critical proposal and technical requirements. The technical proposal and Statement of Work combined shall not exceed 50 pages, excluding full-page graphics. Phase 1A (Preliminary Design) has a 12-month duration, while Phase 1B (Detailed Design) pricing should reflect the contractor's best cost estimate, with the Government awarding cost-reimbursement contracts including Limitation of Cost (FAR 52.232-20) and Limitation of Funds (FAR 52.232-22) clauses. Regarding technical approach, the Government allows design divergence between prototype and production vehicles and expects contractors to propose reasonable critical paths; detailed battery performance data and Battery Management System specifications will be provided at contract award, dependent on industry partner finalization expected in June/July 2026. For autonomy software, the Government specifies no preferred framework but requires well-documented open architecture with TRL 3 or 4 assessment at Phase 1B conclusion. The communications architecture will specify performance, space, and weight requirements rather than mandate specific government-furnished systems, allowing contractors to propose alternative solutions. A dedicated Government team will facilitate close interaction with contractors regarding the Government-furnished propulsor integration, with turnaround times as fast as possible. Finally, the Government will provide general guidance on alternative payload concepts during kickoff to support vehicle design modularity, with a second notional payload configuration under development.
View the file
Other files
| File | Type | Posted |
|---|---|---|
| Attachment 4 Rev1.pdf | ||
| N0001425SBC04 Amendment 006.pdf | ||
| N0001425SBC04_Amendment 005.pdf | ||
| Attachment 4.pdf | ||
| N0001425SB04_Amendment 004.pdf | ||
| N0001425SBC04_Amendment003.pdf | ||
| Attachment 1 Rev1.pdf | ||
| N0001425SBC04_Amendment_002.pdf | ||
| Attachment 3. OEX Memo.pdf | ||
| N0001425SBC04_Amendment 001.pdf | ||
| Attachment 1.pdf | ||
| Q_A.pdf | ||
| N0001425SBC04.pdf |
Show all 13
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
Government File Name Page Para Question/Comment Rationale Government Response
Attachment 4 - Detailed Proposal Information
1 4
Please confirm that the 50 page proposal limit (exempting full page graphics) applies to the technical proposal, the SOW, and the data rights description. The page limit will not apply to the proposal checklist, DCAA accounting system checklist, and ONR Contract Specific Reps and Certs.
Please see revised attachment 4. Technical Proposal and Statement of work combined shall not exceed 50 pages plus exempted full page graphics.
Attachment 4 - Detailed Proposal Information
1 4
For Phase 1B Option pricing, we respectfully request an extension to submittal of a firm proposal price for costs are highly dependent on the results of Phase 1A and the amount of potential design updates required.
The Government understands the complexity and plans on awarding a cost-reimbursement contract(s) that includes FAR 52.232-20, Limitation of Cost and FAR 52.232-22, Limitation of Funds. Offerors should provide their best cost estimate for Phase 1B.
Attachment 4 - Detailed Proposal Information
2 2
The document includes the statement: "The Government desires an overall duration of 1 year for Phase I." Does this mean 12 months for Phase 1A Preliminary Design or all of Phase 1 (1A Preliminary Design and 1B Detailed Design)?
Please clarify.
BAA Call N0001425SBC04 Amendment 0005 states that the period of performance for projects may be from 1 to 3 years, so an overall period of performance for all of Phase 1 (1A and 1B combined) of 1 year would conflict with this guidance.
The 12 months refers to the preliminary design, Phase 1A, only.
Attachment 4 - Detailed Proposal Information
1 A.1
The BAA requires offerors to describe how the Production and Prototype design efforts are "integrated and sequenced to accelerate the Prototype design products".
Will ONR provide guidance on the acceptable level of design divergence between the Prototype and Production vehicles? For instance, what specific subsystems of the Production vehicle design must reach a certain maturity level before the corresponding Prototype Preliminary Design Review (PDR) can occur?
The BAA creates a direct tension between accelerating the prototype and maintaining design fidelity with the production vehicle.
This question aims to clarify the Government's priority and risk tolerance.
The answer is critical for developing a realistic Integrated Master Schedule (IMS) that correctly identifies dependencies and critical paths demonstrating proactive risk management.
No. The Government realizes that many of the critical subsystems do not have precise definitions, as such it’s expected that the contractor will attempt to specify subsystems that they believe will meet the stated functional requirements (as documented in the GFI).
Divergence between the prototype and production is expected and will be driven by the complexity, required design effort, schedule, and estimated costs. The contractor should propose critical paths that are reasonable. Where there does not appear to be a solution within the 1-year effort, an agreement on how to approach the transition to detailed design will be developed jointly.
Attachment 4 - Detailed Proposal Information
3 C.1
The BAA notes that data on battery packs may be provided with Limited Rights. Given that the battery is fundamental to the "endurance" S&T challenge, at what point will offerors have access to the full dynamic performance models (e.g., discharge curves under various load profiles, thermal characteristics) and detailed API specifications for the Battery Management System (BMS)?
A vehicle's energy budget is a dynamic calculation that depends on how the battery performs under operational loads. To create a credible "Vehicle Energy Budget" deliverable, our team needs detailed performance data, not just a nameplate capacity. Vehicle endurance is a complex, system-level problem.
Detailed battery performance information and BMS will be provided at the time of award. However, the level of detail will be highly dependent on the industry partner finalizing the pack for series production, which is expected in June/July 2026.
Attachment 4 - Detailed Proposal Information
1 A.2
The BAA identifies "robust autonomy" as a key S&T challenge. Could ONR clarify the expected Technology Readiness Level (TRL) for the core autonomy software at the conclusion of Phase 1B? Are there specific Government-preferred autonomy frameworks or middleware that should be used to facilitate future integration with the specified payload?
"Robust autonomy" is subjective. Software maturity directly impacts the scope and risk of the software development effort.
No. There is no preferred autonomy framework or middleware, but the Government's preference is for a well-documented open architecture. The offeror should justify their choice in framework and middleware based on their proposed solution. There is no requirement for a minimum software maturity level for all components at the end of Phase 1A; however, the Government expects the detailed design to document the software maturity of all critical software component to provide an assessment of risk and identify R&D requirements. At the conclusion of Phase 1B, the autonomy should be assessed to be TRL 3 or 4.
Attachment 4 - Detailed Proposal Information
2 A.4
"External communications" is a primary S&T challenge and a classified "Communications Architecture" will be provided as GFI. Does this GFI document define specific Government-furnished communication systems, or does it define performance requirements (e.g., bandwidth, latency) that the offeror's proposed solution must meet?
There is a significant difference in scope and risk between integrating a pre-defined Government radio and designing a communications solution to meet a performance specification.
At the time of the award, the Government will specify performance, space, and weight requirements for a system that notionally meets the DRM and requirements.
Additionally, the Government will provide information on risk reduction efforts and communication system prototyping results that are being performed. The performer may propose their own communication system if desired.
Attachment 1-Rev-1 - Additional Information
11 E.2
The "Propulsor" is listed as Additional Government Furnished Information. To effectively manage technical risk, what is the defined process for resolving interface conflicts (mechanical, electrical, data) between our vehicle design and the GFE propulsor design? What is the Government's expected turnaround time for facilitating technical data exchanges and joint design decisions?
Integrating a major GFE component is a classic source of schedule delays. This question addresses the practical process of co-design, interface management, configuration control, and inter-organizational risk.
The Government will have a dedicated team that helped develop the Government concept design. This team will facilitate close and frequent interaction with the Contractor on the details of the propulsor, integration, and performance estimation. The speed of interaction will depend on the complexity, but the expected turnaround time is as fast as possible. Note: there are no defined electrical or data requirements present in the GFI for the propulsor itself.
Approved, DCN# 2026-1-22-1905 01/29/2026
DISTRIBUTION STATEMENT A. Approved for public release: distribution is unlimited. 1 of 2
Attachment 1-Rev-1 - Additional Information
11 E.3
The BAA describes the OEX as a "Large Underwater Vehicle Demonstrator" and requires a "Payload ICD" as GFI.
Beyond the initial objective payload, are there anticipated specifications (e.g., ranges for volume, weight, power, and data interfaces) for future notional payloads that should be considered in Phase 1 to ensure the modularity of the core vehicle design?
Modularity requires designing for future, undefined needs, not just the first use case.
ONR will soon be working on a second notional payload configuration that should help broaden the utility of the modularity concept. The completion time of the second concept is to be determined. However ONR will give general guidance on alternative payload concepts during the kickoff meeting.
Approved, DCN# 2026-1-22-1905 01/29/2026
DISTRIBUTION STATEMENT A. Approved for public release: distribution is unlimited. 2 of 2
File details come from the government source that posted it. Updated .