Request for Information (RFI) - ATIS LMS.pdf

Request for Information (RFI) / Sources Sought

For a Mission-Wide Learning Management System (LMS)

RFI Number: RFI-ATISLMS-2026-01 Issuing Agency: Product Manager Army Training Information System (ATIS) Date of Issuance: 27 April 2026 Response Due Date: 12 May 2026, 0900 EST

1.0 PURPOSE OF THIS NOTICE

This is a Request for Information (RFI)/Sources Sought notice issued in accordance with Federal Acquisition Regulation (FAR) Part 10 for market research purposes only. This is not a solicitation (e.g., Request for Proposal, Request for Quote) and does not constitute a commitment, implied or otherwise, that the U.S. Government will issue a solicitation or award a contract.

2.0 BACKGROUND AND OPERATIONAL SCENARIO

The Product Manager Army Training Information System (ATIS) requires a comprehensive Learning Management System (LMS) to deliver, track, and manage all mandatory, mission-essential, and professional development training for approximately 1.5 million personnel to include users from all Army Components, Civilians, and contractors. Additionally, there are separate and distinct educational needs for the 88+ Centers of Excellence and Schools that must be integrated into the LMS. The LMS must be able to support instructor-led, traditional classroom training and education, as well as asynchronous independent learning

The LMS must be able to support a centrally accessible course catalog as well as sub-organizations or tenant level management. Each sub-organization requires its own designated administrators who require data isolation to allow for content, users, course catalogs, and reporting management. Suborganization administrators should not have access to the personnel data or training records of other sub-organizations. The LMS must simultaneously support central control allowing for Headquarters- type training to be accessible outside of the sub-organizations and retain visibility and governance across all sub-organizations. Additionally, scalability is a required functionality for the LMS.

The LMS must be performant to manage high course loads as some mandatory training is taken by the entire 1.5M user base annually. As such a single course could see over multiple thousands of simultaneous users.

Furthermore, the agency has a significant need for automation to reduce administrative burden. For example, when a new employee is assigned to "Unit X," the system must be capable of automatically enrolling them in that unit’s required onboarding curriculum without manual administrator intervention. Likewise, when a user completes a prerequisite course, the system must automatically unlock the next course in their learning path.

The agency’s training portfolio includes a mix of standard e-learning courses (SCORM 1.2 and 2004 3d Ed.), complex simulations, and performance support tools that are developed in-house. The desired LMS must be flexible enough to integrate these custom tools and allow for future development of bespoke functionalities to meet evolving mission requirements. In addition to support for current Army training, the LMS should be able to support current e-learning standards such as but not limited to xAPI, CMI5, HP5, and have a roadmap that reflects support for emergency capabilities and standards.

3.0 MINIMUM CAPABILITY REQUIREMENTS

The Government is seeking information on commercial-off-the-shelf (COTS) solutions that meet the following minimum capabilities:

ID Category Capability Requirement

A.1 Architecture & User Management

The LMS must support logically segregated learning environments to service multiple, distinct organizational units from a single back-end instance. Each segregated environment must support its own administrators, user cohorts, course catalogs, branding, and reporting.

A.2 Architecture & User Management

The system must allow for bulk user management, including creation, updates, and suspension via standard data formats (e.g., CSV) and/or API integration with Government HR systems.

A.3 Architecture & User Management

The solution must ensure the Government retains unlimited rights to all Government-owned data created, stored, or processed by the LMS. This includes, but is not limited to, all user data, course content, course configurations, and activity records. The LMS must provide a mechanism for a government administrator to export all such data at any time, without vendor intervention, in a non-proprietary, machine-readable format (e.g., SQL, CSV, XML).

B.1 Course Delivery & Automation

The LMS must provide a robust automation engine allowing administrators to create conditional "if-then" rules that trigger actions (e.g., enrollment, messaging, issuing certificates) based on user profile data, course completions, or audience/cohort membership.

B.2 Course Delivery & Automation

Must be compliant with SCORM 1.2, 2004 3rd edition and the Experience API (xAPI).

B.3 Course Delivery & Automation

Must support the creation of structured learning paths and programs, enforcing prerequisites and ordering of courses.

C.1 Customization & Integration

The system’s architecture must allow for the integration of third-party tools and content via modern interoperability standards, such as LTI 1.3 Advantage.

C.2 Customization & Integration

The system must provide access to its Application Programming Interface (API) and/or source code to allow Government or third-party developers to build, integrate, and maintain bespoke functionalities and extensions to meet unique agency requirements The Government prefers solutions built on non-proprietary, open standards to avoid long-term vendor lock-in.

D.1 Reporting & Analytics

The system must provide a configurable reporting engine that allows administrators to generate detailed reports on user progress, course completions, and compliance metrics. Reports must be filterable by audience, organization, and date range.

D.2 Reporting & Analytics

The reporting capability must provide global reporting for the entire LMS as well as restricted reporting that respects the multi-tenancy architecture, ensuring a sub-organization’s administrator can only report on their own personnel.

E.1 Security & Compliance

(DFARS)

The solution must be capable of being deployed within the cArmy AWS GovCloud and meet security controls for at least Impact Level 4 (IL4).

E.2 Security & Compliance

(DFARS)

Vendors must describe their experience with the DoD Risk Management Framework (RMF) and their process for supporting the Government in achieving and maintaining an Authority to Operate (ATO).

E.3 Security & Compliance

(DFARS)

The solution must support DoD-compliant authentication methods, including Single Sign-On (SSO) with Common Access Card (CAC) / Public Key Infrastructure (PKI).

4.0 INSTRUCTIONS FOR SUBMISSION

Interested parties are requested to submit a capabilities statement, not to exceed 15 pages, that provides the following:

1. Company Information:

o Company Name, Address, and Website.

o Point of Contact (Name, Title, Email, Phone).

o CAGE Code and Unique Entity Identifier (UEI).

o A list of any relevant GSA Schedules, NASA SEWP, Army CHESS, or other Government-Wide Acquisition Contracts the solution is available on.

o Business size and any socioeconomic classifications (e.g., Small Business, 8(a), Woman-Owned).

2. Capability Matrix and Narrative:

o A completed matrix that cross-references the vendor's solution against each requirement listed in Section 3.0. For each requirement, the vendor must state "Meets," "Partially Meets," or "Does Not Meet."

o For each requirement marked "Meets" or "Partially Meets," the vendor must provide a corresponding narrative describing how their solution achieves the stated capability. General marketing material is not sufficient. Please provide specific details, screenshots, or links to technical documentation.

3. Cybersecurity & Support:

o A detailed response to the Security & Compliance requirements in Section

3.0 (E.1 - E.3).

o A description of the standard technical support packages offered.

4. SUBMISSION DEADLINE: Responses to the capability statement to this RFI are to be submitted electronically via email to Contracting Officer: Neal Williams at neal.l.williams.civ@army.mil and Contract Specialist: Marisol Trevino at marisol.m.trevino.civ@army.mil no later than 9:00 AM Eastern Standard Time (EST) on May 12, 2026 with the subject line "Response to RFI-ATISLMS-2026-01."

No phone calls will be accepted. The Government is not committed nor obligated to pay for the information provided, and no basis for claims against the Government shall arise as a result of a response to this RFI.

Please submit all questions no later than 5:00 PM Eastern Standard Time on May 01, 2026. All Q&A will be provided on or around May 08, 2026.

5. Confidentiality: Data received in response to this RFI that is marked or designated as corporate or proprietary will be protected from unauthorized disclosure.

6. Disclaimer: THIS RFI IS FOR INFORMATIONAL PURPOSES ONLY. THIS IS NOT A

REQUEST FOR PROPOSAL (RFP) OR SOLICITATION. IT DOES NOT CONSTITUTE A

COMMITMENT BY THE U.S. GOVERNMENT TO AWARD A CONTRACT. RESPONSES

ARE NOT OFFERS AND THE GOVERNMENT IS UNDER NO OBLIGATION TO AWARD A

CONTRACT AS A RESULT OF THIS ANNOUNCEMENT. NO FUNDS ARE AVAILABLE TO

PAY FOR PREPARATION OF RESPONSES. THE INFORMATION SUBMITTED IS

STRICTLY VOLUNTARY. RESPONSES WILL NOT BE RETURNED. FAILURE TO

RESPOND TO THIS RFI DOES NOT PRECLUDE PARTICIPATION IN ANY FUTURE

REQUEST FOR QUOTE (RFQ), INVITATION FOR BID (IFB), OR RFP. ANY SUBSEQUENT

SOLICITATION WILL BE SYNOPSIZED ON THE GOVERNMENT-WIDE POINT OF

ENTRY (GPE). IT IS THE RESPONSIBILITY OF POTENTIAL OFFERORS TO MONITOR

THE GPE FOR ADDITIONAL INFORMATION.

mailto:neal.l.williams.civ@army.mil mailto:marisol.m.trevino.civ@army.mil