Att. 5 LHA 10 MCS RFI Questions & Navy Response.xlsx
XLSX spreadsheet 20 KB Posted
- Attached to
- Amphibious Assault Ship (LHA 10) Machinery Control System (MCS) Request for Information (RFI)
- Solicitation number
- N0002425R2411
About this file
This document is a Questions and Answers (Q&A) file for a Navy Request for Information (RFI) regarding the Amphibious Assault Ship (LHA 10) Machinery Control System (MCS). The RFI covers a Firm-Fixed Price (FFP) contract opportunity, with the Navy clarifying several key points through bidder questions. Important details include: the RFP will focus solely on MCS requirements and installation support, with an anticipated period of performance extending through shipboard delivery; training will be conducted post-MCS software delivery. The Navy indicates that certain detailed documents (such as sections referenced in document 202, signal lists, and CDRLs) may be provided upon request, contingent on active SAM registration. Bidders are advised that the ROM (Rough Order of Magnitude) should include Ship Integration and Test efforts, and that Shipyard requirements will be removed from future solicitation documents.
View the file
Other files
| File | Type | Posted |
|---|---|---|
| SECTION 202 MACHINERY CONTROL SYSTEMS.pdf | ||
| SECTION 402 SECURITY REQUIREMENTS.pdf | ||
| SECTION 409 HME and LAN.pdf | ||
| LHA 10 MCS RFI dtd 2.10.25.docx | DOCX document |
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
Bidders Questions
| # | Question | Proprietary (Y/N) | Navy Response |
| 1 | Is there a RFI Response Page limit? | N | No |
| 2 | What is the anticipated Contract Type? | N | Firm-Fixed Price (FFP) |
| 3 | There seems to be a mix of MCS provider and Shipyard requirements. Was that intended or will the Shipyard requirements be removed in the future? | N | Yes. RFP will only cover MCS req including installation support. |
| 4 | Should the ROM include Ship Integration and Test effort (ex. room arrangements) | N | Yes |
| 5a | Is the development and maintenance of the signal list a shipyard or MCS scope item? | N | Shipyard |
| 5b | Is there a base signal list, and if so, please provide. | The Signal from LHA 8/9 may be provided upon request and verification of an active SAM registration. Requests can be sent via email to nicholas.w.boyles.civ@us.navy.mil and elizabeth.feliciano-hernandez.civ@us.navy.mil. | |
| 6 | Is there a list of CDRLs, if so, can USN provide along with the DIDs. | N | LHA 10 MCS CDRLs are not available at this time. A list of LHA 8 CDRLs and LHA 9 SDRLs may be provided upon request and verification of an active SAM registration. Requests can be sent via email to nicholas.w.boyles.civ@us.navy.mil and elizabeth.feliciano-hernandez.civ@us.navy.mil. |
| 7a | Does the USN want the ROM to include support for the Ship Integration and Test effort of the MCS? | N | Yes |
| 7b | What would be the expected period of performance of that effort post MCS delivery to the shipyard? | N | Period of Performance (PoP) will extend through delivery and the ROM is expected to cover shipboard installation support. |
| 8 | Is training conduct covered outside of the main period of performance / post MCS software delivery? | N | Yes, training is typically covered post MCS software delivery to ensure the training properly captures the delivered product |
| 9 | Is there a GFE list, if so, can USN provide? | N | Refer to the RFI for interface requirements to GFE |
| 10 | Please provide copies of the sections reference in 202 that the bidders are required to be compliant with, as follows; | N | The Sections referenced in 202 may be provided upon request and verification of an active SAM registration. Requests can be sent via email to nicholas.w.boyles.civ@us.navy.mil and elizabeth.feliciano-hernandez.civ@us.navy.mil. |
| 72 | N | ||
| 73 | N | ||
| 80 | N | ||
| 86 | N | ||
| 100 | N | ||
| 235 | N | ||
| 241 | N | ||
| 252 | N | ||
| 256 | N | ||
| 259 | N | ||
| 262 | N | ||
| 300 | N | ||
| 305 | N | ||
| 310 | N | ||
| 314 | N | ||
| 320 | N | ||
| 408 | N | ||
| 430 | N | ||
| 436 | N | ||
| 438 | N | ||
| 512 | N | ||
| 521 | N | ||
| 522 | N | ||
| 529 | N | ||
| 531 | N | ||
| 532 | N | ||
| 551 | N | ||
| 555 | N | ||
| 561 | N | ||
| 604 | N | ||
| 11 | Please provide a copy of project-peculiar document, NAVSEA No. 802-8935889 | N | The project-peculiar document will not be provided with this Request for Information. |
File details come from the government source that posted it. Updated .