Government Answers to STEB Draft RFP Questions-7.17.24.pdf
PDF 210 KB Posted
- Attached to
- Submarine Tethered Expendable Buoy (STEB)
- Solicitation number
- N0002424R6231
About this file
This document contains the government's answers to questions regarding a draft Request for Proposals (RFP) for the Submarine Tethered Expendable Buoy (STEB) system procurement. The STEB system provides a submerged submarine with a surface buoy platform for communications, situational awareness, and collision avoidance data. The procurement is for the development, integration, testing, production, and installation of the STEB system.
The key details include: the procurement will be a single source Indefinite Delivery Indefinite Quantity (IDIQ) contract; the draft RFP is 117 pages long and does not include Sections K, L, and M; the government will provide classified documents, such as the STEB Performance Specification, upon request after the final solicitation is released; the first production delivery order under the IDIQ is anticipated to use a Cost-Plus Incentive Fee (CPIF) contract type; and there will not be a classified industry day prior to solicitation release.
View the file
Other files
| File | Type | Posted |
|---|---|---|
| DRAFT N00024-24-R-6231_STEB_Solicitation.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
Question Number Topic/Section Question Government Answer
1 Classified Portion Will there be any classified portions of the solicitation? Nothing for the proposal submission/ in the proposal should be classified. The performance spec is classified (which is an Attachment to the solicitation) and that will be sent to interested parties upon request once the formal Solicitation is posted.
2 SAM Posting Response Date
Top of SAM.GOV references “Original Response Date: Jul 03, 2024 04:00 pm EDT” but the paragraph (3rd from last on SAM.GOV) on “….specific questions or comments….”
doesn’t reference a due date. Please clarify due date details.
Jul 03, 2024 04:00 pm ensures that USG will answer as part of Q&A answers posted SAM.GOV, if received after Jul 03, 2024 04:00 pm then might not get included in Q&A posted in future.
3 Sections K, L, M
Attached “DRAFT N00024-24-R- 6231_STEB_Solicitation.docx” is 117 pages long meaning sections K, L, M are missing from Draft RFP. Confirm this was intentional.
The Government specifically didn’t include sections K, L, M. Will be provided with final solicitation.
4 Sections L & M Can the government provide drafts of Sections L & M prior to release of the final RFP? No, the Government will provide Sections L&M with final solicitation release
5 Section K
The draft RFP Table of Contents has Section K as pages 117-136, but only page 117 is populated. Can the government provide the full Section K prior to release of the final RFP?
No, the Government will provide Section K with final solicitation release
6 Performance Spec
For our planning purposes, when does the Government anticipate releasing the following documents?
(1) PMS 435-STEB-PS-00xx-xx[TBD] System Performance Spec (attachment 2),
(2) DCU0123674 STEB Mechanical ICD,
(3) DCU0123610 STEB Electrical ICD,
(4) NAVSEA 8827061 3-inch launcher interface control drawing,
(5) STEB PDD-002 Payload Design Document and Interface Control Document,
(6) STEB-REQ-00 Requirements for STEB
(7) STEB-TRD-01 (operational environment and related requirements)
Will be provided upon request after final solicitation is released.
7 Design Is the current sensor design complete and does it meet all STEB requirements?
The IWS5A design is complete, but untested. Therefore, it is unclear if it meets all the requirements. It should be noted this STEB contract is based on a SOW & Perf Spec and is not a built to print contract.
8 Design If sensor design is not complete, how does that affect the production schedule in the RFP?
The success or failure of the IWS5A R&D efforts do not directly impact the production schedule in the solicitation. This contract is based on a SOW & Perf Spec and is not a built to print contract. Whatever is learned by the IWS5A efforts will be shared and will be useful to the performer on the new STEB contract.
9 GFI
Will the government be providing GFI describing the STEB bus, and if so, can it be provided prior to the final RFP release?
Yes, GFI will be provided. No, the GFI will not be provided before the final solicitation release.
10 TIs When the government issues TIs, how will the number of hours for each TI be determined?
The initial TI will be a Government estimate for the initial efforts needed to start the STEB design efforts. After that, they will be based on discussions with the contract performer.
11 SCG Is there an SCG for STEB and can it be provided?
Includes the following SCGs:
- SCG ID# 05-037.3 Submarine Warfare Matters
- SCG ID# 05-069.5 Periscopes
- SCG ID# 06-060.2 Common Submarine Radio Room (CSRR)
- SCG ID# 08-069.5 AN/BLQ-10(V)
12 GFI
Will the government be providing GFI describing interfaces (mechanical and software) between STEB and platform systems such as BLQ-10?
To the degree that it exists, yes. The eventual contract winner for STEB will work with the BLQ-10 integrator to finalize those details.
13 CLIN 0001
On page 2 of the Draft RFP, CLIN 0001 is identified as CPFF. On page 6, Note D indicates that CLIN 0001 will have a 50/50 share ratio. Could the government please clarify whether CLIN 0001 is intended to be CPFF or
CPIF?
CLIN 0001 will be CPFF. Final solicitation will remove the share ratio language throughout the solicitation.
14 Section B - CLIN 0001 CLIN 0001 - Please clarify if this CLIN is intended to be CPIF or CPFF.
CLIN 0001 will be CPFF. Removed share ratio language throughout for CLIN 0001.
15 Note D - CLIN 0001 CLIN 0001 - Please clarify if this CLIN is intended to be CPIF or CPFF.
CLIN 0001 will be CPFF. Removed share ratio language throughout for CLIN 0001.
16 CLIN 0005 FFP indicated as type and also noted as NSP Concur, CLIN 0005 is NSP.
1.4 Open Systems Architecture
Approach and 3.2.13 Use of Contractor Facilities
Section 1.4, indicates a 30 calendar days timeframe for contractor to provide advance notice of "...any events, test or activity that the Government identifies as a specific item of interest." Section 3.2.13 refers to 14 calendar days.
Section 3.2.13 changed to read as "...The Contractor shall notify the Government a minimum of thirty (30) calendar days in advance of any such peer review, tests, events, and/or inspections."
18 3.4.10 Risk Mitigation
CDRL A002 in 3.4.10 is referred to as Monthly Management Report. A002 is also referenced as the Integrated Program Management Data and Analysis Report elsewhere. Should this be A001 in 3.4.10?
Section 3.4.10 changed to read as "...Identified risks and mitigation actions shall be reported as part of the Contractor's Progress and Status Report (CDRL A001) "
19 3.7 Depot and Hardware Repair Support
CDRL A032 and CDRL A040 are both referenced as Technical Report – Study/Services. Section 3.7 changed to read as "...(CDRL A040, Technical Report – Study/Services)."
20 3.8.3.1 ECPs Complete CDRL reference is missing for Specification Change Notices. Should this be A049?
Section 3.8.3.1 changed to read as "...the Contractor shall submit Specification Change Notices (CDRL A049, Specification Change Notices [SCNs]."
21 3.23 Field Engineering Services
CDRL A002 in this section is referenced as Contractor’s Monthly Management Report. A002 is also referenced as the Integrated Program Management Data and Analysis Report elsewhere. Should this be A001 in 3.2.23?
Section 3.23 changed to read as "...The Contractor shall submit a summary of field maintenance and repair services as a part of the Contractor's Progress and Status Report (CDRL A001)."
22 4.4.2 - System Baseline Changes See "Error! Reference source not found." Section 4.4.2 deleted the last sentence "Any requested changes or deviations shall be submitted for approval in accordance with paragraph Error! Reference source not found."
52.211-11 Liquidated Damages -
Supplies, Services, or Research and Development
Confirm applicability of this clause Removed clause based on FAR 11.501 (a).
24 5.0 Enterprise Contractor Manpower Reporting Confirm applicability of this reporting requirement It is still applicable.
System Performance Specification for the Submarine Tethered Expendable Buoy (STEB) System (Attachment 2)
When will the latest version of the performance specification and associated documents be made available to interested bidders (specific documents of interest include?)
Latest version of the spec will be provided upon request when the final solicitation is released.
NAVSEA S9070 Technical
Requirements Manual for Temporary Submarine Alteration ACN-5
When will the latest version of the performance specification and associated documents be made available to interested bidders (specific documents of interest include?)
Latest version of the spec will be provided upon request when the final solicitation is released.
Government Answers to Draft RFP Questions - N00024-24-R-6231 STEB
Submarine Tethered Expendable Buoy (STEB): Mechanical Interface Control
Document
When will the latest version of the performance specification and associated documents be made available to interested bidders (specific documents of interest include?)
Latest version of the spec will be provided upon request when the final solicitation is released.
Submarine Tethered Expendable Buoy (STEB): Electrical Interface Control
Document
When will the latest version of the performance specification and associated documents be made available to interested bidders (specific documents of interest include?)
Latest version of the spec will be provided upon request when the final solicitation is released.
29 3-Inch Launcher Interface Control Drawing
When will the latest version of the performance specification and associated documents be made available to interested bidders (specific documents of interest include?)
Latest version of the spec will be provided upon request when the final solicitation is released.
30 Payload Design Document & Interface Control Document
When will the latest version of the performance specification and associated documents be made available to interested bidders (specific documents of interest include?)
Latest version of the spec will be provided upon request when the final solicitation is released.
31 Requirements for Submarine Tethered Expendable Buoy
When will the latest version of the performance specification and associated documents be made available to interested bidders (specific documents of interest include?)
Latest version of the spec will be provided upon request when the final solicitation is released.
32 AN/BLQ-10 Security Class Guide
When will the latest version of the performance specification and associated documents be made available to interested bidders (specific documents of interest include?)
Latest version of the spec will be provided upon request when the final solicitation is released.
33 Sections J, K, L, & M Will these sections be released in draft form prior to the release of the full solicitation? Latest version of the spec will be provided upon request when the final solicitation is released.
34 DD254 Will the DD254 be released for the Program? Yes, upon final solicitation release.
35 STEB Security Classification Guide (SCG) Will the SCG be released for the Program? Yes, upon final solicitation release.
36 MIT-LL Payload Design
Is the – MIT-LL payload design assumed to be representative of the baseline payload?
Will full details of the MIT-LL payload be made available?
It should be noted this STEB contract is based on a SOW & Perf Spec and is not a built to print contract. The GFI will be provided with RFP and including the following data:
| 1. | System Performance Specification for the Submarine Tethered Expendable Buoy (STEB) System |
| 2. | NAVSEA S9070 Technical Requirements Manual for Temporary Submarine Alteration ACN-5 |
| 3. | Submarine Tethered Expendable Buoy Drawing Package |
| 4. | Submarine Tethered Expendable Buoy (STEB): Mechanical Interface Control Document |
| 5. | Submarine Tethered Expendable Buoy (STEB): Electrical Interface Control Document |
| 6. | 3-Inch Launcher Interface Control Drawing |
| 7. | Payload Design Document & Interface Control Document |
| 8. | Electronics Assembly Drawing Package |
| 9. | Payload Assembly Drawing Package |
37 CLINS – POP Is there a notional POP timeline for the various CLINS?
The draft RFP shows them all running concurrently.
This is an IDIQ contract. As defined in Section F, each CLIN has a 5-year PoP
38 IDR (PDR) and CDR (FDR)
The IDR (PDR) and CDR (FDR) are referenced in the draft RFP – but are not identified/defined explicitly like the other SETR events (i.e., SRR, SFR, TRR, FCA SVR. Etc.) – please clarify.
The following sections are added under Section C SOW paragraph 3.3.2:
(c) The Contractor shall conduct a Preliminary Design Review (PDR). The PDR shall be conducted to help ensure the preliminary design for the system under review is sufficiently mature and ready to proceed into detailed design and can meet the stated performance requirements within program budget, schedule, risk, and other program and system constraints.
(d) The Contractor shall conduct a Critical Design Review (CDR). The CDR shall be conducted to help ensure that the detailed design for the system under review is adequate to proceed into fabrication, system integration, demonstration, and test and can meet stated performance requirements within budget, schedule, risk, and other system constraints.
39 Classified Industry Day Is there a Classified Industry Day scheduled – and if so, when is it scheduled for
No, there is not and will not be a industry day.
40 Classified Reference Request
The RFI provided instructions on requesting classified reference documentation (e.g. STEB Performance Specification). The D-RFP doesn't include same instructions. Please identify how companies can request updated classified documents.
Companies will be given instructions on how to request classified documents upon final solicitation release.
41 Section J Pg 115 of 117
Attachment 2 is listed as "(S) System Performance Specification (SPS) for the Submarine Tethered Expendable Buoy (STEB) System" with a revision date of 10JUN2024. Is the 11OCT2023 version the latest version.
When will the updated 10JUN2024 SPS be made available prior to RFP release?
The updated System Performance Spec will be provided upon request after final RFP release.
42 Section B, CLINs 0003-0004 What are the anticipated quantities for units in CLINs 0003 and 0004?
No, max quantity is defined since this is an IDIQ contract. See Section B Note C for information.
43 Target Prices The RFI contained per unit target prices, are those still valid and will updates be provided ?
No, max quantity is defined since this is an IDIQ contract. Per unit target price will be defined after contract is awarded and at Delivery Order. See Section B Note C for information.
44 Referenced Technical Data Will the existing software/firmware from the MIT-LL prototype be provided?
Software/firmware is not included in the GFE/P/M list
45 Referenced Technical Data Will the existing TDP from the MIT-LL prototype effort be provided?
The GFI will be provided with RFP and including the following data:
| 1. | System Performance Specification for the Submarine Tethered Expendable Buoy (STEB) System |
| 2. | NAVSEA S9070 Technical Requirements Manual for Temporary Submarine Alteration ACN-5 |
| 3. | Submarine Tethered Expendable Buoy Drawing Package |
| 4. | Submarine Tethered Expendable Buoy (STEB): Mechanical Interface Control Document |
| 5. | Submarine Tethered Expendable Buoy (STEB): Electrical Interface Control Document |
| 6. | 3-Inch Launcher Interface Control Drawing |
| 7. | Payload Design Document & Interface Control Document |
| 8. | Electronics Assembly Drawing Package |
| 9. | Payload Assembly Drawing Package |
46 Section B, CLIN 0001 - 006(pg. 2 - 5) All CLINs do not include reference to Period of Performance (PoP). Please identify the PoPs for each
CLIN.
All CLINs have an associated ordering period located in Section F of the solicitation.
47 Section B, CLIN 0001 - 006(pg. 2 - 5) Will all CLINS 1-4 be required to be proposed/quoted as part of the response to the F-RFP?
Yes, all CLINs must be proposed. Please ensure to follow the instructions in Section L of the final solicitation.
48 Section B, CLIN 0004(pg. 4)
CLIN 0004 is currently FFP. To be comfortable with using a fixed-price contract vehicle for production, the following metrics ought to be considered:
•Is the system design mature (i.e. thru CDR/PRR), agreed upon by all parties, and unlikely to change?
• Is the system design to be produced proven through developmental testing?
• Are established manufacturing processes in place?
• Are qualified suppliers in place?
• Does a business case exist, for contractors and suppliers, to continue work in the event industry experiences challenges?
This is an Indefinite Delivery Indefinite Quantity (IDIQ) contract with a combination of Cost-Plus Fixed Fee (CPFF), Cost- Plus Incentive Fee (CPIF), and Firm Fixed Price (FFP). The Government anticipates the first production Delivery Order under this IDIQ will be procured utilization the CPIF ordering CLIN.
48 Section B, CLIN 0004(pg. 4)
The prospective offeror's present understanding is that the STEB design is an immature prototype design that requires additional Non-Recurring Engineering Design work to (at minimum) complete design for manufacturability improvements. Consequently, the current status of the STEB design doesn't align with the criteria for using an FFP contract type.
Recommend modifying CLIN 0004 from the current Fixed Price contract type by utilizing one of the following options:
a) Modify the Contract type to Cost Type (e.g. CPIF) for both production CLINs. In this case, all Fixed Price provisions and clauses shall be removed from the solicitation.
b) Reserve the production CLINs 0004 and request a Build to Print proposal once design is stable (post CDR/PRR).
c) If USG requires estimated pricing to evaluate in competition, a preliminary ROM for the production units could be provided in addition to b).
This is an Indefinite Delivery Indefinite Quantity (IDIQ) contract with a combination of Cost-Plus Fixed Fee (CPFF), Cost- Plus Incentive Fee (CPIF), and Firm Fixed Price (FFP). The Government anticipates the first production Delivery Order under this IDIQ will be procured utilization the CPIF ordering CLIN.
Section B, CLIN 0001 (pg. 2)
Section B, Note D (pg. 6) CLIN 0001 reference
CPFF contract types wouldn’t include a share ratio (share ratio is for CP Incentive Fee, e.g. CLIN 0003). Please confirm this was an editorial error or if CPIF was intended for CLIN 0001 too?
CLIN 0001 will be CPFF. Removed share ratio language throughout for CLIN 0001.
50 Section B, Note D (pg. 7)
The last 5 years have shown the volatility of labor markets and labor rates. The Draft RFP implies that the contractor is signing up to a composite rate table set now and utilized for the next 5 years. This provides significant financial risk to the contractor. Recommend adding wording to the affect "“The Parties agree to re-evaluate Hourly Rate for labor market induced change just prior to each new year".
The Government is confident interested offerors can propose to the composite rate table. When Orders are placed under the production ordering CLINs, all the labor required for delivering those production units with be proposed at that time.
51 Section B, Clauses Incorporated by Full Text , Clause B-227-H001 (Pg. 9)
Industry will not accept the undefined nature of B-227- H001 allowing WITHOLDING of PAYMENTS.
Recommend removal/deletion of Clause B-227-H001.
This clause is to be used in all procurements requiring PTD, a PTD is required in Section C 3.8.3.8
52 Statement of Work 1.2 (pg. 12)
Section 1.2 states the following but we provide the recommend underlined edits "This will allow the system to be expandable, upgradeable, and modular to incorporate future antenna and electronic payload designs without requiring redesign to the STEB BUS."
The STEB BUS is intended to be a standard base which then specific payload sensor capabilities are added to.
Section 1.2 updated to read as: "This will allow the system to be expandable, upgradeable, and modular to incorporate future antenna and electronic payload designs without requiring redesign to the STEB Launch Vehicle."
53 Statement of Work 1.3 (pg. 12)
The Collaborative Development Environment (CDE) paragraph mentions "other organizations as needed" - Please define who all of these parties will be so we can consider the impacts (e.g. NDA, scope of CDE, etc.)
What level of CDE tools are expected?
No other organizations are identified at the present. If other organization is identified after the contract is awarded, the Government anticipates no issue with NDA. CDE scope/level are specified in Section C SOW paragraphs 3.1.1 CLIN 0001 and 3.1.2 CLIN 0002.
54 Statement of Work 1.4 (pg. 12)
The Open Systems Architecture Approach allows the Government to reserve the right to witness all Contractor efforts to accomplish the SOW requirements and maintains right to comment of processes. This is open ended and will cause cost increase and therefore ineffective use of funds.
Recommend changing wording to "The Government reserves the right to witness all Contractor Testing efforts to accomplish the SOW requirements and maintains the right to comment on processes."
Recommendation is not incorporated. The Government reserves the right to witness all Contractor efforts to accomplish the SOW requirements and maintains the right to comment on processes.
55 Statement of Work 2.2.1 (pg. 13)
A current up to date copy of all required documentation should be included with the Final RFP.
The contract required revision and date of release should be added to the table.
Yes final copies will be provided upon final solicitation release.
56 Statement of Work 3.0.2 (pg. 16) Please provide an Updated proposal DRAFT DD254 for security review? The final solicitation DD254 will be provided upon request at final solicitation release.
C-204-H002 Implementation of Enhanced Security Controls on Select
Defense Industrial Base Partner Networks (pg 45)
The prospective offeror can accept the deviation at 2024- O0013 for DFARS 252.204-7012. This entire clause C- 204-H002 is still in review.
The solicitation will have the latest clause versions.
58 H-209-H003 Required Disclosure of OCI Recommend to defer to DFARS clause 252.209-7009 Clause is required in all NAVSEA procurements.
59 H-216-H002 (pg. 85)
Paragraph E states " If, during the term hereof, the Contractor finds it necessary to accelerate the expenditure of direct labor to such an extent that the total man hours of effort specified in Section B would be used prior to the expiration of the term....an offer to undertake the acceleration at no increase in the estimated cost or fee; and an offer for the additional man-hours to cover the remainder of the term to include a proposed level of effort, cost breakdown, and proposed fee, for continuation of the work until expiration of the term. "
The prospective offeror will not accept doing additional work for free. Please delete wording.
This clause and language will remain.
60 H-216-H002 (pg. 85)
Paragraph F gives contractor 5 days ARO to acknowledge order should the KO direct the contractor to accelerate expenditure of direct labor prior to expiration of term. 5 days is tight turn around, recommend extending to 10 or 15 days.
This clause and language will remain.
61 H-216-H002 (pg. 86)
Paragraph H gives the Contractor 45 days after completion of work under each PoP to submit (1) total number of man-hours of direct labor expended separated by compensated and uncompensated (2) breakdown of compensated total in each direct labor classification and associated direct and indirect costs (3) breakdown of other costs incurred (4) contractor's estimate of the total allowable cost incurred under the contract period. 45 days is a tight turn, recommend extending to 60-90 days.
45 days is the standard.
62 Section I Clauses IBR (pg 89)
52.203-15 Whistleblower Protections under the ARRA - As the American Recovery and Reinvestment Act (ARRA) provided its appropriations back on February 17, 2009, recommend this clause should now be removed/deleted.
Concur with removal.
63 Section I Clauses IBR (pg 90)
52.211-11 Liquidated Damages Supplies, Services or R&D -
The prospective offeror can not accept this clause when associated with the contract types. Recommend this clause should now be removed/deleted.
Removed clause based on FAR 11.501 (a).
64 Section I Clauses IBR (pg 90) 52.227-1 Authorization and Consent: The prospective offeror recommend ALT 1 here.
Concur with addition of ALT 1. Prescription: Use the clause with its Alternate I in all R&D solicitations and contracts for which the primary purpose is R&D work
65 Section I Clauses IBR (pg 90)
52.227-3 Patent Indemnity Alt I - Recommend this clause should now be removed/deleted. Instead, the prospective offeror recommends include 52.227-1, Authorization and Consent, when used in accordance with the prescription clause 27.201-2(a)(1), and when the contract is above the simplified acquisition threshold. 52.227-1. 52.227-1 generally provides U.S. Government customers with what they need when data rights are properly negotiated and documented.
The clause will not be removed.
66 Section I Clauses IBR (pg 92)
252.204-7012 Safeguarding Covered Defense Information and Cyber Incident Reporting - the prospective offeror accepts the deviation 2024-O0013 which clarifies compliance to Rev 2 of the NIST22
The solicitation will have the latest clause versions.
67 Section I Clauses IBR (pg 92)
252.227-7026 & 252.227-7027 - Recommend this clause should now be removed/deleted.
If USG need it, industry will need to price in the risk for two years after pop.
These clauses will not be removed.
68 Section C paragraph 3.21.1 (pg 39)
Paragraph 3.21.1 of the SOW indicates the contractor will assist the Government in obtaining STEB ATOs at the SCI level. Paragraph 3.0.2 states the contractor must maintain a level of safeguarding for classified information, material, and data at the Secret level. Further, the SOW states the location of work is at the contractor facility. Please clarify if the contractor requires a SCIF to support the development, testing, documentation, etc. for SCI ATOs and if Cybersecurity personnel require SCI access.
A sensitive compartmented information facility (SCIF) is not required.
69 TRL Expectations and CLIN 0001 Provide better understanding of the TRL expectations for this procurement and the goals for CLIN 0001.
This is a performance specifications effort. The GFI provided is to be representative of a system at TRL 6/7. That will be the basis for the performance specifications used for the development efforts accomplished using CLIN 0001.
The expectation to achieve getting a Tempalt to be at a TRL 7/8. The version developed to be paired with TI-26 for permanent install will be at TRL 8/9. All the development efforts will be using CLIN 0001. Production efforts will use the appropriate CLIN depending on design maturity and overall risk.
Sheet1
File details come from the government source that posted it. Updated .