ASA(ALT) AOS Call for Solutions - ADN - 20260130.pdf

Call for Solution for

Assistant Secretary of the Army for Acquisition, Logistics, and Technology

[ASA(ALT)],

Chief Automation and Data Integration Office

(CADIO)

Call Reference Number: ASA(ALT)_26-01 Army Open Solicitation (AOS) Number: W9128Z-25-S-A002 Call for Solution Title: Acquisition Data Nexus (ADN) Requiring Activity: ASA(ALT) CADIO Issued By: Army Contracting Command – Aberdeen

Proving Ground (ACC-APG), Digital Capabilities Contracting Center of Excellence (DC3oE)

Submission Instructions: To respond to this Call for Solution, please refer to Section 6 of this Call for Solution.

*Solution Briefs Due Date/Time (Suspense)

FEB 27, 2026, 1:00PM Eastern Time

(ET)

Points of Contact (POCs) for Solution Brief Submission:

Contracting/Agreements Officer:

Kristen Weiman kristen.l.weiman.civ@army.mil

Contract Specialist:

Thomas Lueddeke thomas.j.lueddeke.civ@army.mil

Note 1: Please advise the Contracting Office as soon as possible via the Microsoft Forms link if your organization intends to submit a Solution Brief in response to this Call for Solution. The Forms link can be found in the “Links” section of the SAM.gov posting.

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

1. BACKGROUND

The Army's acquisition enterprise currently operates within a fragmented data environment where Portfolio Acquisition Executives (PAEs), their subordinate Capability Program Executives (CPEs) and further Program/Project/Product Managers (PMs) manage complex portfolios using disconnected systems and manual processes.

Acquisition professionals across multiple PAEs must navigate numerous authoritative data systems such as the Program Management Resource Tool (PMRT), Virtual Contracting Enterprise (VCE), and Army Contract Writing System (ACWS), while working their own internal business processes. These stakeholders require timely, accurate program data to make critical decisions regarding capability delivery, resource allocation, and risk management. However, the current environment forces users into repetitive manual data entry across multiple platforms, creating inefficiencies, increasing technical debt, and hindering portfolio-level analysis. The lack of integrated identity management and standardized data exchange mechanisms further compounds these challenges, preventing the Army from leveraging its acquisition data as a strategic asset for accelerated capability delivery. The Acquisition Data Nexus (ADN) initiative seeks to establish a modern, layered architecture that separates enterprise-wide data integration services from PAE-specific business applications, enabling both standardization and innovation.

2. PROBLEM STATEMENT

The Army acquisition community faces a critical capability gap in efficiently managing, integrating, and utilizing program data across the enterprise. Acquisition professionals spend excessive time on manual data entry and "swivel chair" operations between disconnected systems rather than focusing on analysis and decision-making. This fragmented approach prevents PAEs and PMs from rapidly implementing tailored business processes specific to their portfolio needs while maintaining data integrity in authoritative systems. The current state lacks both a unified enterprise data integration backbone and a framework that allows different acquisition organizations to define and execute their unique workflows. Each PAE has distinct business processes— Command and Control/Counter Command and Control (C2/CC2) operates differently than Maneuver Ground or Fires—yet all must ultimately feed data into the same authoritative Army systems. Success would be achieved when a secure, enterprise-wide data brokerage layer handles all integration with authoritative systems, abstracting this complexity from users, while simultaneously enabling PAEs to rapidly develop and deploy their own mission-focused applications that leverage this data backbone. The desired end-state is an environment where digital tools and live data become the standard for all acquisition activities, enabling data-driven decisions at speed and scale while eliminating redundant manual processes and duplicative integration efforts.

3. REQUIRED SOLUTION ATTRIBUTES

A successful solution must possess the following key attributes:

For Data Brokerage Layer Solutions (Enterprise-Wide Integration Services):

• Seamless bidirectional integration with Army authoritative acquisition systems including PMRT, VCE, and ACWS through Application Programming Interfaces (APIs) and modern data exchange protocols

• The solution must be deployable in cARMY environments and meet Department of Defense (DoD) Impact Level 5 (IL5) security requirements

• Integration with Army Identity, Credential, and Access Management (ICAM) systems to enable role-based access control and permissions management across the enterprise

• Capability to enforce flexible business rules that allow users to view and edit data based on their organizational assignment and program responsibilities

• Support for dynamic data orchestration that can route information to appropriate authoritative systems based on data type and approval workflows

• Scalable architecture that can accommodate multiple PAEs and their subordinate programs simultaneously

• Functions as a secure API-driven data backbone that abstracts users and applications from direct interface with authoritative systems

• Allows seamless integration of innovative Artificial Intelligence (AI) capabilities

• Does not include visualization or user-facing application interfaces—focuses solely on data integration, orchestration, and access management

For Application and Automation Layer Solutions (PAE-specific Business Process Tools):

• Intuitive interface that enables PAEs to define and rapidly implement their own business processes and workflows without extensive technical expertise

• The solution must be deployable in cARMY environments and meet DoD Impact Level 5 (IL5) security requirements

• Flexibility to accommodate different business processes across various acquisition domains while maintaining data standardization

• Capability to connect with the data brokerage layer to retrieve data from and send approved data to authoritative systems

• Support for workflow automation that reduces manual data entry and streamlines approval processes within PAE-specific business operations

• Ability to provide users with relevant data visibility while maintaining appropriate access controls

• Enables PAEs to govern their own portfolio management tools and applications independently

• Allows seamless integration of innovative AI capabilities

For Combined Solutions (Data Brokerage Layer & Application and Automation Layer):

• All attributes listed above for both layers, plus demonstrated interoperability and clear architectural separation between the application layer and data brokerage layer components

• Clear delineation showing how the application layer leverages the data brokerage layer for all authoritative system integration

For Novel Solutions to the Above or Army Acquisition Enterprise Challenges:

• Combine attributes of any of the above for solutions to perceived public, Army, or unit-level acquisition to drive speed, agility, and accountability

(Figure 1) Focus of this Call is for the Data Brokerage Layer and the Application and Automation Layer

4. AWARDING INSTRUMENT

In accordance with Army Open Solicitation Procedures detailed within W9128Z-25-S- A0021, the Government intends to award FAR Part 12, Firm-Fixed-Price (FFP) type contract(s) as a result of this Call; however the Government also reserves the right to award Other Transaction(s) (OT) for Prototype Project(s) pursuant to 10 United States Code (U.S.C.) § 4022. The Government further reserves the right to award to all, some, or none of the companies who submit proposals. This Call for Solution will utilize Commercial Solutions Opening (CSO) procedures. Use of a CSO in accordance with Defense Federal Acquisition Regulation Supplement (DFARS) subpart 212.70 is considered to be a competitive procedure for the purposes of 10 U.S.C. chapter 221 and FAR subpart 6.102.

5. GENERAL 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.

• Resellers and academic research proposals are not desired.

• All Solution Briefs will be valid for 180 calendar days after the submission date.

1 https://sam.gov/workspace/contract/opp/c7316940150a42f39600ac8cf5b6b34d/view

Visualization Layer Visualization Tools and Platforms

Authoritative Layer PMRT and other Army Authoritative Systems and Data

1. Data Brokerage Layer Integration Services, Data Orchestration, Semantic Support, AI Inference

2. Application & Automation Layer PAE Applications, Workflow Automation, Business Processes

Cross- Cutting

Services

ICAM

cARMY etc.

(Existing) https://sam.gov/workspace/contract/opp/c7316940150a42f39600ac8cf5b6b34d/view

• The Government may down-select potential awardees under this call for solution.

• The Government reserves the right to issue multiple awards from this Call for

Solution. It similarly reserves the right to refrain from making any award.

• Submittals must use a standard, readable font (i.e., not requiring magnification), as the document's readability directly impacts the Government's ability to assess the merits of the proposed solution. Offerors are strongly encouraged to use diagrams, graphics, and concise text to effectively convey complex information.

For this purpose, landscape-oriented (11 x 8.5 inch) pages are permissible for visuals but will be counted toward the total page limit, which is strictly enforced.

Any pages submitted beyond the maximum allowed will be removed by the Government and will not be evaluated.

• The Government may utilize internal AI tools to assist in the administrative review and analysis of proposals, such as by summarizing content or verifying compliance with solicitation requirements. However, the use of AI is strictly for support purposes; all final evaluation judgments, the assignment of ratings, best value determinations, and the ultimate source selection decision are inherently governmental functions that will be made exclusively by Government personnel.

The Government is committed to protecting all offeror proprietary and source selection sensitive information, and any AI tool used will operate in a secure environment, consistent with all applicable data protection regulations, and will not transmit data to external systems.

• Questions are to be sent only to the Contracting/Agreements Officer and Specialist (POCs) listed in this Call for Solution by FEB 13, 2026 @ 1:00 PM ET.

The following shall be utilized in the email subject line: "Call for Solution —

ASA(ALT)_26-01".

6. SOLUTION SUBMISSION AND EVALUATION PROCESS

The Government is interested in unique and innovative solutions, including techniques to reduce costs, improve efficiency, and enhance performance. The Government will utilize up to three (3) phases for assessing solutions:

Phase 1 – Solution Brief:

For Phase 1 of this acquisition, offerors shall submit a Solution Brief. The brief is a written technical submission that must provide a detailed discussion explicitly addressing the technical merit of the commercial solution offering with respect to the problem statement defined herein, using the content guidelines in Section 6.1.

Furthermore, the submission must clearly articulate how the proposed solution meets the Government's objectives and satisfies the evaluation criteria detailed in Section 6.2.

All Solution Briefs will be evaluated against these criteria. Offerors are advised that the Government will not reimburse any costs incurred in the preparation or submission of a Solution Brief.

Phase 2 – Pitch Session (Unless Bypassed):

Offerors whose Phase 1 Solution Briefs that demonstrate technical merit, satisfy the minimum evaluation criteria, and are selected to proceed may be invited to participate in a Phase 2 Pitch Session. The Government reserves the right to limit the number of offerors invited to pitch. As such, an offeror’s solution may be evaluated to be of merit, however not invited to pitch.

If conducted, the Pitch Session may include a technical demonstration or challenge, and specific instructions will be provided to selected participants. The Government reserves the right to record all pitch sessions for evaluation purposes. Furthermore, the Government reserves the right, at its sole discretion, to bypass Phase 2 entirely and proceed to an award decision based on the Phase 1 submission. Unless otherwise stipulated, the Government will not reimburse offerors for any costs associated with preparing for or participating in the Pitch Session.

Phase 3 – Solution Proposal:

Following the completion of the preceding evaluation phase(s), the Government may issue an invitation to select offerors to submit a full Request for Solution Proposal (RSP). The invitation for Phase 3 will provide detailed instructions on the required format and content for the solution proposal submission. Unless otherwise stipulated, the Government will not reimburse offerors for any costs associated with preparing the Solution Proposal or engaging in any subsequent negotiations. Furthermore, offerors are advised that any potential award resulting from this solicitation is contingent upon the availability of Government funds and need.

6.1 PHASE 1 – SOLUTION BRIEF

6.1.1 SOLUTION BRIEF CONTENT

Companies responding to this Call shall submit a Solution Brief for evaluation.

Submissions are to be sent via email only to the Contracting/Agreements Officer and Specialist (POCs) listed in this Call for Solution.

Solution Briefs shall follow the below-referenced page limits and use 12-point Arial font.

Any pages exceeding the limit will be removed and not evaluated. The Government will not consider inserted textboxes/pop-ups or internet links to additional information as part of the Solution Brief and will not consider such information in its evaluation of submissions. Solution Briefs are intended to be clear, concise and succinct submissions.

Solution Briefs shall include the following at a minimum:

a. Title Page (one-page limit)

i. Offeror Name, Call Title, Date, Point of Contact Name, POC Title, E-Mail

Address, Phone, Address, and Call reference number. If registered in SAM.gov, include the Commercial and Government Entity (CAGE) code, and Unique Entity Identification (UEI) code. Note: SAM registration is required for any award.

ii. Ensure to clearly identify the Call for which the Solution Brief is submitted.

b. Executive Summary (one-page limit)

i. Provide an executive summary of the offeror and its solution.

c. High-Level Solution/Concept (eight-page limit)

i. Explain the unique technical aspects of your solution, its relevance to this

Call, and how it is innovative or represents a potential capability. Highlight how the solution addresses the problem statement and required solution attributes.

ii. Describe the capabilities of your solution, its scalability, and the specific benefits it offers in relation to the objectives of this Call.

iii. Provide a detailed explanation of the technical approach, demonstrating its feasibility and achievability. Address how the solution will meet the Army’s hosting and security requirements, including whether an Authority to Operate (ATO) is currently held or able to be achieved. Include information about the technical team’s expertise and experience to successfully implement the proposed solution.

iv. Indicate whether the solution includes a pilot or demonstration of existing commercial technology or involves the development of technology for defense applications. Identify the DoD Technical Readiness Level (TRL) and, if applicable, discuss the path to maturity for developmental or adapted technologies.

d. ROM/Schedule (Limit of one page for ROM, and one page for Schedule)

i. Rough Order of Magnitude (ROM): The ROM must contain the breakout of pricing. Tie pricing to milestones, where appropriate. Annotate assumptions used to develop the ROM.

ii. Notional Schedule: The notional schedule must contain a project schedule outlining major tasks, milestones, and/or timeline for delivering the proposed solution. Annotate assumptions used to develop the schedule.

e. Affirmation of Business Status Certification (two-page limit each, using Appendix A template; incorporate in the single .pdf submission)

i. The offeror shall include a separate Affirmation of Business Status Certification form (Appendix A) for each company/vendor participating in the proposed solution Call submission.

f. Intellectual Property Statement/Agreement/Disclosures (no page limit)

i. The Solution Brief must identify any intellectual property associated with the proposed solution, and the associated restrictions on the Government’s use of that intellectual property. DFARS subpart 252.277- 7017(d) shall be used for formatting, to include the signature of an official authorized to contractually obligate the offeror. As needed, include a separate disclosure for each company that would be a participant of the solution/concept.

g. Non-Government Advisor Non-Disclosure Agreements (NDAs) (Only as applicable and no page limit)

i. See Section 7 of this Call.

ii. It is the sole responsibility of industry to independently execute NDAs with disclosed Non-Government Advisor under Section 7.

h. Organizational Conflict of Interest (OCI) Analysis and Mitigation Plan (As applicable, no page limit)

i. See Section 8 of this Call.

The Government may be unable to evaluate the Solution Brief if a Company fails to submit the required contents for Phase 1. For ease of evaluation, please include ALL sections (a. through h.) in one (1) .pdf submission.

6.1.2 SOLUTION BRIEF BASIS FOR EVALUATION

The Government intends to evaluate the Solution Briefs to determine if they have technical merit and address the Government’s problem statement and required attributes. Solution Briefs submitted IAW with this Call for Solution will be evaluated against the criteria in this Section. The Government reserves the right to use external market research in the evaluation of an Offeror. The Government reserves the right to select all, some, or none of the Solution Briefs submitted IAW this Call to proceed to subsequent phases.

Evaluation criteria in this section are listed in descending order of importance:

a. Technical Merit: The Government will evaluate the Technical Merit of an Offeror’s Solution Brief. Technical Merit is defined as the solution’s direct relevance to the Call for Solution, its ability to address the problem statement and required solution attributes, and/or its potential to provide innovative technological advancements. As part of Technical Merit, the evaluation will consider the scalability of the solution, its benefits in relation to the problem statement and required attributes of this Call, and whether the technical approach is both feasible and achievable. Additionally, the Government will assess whether the proposed solution constitutes a compelling and innovative response to the Call for Solution.

If the Offeror’s solution is evaluated as not having Technical Merit, the Government reserves the right to not continue the evaluation for the remaining Evaluation Criteria, assigning an overall Solution Brief rating of ‘Not Selected for Further Consideration’.

b. Schedule: The Government will evaluate the Offeror’s proposed solution schedule, major tasks, milestones, timeline, and/or maturity path for feasibility and achievability.

c. ROM: The Government will evaluate the ROM for compliance with the Call’s instructions only. Cost and/or Price evaluation, and Fair and Reasonable Price determination, will not be performed on the ROM for Phase 1 evaluation.

d. Intellectual Property (Data Rights): The submitted IP and Data Rights assertions will be evaluated based on compliance with DFARS 252.227-7017, and the instructions in this Call.

6.1.3 SOLUTION BRIEF SELECTION PROCESS

Based on the evaluation, the Solution Brief 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 Solution Brief 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 Solution Brief 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.

Solution Briefs, whether selected or not selected for subsequent Phases, will be notified in writing as soon as practicable of their evaluation results.

6.2 PHASE 2 – PITCH SESSION

All Solution Briefs submitted IAW this Call will undergo a fair, impartial, and consistent evaluation in accordance with the stated criteria. The Government anticipates disparate innovative solutions in response to this Call, to include Solutions or Concepts that the Government had not previously explored. To allow flexibility in accommodating the best method for evaluating all solutions in Phase 2, the content of Sections 6.2.1 through

6.2.3 will be provided in an invitation letter to those Offerors selected to proceed to Phase 2 (unless bypassed).

6.2.1 PITCH SESSION CONTENT

See above Section.

6.2.2 PITCH SESSION BASIS OF EVALUATION

See above Section.

6.2.3 PITCH SESSION SELECTION PROCESS

See above Section.

6.3 PHASE 3 – SOLUTION PROPOSAL

The content of Sections 6.3.1 through 6.3.3 will be provided in an invitation letter to those Offerors selected to proceed to Phase 3.

6.3.1 SOLUTION PROPOSAL CONTENT

See above Section.

6.3.2 SOLUTION PROPOSAL BASIS OF EVALUATION

See above Section.

6.3.3 SOLUTION PROPOSAL SELECTION PROCESS

See above Section.

7. NON-GOVERNMENT ADVISORS

As stated in Section I2 of the AOS, non-Government advisors may be used in the evaluation of Solution Briefs, Pitch Sessions, and Solution Proposals, and negotiation of said Proposals. For this Call, the Government anticipates using non-Government advisor(s) from the following contractors:

No Non-Government Advisors are identified at this time. If Non-Government Advisors are deemed necessary post-Phase 1 evaluations, the Government will give advanced notice to the selected offerors.

Non-Government advisors will have signed non-disclosure agreements (NDAs) with the Government. By submitting a Solution, the Offeror understands that the Government may share proprietary Company information with the identified non-Government advisor(s) for evaluation and administrative purposes only. In addition, the Offeror further understands that it has an opportunity before submitting a Solution Brief to the Government to enter an NDA directly with the Non-Government advisor(s), and therefore waives all claims against the Government for any disclosures of proprietary information by the non-Government personnel. Such NDAs are the responsibility of the Offeror, and the Government shall not be a party to them. Companies shall provide a copy of the signed NDAs to the Government with submissions.

8. ORGANIZATIONAL CONFLICT OF INTEREST (OCI)

The Offeror shall perform an OCI analysis and submit the results of that analysis in addition to the Solution Brief submission. Specifically, the Offeror shall analyze the details of the Call and the implementation of their proposed Solution for actual or potential OCI situations associated with the performance of the Offeror, or any of the Offeror’s proposed teammates or subcontractors, under any contract or agreement the Offeror or the Offeror’s teammates or subcontractors have been or may be awarded by any federal agency or other entity. The Offeror shall describe in detail the methodology used to identify actual or potential OCI issues. The level of detail for OCI analysis may not be the same for all vendors. FAR 9.5 may be used as guidance for OCI analysis. If no conflicts are identified, a risk mitigation plan is not required; however a description of the analysis methodology, and an affirming statement that no conflicts are identified shall be included.

2 Attachment titled “Army Open Solicitation_3 December 2025.pdf” on the main AOS SAM.gov posting.

If the Offeror identifies any actual or potential OCIs with respect to the performance of the Offeror or the Offeror’s subcontractors or teammates, the contractor shall provide an OCI Mitigation Plan to be incorporated as an attachment to any resulting contract or agreement. 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.