J-S2 BQ Round 2 dtd 15 April 2022.xlsx
XLSX spreadsheet 30 KB Posted
- Attached to
- AN/SRQ-4 Radio Terminal Set (Ku Band)
- Solicitation number
- N00024-22-R-5206
About this file
This solicitation requests proposals for the production of a modernized AN/SRQ-4 Radio Terminal Set (Ku Band) system. The Navy seeks to eliminate obsolete analog interfaces, modernize the system to meet cybersecurity requirements for Aegis Baseline 10 and beyond, and maximize future interoperability by supporting Band Efficient - Common Data Link and Crypto Core Modernization. A five-year contract will be awarded to provide development of production units, associated engineering services, and incidental materials and other direct costs. Offerors must submit all questions by March 29, 2022 to allow the Navy to prepare responses prior to the proposal due date. Proposals are due in response to solicitation number N00024-22-R-5206 issued by the Naval Sea Systems Command on behalf of the Program Executive Office Integrated Warfare Systems 5.0.
View the file
Other files
| File | Type | Posted |
|---|---|---|
| J-S2 BQ Round 4 dtd 27 April 2022.xlsx | XLSX spreadsheet | |
| J-S8 Contractor Award Information.docx | DOCX document | |
| N0002422R5206 Amendment 0003.pdf | ||
| J-S2 BQ Round 3 dtd 25 April 2022.xlsx | XLSX spreadsheet | |
| N0002422R5206 Amendment 0002.pdf | ||
| Exhibit A - CDRLs (signed).pdf | ||
| J-S2 BQ Round 1.pdf | ||
| N0002422R5206 Amendment 0001.pdf | ||
| J-S2 Bidders Question Submittal Form.xlsx | XLSX spreadsheet | |
| J-S1 Contract-wide Staffing Plan.xlsx | XLSX spreadsheet | |
| Attachment J-6 CDRL Cross Reference Matrix.xlsx | XLSX spreadsheet | |
| N0002422R5206 SRQ-4 RFP 031522.pdf | ||
| Attachment J-1 DD254.pdf | ||
| Attachment J-2 GFP List.xlsx | XLSX spreadsheet | |
| Attachment J-3 GFI List.pdf |
Show all 15
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
Sheet1
| Question Number: | Question Source: (RFP, attachment #, GFI title, etc.) | Page number and paragraph header from source: | Question: | RFP Update? | Answer |
| 1 | RFP | 1 | Line 9 indicates the RFP is due 29 March 2022. SAM.gov states 15 April 2022. We assume the latter is correct, but can the government clarify? | Yes | 29 April 2022 is the updated proposal submission deadline. See Amendment 0001. |
| 2 | RFP | 80 | CLIN 1002AA is listed as ADC. Should this be AOE? | Yes | Yes. CLIN 1002AA should be AOE. See Amendment 0001 |
| 3 | RFP | 123 (Section 3.2.1.1.1) | The RFP states that the Staffing plan "shall include all labor category personnel (by name - both prime and subcontractors) known at the time of proposal submission." Is the subcontractor personnel staffing information requested in the management volume required for "Major Subcontractors" only? | No | Yes, Major Subcontractors only. |
| 4 | RFP Section B | Section B Notes, page 29, Note F | Section B specifying CLIN details notes quantity of 13 for CLIN 0001, 1001, 2001, 3001, and 4001, but Note F describes a stated maximum quantity of three for 0001 and 1001, and maximum quantity of 11 for 2001 and 3001. Please clarify the quantities to populate in Note F. | Yes | Note F has been revised. See Amendment 0001. |
| 5 | RFP Section B | Section B Notes, page 30, Note G | Section B specifying CLIN details notes quantity of 13 for CLIN 1006, 2006, 3006, and 4006, but Note G describes a stated maximum quantity of give all stated CLINs. Please clarify the quantities to populate in Note G. | Yes | Note G has been revised. See Amendment 0001. |
| 6 | RFP | Page 106 | CLIN 0006 is stated as an option, but there is no timeframe given for the latest option exercise date after date of contract (ADC). Please clarify the ADC timeframe for CLIN 0006 | Yes | 18 months After Date of Contract. See Amendment 0001. |
| 7 | RFP | Page 79 | Page 79 references that CLIN 0002AA has a ceiling quantity of 12,247 hours for a 24 month POP, consistent with the hours in CLIN 1002AA which is for 12 months. Please confirm the ceiling hours provided in CLIN 0002AA | Yes | CLIN 0002AA has a ceiling quantity of 12,247 hours for a 12 month period of performance. See Amendment 0001. |
| 8 | RFP | Page 117 | The RFP consistently uses "subcontractor" and "Subcontractor" when delineating requirements for a response, but the only clarifications made are regarding "Major subcontractors" and "minor subcontractors." When "subcontractor" is used by itself without adjective, are we to assume that is only referring to "Major subcontractors" or all subcontractors regardless of major/minor classification? | No | When "subcontractor" is used by itself it refers to all subcontractors regardless of major/minor classification. |
| 9 | RFP | Page 117, Page 131 | Please clarify the definition of "minor subcontractor." Page 117 defines a "minor subcontractor" as all subcontractors that do not meet the definition of major subcontractor. Please confirm that all subcontractors, including FFP subcontractors, would be required to provide hours and cost detail sufficient to populate the Prime Offeror's Total Cost/Price Buildup Spreadsheet as referenced on Page 131, including detail by individual to populate the Prime Offeror's Staffing Plan. Is it also the expectation that minor subcontractor hours count against the ceiling for CLIN's X002 and X008? | No | For the purposes of this solicitation, major subcontractors are defined as any cost-reimbursement subcontractor |
proposed to perform 10% or more of the cumulative hours under CLINs X002 and X008. Subcontractors that do not meet this definition are not considered a major subcontractor. Minor subcontractor hours count against the ceiling for CLINs X002 and X008. Please refer to H-216-H002 LEVEL OF EFFORT--ALTERNATE I (NAVSEA) (OCT 2018); Section L: 3.3.4; and Section M: 2.4.1.5 for further information.
10 RFP Page 107 Please provide latest copies of the J-5 RTS Specification, J-4 TDP, and SCG #02-235.4 MH-60R MMH Security Classification Guide No Please refer to Section 1.3 - Availability of Attachments and GFI and follow the instructions to request attachments and GFI.
No SCG is required to be sent.
| 11 | RFP | Page 107 | Is J-S6 supposed to be a contractor format or is there a template for inputs to assist in calculating the TEP? The attachment referenced on the RFP is not included on the SAM.gov listing. | Yes | Attachment J-S6 to be contractor format. See Amendment 0001. |
| 12 | Attachment J-6 | Attachment J-6 does not include expected formats/DID information. Will the government be providing an Exhibit A DD-1423 or is contractor format acceptable? | Yes | The Government will provide Exhibit A – Contract Data Requirements List (CDRL) DD Form 1423. See Amendment 0002. | |
| 13 | RFP Section C | Page 50 | Are MAM and OBRP kits required as deliverable assets for each RTS system delivered? i.e. each RTS delivered under CLIN X001 and X006 would include both a MAM and OBRP kit. | Yes | One MAM kit is required for each RTS system delivered on CLINs X001 and X006, MAM kits are ordered and delivered on CLINs X001 and X006. One OBRP kit is required for each RTS system delivered on CLINs X001 and X006, ORBPS are ordered and delivered on CLIN X005. See Amendment 0002. |
| 14 | RFP Section C | Page 50 | Are MAM and OBRP kits required with the First Article Unit (CLIN 0007) | No | MAM and OBRP kits are not required with CLIN 0007. |
| 15 | 03_Attachment J-5 SRQ-4 Specification.pdf | Paragraph 3.1 | Are OR-209 rack, shock isolators, and ship-run cabling to be provided by a ship installation activity, or is this equipment to be provided by offeror? | Yes | The rack and shock isolators are to be provided by the offeror. Ship-run cabling will be provided by the ship yard installing the system. See Amendment 0002. |
| 16 | RFP Section C SOW | SOW Paragraphs 5.1.2-5.1.4, 5.1.6 | The SOW currently states that ESS, acceptance tests, serializing hardware and nomenclature, and the As Built Configuration List are all SEPM expenses. Is that the intent? Recommend these costs be within X001, X006, and 0007 as they are a part of the process to manufacture, test, and deliver the AN/SRQ-4 (Ku) RTS System | Yes | Concur with SOW Paragraphs 5.1.2, 5.1.3, 5.1.4, and 5.1.6 being part of X001, X006, and 0007. See Amendment 0002. |
| 17 | RFP | Section 3.2.1 | Bullet 7: The Offeror shall discuss how its production approach supports successful execution of the requirements in SRQ-4 SOW Section D paragraph 3.2 and its subparagraphs. - Paragraph 3.2 is about the ILS (covered at in Tech Vol), is this in error? | Yes | This is an error. It is should say paragraph 5.0 and its subparagraphs. See Amendment 0002. |
| 18 | RFP | Section 3.2.1.3 | Bullet 5: The Offeror shall describe the availability of the facilities to conduct testing of RF equipment to satisfy the requirements of SRQ-4 SOW Section C paragraph 6.0. Paragraph 6.0 is about Security, is this mapped incorrectly? | Yes | This is an error. It is should say paragraph 4.0 and 5.0 and their subparagraphs. See Amendment 0002. |
| 19 | 03_Attachment J-5 SRQ-4 Specification.pdf | 3.2.1.19.19, 3.2.1.19.19.1, 3.6.1.2.12.1, 3.6.1.5 | Several "Error! Reference source not found" comments exist in the Word to PDF conversion of the spec. Will the government be providing a Word or updated version with these corrected? | No | Will provide an updated version fixing the errors. See version C.1 of the Spec. See Amendment 0002. |
| 20 | 03_Attachment J-5 SRQ-4 Specification.pdf | 3.2.1.19.14 | Section indicates interface specifics for Acoustic Channels. This is in disagreement with figures SRQ-49 and SRQ-51. Should this analog interface be eliminated? | No | No, this interface is not eliminated and is still present. |
| 21 | ICD 45105 | ICD 45105-0002 | ICD appears to be in conflict with the PIDS Diagrams SRQ-49 and SRQ-51 and PIDS content, i.e. Legacy Analog Interfaces are represented in the ICD, but most references to these interfaces have been eliminated from the PIDS. Is the ICD in error? | No | The ICD is not in error. The ICD is the current configuration for reference. The PIDS will take preference over the ICDs. |
| 22 | ICD 45105 | ICD 45105-0002, -0008 | ICD includes Control Monitor, but all references to this device have been eliminated in the PIDS. Is the ICD in error? | No | The ICD is not in error. The ICD is the current configuration for reference. The PIDS will take preference over the ICDs. |
| 23 | 03_Attachment J-5 SRQ-4 Specification.pdf | 3.2.4.2.2, 3.7.3 | Sections refer to Sensor modes 1, 2, and 3. Is this in error? (references to ASW, ASST, and Mixed modes have been eliminated) | No | See version C.1 of the Spec. |
| 24 | 03_Attachment J-5 SRQ-4 Specification.pdf | 3.6.1.2 | Is reference to WRN-6 RS-422 interface in error, or should the system still support WRN-6? | No | See version C.1 of the Spec. |
| 25 | 03_Attachment J-5 SRQ-4 Specification.pdf | 3.6.1.2.11 | Section includes specific interface information for Acoustic Analog signals. Is this in error? | No | See version C.1 of the Spec. |
| 26 | 03_Attachment J-5 SRQ-4 Specification.pdf | 3.6.1.2.12.1 | Section includes specific ISAR Radar Video output information. Is this in error? | No | See version C.1 of the Spec. |
| 27 | 03_Attachment J-5 SRQ-4 Specification.pdf | 3.6.1.2.12.2-4 | Sections include specific analog Radar interface information. Is this in error? | No | See version C.1 of the Spec. |
| 28 | ICD 45105-0003 | 26 | Several Cables in the Cable running sheets are indicated as "Optional". For example, R-SI(361). Are any of the optional cables required? | No | The ICD is not in error. The ICD is the current configuration for reference. The PIDS will take preference over the ICDs. |
| 29 | 03_Attachment J-5 SRQ-4 Specification.pdf | 3.2.1.19.18 | Narrowband CDL Red Egress Panel interface is not reflected in figures SRQ-49 and SRQ-51. Is this interface required? | No | The Narrowband CDL Red Egress Panel interface is not required. The solicitation will be amended to delete this requirement. See version C.1 of the Spec. |
| 30 | ICD 45105-0003 | Sheet 3, note 12 |
Sheet 3, page 29-30
| Sheet 3, page 32-34 | ICD includes references to Fiber Optic interfaces, but there are no indications of such interfaces in the 03_Attachment J-5 SRQ-4 Specification. Are fiber optic interfaces required? | No | The requirement for fiber optic interfaces is covered under requirement SRQ-1039. | |||
| 31 | RFP | page 95 | Given the current environment with work at home situations due to COVID, is the government’s intent to enforce the limitation in section (i) of clause H-216-H002 with respect to only 10% of hours worked at an alternative worksite? | No | Aside from classified work, manufacturing, and testing related efforts that require a specific facility, we don’t see any issue with giving relief to the 10%. | |
| 32 | RFP | page 125 | Please confirm that clause H-216-H002 only applies to LOE CLINs X002 and X008. If so, how does the average rate of 341 hours per week called out in section (d) relate to the labor mix outlined in section 3.2.1.1.2 of Section L (p. 125). The required number of hours in Section L would result in a greater spend rate per week than 341 hours per week on CLINs 0002 and 0008. For the intended purposes of this clause, will the first year (CLIN 0008) hours be treated as an acceleration to accomplish the related development and test scope? | No | Clause H-216-H002 only applies to LOE CLINs X002 and X008. The average rate of approximately 341 hours per week can be calculated by taking the sum of all LOE hours (88,641 hours) and dividing by 260 weeks (52 weeks * 5 years). The rate per week is an average and can be accelerated as needed. | |
| 33 | RFP | 3.2.1.2, page 127 | Does the requirement of the IMS include details on all CLINS or just the CPFF CLINs? Is it restricted to CLINs exercised ADC? Given the variable nature of the production FFP CLINS, if required, is there an assumed "most likely" award date/quantity to use for the baseline schedule? | No | All CLINs are to be included in the IMS. Minumin quanity is 10. Notional contract award date of September 30, 2022. | |
| 34 | PID Spec 20080613SRQ REV C | Pg 12; 1.0 Scope | A general document question in response to "The modification eliminates legacy analog interfaces, replaces the obsolete KGV-135A…" etc. Many paragraphs were found to what appear to be describing Legacy analog interfaces. | |||
| Can we assume that references to legacy analog interfaces are no longer valid? | No | All legacy analog interfaces are removed except for the voice requirement. See version C.1 of the Spec. | ||||
| 35 | PID Spec 20080613SRQ REV C | Pg 15; 2.1.2 - Other Documents | Is PMA299-07000 the same as SAU7000 messages? | No | Yes, the PMA299-07000 is the same as SAU7000. | |
| 36 | PID Spec 20080613SRQ REV C | Pg 16; 3.0 Requirements: | ||||
| The AN/SRQ-4(Ku) shall transfer the various types of data uplink and downlink simultaneously within the distortion limits specified herein, and to the ranges, operational conditions, environments, accuracies, and data formats required while installed in ship platforms. (SRQ-2009) | General Requirements question: If data is passed from aircraft to ship using Ethernet PMA299-07000 messages for sensor data as they do on CVN, how does this impact the data flow? | No | Please refer to the SAU7000 IDS. | |||
| 37 | PID Spec 20080613SRQ REV C | Pg 20; 3.2.1.1.1 Waveform Definition | General Waveform question: All these Waveform Definitions are all covered in the CDL waveform spec up to at least Rev F. These are all verified by JTIC. |
| Is JTIC certification sufficient to meet these requirements? | No | JITC certification alone is not sufficient. JITC certification is in addition to the CDL requirements. | |
| 38 | PID Spec 20080613SRQ REV C | Pg 30; 3.2.1.9.4 (subpara g) SRQ-4 Ku Directional Antenna. |
g. Shall be 40.5 dBi minimum at receive frequencies Pg 26; 3.2.1.8 Range It is stated here that the directional antenna Shall be 40.5 dBi minimum. But on page 26, 3.2.1.8 Range, it shows a requirement for 100nm "The DTS shall perform beyond 100 nm up to its 0 dB fade margin point ".
| Which requirement takes precedence? Antenna dB performance, or actual range performance? | No | The 100 nm range takes precedence. The antenna gain value is determined by the link margins at 100 nm for all waveforms based on transmitter power and receiver sensitivity. | ||||
| 39 | PID Spec 20080613SRQ REV C | Pg 32; 3.2.1.10.1.3 Video Data | ||||
| Video data is now via Ethernet IP packets via multicast video. Is the requirement for this system to decode the video data, or is that function performed at the shipboard system level? | No | The SRQ-4 acts as a pass through system and the shipboard system will decode the MPEG 2 data. Please refer to the PMA299-07000 IDS. See version C.1 of the Spec. | ||||
| 40 | PID Spec 20080613SRQ REV C | Pg 32; 3.2.1.10.1.1 and 10.1.2 Radar and ISAR data. | ||||
| Both paragraphs state system shall be capable with receiving and outputting data in accordance to PMA299-07000. Does this require legacy analog interface support? | No | No, the only analog interface is voice. | ||||
| 41 | PID Spec 20080613SRQ REV C | Pg 35; 3.2.1.19.4.2 GPNTS Attitude Inputs. | If a technical solution is available which doesn't require the GPNTS, can those interfaces be removed from the architecture? | Yes | A GPNTS-free solution is highly discouraged due to likely inability to maintain and establish link as well as meeting other requirements. A GPNTS-free solution can be proposed but could increase risks to maintaining and establishing link. See amendment 0002. | |
| 42 | PID Spec 20080613SRQ REV C | pg 38; 3.2.1.19.14 Outputs to ISSS | Is this an analog/legacy requirement now supported by Ethernet connections? | No | This section is an error and will be removed from the specifications. See version C.1 of the Spec. | |
| 43 | PID Spec 20080613SRQ REV C | Pg 59; 3.6.1 Receiver-Transmitter (RT) Processor Group | Is the equipment to follow this exact description, or can a different rack design be allowed? | No | A different rack is allowed as long as it meets remaining SRQ-4 specifications, meets the ICD envelope and all space, weight, power, cooling, and shock requirements. | |
| 44 | PID Spec 20080613SRQ REV C | Pg 60; 3.6.1.2 Multiplexer Assy | Is the RS-422 interface still a requirement to the WRN-6? Or is that Ethernet now via GPNTS? | No | This section is an error and will be removed from the specifications. See version C.1 of the Spec. | |
| 45 | PID Spec 20080613SRQ REV C | Pg 61; 3.6.1.2.11 Acoustic Channels. | Is this analog interface a requirement or is it included in the Ethernet traffic? | No | This section is an error and will be removed from the specifications. See version C.1 of the Spec. | |
| 46 | PID Spec 20080613SRQ REV C | Pg 62; 3.6.1.2.12 Radar Decoding and Reconstruction (and subparagraphs) | Is this analog interface a requirement or is it included in the Ethernet traffic? | No | This section is an error and will be removed from the specifications. See version C.1 of the Spec. | |
| 47 | PID Spec 20080613SRQ REV C | Pg 63; 3.6.2.6 Waveguide Switch | Would an alternative option for RF switching be acceptable instead of a waveguide switch? | No | An alternative option for RF switching is allowed as long as it meets remaining SRQ-4 specifications, meets the Interface Control Documents envelope and all space, weight, power, cooling, and shock requirements. | |
| 48 | PID Spec 20080613SRQ REV C | General question not specific to spec | Is the SRQ-4 mission controller software GFE or should it be provided as part of the system solution? | No | The SRQ-4 will be controlled by the AEGIS Display System terminal. This software is currently under development. | |
| 49 | 03_Attachment J-5 SRQ-4 Specification.pdf | 3.1.3 a, page 8 | Reference made to Audio System: AN/USQ-155(V). Please provide ICD for this new system. | No | We don’t have this Interface Control Document available at this time. However, it is not required as long as all audio requirements on the spec are met. | |
| 50 | 03_Attachment J-5 SRQ-4 Specification.pdf | 3.1.3 h, page 8 | Spec makes reference to "Combat Systems cybersecurity management service. Will the Navy provide this application/software to enable the offeror to perform integration testing? | No | We can't provide this software at this time. The software is currently in development. | |
| 51 | RFP, Amendment 1 | page 27 | Are hard copies of the Attachment J-S1 - Contract Wide Staffing Plan and Attachment J-S6 Total Cost/Price Build Up Spreadsheet submittals required or just soft copies of the Excel files? | Yes | Soft copies/electronic copies of the Staffing Plan and Cost/Price Build Up Spreadsheet is sufficient. See amendment 0002. | |
| 52 | RFP, Amendment 1 | page 27 | The RFP does not appear to ask/require BOE data as part of the submittal. Is this correct? | Yes | BOE is required. The RFP Section 3.3.4.1 has been updated. See amendment 0002. | |
| 53 | RFP | - Section B |
- B-216-H006 Fee Table
- Delivery Information
| - 3.2.1.1.2 | The RFP references hours for the X008 CLIN's, in particular CLIN 1008 and 2008 in the areas cited. Within Section B, Delivery Information, and 3.2.1.1.2, the hours for CLIN 1008 are 1,000 and 2008 and 2,036, but in B-216-H006 those values are flipped. Please clarify the intended ceiling hours for 1008 and 2008. | Yes | The hours in Section B, Delivery Information, and 3.2.1.1.2 are correct. The RFP will be updated to reflect this in B-216-H006. See amendment 0002. |
| 54 | RFP | - Page 48 |
- Section C
| - 4.1.56 (FAIT) | Is the intent to have activities under 4.1.56 applied to CLIN 0007, rather than CLIN X008? | No | No, the intent is for the acitviites in 4.1.56 to be covered under X008. | |||
| 55 | RFP, Amendment 1 | Page 8, Section 3.1.9 | Will tailoring of EIA-649-1 be allowed/provided? | No | Yes, tailoring of EIA-649-1 will be allowed with Government concurrence. |
&"Times New Roman,Regular"&10N00024-22-R-5206 &"Times New Roman,Regular"&10Bidder's Question Submittal Form &"Times New Roman,Regular"&10Attachment J-S2
&"Times New Roman,Regular"&10&P of &N
Sheet2
Sheet3
File details come from the government source that posted it. Updated .