1.2.1_RFI_FEMA Learning Management Ecosystem Design Phase.pdf

PDF 220 KB Posted

Attached to
Learning Management Ecosystem Design
Solicitation number
70FA3126I00000005
Issued by

About this file

This is a Request for Information (RFI) issued by the Federal Emergency Management Agency (FEMA) Office of Chief Information Officer seeking market research on software factory services. FEMA requires establishment of an initial software factory foundation and development of a working prototype demonstrating a unified registration experience across FEMA's fragmented Learning Management Ecosystem (LME) in ServiceNow Test Environment. The current LME comprises over 20 independently owned and operated systems supporting student registration, registrar services, classroom management, help desk services, analytics, geospatial reporting, budget management, evaluations, and transcript functions. The primary challenge is the absence of unified student registration, requiring separate logins across systems for internal staff and external learners including state, local, and first-responder communities. FEMA seeks a federated registration approach supporting PIV-based access for federal employees and centralized authentication via Login.gov for external users.

RFI responses must be submitted electronically to Ross Wakeman, Contracting Officer (ross.wakeman@fema.dhs.gov) and Myeshia Daniels, Contract Specialist (Myeshia.daniels@fema.dhs.gov) by 3:00 PM Eastern Time on August 31, 2026, with questions due by August 26, 2026. The anticipated performance period starts in Fiscal Year 2027 with an acquisition strategy to be determined. Responses must include a cover page with company information and business size status, a capability statement (maximum 2 pages), and responses to RFI questions (maximum 5 pages) addressing business structure, LME prototype design, consolidation strategies, development pipeline creation, five-month completion feasibility, proposed tools and technologies, rough order of magnitude cost estimates with assumptions, labor mix and staffing details, risks and mitigation strategies, and requirements feedback. The applicable NAICS code is 541512 (Computer Systems Design Services) and Product Service Code is 7D20 (IT and Telecom – Service Delivery Management). All costs associated with RFI response are the sole responsibility of respondents, and FEMA incurs no obligations or liabilities for expenses incurred.

View the file

Other files

On GovTribe

Work with this file

  • Download the original file
  • Contacts named in this file
  • Similar government files
  • Ask GovTribe AI about this file

Text version

Federal Emergency Management Agency (FEMA) Request for Information (RFI) 70FA3126I00000005

REQUEST FOR INFORMATION (RFI) SUMMARY: The Department of Homeland Security (DHS), Federal Emergency Management Agency (FEMA), Office of Chief Information Officer, has a requirement to establish an initial software factory foundation and demonstrate that foundation through a first use case: a working prototype of a unified registration experience across FEMA’s Learning Management Ecosystem (LME) in FEMA’s ServiceNow Test Environment.

The requirement arises from FEMA’s fragmented LME environment, which has evolved over more than two decades through independent program-level decisions. The current ecosystem includes more than 20 separate systems that are independently owned, operated, and maintained by different program offices.

These systems support a wide range of functions, including student registration, registrar services, classroom and room management, help desk services, analytics, geospatial reporting, budget and spend-plan management, instructor and student evaluations, and transcript-related functions.

A central challenge is the lack of a unified student registration experience. Learners and administrators currently navigate separate login processes across different systems. This creates inefficiencies for internal FEMA staff as well as external learners, such as state, local, and first-responder communities.

FEMA seeks to address this gap through a federated registration approach that could support PIV-based access for federal employees and a centralized authentication service, such as Login.gov, for external learners.

Prior consolidation efforts have reportedly stalled due to a conventional, siloed approach in which architecture and DevSecOps pipelines were established separately from design and development, and individual mission offices scoped and owned systems independently.

GENERAL INFORMATION: This RFI is issued solely for information gathering purposes to identify sources that can provide support for the Office of Chief Information Officer. In accordance with FAR 15.101(c), RFIs may be used when the Government wants to obtain price, delivery, other market information, and capabilities for planning purposes. Responses to these RFIs are not offers and cannot be accepted by the Government to form a binding contract. This RFI shall not be construed as a commitment by the Government for any purpose, nor does it restrict the Government to an ultimate acquisition approach. Respondents are solely responsible for all expenses associated with their RFI response.

Respondents will not receive additional information in response to their submittal to the RFI and will not be notified of the resulting market research.

PROPRIETARY INFORMATION AND DISCLAIMERS: Respondents shall identify any proprietary information in its RFI response. Information submitted in response to this RFI will be used at the discretion of the Government. Further, the information submitted will remain confidential insofar as permitted by law, including the Freedom of Information and Privacy Acts. FEMA reserves the right to utilize any non-proprietary technical information in the anticipated PWS or solicitation.

Although it is not necessary to address in their response, respondents shall be aware of any potential, actual, or perceived organizational conflicts of interests. Any real or potential conflicts must be sufficiently mitigated prior to a contract award. For further guidance, refer to the Federal Acquisition Regulation, Part 9.5.

NAICS CODE: 541512 – Computer Systems Design Services

PRODUCT SERVICE CODE (PSC): 7D20 - IT and Telecom - Service Delivery Management

ANTICIPATED PERIOD OF PERFORMANCE START DATE: Fiscal Year 2027

ANTICIPATED ACQUISITION STRATEGY: To be Determined

ATTACHMENT: Statement of Objectives

RFI RESPONSE SUBMITTAL INSTRUCTIONS:

Interested contractors shall submit their RFI responses electronically to Ross Wakeman, Contracting Officer, at ross.wakeman@fema.dhs.gov and Myeshia Daniels, Contract Specialist, at Myeshia.daniels@fema.dhs.gov no later than 3:00PM Eastern Time (ET) on 08/31/2026 with the following subject line: FEMA Learning Management EcoSystem RFI Response. Questions regarding this RFI are due no later than 08/26/2026.

“RFI Response for Office of Chief Information Officer FEMA Learning Management Ecosystem Design Phase” shall be in the subject line of your e-mail. All responses shall be unclassified, with proprietary information clearly marked. The document format shall be either Microsoft Word (.doc or .docx), or Adobe Acrobat (.pdf) formats. Pages shall be 8.5 by 11 inch and shall use a type pitch that is no smaller than a standard 11-point font type, with the exception of charts, graphs, or tables, which shall use a pitch not smaller than 10-point font. Responses shall not exceed (page limit) pages in length including images, data displays, charts, graphs, and tables. Page limitation does not include: 1 cover page. Do not include promotional materials.

RFI Responses shall include the following information in the order below:

A. Cover Page with the following information:

1. Company Name

2. Company Address

3. UEI Number

4. Company Point of Contact - Name, Title, Phone, and Email address

5. Statement of current business size status (i.e., HUBZone small business concern, service-disabled veteran-owned small business firm, 8(a) contractor, woman-owned small business, small business, or large business concern). Also, business size in relation to the NAICS code size standards assigned to this acquisition.

6. GSA Schedule Number, Contract Number, and Period of Performance and/or DHS Strategic Sourcing Vehicle Category Name and Contract Number, if applicable

B. Contractor Capability Statement (No more than 2 pages in length)

1. Summarization of relevant projects showing capabilities

2. Past performance in applicable areas

C. Contractor RFI Responses to questions (No more than 5 pages in length)

The responses received will assist FEMA with identifying the number and nature of the entities that consider themselves potential technical solution providers. Each respondent, by submitting a response, agrees that any cost incurred in response to this RFI, or in support of activities associated with this RFI, shall be the sole responsibility of the respondent. FEMA shall incur no obligations or liabilities whatsoever, to anyone, for any costs or expenses incurred by the respondent in responding to this RFI.

REQUEST FOR INFORMATION (RFI) QUESTIONS

Business Structure:

• Can your organization fulfill all requirements as a prime contractor, or will you require teaming arrangements or subcontracting relationships?

• If a teaming or subcontracting relationship is required, please delineate the capabilities your organization and your partner(s) can provide for this effort.

Learning Management Ecosystem:

• How would you design a working prototype of a unified registration experience across FEMA’s Learning Management Ecosystem (LME) in FEMA’s ServiceNow Test Environment.

Execution Strategy (Primary objectives):

• What strategies would you recommend for consolidation?

• How would you develop a development pipeline for use by all of FEMA?

Period of Performance

• Can the objectives be completed in five months? If not, please describe what can be accomplished.

Tools, Licenses, & Technology

• What tools, platforms, and technologies, if applicable, do you propose to use for this project?

• Can the objectives be achieved without paying for licenses tools?

Cost Structure & Estimates

• Please provide an itemized Rough Order of Magnitude (ROM) cost estimate, outlining key cost drivers, constraints, and limitations.

• Please describe any assumptions or dependencies that impact your cost estimate.

Labor Mix & Staffing

• Please provide a proposed labor mix for the project, including roles, skill levels, and estimated hours for each labor category, e.g. – Service Designer, UI/UX Designer, DevSecOps Engineers, etc.

Risk, Constraints, & Limitations

• What risks, constraints, or limitations do you foresee in executing this project, and how will you mitigate them? Please describe any dependencies on DHS resources, data, or personnel.

Requirements Feedback:

• Is there any aspect of the RFI that needs further clarification from the government?

• Please provide any recommendations on what information the government should provide in an

RFP for vendors to properly respond.

File details come from the government source that posted it. Updated .