Attachment 10 HFRBS Crosswalk - V3.xls
XLS spreadsheet 162 KB Posted
- Attached to
- High Frequency Radio System (HFRS)
- Solicitation number
- DRAFT70Z04421R21000900
About this file
This draft request for proposal is for a high frequency radio system to replace legacy equipment aboard large United States Coast Guard cutters and shore facilities. The Coast Guard requires HF transceivers, receivers, remote control units, high power amplifiers, medium power amplifiers, low power amplifiers, antenna tuning units, and associated power supplies. Interested vendors are requested to provide company information and size, identify any concerns with requirements or evaluation factors, and submit comments on the draft solicitation and attachments by December 8, 2020. The Coast Guard will consider feedback to refine the final solicitation for this requirement.
View the file
Other files
| File | Type | Posted |
|---|---|---|
| Attachment 4 HFRS TMCR.docx | DOCX document | |
| Attachment 12_Logistics Plan Requirements.docx | DOCX document | |
| Attachment 3 HFRS IDD v1_0-20AUG20.docx | DOCX document | |
| Attachment 2 HFRS Specification-10NOV20.docx | DOCX document | |
| Attachment 11_FAR Provision 52.212-3_180023.pdf | ||
| Attachment 1 HFRBS kit pricing.xlsx | XLSX spreadsheet | |
| Attachment 7 DHS Form 700-21Fillable508.pdf | ||
| Attachment 9_PPQ_HFRS 210009.pdf | ||
| Combined Synopsis_Solicitation_210009 11042020.doc | DOC document | |
| Attachment 6_ MarkingsPackagingDeliveryInspect.doc | DOC document | |
| Attachment 8 DHS-Form-700-3.pdf |
Show all 11
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
Compliance Matrix
| SOLICITATION#: |
| CONTRACTOR'S NAME: |
| COMPLIANCE MATRIX TO ATTACHMENT 2, TECHNICAL SPECIFICATIONS |
An “Objective” is a preferred/desired system capability, but not a minimum required specification
| and will be evaluated based on the degree of benefit to the Government. | Contractor - Provide compliance information below for each specification. If a specification is addressed in more detail in your Volume I, also provide the Page #, Section/Paragraph within Volume I for reference. | |
| NOTE: All specifications below are from Section 4 - 8 of HFRS Specifications Document | ||
| Specification Section 1 - HF Radio System (HFRS) | ||
| Specification Section 1.1 - General Requirements | ||
| 1.1.1 The HFRS shall be compliant with MIL-STD-188-141D. | ||
| 1.1.2 The HFRS shall be compliant with MIL-STD-188-110D. | ||
| 1.1.3 The HFRS shall be comprised of commercial-off-the-shelf (COTS) products, available for immediate purchase in the United States of America. | ||
| 1.1.4 The HFRS shall be scalable, consisting of a combination of HF transceivers, receivers, RCU’s, low power Linear Power Amplifiers (LPA) and couplers, high power LPA’s and couplers, power supplies and conditioners, mating connectors, and any other hardware or software components required to make a complete system depending on platform or hull type. | ||
| 1.1.5 The Vendor shall provide a reliability prediction and service life with their proposal to ensure the design of the HFRS is adequate to meet USCG needs. | ||
| 1.1.6 The HFRS shall support external National Security Agency (NSA) Type I encryption devices for voice and data communications. | ||
| 1.1.7 The HFRS shall support external Type III encryption devices for voice and data communications. | ||
| 1.1.8 The HFRS functionality shall be fully compatible and able to be controlled via a third party Communications Management System (CMS) currently used in the Coast Guard. These systems are defined as a solution capable of remotely controlling a radio or associated devices manufactured by another source of supply. | ||
| 1.1.9 The HFRS functionality shall be fully compatible and able to be configured via a third party CMS currently used in the Coast Guard. | ||
| 1.1.10 The HFRS shall interface with existing CG Automated Communications Resource Manager via RS232/485 Protocol for controls. | ||
| 1.1.11 The HFRS shall interface with existing CG Automated Communications Resource Manager via TCP/IP, 10/100 Base T (IEEE 802.3) Protocol for IP data. | ||
| 1.1.12 The HFRS shall be capable of being programmed and configured via a Windows based PC, utilizing a connector on the front panel of the transceiver, receiver, and RCU. | ||
| 1.1.13 The HFRS shall provide option to use external time standard reference in accordance with the Interface Design Description (IDD). | ||
| 1.1.14 Objective: Components of the HFRS shall be offered and supported by the same manufacturer. | ||
| 1.1.15 Objective: The HFRS shall comply with NATO Technical Standards for Single Channel HF Radio Equipment in accordance with STANAG 4203. | ||
| Cyber Security | ||
| 1.1.16 The HFRS shall be cyber security compliant in accordance with NIST SP 800-53. | ||
| Electrical | ||
| 1.1.17 Unless otherwise specified, HFRS equipment shall operate in a nominal 115/230 VAC, 60 HZ, Single Phase, Delta, in accordance with MIL-STD-1399, Section 300A/B, TYPE I. | ||
| 1.1.18 HFRS equipment shall demonstrate no susceptibility to voltage spikes when tested in accordance with MIL-STD-1399, Section 300B. | ||
| Mechanical | ||
| 1.1.19 The HFRS shall be mountable into standard, 19- inch ANSI/EIA-310-D enclosures. | ||
| 1.1.20 The HFRS equipment shall not exceed the following rack space and weight constraints of anticipated configuration (based off of current configuration) in accordance with Table 1: |
Note: All couplers are included in the Total Configuration Max Weight, but will not be installed in the rack.
| Table 1: Platform Configurations | ||||
| Equipment | Max Height/Depth | Max Weight | ||
| Configuration 1 (FRC 154’) | 25U/16” | 193.5 lbs | ||
| (2) Low power circuits includes: | ||||
| (1) Multi-channel transceiver interfacing with two circuits, (1) multi-channel receiver (1) multi- channel ALE modem, power supplies, (1) RCU, (2) Low power LPA, (1) RF Switch Matrix, (1) Multi-coupler, (2) Low power Antenna Couplers, (1) NVIS ATU Coupler | ||||
| Configuration 2 (WMEC 210’) | 34U/16” | 182.2 lbs | ||
| (3) Low power circuits includes: | ||||
| (1) Multi-channel transceiver interfacing with two circuits, (1) single channel transceiver, (1) multi-channel ALE modem, (1) single-channel ALE modem, power supplies, (3) RCU, (3) Low power LPA’s, (2) Low power Antenna Couplers, (1) NVIS ATU Coupler | ||||
| Configuration 3 (WMEC 270’) | 52U/16” | 555.2 lbs | ||
| (4) Low power circuits includes: | ||||
| (2) Multi-channel transceivers interfacing with four circuits, (2) multi-channel ALE modems, power supplies, (3) RCU, (2) Low power LPA’s, (2) High power LPA’s, (2) Low power Antenna Couplers, (2) NVIS ATU Couplers | ||||
| Configuration 4 (WMEC 282’) | 49U/20” | 329.8 lbs | ||
| (3) Low power & (1) high power circuits includes: | ||||
| (2) Multi-channel transceivers interfacing with four circuits, (2) multi-channel ALE modems, (4) RCU, (3) Low power LPA’s, (1) High power LPA, (3) Low power Antenna Couplers, (1) High power Antenna Coupler, (1) NVIS Antenna Coupler | ||||
| Configuration 5 (WAGB 399’ & 420’) | 65U/20” | 964.7 lbs | ||
| (1) Low power & (4) high power circuits includes: | ||||
| (2) Multi-channel transceivers interfacing with four circuits, (1) single-channel transceiver (2) multi-channel ALE modems, (1) single-channel ALE modem, power supplies, (4) RCU, (1) Low power LPA’s, (4) High power LPA, (1) Low power Antenna Couplers, (4) High power Antenna Coupler | ||||
| Configuration 6 (WTGB 140’) | 10U/19” | 168 lbs | ||
| (2) Low power circuits includes: | ||||
| (1) Multi-channel transceiver interfacing with two circuits, (1) multi-channel ALE modem, power supplies, (2) Low power LPA, (2) Low Power Antenna Couplers | ||||
| Configuration 7 (WLM 175’) | 8U/17.66” | 92 lbs | ||
| (1) Low power circuit includes: | ||||
| (1) single-channel transceiver, (1) single-channel ALE modem, power supplies, (1) RCU, (1) Low power LPA, (1) Antenna Coupler | ||||
| Configuration 8 (WLB 225’) | 16U/17.66” | 236 lbs | ||
| (3) Low power circuits includes: | ||||
| (3) single-channel transceivers, (3) single-channel ALE modems, power supplies, (1) RCU, (3) Low power LPA’s, (3) Low power Antenna Couplers | ||||
| Configuration 9 (WLBB 240’) | 23U/19” | 292 lbs | ||
| (3) Low Power circuits includes: | ||||
| (3) single-channel transceivers, (3) single-channel ALE modems, power supplies, (2) RCU, (3) Low power LPA, (3) Low power Antenna Couplers, (3) PRE/POST Selectors | ||||
| Configuration 10 (WIX 295’) | 19U/19” | 363 lbs | ||
| (2) Low & (1) High Power circuits includes: | ||||
| (3) single-channel transceivers, (3) single-channel ALE modems, (1) RCU, (2) Low power LPA’s, (1) High power LPA, (2) Low power Antenna Couplers, (1) High power Antenna Coupler, (3) PRE/POST Selectors | ||||
| Specification Section 1.2 - Transceiver Requirements | ||||
| 1.2.1 The HFRS shall be able to exchange communications on multiple transceiver circuits to support simultaneous operations (SIMOPS). SIMOPS is defined as the use of simplex/half duplex and/or unidirectional radio frequency paths to communicate with multiple radio equipped assets simultaneously (e.g., transmitting and/or receiving radio signals from a cutter, small boat, and aircraft at the same time). | ||||
| 1.2.2 The HFRS transceiver system shall have a minimum of two separate input/output channels independent of the RCU. | ||||
| 1.2.2.1 The HFRS transceiver shall have a minimum of two external interfaces for transmit audio (0 dBm at 600-ohm). | ||||
| 1.2.2.2 The HFRS transceiver shall have a minimum of two external interfaces for receive audio (0 dBm at 600-ohm). | ||||
| 1.2.2.3 The HFRS transceiver shall have a minimum of two external interfaces for Keyline/PTT. | ||||
| 1.2.3 The HFRS transceiver shall provide a fixed audio output (0dBm at 600-ohm) of transmit and receive signals for recording capabilities (currently the DVL-740). | ||||
| 1.2.4 The HFRS transceiver shall have an operating frequency range of, at a minimum, 1.5 MHz – 30 MHz. | ||||
| 1.2.5 The HFRS transceiver frequency shall be adjustable in 10 Hz increments. | ||||
| 1.2.6 The HFRS transceiver shall be compatible with existing 2G ALE networks in accordance with MIL-STD-188-141D Appendix A. | ||||
| 1.2.7 The HFRS transceiver shall be 3G ALE capable in accordance with MIL-STD-188-141D Appendix C. | ||||
| 1.2.8 Objective: The HFRS transceiver shall be 4G ALE capable in accordance with MIL-STD-188-141D Appendix G. | ||||
| 1.2.9 Objective: The HFRS transceiver shall be software/firmware upgradeable to 4G ALE IAW MIL-STD-188-141D, Appendix G. | ||||
| 1.2.10 The HFRS transceiver data modem shall be capable of multi-channel operations (independent sidebands of a single carrier or 2-ISB) IAW MIL-STD-188-110D, Appendix F. | ||||
| 1.2.11 Objective: The HFRS transceiver shall have an HF data modem compatible with WBHF MIL-STD-188-110D - Appendix D. | ||||
| ` | ||||
| 1.2.13 Objective: The HFRS transceiver data modem shall be capable of multi-channel operations (independent sidebands of a single carrier or 2-ISB) in WBHF IAW MIL-STD-188-110D, Appendix D and F. | ||||
| 1.2.14 Objective: The HFRS shall exchange data via NATO robust mode in accordance with STANAG 4415. | ||||
| 1.2.15 Objective: The HFRS shall exchange data via NATO serial tone mode in accordance with STANAG 4539. | ||||
| 1.2.16 Objective: The HFRS transceiver data modem shall be capable of frequency-hopping (anti-jam) in accordance with MIL-STD-188-148. | ||||
| 1.2.17 Objective: The HFRS transceiver shall be capable of ALE linking protection in accordance with MIL-STD-188-141D Appendix B. | ||||
| 1.2.18 Objective: The HFRS transceiver shall be capable of Wideband ALE linking protection in accordance with MIL-STD-188-141D Appendix H. | ||||
| 1.2.19 Objective: The HFRS shall have a robust modem capable of 75 bits per second (bps) in accordance with STANAG 4415. | ||||
| 1.2.20 The HFRS transceiver shall be either innately capable of two-way secure Link 11 Tactical Digital Information Link (TADIL A) communications or made capable when an external modem is used IAW MIL-STD-188-203-1. | ||||
| 1.2.21 Objective: The HFRS transceiver shall be capable, via software upgrade, to compatibility with Link 22/ NATO Improved Link Eleven (NILE) in compliance with STANAG 5522. | ||||
| 1.2.22 The HFRS transceiver shall be capable of upper sideband (USB) IAW MIL-STD-188-141D. | ||||
| 1.2.23 The HFRS transceiver shall be capable of lower sideband (LSB) IAW MIL-STD-188-141D. | ||||
| 1.2.24 The HFRS transceiver shall be capable of continuous waveform (CW) IAW MIL-STD-188-141D. | ||||
| 1.2.25 The HFRS transceiver shall be capable of amplitude modulation (AM) IAW MIL-STD-188-141D. | ||||
| 1.2.26 The HFRS transceiver shall be capable of dual independent sideband (2-ISB) IAW MIL-STD-188-141D. | ||||
| 1.2.27 Capable of frequency shift keying (FSK) modes of operation within the transceiver system IAW MIL-STD-188-141D. | ||||
| 1.2.28 The HFRS transceiver shall have HF data exchange capability IAW MIL-STD-188-141D. | ||||
| 1.2.29 Objective: The HFRS transceiver shall be compatible with HF data exchange capability in compliance with STANAG 5066. | ||||
| 1.2.30 The HFRS transceiver shall have receive sensitivity of ≤ -111 dBm (0.63 µV) with a 10 dB SINAD over the operating frequency range in CW mode (unmodulated) at 3 kHz bandwidth. | ||||
| 1.2.31 Objective: The HFRS transceiver shall have receive sensitivity of ≤ -121 dBm (0.63 µV) with a 10 dB SINAD over the operating frequency range in CW mode (unmodulated) at 3 kHz bandwidth. | ||||
| 1.2.32 The HFRS transceiver shall have squelch circuitry that monitors the RF input signal to the transceiver while muting the audio output to the speakers. | ||||
| 1.2.33 The HFRS transceiver shall include a software defined and programmable Human Machine Interface (HMI) radio control system that provides user friendly control of all radio functions including ALE operations. Available as supplied as a front panel local control or standalone RCU. | ||||
| 1.2.33.1 The HFRS transceiver local front panel controls shall be built into the transceiver or use a local RCU. | ||||
| 1.2.33.2 The HFRS transceiver local front panel controls shall be built into the transceiver/s and/or use a local RCU/s. | ||||
| 1.2.33.3 The HFRS transceiver shall have local front panel status display for receive RF signal strength. | ||||
| 1.2.33.4 The HFRS transceiver shall have local front panel controls for Output Power with selection options for low to high power. | ||||
| 1.2.33.5 The HFRS transceiver shall have local front panel status display for Output Power. | ||||
| 1.2.33.6 The HFRS transceiver shall have local front panel controls for Frequency Selection. | ||||
| 1.2.33.7 The HFRS transceiver shall have local front panel status display for Frequency Selection. | ||||
| 1.2.33.8 The HFRS transceiver shall have local front panel controls for Modulation Selection (e.g. USB, LSB, ISB, AM, CW, FSK (ALE)). | ||||
| 1.2.33.9 The HFRS transceiver shall have local front panel status display for Modulation Selection (e.g. USB, LSB, ISB, AM, CW, FSK (ALE)). | ||||
| 1.2.33.10 The HFRS transceiver shall have a visual power indicator on front panel. | ||||
| 1.2.33.11 The HFRS transceiver shall have local front panel controls for display intensity. | ||||
| 1.2.33.11.1 The HFRS transceiver local front panel display shall be visible at night without loss of night-vision, down to 1 NITS (cd/m2). | ||||
| 1.2.33.11.2 Objective: The HFRS transceiver local front panel display shall be dimmable to 0.5 NITS (cd/m2). | ||||
| 1.2.33.11.3 Objective: The HFRS transceiver local front panel display shall be able to be powered off, while still maintaining all required transceiver behavior. | ||||
| 1.2.33.11.4 Objective: The dimming of the HFRS transceiver local front panel display shall be accomplished by controls that do not require the screen to be visible. Dimming shall not be accomplished solely via on-screen menus. | ||||
| 1.2.33.11.5 Objective: The HFRS transceiver local front panel display shall employ mechanical (knob/push button) backlight dimming. | ||||
| 1.2.33.12 The HFRS transceiver shall include an internal speaker. | ||||
| 1.2.33.12.1 The HFRS transceiver shall have local front panel control for internal speaker volume. | ||||
| 1.2.33.12.2 The HFRS shall have local front panel status display for volume level. | ||||
| 1.2.33.13 The HFRS shall include an external speaker with independent volume control. | ||||
| 1.2.33.14 The HFRS shall include a compatible microphone for use with the transceiver. | ||||
| 1.2.33.14.1 The HFRS microphone shall have Push-to-Talk (PTT) capabilities. | ||||
| 1.2.33.14.2 Objective: The HFRS microphone shall be interchangeable between the Transceiver and RCU. | ||||
| 1.2.33.15 The HFRS shall have local front panel control for Noise Filtering (Squelch). | ||||
| 1.2.33.16 The HFRS shall have local front panel controls of ALE linking operation. | ||||
| 1.2.33.16.1 The HFRS shall be capable of being programmed with both ALE addresses and frequencies. | ||||
| 1.2.33.17 The HFRS shall have operator friendly local front panel with status display of ALE link. | ||||
| 1.2.33.17.1 Objective: The HFRS shall have discernable audible alerts for ALE link established/disestablish. | ||||
| 1.2.33.17.2 Objective: The HFRS Transceiver shall provide Link Quality Analysis (LQA) on display. | ||||
| 1.2.34 The HFRS transceiver shall be capable of automatic (upon equipment power on) built-in test (BIT) that encompasses all hardware modules by identifying faults to the lowest repairable unit. | ||||
| 1.2.35 The HFRS transceiver shall be Transmission Control Protocol / Internet Protocol (IP) addressable via TCP/IP interface. | ||||
| 1.2.35.1 The HFRS transceiver shall be capable of full remote control via TCP/IP. | ||||
| 1.2.35.2 The HFRS transceiver shall be capable of remote operator-initiated BIT via TCP/IP interface. | ||||
| 1.2.35.3 The HFRS transceiver shall be programmable/configurable via TCP/IP. | ||||
| 1.2.35.4 The HFRS transceiver TCP/IP addressability shall have the ability to simultaneously operate locally and remotely via PC or Server-based virtual control. | ||||
| 1.2.35.5 The HFRS transceiver shall be compatible with Internet Protocol version 4 (IPv4). | ||||
| 1.2.35.6 Objective: The HFRS transceiver shall utilize, or be upgradeable via software or firmware, Internet Protocol version 6 (IPv6) via software/firmware update. | ||||
| 1.2.36 The HFRS transceiver shall have a serial interface. | ||||
| 1.2.36.1 The HFRS transceiver shall be capable of full remote control via serial interface. | ||||
| 1.2.36.2 The HFRS transceiver shall be programmable/configurable via serial interface. | ||||
| 1.2.37 Objective: The HFRS transceiver shall be JITC certified to comply with HF interoperability standards. | ||||
| 1.2.37.1 Objective: The HFRS transceiver shall be JITC certified for MIL-STD-188-110D. | ||||
| 1.2.37.2 Objective: The HFRS transceiver shall be JITC certified for MIL-STD-188-141D. | ||||
| 1.2.37.3 Objective: The HFRS transceiver shall be JITC certified for MIL-STD-188-148B. | ||||
| 1.2.37.4 Objective: The HFRS transceiver shall be JITC certified for MIL-STD-188-203-1A | ||||
| Specification Section 1.3 Receiver Requirements | ||||
| 1.3.1 The HFRS receiver shall include a software defined and programmable Human Machine Interface (HMI) radio control system that provides control of all radio functions. Available as supplied as a front panel local control or standalone RCU. | ||||
| 1.3.1.1 The HFRS receiver local front panel controls shall be built into the receiver or use a local RCU. | ||||
| 1.3.1.2 The HFRS receiver shall have local front panel status display for receive RF signal strength. | ||||
| 1.3.1.3 The HFRS receiver shall have local front panel controls for Frequency Selection. | ||||
| 1.3.1.4 The HFRS receiver shall have local front panel status display for Frequency Selection. | ||||
| 1.3.1.5 The HFRS receiver shall have local front panel controls for Modulation Selection (e.g. USB, LSB, ISB, AM, CW). | ||||
| 1.3.1.6 The HFRS receiver shall have local front panel status display for Modulation Selection (e.g. USB, LSB, ISB, AM, CW). | ||||
| 1.3.1.7 The HFRS receiver shall have a visual power indicator on front panel. | ||||
| 1.3.1.8 The HFRS receiver shall have local front panel controls for display intensity. | ||||
| 1.3.1.8.1 The HFRS receiver local front panel display shall be visible at night without loss of night-vision, down to 1 NITS (cd/m2). | ||||
| 1.3.1.8.2 Objective: The HFRS receiver local front panel display shall be dimmable to 0.5 NITS (cd/m2). | ||||
| 1.3.1.8.3 Objective: The HFRS receiver local front panel display shall be able to be powered off, while still maintaining all required receiver behavior. | ||||
| 1.3.1.8.4 Objective: The dimming of the HFRS receiver local front panel display shall be accomplished by controls that do not require the screen to be visible. Dimming shall not be accomplished solely via on-screen menus. | ||||
| 1.3.1.8.5 Objective: The HFRS receiver local front panel display shall employ mechanical (knob/push button) backlight dimming. | ||||
| 1.3.1.9 The HFRS receiver shall include an internal speaker with volume control. | ||||
| 1.3.1.9.1 The HFRS receiver shall have local front panel control for volume. | ||||
| 1.3.1.10 The HFRS receiver shall have local front panel status display for volume level. | ||||
| 1.3.1.11 The HFRS receiver shall have local front panel control for Noise Filtering (Squelch). | ||||
| 1.3.2 The HFRS receiver shall provide fixed audio output (0 dBm at 600-ohm) of receive signals for recording capabilities (currently the DVL-740). | ||||
| 1.3.2.1 Objective: The HFRS receiver system shall have a minimum of two separate output channels independent of the RCU. | ||||
| 1.3.3 The HFRS receiver shall operate from, at minimum, 20 kHz to 30 MHz with 10 Hz increments. | ||||
| 1.3.4 The HFRS receiver shall have receive sensitivity of ≤ -111 dBm (0.63 µV) with a 10 dB SINAD over the operating frequency range in CW mode (unmodulated) at 3 kHz bandwidth. | ||||
| 1.3.5 Objective: The HFRS receiver shall have receive sensitivity of ≤ -121 dBm (0.63 µV) with a 10 dB SINAD over the operating frequency range in CW mode (unmodulated) at 3 kHz bandwidth. | ||||
| 1.3.6 The HFRS receiver shall have squelch circuitry that monitors the RF input signal while muting the audio output to the speakers. | ||||
| 1.3.7 The HFRS receiver data modem shall be capable of a minimum of two separate output channels compatible with MIL-STD-188-110D, Appendix F. | ||||
| 1.3.8 Objective: The HFRS receiver shall have an HF data modem compatible with WBHF MIL-STD-188-110D - Appendix D. | ||||
| 1.3.9 Objective: The HFRS receiver shall have an HF data modem that complies with STANAG 4285. | ||||
| 1.3.10 Objective: The HFRS receiver data modem shall be capable of a minimum of two separate output channels compatible with WBHF MIL-STD-188-110D - Appendix F. | ||||
| 1.3.11 The HFRS receiver shall be capable of upper sideband (USB) IAW MIL-STD-188-141D. | ||||
| 1.3.12 The HFRS receiver shall be capable of lower sideband (LSB) IAW MIL-STD-188-141D. | ||||
| 1.3.13 The HFRS receiver shall be capable of continuous waveform (CW) IAW MIL-STD-188-141D. | ||||
| 1.3.14 The HFRS receiver shall be capable of amplitude modulation (AM) IAW MIL-STD-188-141D. | ||||
| 1.3.15 The HFRS receiver shall be capable of dual independent sideband (2-ISB) IAW MIL-STD-188-141D. | ||||
| 1.3.16 The HFRS receiver shall be capable of automatic (upon equipment power on) built-in test (BIT) that encompasses all hardware modules by identifying faults to the lowest repairable unit. | ||||
| 1.3.17 The HFRS receiver shall be Transmission Control Protocol / Internet Protocol (IP) addressable via TCP/IP interface. | ||||
| 1.3.17.1 The HFRS receiver shall be capable of full remote control via TCP/IP. | ||||
| 1.3.17.2 The HFRS receiver shall be capable of remote operator-initiated BIT via TCP/IP interface. | ||||
| 1.3.17.3 The HFRS receiver shall be programmable/configurable via TCP/IP. | ||||
| 1.3.17.4 The HFRS receiver TCP/IP addressability shall have the ability to simultaneously operate locally and remotely via PC or Server-based virtual control. | ||||
| 1.3.17.5 The HFRS receiver shall be compatible with Internet Protocol version 4 (IPv4). | ||||
| 1.3.17.6 Objective: The HFRS receiver shall utilize, or be upgradeable via software or firmware, Internet Protocol version 6 (IPv6) via software/firmware update. | ||||
| 1.3.18 The HFRS receiver shall have a serial interface. | ||||
| 1.3.18.1 The HFRS receiver shall be capable of full remote control via serial interface. | ||||
| 1.3.18.2 The HFRS receiver shall be programmable/configurable via serial interface. | ||||
| 1.3.19 Objective: The HFRS receiver shall be JITC certified to comply with HF interoperability standards. | ||||
| 1.3.19.1 Objective: The HFRS receiver shall be JITC certified for MIL-STD-188-110D. | ||||
| 1.3.19.2 Objective: The HFRS receiver shall be JITC certified for MIL-STD-188-141D. | ||||
| 1.3.19.3 Objective: The HFRS receiver shall be JITC certified for MIL-STD-188-148B. | ||||
| 1.3.19.4 Objective: The HFRS receiver shall be JITC certified for MIL-STD-188-203-1A | ||||
| Specification Section 1.4 - Remote Control Unit (RCU) Requirements | ||||
| 1.4.1 The HFRS RCU shall be controlled remotely using operator friendly RCU’s. | ||||
| 1.4.1.1 The HFRS RCU shall have local front panel status display for receive RF signal strength. | ||||
| 1.4.1.2 The HFRS RCU shall have controls for Output Power with selection options for low to high power. | ||||
| 1.4.1.3 The HFRS RCU shall have status display for Output Power. | ||||
| 1.4.1.4 The HFRS RCU shall have controls for Frequency Selection. | ||||
| 1.4.1.5 The HFRS RCU shall have local front panel status display for Frequency Selection. | ||||
| 1.4.1.6 The HFRS RCU shall have controls for Modulation Selection (e.g. USB, LSB, ISB, AM, CW, FSK (ALE)). | ||||
| 1.4.1.7 The HFRS RCU shall have status display for Modulation Selection (e.g. USB, LSB, ISB, AM, CW, FSK (ALE)). | ||||
| 1.4.1.8 The HFRS RCU shall have a visual power indicator on front panel. | ||||
| 1.4.1.9 The HFRS RCU shall have controls for display intensity. | ||||
| 1.4.1.9.1 The HFRS RCU display shall be visible at night without loss of night-vision, down to 1 NITS (cd/m2). | ||||
| 1.4.1.9.2 Objective: The HFRS RCU display shall be dimmable to 0.5 NITS (cd/m2). | ||||
| 1.4.1.9.3 Objective: The HFRS RCU display shall be able to be powered off, while still maintaining all required transceiver behavior. | ||||
| 1.4.1.9.4 Objective: The dimming of the HFRS RCU display shall be accomplished by controls that do not require the screen to be visible. Dimming shall not be accomplished solely via on-screen menus. | ||||
| 1.4.1.9.5 Objective: The HFRS RCU display shall employ mechanical (knob/push button) backlight dimming. | ||||
| 1.4.1.10 The HFRS RCU shall include an internal speaker with volume control. | ||||
| 1.4.1.10.1 The HFRS RCU shall have local front panel control for internal speaker volume. | ||||
| 1.4.1.10.2 The HFRS RCU shall have status display for volume level. | ||||
| 1.4.1.11 The HFRS RCU shall include an external speaker with independent volume control. | ||||
| 1.4.1.12 The HFRS shall include a compatible microphone for use with the RCU. | ||||
| 1.4.1.12.1 The HFRS microphone shall have Push-to-Talk (PTT) capabilities. | ||||
| 1.4.1.12.2 Objective: The HFRS microphone shall be interchangeable between the Transceiver and RCU. | ||||
| 1.4.1.13 The HFRS RCU’s shall have controls for Noise Filtering (Squelch). | ||||
| 1.4.1.14 The HFRS RCU’s shall have controls of ALE linking operation. | ||||
| 1.4.1.14.1 The HFRS RCU’s shall be capable of programming both ALE addresses and frequencies. | ||||
| 1.4.1.15 The HFRS RCU’s shall have status display of ALE link. | ||||
| 1.4.1.15.1 Objective: The HFRS RCU’s shall have discernable audible alerts for ALE link established/disestablish. | ||||
| 1.4.1.15.2 Objective: The HFRS RCU shall provide Link Quality Analysis (LQA) on display | ||||
| 1.4.2 The HFRS RCU shall have squelch circuitry that monitors the RF input signal to the transceiver while muting the audio output to the speakers. | ||||
| 1.4.3 The HFRS shall be selectable on one to five independent RCU’s allowing concurrent control of transceiver functions of one to five independent transmitter circuits (1-5 RCUs to one Transceiver/receiver), (one RCU to 1-5 Transceivers/ receivers). | ||||
| 1.4.3.1 All RCU shall be updated with current parameters following changes on any other RCU/s. | ||||
| 1.4.4 The HFRS shall be configurable on one to five independent RCU’s allowing concurrent control of transceiver functions of one to five independent transmitter circuits. | ||||
| 1.4.5 The HFRS shall use common, interchangeable RCU’s. | ||||
| 1.4.6 The HFRS RCU shall be capable of automatic (upon equipment power on) built-in test (BIT) that encompasses all hardware modules by identifying faults to the lowest repairable unit. | ||||
| 1.4.7 The HFRS RCU shall be capable of operator initiated built-in test (BIT) that encompasses all hardware modules by identifying faults to the lowest repairable unit. | ||||
| 1.4.8 Objective: The RCU shall be one of the interfaces used to program and configure the HFRS transceiver. This shall include the capability for the operator to input and edit frequency scan lists. | ||||
| 1.4.9 The HFRS RCU shall be Transmission Control Protocol / Internet Protocol (IP) addressable via TCP/IP interface. | ||||
| 1.4.9.1 The HFRS RCU shall be capable of full remote control via TCP/IP. | ||||
| 1.4.9.2 The HFRS RCU shall be capable of remote operator-initiated BIT via TCP/IP interface. | ||||
| 1.4.9.3 The HFRS RCU shall be programmable/configurable via TCP/IP. | ||||
| 1.4.9.4 The HFRS RCU shall be compatible with Internet Protocol version 4 (IPv4). | ||||
| 1.4.10 The HFRS RCU shall have a serial interface. | ||||
| 1.4.10.1 The HFRS RCU shall allow full remote control of transceiver and receiver via serial interface. | ||||
| 1.4.10.2 The HFRS shall be programmable/configurable by using the RCU via serial interface. | ||||
| Specification Section 1.5 - Low Power Linear Power Amplifier Requirements | ||||
| 1.5.1 The HFRS configuration shall include Low Power LPA’s (Minimum 100W peak envelope power) with 100% duty cycle at rated power throughout the transceiver’s frequency spectrum. | ||||
| 1.5.2 The Low Power LPA shall have operator selectable output level control within the range of 0-100% (0% = transmit inhibit, 100% = max power). | ||||
| 1.5.3 The Low Power LPA shall be capable of automatic (upon equipment power on) built-in test (BIT) that encompasses all hardware modules by identifying faults to the lowest repairable unit | ||||
| 1.5.4 The Low Power LPA shall be BIT capable allowing faults to be detected and then displayed on the RCU and Transceiver. | ||||
| 1.5.4.1 Objective: The Low Power LPA shall be BIT compatible allowing faults to be detected and relayed on IPV4 interface. | ||||
| 1.5.4.2 Objective: The Low Power LPA shall be BIT compatible allowing faults to be detected and relayed on IPV6 interface. | ||||
| 1.5.5 The Low Power LPA shall have a visual power indicator on front panel. | ||||
| 1.5.6 The Low Power LPA shall have a visual hardware condition indicator on front panel. | ||||
| 1.5.7 The Low Power LPA shall have a visual fault condition indicator on front panel. | ||||
| 1.5.8 Objective: The Low Power LPA shall have limited power operation upon module/component failure. | ||||
| 1.5.9 Objective: The Low Power LPA shall have operator adjustable intensity of front panel indicators. | ||||
| Specification Section 1.6 - Objective: Medium Power Linear Power Amplifier Requirements | ||||
| 1.6.1 Objective: The HFRS configuration shall include a Medium Power LPA (Minimum 500W peak envelope power) with 100% duty cycle at rated power throughout the transceiver’s frequency spectrum. | ||||
| 1.6.2 Objective: The Low Power LPA shall have operator selectable output level control within the range of 0-100% (0% = transmit inhibit, 100% = max power). | ||||
| 1.6.3 Objective: The Medium Power LPA shall be capable of automatic (upon equipment power on) built-in test (BIT) that encompasses all hardware modules by identifying faults to the lowest repairable unit. | ||||
| 1.6.4 Objective: The Medium Power LPA shall be BIT capable allowing faults to be detected and then displayed on the RCU and Transceiver. | ||||
| 1.6.4.1 Objective: The Medium Power LPA shall be BIT compatible allowing faults to be detected and relayed on IPV4 interface. | ||||
| 1.6.4.2 Objective: The Medium Power LPA shall be BIT compatible allowing faults to be detected and relayed on IPV6 interface | ||||
| 1.6.5 Objective: The Medium Power LPA shall have a visual power indicator on front panel. | ||||
| 1.6.6 Objective: The Medium Power LPA shall have a visual hardware condition indicator on front panel. | ||||
| 1.6.7 Objective: The Medium Power LPA shall have a visual fault condition indicator on front panel. | ||||
| 1.6.8 Objective: The Medium Power LPA shall have limited power operation upon module/component failure. | ||||
| 1.6.9 Objective: The Low Power LPA shall have operator adjustable intensity of front panel indicators. | ||||
| Specification Section 1.7 - High Power Linear Power Amplifier Requirements | ||||
| 1.7.1 The HFRS configuration shall include a High Power LPA (minimum 1kW peak envelope power) with 100% duty cycle at rated power throughout the transceiver’s frequency spectrum. | ||||
| 1.7.2 The Low Power LPA shall have operator selectable output level control within the range of 0-100% (0% = transmit inhibit, 100% = max power). | ||||
| 1.7.3 The High Power LPA shall be capable of automatic (upon equipment power on) built-in test (BIT) that encompasses all hardware modules by identifying faults to the lowest repairable unit. | ||||
| 1.7.4 The High Power LPA shall be BIT capable allowing faults to be detected and then displayed on the RCU and Transceiver. | ||||
| 1.7.4.1 Objective: The High Power LPA shall be BIT compatible allowing faults to be detected and relayed on IPV4 interface. | ||||
| 1.7.4.2 Objective: The High Power LPA shall be BIT compatible allowing faults to be detected and relayed on IPV6 interface | ||||
| 1.7.5 The High Power LPA shall have a visual power indicator on front panel. | ||||
| 1.7.6 The High Power LPA shall have a visual hardware condition indicator on front panel. | ||||
| 1.7.7 The High Power LPA shall have a visual fault condition indicator on front panel. | ||||
| 1.7.8 Objective: The High Power LPA shall have limited power operation upon module/component failure. | ||||
| 1.7.9 Objective: The High Power LPA shall have operator adjustable intensity of front panel indicators. | ||||
| Specification Section 1.8 - Low Power Antenna Requirements | ||||
| 1.8.1 The Low Power antenna coupler shall cover the operating frequency of the transceiver. | ||||
| 1.8.2 The Low Power antenna coupler shall be capable of maximum rated peak envelope power at a 100% duty cycle at rated power throughout the transceiver’s frequency spectrum. | ||||
| 1.8.3 The Low Power antenna coupler shall be BIT compatible allowing faults to be detected and then displayed on the RCU and Transceiver. | ||||
| 1.8.4 Objective: The Low Power Antenna Coupler shall be BIT compatible allowing faults to be detected and relayed on IPV4 interface. | ||||
| 1.8.5 Objective: The Low Power Antenna Coupler shall be BIT compatible allowing faults to be detected and relayed on IPV6 interface. | ||||
| 1.8.6 The Low Power antenna coupler shall include built in overvoltage protection to protect HFRS from lightning strikes. | ||||
| 1.8.7 The manufacturer supplied hardware shall allow a power efficient coupling capability with the Coast Guard grounded NVIS antenna system throughout the transceiver operating frequency range with a maximum voltage standing wave ratio (VSWR) of 2.0:1. | ||||
| 1.8.8 The manufacturer supplied hardware shall allow power efficient coupling capability with the Coast Guard grounded whip antenna throughout the transceiver operating frequency range with a maximum voltage standing wave ratio (VSWR) of 2.0:1. | ||||
| 1.8.9 The Low Power antenna coupler shall provide 50Ω output impedance to antenna. | ||||
| Specification Section 1.9 - Objective: Medium Power Antenna Requirements | ||||
| 1.9.1 Objective: The Medium Power antenna coupler shall cover the operating frequency of the transceiver. | ||||
| 1.9.2 Objective: The Medium Power antenna coupler shall be capable of maximum rated peak envelope power at a 100% duty cycle at rated power throughout the transceiver’s frequency spectrum. | ||||
| 1.9.3 Objective: The Medium Power antenna coupler shall be BIT compatible allowing faults to be detected and then displayed on the RCU and Transceiver. | ||||
| 1.9.4 Objective: The Medium Power Antenna Coupler shall be BIT compatible allowing faults to be detected and relayed on IPV4 interface. | ||||
| 1.9.5 Objective: The Medium Power Antenna Coupler shall be BIT compatible allowing faults to be detected and relayed on IPV6 interface. | ||||
| 1.9.6 Objective: The Medium Power antenna coupler shall include built in overvoltage protection to protect HFRS from lightning strikes. | ||||
| 1.9.7 Objective: The manufacturer supplied hardware shall allow power efficient coupling capability with the Coast Guard grounded whip antenna throughout the transceiver operating frequency range with a maximum voltage standing wave ratio (VSWR) of 2.0:1. | ||||
| 1.9.8 Objective: The manufacturer supplied hardware shall allow power efficient coupling capability with the Coast Guard grounded Light Weight Communications Antenna (LWCA) FAN antenna throughout the transceiver operating frequency range with a maximum voltage standing wave ratio (VSWR) of 2.0:1. | ||||
| 1.9.9 Objective: The Medium Power antenna coupler shall provide 50Ω output impedance to antenna. | ||||
| Specification Section 1.10 - High Power Antenna Requirements | ||||
| 1.10.1 The High Power antenna coupler shall cover the operating frequency of the transceiver. | ||||
| 1.10.2 The High Power antenna coupler shall be capable of maximum rated peak envelope power at a 100% duty cycle at rated power throughout the transceiver’s frequency spectrum. | ||||
| 1.10.3 The High Power antenna coupler shall be BIT compatible allowing faults to be detected and then displayed on the RCU and Transceiver. | ||||
| 1.10.4 Objective: The High Power Antenna Coupler shall be BIT compatible allowing faults to be detected and relayed on IPV4 interface. | ||||
| 1.10.5 Objective: The High Power Antenna Coupler shall be BIT compatible allowing faults to be detected and relayed on IPV6 interface. | ||||
| 1.10.6 The High Power antenna coupler shall include built in overvoltage protection to protect HFRS from lightning strikes. | ||||
| 1.10.7 The manufacturer supplied hardware shall allow power efficient coupling capability with the Coast Guard grounded whip antenna throughout the transceiver operating frequency range with a maximum voltage standing wave ratio (VSWR) of 2.0:1. | ||||
| 1.10.8 The manufacturer supplied hardware shall allow power efficient coupling capability with the Coast Guard grounded Light Weight Communications Antenna (LWCA) FAN antenna throughout the transceiver operating frequency range with a maximum voltage standing wave ratio (VSWR) of 2.0:1. | ||||
| 1.10.9 The High Power antenna coupler shall provide 50Ω output impedance to antenna. | ||||
| Specification Section 1.11 - Pre/Post Selector Requirements (All proposed variants) | ||||
| 1.11.1 The Pre/Post Selector shall cover the frequency range of the transceiver. | ||||
| 1.11.2 The Pre/Post Selector shall be capable of up to 1kW (peak envelope power) at 100% duty cycle at rated power throughout the transceiver’s frequency spectrum. | ||||
| 1.11.3 The Pre/Post Selector shall have a visual power indicator on front panel. | ||||
| 1.11.4 Objective: The Pre/Post Selector shall have operator adjustable intensity of front panel indicators. | ||||
| 1.11.5 The Pre/Post Selector shall be capable of automatic (upon equipment power on) built-in test (BIT) that encompasses all hardware modules by identifying faults to the lowest repairable unit. | ||||
| 1.11.6 The Pre/Post Selector shall be BIT compatible allowing faults to be detected and then displayed on the RCU and Transceiver. | ||||
| 1.11.7 Objective: The Pre/Post Selector shall be BIT compatible allowing faults to be detected and relayed on IPV4 interface. | ||||
| 1.11.8 Objective: The Pre/Post Selector shall be BIT compatible allowing faults to be detected and relayed on IPV6 interface. | ||||
| Specification Section 1.12 - Power Supply Requirements (All proposed variants) | ||||
| 1.12.1 If applicable, the HFRS power supply/s shall have a power factor correction greater than 95%. | ||||
| Specification Section 1.13 - Installation Hardware and Cabling Requirements | ||||
| 1.13.1 The HFRS power/signal cables shall be low smoke and zero halogen compliant in accordance with MIL-DTL-24643B. | ||||
| 1.13.2 The HFRS RF cables shall be low smoke and zero halogen compliant in accordance with MIL-DTL-17H. | ||||
| Specification Section 1.14 - Microphone Requirements | ||||
| 1.14.1 The HFRS shall include a compatible microphone for use with the transceiver. | ||||
| 1.14.2 The HFRS shall include a compatible microphone for use with the RCU. | ||||
| 1.14.3 The HFRS microphone shall have Push-to-Talk (PTT) capabilities. | ||||
| 1.14.4 Objective: The HFRS microphone shall be interchangeable between the Transceiver and RCU. | ||||
| Specification Section 1.15 - Speaker Requirements | ||||
| 1.15.1 The HFRS shall include an internal speaker with volume control. | ||||
| 1.15.2 The HFRS shall include an external speaker with independent volume control. | ||||
| Specification Section 1.16 - Shipboard Component Interface Requirements | ||||
| 1.16.1 The HFRS transceiver shall comply with the IDD; Attachment #3 | ||||
| 1.16.1.1 The HFRS transceiver shall provide transmit audio interface/s in accordance with IDD. | ||||
| 1.16.1.2 The HFRS transceiver shall provide receive audio interface/s in accordance with IDD. | ||||
| 1.16.1.3 The HFRS transceiver shall provide Key Line (PTT) interface/s in accordance with IDD. | ||||
| 1.16.1.4 The HFRS transceiver shall provide RF interface/s in accordance with IDD. | ||||
| 1.16.2 The HFRS receiver shall comply with the IDD. | ||||
| 1.16.2.1 The HFRS receiver shall provide receive audio interface/s in accordance with IDD. | ||||
| 1.16.2.2 The HFRS receiver shall provide RF interface/s in accordance with IDD. | ||||
| Specification Section 1.17 - Environmental Requirements | ||||
| 1.17.1 Operating environment: The HFRS shall meet performance requirements during the applicable marine operating environments. | ||||
| 1.17.1.1 ‘Sheltered’ indicates that the equipment is in an enclosed compartment and will not be exposed to the outside weather. | ||||
| 1.17.1.2 ‘Controlled’ indicates that the environment in the compartment will be controlled and regulated. | ||||
| 1.17.1.3 ‘Uncontrolled’ indicates that the equipment will be in an uncontrolled environment and exposed to weather elements. The bridge of the ship will be considered ‘uncontrolled’ space due to its open-door exposure to the outside weather. | ||||
| 1.17.1.4 ‘Isolated’ indicates that the equipment will be housed in a shock isolated, EMI protected cabinet. | ||||
| 1.17.2 The following equipment shall meet requirements in Table 2: sheltered, controlled and isolated environment mounted to the deck, desktop, rack, or bulkhead: transceivers, receivers, and RCUs. Environmental compliance criteria denoted as ‘Note in Response’ is required and compliance/test parameters shall be included for evaluation as part of the technical proposal. | ||||
| 1.17.3 The following equipment shall be meet requirements in Table 3: sheltered and uncontrolled environment mounted to the deck, desktop, rack, or bulkhead: LPAs and Pre/Post Selectors. Environmental compliance criteria denoted as ‘Note in Response’ is required and compliance/test parameters shall be included for evaluation as part of the technical proposal. | ||||
| 1.17.4 The following equipment shall meet the requirements in Table 4: un-sheltered environment (exposed to the weather) mounted on the deck, super structure or mast: antenna couplers (all). Environmental compliance criteria denoted as ‘Note in Response’ is required and compliance/test parameters shall be included for evaluation as part of the technical proposal. | ||||
| Table 2 Sheltered, Controlled, and Isolated Equipment | ||||
| DESCRIPTION | OPERATING | NON-OPERATING (STORAGE) | SUGGESTED VERIFICATION1 | |
| TEMPERATURE | +10 TO +35°C | –20 TO 49°C | TAILORED MIL-STD-810H, METHOD 501.7 AND 502.7 | |
| HUMIDITY | 80 % RH (NON-COND.) | 90% RH (NON-COND.) | TAILORED MIL-STD-810H METHOD 507.6 | |
| SHOCK | NOTE IN RESPONSE | NOTE IN RESPONSE | TAILORED MIL-STD-810H, METHOD 516.8 (Half-Sine, TP Sawtooth, SRS, TWR) | |
| VIBRATION | NOTE IN RESPONSE | NOTE IN RESPONSE | MIL-STD-167, TYPE I / TAILORED MIL-STD-810H, METHOD 514.8 | |
| RAIN (DRIP) | NOTE IN RESPONSE | NOTE IN RESPONSE | MIL-STD-810H, METHOD 506.6 PROCEDURE III | |
| Table 3 Sheltered and Uncontrolled Equipment | ||||
| DESCRIPTION | OPERATING | NON-OPERATING (STORAGE) | SUGGESTED VERIFICATION1 | |
| TEMPERATURE | +10 TO +35°C | –20 TO 49°C | TAILORED MIL-STD-810H, METHOD 501.7 AND 502.7 | |
| HUMIDITY | 80 % RH (NON-COND.) | 90% RH (NON-COND.) | TAILORED MIL-STD-810H METHOD 507.6 | |
| SHOCK | NOTE IN RESPONSE | NOTE IN RESPONSE | TAILORED MIL-STD-810H, METHOD 516.8 (Half-Sine, TP Sawtooth, SRS, TWR) | |
| VIBRATION | NOTE IN RESPONSE | NOTE IN RESPONSE | MIL-STD-167, TYPE I / TAILORED MIL-STD-810H, METHOD 514.8 | |
| RAIN (DRIP) | NOTE IN RESPONSE | NOTE IN RESPONSE | MIL-STD-810H, METHOD 506.6 PROCEDURE III | |
| Salt Fog (Objective) | NOTE IN RESPONSE | NOTE IN RESPONSE | MIL-STD-810F, METHOD 509.7 | |
| Table 4 Unsheltered Equipment | ||||
| DESCRIPTION | OPERATING | NON-OPERATING (STORAGE) | SUGGESTED VERIFICATION1 | |
| TEMPERATURE | +10 TO +35°C | –20 TO 49°C | TAILORED MIL-STD-810H, METHOD 501.7 AND 502.7 | |
| HUMIDITY | 80 % RH (NON-COND.) | 90% RH (NON-COND.) | TAILORED MIL-STD-810H METHOD 507.6 | |
| SHOCK | NOTE IN RESPONSE | NOTE IN RESPONSE | TAILORED MIL-STD-810H, METHOD 516.8 (Half-Sine, TP Sawtooth, SRS, TWR) | |
| VIBRATION | NOTE IN RESPONSE | NOTE IN RESPONSE | MIL-STD-167, TYPE I / TAILORED MIL-STD-810H, METHOD 514.8 | |
| RAIN (Rain and Blowing Rain) | NOTE IN RESPONSE | NOTE IN RESPONSE | MIL-STD-810H, METHOD 506.6 PROCEDURE I | |
| Salt Fog (Objective) | NOTE IN RESPONSE | NOTE IN RESPONSE | MIL-STD-810H, METHOD 509.7 | |
| ICING | NOTE IN RESPONSE | NOTE IN RESPONSE | MIL-STD-810H, METHOD 521.4 | |
| SOLAR RADIATION | NOTE IN RESPONSE | NOTE IN RESPONSE | MIL-STD-810H, METHOD 505.7 PROCEDURE II | |
| Specification Section 1.18 - Electromagnetic Emissions and Susceptibility Requirements | ||||
| 1.18.1 The HFRS equipment shall meet applicable electromagnetic emissions susceptibility requirements in accordance with MIL-STD-461F. For shipboard emissions compliance, refer to specific requirements below: | ||||
| 1.18.1.1 The HFRS Transceiver shall comply with MIL-STD-461F: Sections CE102, CS101, CS114, RE101, RE102, RS101, and RS103. | ||||
| 1.18.1.2 The HFRS Receiver shall comply with MIL-STD-461F: Sections CE102, CS101, CS114, RE101, RE102, RS101, and RS103. | ||||
| 1.18.1.3 The HFRS couplers shall comply with MIL-STD-461F: Sections CS114, RE101, RE102, RS101 and RS103. | ||||
| Specification Section 1.19 - Identification and Labeling Requirements | ||||
| 1.19.1 Equipment shall be identified and labeled as per Attachment #2 packaging and marking instructions. | ||||
| 1.19.2 Equipment shall be identified and labeled in accordance with MIL-STD-15024F. | ||||
| Specification Section 1.20 - Vendor Data Requirements | ||||
| 1.20.1 Technical Data (TD): This section defines the requirements for the Vendor to provide TD necessary to integrate the Vendor’s equipment into the design of Coast Guard Cutters. The Vendor’s TD shall include the following: | ||||
| 1.20.1.1 The contractor shall provide technical documentation describing installation, operation, data communication, data rights, and maintenance of the HFRS that meets the requirements in Exhibit 1 Technical Manual Contract Requirement (TMCR). | ||||
| 1.20.1.2 A unique assembly part number, nomenclature, serial number, and original equipment manufacturer Commercial and Government Entity Code (CAGE) Code for each repairable subassembly. | ||||
| 1.20.1.3 The contractor shall provide Interface Design Description (IDD) detailing all subassembly interfaces and external connections. | ||||
| 1.20.1.4 Documented overall component and system weight. | ||||
| 1.20.1.5 Electrical schematic of each power and data circuit. | ||||
| 1.20.1.6 Manual, technical publication, and/or catalogue data detailing the installation requirements for each piece of equipment. | ||||
| 1.20.1.7 Operator’s Manual. | ||||
| 1.20.1.8 Software Manual. | ||||
| 1.20.1.9 Recommended preventative maintenance periodicity and procedures at the Operational (field) level. | ||||
| 1.20.1.10 Objective: Illustrated Parts Breakdown - Identify parts associated with the equipment. An exploded illustrated parts breakdown shall show the location of the parts. The parts list shall identify the piece part of the illustration, quantity installed, nomenclature, designation, original manufacturer and manufacturer’s part number. Part numbers are not required for common hardware available from multiple sources, if adequate descriptive data is provided. Parts data listed in the technical manual shall be the same as listed on the hierarchical listing. If metric system components are provided, they shall be so noted. | ||||
| 1.20.1.11 The system parts stock list. | ||||
| 1.20.1.12 All special tools and list of test equipment required to maintain and repair the end item. If not common tools or equipment available from multiple sources, a supply source shall be provided. | ||||
| 1.20.1.13 A list of all software/licenses needed to accomplish diagnostic testing. If not common software/licenses available from multiple sources, a supply source shall be provided. | ||||
| 1.20.1.14 Technical Manuals/Publications shall: | ||||
| 1.20.1.14.1 Completely describe the end item, end item’s equipment and/or piece parts as well as material, mechanical, electrical, dimensional characteristics, location, and their function within the assembly. | ||||
| 1.20.1.14.2 Include theory of operation, equipment and component set points and related technical information. | ||||
| 1.20.1.14.3 Include the following procedures to be carried out at the Operational (field) level: disassembly, lay-up procedures, component repair and maintenance instructions, troubleshooting guide. | ||||
| 1.20.1.14.4 Include parts schematic/line diagrams, and complete drawings and diagrams. | ||||
| 1.20.1.14.5 Be in accordance with TS 086, SFLC Standards specification 0860. | ||||
| 1.20.1.14.6 Provide to the Government in unlocked and editable PDF format all technical manuals/publications. | ||||
| 1.20.1.15 Data Submission Format: Drawings shall be submitted as electronic media. Electronic media shall be in AutoCAD and at least Version 2009 or later. Where electronic media is submitted, it shall be with the manufacturer’s permission to use the data on Coast Guard drawings. Text files shall be provided in MICROSOFT WORD. Spreadsheets shall be provided in MICROSOFT EXCEL. Documentation supplied as electronic media shall be one (1) copy. | ||||
| 1.20.1.16 Any changes to components or subassembly part numbers shall be accompanied by all necessary version change documentation to the COR within 60 days of the component change. All TD requirements shall be met by the revised documentation. | ||||
| Specification Section 1.21 - Onboard Repair Parts Listing | ||||
| 1.21.1 The Vendor shall provide a recommended onboard repair parts (OBRP) list. | ||||
| 1.21.1.1 OBRP consist of all items required to conduct 1 year’s worth of OEM recommended maintenance that unit personnel can perform without additional special tools or technical support. Typical onboard spare parts include filters, bulbs, belts, and other general consumable items. | ||||
| 1.21.2 The Vendor shall supply the following for each item in the OBRP list: the OEM part number, CAGE Code, part description, National Stock Numbers for parts already identified in the Federal Stock System, shelf life, special material/operating requirements, quantity, estimated retail cost. | ||||
| Specification Section 1.22 - System Stock Parts | ||||
| 1.22.1 The Vendor shall provide a recommended system stock parts list spreadsheet. System stock parts are defined as material with delivery lead times over 45 days and manufacturer designated critical items. The system stock parts list shall be provided after contract award and shall include the OEM part number, CAGE Code, part description, National Stock Numbers for parts already identified in the Federal Stock System, shelf life, special material/operating requirements, quantity, individual part retail cost and complete list cost. The Government reserves the right to order part quantities less than or greater than the Vendor provided parts list. | ||||
| Specification Section 1.23 - Provisioning Quality Control |
This is the start of the file's text. The full file is on GovTribe.
File details come from the government source that posted it. Updated .