UCR RFI_August 2026.pdf

DOD UNIFIED CAPABILITIES REQUIREMENTS (UCR)

REQUEST FOR INFORMATION (RFI) 612673989-001

The Defense Information Systems Agency (DISA), Emerging Technology (EM) Directorate, and Defense Information Technology Contracting Organization (DITCO) PS61 are requesting industry input to inform updates to the Department of Defense (DoD) Unified Capabilities Requirements 2013 (UCR 2013), Change 21. This effort focuses on a review of proposed interoperability requirements relevant to current DoD Unified Capabilities (UC) technologies, system integration, and interoperability.

The RFI seeks industry perspectives on proposed draft interoperability requirements for the foundational UC technologies of Voice, Video, Chat, and Data/SDN.

In accordance with DoD CIO Memorandum, DoD Information Network Approved Products List, dated 18 July 2025 and the DoDIN Approved Products List Sunset FAQ, dated 30 September 2025, only UC interoperability requirements are the focus of the UCR update. Please do not include in your response any cybersecurity or Quality of Service (QoS) related requirements.

THIS IS A REQUEST FOR INFORMATION (RFI) ONLY. THIS IS NOT A REQUEST

FOR PROPOSALS (RFP). NO SOLICITATION IS AVAILABLE AT THIS TIME.

1 OVERVIEW/PURPOSE/DESCRIPTION

The purpose of this RFI is to gather information from industry regarding DISA EM’s approach to defining new UC interoperability requirements.

Additionally, the RFI supports the DoD Chief Information Officer’s (CIO) DoDIN Approved Products List (APL) Sunset Memorandum2 objectives related to modernization and continuous improvement of Department-wide processes, policies, and instructions, while maintaining security, reliability, interoperability, efficiency, and effectiveness across the DoDIN.

Information received will assist DISA EM in establishing a new UC process supporting the acquisition of UC technologies while using an independently verifiable evaluation paradigm detached from the evolution away from the DoDIN APL-based testing and certification processes. This approach constitutes an alternative methodology for assessing UC product alignment with interoperability and enterprise integration requirements. Any such considerations are preliminary and subject to further analysis, coordination, and approval.

DISA is interested in industry perspectives regarding the approach to the codification and validation of UC technologies for integration and utilization within the DoDIN and across Joint, Coalition, and mission partner environments.

1 https://www.disa.mil/-/media/Files/DISA/Services/UCCO/UCR2013/UCR_2013_Combined.pdf 2 https://aplits.disa.mil/docs/DODIN_APL_SUNSET.pdf https://www.disa.mil/-/media/Files/DISA/Services/UCCO/UCR2013/UCR_2013_Combined.pdf https://aplits.disa.mil/docs/DODIN_APL_SUNSET.pdf

Responses to this RFI are voluntary and will be used solely for market research and planning purposes. Information submitted will not be returned and will not be considered proprietary.

This RFI does not constitute a solicitation, does not represent a commitment by the Government to issue a solicitation or award a contract, and does not obligate the Government to pay for any information provided.

2 SCOPE OF EFFORT

The scope of this RFI is limited to gathering industry feedback to support the review and potential update of the UCR 2013 document. DISA seeks information regarding the relevance, clarity, applicability, and future alignment of existing UCR requirements to current and emerging technologies, operational and mission needs, as well as evolving DoD enterprise architectures.

Industry feedback may also be used to assess the effectiveness of current requirements, processes, and support frameworks enabling secure, interoperable, scalable, and efficient UC solutions across the DoDIN. Responses may identify areas where clarification, refinement, or potential future updates could be considered.

Within this scope, respondents may address the following areas, as applicable:

• Requirement Modernization:

o Analysis of the draft UC interoperability requirements attached to this RFI that may be unclear, duplicative, overly prescriptive, or misaligned with current implementation practices.

o Addition of UC requirements that your organization’s Subject Matter Experts (SME) identify as valuable for consideration and adjudication by the DISA EM.

Please attach any requirements related documentation your organization may currently use to guide the UC technology deployment and validation of enterprise interoperability.

• Interoperability and Integration: Observations regarding interoperability across DoD Components, Joint and Coalition partners, and mission environments, including alignment with open standards, modular architectures, and real-time integrative approaches that rationalize differing Joint and Coalition standards.

• Implementation Considerations: High-level lessons learned, risks, or constraints associated with implementing UCR-aligned capability requirements.

This RFI does not request detailed technical solutions, cost or pricing data, proprietary information, or proposals. Responses should be provided at a conceptual and capability-based requirement level and should not reference specific vendor products or services.

3 REQUESTED INFORMATION

DISA requests that respondents provide concise, high-level, non-proprietary information using the Government-provided Excel response template. Inputs will inform Government analysis and planning related to updates of the UCR. Respondents shall provide information only in the tabs specified below and in accordance with the instructions embedded in each tab.

3.1 TAB 3: UCR COMMENTS (REQUIRED)

Respondents shall use TAB 3 to provide draft requirement review input or to define additional interoperability requirements for consideration and adjudication. All responses must align to the Government-predefined categories and column headers provided in the Excel template.

Inputs should reflect, as applicable:

• Current and anticipated operational relevance

• Integration with existing, modern, and emerging technologies

• Interoperability across systems, platforms, and Joint, Coalition, and mission partner environments

• Scalability and adaptability to future requirements

• Continued effectiveness of the UC area and associated requirements

Respondents shall use TAB 3 as the primary input mechanism for requirement review and analysis. All entries shall align with the predefined fields and instructions within the tab.

Respondents shall review the interoperability requirements attached to this RFI and provide suggested revision or addition in accordance with the categories included in TAB 3. Respondents shall not create, modify, or supplement defined categories.

Required TAB 3 Inputs:

• General Format: use draft requirements guide format ensuring applicable data fields for appropriate definition are specified for suggested revision/addition of requirements.

• Industry Comment: for any revision to draft requirements or suggested additions of requirements, please ensure narrative in this field sufficiently defines rationale for revision/addition and requirement applicability to existing/non-existing DoW enterprise service. Inputs should reflect operational relevance, interoperability, architectural alignment, and modernization considerations at the requirements level. Vendor-specific solutions, proprietary approaches, pricing, or product references shall not be included.

3.2 TAB 4: GAPS, RISKS, AND OBSERVATIONS (OPTIONAL)

Respondents may use TAB 4 to provide optional observations that are not limited to a single UC interoperability technology. Input should address overarching considerations relevant to UCR modernization, integration, and interoperability.

Examples include, but are not limited to:

• Capability gaps, overlaps, or redundancies within the draft UC requirements.

• Risks, constraints, or assumptions associated with existing requirements.

• Dependencies or interactions across functional areas.

• Integration or interoperability challenges.

• Recommendations to improve requirement clarity, measurability, flexibility, or deployability.

TAB 4 Columns Inputs:

• Category Type: Select: Gap / Risk / Observation

• Description of Gap, Risk, or Observation: Provide concise, non-proprietary description.

• Currently within the UCR: Select: Yes/No. If Yes, identify impacted area.

• UCR Functional Area Impacted: Select applicable functional area, if any.

• Recommendations or Mitigation: Provide recommended actions or considerations.

Responses should address overarching UCR considerations such as capability gaps, risks, dependencies, integration or interoperability challenges, and opportunities to improve requirement clarity, flexibility, or deployability.

All inputs must remain non-proprietary and capability focused.

4 RESPONSE GUIDELINES

All responses must be submitted using the Government-provided Excel response template (Attachment: DRAFT UCR RFI RESPONSE TEMPLATE). Responses submitted in alternate formats, modified templates, or external documents may not be reviewed or considered as part of the Government’s analysis.

Respondents are requested to structure their submissions strictly in accordance with the tab organization, column headers, and instructions provided in the template to promote consistency, traceability, and efficient Government review. Responses should be clear, concise, and focused on requirements- and capability-based insights.

Proprietary, classified, competition-sensitive, or vendor-specific information shall not be included.

4.1 TAB 1: INSTRUCTIONS (READ FIRST)

This tab contains Government-provided instructions for completing the Excel response template.

Instructions (shown in purple at the top of each tab) describe the purpose of the tab, required and optional fields, and formatting guidance.

Respondents shall review TAB 1 in its entirety before completing any other tabs. Respondents shall not enter data into or modify this tab or any Government-provided instructional content.

4.2 TAB 2: RESPONDENT INFORMATION

Respondents shall provide general information about the responding organization, including:

• Organization Name: Name of the company or entity submitting the response.

• Point of Contact: Name, title, and email address of the primary point of contact.

• Company Unique Entity Identifier (UEI): Enter the organization’s UEI. This is provided for Government identification purposes only.

• Commercial and Government Entity (CAGE) Code: Enter the organization’s CAGE

Code. This is provided for Government identification purposes only.

• Defense Federal Acquisition Regulation Supplement (DFARS) Company Size

Classification: Enter the applicable classification in accordance with DFARS criteria (e.g., small business, large business, etc.).

• Date Submitted: Date the response is completed and submitted.

4.3 TAB 3: UCR COMMENTS (REQUIRED)

TAB 3 serves as the primary mechanism for collecting UC technology interoperability requirements recommendations for revision or addition. Respondents shall populate all required columns and comply with conditional logic exactly as implemented in the Excel template.

Mandatory Completion:

• All rows corresponding to listed UC requirement areas shall be completed.

• Respondents shall not alter column headers, add rows, insert comments, or modify validation rules.

Narrative Input Constraints: Narrative responses shall be concise, requirements-focused, and limited to the scope of the identified functional area.

Entries in TAB 3 shall address requirements-level considerations such as operational relevance, interoperability, architectural alignment, and modernization needs. Vendor-specific solutions, proprietary approaches, pricing, schedules, or product references shall not be included.

4.4 TAB 4: GAPS, RISKS, AND OBSERVATIONS (OPTIONAL)

TAB 4 provides an optional mechanism for capturing cross-functional insights that are not fully represented at the individual functional area level in TAB 3.

Completion Guidance:

• Each row shall address a single gap, risk, or observation.

• The Category Type column shall be completed using only the predefined options.

• Where an issue is already reflected in the UCR, respondents shall indicate applicability and identify the impacted functional area using the designated columns.

Acceptable Input Scope:

• Capability gaps, overlaps, or redundancies

• Risks or constraints associated with existing UCR requirements

• Cross-functional dependencies or integration challenges

• Interoperability considerations spanning multiple functional areas

• Recommendations to improve requirement clarity, measurability, flexibility, or implementability

TAB 4 inputs shall remain high-level, non-proprietary, and capability requirement-focused.

Vendor-specific implementations, proprietary methodologies, or product references shall not be included.

The response should not exceed a five (5) MB e-mail limit for all items associated with the RFI response. 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 e-mail no later than 12:00 p.m. Eastern on 12 August 2026, to disa.meade.em-unified-capabilities@mail.mil. All responses should reference “UC Requirements Review RFI Response” in the e-mail subject line.

5 INDUSTRY DISCUSSIONS:

At the Government’s discretion, DISA representatives may conduct follow-on discussions with respondents for the limited purpose of seeking clarification or additional information related to submitted responses. Any such discussions will be conducted solely to support market research and to enhance the Government’s understanding of general considerations. Participation in any discussions are voluntary and do not constitute a commitment by the Government to pursue an acquisition, solicitation, or engage in contractual activity.

6 QUESTIONS

Questions regarding this announcement shall be submitted in writing by e-mail to disa.meade.em-unified-capabilities@mail.mil. Any questions submitted shall reference “UC Requirements Review Questions” in the subject line of the e-mail.

Verbal questions will NOT be accepted and responses posted to SAM.gov. The Government does not guarantee that questions received after 12:00 p.m. Eastern on 10 August 2026, will be answered. The Government will not reimburse companies for any costs associated with the submission 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, subject to modification, and is in no way binding to the Government. FAR clause 52.215-3, “Request for Information or Solicitation for Planning Purposes”, is incorporated for reference with this RFI. The Government does not intend to pay for information received in response to this RFI and 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 and 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.