N00024-23-R-5203 Draft RFP Responses.pdf
PDF 162 KB Posted
- Attached to
- Surface Ship Undersea Warfare (USW) Combat System Production Federal contract opportunity
- Solicitation number
- N0002423R5202
About this file
This document contains responses to questions from potential offerors regarding solicitation number N0002423R5202 for the Surface Ship Undersea Warfare (USW) Combat System Production opportunity with the Department of the Navy Naval Sea Systems Command. The solicitation seeks an eight-year Indefinite Delivery/Indefinite Quantity contract for engineering, design, logistics, technical services, and production of the AN/SQQ-89 USW Combat System. Key details include that the contract will cover engineering design efforts, maintenance of technical data packages, production and testing of build-to-print and build-to-specification systems, adaptation for foreign military sales, and infrastructure as a service support. The contract will be awarded to a single offeror. No further drafts of the RFP will be released and the final RFP is expected to include full proposal instructions and evaluation criteria.
View the file
Other files for this federal contract opportunity
Show all 18
On GovTribe
Work with this file on GovTribe
- Download the original file
- Contacts named in this file
- Similar government files
- Ask GovTribe AI about this file
Text version
Question Number: Date Submitted:
Question Source: (GFI title, attachment # etc.)
Page number and paragraph header from source:
Question: Government Response:
1 6/15/2023 Draft RFP released 06/01/2023
Based on the released RFI and included TDP, it was expected that this RFP would be a Build to Print contract rather than a continuation of Engineering, Design, ILS, Technical Services, and Production Baselines (as with the current SQQ-89 contract). Is it the intent of the government to continue current efforts with this solicitation award and then follow with a Build to Print solicitation at the completion of the development of the updated AN/SQQ-89 system within the next one to two years?
No, the Government's intent is to continue with the Engineering, Design, ILS, Technical Services and Production efforts. The Government's intention is to have this contract cover the production of Build to Print and Build to Spec systems. The initial product baseline, HT0, can be characterized as Build to Print to the extent that there are Level 3 Technical Data Packages (TDPs) that represent the system. However, the TDP is expected to be impacted by obsolescence by the time production begins. Design and test services are required to resolve this problem to maintain a producible system. Additionally, a substantial revision to the TDP will be required during the ordering period of this contract to establish the HT1 functional baseline in support of changing shipboard requirements. Finally, this contract also covers the adaptation of the SQQ- 89 system in support of foreign military sales (FMS) cases. These are derivatives from the CRUDES and FFG configurations.
2 6/15/2023 Draft RFP released 06/01/2023 The draft RFP does not include Section L and Section M. Will there be an additional release of a draft RFP which contains these critical sections?
The next release of the RFP will be the final RFP which will include Sections L & M.
3 6/15/2023 Draft RFP released 06/01/2023
The draft RFP does not contain direction on Key Personnel or Personnel Requirements for the 1,648,054 Engineering and Technical Services hours or the 305,988 PMO hours. Will there be an additional release of a draft RFP which contains this information?
The next release of the RFP will be a formal release which will contain the Key Personnel and Personnel Resources information.
4 6/15/2023 Draft RFP released 06/01/2023 Page 14, Composite Rate Table
The CLIN structure is for a two year period, base and a single option. However, the Composite Rate Table indicates a four year period for CLINs 0002, 0008, 1002, and 1008. Request clarification if N0002423R5202 is a two or four year contract.
This is an eight year IDIQ contract. Base contract covers years 1-4, and the options cover the years 5-8. The composite rate table has been to reflect CLINs 1002 and 1008 to cover years 5-8.
5 6/15/2023 Draft RFP released 06/01/2024 Page 37, 3.2.4 Production
The referenced paragraph states, "The Contractor shall consider the delta between TI-20 and HT0 as representative of the delta between subsequent hardware baselines." Has a final version of the HT0 TDP been approved and will it be made available prior to release of the actual RFP?
The TDP provided with the draft RFP has been approved by the Government and is considered final. Any revisions will be a result of inspection and test findings.
6 6/15/2023 Draft RFP released 06/01/2025 Page 47, 3.4.12 Source Material For ILS Products
The referenced paragraph states, "The Contractor shall provide source material required to facilitate ILS product development," then goes on to list several categories of deliverables. Will the current version of these documents be provided to bidders prior to release of the actual RFP to allow a realistic assessment of the LOE required to fulfill the requirements?
There will not be another release of GFI prior to formal RFP release. As part of an updated GFI list, the Government will include a copy of an IETM and an RMA report.
7 6/15/2023 Draft RFP released 06/01/2026 CLIN 0004 and CLIN
Production CLINs are listed as Cost Plus Incentive Fee based on overruns and underruns. Question: Does the use of CPIF for production indicate that the current Technical Data Package is not complete? Can the Government detail the status and condition of the TDP, and its scope in relation to the total SQQ-89 system solicitation requirements (i.e., what remains developmental and what is
BTP).
The current TDP is determined to be final; however, there are continuing efforts such as Environmental Qualification Testing (EQT) and Physical Configuration Audit (PCA) that may drive minor design and production changes. The CPIF CLIN structure will reduce the vendor's cost risk exposure within the first production year to incorporate those changes.
Years two and after of production are FPIF to reflect the lower cost risk.
8 6/15/2023 Draft RFP Document Pg.1 Is it the Government’s intention to award the IDIQ to a single offeror? Yes, see Section M.
AN/SQQ-89 Surface Ship Combat System Question Submittal Form
9 6/15/2023 Section B - Supplies or Services and Prices Pg.1
Can the Government please share the intended or notional procurement schedule, such as:
- Date to release answers to questions
- Intention / date to release a second DRFP including Section J Attachments, Section L Instructions, and Section M Evaluation Criteria?
- Date to release Final RFP
- Deadline to submit proposals
- Contract award date
The relevant requested information is included in the final RFP.
10 6/15/2023 Section B - Supplies or Services and Prices
Pg.2, CLIN 0001 Pg.6, CLIN 1001
Note C states that 0001 and 1001 are not separately priced; should this say NSP? Yes. See the final RFP.
11 6/15/2023 Section B - Supplies or Services and Prices
Pg.3, CLIN 0004 Pg.5, CLIN 0009 Pg.7, CLIN 1004 Pg.9, CLIN 1009
Production CLINs do not include a quantity; is this an indication that the Government does not intend to request production pricing in the IDIQ proposal?
If production pricing will be included, can the Government please share details about how that will be requested?
The RFP will request a cost sample for evaluation purposes. Final pricing per system will be established via each individual Delivery Order. See the final RFP for instructions.
12 6/15/2023 Section B - Supplies or Services and Prices Pg.13 - Note A Should Item 0008 appear in note A? Yes. See the final RFP.
13 6/15/2023 Section C - Statement of Work Pg.18 - Paragraph 1.1 Description of the Effort
Recommended adding Frigate to description of effort. Concur. Future Surface Combatants are included in the SOW.
14 6/15/2023 Section C - Statement of Work
Pg.20 - Paragraph 2.1.2 Department of Defense
(DOD) and Department of Navy (DON) Regulations, Directives and Instructions
DoD Supplier's Passive RFID Information Guide (available at http://www.acq.osd.mil/log/rfid/index.html), Version 14 - Link results in error.
Recommend updating to Version 15 at https://www.acq.osd.mil/log/LOG/.AIT.html/DoD_Suppliers_Passive_RFID_ Info_Guide_v15update.pdf.
Update made; see the final RFP.
15 6/15/2023 Section C - Statement of Work Pg.23 - Paragraph 3.1 Program Management
There is no CLIN 0007 nor CLIN 1007 identified in Section B. Please provide clarification.
CLINs 0007 and 1007 are reserved. See the final RFP.
16 6/15/2023 Section C - Statement of Work Pg.23 - Paragraph 3.1.3
Contract Work Breakdown Structure
Section C 2.1.1 Military Standards lists MIL-STD-881E as an applicable document but does not list the version C noted here.
Updated to version F throughout. See the final RFP.
6/15/2023 Section C - Statement of Work
Pg.26 - Paragraph 3.1.9 Design Disclosure, Intellectual Property and Data Rights
There is no scope identified for software development. Recommend removing the following statement: The Contractor and its subcontractors are responsible to ensure that all software developed under this contract is properly marked with the delivered product.
In accordance with Section C 3.2.1.9, the contractor is responsible for software design, with regards to the Infrastructure as a Service components of the AN/SQQ-89 system. The word "developed" has been updated to "designed".
6/15/2023 Section C - Statement of Work Pg.31 - Paragraph 3.2 Engineering part (c) c)Trace the Ship, Warfare System, and operational requirements to components to ensure that test cases are maintained for each requirement.
Is this statement referring to hardware operational requirements vice system "shall" statements in the P-Spec? Can the Government please clarify if this is meant to focus on Hardware vs. System/Software?
This bullet has been updated to: "Conduct tests at the component and system level to verify functionality in support of system qualification and selloff"
6/15/2023 Section C - Statement of Work Pg.31 - Paragraph 3.2 Engineering part (e)
e) Modify and update the hardware IaaS configuration and elements allocated to the Contractor as required to support the tactical software baseline.
Recommend adding clarification for the hardware IAAS configuration.
Software configuration will be delivered from another contract as GFE.
The existing IaaS hardware/software configuration will be delivered as GFI with the RFP. For this contract, the contractor will be responsible for modifying, updating, and maintaining the IaaS configuration and elements required to support the tactical software baseline.
6/15/2023 Section C - Statement of Work
Pg.33 - Paragraph 3.2.1.4 Open Systems Architecture
Approach b)Modular, Open Design: The Contractor shall develop an architecture that is layered and modular and uses COTS/NDI hardware, Operating Systems (OS), and middleware that utilize non-proprietary or non-vendor-unique, key Application Programming Interfaces (APIs). The Contractor’s design approach must be applied to all subsystems and components. The Contractor shall provide the Government (and/or Government support contractors) electronic access to its integrated development environment throughout the term of the contract.
c)Modular Open Systems Approach (MOSA): The Contractor’s design approach shall produce a system that consists of hierarchical collections of hardware configuration items (e.g., components). These components must be of a size that supports competitive acquisition as well as reuse. The Contractor’s design approach shall emphasize the selection of components that are available commercially or within the DOD, to avoid the need to redevelop products that already exist and that can be re-used.
Recommend these two items be indented under part (b), "b) Infrastructure as a Service (IaaS).:"
The description for IaaS was left out in error. Please see Section C of the final RFP for description of Infrastructure as a Service in this section.
6/15/2023 Section C - Statement of Work Pg.35 - Paragraph 3.2.1.9 Infrastructure as a Service
Section 3.2.1.9 requires the Contractor to establish IaaS using COTS software. Is it the Government's intent that the Contractor provide the IaaS software infrastructure solution?
Recommend removal of CDRL A022 - Software Requirements Specification (SRS): Infrastructure as a Service Specification.
Yes. The contractor will be provided the current IaaS Configuration as GFI, but will be required to maintain, update, and expand that design, including the software infrastructure that rides on the IaaS Hardware.
Concur with the removal of CDRL A022 and the addition of CDRL A037 to cover the applicable scope.
6/15/2023 Section C - Statement of Work
Pg.37 - 3.2.3 System Integration
Section 3.2.3 requires the contractor to verify IaaS software. Earlier the SOW states there is no software development required as part of the draft RFP.
Verification of software requirements should be performed by the software developer.
Accordingly, recommend deletion of:
"a)The IaaS performs as defined in the IaaS Specifications b)The hardware baseline, inclusive of IaaS, supports the tactical software requirements
CDRL A028 – Management Plan: System Integration Plan CDRL A032 – Test Plans CDRL A034 –Test Procedures CDRL A035 T t/I ti R t"
This section has been revised; see Section C of the final RFP.
Section C 3.2.3 is specific to the IaaS virtualization software and this scope pertains only to the IaaS hardware/software to ensure it performs as defined in the IaaS Specification, and that the hardware baseline, inclusive of IaaS, supports that tactical software requirements. It does not cover the tactical software being developed, which is being developed under a separate Software Development Contract that is responsible for the development of Tactical Software and performing Software Verification Testing on that Tactical Software.
6/15/2023 Section C - Statement of Work
Pg.40 - Paragraph 3.3.1 Test and Evaluation
Program
"The TEPP shall also address recent advances in Automated Testing and Re-Test capabilities that can be accommodated during government conducted test and Certification and regression testing." This is a software task and recommended for deletion from the requirements.
This sentence has been updated to show that the TEPP must speak to the role that Automated Testing will have in conducting repeatable tests that allow for efficient testing and reduced human error. This applies for all testing to be conducted under this contract. See the final RFP.
Pg.41 - Paragraph 3.3.6 Testing and Inspections
Will portions of Section 3.3.6 of testing requirements specifically Production Verification Testing (PVT) be waived in the event a production infrastructure is in place?
Will a complete GFI/GFE list be provided for respective testing requirements and Build-In-Place philosophy?
Recommend modifying this paragraph to clarify:
Within the TEPP, the Contractor shall propose a product evaluation structure and sequence culminating in Government required Qualification and First Article Inspections (FAI) for any newly established production and test facility .
Will portions of Section 3.3.6 of testing requirements specifically Production Verification Testing (PVT) be waived in the event a production infrastructure is in place?
Not necessarily. PVT will be required to be held in accordance with the
EPQS.
Will a complete GFI/GFE list be provided for respective testing requirements and Build-In-Place philosophy?
The GFI list will contain a TDP for BIP and will contain parts lists for Test Cabinets and shipment material.
Recommend modifying this paragraph to clarify:
Within the TEPP, the Contractor shall propose a product evaluation structure and sequence culminating in Government required Qualification and First Article Inspections (FAI) for any newly established production and test facility.
Do not concur. PVT will be required to be held in accordance with the
EPQS.
6/15/2023 Section C - Statement of Work
Pg.44 - Paragraph 3.3.6.13 Reliability & Maintenance
Program Reviews
Recommend modifying paragraph 3.3.6.13 as follows:
The Contractor shall conduct, participate in, and submit source documentation to prepare for R&M program reviews for each individual system baseline conducted on a separate contract . The Contractor shall provide an agenda five calendar days in advance of each review to provide adequate coverage of topics and participant preparation.
CDRL A042 – Reliability and Maintainability (R&M) Program Plan
Paragraph has been modified. See the final RFP.
6/15/2023 Section C - Statement of Work
Pg.44- Paragraph 3.4.1 Performance Based
Logistics
Recommend modifying paragraph 3.4.1 as follows:
The Contractor shall perform provide the source material identified in section
3.4.4 to support conducting Performance Based Logistics (PBL) Business Case Analyses (BCA) under a separate contract as a part of the systems engineering process to ensure that PBL is a primary concern in system design changes. The study shall will need to consider the most cost effective balance of logistics support capabilities to maintain the required Operational Availability (Ao), or readiness, of the system over its expected life cycle. The BCA shall will need to address primary ILS elements, such as supply support, technical manuals, and training and alternatives for fulfilling associated requirements. The Contractor shall report progress and results of the study at applicable ILS IPT meetings and in a final report. The final report shall include the cost model used for the analysis.
CDRL A044 – Technical Report - Study/Services – Performance Based Logistics Business Case Analysis
Paragraph has been modified. See the final RFP.
Pg.45 - Paragraph 3.4.4 Supportability Analyses
Recommend modifying paragraph 3.4.4 as follows:
"The Contractor shall conduct supportability analyses as an integral part of the systems engineering process to ensure that supportability is a primary concern in system design and to demonstrate that the USW combat system is cost effectively supportable. The Contractor shall use MIL-HDBK-502 as guidance in the performance of supportability analyses. At a minimum, the supportability analyses must include Failure Modes, Effects and Criticality Analysis (FMECA) and Fault Tree Analysis (FTA). Additionally the contractor shall provide source documentation to support Level of Repair Analysis (LORA), and Reliability Centered Maintenance (RCM) Analysis performed on a separate contract . Functional Requirements Identification with appropriate feedback to the design process includes:
Testability and Diagnostic Procedure Development b)Maintainability Optimization to include accessibility, testing and change out of components
c) Assisting the Government or separate contract performer in identifying
Identification of Maintenance Assist Modules (MAMs), if required to support troubleshooting of the equipment
d) Source documentation to support identification of Unique Support and Test Equipment (S&TE) performed on a separate contract e)Reliability Block Diagram including component criticality and failure rates for input to the Readiness Based Sparing process."
Concur with the update.
6/15/2023 Section C - Statement of Work
Pg.45 - Paragraph 3.4.5 Support and Test
Equipment
Recommend modifying paragraph 3.4.5 as follows:
"The Contractor shall provide information source documentation required to identify and document Organization (O), Intermediate (I), and Depot (D) level support and test equipment under a separate contract for the USW combat systems, including GFP, based on the operation and maintenance requirements determined as part of the supportability analyses process. Support and test equipment identified shall will need to consider scheduled and unscheduled maintenance at each maintenance level. Maintenance includes periodic maintenance, equipment due-in for calibration, and other required maintenance as required by the Government. The Contractor shall minimize the number of different types of support equipment needed for the system and shall provide information necessary to identify the test equipment as General or Special Purpose Electronic Test Equipment (GPETE or SPETE) under a separate contract . The Contractor shall provide justification for use of SPETE.
Recommend modifying paragraph 3.4.5 as follows:
"The Contractor shall provide the Government information source documentation that allows for the identification and documention of Organization (O), Intermediate (I), and Depot (D) level support and test equipment under a separate contract for the USW combat systems, including GFP, based on the operation and maintenance requirements determined as part of the Government's supportability analyses process.
Support and test equipment identified shall will need to consider scheduled and unscheduled maintenance at each maintenance level.
Maintenance includes periodic maintenance, equipment due-in for calibration, and other required maintenance as required by the Government. The Contractor shall minimize the number of different types of support equipment needed for the system and shall provide information necessary for the Government to identify the test equipment as General or Special Purpose Electronic Test Equipment (GPETE or SPETE) under a separate contract . The Contractor shall provide justification for use of SPETE.
Pg.47 - Paragraph 3.4.11
Provisioning Data
Recommend modifying paragraph 3.4.11 as follows:
"The Contractor shall generate data required to support the ICAPS format that includes data elements provided via the Hardware IPT and, as available, OEM source data, drawings, technical information, and photographs for maintenance planning and Provisioning Parts List (PPL). The Contractor shall participate in provisioning conferences. "
Recommend removal of the following paragraph:
"The Contractor shall provide a complete list of end items being delivered. The Contractor shall interface with Navy Supply System and the Program Office for support date planning and provisioning conferences. If any changes are made to the equipment after the provisioning data is submitted and approved by the Government, the Contractor shall submit a Specification Change Notice to the Government."
Paragraph has been modified. See the final RFP.
6/15/2023
Section E - Inspection and Acceptance Terms
Pg.80 - Section E Inspection and Acceptance
Terms
Recommend all "INSPECT AT" and "ACCEPTED AT" be changed to Origin. Section E has been updated as shown in the final RFP.
31 6/15/2023 Section I - Contract Clauses Pg.104 - Section I Recommend deletion of DFARs Clauses 252.246-7001 'Warranty of Data' and 252.246-7001 ALT I 'Warranty of Data - Alternate I'
Clause is applicable to this effort. The Government does not concur with removal.
File details come from the government source that posted it. Updated .