Amendment 00002 - Attachment 2 HFRS Specification-07272021_clean.pdf
PDF 14 MB Posted
- Attached to
- High Frequency Radio System (HFRS)
- Solicitation number
- 70Z04421R21000900
About this file
This document is a combined synopsis and solicitation for a high frequency radio system. The U.S. Coast Guard seeks proposals for a single-award indefinite delivery/indefinite quantity contract to provide a high frequency radio system over ten years. Interested offerors must submit proposals through the Department of Defense's Safe Access File Exchange by June 14, 2021 at 11:00 AM Eastern. The system will be delivered to the U.S. Coast Guard C3CEN in Portsmouth, Virginia to facilitate integration testing. Price schedules, specifications, delivery requirements and additional terms are provided in attachments to the solicitation. Offerors must represent their size standard and certifications through the System for Award Management or by completing paragraphs C through U of provision 52.212-3 included as an attachment. Questions are due by May 21, 2021 and will be answered through an amendment posted to Sam.gov.
View the file
Other files
Show all 24
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
REVISION NO. 6 – 07/27/2021 . Amendment 00002 to RFP 70Z04421R21000900
High Frequency Radio System
SPECIFICATION
USCG C5ISC Portsmouth – High Frequency Radio System
Table of Contents
1 SCOPE
2 BACKGROUND
3 APPLICABLE DOCUMENTS
3.3 Specifications, Military
3.4 Standards, Military
3.5 Standardized Agreements
3.6 Other Government Documents
3.7 Commercial Documents
4 REQUIREMENTS
4.1 General Requirements
4.2 Transceiver Requirements
4.3 Receiver Requirements
4.4 Remote Control Unit (RCU) Requirements
4.5 Low Power Linear Power Amplifier Requirements
4.6 Objective: Medium Power Linear Power Amplifier Requirements
4.7 High Power Linear Power Amplifier Requirements
4.8 Low Power Antenna Coupler Requirements
4.9 Objective: Medium Power Antenna Coupler Requirements
4.10 High power Antenna Coupler Requirements
4.11 Pre/Post Selector Requirements (All proposed variants)
4.12 Power Supply Requirements (All proposed variants)
4.13 Installation Hardware and Cabling Requirements
4.14 Microphone Requirements
4.15 Speaker Requirements
4.16 Joint Interoperability Test Command (JITC) Requirements ......................... Error! Bookmark not defined.
4.17 Environmental Requirements
4.18 Electromagnetic Emissions and Susceptibility Requirements
4.19 Identification and Labeling Requirements
4.20 Vendor Data Requirements
4.21 Onboard Repair Parts Listing
4.22 System Stock Parts
4.23 Provisioning Quality Control
5 QUALITY ASSURANCE
6 ABBREVIATIONS AND ACRONYMS
1 SCOPE
2 BACKGROUND
3 APPLICABLE DOCUMENTS
4 REQUIREMENTS
The HFRS system specifications contain requirements identified as “Objective.” These requirements are the preferred system capabilities. All other specifications contained herein are the minimum required specifications.
Electrical
Mechanical
Table 1: Platform Configurations
(Total Configuration Max height/Depth and Total Configuration Max Weight removed by RFP Amendment 00002)
Configuration 1 (FRC 154’)
(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) Multi-coupler, (2) Low power Antenna Couplers,
(1) NVIS ATU Coupler
Configuration 2 (WMEC 210’)
(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
Standalone Receiver
(5) Multi-channel receivers
49U/26”
382.2 lbs. + 5% = 401.3lbs.
Configuration 3 (WMEC 270’)
(2) Low and (2) High 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
Standalone Receiver
(6) Multi-channel receivers
70U/26”
795.2 lbs. + 3% = 819.1 lbs.
Configuration 4 (WMEC 282’)
(3) Low & (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
Standalone Receiver
(5) Multi-channel receivers
64U/26”
529.8 lbs. + 3% = 545.7 lbs.
Configuration 5 (WAGB 399’)
(1) Low & (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
Standalone Receiver
(10) Multi-channel receivers
95U/26”
1364.7 lbs. + 2% = 1392 lbs.
Configuration 5 (WAGB 420’)
(1) Low & (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
Standalone Receiver
(4) Multi-channel receivers
77U/26”
1124.7 lbs. + 2% = 1147 lbs.
Configuration 6 (WTGB 140’)
(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
Standalone Receiver
(1) Multi-channel receiver
13U/26”
208 lbs. + 5% = 218.4 lbs.
Configuration 7 (WLM 175’)
(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
8U/26” 92 lbs. + 5% = 96.6 lbs.
Configuration 8 (WLB 225’)
(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
Standalone Receiver
(2) Multi-channel receivers
22U/26”
316 lbs. + 5% = 331.8 lbs.
Configuration 9 (WLBB 240’)
(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
Standalone Receiver
(2) Multi-channel receivers
29U/26”
372 lbs. + 5% = 390.6 lbs.
Configuration 10 (WIX 295’)
(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
Standalone Receiver
(3) Multi-channel receivers
28U/26”
483 lbs. + 5% = 507.15 lbs.
Table 2: Sheltered, Controlled, and Isolated Environment
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 NOT SPECIFIED NOT SPECIFIED TAILORED MIL-STD-810H, METHOD 516.8
(Half-Sine, TP Sawtooth, SRS, TWR)
VIBRATION NOTE SPECIFIED NOT SPECIFIED MIL-STD-167, TYPE I / TAILORED MIL-STD-
810H, METHOD 514.8
RAIN
(DRIP) NOT SPECIFIED NOT SPECIFIED MIL-STD-810H, METHOD 506.6 PROCEDURE III
Table 3: Sheltered and Uncontrolled Environment
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 NOT SPECIFIED NOT SPECIFIED TAILORED MIL-STD-810H, METHOD 516.8
(Half-Sine, TP Sawtooth, SRS, TWR)
VIBRATION NOT SPECIFIED NOT SPECIFIED MIL-STD-167, TYPE I / TAILORED MIL-STD-
810H, METHOD 514.8
RAIN
(DRIP) NOT SPECIFIED NOT SPECIFIED MIL-STD-810H, METHOD 506.6 PROCEDURE III
SALT FOG
(Objective) NOT SPECIFIED NOT SPECIFIED MIL-STD-810F, METHOD 509.7
Table 4: Unsheltered Environment
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 NOT SPECIFIED NOT SPECIFIED
TAILORED MIL-STD-810H, METHOD 516.8
(Half-Sine, TP Sawtooth, SRS, TWR)
VIBRATION NOT SPECIFIED NOT SPECIFIED MIL-STD-167, TYPE I / TAILORED MIL-STD-
810H, METHOD 514.8
RAIN
(DRIP) NOT SPECIFIED NOT SPECIFIED MIL-STD-810H, METHOD 506.6 PROCEDURE III
SALT FOG
(Objective) NOT SPECIFIED NOT SPECIFIED MIL-STD-810F, METHOD 509.7
ICING NOT SPECIFIED NOT SPECIFIED MIL-STD-810H, METHOD 521.4
SOLAR
RADIATION NOT SPECIFIED NOT SPECIFIED MIL-STD-810H, METHOD 505.7
PROCEDURE II
4.20.1.4.1.1 Operator Manuals shall have Safety Instructions
4.20.1.4.1.2 Operator Manuals shall completely describe the end item, end item’s equipment and/or piece parts as well as material, mechanical, electrical, dimensional and weight characteristics, location, and their function within the assembly.
4.20.1.4.1.3 Operator Manuals shall include theory of operation, equipment and component set points and related technical information.
4.20.1.4.1.4 Operator Manuals shall include schematic/line
diagrams, and complete drawings and functional block diagrams. For troubleshooting purposes.
4.20.1.4.2.1 Maintenance Manuals shall have recommended
preventative maintenance periodicity and procedures at the Operational (field) level.
4.20.1.4.2.2 Maintenance Manuals shall include the following
procedures to be carried out at the Operational (field) level: disassembly, component repair and maintenance instructions, troubleshooting guide.
4.20.1.4.2.3 Maintenance Manuals shall include a list of required tools to preform maintenance.
4.20.1.4.3.1 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.
5 QUALITY ASSURANCE
Vendor shall maintain an inspection system which shall ensure that each item offered to the Coast
Guard for acceptance or approval conforms to the contract requirements. The inspection system shall be documented and available for review by the Coast Guard upon request. The Vendor shall maintain an inspection system which shall ensure that each item offered to the Coast Guard for acceptance or approval conforms to the contract requirements. The inspection system shall be documented and available for review by the Coast Guard upon request.
6 ABBREVIATIONS AND ACRONYMS
The abbreviations and acronyms used in this document are defined below.
AES Advanced Encryption Standard ALE Automatic Link Establishment AM Amplitude Modulation ANSI Ame ATU Antenna Tuning Unit BIT Built In Test Bps bits per second C5ISC Command, Control, Communications, Computers, Cyber &
Intelligence Service Center CAGE Commercial and Government Entity Code CEUT Communication End User Terminals CG Coast Guard CMS Communications Management Systems COMDTINST Commandant’s Instruction COR Contracting Officers Representative COTS Commercial off the Shelf CW Continuous Waveform DHS Department of Homeland Security DoD Department of Defense DODISS Department of Defense Index of Specifications and Standards DVL Digital Voice Logger DVP Digital Voice Privacy EA Enterprise Architecture EDMO Enterprise Data Management Office EIA Electronic Industries Alliance EMI Electro Magnetic Interference FIPS Federal Information Processing Standards FSK Frequency Shift Keying HF High Frequency HFRS High Frequency Radio System HMI Human Machine Interface
HW/SW Hardware / Software Hz Hertz IAW In accordance with IDD Interface Design Description IP Internet Protocol IA Information Assurance ISB Independent Sideband IT Information Technologies JITC Joint Interoperability Test Command Kbps kilobits per second kHz kilohertz KO Contracting Officer kW Kilowatt LPA Linear Power Amplifier LSB Lower Sideband MF Medium Frequency MHz Megahertz MIL-STD Military Standard MTBF Mean Time Between Failure MTTR Mean Time To Repair NATO North Atlantic Treaty Organization NFPA National Fire Protection Association NILE NATO Improved Link Eleven NIST National Institute of Standards and Technology NSA National Security Agency NSI National Security Information NVIS Near Vertical Incidence Sky-wave OBRP Onboard Repair Parts OEM Original Equipment Manufacture OMB Office of Management and Budget PSK Phase Shift Keying PTT Push-To-Talk PUB Publication PWS Performance Work Statement
QA Quality Assurance Qty Quantity RCU Remote Control Unit RF Radio Frequency RFCB Radio Frequency Communications Branch SDR software defined radio SFLC Surface Forces Logistics Center SIMOPS Simultaneous Operations SOW Statement of Work STANAG Standardization NATO Agreement TADIL Tactical Digital Information Link TCP/IP Transition Control Protocol / Internet Protocol TD Technical Data TP Technical Publications TRM Technical Reference Model USB Upper Sideband USCG United States Coast Guard VAC Volt Alternating Current VSWR Voltage Standing Wave Ratio W Watt WBHF Wide Band HF
| 1 SCOPE |
| 1.1 The purpose of this Specification is to acquire the Next Generation HF Radio System (HFRS) components to replace legacy radio systems aboard USCG Large cutters, defined as greater than 110’ in length, and shore facility installations necessary for... |
| 2 BACKGROUND |
| 2.1 In order to maintain long haul high frequency (HF) communications aboard certain classes of cutters, the United States Coast Guard has a requirement to replace HF radio transceiver systems that are at end of life. The age of the systems, lack of a... |
| 3 APPLICABLE DOCUMENTS |
| 3.1 The documents in this section form a part of this Specification to the extent specified herein. The documents listed are by title unless otherwise documented. Commercial documents may be listed in the Department of Defense Index of Specifications ... |
| 3.2 Order of Precedence: In the event of a conflict between the text of this Specification and the references cited herein, this Specification takes precedence. The Vendor shall notify the Contracting Officer (KO) in writing for a resolution of any am... |
| 3.3 Specifications, Military |
| 3.3.1 MIL-DTL-15024F; Detail Specification: Plates, Tags and Bands for Identification of Equipment, General Specification for 1997 |
| 3.3.2 MIL-DTL-24643B; Detail Specification: General Specification for Shipboard Use for Cables and Cords, Electric, Low Smoke, |
| 3.3.3 MIL-DTL-17H; Detail Specification: General Specification for Cables, Radio Frequency, Flexible and Semi rigid |
| 3.4 Standards, Military |
| 3.4.1 MIL-STD-1399, Section 300B, Electric Power, Alternating Current |
| 3.4.2 MIL-STD-188-141D: Interoperability and Performance Standards for Medium and High Frequency Radio Systems |
| 3.4.3 MIL-STD-188-110D: Interoperability and Performance Standards for Data Modems |
| 3.4.4 MIL-STD-461F: Requirements for the Control of Electromagnetic Interference Characteristics of Subsystems and Equipment |
| 3.4.5 MIL-STD-810H: Environmental Engineering Considerations and Laboratory Test |
| 3.4.6 MIL-STD-188-203-1A: Interoperability and Performance Standards for Tactical Digital Information Link (TADIL) A |
| 3.5 Standardized Agreements |
| 3.5.1 STANAG 4203: Technical Standards for Single Channel HF Radio Equipment |
| 3.5.2 STANAG 4285: Characteristics of 1200 / 2400 / 3600 Bits per Second Single Tone Modulators / Demodulators for HF Radio Links |
| 3.5.3 STANAG 4529: Characteristics of Single Tone Modulators / Demodulators for Maritime HF Radio Links with 1240 Hz Bandwidth |
| 3.5.4 STANAG 4538: Technical Standards for an Automatic Radio Control System (ARCS) for HF Communication Links |
| 3.5.5 STANAG 4539: HF data waveforms for data rates above 2400 bps in 3 kHz channels |
| 3.5.6 STANAG 4415: Characteristics of a Robust, Non-Hopping, Serial Tone Modulator/Demodulator for Severely Degraded HF Radio Links |
| 3.5.7 STANAG 5066: Profile for Maritime High Frequency (HF) Radio Data Communication |
| 3.5.8 STANAG 5511: Tactical Data Exchange - Link 11/11B |
| 3.5.9 STANAG 5522: NATO Improved Link Eleven (NILE) - Link 22 |
| 3.6 Other Government Documents |
| 3.6.1 SFLC TS 0860, TS 086, SFLC Standards specification 086, Technical Publications (TP) |
| 3.6.2 NIST Special Publication 500-267: A Profile for IPv6 in the US Government V1.0 |
| 3.6.3 NIST Special Publication 800-53: Security and Privacy Controls for Federal Information Systems and Organizations |
| 3.7 Commercial Documents |
| 3.7.1 AES FIPS PUB 197: Advanced Encryption Standard (AES) |
| 3.7.2 AES FIPS PUB 140-2: Security Requirements for Cryptographic Modules |
| 3.7.3 National Electric Code NFPA 70, 2017 edition |
| 4 REQUIREMENTS |
| 4.1 General Requirements |
| 4.1.1 The HFRS shall be compliant with MIL-STD-188-141D. |
| 4.1.2 The HFRS shall be compliant with MIL-STD-188-110D. |
| 4.1.3 The HFRS shall be comprised of commercial-off-the-shelf (COTS) products, available for immediate purchase in the United States of America. |
| 4.1.4 The HFRS shall be scalable, consisting of a combination of HF transceivers, receivers, RCU, low power Linear Power Amplifiers (LPA) and couplers, high power LPA’s and couplers, power supplies and conditioners, mating connectors, and any other ha... |
| 4.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. |
| 4.1.6 The HFRS shall interface with external National Security Agency (NSA) Type I encryption devices for voice and data communications. |
| 4.1.7 The HFRS shall interface with external Type III encryption devices for voice and data communications. |
| 4.1.8 The HFRS shall interface with third party Communications Management Systems (CMS) for system controls. |
| 4.1.9 The HFRS shall interface with third party Communications Management Systems (CMS) for external input audio. |
| 4.1.10 The HFRS shall interface with third party Communications Management Systems (CMS) for external output audio. |
| 4.1.11 The HFRS shall interface with third party Communications Management Systems (CMS) for input data. |
| 4.1.12 The HFRS shall interface with third party Communications Management Systems (CMS) for output data |
| 4.1.13 The HFRS shall interface with third party Communications Management Systems (CMS) for Keyline/PTT (Push-to-Talk). |
| 4.1.14 The HFRS shall interface with switch board matrices for external input audio. |
| 4.1.15 The HFRS shall interface with switch board matrices for external output audio. |
| 4.1.16 Objective: The HFRS shall interface with switch board matrices for external input data. |
| 4.1.17 Objective: The HFRS shall interface with switch board matrices for external output data. |
| 4.1.18 The HFRS shall interface with switch board matrices for Keyline/PTT. |
| 4.1.19 The HFRS shall provide an interface to use external time standard reference. |
| 4.1.20 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. |
| 4.1.21 Objective: Components of the HFRS shall be offered and supported by the same manufacturer. |
| 4.1.22 Objective: The HFRS shall comply with NATO Technical Standards for Single Channel HF Radio Equipment in accordance with STANAG 4203. |
| 4.1.23 The HFRS shall be cyber security compliant in accordance with NIST SP 800-53. (requirement 4.1.23 removed by RFP Amendment 00001) |
| 4.1.24 The 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. |
| 4.1.25 The HFRS equipment shall be shipboard electrical power compliant in accordance with MIL-STD-1399, Section 300B. |
| 4.1.26 The HFRS shall be mountable into standard, 19- inch ANSI/EIA-310-D enclosures. |
| 4.1.27 The proposed HFRS equipment shall be based off of current platform specific configurations in accordance with Table 1. (requirement 4.1.27 revised by RFP Amendment 00002) |
| 4.1.28 Note: All couplers are included in the Total Configuration Max Weight, but will not be installed in the rack. (requirement 4.1.28 removed by RFP Amendment 00002) |
| 4.2 Transceiver Requirements |
| 4.2.1 The HFRS shall be able to exchange communications on multiple transceiver circuits to support simultaneous operations (SIMOPS) for operation in a co-sited environment in accordance with MIL-STD-188-141D, Appendix F. SIMOPS is defined as the use ... |
| 4.2.2 The HFRS transceiver shall have an operating frequency range of, at a minimum, 1.5 MHz – 30 MHz. |
| 4.2.3 The HFRS transceiver frequency shall be adjustable in 10 Hz increments. |
| 4.2.4 The HFRS transceiver shall be compatible with existing 2G ALE networks in accordance with MIL-STD-188-141D Appendix A. |
| 4.2.5 The HFRS transceiver shall be 3G ALE capable in accordance with MIL-STD-188-141D Appendix C. |
| 4.2.6 Objective: The HFRS transceiver shall be 4G ALE capable in accordance with MIL-STD-188-141D Appendix G. |
| 4.2.7 Objective: The HFRS transceiver shall be software/firmware upgradeable to 4G ALE IAW MIL-STD-188-141D, Appendix G. |
| 4.2.8 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. |
| 4.2.9 Objective: The HFRS transceiver data modem shall be capable of multi-channel operations in WBHF IAW MIL-STD-188-110D, Appendix D. |
| 4.2.10 Objective: The HFRS transceiver shall have an HF data modem that complies with STANAG 4285. |
| 4.2.11 The HFRS transceiver shall have an HF data modem that is upgradable, via software/firmware only, to full compatibility with WBHF MIL-STD-188-110D - Appendix D Block 4 waveforms. |
| 4.2.12 Objective: The HFRS shall exchange data via NATO robust mode in accordance with STANAG 4415. |
| 4.2.13 Objective: The HFRS shall exchange data via NATO serial tone mode in accordance with STANAG 4539. |
| 4.2.14 Objective: The HFRS transceiver data modem shall be capable of frequency-hopping (anti-jam) in accordance with MIL-STD-188-148. |
| 4.2.15 Objective: The HFRS transceiver shall be capable of ALE linking protection in accordance with MIL-STD-188-141D Appendix B. |
| 4.2.16 Objective: The HFRS transceiver shall be capable of Wideband ALE linking protection in accordance with MIL-STD-188-141D Appendix H. |
| 4.2.17 Objective: The HFRS shall have a robust modem capable of 75 bits per second (bps) in accordance with STANAG 4415. |
| 4.2.18 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. |
| 4.2.19 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. |
| 4.2.20 The HFRS transceiver shall be capable of upper sideband (USB) IAW MIL-STD-188-141D. |
| 4.2.21 The HFRS transceiver shall be capable of lower sideband (LSB) IAW MIL-STD-188-141D. |
| 4.2.22 The HFRS transceiver shall be capable of continuous waveform (CW) IAW MIL-STD-188-141D. |
| 4.2.23 The HFRS transceiver shall be capable of amplitude modulation (AM) IAW MIL-STD-188-141D. |
| 4.2.24 The HFRS transceiver shall be capable of two-channel independent sideband (2-ISB) IAW MIL-STD-188-141D. |
| 4.2.25 Capable of frequency shift keying (FSK) modes of operation within the transceiver system IAW MIL-STD-188-141D. |
| 4.2.26 The HFRS transceiver shall have HF data exchange capability IAW MIL-STD-188-141D. Data exchange values are provided inMIL-STD-188-141D Appendix A. |
| 4.2.27 Objective: The HFRS transceiver shall be compatible with HF data exchange capability in compliance with STANAG 5066. |
| 4.2.28 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. |
| 4.2.29 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. |
| 4.2.30 The HFRS transceiver shall have squelch circuitry that monitors the RF input signal to the transceiver while muting the audio output to the speakers. |
| 4.2.31 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 (LRU). The HFRS transceiver shall include a software defi... |
| 4.2.31.1 The HFRS transceiver local front panel controls shall be built into the transceiver or use a local RCU. |
| 4.2.31.2 The HFRS transceiver local front panel controls shall be built into the transceiver/s and/or use a local RCU/s. |
| 4.2.31.3 The HFRS transceiver shall have local front panel status display for receive RF signal strength. |
| 4.2.31.4 The HFRS transceiver shall have local front panel controls for Output Power with selection options for low to high power. |
| 4.2.31.5 The HFRS transceiver shall have local front panel status display for Output Power. |
| 4.2.31.6 The HFRS transceiver shall have local front panel controls for Frequency Selection. |
| 4.2.31.7 The HFRS transceiver shall have local front panel status display for Frequency Selection. |
| 4.2.31.8 The HFRS transceiver shall have local front panel controls for Modulation Selection (e.g., USB, LSB, ISB, 2-ISB, AM, CW, FSK (ALE)). |
| 4.2.31.9 The HFRS transceiver shall have local front panel status display for Modulation Selection (e.g., USB, LSB, ISB, 2-ISB, AM, CW, FSK (ALE)). |
| 4.2.31.10 The HFRS transceiver shall have a visual power indicator on front panel. |
| 4.2.31.11 The HFRS transceiver shall have local front panel controls for display intensity. |
| 4.2.31.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). |
| 4.2.31.11.2 Objective: The HFRS transceiver local front panel display shall be dimmable to 0.5 NITS (cd/m2). |
| 4.2.31.11.3 Objective: The HFRS transceiver local front panel display shall be able to be powered off, while still maintaining all required transceiver behavior. |
| 4.2.31.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. |
| 4.2.31.11.5 Objective: The HFRS transceiver local front panel display shall employ mechanical (knob/push button) backlight dimming. |
| 4.2.31.12 The HFRS transceiver shall include an internal speaker. |
| 4.2.31.12.1 The HFRS transceiver shall have local front panel control for internal speaker volume. |
| 4.2.31.12.2 The HFRS shall have local front panel status display for volume level. |
| 4.2.31.13 The HFRS shall include an external speaker with independent volume control. |
| 4.2.31.14 The HFRS shall include a compatible microphone for use with the transceiver. |
| 4.2.31.14.1 The HFRS microphone shall have PTT capabilities. |
| 4.2.31.14.2 Objective: The HFRS microphone shall be interchangeable between the Transceiver and RCU. |
| 4.2.31.15 The HFRS shall have local front panel control for Noise Filtering (Squelch). |
| 4.2.31.16 The HFRS shall have local front panel controls of ALE linking operation. |
| 4.2.31.16.1 The HFRS shall be capable of being programmed with both ALE addresses and frequencies. |
| 4.2.31.17 The HFRS shall have local front panel with status display of ALE link. |
| 4.2.31.17.1 Objective: The HFRS Transceiver shall have discernable audible alerts for ALE link established/disestablish. |
| 4.2.31.17.2 Objective: The HFRS Transceiver shall provide Link Quality Analysis (LQA) on display. |
| 4.2.32 The HFRS transceiver shall have a rear panel interface. |
| 4.2.32.1 The HFRS transceiver shall have an N-Type RF transmit/receive interface. |
| 4.2.32.2 The HFRS transceiver shall have a minimum of two external interfaces for transmit audio (balance 600-ohm, 0dbm). |
| 4.2.32.3 The HFRS transceiver shall have a minimum of two external interfaces for receive audio (balance 600-ohm, 0dbm). |
| 4.2.32.4 The HFRS transceiver shall have a minimum of two external interfaces for Keyline/PTT. |
| 4.2.32.5 The HFRS transceiver (with a built in or external modem) shall have a minimum of two input data interfaces for data exchange. |
| 4.2.32.6 Objective: The HFRS transceiver shall provide line level input audio interface (balance 600-ohm, 0dbm) for recording capabilities. |
| 4.2.32.7 Objective: The HFRS transceiver shall provide line level output audio interface (balance 600-ohm, 0dbm) for recording capabilities |
| 4.2.32.8 The HFRS transceiver shall have a Transmission Control Protocol / Internet Protocol (TCP/IP) interface that is IEEE 802.3 compliant. |
| 4.2.32.8.1 The HFRS transceiver shall be capable of full remote control via TCP/IP. |
| 4.2.32.8.2 The HFRS transceiver shall be programmable/configurable via TCP/IP. |
| 4.2.32.8.3 The HFRS transceiver shall be capable of remote operator-initiated BIT via TCP/IP interface. |
| 4.2.32.8.4 The HFRS transceiver TCP/IP addressability shall have the ability to simultaneously operate locally and remotely via PC or Server-based virtual control. |
| 4.2.32.8.5 The HFRS transceiver shall be compatible with Internet Protocol version 4 (IPv4). |
| 4.2.32.8.6 Objective: The HFRS transceiver shall utilize, or be upgradeable via software or firmware, Internet Protocol version 6 (IPv6) via software/firmware update. |
| 4.2.32.9 The HFRS transceiver shall have a serial interface that is RS232/485 compliant. |
| 4.2.32.9.1 The HFRS transceiver shall be capable of full remote control via serial interface. |
| 4.2.32.9.2 The HFRS transceiver shall be programmable/configurable via serial interface. |
| 4.3 Receiver Requirements |
| 4.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. |
| 4.3.1.1 The HFRS receiver local front panel controls shall be built into the receiver or use a local RCU. |
| 4.3.1.2 The HFRS receiver shall have local front panel status display for receive RF signal strength |
| 4.3.1.3 The HFRS receiver shall have local front panel controls for Frequency Selection. |
| 4.3.1.4 The HFRS receiver shall have local front panel status display for Frequency Selection. |
| 4.3.1.5 The HFRS receiver shall have local front panel controls for Modulation Selection (e.g., USB, LSB, ISB, 2-ISB, AM, CW). |
| 4.3.1.6 The HFRS receiver shall have local front panel status display for Modulation Selection (e.g., USB, LSB, ISB, 2-ISB, AM, CW). |
| 4.3.1.7 The HFRS receiver shall have a visual power indicator on front panel. |
| 4.3.1.8 The HFRS receiver shall have local front panel controls for display intensity. |
| 4.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). |
| 4.3.1.8.2 Objective: The HFRS receiver local front panel display shall be dimmable to 0.5 NITS (cd/m2). |
| 4.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. |
| 4.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. |
| 4.3.1.8.5 Objective: The HFRS receiver local front panel display shall employ mechanical (knob/push button) backlight dimming. |
| 4.3.1.9 The HFRS receiver shall include an internal speaker with volume control. |
| 4.3.1.9.1 The HFRS receiver shall have local front panel control for volume. |
| 4.3.1.10 The HFRS receiver shall have local front panel status display for volume level. |
| 4.3.1.11 The HFRS receiver shall have local front panel control for Noise Filtering (Squelch). |
| 4.3.1 The HFRS receiver shall have a rear panel interface. |
| 4.3.1.1 The HFRS receiver shall have an N-Type RF receive interface. |
| 4.3.1.2 The HFRS receiver shall have a minimum of two external interfaces for receive audio (balance 600-ohm, 0dbm). |
| 4.3.1.3 The HFRS receiver (with a built in or external modem) shall have a minimum of two input data interfaces for data exchange. |
| 4.3.1.4 Objective: The HFRS receiver shall provide line level input audio interface (balance 600-ohm, 0dbm) for recording capabilities. |
| 4.3.1.5 The HFRS receiver shall have a Transmission Control Protocol / Internet Protocol (TCP/IP) interface that is IEEE 802.3 compliant. |
| 4.3.1.5.1 The HFRS receiver shall be capable of full remote control via TCP/IP. |
| 4.3.1.5.2 The HFRS receiver shall be programmable/configurable via TCP/IP. |
| 4.3.1.5.3 The HFRS receiver shall be capable of remote operator-initiated BIT via TCP/IP interface. |
| 4.3.1.5.4 The HFRS receiver TCP/IP addressability shall have the ability to simultaneously operate locally and remotely via PC or Server-based virtual control. |
| 4.3.1.5.5 The HFRS receiver shall be compatible with Internet Protocol version 4 (IPv4). |
| 4.3.1.5.6 Objective: The HFRS receiver shall utilize, or be upgradeable via software or firmware, Internet Protocol version 6 (IPv6) via software/firmware update. |
| 4.3.1.6 The HFRS receiver shall have a serial interface that is RS232/485 compliant. |
| 4.3.1.6.1 The HFRS receiver shall be capable of full remote control via serial interface. |
| 4.3.1.6.2 The HFRS receiver shall be programmable/configurable via serial interface. |
| 4.3.2 The HFRS receiver shall operate from, at minimum, 20 kHz to 30 MHz with 10 Hz increments. |
| 4.3.3 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. |
| 4.3.4 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. |
| 4.3.5 The HFRS receiver shall have squelch circuitry that monitors the RF input signal while muting the audio output to the speakers. |
| 4.3.6 The HFRS receiver data modem shall be capable of a minimum of two separate output channels compatible with MIL-STD-188-110D, Appendix F. |
| 4.3.7 Objective: The HFRS receiver shall have an HF data modem compatible with WBHF MIL-STD-188-110D - Appendix D. |
| 4.3.8 Objective: The HFRS receiver shall have an HF data modem that complies with STANAG 4285. |
| 4.3.9 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. |
| 4.3.10 The HFRS receiver shall be capable of upper sideband (USB) IAW MIL-STD-188-141D. |
| 4.3.11 The HFRS receiver shall be capable of lower sideband (LSB) IAW MIL-STD-188-141D. |
| 4.3.12 The HFRS receiver shall be capable of continuous waveform (CW) IAW MIL-STD-188-141D. |
| 4.3.13 The HFRS receiver shall be capable of amplitude modulation (AM) IAW MIL-STD-188-141D. |
| 4.3.14 The HFRS receiver shall be capable of two-channel independent sideband (2-ISB) IAW MIL-STD-188-141D. |
| 4.3.15 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 (LRU). |
| 4.4 Remote Control Unit (RCU) Requirements |
| 4.4.1 The HFRS RCU shall be controlled remotely using operator friendly RCU’s or suitable PC-based interface. |
| 4.4.1.1 The HFRS RCU shall have local front panel status display for receive RF signal strength |
| 4.4.1.2 The HFRS RCU shall have controls for Output Power with selection options for low to high power. |
| 4.4.1.3 The HFRS RCU shall have status display for Output Power. |
| 4.4.1.4 The HFRS RCU shall have controls for Frequency Selection. |
| 4.4.1.5 The HFRS RCU shall have local front panel status display for Frequency Selection. |
| 4.4.1.6 The HFRS RCU shall have controls for Modulation Selection (e.g., USB, LSB, ISB, 2-ISB, AM, CW, FSK (ALE)). |
| 4.4.1.7 The HFRS RCU shall have status display for Modulation Selection (e.g., USB, LSB, ISB, 2-ISB, AM, CW, FSK (ALE)). |
| 4.4.1.8 The HFRS RCU shall have a visual power indicator on front panel. |
| 4.4.1.9 The HFRS RCU shall have controls for display intensity. |
| 4.4.1.9.1 The HFRS RCU display shall be visible at night without loss of night-vision, down to 1 NITS (cd/m2). |
| 4.4.1.9.2 Objective: The HFRS RCU display shall be dimmable to 0.5 NITS (cd/m2). |
| 4.4.1.9.3 Objective: The HFRS RCU display shall be able to be powered off, while still maintaining all required transceiver behavior. |
| 4.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. |
| 4.4.1.9.5 Objective: The HFRS RCU display shall employ mechanical (knob/push button) backlight dimming. |
| 4.4.1.10 The HFRS RCU shall include an internal speaker with volume control. |
| 4.4.1.10.1 The HFRS RCU shall have local front panel control for internal speaker volume. |
| 4.4.1.10.2 The HFRS RCU shall have status display for volume level. |
| 4.4.1.11 The HFRS RCU shall include an external speaker with independent volume control. |
| 4.4.1.12 The HFRS shall include a compatible microphone for use with the RCU. |
| 4.4.1.12.1 The HFRS microphone shall have PTT capabilities. |
| 4.4.1.12.2 Objective: The HFRS microphone shall be interchangeable between the Transceiver and RCU. |
| 4.4.1.13 The HFRS RCU’s shall have controls for Noise Filtering (Squelch). |
| 4.4.1.14 The HFRS RCU’s shall have controls of ALE linking operation. |
| 4.4.1.14.1 The HFRS RCU shall be capable of programming both ALE addresses and frequencies. |
| 4.4.1.15 The HFRS RCU’s shall have status display of ALE link. |
| 4.4.1.15.1 Objective: The HFRS RCU’s shall have discernable audible alerts for ALE link established/disestablish. |
| 4.4.1.15.2 Objective: The HFRS RCU shall provide Link Quality Analysis (LQA) on display. |
| 4.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. |
| 4.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). |
| 4.4.3.1 All RCU shall be updated with current parameters following changes on any other RCU/s. |
| 4.4.3.2 To avoid conflicts when multiple controllers are present, the system shall utilize a leader/follower (master/slave) relationship with defined procedures for passing the leader (master) role between controllers. |
| 4.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. |
| 4.4.5 The HFRS shall use common, interchangeable RCU’s. |
| 4.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 (LRU). |
| 4.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 (LRU). |
| 4.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. |
| 4.4.9 The HFRS RCU shall be Transmission Control Protocol / Internet Protocol (IP) addressable via TCP/IP interface. |
| 4.4.9.1 The HFRS RCU shall be capable of full remote control via TCP/IP. |
| 4.4.9.2 The HFRS RCU shall be capable of remote operator-initiated BIT via TCP/IP interface. |
| 4.4.9.3 The HFRS RCU shall be programmable/configurable via TCP/IP. |
| 4.4.9.4 The HFRS RCU shall be compatible with Internet Protocol version 4 (IPv4). |
| 4.4.10 The HFRS RCU shall have a serial interface. |
| 4.4.10.1 The HFRS RCU shall allow full remote control of transceiver and receiver via serial interface. |
| 4.4.10.2 The HFRS shall be programmable/configurable by using the RCU via serial interface. |
| 4.5 Low Power Linear Power Amplifier Requirements |
| 4.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. |
| 4.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). |
| 4.5.3 The Low Power LPA shall be controllable from the transceiver. |
| 4.5.4 The Low Power LPA shall be controllable from the RCU. |
| 4.5.5 The Low Power LPA shall be controllable from third party CMS. |
| 4.5.6 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 (LRU). |
| 4.5.7 The Low Power LPA shall be BIT capable allowing faults to be detected and then displayed on the RCU and Transceiver. |
| 4.5.7.1 Objective: The Low Power LPA shall be BIT compatible allowing faults to be detected and relayed on IPV4 interface. |
| 4.5.7.2 Objective: The Low Power LPA shall be BIT compatible allowing faults to be detected and relayed on IPV6 interface. |
| 4.5.8 The Low Power LPA shall have a visual power indicator on front panel or RCU |
| 4.5.9 The Low Power LPA shall have a visual hardware condition indicator on front panel or RCU. |
| 4.5.10 The Low Power LPA shall have a visual fault condition indicator on front panel or RCU. |
| 4.5.11 Objective: The Low Power LPA shall have limited power operation upon module/component failure. |
| 4.5.12 Objective: The Low Power LPA shall have operator adjustable intensity of front panel indicators. |
| 4.6 Objective: Medium Power Linear Power Amplifier Requirements |
| 4.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. |
| 4.6.2 Objective: The Medium Power LPA shall have operator selectable output level control within the range of 0-100% (0% = transmit inhibit, 100% = max power). |
| 4.6.3 Objective: The Medium Power LPA shall be controllable from the transceiver. |
| 4.6.4 Objective: The Medium Power LPA shall be controllable from the RCU. |
| 4.6.5 Objective: The Medium Power LPA shall be controllable from third party CMS. |
| 4.6.6 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 (LRU). |
| 4.6.7 Objective: The Medium Power LPA shall be BIT capable allowing faults to be detected and then displayed on the RCU and Transceiver. |
| 4.6.7.1 Objective: The Medium Power LPA shall be BIT compatible allowing faults to be detected and relayed on IPV4 interface. |
| 4.6.7.2 Objective: The Medium Power LPA shall be BIT compatible allowing faults to be detected and relayed on IPV6 interface |
| 4.6.8 Objective: The Medium Power LPA shall have a visual power indicator on front panel. |
| 4.6.9 Objective: The Medium Power LPA shall have a visual hardware condition indicator on front panel. |
| 4.6.10 Objective: The Medium Power LPA shall have a visual fault condition indicator on front panel. |
| 4.6.11 Objective: The Medium Power LPA shall have limited power operation upon module/component failure. |
| 4.6.12 Objective: The Low Power LPA shall have operator adjustable intensity of front panel indicators. |
| 4.7 High Power Linear Power Amplifier Requirements |
| 4.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. |
| 4.7.2 The High Power LPA shall have operator selectable output level control within the range of 0-100% (0% = transmit inhibit, 100% = max power). |
| 4.7.3 The High Power LPA shall be controllable from the transceiver. |
| 4.7.4 The High Power LPA shall be controllable from the RCU. |
| 4.7.5 The High Power LPA shall be controllable from third party CMS. |
| 4.7.6 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 (LRU). |
| 4.7.7 The High Power LPA shall be BIT capable allowing faults to be detected and then displayed on the RCU and Transceiver. |
| 4.7.7.1 Objective: The High Power LPA shall be BIT compatible allowing faults to be detected and relayed on IPV4 interface. |
| 4.7.7.2 Objective: The High Power LPA shall be BIT compatible allowing faults to be detected and relayed on IPV6 interface |
| 4.7.8 The High Power LPA shall have a visual power indicator on front panel. |
| 4.7.9 The High Power LPA shall have a visual hardware condition indicator on front panel. |
| 4.7.10 The High Power LPA shall have a visual fault condition indicator on front panel. |
| 4.7.11 Objective: The High Power LPA shall have limited power operation upon module/component failure. |
| 4.7.12 Objective: The High Power LPA shall have operator adjustable intensity of front panel indicators. |
| 4.8 Low Power Antenna Coupler Requirements |
| 4.8.1 The Low Power antenna coupler shall cover the operating frequency of the transceiver. |
| 4.8.2 The Low Power antenna coupler shall be capable of maximum rated peak envelope power at a 100% duty cycle in CW throughout the transceiver’s frequency spectrum. |
| 4.8.3 The Low Power antenna coupler shall be controllable from the transceiver. |
| 4.8.4 The Low Power antenna coupler shall be controllable from the RCU. |
| 4.8.5 The Low Power antenna coupler shall be controllable from third party CMS. |
| 4.8.6 The Low Power antenna coupler shall be BIT compatible allowing faults to be detected and then displayed on the RCU and Transceiver. |
| 4.8.7 Objective: The Low Power Antenna Coupler shall be BIT compatible allowing faults to be detected and relayed on IPV4 interface. |
| 4.8.8 Objective: The Low Power Antenna Coupler shall be BIT compatible allowing faults to be detected and relayed on IPV6 interface. |
| 4.8.9 The Low Power antenna coupler shall include built in overvoltage protection to protect HFRS from lightning strikes. |
| 4.8.10 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. |
| 4.8.11 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. |
| 4.8.12 The Low Power antenna coupler shall provide 50Ω output impedance to antenna. |
| 4.9 Objective: Medium Power Antenna Coupler Requirements |
| 4.9.1 Objective: The Medium Power antenna coupler shall cover the operating frequency of the transceiver. |
| 4.9.2 Objective: The Medium Power antenna coupler shall be capable of maximum rated peak envelope power at a 100% duty cycle in CW throughout the transceiver’s frequency spectrum. |
| 4.9.3 Objective: The Medium Power antenna coupler shall be controllable from the transceiver. |
| 4.9.4 Objective: The Medium Power antenna coupler shall be controllable from the RCU. |
| 4.9.5 Objective: The Medium Power antenna coupler shall be controllable from third party CMS. |
| 4.9.6 Objective: The Medium Power antenna coupler shall be BIT compatible allowing faults to be detected and then displayed on the RCU and Transceiver. |
| 4.9.7 Objective: The Medium Power Antenna Coupler shall be BIT compatible allowing faults to be detected and relayed on IPV4 interface. |
| 4.9.8 Objective: The Medium Power Antenna Coupler shall be BIT compatible allowing faults to be detected and relayed on IPV6 interface. |
| 4.9.9 Objective: The Medium Power antenna coupler shall include built in overvoltage protection to protect HFRS from lightning strikes. |
| 4.9.10 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... |
| 4.9.11 Objective: The manufacturer supplied hardware shall allow power efficient coupling capability with the Coast Guard grounded Light Weight Communications Antenna (LWCA) FAN antenna (NSN: 4010-01-387-6610) throughout the transceiver operating freq... |
| 4.9.12 Objective: The Medium Power antenna coupler shall provide 50Ω output impedance to antenna. |
| 4.10 High power Antenna Coupler Requirements |
| 4.10.1 The High Power antenna coupler shall cover the operating frequency of the transceiver. |
| 4.10.2 The High Power antenna coupler shall be capable of maximum rated peak envelope power at a 100% duty cycle in CW throughout the transceiver’s frequency spectrum. |
| 4.10.3 The High Power antenna coupler shall be controllable from the transceiver. |
| 4.10.4 The High Power antenna coupler shall be controllable from the RCU. |
| 4.10.5 The High Power antenna coupler shall be controllable from third party CMS. |
| 4.10.6 The High Power antenna coupler shall be BIT compatible allowing faults to be detected and then displayed on the RCU and Transceiver. |
| 4.10.7 Objective: The High Power Antenna Coupler shall be BIT compatible allowing faults to be detected and relayed on IPV4 interface. |
| 4.10.8 Objective: The High Power Antenna Coupler shall be BIT compatible allowing faults to be detected and relayed on IPV6 interface. |
| 4.10.9 The High Power antenna coupler shall include built in overvoltage protection to protect HFRS from lightning strikes. |
| 4.10.10 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. |
| 4.10.11 The manufacturer supplied hardware shall allow power efficient coupling capability with the Coast Guard grounded Light Weight Communications Antenna (LWCA) FAN antenna (NSN: 4010-01-387-6610) throughout the transceiver operating frequency rang... |
| 4.10.12 The High Power antenna coupler shall provide 50Ω output impedance to antenna. |
| 4.11 Pre/Post Selector Requirements (All proposed variants – if required in order to meet co-site requirements in accordance with MIL-STD-188-141D Appendix F.) |
| 4.11.1 The Pre/Post Selector shall cover the frequency range of the transceiver. |
| 4.11.2 The Pre/Post Selector shall capable of up to1kW (peak envelope power) at 100% duty cycle at rated power throughout the transceiver’s frequency spectrum. |
| 4.11.3 The Pre/Post Selector shall have a visual power indicator on front panel. |
| 4.11.4 The Pre/Post Selector shall be controllable from the transceiver. |
| 4.11.5 The Pre/Post Selector shall be controllable from the RCU. |
| 4.11.6 The Pre/Post Selector shall be controllable from third party CMS. |
| 4.11.7 Objective: The Pre/Post Selector shall have operator adjustable intensity of front panel indicators. |
| 4.11.8 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 (LRU). |
| 4.11.9 The Pre/Post Selector shall be BIT compatible allowing faults to be detected and then displayed on the RCU and Transceiver. |
| 4.11.10 Objective: The Pre/Post Selector shall be BIT compatible allowing faults to be detected and relayed on IPV4 interface. |
| 4.11.11 Objective: The Pre/Post Selector shall be BIT compatible allowing faults to be detected and relayed on IPV6 interface. |
| 4.12 Power Supply Requirements (All proposed variants) |
| 4.12.1 The HFRS power supply/s shall have a power factor correction greater than 95%. |
| 4.13 Installation Hardware and Cabling Requirements |
| 4.13.1 The HFRS power/signal cables shall be low smoke and zero halogen compliant in accordance with MIL-DTL-24643B. |
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 .