CALL FOR SOLUTIONS

Project Number UC_FY26-01

Army Open Solicitation (AOS) Number W9128Z-25-S-A002

Call for Solution Title Unified Communications Software Platform Licensing

Issued By

U.S. Army Contracting Command – Aberdeen Proving Ground (ACC-APG) on behalf of Capability Program Executive – Command and Control Information Network (CPE C2IN), Product Manager Command and Control Data & AI (PM C2 Data & AI)

Submission Instructions:

Item Details

White Papers Due Date/Time (Suspense) 30 April 2026 1700 hours Eastern Daylight Time (EDT)

Contracting Officer MAJ Quentin Sica, Quentin.sica.mil@army.mil

Specialist MAJ Lindsay Keel, lindsay.e.keel.mil@army.mil

Note: Please advise the cognizant Contracting Officer and Specialist as soon as possible via the emails above if your organization intends to submit a White Paper in response to this Call for Solutions.

Any submissions received by the Contracting Officer after the suspense date/time listed above will be deemed late and will not be evaluated. It is the sole responsibility of the company to ensure that its submission is received in the inbox listed above before the deadline specified.

This Call for Solutions may result in the Government awarding a Federal Acquisition Regulation (FAR) Part 12 commercial contract in accordance with 10 U.S.C. § 3458 and Defense Federal Acquisition Regulation Supplement (DFARS)

212.70 – Defense Commercial Solutions Opening (deviated to remove “innovative” as a requirement) .

1. INTRODUCTION

The U.S. Army is seeking mature, commercially available software solutions for a unified communications platform. This Call for Solutions is issued under the authority of 10 U.S.C. § 3458 and DFARS 212.70, Defense Commercial Solutions Opening (CSO), as an amendment to Army Open Solicitation W9128Z-25-S-A002.

The Government's preference is to award a FAR Part 12 commercial contract for commercial products and commercial services as defined in FAR 2.101.

This Call for Solutions document is UNCLASSIFIED. Detailed technical requirements, including performance objectives and requested capabilities, are contained in the accompanying Statement of Objectives (SOO), which is posted alongside this Call for Solutions. Offerors must obtain and review the SOO to fully understand the Government's requirements. Portions of the SOO are marked as Controlled Unclassified Information (CUI) and must be handled accordingly.

Access to Controlled Unclassified Information (CUI) Statement of Objectives (SOO). The SOO for this Call for Solutions contains Controlled Unclassified Information (CUI) and will only be accessible upon request. Offerors must use the "Request Access" button within SAM.gov to initiate access. The system will automatically provide the Government with the offeror's UEI and CAGE Code. The Government will verify the offeror's Level 1 Cybersecurity Maturity Model Certification (CMMC) compliance or higher before granting access to CUI documents. Approved offerors will access the SOO directly through SAM.gov and must adhere to all CUI handling and safeguarding requirements as outlined in DoD Instruction 5200.48. Non-compliance may result in access revocation and disqualification. Early submission of access requests is strongly encouraged. More information regarding CMMC can be found at https://dodcio.defense.gov/CMMC/.

2. BACKGROUND

The Army requires a unified communications software platform that provides an interoperable capability within the Army's tactical voice architecture. The objective is to bridge legacy and modern systems into a single integrated voice environment, encompassing Combat Net Radios, telephony, IP devices, mobile ad-hoc networks (MANET), mobile devices, tablets, and legacy hardware radio platforms.

The software must support real-time collaboration through messaging, file sharing, video conferencing, and virtual meeting rooms. It must provide advanced analytics and reporting capabilities and include end-to-end encryption. The Army seeks to streamline communication across multiple channels, including voice, video, chat, and collaboration tools, to enhance productivity and collaboration while integrating seamlessly with existing enterprise applications.

This requirement supports Command and Control Network Optimized for Warfighting (C2NOW) fielding and will affect units currently using unified voice communications platforms across the active Army network. The procurement of a unified communications software platform is projected to be an enduring, mission-critical requirement to ensure the safety, operational effectiveness, and real-time connectivity of warfighters. Once procured, this will be a recurring annual requirement.

https://dodcio.defense.gov/CMMC/

For complete technical requirements, refer to the Statement of Objectives (SOO) posted with this Call for Solutions.

3. PROBLEM STATEMENT

The Army's current communications architecture requires a mature commercial solution to address the following challenges:

• Fragmented Systems: Multiple, disconnected communication platforms hinder the ability to bridge legacy and modern systems into a single, integrated voice environment.

• Limited Interoperability: Lack of seamless interoperability between various communication systems and platforms.

• Operational Inefficiencies: Difficulty in creating and managing talk groups, patching channels, and collaborating in real-time.

• Data Integration: Need for effective transcription, logging, and analysis of communications for integration into data systems.

• Scalability: Requirement for solutions that scale from small tactical teams to large-scale deployments.

4. DESIRED SOLUTION OBJECTIVES

The Army seeks a mature, commercially available software solution that meets the performance objectives and requested capabilities detailed in the SOO. Key solution characteristics include:

• System and hardware agnostic architecture

• Multicast stream ingestion capability

• Voice over IP (VoIP) interoperability

• Dynamic talk group management

• Scalability from small teams to large formations

• Mobile device integration

• Offline/disconnected operation capability

• Server-based and serverless client options

• Modular, cloud-native microservices architecture

• Kubernetes-based container deployment

• Access control and auditing capabilities

• Operationally ready to deploy

Offerors must review the SOO for complete performance objectives and requested capabilities.

5. AWARDING INSTRUMENT

This Call for Solutions will be awarded in accordance with the Army Open Solicitation procedures detailed within Solicitation W9128Z-25-S-A002, posted to SAM.gov.

Preferred Contract Type:

The Government's preference is to award a Firm-Fixed-Price (FFP) using FAR Part 12 commercial procedures as a result of this Call for Solutions. The Government anticipates awarding an Indefinite Delivery/Indefinite Quantity (IDIQ) contract with a 5-year ordering period.

The Government reserves the right to award using other appropriate contract types or any other authorities specified in the Army Open Solicitation.

6. SOLICITATION NOTES

In addition to the general guidelines included in the Open Solicitation, the following guidelines apply to this Call for Solution:

• Offerors are responsible for monitoring SAM.gov for any amendments to this solicitation that may have updated information.

• Academic research proposals are not desired.

• The Solution Brief must identify any intellectual property involved in the effort and associated restrictions on the Government's use of that intellectual property.

• The Government reserves the right to go directly from Solution Brief to award.

• The Government reserves the right to award more than one (1) award resulting from this Call for Solution or to make no award.

7. GENERAL INFORMATION AND QUESTIONS

Questions are to be sent only to the Contracting Officer and Contract Specialist (POCs) listed in this Call for Solutions. The following shall be utilized in the email subject line:

"Call for Solutions – [CALL Number] – Question – [Your Company Name]" Material questions and answers will be published and updated on www.sam.gov as amendments to this solicitation.

Deadline to submit questions for Step 1:

24 April 2026, 0900 hours Eastern Daylight Time (EDT)

8. SOLUTION SUBMISSION REQUIREMENTS

Companies responding to this Call for Solutions shall submit a White Paper for evaluation. Submissions are to be sent via email only to the Contracting Officer and Contract Specialist (POCs) listed in this Call for Solutions.

8.1 Evaluation Process Overview

The Government will utilize up to three (3) steps for assessing solutions:

http://www.sam.gov/

Step Description

Step 1: White Paper A written submission addressing how the proposed solution meets the requirements in the SOO and the evaluation criteria in this Call for Solutions.

Step 2: Demonstration An oral briefing and technical demonstration. The Government reserves the right to bypass this step when it is in the best interest of the Government.

Step 3 - Award Contract award based on evaluation results.

8.2 Step 1: White Paper Submission Requirements:

Each White Paper shall not exceed ten (10) written pages (not including the title page, company information, table of contents, Data Rights Assertion, Rough Order of Magnitude pricing, or OCI Analysis).

Format Requirements:

• Font: Minimum 11-point, readable without magnification

• Paper size: 8.5 x 11 inches (landscape graphics permitted within page count)

• Margins: Minimum 1 inch on all sides

• Use of diagrams or graphics with associated text to depict the proposed solution is encouraged. Any pages exceeding the 10-page limit will be removed and not evaluated.

8.2.1 Company Information (Not included in 10-page limit; maximum 2 pages)

Item Required Information

a. Program/Project Name: Unified Communications Software Platform Licensing

b. Issuing Organization: PM C2 Data & AI, PEO C3T

c. Company Name d.

Business Size and Socioeconomic Status (e.g., Small Business, SDVOSB, 8(a), HUBZone, WOSB, Large Business)

e. Commercial and Government Entity (CAGE) Code

f. Unique Entity Identifier (UEI)

g. Contracting Point of Contact (Name, Phone, Email)

h. Technical Point of Contact (Name, Phone, Email) i.

Gate Criteria 1 Response: Commercial Unified Communications Solution Reference (see Section 10.1.1)

8.2.2 Technical Solution (Included in 10-page limit)

The Technical Solution shall address the following:

1. Solution Overview:

Provide a clear description of the proposed commercial software solution, including its name, version, and key components.

2. Requirements Compliance:

Describe how the proposed solution meets the performance objectives and requested capabilities in the SOO. Offerors should address each requirement area and indicate full compliance, partial compliance, or non-compliance with explanation.

3. Solution Maturity:

Describe the current maturity and commercial availability of the solution. Provide evidence of successful deployment in commercial and/or government environments.

4. Architecture:

Describe the solution architecture, including how it meets the modular, cloud-native, and Kubernetes-based deployment requirements.

5. Integration Approach:

Describe how the solution will integrate with existing Army systems and infrastructure.

6. Deployment Approach:

Describe the approach and timeline to meet the Government's deployment requirements as specified in the SOO.

7. Training and Support:

Describe the training approach and ongoing support services included with the solution.

8. GFP/GFE/GFI Requirements:

Identify any Government Furnished Property, Equipment, or Information required to support deployment.

9. Direct Ownership/Control over proposed capability The Government is particularly interested in solutions offered by entities that have direct ownership or control over the development, innovation, and support of the proposed capability. Offerors must clearly state whether they are the original provider (i.e., the developer or manufacturer) of the capability or are acting as an intermediary, such as a reseller, integrator, or distributor. Offerors who are not the original provider must explicitly describe the value they add beyond what is available from the primary source, including but not limited to unique integration, customization, or support services. This added value must go beyond the original provider’s offering and provide a clear, quantifiable return on value to the Government, such as measurable cost savings, enhanced performance, or other tangible benefits. The Government will evaluate whether the added value justifies any additional costs or complexity introduced by the intermediary relationship.

8.2.3 Data Rights Assertion (Not included in 10-page limit; maximum 2 pages)

The Offeror shall identify all proposed intellectual property restrictions, particularly those relating to key interface data within the system.

As stated in the SOO, the Government is seeking Government Purpose Rights (GPR) in pre-existing contractor proprietary key interface data to competitively procure maintenance/sustainment services and/or integrate enhancements from a third party in the future.

Offerors shall:

• Identify all data rights assertions for technical data and computer software

• Explain any restrictions on the Government's use of the solution

• If GPR is not offered for key interface data, propose an alternative approach the

Government can use to competitively procure maintenance/sustainment services

• Include information on software license agreements, API specifications, and

SDKs available for the platform

8.2.4 Rough Order of Magnitude (ROM) Pricing (Not included in 10-page limit;

maximum 2 pages)

Provide a ROM price estimate against the delivery schedule in the SOO:

Item Quantity Delivery Date

Licenses – Base Year 950 server/ 23,750 Mobile 1-Jun-26

Licenses – Ordering Year 1

2,540 Server / 63,500 Mobile 1-Jun-27

Licenses – Ordering Year 2

4,479 Server / 111,975 Mobile 1-Jun-28

Licenses – Ordering Year 3

5,246 Server / 131,150 Mobile 1-Jun-29

Licenses – Ordering Year 4

5,246 Server / 131,150 Mobile 1-Jun-30

Support Services N/A Full Period of Performance (5 years)

Travel N/A Full Period of Performance (5 years)

The ROM shall include:

• Yearly software license costs

• Associated maintenance and support costs

• Any other recurring or non-recurring costs

• Pricing model, discount description

8.2.5 Organizational Conflict of Interest (OCI) Analysis (Not included in 10-page limit) The Offeror shall perform an OCI analysis and submit the results in addition to the White Paper submission.

Specifically, the Offeror shall:

• Analyze the planned acquisition for actual or potential OCI situations associated with the Offeror or any proposed teammates or subcontractors

• Describe in detail the methodology used to identify actual or potential OCI issues

• If any actual or potential OCIs are identified, provide an OCI Mitigation Plan

Any proposed avoidance or mitigation techniques shall be consistent with FAR 9.5 and the most recent decisions of the Government Accountability Office (GAO) and the U.S.

Court of Federal Claims

9. NON-GOVERNMENT ADVISORS

For this Call for Solutions, the Government does not anticipate using non-government advisors to assist with the evaluation in step 1. However, if non-government advisors are used in subsequent phases, their involvement will be specified in the invitation letter.

10. EVALUATION CRITERIA

10.1 Step 1 White Paper Evaluation: White Papers will first be evaluated against the following gate criteria. Submissions must meet both gate criteria to be eligible for full evaluation:

10.1.1 Step 1 White Paper – Gate Criteria

Gate Criteria Requirement

Gate 1: Commercial Solution Experience

Submission includes at least one (1) referenceable program or project demonstrating current or past experience providing a commercial unified communications or VoIP software solution to commercial or government customers.

Gate 2: Solution Maturity

Submission demonstrates that the proposed solution is a mature, commercially available product that is currently deployed and operationally ready. Solutions that are concepts, prototypes, or in development are not acceptable.

Submissions that do not meet both gate criteria will be deemed "Not Selectable" and will not be further evaluated.

10.1.2 Step 1 White Paper – Full Evaluation Criteria

Factor Description

Technical Capability

Degree to which the proposed solution meets the performance objectives and requested capabilities in the SOO. Includes solution architecture, integration approach, and deployment readiness.

Solution Maturity & Past Performance Evidence of successful commercial deployment and operational use. Includes references, customer base, and track record of reliability and performance.

Data Rights

Degree to which the proposed data rights support the Government's ability to competitively sustain and enhance the solution.

Price Reasonableness of the proposed ROM pricing relative to the scope, complexity, and technical approach of the proposed solution.

10.1.3 Evaluation Ratings

Based on the evaluation, the White Paper will be categorized as ‘Selected for Further Consideration’ or ‘Not Selected for Further Consideration’. Selection into the next Phase will be based on the criteria listed above, Government Need, and funding availability.

Selected for Further Consideration: The submitted White Paper has been determined to be of technical merit, represents a feasible and achievable schedule, and included all required submittals in accordance with the Call. As such, the Government intends to invite the Company to participate in next phase should funding be available.

Not Selected for Further Consideration: The submitted White Paper does not represent the necessary degree of technical merit, does not represent a feasible and achievable schedule, and/or did not include all required submittals in accordance with the Call.

Offerors ‘Selected for Further Consideration’ may be invited to participate in subsequent phases, subject to the availability of funds. The Government reserves the right to limit the number of offerors invited to Phase 2 – Pitch Session (unless bypassed) and/or Phase 3 – Solution Proposal. As such, an Offeror’s solution may be evaluated as ‘Selected for Further Consideration’, however, not invited to Phase 2 and/or Phase 3. White Papers, whether selected or not selected for subsequent Phases, will be notified in writing as soon as practicable of their evaluation results.

10.1.4 Evaluation Process

White Papers are evaluated by a panel of Government subject matter experts (SMEs).

In conformance with Section I of the Army Open Solicitation, non-Government advisors may also participate in the evaluation.

During the evaluation period, the Government and/or supporting evaluators may contact submitting companies to request clarifications on submitted information.

Solutions submitted in response to this Call for Solutions will be evaluated based on merit of the solution against the requirements, not against other solutions submitted in response to this Call for Solutions.

The evaluation panel will provide recommended ratings and comments for each White Paper to the designated Decision Authority, who is responsible for determining the final Selectable/Not Selectable status of each submission.

The Government will notify all companies whether they have or have not been selected to proceed. Companies whose White Papers are deemed "Selectable" will be invited to participate in Step 2: Demonstration or, at the Government's discretion, may proceed directly to Step 3 Award.

10.2 Step 2: Demonstration (Unless Bypassed)

The Government reserves the right to bypass Step 2 and proceed directly from Step 1 to Step 3 when it is in the best interest of the Government.

Factors that may lead to bypassing Step 2 include, but are not limited to:

• The White Paper clearly demonstrates a mature, proven solution with verifiable references

• Schedule urgency to meet deployment requirements

• The solution has been previously demonstrated to or deployed by the

Government

• Sufficient information is available from the White Paper to make a selection decision

10.2.1 Demonstration Overview

If Step 2 is conducted, selected offerors will be invited to provide an oral presentation and technical demonstration of their proposed solution. Detailed instructions, including demonstration scenarios, evaluation criteria, schedule, and logistics, will be provided in the invitation to demonstrate following Step 1 selection notification.

The Demonstration is anticipated to include:

1. Oral Presentation: Overview of the solution, technical approach, and implementation plan.

2. Technical Demonstration: Live or simulated demonstration of key capabilities as specified in the SOO.

3. Question & Answer Session: Government evaluators will ask clarifying questions.

4. Updated Pricing and Schedule: Offerors will provide an updated ROM and proposed delivery schedule.

The Government will evaluate submissions based on the factors outlined in Section

10.1. To allow flexibility in accommodating the best method for evaluating all solutions in

Step 2, the content of Sections 10.2.2 will be provided in an invitation letter to those Offerors selected to proceed to Phase 2 (unless bypassed).

10.2.2 Step 2: Evaluation

See above Section.

10.3 Step 3: Award

Based on the Government's evaluation of Step 1 (and Step 2, if conducted), the Government may select one or more vendors for potential contract award.

For selected offeror(s), the Government will:

1. Request detailed information including:

o Final technical proposal o Detailed pricing proposal with supporting documentation o Delivery schedule o Final data rights assertions o Representations and certifications required by FAR Part 12

2. Conduct negotiations as necessary

3. Award a FAR Part 12 commercial contract (anticipated IDIQ with FFP task orders)

The RFP or negotiation letter will include specific submission requirements and evaluation criteria for final selection.

11. ANTICIPATED SCHEDULE

Milestone Anticipated Date

Call for Solutions Posted to SAM.gov

17 April 2026

Deadline for Questions (Step 1) 24 April 2026

White Papers Due (Step 1) 30 April 2026

Step 1 Evaluation Complete (Target)

04 May 2026

Step 2 Demonstrations (if conducted)

15 May 2026

Step 3 Award Negotiations 25 May 2026

Anticipated Contract Award 29 May 2026

12. ADDITIONAL INFORMATION

12.1 Security Requirements

Security requirements, if any, will be identified during Step 3 negotiations and included in the resulting contract.

12.2 Place of Performance

Place of performance shall be primarily at Offeror facilities. Travel to Government facilities within CONUS and OCONUS may be required. Refer to the SOO for anticipated places of performance.

13. ATTACHMENTS

Attachment Title Classification

Attachment A

Statement of Objectives (SOO) – Unified Communications Software Platform Licensing

CUI – Handle IAW marking instructions