HFRS_Consolidated-Vendor-Questions_06-04-21_v8.pdf

Vendor Terms and Conditions Questions

RFP 70Z04421R21000900

Question # Reference Document

Section / Paragraph

Reference Question Response / Adjudication

C1 Combined Synopsis/

Solicitation Page 4, section xv Offer Due Date/Time: 14 June 2021 / 11:00AM (Eastern)

Requests a 2 week extension to the proposal due date to allow for time to evaluate and potentially incorporate feedback from the Government into our response.

2 week extension granted - new proposal due date Tue, June 29, 2021 at 1100 eastern time.

RFP revision completed.

C2 HFRS Price Schedule Kit Pricing Exhibits n/a

Given that each offeror's potential solution will include unique configurations to meet threshold requirements, can offerors add/delete individual part items from the HFRS Price Schedule ' Kit Pricing Exhibit' tab to accurately represent the proposed bill of material (BOM)?

Yes, the intention is that the vendor will modify the complete list of all potential components on the "Parts List" tab (which will auto-populate to the individual kit tabs), and then modify the quantity for each component within the individual kit tabs based upon the offeror's proposed solution, with any un-needed components for a particular cutter class marked with a quantity of zero (0).

No RFP revisions required.

C3 HFRS Price Schedule Kit Pricing Exhibit Tab

"Kit Pricing Exhibit" tab, Note 3 states that Total Evaluated Price will be calculated with an algorithm that factors in 'expected ordering by FY'.

Does the Government intend to provide a notional ordering schedule to allow offerors to price according to projected demand?

The Government does not intend to provide a notional ordering schedule.

No RFP revisions required.

C4 Combined Synopsis/

Solicitation Section 1.6

“The required time of delivery for all delivery orders shall be within 90 calendar days after receipt of a delivery order…”

Lead times of 90 days ARO for HF radio equipment is shorter than common industry standard. Achieving those lead times would impact pricing. On similar prior IDIQ contracts, a lead time of 210 days ARO was acceptable;

would 210 days be acceptable for this proposal?

RFP delivery requirement changed to required/threshold requirement of 210 days and desired/objective requirement of 90 days.

RFP revision completed.

C5 Combined Synopsis/

Solicitation

(2) Offer Content -

Volume 2 Past Performance

(Page 25)

“Page Limit: Volume 2 and shall be limited to four (4) pages. A “page” is one single sided 8.5” x 11” sheet.”

Assuming the page limit includes front matter, will the USCG please consider excluding front matter (cover sheet, TOC, etc.) from the page limit for this section?

The 4 page limit for volume 2 is firm and all-inclusive (includes cover sheet and TOC, if the offeror chooses to include them, however a separate cover page and TOC are not strictly required … "front matter" for volume 2 is anticipated to be minimal).

No RFP revisions required.

C6 Combined Synopsis/

Solicitation HSAR Clauses n/a

Please confirm per HSAR 3052.219-72, Evaluation of Prime Contractor Participation in the DHS Mentor Protégé Program (JUN 2006) and HSAR 3052.219-71, DHS Mentor Protégé Program (JUN 2006), as prescribed in HSAR 48 CFR 3019.708–70(c), Evaluation of Prime Contractor Participation in the DHS Mentor-Protégé Program (JUN 2006) will apply whereas, the KO may, at their discretion, give credit for approvals that occur after initial evaluation of proposals, but before final evaluation.

Section 5 Evaluation of the HFRS Solicitation is void of this language or provision.

Both HSAR 3052.219-72, Evaluation of Prime Contractor Participation in the DHS Mentor Protégé Program (JUN 2006) and HSAR 3052.219-71, DHS Mentor Protégé Program (JUN 2006) are already incorporated by reference in the originally-release RFP (page 20).

An evaluation factor has been added to the RFP; please see Amendment 00001.

RFP revision completed.

C7 Combined Synopsis/

Solicitation HSAR Clauses n/a

If the USCG decides not to support the DHS Mentor Protégé Program in the HFRS Solicitation, please explain why.

An evaluation factor has been added to the RFP; please see Amendment 00001.

RFP revision completed.

C8 Combined Synopsis/

Solicitation General n/a

Will the USCG recognize and support the Department of Veterans Affairs Center for Verification & Evaluation program for verified SDVOSB concerns in contract evaluation?

Final CG-913 Answer :

This question appears to refer to the Veterans First Contracting Program.

This program and procurement authority is unique to the Department of Veterans Affairs. The U.S. Coast Guard falls under the Department of Homeland Security. See the FAQs here: Vets First Contracting Program FAQs - Office of Small & Disadvantaged Business Utilization. Note that this particular RFP is unrestricted.

No RFP revisions required.

C9 Combined Synopsis/

Solicitation General n/a

If the USCG decides not to support the Department of Veterans Affairs Center for Verification & Evaluation program for verified SDVOSB concerns in this solicitation, please explain why?

Final CG-913 Answer :

See answer C8 above.

No RFP revisions required.

C10 Combined Synopsis/

Solicitation General n/a

Does the USCG have congressionally approved appropriations for FY21 Re HFRS Combined Synopsis/Solicitation 70Z04421R21000900? If so, how much?

An annual appropriation bill for USCG has not yet been approved for FY21.

No RFP revisions required.

C11 Combined Synopsis/

Solicitation General n/a

What Major Systems Acquisition level is the HFRS Combined Synopsis/Solicitation 70Z04421R21000900 defined as Level 1, Level 2, or Level 3?

HFRS is not classified as a Major Systems Acquisition.

No RFP revisions required.

C12 Combined Synopsis/

Solicitation General n/a

Will this HFRS contract be awarded in FY21? If not, are these appropriations multi-year?

The goal is award in FY21. HFRS does not have a multi-year appropriation.

No RFP revisions required.

C13 Combined Synopsis/

Solicitation General n/a

If multi-year appropriations, please list the amount of approved funding per year.

HFRS does not have a multi-year appropriation.

No RFP revisions required.

C14 Combined Synopsis/

Solicitation General n/a Are hyperlinks authorized?

No, hyperlinks are not permitted within the proposal due to the enforcement of page limits.

No RFP revisions required.

C15 Combined Synopsis/

Solicitation General n/a

Past Performance Questionnaire (PPQ) Section A:

Instructions states: The completed PPQ is due on or before 1 March 2021 11:00 AM Eastern, unless the due date is extended via a Solicitation Amendment. Please confirm that the PPQ is expected with the submission of the proposal.

This is an error and will be corrected … PPQs are due the same date that proposals are due.

PPQ attachment correction completed.

C16 Combined Synopsis/

Solicitation General n/a

Please explain why the USCG has not utilized the required DHS Strategic Sourcing Vehicle, TacCom II, Technical Category 1 Equipment, Subcategory High-Frequency (including end-user equipment, associated accessories, and infrastructure to support) for the HFRS solicitation. We understand it is mandatory for use per DHS Directive 060- 01, Development & Use of Strategic Sourcing Contracting Vehicles. Please justify, explain, or provide the Approving Authority's release if an approved waiver has been granted.

use this below...I had a conference call with Telephonics last week and gave this exact answer:

A Strategic Source Waiver was approved by DHS to compete this requirement Open Market due to TACCOM II having insuffiecient remaining ordering period. The HFRS contract will have a 10 year ordering period, and TACCOM II cannot accomodate this duration.

No RFP revisions required.

C17 Combined Synopsis/

Solicitation General n/a

Will the USCG extend the due date for submissions to 28 June 2021 to allow ample time to receive the USCG's responses to all questions submitted and adjust all offerors' proposals accordingly?

See answer to C1 above.

RFP revision completed.

C18 Combined Synopsis/

Solicitation General n/a

We have noticed the absence of the Polar Security Cutter, the Offshore Patrol Cutter, and Waterways Commerce Cutter HFRS requirements. Was it by design or an oversight, or will these cutters be added later in the contract? If added now, pricing can be advantageous as the USCG plans to acquire 16 river buoy tenders, 11 inland construction tenders, and three inland buoy tenders, as well as two or three polar security cutters and 25 OPCs.

The cutter platforms included in this RFP are those currently listed in the RFP and there are not current plans to include any additional cutter platforms.

No RFP revisions required.

C19 Price Schedule General n/a How does the government intend to use the percentage discount factor included in column E of the Price Schedule, Attachment 1?

Per block A72 of the price schedule, the percentage discount off the commercial price establishes the discount factor that will be applicable to pricing for any replacement parts required due to obsolescence during the 10-year ordering period of the IDIQ contract. The discount factor will be applied to the commercial list price of any proposed replacement part in the first ordering year that it becomes necessary due to obsolescence of the originally-proposed part.

No RFP revisions required.

Vendor Technical Questions

Question # Reference Document

Section / Paragraph

Reference Question Response / Adjudication

T1 HFRS Specification Requirement

4.2.1 Requirement 4.2.1

Regarding Requirement 4.2.1, strict adherence to MIL-STD- 188-141D Appendix F of HFRS on all cutter classes will significantly increase the rack space and weight required to satisfy the requirement than is allocated by the HFRS specification and may be a disproportionately large cost driver with respect to the radios. Would the Government consider making this requirement an objective vs.

threshold so that radio co-site performance and mitigation techniques can be evaluated and applied as needed.

Requirement 4.2.1 remains a threshold requirement of the HFRS system.

No Spec revision required.

T2 HFRS Specification Requirements

4.4.10 through

4.4.10.2

Requirements 4.4.10 through 4.4.10.2

Regarding requirements 4.4.10 through 4.4.10.2, the requirement for using a serial interface between the RCU(s) and radio(s) is vendor specific; may suppliers propose an Ethernet-based alternative? This would not eliminate the requirement to provide a serial interface for remote control from the CMS.

Yes, an ethernet-based solution is acceptable.

No Spec revision required.

T3 HFRS Specification Requirement

4.1.28.3 Configuration 3 (WMEC 270')

Regarding Requirement 4.1.28.3 Configuration 3 (WMEC 270’), the requirement states this configuration includes 4 Low Power circuits, however the equipment list includes 2 High Power LPA’s. Please clarify how many low power and high power devices are specifically required for this vessel class.

Specification has been corrected to reflect the correct configuration of 2 low power circuits and 2 high power circuits.

Spec revision completed.

T4 HFRS Specification Requirement

4.1.28 large cutters (WMEC 282', WAGB 399', WAGB 420' and WLBB 240')

Regarding Requirement 4.1.28, for the large cutters (WMEC 282’, WAGB 399’, WAGB 420’ and WLBB 240’) where there is only a single cutter of each class, will the Government increase the weight allowance by 150 lbs?

No, weight allowance remains as specified in the requirements.

No Spec revision required.

T5 HFRS Specification Requirements

4.2.28 & 4.2.29 Requirements 4.2.28 & 4.2.29

Regarding Requirements 4.2.28 and 4.2.29, would the Government confirm that the applicable frequency range is

2.0 MHz to 29.9999 MHz per MIL-STD-188-141D?

Correct. As per MIL-STD-188-141D this spec only applies to the frequencies range of 2.0-29.9999 MHz, not 1.5 to 30 MHz.

No Spec revision required.

T6 HFRS Specification Requirement

4.1.23

The HFRS shall be cyber security compliant in accordance with

NIST SP 800-53.

Please advise the section of NIST SP 800-53 that is applicable to this RFP.

This reference has been determined by the Government to be not applicable to the HFRS requirements and requirement 4.1.23 has been removed.

Spec revision completed.

T7 HFRS Specification

Requirements

4.1.6 thru

4.1.20 (pages 5-6) n/a

These paragraphs define a number of 3rd party systems that the radio equipment is required to interface with.

Our equipment uses open standard interfaces that will be defined together with the necessary proprietary interface protocols within the IDD to be supplied. Please confirm that any work related to the integration activity would be the responsibility of the system integrator.

Integration activity is not a requirement of this contract and will be the responsibility of a separate system integrator.

No Spec revision required.

T8 HFRS Specification Requirement

4.1.28 (page 6) n/a

Each configuration lists a number of RCUs. We assume these RCUs will be remote mounted and will not count toward the total system height. Please confirm this assumption.

RCUs are assumed to be remotely mounted and do not count toward the total system height, however the RCUs do count toward the total system weight limitation.

No Spec revision required.

T9 HFRS Specification

Requirements

4.1.28.1 thru

4.1.28.11 (pages 7-9) n/a Request that the USCG please provide current architecture diagrams to clarify understanding of each of the configurations.

A current system architectures attachment has been added to the RFP as new attachment 12 via amendment 00001.

RFP Revision (add attachment) completed.

T10 HFRS Specification

Requirements

4.1.28.1 thru

4.1.28.11 (pages 7-9) n/a Please confirm that ‘multi-channel’ -- when applied to transceivers, receivers, modems etc. -- means ‘dual’ channel.

Not limited to dual channel, could be whatever configuration to meet specification requirement. Please note additional information available in the new current system architectures document (attachment 12).

No Spec revision required.

T11 HFRS Specification

Requirements

4.1.28.1 thru

4.1.28.11 (pages 7-9) n/a For each configuration, will all racked equipment be located in the same compartments or will racks be distributed in different compartments?

Not always in the same compartment. New current architectures document (new attachment 12) provides additional detail regarding current system configurations.

No Spec revision required.

T12 HFRS Specification Requirement

4.1.28.1 (page 7) n/a Configuration #1 calls for 2-off low power LPAs, but 3 antenna couplers. What is the interfacing arrangement between the two?

There is an antenna patch panel interfaced between the two.

Required for redundancy, vendor to define proposed solution.

No Spec revision required.

T13 HFRS Specification Requirement

4.1.28.1 (page 7) n/a Configuration #1 calls for a multicoupler, although there is no definition of this elsewhere. Does this refer to a receive multicoupler/ distribution function? If not, what is it?

Required for redundancy, vendor to define proposed solution. Please see the new current system architectures document (new attachment 12) for additional information.

Pending additional feedback/confirmation from technical to confirm this sufficiently addresses the question.

No Spec revision required.

T14 HFRS Specification

Requirements

4.1.28.1 thru

4.1.28.11 (pages 7-9) n/a

Most configurations define a quantity of standalone receivers. Are these fed from a receive antenna(s) and, if so, should some receive multicoupler/distribution capability be included in the equipment supply?

Are all receive feeds for transceivers derived from separate receive antenna(s) or are the antennas Tx/Rx?

Depends on the configuration and the vendor's proposed solution.

No Spec revision required. New current architectures attachment may help to clarify.

T15 HFRS Specification Requirement

4.1.28.3 (page 7) n/a Please confirm the NVIS ATU coupler is dedicated to the high power LPA.

No, it is not dedicated.

No spec revision required.

T16 HFRS Specification Requirement

4.1.28.4 (page 8) n/a

Similarly to Configuration #1, there are 4 PAs and 5 antenna couplers. What are the interfacing arrangements between them? Is the NVIS antenna coupler intended to be high power only?

What are the interfacing arrangements between them?

- Vendor to define proposed solution within the boundaries of the stated requirements.

Is the NVIS antenna coupler intended to be high power only?

- No

T17 HFRS Specification

Requirements

4.1.28.9 thru

4.1.28.11 (page 9) n/a

Configurations #8 thru #10 detail single channel transceivers and modems. Can these be supplied as dual channel (i.e. can 3x single be supplied as 1x dual plus 1x single)?

Vendor to define proposed solution within the boundaries of the stated requirements.

No Spec revision required.

T18 HFRS Specification

Requirements

4.1.28.10 & 4.1.28.11 (page 9) n/a These are the only configurations that detail pre/post selectors (presumably high power). What is the reason for this?

For improved signal quality.

No Spec revision required.

T19 HFRS Specification

Requirements

4.1.28.1 thru

4.1.28.11 (pages 7-9) n/a

Where multiple medium and high power LPAs are specified, are there any limitations on supplying their associated power supplies in dual racked arrangements where possible? For example, will high power LPAs (6U high) be racked in pairs where possible?

Vendor to define proposed solution within the boundaries of the stated requirements.

No Spec revision required.

T20 HFRS Specification Requirement

4.2.31 (page 12) n/a Are there any physical restrictions if the controller equipment is provided as a standalone unit (PC or RCU) (i.e. not fitted within the main equipment racks?)?

Not specified, vendor to define proposed solution within the boundaries of the stated requirements.

No Spec revision required.

T21 HFRS Specification Requirement

4.4.3 (page 19) n/a

The opening statement indicates that 3 different controllers could each individually control 3 different transceivers concurrently, but 4.4.3.2 suggests that only one controller can be master on the system at any one time. Please clarify the relationship between controllers and transceiver/receivers.

Vendor to define proposed solution within the boundaries of the stated requirements. The word "concurrently" has been removed from requirement 4.4.3 for clarity and the relationship between equipment is defined by requirement 4.4.3.2.

Spec revision completed.

T22 HFRS Specification Requirement

4.6.X (page 21) n/a Please clarify how the medium power LPA is being used in the system, as it is not referenced in any configuration.

Vendor to define proposed solution within the boundaries of the stated requirements. Medium Power LPA is not in use with any current configurations, however if vendor's solution utilizes a Medium Power LPA, these requirements are applicable.

No Spec revision required.

T23 HFRS Specification

Requirements 4.8.11, 4.9.10 &

4.10.10 (pages 23-25) n/a Please confirm the length of the grounded whip antenna.

10 meter/35 foot?

Two lengths currently in use, depending on configuration: 23' and 35'.

No spec revision required.

T24 HFRS Specification

Requirements

4.9.11 & 4.10.11

(pages 24-25) n/a Please provide the characteristics of the LWCA FAN antenna (i.e. impedance characteristic, input VSWR, etc.).

National Stock Number (NSN) provided in the specification and the characteristics of the LWCA Fan can be found using the NSN.

No Spec revision required.

T25 HFRS Specification Requirement

4.16.X (pages 26-29) n/a Should modems, multicouplers and power supplies be listed within any of the installation categories?

Sheltered, Controlled, and Isolated Environment. Specification requirement 4.16.2 has been revised accordingly.

Spec Revision completed.

T26 HFRS Specification Requirement

4.16.X (pages 26-29) n/a

We note that the radios and PA equipment are placed in different environmental categories, inferring that they are not co-located.

Would a co-located configuration be acceptable?

Yes.

No spec revision required.

T27 HFRS Specification Requirement

4.2.32.5 (page 14)

The HFRS transceiver (with built in or external modem) shall have a minimum of two input data interfaces for data exchange

Is this requirement describing use of data with the ISB-mode waveforms of MIL STD 188 110 Appendix F? For example, the two data interfaces are the USB and LSB channels of the multi-channel waveform.

Clarification from Vendor:

Requirement 4.2.32.5 defines the need for two data interfaces for each radio/modem channel. Is the purpose of this to provision for the transmission/reception of two independent data streams in ISB mode (requiring two discrete modem channels) as opposed to MIL-STD-188- 110D Appendix F, which defines the transmission/reception of a single data stream utilizing two sidebands (USB & LSB)? If not, what is their operational/functional purpose?

Requirement is for data exchange (RS-232 – Serial Data) regardless of radio mode. Function and purpose should support serial data.

No spec revision required.

T28 HFRS Specification General n/a

Can the USCG provide platform architecture diagrams that clarify the configurations outlined? An example – several configurations have several receive-only radios. Where do these get their inputs from and how are these distributed to the receivers? There is no mention of a receive multicoupler in these configurations.

A current system architectures document (new attachment 12) has been added through RFP amendment 00001.

RFP Revision (add attachment) completed.

T29 HFRS Specification not given n/a Given the shipboard operational environment, can Appendix F of MIL-STD-188-141D be considered an Objective requirement instead of a Threshold?

No.

No spec revision required.

T30 HFRS Specification Specification

4.1.26 (page 6) n/a Who(m) will be responsible for the cabinet designs/re-design? As a consequence of this, who(m) is responsible for installed system performance?

Cabinet re-design is not a requirement of this contract and will be the responsibility of a separate system integrator.

No Spec revision required.

T31 HFRS Specification Specification 4.1.23

(page 6) n/a NIST SP 800-53 is a system-level requirement. The contract appears to be an equipment supply contract.

Please clarify how this requirement should be applied.

This reference has been determined by the Government to be not applicable to the HFRS requirements and requirement 4.1.23 has been removed.

Spec revision completed.

T32 HFRS Specification

Specifications 4.8.12, 4.9.12 &

4.10.12 (page 30)

"…antenna coupler shall provide 50Ω output impedance to the antenna."

The coupler provides 50Ω back to the PA. Impedance to the antenna will depend on antenna impedance. Please confirm that 50Ω back to the PA is acceptable.

Confirmed acceptable.

No spec revision required.

T33 HFRS Specification Specification

4.20.1.1 (page 30)

"The contractor shall provide technical documentation describing installation, cabinet configuration,……."

Who(m) is responsible for the design of the cabinet configurations?

Cabinet re-design is not a requirement of this contract and will be the responsibility of a separate system integrator.