SOURCES SOUGHT
58 -- Land Mobile Radio Systems and Equipment
- Notice Date
- 4/14/2017
- Notice Type
- Sources Sought
- NAICS
- 334220
— Radio and Television Broadcasting and Wireless Communications Equipment Manufacturing
- Contracting Office
- Department of the Navy, Naval Air Systems Command, Naval Air Warfare Center Aircraft Division Lakehurst, Contracts Department, Hwy. 547 Attn:B562-3C, Lakehurst, New Jersey, 08733-5083
- ZIP Code
- 08733-5083
- Solicitation Number
- N68335-17-RFI-0227
- Archive Date
- 5/6/2017
- Point of Contact
- Evanuel Hairston, Phone: 7323232094
- E-Mail Address
-
evanuel.hairston@navy.mil
(evanuel.hairston@navy.mil)
- Small Business Set-Aside
- N/A
- Description
- Land Mobile Radio Systems and Equipment RFI Number: N68335-17-RFI-0227 Classification Code: 5820 Radio and Television Communication Equipment, Except Airborne NAICS Code(s): 334220 Radio and Television Broadcasting and Wireless Communications Equipment Manufacturing Response date - 7 days Primary Point of Contact: Evanuel Hairston evanuel.hairston@navy.mil Phone: 732 323 2094 This Sources Sought/Request For Information notice is being posted to satisfy the requirement of Defense Federal Acquisition Regulation Supplement 206-302-1(d). The Naval Air Warfare Center Aircraft Division (NAWCAD), Special Communications Mission Solutions (SCMS) Division is soliciting information and comments from industry on its ability to provide non-developmental or Commercial Off the Shelf (COTS) systems and equipment for several independent projects that require Land Mobile Radios as follows: •1. Pacific Region System The Navy requires an Enterprise Land Mobile Radio (ELMR) Master Site System with multiple Radio Frequency (RF) zone controllers. In addition to the new Master Site System, the Government seeks information regarding a Key Management Facility client, Network Management Systems, Radio Authentication, Radio Management, Dispatch Consoles, and an Internet Protocol (IP) Logging Recorder. The Master Site System will support operations on an existing US Department of Defense (DoD) network, and thus the system must comply with DoD Cybersecurity policies for Authority to Operate, and support Host Base Security Scanning. The Master Site System must be compliant with the Association of Public-Safety Communication Officials (APCO) Project 25 (P25) standards, and must be interoperable with other US Navy ELMR systems in the Pacific region that use Motorola Astro 25 based equipment. The Government seeks a system that provides immediate and assured voice, providing rapid response upon activation of the radio push-to-talk. The system will provide fully-featured, trunked communications, even after experiencing multiple points of failure. Levels of redundancy are needed to be built into the design to allow the proposed architecture to retain the greatest level of communication and the broadest scope of features in the unlikely event that a supporting subsystem or component fails. The system will provide system managers with the ability to monitor, program, diagnose, and maintain the Master Site System. Operating in a client/server environment, system management features will need to be accessible across the IP network from any Network Management (NM) client. The NM applications will align with the F ault, Configuration, Accounting, Performance, Security ( FCAPS) model by utilizing a combination of applications and interfaces. This includes web based applications such as the Unified Event Manager (UEM), Unified Network Configurator (UNC), and Provisioning Manager as well as unidirectional and bidirectional interfaces. A Key Management Facility (KMF) client will operate with the system to support Over-the-Air Rekeying (OTAR). A P25-compliant OTAR solution is required to allow key administrators to securely rekey radios from the proposed KMF client. OTAR is to eliminate the need for radios to be physically rekeyed using a Key Variable Loader (KVL) and cable. Once a rekeying update is activated on the OTAR-enabled P25 system, encrypted radios anywhere within the radio coverage area will automatically receive updated encryption keys without any disruption to ongoing communication. The system will provide immediate wireless delivery of new key material to prevent a compromised radio from accessing the P25 system over any channel, clear or encrypted. •2. Poland System The Navy requires a new RF site in Poland that will be part of an existing Enterprise Land Mobile Radio (ELMR) System that is located in Europe. This RF site is to have five UHF trunked repeaters, two redundant site controllers, and three independent bi-directional amplifiers for in-building coverage. The RF site shall have the RF equipment necessary for one tower mounted transmit antenna and one tower mounted receive antenna. The Government also seeks information regarding a Key Management Facility client, Network Management Systems, Radio Authentication, Radio Management, Dispatch Consoles, and an IP Logging Recorder for this location. The RF site equipment will support operations on an existing US Department of Defense (DoD) network, and thus the equipment must comply with DoD Cybersecurity policies for Authority to Operate, and support Host Base Security Scanning. The RF site equipment must be APCO P25 compliant, and must be interoperable with other US Navy ELMR systems in the European region that use Motorola Astro 25 based equipment. The Government seeks a system which provides immediate and assured voice, providing rapid response upon activation of the radio push-to-talk. The system will provide fully-featured, trunked communications, even after experiencing multiple points of failure. Levels of redundancy are needed to be built into the design to allow the proposed architecture to retain the greatest level of communication and the broadest scope of features in the unlikely event that a supporting subsystem or component fails. The RF site will provide system managers with the ability to remotely monitor, program, diagnose, and maintain the equipment. Operating in a client/server environment, system management features will need to be accessible across the IP network from any Network Management (NM) client. The NM applications will align with the F ault, Configuration, Accounting, Performance, Security ( FCAPS) model by utilizing a combination of applications and interfaces. This includes web based applications such as the Unified Event Manager (UEM), Unified Network Configurator (UNC), and Provisioning Manager as well as unidirectional and bidirectional interfaces. A Key Management Facility (KMF) client will operate with the system to support Over-the-Air Rekeying (OTAR). A P25-compliant OTAR solution is required at the RF site to allow key administrators to securely rekey radios from the proposed KMF client. OTAR is to eliminate the need for radios to be physically rekeyed using a Key Variable Loader (KVL) and cable. Once a rekeying update is activated on the OTAR-enabled P25 system, encrypted radios anywhere within the radio coverage area will automatically receive updated encryption keys without any disruption to ongoing communication. The system will provide immediate wireless delivery of new key material to prevent a compromised radio from accessing the P25 system over any channel, clear or encrypted. •3. Virginia Systems The Navy requires two new RF sites in Virginia that will be part of an existing Enterprise Land Mobile Radio (ELMR) System. Each of these RF sites is to have seven UHF trunked repeaters and two redundant site controllers. The RF site shall have the RF equipment necessary for two tower mounted transmit antenna and one tower mounted receive antenna. The Government also seeks information regarding a Key Management Facility client, Network Management Systems, Radio Authentication, Radio Management, Dispatch Consoles, and an IP Logging Recorder for these locations. The RF site equipment will support operations on an existing US Department of Defense (DoD) network, and thus the equipment must comply with DoD Cybersecurity policies for Authority to Operate, and support Host Base Security Scanning. The RF site equipment must be APCO P25 compliant, and must be interoperable with other US Navy ELMR systems in the US that use Motorola Astro 25 based equipment. The Government seeks a system which provides immediate and assured voice, providing rapid response upon activation of the radio push-to-talk. The system will provide fully-featured, trunked communications, even after experiencing multiple points of failure. Levels of redundancy are needed to be built into the design to allow the proposed architecture to retain the greatest level of communication and the broadest scope of features in the unlikely event that a supporting subsystem or component fails. •4. Public Safety Radios (mobile and portable) The radios shall be trunked, mobile (vehicular) and portable/handheld. The radios shall be compliant with the APCO P25 standards. The radio solution shall provide a digital Common Air Interface (CAI) and shall utilize Time Division Multiple Access (TDMA) technology to increase the quantity of channels available. The radios must include a P25 compliant Over-the-Air Rekeying (OTAR) capability and an Over-the-Air-Programming (OTAP) capability. A vehicle mount for the portable radio is required that includes a battery charger and a RF amplifier; this mount should permit "grab and go" of the portable radio. RESPONSES Requested Information Section 1 of the response shall provide administrative information, and shall include the following as a minimum: Organization name, mailing address, overnight delivery address (if different from mailing address), phone number, fax number, and name and e-mail of designated point of contact. •· Business type (large business, small business, small disadvantaged business, 8(a)-certified small disadvantaged business, HUB Zone small business, woman-owned small business, very small business, veteran-owned small business, service-disabled veteran-owned small business). Section 2 of the response shall provide technical information, and shall include the following as a minimum: •· Interested parties shall respond with existing capabilities or products that meet all or a subset of the aforementioned attributes. Reponses that include information detailing potential tradeoffs or alternative solutions is encouraged. •· Respondents shall include product specifications and sketches with submission. Product specification and sketches are not included in the final page count. •· For the Pacific region, Poland site, and Virginia site projects the respondents should provide a detailed description of the following characteristics of their solution in their submission: •§ Master Site Zone Core Operations •o Signal Type (Digital, Analog, Phase II TDMA, mixed mode) •o Configuration capabilities (via S/W over IP) •o Software configuration & type (Windows) •§ Modular Frequency Timing System Operations •o Frequency in Megahertz (MHz) •§ Network Management Terminals Operations •o Accessibility within the IP network •o Loaded software capabilities •§ Network Security Gateway Systems Operations •o Roaming protocol between systems (inter-system, intra-system) •o Group mapping capabilities •§ Switching Routing Center Systems Operations •o Connection Options •o Real-time system transporting voice, call control, network management, and ancillary network services •o Wide Area Network Routing •§ Key Management Facility (KMF) Enterprise Solution •o Capability to pass Over-the-Air-Rekeying (OTAR) to subscriber units through a serial interface •o Capability to update keys via KMF •§ Dispatch Console Systems Operations •o Output (Watts) •o Screen Display type (touch screen) •o Channel Switching capability (remote, manual) •o Maximum number of channels •o Minimum/maximum call transmission time (In milliseconds) •o Maximum system load and error mitigation strategies •o Console Router type •§ Logging Recorder System •o Recording and archiving capabilities •o Replay capabilities •o Maximum Storage capacity •§ Cybersecurity Compliance •o Identify Security Technical Implementation Guides (STIG), Military Standards compliance, or Federal Agency Ratings and Test results •§ Candidate base station radio features •o APCO Project 25 (P25) Compliance •o Channel Spacing - Frequency in Kilohertz (kHz) •o Frequency Bands (VHF, UHF) •o Signal Type (Digital, Analog, Common Air Interface (CAI), TDMA, mixed mode) •o GPS/GNSS Capabilities •o Weight (lbs.) •o Encryption capabilities •o Functional description of all button and switches •o Pairing Capabilities •o Screen Display type •o RF Output (Watts) •o Capability to pass Over-the-Air-Rekeying (OTAR) to subscriber units through a serial interface •o Capability to pass Over-the-Air-Programming (OTAP) to subscriber units through a serial interface •o Description of how to configure the radio, including any software and/or cables used for configuration purposes •o Computer operating system used by the radio, if any •o Describe recommended ancillary items, such as Power Supplies, RF combiners, RF multi-couplers, etc •· For the Mobile and Portable radio project respondents should provide a detailed description of the following characteristics of their solution in their submission:: •o APCO Project 25 (P25) Phase I and II Compliance •o Intrinsically Safety Standards Compliance •o Channel Spacing - Frequency in kHz •o Frequency Bands (VHF, UHF, and 700/800 Megahertz (MHz)) •o Signal Type (Digital, Analog, Common Air Interface (CAI), FDMA, TDMA, mixed mode) •o Mobile and Portable / Handheld version capabilities •o Vehicle Adapters / Mobile mount capability •o GPS/GNSS Capabilities •o Weight (lbs.) •o Encryption capabilities •o Functional description of all button and switches •o Pairing Capabilities •o Screen Display type •o RF Output (Watts) •o Capability to pass Over-the-Air-Rekeying (OTAR) to subscriber units through a wireless media •o Capability to pass Over-the-Air-Programming (OTAP) to subscriber units through a media •o Description of how to configure the radio, including any software and/or cables used for configuration purposes •o Computer operating system used by the radio, if any •o Man portable repeater systems capabilities for VHF, UHF and 700/800 MHz •o Programming software, licensing, and reuse capabilities •o Describe recommended ancillary items, such as: power supplies, battery chargers, external antennas, vehicle mounts, grab and go vehicle mounts, etc. •· If applicable, respondents shall include a list of DoD, Department of Justice (DoJ) or Department of Homeland Security (DoHS) programs of record that currently employ their solution. Include a sponsor POC for each program, with email address and phone number. •· The Government is interested in receiving vendors' price lists for items they believe meet the need in this RFI. Supplying price data does not imply a contractual obligation and must be provided and marked as PRICE DATA. Respondents should include a list of authorized distributors. ADDITIONAL INFORMATION This RFI is issued solely for information and planning purposes - it does not constitute a Request for Proposal (RFP) or a promise to issue an RFP in the future. This request for information does not commit the Government to contract for any supply or service. Responders are advised that the U.S. Government will not pay for any information or administrative costs incurred in response to this RFI; all costs associated with responding to this RFI will be solely at the interested party's expense. Interested parties are responsible for adequately marking proprietary or competition sensitive information contained in their response. While the Government intends to use this information for future acquisition planning purposes, it will not release any information about your approach that might in any way compromise your competitive posture or proprietary information. The Government will not use any information provided to level your approach relative to another competition. All information received in response to the RFI that is marked PROPRIETARY will be handled accordingly. The Government will not be liable for or suffer any consequential damages for any proprietary information not properly identified. Proprietary information will be safeguarded in accordance with the applicable Government regulations. Responses to this RFI will not be returned. Respondents will not be notified of the result of the review. Failure to respond to this RFI does not preclude participation in any future associated RFP that may be issued. Information provided in no way binds the government to solicit or award a contract. If a solicitation is released, it will be synopsized on the Federal Business Opportunities website: www.fbo.gov. It is the potential vendor's responsibility to monitor this site for the release of any follow-on information. HOW TO RESPOND In response to this RFI, respondents shall submit written responses, not-to-exceed ten (10) pages in length via electronic mail. Product specification, sketches, or listings of authorized distributors will not count toward the page limitation. The Government is interested in receiving vendors' commercial published price lists for items they believe meet the requirement of this RFI, as well as, identification of long lead items(s), sub-systems(s), or systems(s). Supplying price data does not imply a contractual obligation and must be provided as a separate document, marked as PRICE DATA, and sent only to the contract point of contact identified below. Interested parties are requested to submit responses in PDF Document Format via e-mail to Evanuel Hairston at evanuel.hairston@navy.mil. Responses are due no later than 21 April 2017, 5:00 P.M. EDT.
- Web Link
-
FBO.gov Permalink
(https://www.fbo.gov/spg/DON/NAVAIR/N68335/N68335-17-RFI-0227/listing.html)
- Record
- SN04473145-W 20170416/170414234421-f482b4dc8d32d05ac7a46a40c67403c6 (fbodaily.com)
- Source
-
FedBizOpps Link to This Notice
(may not be valid after Archive Date)
| FSG Index | This Issue's Index | Today's FBO Daily Index Page |