REQUEST FOR INFORMATION

REQUEST FOR INFORMATION (RFI)

423430 - Computer Software Merchant Wholesalers

PURPOSE

The National Endowment for the Humanities (NEH) is conducting market research and early exchanges with industry to improve its understanding of available approaches, capabilities, price/delivery information, and risks for modernizing the user interface (UI) of an enterprise grants management system (“eGMS”) managed by NEH and used by additional federal agencies as a shared service.
This Request for Information is for planning purposes only and is being used solely as a market research tool in accordance with FAR Subpart 10.002(b). This is not a Request for Proposal (RFP), nor is a Request for Quotation (RFQ) nor is an announcement of a solicitation. Response is strictly voluntary and the Government will not provide any reimbursement for any response for the effort expended in the preparation of a response by any vendor. Submission of a response to this RFI notice will not affect any potential offeror’s ability to submit a quotation/proposal in the future should funding become available and a solicitation is issued. There is no solicitation document associated with this RFI. There is no obligation on the part of the Government to acquire any product or service as a result of this RFI. Submissions made to the Government will not be returned. Information provided in this RFI is subject to change and is not binding upon the Government.

BACKGROUND

The eGMS platform is a mission‑critical, shared grants management system that serves NEH and partner agencies. The current platform is built with the Microsoft .Net Framework and the user interface is built with ASP.Net web forms. As part of a modernization that will migrate data and service layers to Microsoft .Net Core, NEH seeks specialized expertise to select the right modern solution for its user interface layer, ensure resilient architecture, plan the migration, and train staff to execute the work.

PURPOSE & GENERAL REQUIREMENTS

NEH seeks non‑binding input, examples, and recommendations focused on a UI migration from ASP.NET Web Forms to ASP.NET Core, with a preference for Microsoft Blazor but openness to alternative frameworks (e.g., Razor Pages, MVC,)

OBJECTIVES

React/Angular front-ends with .NET back-ends) where justified. Responses should assume: •
•
•

Existing authentication and authorization must be fully preserved and transferred, with no degradation in security posture.
Existing service and data layers are ASP.NET Core / C# and should be leveraged, not