RFI_Mobility New Retransmission Device_842571197.docx

REQUEST FOR INFORMATION (RFI) #842571197

The Defense Information Systems Agency (DISA) / Emerging Technology (EM) Directorate / Defense Information Technology Contracting Organization PS8414 is seeking information from industry to assist with the development and planning of a potential new requirement.

THIS IS AN RFI NOTICE ONLY. THIS IS NOT A REQUEST FOR PROPOSALS (RFP). NO SOLICITATION IS AVAILABLE AT THIS TIME.

1. OVERVIEW/PURPOSE/DESCRIPTION OF PROCUREMENT

The DISA EM Directorate is seeking industry input through this RFI to better understand the capabilities, solutions, and services available to support the future evolution of Commercial Solutions for Classified (CSfC) compliance retransmission devices (RD).

DISA currently manages mobile device services for Department of Defense (DoD) and approved non-DoD users and is required to keep pace with the evolving CSfC compliance. The evolution of CSfC Mobile Access Capability Package (MACP) requirements is a continuous effort to meet growing security demands while improving functionality, usability, and compliance in a rapidly changing technological landscape. The newly published CSfC MACP version 2.6 requires the RD to be connected to the mobile device through a hardwired connection. In earlier versions of MACP, this requirement could be met by using a cellular hotspot device that connects to the mobile device via Wi-Fi connection.

The Government acknowledges evolution of the CSfC MACP requirements and seeks smaller, more portable RDs that uphold high security standards. To ensure compliance with CSfC MACP regulations and enable future operational efficiencies, the Government is seeking recommendations from vendors on innovative strategies that would enhance both effectiveness and cost efficiency of retransmission devices.

2. SCOPE OF EFFORT

EM is seeking information on available products that can replace the existing RD, for current and future mobile devices. Meeting the CSfC MACP tethering requirement has proven difficult with smartphones due to their form factors. Many of the technically suitable devices available today are either the same size as or larger than the smartphones. EM is looking for a compact RD (e.g., smaller than a traditional smartphone) that adheres to CSfC MACP requirements while preserving the mobile device usability. To achieve this, it may be necessary to limit the hardware included in the RD.

Ideally, the RD should offer both cellular and Wi-Fi connectivity on the wide area network (WAN) side. However, at a minimum, it must support Wi-Fi connectivity only on the WAN. This flexibility is crucial for enabling the Government the ability to adapt to different operational scenarios and ensuring reliable communication. The future RD should aim to further reduce the size and weight while enhancing performance and security capabilities.

In addition to evaluating options for replacing the existing classified RDs, the Government is also seeking information on innovative, low-cost solutions that would enable the RD to be attached to various mobile device form factors quickly after device market release date. The mobile device case/sleeve does not need to be a commercially available off-the-shelf (COTS) item and can be a custom-developed or manufactured product.

The DISA mobile service offers DoD and approved non-DoD users the option to acquire a Samsung tablet or Samsung smartphone device. As new mobile devices are approved for utilization the device case/sleeves will need to be manufactured to support new form factors.

For the purposes of this RFI, the Government anticipates the vendor would be required to provide new compact CSfC MACP compliant RD and custom cases/sleeves for 2,500 tablets and 1,800 smartphones for users that are both continental United States and outside continental United States.

3. TECHNICAL CHARACTERISTICS

EM will follow a two-phased approach to assess potential solutions. In the first phase, the pilot phase of the CSfC RDs, a controlled, smaller-scale trial will be conducted to test specific commercial solutions for their ability to meet the security and operational requirements established by DISA and National Security Agency CSfC guidelines. If the pilot phase is successful, the next phase will involve scaling the solution to full-scale operations, expanding its deployment across a larger operational environment. The final proposed solution will replace the existing operational CSfC RD devices currently in use, such as Samsung tablets and smartphones.

For this RFI only a subset of the CSfC MACP requirements is being sought. Appendix A represents the minimum RD requirements, which have been derived from the CSfC MACP table 16-Retransmission Device Requirements and table 17-Enhanced Hardware Isolation Requirements. The vendor product may have additional features beyond the minimum requirements listed in Appendix A but must address the minimum RD requirements identified by the Government.

The following are a detailed list of questions for which the Government is seeking information.

1.1 General

1.1.1 Describe your primary business and market penetration with CSfC MACP accredited RD that connect to Wi-Fi and support a form factor that is usable with existing DoD approved classified mobile devices.

1.1.2 Provide insight on how you recommend DoD best acquire and deploy a new CSfC accredited Wi-Fi capable retransition device to minimize costs and optimize performance / security. If possible, discuss contract vehicles, deployment approaches/methods and lessons learned.

1.2 RD Products

1.2.1 Describe your experience with RD integration and migration (e.g. scale, duration, automation, lessons). If possible, describe the user/device provisioning and integration required to transition from the legacy mobile hotspot to a new RD based upon your product.

1.2.2 Cite one or more examples where your Company’s technical product is being used for an CSfC approved implementation that supports 5,000 users/devices. Include any relationships you have with other CSfC Trusted Integrators for which your product is configured to provide an enterprise CSfC validated product/service.

1.2.3 List the mobile devices that are supported or compatible with your RD product. Please identify any limitations (e.g., connection, device type, etc.) that the RD will not support.

1.2.4 Provide insight on how your Company will provide a more user-friendly, interface design will enable easier administrative management and configuration of the RD.

1.2.5 Describe the power consumption of your RD, and how it will impact the battery life of the mobile device.

1.2.6 Outline any innovative features your RD could offer that differentiate it from the existing solutions.

1.2.7 Describe how your RD be integrated into existing network infrastructures and what is the typical deployment timeline for your RD.

1.2.8 Describe how software and/or firmware updates will be managed and deployed.

1.3 Mobile Form Factor Case/Sleeve

1.3.1 Provide a brief overview of the Wi-Fi retransmission products your Company offers that can be easily attached to the mobile device via a mechanism that will allow the approved mobile device to be used and carried without impacting the user experience. Examples of user experience include, but are not limited to, access to all mobile device buttons, cameras, and ports.

1.3.2 Describe your approach on how the mobile device can be charged without losing connectivity to the RD. If this cannot be accomplished, describe how the RD can be easily attached and detached from the back of the mobile device, with the tether still connected, allowing the mobile device to continue communicating through the RD while charging inductively. If inductive charging cannot be supported, describe how the mobile device can be charged while the RD is connected without impacting the functionality of the device.

1.3.2.1 (Optional) Describe how you would support peripherals such as a keyboard, mouse, and monitor without impacting the ability to charge the device.

1.3.3 Describe your company's approach to supporting the evolution of new mobile device form factor models and how the Government will be supplied with the latest cases or sleeves that accommodate those mobile form factors.

1.3.4 (Optional) Describe how the device will meet MIL-STD-810H for environmental protection and MIL-STD-810G 516.6 for fall protection.

1.4 Security

1.4.1 List any accreditations (e.g. DISA Security Technical Implementation Guide (STIG), DoD component Authorization to Operate, etc.) that your product has for government or DoD operations. If none are currently in-place, what are your challenges and timelines for obtaining certifications necessary for the DoD (e.g. STIG, CSfC).

1.4.2 Explain your Company’s operating system patch management process for RD and how it aligns with DoD security standards and regulations.

1.4.3 Describe whether your Company currently possesses cleared personnel (minimum secret) required to support the product integration with existing DoD infrastructure, accreditation (if required), and users/device provisioning activities.

1.4.4 Describe your Company strategies to identify and mitigate risks associated with your supply chain and how your Company handles disruptions in the supply chain to ensure continuity of supply for critical defense components.

1.4.5 Provide a brief overview of how the RD will include the ability for administrators to control patch installation remotely.

1.4.6 Indicate if your company is currently listed as a trusted integrator[footnoteRef:1] for the CSfC program. If your Company is not currently listed as a trusted CSfC integrator what are your challenges and timelines for obtaining certifications necessary. [1: https://www.nsa.gov/Resources/Commercial-Solutions-for-Classified-Program/Trusted-Integrator-List/]

1.5 Connectivity

1.5.1 Describe how the RD could be connected to a smartphone for data and power using a single cable.

1.5.2 Provide a brief overview or description of how the RD will enable Wi-Fi connectivity on the WAN side of the device.

1.5.2.1 (Optional) Describe the device’s support for WPA. At a minimum, it should support WPA2, but WPA3 support is desired.

1.5.2.2 (Optional) Describe the versions of Wi-Fi that will be supported on the device. 802.11ac is required and 802.11ax is desired.

1.5.2.3 (Optional) Provide a brief overview or description of how the RD will enable cellular connectivity on the WAN side of the device.

1.5.2.3.1 (Optional) Describe how the device will support 4G and 5G frequencies both domestically and internationally.

1.5.2.3.2 (Optional) Describe how the device will support physical SIM and eSIM.

1.5.2.3.3 (Optional) Describe how the device will enable support for FirstNet.

1.5.2.4 (Optional) Describe how the device will support a wired ethernet connection on the WAN side of the device.

1.5.3 Describe how the RD will provide an interface that allow users to add and select Wi-Fi networks.

1.5.4 Split tunneling is prohibited on the mobile device. Please describe how the Wi-Fi selection interface can be accessed from an alternate smartphone or laptop.

1.5.5 Explain how the RD's Wi-Fi selection interface is restricted or inaccessible from the WAN side of the RD.

1.5.6 Cite if a mobile service and the RD combination will permit the use of a wired headset. If supported, indicate any specific product limitations (e.g., headset or smartphone compatibility).

1.5.7 Describe how your Company plans to support the evolution of new mobile device form factors and emerging network technologies (e.g., 5G, 6G).

1.6 Cost

1.6.1 Describe the approximate cost to provide the RD and smartphone case/sleeve product based upon your solution. Identify important assumptions and, if possible, distinguish between non-recurring and recurring costs, as well as user-dependent (costs/user) and user-independent (“fixed”) costs.

1.6.2 Identity the minimum number of units/qty that is required for your Company to provide cost-effective products that meets the Governments RD and continuous mobile device/sleeve requirements. If possible, breakout the annual manufacturing costs for the mobile device cases/sleeves vs. the RDs costs.

1.6.3 Discuss your approach for maintaining cost control of the RD and custom case/sleeve. Also identify any vendor price reductions associated with units/qty for the RD and case/sleeve.

1.6.4 Cite any existing contracts or catalogs where your technical product is currently being provided to the Government.

1.7 Special Requirements

1.7.1 All personnel performing on or supporting a DISA contract/order in any way shall be United States citizens. Contractor personnel must possess the interim or final security clearance when performance starts.

4. REQUESTED INFORMATION

The Government currently does not have any existing Government-Wide Acquisition Contracts that align with the scope of the requirements outlined in this request. The information provided will help the Government determine the most suitable procurement method or approach.

Responses may include pricing information, such as a Rough Order of Magnitude (ROM), but should not be as detailed as a formal price proposal. Additionally, please provide any suggestions or recommendations you may have for the Government's consideration regarding this request.

To assist DISA in determining the level of participation by small business in any subsequent procurement that may result from this RFI, provide information regarding any plans to use joint ventures (JVs) or partnering. Please outline the company's areas of expertise and those of any proposed JV/partner who combined can meet the specific requirements contained in this notice.

RESPONSE GUIDELINES:

Interested parties are requested to respond to this RFI with a white paper. Submissions cannot exceed 10 pages, single spaced, 12-point type with at least one-inch margins on 8 1/2” X 11” page size. The response should not exceed a 5 MB e-mail limit for all items associated with the RFI response. Responses must specifically describe the contractor’s capability to meet the requirements outlined in this RFI. Oral communications are not permissible. SAM.gov will be the sole repository for all information related to this RFI.

Companies who wish to respond to this RFI should send responses via email no later than 12:00 p.m. Eastern on January 6, 2025, to angela.k.zang.civ@mail.mil and melissa.a.weh.civ@mail.mil.

INDUSTRY DISCUSSIONS:

DISA representatives may choose to meet with potential offerors and hold one-on-one discussions. Such discussions would only be intended to obtain further clarification of potential capability to meet the requirements, including any development and certification risks.

QUESTIONS:

Questions regarding this announcement shall be submitted in writing by e-mail to angela.k.zang.civ@mail.mil and melissa.a.weh.civ@mail.mil. Verbal questions will NOT be accepted. Answers to questions will be posted to SAM.gov. The Government does not guarantee that questions received after 12:00 p.m. Eastern on January 6, 2025, will be answered. The Government will not reimburse companies for any costs associated with the submissions of their responses

DISCLAIMER:

This RFI is not an RFP and is not to be construed as a commitment by the Government to issue a solicitation or ultimately award a contract. Responses will not be considered as proposals, nor will any award be made as a result of this synopsis.

All information contained in the RFI is preliminary as well as subject to modification and is in no way binding on the Government. FAR clause 52.215-3, “Request for Information or Solicitation for Planning Purposes”, is incorporated by reference in this RFI. The Government does not intend to pay for information received in response to this RFI. Responders to this invitation are solely responsible for all expenses associated with responding to this RFI. This RFI will be the basis for collecting information on capabilities available. This RFI is issued solely for information and planning purposes. Proprietary information and trade secrets, if any, must be clearly marked on all materials. All information received in this RFI that is marked “Proprietary” will be handled accordingly. Please be advised that all submissions become Government property and will not be returned nor will receipt be confirmed. In accordance with FAR 15.201(e), responses to this RFI are not offers and cannot be accepted by the Government to form a binding contract.

Appendix A – Government Specific MACPv2.6 Technical RD Requirements

ID #

MA-RD-32

MA-RD-32

MA-RD-31

Legend:

VE – VPN EUD TE – TLS EUD HI – Hardware Isolation