B01 - RFI_EBS-Application Ecosystem_v5_2026-01-301.pdf

UNCLASSIFIED

LCNC Application Ecosystem RFI

February 2026

Low Code No Code (LCNC)

Logistics and Finance Application Ecosystem

Request for Information (RFI)

U.S. Army Contracting Command – Rock Island (ACC-RI)

3055 Rodman Avenue Rock Island, IL 61299-0001 i

THIS PAGE INTENTIONALLY LEFT BLANK

ii

Table of Contents

1.0 Purpose

2.0 Background

3.0 Objectives

4.0 Requested Information

4.1 Company Profile

4.2 Application Type and Data Model

4.3 Domain Expertise/Areas of Interest and Operational Impact

4.4 Experience with the Army’s Approved Platforms

4.5 Proposing an Alternative (non-APL) Platform

4.6 Partnering for Rapid Acquisition

4.7 Driving Mission Advantage through Innovative Technologies

4.8 Security and Interoperability Standards

4.9 Illustrative Cost and Schedule

5.0 Submission Instructions

6.0 Appendices

6.1 Appendix A: Current Army ERP Systems

6.2 Appendix B: The EBS-C Value Chains

6.3 Appendix C: EBS-C Solution Architecture

6.4 Appendix D: References

6.5 Appendix E: Approved Product List

1.0 Purpose

The Army Contracting Command – Rock Island (ACC-RI), on behalf of PEO Enterprise and the Project Manager, Enterprise Business Systems – Convergence (PM EBS-C), requests information from industry regarding capabilities, interest, and approaches to develop, host, integrate, and sustain Low-Code/No-Code (LCNC) applications that support Army logistics and finance communities. The Army is committed to fostering innovation and collaboration with industry, including non-traditional contractors, to develop solutions that align with modernization goals. Vendors who may not have a fully developed solution but have the capability, interest, and willingness to develop applications tailored to Army needs are encouraged to respond.

Vendor input will be used to inform the acquisition approach, technical requirements, integration strategies, and potential enterprise adoption consistent with Army LCNC guidance.

Disclaimer: This RFI is issued solely for market research purposes and does not constitute a solicitation or a commitment to issue a solicitation in the future. Responses to this notice are not offers and cannot be accepted by the Government to form a binding contract. Any information submitted by respondents to this RFI is strictly voluntary. Respondents are responsible for all costs associated with response preparation. Responses will not be returned to the responder. Information received in response to this RFI shall be safeguarded adequately from unauthorized disclosure.

2.0 Background

The Army is undergoing a major modernization effort to establish a Common Business Operating Environment (CBOE) with EBS-C converging the current Army SAP ERP systems (Appendix A). This modernization effort includes assessing and migrating operational value chain processes (Appendix B) to enable:

1. Supply Chain Simplification

2. Process Automation

3. Resilient and Secure Infrastructure

4. Agility to Support Maneuvers

5. Scalability to Adapt to Future Demands

6. Auditability to Maintain Transparency, Traceability, and Accountability

The key elements of the CBOE are captured in the EBS-C architecture diagram (Appendix C), which includes the:

• Transactional Core Layer: The foundation of the system using SAP S/4HANA and provides stable, governed, and reliable processing of all core business transactions (e.g., financials, procurement, logistics, HR, and manufacturing).

• Engagement Layer: Facilitates all user interactions.

• Agility Layer: Enables unique business processes and business workflows to avoid building customization of the Transactional Core.

• Integration Layer: Ensures reliable, real-time flow and transformation of data between the Transactional Core, the Agility Layer, and external systems.

A key aspect of the EBS-C architecture is the support of an application ecosystem to augment EBS-C capabilities at the operational level. LCNC solutions will play a critical role in modernizing hundreds of defense business systems that perform routine, non-transactional functions (analytics and decision support tools) or transactional functions that integrate with ERP systems. These solutions will leverage APIs to authoritative data sources and align with the Army CIO Low-Code/No-Code Development Guidance (Appendix D). Additionally, these solutions must align with the Army Unified Data Reference Architecture (UDRA) to emphasize interoperability and data portability across systems.

3.0 Objectives

The Army is establishing an LCNC ecosystem to accelerate delivery of business and mission solutions while ensuring governance, cybersecurity, and interoperability with Army enterprise services and data platforms. LCNC applications will augment EBS-C by providing rapid user-centric solutions for mission support tasks that are not part of the EBS-C core.

The Army seeks information on vendor capabilities and approaches that address the following high-level objectives:

1. Market Capabilities: Discover industry capabilities, interest, and willingness to support the Army’s ecosystem of applications in the areas of finance and logistics. Vendors may respond based on their existing solutions or their capability to develop applications tailored to Army requirements. Responses should categorize applications as transactional or non-transactional and assess integration needs.

2. Development using Approved Platforms: Identify vendors, solutions, and development approaches using Approved Product List (APL) systems (Appendix E) to ensure compatibility, security, and compliance with Army standards.

3. Development using non-APL Platforms: Determine the feasibility of adopting new platforms and the timeline for approval if not on the APL.

4. Partnering for Rapid Acquisition: Design strategies to maximize outreach, encourage innovation, expand the industrial base, streamline acquisition and transition successful prototypes to production.

5. Driving Mission Advantage through Innovative Technologies: Pursue innovative features or tools for accelerating development of the application and aligned with the functional communities’ needs for the application to improve operational readiness and enhance decision-making. Collaboration with functional communities during development is required.

6. Security and Interoperability Standards: Provide solutions that adhere to Army cybersecurity, interoperability, and governance standards.

7. Cost and Schedule: Rapidly deploy and demonstrate prototype projects and determine development and operation costs.

4.0 Requested Information

4.1 Company Profile

Please provide the following information for your company. If you are submitting as part of a team, please provide this information for each company on the team. Vendors who may not have a fully developed solution but are willing to develop applications tailored to Army needs should describe their capability and interest in doing so."

1. Company Information: Please provide the company's name, address, country of business, and website.

2. Company Representative: Please provide the name, business title, phone number, and email address of the company representative

3. Government Identification: Please provide the CAGE code and SAM Unique Entity ID.

4. Partnering: Please describe your team's approach to partnering.

5. Certifications: Please list any relevant certifications, such as FedRAMP, RMF, or

ATO.

4.2 Application Type and Data Model

Please define your solution or proposed solution for development by selecting the category below that best describes its primary function and its interaction with Army data systems. Vendors who do not have a fully developed application but have the capability and willingness to develop solutions tailored to Army needs should describe their approach and technical expertise. If your solution or proposed solution for development has both transactional and non-transactional components, please describe each.

1. Transactional Applications. Definition: These applications are built to process data and execute transactions that require a two-way, read/write integration with an Army ERP system of record (Appendix A). Their core purpose is to create, update, or modify data within those authoritative systems. Your Response Must Describe:

• Your technical approach to integration and data synchronization.

• How you ensure data integrity, manage error handling, and maintain an audit trail between your application / proposed application and the Army's

ERP.

• Which specific Army ERP systems your solution is designed to integrate with.

2. Non-Transactional Applications. Definition: These applications are designed for analytics, decision support, visualization, or reporting. They consume data from authoritative Army sources in a read-only capacity and do not write new or modified data back to the core ERP systems. Your Response Must Describe:

• How your application or proposed application aggregates data from one or more authoritative sources to provide actionable insights.

• Your methodology for transforming raw data into intuitive dashboards, predictive analytics, or other tools that enhance decision-making for the finance and logistics communities.

• The primary Army data sources your application would leverage.

4.3 Domain Expertise/Areas of Interest and Operational Impact

Demonstrate your company's expertise and willingness to solve challenges specific to the Army's finance and logistics domains. Vendors who may not have a fully developed solution but have the capability and interest in developing applications tailored to Army needs should describe their approach and technical expertise. Your response should provide concrete evidence of your capabilities and experience.

1. Primary Area of Expertise: Please select the area(s) where you have proven experience and provide examples of your solutions or projected solutions you could develop.

• For Finance: Describe a finance application you have developed or propose to develop based on your expertise. Explain the specific problem it solved or could solve (e.g., improved budget tracking, streamlined financial reporting, enhanced audit readiness) and the value it provided or could provide for the user.

• For Logistics: Describe a logistics application you have developed or propose to develop based on your expertise. Explain the specific problem it solved or could solve (e.g., increased inventory accuracy, improved supply chain visibility, enhanced readiness reporting). Show how it delivered or could deliver measurable value to the user.

• Describe your ability to develop logistics applications that support Army requirements (e.g., inventory management, readiness indicators and others).

Provide examples of innovative logistics applications you have developed.

2. Bridging the Finance-Logistics Divide: A critical Army requirement is maintaining a seamless, auditable link between logistical actions and financial transactions (e.g., linking a parts request to a purchase order and its final payment).

• Describe how your solution(s) or proposed solution(s) ensure or would ensure this data integrity.

• Explain your approach to creating and maintaining an unbreakable audit trail that connects logistics and financial data across different systems.

3. Scalability for the Global Mission: Army operations span the globe, from large, well-connected installations to small teams in disconnected, tactical environments.

• Describe your architecture and methodology for scaling your application to support enterprise-wide deployment (potentially hundreds of thousands of users).

• Explain how your application can effectively support users in disconnected, limited bandwidth, or intermittent connectivity (tactical edge) environments.

What is your model for data synchronization when a connection is re-established?

4.4 Experience with the Army’s Approved Platforms

Your ability to effectively build and deploy on our approved platforms is critical. This section requires you to provide evidence of your experience with the Army's specific technology ecosystem as defined in Appendix E. If you only have experience in a commercial technology ecosystem, please relate that experience to the questions below.

1. Platform Expertise and Project Experience:

• Identify which of the CIO Approved Development Platforms (e.g., Vantage, PowerApps, ServiceNow) you have direct, hands-on experience building solutions on

• For each platform you identify, provide an example of a project you have delivered. Describe the solution and explain why that platform was the correct technical choice for that specific use case.

2. Integration with Army Enterprise Services: A standalone application is not sufficient. Your solution must function as part of a larger enterprise ecosystem.

Describe your technical approach and proven experience integrating with:

• Identity, Credential, and Access Management (ICAM): How does your solution integrate with enterprise identity providers to ensure only authorized personnel can access the application and its data?

• Army Data Platforms (e.g., Vantage, Gabriel Nimbus): Describe how your application will securely connect to and consume data from the Army's authoritative data platforms.

3. Agile Development and Deployment Methodology: Describe your end-to-end process for building, testing, and deploying applications within a government environment.

• Agile Framework: What specific Agile methodology (e.g., Scrum, Kanban) does your team use? How do you structure your sprints, and how do you ensure government stakeholders are actively involved in feedback and review cycles?

• DevSecOps and Automation: Describe your approach to automating testing and security scans within your development process. Do you have experience building and using Continuous Integration/Continuous Deployment (CI/CD) pipelines to deploy applications onto government-owned platforms?

4.5 Proposing an Alternative (non-APL) Platform

While the Army prefers solutions built on the approved platforms listed in Appendix E, we are open to considering new platforms if they offer a truly transformative capability.

Vendors who may not have a fully developed solution but have the capability and willingness to develop applications on non-APL platforms should describe their approach and technical expertise. If your solution requires a platform not currently on the APL, you must provide a compelling business case and a realistic plan for its approval.

1. Business Case and Justification:

• Identify the Platform: Clearly state the name of your preferred development platform.

• Provide the Justification: Explain why this platform is technically superior to the existing APL options (e.g., PowerApps, ServiceNow, Vantage) for the

Army's finance and logistics missions. What specific, mission-critical capabilities does it provide that the approved platforms lack? Why would the benefit of using this new platform outweigh the significant cost, time, and security effort required for its approval?

2. Viable Path to Army Approval and Accreditation: Demonstrate that you have a clear understanding of the rigorous process required to get a new platform approved for use on DoD networks.

• Current Security Posture: What is the platform's current FedRAMP status? Is it "FedRAMP Authorized," "FedRAMP Ready," or "In-Process" at the Moderate or High baseline?

• Accreditation Plan & Timeline: Provide a detailed step-by-step plan for how you will achieve an Army Authority to Operate (ATO). Your plan must account for the full Risk Management Framework (RMF) process. Provide a realistic timeline, in months, for this entire process.

• Estimated Costs for Approval: Provide a Rough Order of Magnitude (ROM) for the costs associated specifically with the approval and accreditation process. This should include FedRAMP sponsorship/consulting fees and the labor costs required to produce RMF documentation.

4.6 Partnering for Rapid Acquisition.

We are committed to building a contracting framework that is as agile and innovative as the solutions we seek. To achieve this, we need your expert recommendations on how to structure our acquisition process to foster a true partnership with industry and expand the defense industrial base. Please provide your insights into the following:

1. Accelerating from Prototype to Production:

• What contracting model(s) (e.g., Other Transaction Authority (OTA), Broad Agency Announcement (BAA), multi-step procurements) do you believe would create the fastest, most effective pathway from an initial prototype award to a full-scale production contract?

• How can we design the process to avoid the common delays that prevent successful prototypes from reaching operational use?

2. Lowering Barriers and Encouraging Diverse Participation:

• How can we make it easier for small businesses, startups, and other non-traditional defense contractors to partner with us?

• What specific barriers in the typical government contracting process should we remove or simplify for this type of LCNC development? What would make it easier for your company to bring its best ideas to the Army?

4.7 Driving Mission Advantage through Innovative Technologies

We are looking for partners who can deliver a decisive operational advantage through technology. We want to understand not just what your solution does, but how it will empower our soldiers and civilians.

1. Core Technology and Innovation:

• What are the key innovative technologies at the core of your solution (e.g., AI/ML, predictive analytics, intelligent automation)?

• How do these specific features create a tangible advantage for Army finance or logistics operations? For example, how do they accelerate decision-making, improve asset visibility, or increase operational readiness?

2. Future Proofing and Evolution:

• Provide a 2–3-year visionary roadmap for your solution.

• How will you evolve its capabilities to incorporate emerging technologies and adapt to the Army's future mission requirements?

3. User-Centric Development:

• Success is defined by user adoption. Describe your methodology for engaging with end-users—the Army's finance and logistics personnel— throughout the development, testing, and deployment lifecycle.

• How do you ensure the final solution is intuitive, solves their specific day-to-day challenges, and has their active support?

4.8 Security and Interoperability Standards

All solutions operating on Army networks must be secure, resilient, and interoperable.

Your response must demonstrate a clear understanding of and a viable plan to meet these mandatory requirements.

1. Your Plan for Achieving a Security Accreditation (Authority to Operate -

ATO):

• The Army uses the Risk Management Framework (RMF) to assess and authorize systems. Describe your technical and procedural plan for successfully navigating the RMF process to achieve an ATO for your solution.

• Please provide evidence of your company's experience in this area, such as existing or previous ATOs you have secured for solutions with the DoD or other federal agencies.

2. Alignment with Army Enterprise Policies: The Army has a clear strategy for modern application development. Explain how your solution's architecture and data strategy specifically align with the principles outlined in key Army policies, particularly:

• The Army CIO's Low-Code/No-Code (LCNC) Development Guidance.

• The Army Unified Data Reference Architecture (UDRA).

4.9 Illustrative Cost and Schedule

To help us understand the potential costs and timelines, please provide a Rough Order of Magnitude (ROM) based on a hypothetical prototype project. Your estimate will be used for planning purposes only and is non-binding.

Scenario: Assume the Army asks you to develop a transactional LCNC application for a single Army command to solve a common financial challenge: tracking, managing, and resolving Unliquidated Obligations (ULOs).

⦁ The application must pull data from an Army ERP system (e.g., GFEBS) via a provided API.

⦁ It must provide a user-friendly dashboard for managers to review and assign ULOs to analysts.

⦁ Analysts must be able to document their research and update the status of each ULO within the app.

⦁ The solution must be developed on one of the Army's Approved Platforms (e.g., PowerApps, ServiceNow).

Based on this scenario, please provide the following:

1. Cost (ROM):

• What is the estimated cost for an initial 3–4-month prototype to demonstrate the core functionality to a group of 50 users?

• What is the estimated cost for a subsequent 6-month pilot to refine the prototype and deploy it to the entire command (approx. 500 users)?

• What is the estimated annual sustainment cost post-pilot (including help desk support, security patching, and minor enhancements)?

• Please state the key assumptions in your cost estimate (e.g., Does it include software licensing costs?). What is the assumed size and composition of your development team?

2. Schedule and Milestones:

• Provide an estimated timeline from project kickoff to the delivery of the initial prototype.

• Identify the major milestones you would include in your project plan (e.g., Kickoff, Requirements Validation, Prototype Demo, User Feedback Session).

• What do you see as the biggest risks or dependencies that could impact this schedule (e.g., availability of government personnel/SMEs, finalization of API requirements, security accreditation process)?

5.0 Submission Instructions

Response Submission: Submit responses via email by 1200 Central Time, 16 February 2026 to:

• Jessica Rooks, Contract Specialist: jessica.b.rooks.civ@army.mil and Nathan B.

Bowers, Contracting Officer: nathan.b.bowers.civ@army.mil

• Format: Submissions should be a single Microsoft Word file 2016 or later compatible file (.docx), limited to 10 pages. Proprietary information MUST BE CLEARLY MARKED. Vendors who may not have a fully developed solution but are interested and capable of developing applications tailored to Army needs are encouraged to respond.

• Font: Times New Roman, no smaller than 10pt, with at least a one-inch margin.

6.0 Appendices

1. Appendix A: Current Army ERP Systems

2. Appendix B: The EBS-C Value Chains

3. Appendix C: EBS-C Solution Architecture

4. Appendix D: Army CIO Low-Code/No-Code Development Guidance

5. Appendix E: Approved Products List (APL)

6.1 Appendix A: Current Army ERP Systems

EBS-C will converge the five (5) Army SAP ERP Systems listed below:

1. General Fund Enterprise Business System (GFEBS): the Army's core financial management system for administering its General Fund

2. General Fund Enterprise Business System - Sensitive Activities (GFEBS-SA):

the sensitive activities component of GFEBS

3. Global Combat Support System – Army (GCSS-A): supports logistical, financial and tactical management of Army assets

4. Logistics Modernization Program (LMP): facilitates national supply chain management of parts and equipment and serves as the General Ledger for the Army Working Capital Fund

5. Army Enterprise Systems Integration Program (AESIP) Hub: supports integration of components of Army business processes master data management

6.2 Appendix B: The EBS-C Value Chains

6.3 Appendix C: EBS-C Solution Architecture

App Eco-System *supports multiple software products and tools

Engagement Layer:

• Purpose: Facilitates all user interactions

• Key Functions: Focuses on UI/UX rendering, providing role-based access, multi-device support

(desktops, tablets, phones), and notifications.

Agility Layer:

• Purpose: Enables unique business processes and business workflows to avoid building customization of the Transactional Core

• Key Functions: Supports process automation, orchestration, agile application creation, and workflows.

Integration/Brokering Layer:

• Purpose: Ensures reliable, real-time flow and transformation of data between the

Transactional Core, the Agility Layer, and external systems.

• Key Functions: Data mapping, synchronization, real-time messaging, API mediation, and Master Data Management (MDM) enforcement.

Transactional Core:

• Purpose: Provides stable, governed, and reliable processing of all core business transactions.

• Key Functions: Manages essential enterprise functions including financials, procurement, HR, logistics, and manufacturing. Supports compliance, auditability, and accurate record-keeping.

EBS-C Solution Architecture

Engagement Layer

Agility Layer

Transactional Core Layer

Data Integration/Brokering Layer

How the user interacts with

EBS-C

Quick development to adapt to changing / unique business needs

Connective tissue between layers and across systems

Integrated finance and logistics system of record

UNCLASSIFIED

UNCLASSIFIED

ERP strategy since 2021; Aligned with best industry practices of a composable ERP architecture

6.4 Appendix D: References

1. AR 25-2 Army Cybersecurity – 04 April 2019

2. Army Modernization Strategy – 2021

3. Army Digital Transformation Strategy -2021

4. Data Platform Guidance – 01 February 2024

5. Army Unified Data Reference Architecture - 22 March 2024

6. Army Enterprise Data Product Definition - 18 July 2024

7. Risk Management Framework Modernization – 02 March 2025

8. Army Data Stewardship Roles and Responsibilities - 28 April 2025

9. Policy for Interim Army Approved Products List – 04 June 2025

10. Army Low-Code/No-Code Development Guidance - 31 July 2025

11. Army Data Modernization and Centralization to Vantage - 26 September 2025 https://armypubs.army.mil/epubs/DR_pubs/DR_a/ARN37506-AR_25-2-003-WEB-4.pdf https://www.army.mil/e2/downloads/rv7/about/2021_army_modernization_strategy.pdf https://api.army.mil/e2/c/downloads/2021/10/20/3b64248b/army-digital-transformation-strategy.pdf https://armypubs.army.mil/epubs/DR_pubs/DR_a/ARN41173-PPM_CIO-032-000-WEB-1.pdf https://api.army.mil/e2/c/downloads/2024/03/25/c3d9b3aa/udra-version-1-0-final.pdf https://armypubs.army.mil/epubs/DR_pubs/DR_a/ARN41492-PPM_CIO-036-000-WEB-1.pdf https://armypubs.army.mil/epubs/DR_pubs/DR_a/ARN43739-PPM_CIO-075-000-WEB-1.pdf https://armypubs.army.mil/epubs/DR_pubs/DR_a/ARN43678-PPM_CIO-071-000-WEB-1.pdf https://armypubs.army.mil/epubs/DR_pubs/DR_a/ARN44038-PPM_CIO-077-000-WEB-1.pdf https://armypubs.army.mil/epubs/DR_pubs/DR_a/ARN44571-PPM_CIO-076-000-WEB-1.pdf https://armypubs.army.mil/epubs/DR_pubs/DR_a/ARN45262-PPM_CIO-092-000-WEB-1.pdf

6.5 Appendix E: Approved Product List

CIO Approved Data Platforms

(HQDA CIO memorandum (Army LCNC Development Guidance, 31 July 2025)

1. Vantage 4. Gabriel Nimbus

2. Army Intelligence Data Platform 5. The Army Resource Cloud

3. ADVANA 6. cPeople/Person Event Data Environment

CIO Approved Development Platforms

* Sustained by the Army Software & Innovation Center (ASIC)

1. Vantage * 4. ServiceNow * 7. SAP

2. PowerApps * 5. Appian *

3. Salesforce * 6. Palantir