SOURCES SOUGHT
58 -- Mobile Ad Hoc Networking (MANET)
- Notice Date
- 11/4/2015
- Notice Type
- Sources Sought
- 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-0045
- Archive Date
- 12/5/2015
- Point of Contact
- Danielle DiLorenzo, Phone: 732-323-7067, Eric L. Waterman, Phone: (732) 323-2559
- E-Mail Address
-
danielle.dilorenzo@navy.mil, eric.waterman@navy.mil
(danielle.dilorenzo@navy.mil, eric.waterman@navy.mil)
- Small Business Set-Aside
- N/A
- Description
- 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 (NAWCAD), Special Communications Mission Solutions (SCMS) Division is soliciting information and comments from industry on its ability to provide a non-developmental or Commercial Off The Shelf (COTS) Mobile Ad Hoc Networking (MANET) radio based communications system which can support a variety of purposes including a secure/private data backbone to support Internet Protocol (IP) based data exchange between COTS tablets, laptop devices and various sensors. Required data types will include sensor data, voice, video, images and position location information. The solution should provide multiple input/output (IO) ports for integration with various sensors. The MANET radio solution should also be able to receive data wirelessly from sensors that transmit data over Wi-Fi. This connection can be through either embedded Wi-Fi or attached dongle. The solution must be able to receive from this Wi-Fi connection while simultaneously transmitting data over the MANET on a different frequency band. The MANET radio solution should be capable of performing multiple tasks simultaneously thereby reducing the equipment footprint and tactical/operational burden on the deployed personnel. SCMS desires to leverage advancements in technology to standardize the existing baseline architecture for supportability and sustainability. The MANET radio solution should be capable of supporting missions at large capacity public venues such as stadiums/arenas or wide-area venues such as marathons or multi-site events in challenging RF environments, particularly in dense urban environments. The components of the MANET radio 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 (PPE) (e.g., Class 1/Level A fully encapsulated). The MANET radio solution should have the capability of expanding to at least 150 nodes without degradation to the quality of the network. Additionally, the solution should include the ability for nodes to seamlessly join and leave the network. The MANET 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 "stub" network connecting to a fixed internetwork. Stub networks carry traffic originating at and/or destined for internal nodes, but do not automatically permit exogenous traffic to "transit" through the stub network. MANET 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. At a given point in time, depending on the nodes' positions and their transmitter and receiver coverage patterns, transmission power levels and co-channel interference levels, a wireless connectivity in the form of a random, multi-hop graph or "ad hoc" network would exist between the nodes. This ad hoc topology may change with time as the nodes move or adjust their transmission and reception parameters. 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. • Respondents should provide a detailed description of the following characteristics of their solution in their submission: 1. Transmit (Tx)/Receive (Rx) Frequency Range 2. Battery type, battery size, and battery life 3. Bandwidth and associated throughput (megabits per second (Mbps)) 4. Form factor/SWAP/ Dimensions and weight for each radio in the family of radios 5. Antenna Gain (EIRP) for all antenna types 6. Description of Network Architecture, including 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. Encryption capability (include any NSA or FIPS approvals/certifications) 9. Input/output interfaces (hard-wired and wireless) 10. GPS capabilities - integrated, separate, etc. 11. Quality of Service (QoS) capabilities: priorities and bandwidth control features 12. Method of configuration (front panel or external device such as a PC) 13. Ease of Operation and any included network management tools 14. Methods to perform manual override of channel and power assignment 15. Operational limitations and characteristics in different environments (open sea, farm, forest, suburban, and dense urban) 16. Data at Rest capabilities (capacity, storage method, encryption capabilities, etc.) 17. Embedded capabilities of the radio such as voice encoding, video encoding, Wi-Fi access point, etc. 18. Maximum hop count 19. RF Waveforms and DSP techniques 20. Beamforming capabilities/techniques 21. Channel Access methods 22. Low Probability of Intercept or Low Probability of Detection capabilities and characteristics 23. Latency, node to node operation (non encrypted and encrypted, if different) 24. Latency in a >20 node network, node to node 25. Ancillary equipment used to overcome line-of-site limitations resulting from dense urban environments 26. Total quantity of units sold to date 27. Date of delivery of the first unit 28. Date of delivery of most recent unit 29. Basic and extended warranty information 30. Status of JF-12 (DD Form 1494) Certification, whether pending or final. • 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. • Respondents shall include a list of authorized distributors, if applicable. 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 receiving vendors' commercial published price lists for items they believe meet the requirement of this RFI, as well as, identification of long lead item(s), sub-system(s), or system(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 contracts point of contact identified below. 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 competitor. All information received in response to this 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 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 only to Contracting Officer name at Eric.Waterman@navy.mil. Proprietary information, if any, should be minimized and must be clearly marked. Responses are due no later than 20 November 2015, 3: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. Contracting Office Address: Department of the Navy, Naval Air Systems Command Naval Air Warfare Center Aircraft Division-Lakehurst Contracts Navy Department Hwy. 547 Attn: Bldg. 120-Room 180 Lakehurst, NJ, 08733-5083, United States
- Web Link
-
FBO.gov Permalink
(https://www.fbo.gov/spg/DON/NAVAIR/N68335/N68335-16-RFI-0045/listing.html)
- Record
- SN03937987-W 20151106/151104234945-c1985896b88190c62fffdd5468d7dad0 (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 |