MODIFICATION
99 -- Private Wireless Ad Hoc Network
- Notice Date
- 3/3/2016
- Notice Type
- Modification/Amendment
- NAICS
- 334290
— Other 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-16-RFI-0154
- Archive Date
- 3/31/2016
- Point of Contact
- Stephen Winkler, Phone: 7323232971, Eric L. Waterman, Phone: (732) 323-2559
- E-Mail Address
-
stephen.winkler@navy.mil, eric.waterman@navy.mil
(stephen.winkler@navy.mil, eric.waterman@navy.mil)
- Small Business Set-Aside
- N/A
- Description
- Request for Information (RFI) Private Wireless Ad Hoc Network Special Communications Mission Solutions (SCMS) Naval Air Warfare Center Aircraft Division ______________________________________________________________________________ RFI Number: N68335-16-RFI-0154 Classification Code: 5895; Miscellaneous Communication Equipment NAICS Code(s): 334290 - Other Communications Equipment Manufacturing REQUEST FOR INFORMATION PURSUANT TO FAR 15.201(e) - THIS IS A REQUEST FOR INFORMATION (RFI) ONLY. 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 whatsoever. Further, the government is not at this time seeking proposals and will not accept unsolicited proposals. 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. Proprietary information will be safeguarded in accordance with the applicable Government regulations. Failure to respond to this RFI does not preclude participation in any future associated RFP that may be issued. BACKGROUND/PURPOSE/TECHNICAL REQUIREMENTS The Naval Air Warfare Center Aircraft Division, SCMS Division is soliciting information and comments from industry on its ability to provide a non-developmental or Commercial Off The Shelf (COTS) a private wireless ad hoc network such as a Mobile Virtual Private Network or a Mobile Ad Hoc Networking radio based communications system which can support a variety of purposes including a secure/private data backbone to support Internet Protocol based data exchange between COTS tablets, laptop devices and various sensors. Required data types will include sensor data, voice, and position location information. The communication solution will need to be able to receive data wirelessly from sensors that transmit data via Bluetooth. This connection can be through either embedded Bluetooth or attached USB adapter or dongle. The solution must be able to receive from this Bluetooth connection while simultaneously transmitting data over the communication network on a different frequency band. The solution should be capable of performing multiple tasks simultaneously thereby reducing the equipment footprint and tactical/operational burden for deployed personnel. SCMS desires to leverage advancements in technology to standardize the existing baseline architecture for supportability and sustainability. The communications/data transmission solution shall be capable of supporting missions in a variety of settings that range from dense urban environments to rural areas with varied terrain and topography. The urban environments can include: a) large capacity public venues such as stadiums/arenas, b) wide-area venues such as marathons, and c) multi-site events with challenging Radio Frequency (RF) situations. The components of the communication/data transmission solution should complement a variety of deployment uniforms (e.g., low profile and overt) and be capable of performing in concert with various levels of HAZMAT personal protective equipment (e.g., Class 1/Level A fully encapsulated). The communication solution shall have the capability of expanding to at least 60 nodes without degradation to the quality of the network. Additionally, the solution shall include the ability for nodes to seamlessly join and leave the network. The communication devices will be configured to be man portable and are required to support operations in highly mobile environments. The system may operate in isolation, or may have gateways to, and interface with, a fixed network. In the latter operational mode, it is typically envisioned to operate as a closed (stub) network connecting to a fixed internetwork. The nodes may be equipped with wireless transmitters and receivers using antennas which may be Omni-directional (broadcast), highly-directional (point-to-point), possibly steerable, or some combination thereof. 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. •· Respondents should provide a detailed description of the following characteristics of their solution in their submission: •§ List of Certifications and Standards •§ Operation •1. Transmit (Tx)/Receive (Rx) Frequency Range •2. Bandwidth and associated throughput (megabits per second (Mbps)) •3. Band capability (i.e., software feature, software programmable or hardware component that must be changed out) •4. Antenna Gain for all antenna types - Equivalent Isotropically Radiated Power (EIRP) •5. Beamforming capabilities/techniques •6. Description of Network Architecture (include how meshing is implemented) •7. Maximum nodes on the network (if not defined, then the percentage of maximum available bandwidth consumed by overhead management/discovery/path selection traffic at 200 nodes) •8. Wireless broadband capability (e.g., 3G, 4G) •9. Encryption capability (include any National Security Agency (NSA) or Federal Information Processing Standard Publication (FFIPS) approvals/certifications) •10. Input/output interfaces (hard-wired and wireless) •11. GPS capabilities (integrated, separate, etc.) •12. Quality of Service (QoS) capabilities (priorities and bandwidth control features) •13. Method of configuration (front panel or external device such as a PC) •14. Ease of Operation and any included network management tools •15. Methods to perform manual override of channel and power assignment •16. Operational limitations and characteristics in different environments (open sea, farm, forest, suburban, and dense urban) •17. Ancillary equipment used to overcome line-of-site limitations resulting from dense urban environments •18. Data at Rest capabilities (capacity, storage method, encryption capabilities, etc.) •19. Embedded capabilities of the radio (e.g., voice encoding, video encoding, Wi-Fi access point, etc.) •20. RF Waveforms and Digital Signal Processing (DSP) techniques •21. Low Probability of Intercept or Low Probability of Detection capabilities and characteristics •22. Maximum hop count •23. Latency, node to node operation (non-encrypted and encrypted, if different) •24. Latency in a >20 node network, node to node •25. Form factor (compatibility with other devices) •§ Features •1. Number of users capable of being on the network •2. Number of bands capable •3. Battery type(s), battery size, and battery life •4. Dimensions (height x width x depth) •5. Weight in lbs. •§ Time to Production •§ Total quantity of units sold to date •§ Date of delivery of the first unit •§ Date of delivery of most recent unit •§ Basic and extended warranty information •· If applicable and able, respondents shall include a list of Department of Defense (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 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 identification of long lead items(s), sub-systems(s), or systems(s). The Government does not intend to award a contract on the basis of this request or to otherwise pay for the information solicited. 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. 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. HOW TO RESPOND Interested parties are requested to respond to this RFI with a PDF Document Format. Responses shall be limited to 10 pages and submitted via e-mail to the Technical Point of Contact, Brian Metcalf at brian.d.metcalf@navy.mil. The Contracting Officer, Eric Waterman, shall also be copied on email submissions at Eric.Waterman@navy.mil. Proprietary information, if any, should be minimized and must be clearly marked. Responses are due no later than 16 March 2016, 5:00 P.M. EST. Responses to this RFI will not be returned. Respondents will not be notified of the result of the review. 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.
- Web Link
-
FBO.gov Permalink
(https://www.fbo.gov/spg/DON/NAVAIR/N68335/N68335-16-RFI-0154/listing.html)
- Record
- SN04039262-W 20160305/160304000228-5f366df934caf94acac275552de2f2d4 (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 |