Request for Information (RFI) for Army Enterprise Identity, Credential, and Access Management (E-ICAM) Services Delivery Contract

Request for Information (RFI) for Army Enterprise Identity, Credential, and Access Management (E-ICAM) Services Delivery Contract RFI Number: RFI-ARMY-EICAM-2026-02 Date of Issuance: July 14, 2026 Response Due Date: August 04, 2026, 1:00 PM ET 1.0 Introduction and Purpose This is a Request for Information (RFI) as defined in Federal Acquisition Regulation (FAR) 15.201(e). The Army Contracting Command, Aberdeen Proving Ground (ACC-APG), on behalf of Product Lead Enterprise Identity, Credential, and Access Management (PdL E-ICAM) under PdL Enablers, is conducting market research to identify potential sources, best practices, and innovative solutions for a comprehensive Enterprise Identity, Credential, and Access Management (E-ICAM) service. The Army seeks to continuously deliver its current E-ICAM capabilities and modernize its enterprise platform to support a globally deployed force, enable multi-domain operations, integrate with tactical environments, and accelerate the implementation of a Zero Trust Architecture. This RFI is for planning and informational purposes only and does not constitute a Request for Proposal (RFP). The Government will not award a contract based on responses to this RFI or pay for any information submitted. 2.0 Background and Current Environment The Army's E-ICAM infrastructure is a complex ecosystem that requires both continuously delivery of currently fielded systems and modernization to address future requirements. This service must manage the full lifecycle of identities for all users (soldiers, civilians, contractors, mission partners), enforce the principle of least privilege, and align with the DoD's Zero Trust Strategy. To assist vendors in understanding the scale of this effort, the current E-ICAM environment encompasses approximately: Identities Managed: Est. up to 3.5M user Applications Integrated: Est. 2,000 applications Privileged Accounts: Est. up to 4,000 users Average Monthly Help Desk Tickets (Tier 3/4): Est. Up to 3,500 The future solution must be scalable, leverage commercial innovation (including Commercial Off-The-Shelf (COTS) products), utilize non-proprietary connections where feasible, and operate effectively under a single prime contractor who will coordinate with other Government and vendor stakeholders. 3.0 Scope of Interest The Army is interested in information related to the following key areas: Continuous Delivery: Strategies for operations, maintenance, and incremental improvement of existing enterprise ICAM systems. Modernization & Onboarding: Application of Agile/DevSecOps methodologies to modernize the architecture and efficiently onboard a backlog of existing and future Army applications. Integration & Interoperability: Methodologies for extending enterprise capabilities to tactical environments when connected. Organizational Conflict of Interest (OCI): Strategies to comply with strict OCI requirements regarding the recommendation and integration of commercial products. Contracting & Pricing Approach: Recommendations for structuring a hybrid contract that defaults to Firm-Fixed-Price (FFP) CLINs for defined deliverables and agile modernization tasks, while providing structured flexibility for the Contracting Officer to utilize alternative, performance-tied CLIN structures for complex delivery components where justified in accordance with Executive Order 14402.4.0 Information Requested Interested parties are requested to provide concise responses to the following. Please limit your total response to 15 pages, not including the cover page and corporate information. Corporate Information: Company Name, Address, Website, CAGE Code, and Unique Entity Identifier Number. Point of Contact (Name, Title, Email, Phone). Business Size and applicable NAICS codes. Section A: Continuously Delivery (Existing State) Describe your experience providing solutions to continuously deliver the following ICAM capabilities at a scale similar to the Army's environment (as detailed in Section 2....