Media Gateway Solution

REQUEST FOR INFORMATION The Defense Information Systems Agency (DISA) Teleport Program Management Office (PMO) is seeking information from industry to assist with the development and planning of a potential new requirement. THIS IS A REQUEST FOR INFORMATION (RFI) NOTICE ONLY. THIS IS NOT A REQUEST FOR PROPOSALS (RFP). NO SOLICITATION IS AVAILABLE AT THIS TIME. 1. Overview / Purpose / Description of Procurement DISA PMO is issuing this RFI to identify available industry capabilities regarding a Media Gateway (MGW) solution for the Department of War (DoW) s Teleport System s Generation 3 Phase 3 (G3P3) capability. The DoW leverages two Ultra High Frequency (UHF) satellite communication systems: Legacy UHF and Mobile User Objective System (MUOS). Due to their varying waveforms, an interoperability solution is required. Resultantly, DISA developed essential integration systems known as the MUOS to Legacy Gateway Component (MLGC) and the MUOS Voice Gateway (MVG). These gateways serve as the bridging architecture within the DoW s Teleport System s G3P3 capability, which is designed to connect modern satellite communications with legacy field gear. Together, MLGC and MVG resolve a fundamental technological gap between generations of military radio systems: They provide direct interconnectivity between legacy UHF tactical radios (which operate on half-duplex, push-to-talk mechanisms) and MUOS radios (which utilize full-duplex, 3G-like cellular technology). Specifically, the MVG manages the voice networks. It routes and translates voice packets to allow ground troops to use legacy UHF radios to communicate seamlessly with those utilizing MUOS terminals. The MLGC handles data exchanges and network-level translation, ensuring that security protocols and waveforms are converted in real-time to enable interoperable communication without losing critical data. However, the MVG-MUOS integration technologies are reaching end of life (EOL). For this reason, the Government is seeking to identify vendor sources to replace the EOL equipment with existing or new technologies, such as a MGW solution capable of providing robust Telecommunication Union - Telecommunication Standardization Sector (ITU-T) V.150.1 Modem-over-Internet Protocol support within a Session Initiation Protocol (SIP) based architecture. DISA s primary objective for this RFI is to facilitate seamless, secure voice and data communication between legacy analog endpoints (e.g., Secure Terminal Equipment (STE), modems) and IP-based secure terminals (e.g., Voice over Internet Protocol Encryptor (vIPer), Secure Communication Interoperability Protocol (SCIP)-compliant devices) across the Defense Information System s unclassified and classified networks (IL5/6). Responses to this RFI must at a minimum describe vendor capabilities, experience, and provide a brief synopsis of the ability to meet the requirements described herein. 2. Scope of Effort a. Current Architecture and Operational Need See Controlled Unclassified Information (CUI) Appendix, access can be requested at antoine.c.etchene.civ@us.navy.mil or amadeo.l.roybal.civ@mail.mil b. Risk Assessment and Urgency See Controlled Unclassified Information (CUI) Appendix, access can be requested at antoine.c.etchene.civ@us.navy.mil or amadeo.l.roybal.civ@mail.mil c. Integration with Future IP-Based Cryptographic Development See CUI Appendix, access can be requested at antoine.c.etchene.civ@us.navy.mil or amadeo.l.roybal.civ@mail.mil 3. Technical Characteristics a. MGW Technical Specification Compliance Respondents must demonstrate that their proposed MGW solution satisfies the core technical specifications outlined below: See CUI Appendix, access can be requested at antoine.c.etchene.civ@us.navy.mil or amadeo.l.roybal.civ@mail.mil b. Waveform Integration Parameters The vendor must possess a comprehensive technical understanding of the tactical MUOS waveform architecture, payload capabilities, and functional characteristics. Where feasible, the vendor should adapt the specialized V.150 protocol to align with modern, adaptive, wideband protocols. Vendors must configure solutions to accommodate established operational profiles to ensure interoperability: See CUI Appendix, access can be requested at antoine.c.etchene.civ@us.navy.mil or amadeo.l.roybal.civ@mail.mil 4. Requested Information Interested vendors are requested to submit white papers addressing their capability to meet the technical characteristics above. Additionally, responses must explicitly address the following vendor expertise and implementation inquiries: Provide at least two (2) examples of successful V.150.1 Minimum Essential Requirements implementations in a defense or high-security environment that involved SCIP-215/216 compliance. The vendor shall state their current Facility Clearance Level and certify that all engineering support personnel possess the requisite security clearances to operate on DoW defense networks. The vendor must confirm whether their solution will be compatible with future Government-specified IP-based cryptographic devices or state their willingness to co-design a compatible solution. Vendors must outline their technical methodology, including required interfaces and protocols, for integrating with proprietary IP-based crypto devices. Include previous experience, interface specifications, or technical risks. Describe the diagnostic tools natively available within the gateway for analyzing Simple Packet Relay Protocol packet headers and monitoring modem state machine transitions. List all third-party SIP Cores and end-user devices (e.g., standard Unified Call Managers, vIPer, STE, MUOS Radios) with which the proposed solution has been natively tested and verified. Confirm the availability and structure of Tier-3 engineering support, specifically detailing vendor expertise in International ITU-T V-series modem recommendations. Vendors must identify if their proposed MGW solution and associated engineering support services are available on any existing Government-Wide Acquisition Contracts, General Services Administration Multiple Award Schedules, or active Department of Defense /DoW Indefinite Delivery/Indefinite Quantity contracts. If applicable, please provide the specific contract name, contract number, and the relevant Special Item Numbers or scope categories that align with this requirement. Based on their understanding of the MGW market and the technical specifications outlined in this RFI, vendors should provide recommendations for the most effective procurement method. Discuss whether they believe this requirement should be pursued as a commercial item acquisition (FAR Part 12), a traditional negotiated procurement (FAR Part 15), or via Other Transaction Authority. Additionally, vendors should advise if there are specific set-aside considerations (e.g., small business) that the Government should evaluate for this effort. Vendors must explicitly state their company's intended role in any potential future solicitation stemming from this requirement. Specify whether their firm is interested in competing as a Prime Contractor capable of delivering the end-to-end solution, or if they intend to participate as a Subcontractor offering specific components (e.g., proprietary hardware, specialized Tier-3 ITU-T V-series support). If they anticipate utilizing teaming arrangements or joint ventures to fulfill the entire scope, briefly outline their teaming strategy. Vendors must provide constructive feedback on the requirement. The Government highly values industry insight and welcomes any suggestions that could improve the clarity, feasibility, or cost-effectiveness of this potential procurement. Please identify any potential cost drivers, timeline risks, or overly restrictive elements within the current draft technical characteristics (such as V.150.1 or SCIP-215/216 compliance). Furthermore, please suggest any commercial best practices, alternative architectures, or emerging technologies that the DISA Teleport PMO should consider to better achieve our interoperability objectives. (Note: If further detailed technical specifications containing CUI/CTI are required for accurate Rough Order of Magnitude (ROM) generation, vendors must submit a formal request via DoD SAFE to antoine.c.etchene.civ@us.navy.mil or amadeo.l.roybal.civ@mail.mil upon verification of an active DD Form 2345/JCP Certification.) 5. Response Guidelines & Disclaimer Response Guidelines: Estimated Program Value and ROM Respondents are requested to provide a ROM cost estimate demonstrating how their proposed solution aligns with the technical requirements. The ROM must be structured to distinguish between initial engineering, development, and long-term sustainment. Cost Category Description of Effort Estimated Lifecycle Cost Research & Development Costs associated with engineering, integration with IP encryptors, SIP/V.150.1 protocol adaptation, and security certification/ Approved…