Army LCNC Intelligence Brief
Based on 8 Army CIO Policy Documents · Updated March 2026
The Army has issued a formal LCNC governance framework (CIO-076, July 2025) establishing 7 approved enterprise LCNC platforms and a structured acquisition pathway. The framework is directly tied to the Army's Digital Transformation Strategy targeting Waypoint 2028. Commercial vendors (ServiceNow, Appian, Power Platform, etc.) are not currently listed as approved Army LCNC platforms — but the ECMA Cloud Governance Council nomination process is open. The key active opportunity is the PEO EBS-C Sources Sought for an LCNC Application Ecosystem for Army Logistics and Finance — a bellwether for where Army acquisition spend is heading.
CIO Policy Docs
8
Analyzed from Army CIO
Approved Platforms
7
Per CIO-076 (Jul 2025)
Active Army Opps
6
Sources sought, active on SAM
Strategy Target
Waypoint 2028
Army Digital Transformation
Commercial Platforms Approved
0
ECMA process open for nominations
Spotlight: Active Army Acquisition
ACC-RI, on behalf of PEO EBS-C, is seeking information from industry on capabilities to develop, host, integrate, and sustain Low-Code/No-Code applications in the Army logistics and finance domain. This is a market research Sources Sought — there are 6 related notice IDs on SAM.gov, indicating iterative amendments/updates to the requirement. The fact that PEO EBS-C is issuing this Sources Sought signals they are building toward a competitive procurement. Logistics and finance are among the Army's largest legacy system modernization targets per the Digital Transformation Strategy.
View on SAM.gov
Also see notice IDs: 2bd3aaaa, 77e49ced, 866ad7f9, a05f8f1a, b1270adb
What Army is Looking For
ATO Inheritance: Solutions must operate within an existing platform ATO. Vendors who can nest apps inside an Army-approved platform boundary (especially Army 365) have a major compliance advantage.
Data Platform Integration: LCNC apps must integrate with Army's approved data platforms — especially Army Vantage — via open APIs. Native connectors to Army Vantage will be differentiating.
Citizen Developer Enablement: Policy explicitly targets non-technical users solving organizational problems. Solutions that enable Army business users — not just developers — will be favored.
Legacy System Replacement: Army intends to use LCNC to replace hundreds of routine/transactional legacy systems. Focus areas: logistics (EBS-C), finance, HR (cPeople), readiness reporting.
cArmy Cloud Compatibility: Solutions must operate on or integrate with cArmy (Army's cloud). Cloud-native or hybrid-cloud solutions that run in cArmy are strongly preferred per ADTS.
ICAM Integration: All LCNC platforms must use Army Identity, Credential and Access Management (ICAM) for authentication. No standalone identity solutions.
Zero Trust: RMF modernization (CIO-075) requires Zero Trust principles. LCNC platforms must align with Zero Trust architecture — not just have ATOs.
Compliance & Governance Requirements
APL Listing Required: Per CIO-077, all software must appear on the Army Approved Products List before deployment. Vendors must proactively get listed — this is a pre-sale requirement.
ECMA Nomination Process: New LCNC platforms require PEO or Command to nominate them to the ECMA Cloud Governance Council. Vendors need an Army sponsor (PEO/Command) to initiate this process.
Quarterly KPI Reporting: Platform Owners must provide quarterly performance reports to Army CIO covering deployment speed, user adoption, and cybersecurity incident reduction. Structure offerings around these metrics.
Data Portability: Per UDRA (Army Unified Data Reference Architecture), solutions must support data portability and open APIs — no proprietary data lock-in.
Onboarding Transparency: CIO-076 requires Platform Owners to establish clear, transparent onboarding processes and document capabilities for end users. Self-service capability is critical.
Fully Burdened Cost Model: Platform Owners must manage fully burdened costs and propose billing structures (chargeback/showback) for CIO approval. SaaS pricing must fit Army fiscal models.
Enterprise License Agreements: Army Digital Transformation Strategy explicitly calls for ELAs with strategic vendors to reduce procurement friction. Position for Army-wide ELA — not agency-by-agency deals.
Vendor Engagement Roadmap
Step 1 · Immediate
Respond to PEO EBS-C Sources Sought
Submit a capability statement to ACC-RI for the LCNC Application Ecosystem (Sol# AppEcosystem). Highlight logistics/finance domain expertise, Army platform integrations, and cArmy compatibility. This is the active Army LCNC procurement signal right now.
Step 2 · Near-Term
Get Listed on Army APL (CIO-077)
Initiate the interim APL listing process. This is a gate requirement for any Army deployment. Contact: SAIS-CS policy office. Without APL listing, even a won contract can't deploy.
Step 3 · Near-Term
Secure a PEO/Command as Platform Sponsor
ECMA nomination requires a Functional Owner (PEO or Command) to champion your platform. Target PEO EBS-C (given active solicitation), PEO Enterprise Information Systems, or TRADOC G-6 as natural sponsors.
Step 4 · Mid-Term
ECMA Cloud Governance Council Nomination
Work with your sponsor to submit nomination through ECMA. Be prepared for technical viability assessment. Key criteria: cArmy compatibility, ICAM integration, ATO boundary, Army Vantage API connectivity, data portability.
Step 5 · Mid-Term
Structure an Army-Specific Offering
Build a demo environment using Army Vantage connectors, Army 365 / Power Platform interoperability, and Zero Trust-aligned architecture. Show chargeback billing model. Focus messaging on citizen developer enablement for logistics and finance use cases.
Step 6 · Long-Term
Target Enterprise License Agreement
Army ADTS explicitly calls for ELAs with strategic vendors to reduce costs and procurement friction. Position for Army-wide ELA through ASA(ALT) (Army Acquisition Executive). Coordinate via CHESS contracts where possible.
Key Risk: Microsoft/Power Platform Has Built-In Advantage
Army 365 (Microsoft 365 + Power Platform) is already approved, already on every Army user's desktop, and carries zero additional ATO burden. This gives Power Platform an enormous structural advantage in the citizen developer space. Competing vendors need to demonstrate clear differentiation: superior capabilities for complex multi-step workflows, better enterprise governance, deeper Army Vantage integrations, or lower total cost — not just matching Power Platform features.
Key Policy Quotes
The Army must modernize hundreds of defense business systems that primarily perform routine or common transactional functions. Several of these functions could be streamlined using LCNC solutions, leveraging APIs to authoritative data sources.
— CIO-076, Army Low-Code/No-Code Development Guidance (July 31, 2025)
The Department of the Army views the rapid adoption of scalable, secure, LCNC platforms as an essential component of enhancing readiness and modernizing the Force. Accelerating the adoption of these technologies is essential and requires the barriers to entry to be significantly lowered.
— CIO-076, Platform Adoption Section
Centralizing data to Vantage is more than a technical upgrade, it is a cultural shift. We are building a data-driven Army where leaders at every level can access timely, trusted information to make informed decisions.
— CIO-092, Army Data Modernization and Centralization to Vantage (September 2025)
The Army will establish Enterprise License Agreements (ELA) with strategic vendors to both achieve cost savings and reduce procurement manpower through a single contract, as well as drive accountability for the use of licenses by the Commands.
— Army Digital Transformation Strategy 2028 (ADTS), LOE 2.2
The Army will also establish an open technical architecture and open Application Programming Interfaces (APIs) for integration and interoperability in order to minimize vendor lock in and retain flexibility to adopt newer technologies in future.
— Army Digital Transformation Strategy 2028 (ADTS), Enterprise Business Systems Modernization