REQUEST FOR INFORMATION.pdf

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 replaced.

• The modernization project includes training development staff on migrating coding practices and patterns from Web Forms to the chosen approach.

The modernization project will address approximately 650 UI module components consisting of both web pages and reusable page components.

Please provide concise, evidence-based input in the areas below. You do not need to address every question; focus on areas where your organization has demonstrated expertise.

1. Decomposition: Recommended approach to identify and extract UI logic (code-behind, ViewState, server controls) into component-based, testable patterns (e.g., Blazor components, MVC views, Razor, or SPA components).

2. State Management: Strategies to replace ViewState/postback patterns with modern state and event models, including session handling and mitigation of latency.

3. Server Controls & Third-Party Libraries: Methods to inventory/replace Web Forms server controls and equivalent Blazor/ASP.NET Core components; note existing use of Telerik by Progress control libraries and the plan to continue use after modernization.

4. Routing & URL Structure: Preserving or refactoring routing to minimize impact on external links, bookmarks, and integrations.

5. Data Binding & Validation: Replacing web forms binding with model binding, data annotations, and middleware-driven validation in ASP.NET Core.

6. Testing: Introducing unit, integration, and UI tests to validate functionality parity during phased migration.

7. Accessibility (Section 508): Approach to achieve/maintain Section 508/WCAG compliance throughout migration; tooling and audit steps.

Security, Identity, and Authorization

1. Se Authentication/Authorization Parity: Detailed plan to transfer existing identity, RBAC, and policy-based authorization in ASP.NET Core without breaking existing workflows.

2. Zero Trust: Recommendations to align the modern UI with agency Zero Trust patterns.

3. Secrets and Configuration: Use of Azure Key Vault, OWASP considerations, and secure configuration.

Architecture and Technology Selection

1. Blazor vs. Alternatives: Comparative analysis of Blazor Server, Razor Pages/MVC, or

SPA frameworks (Angular/React) with ASP.NET Core APIs, including trade-offs in performance, developer productivity, accessibility, maintainability, and long-term support.

2. Interoperability: How your approach leverages existing ASP.NET Core/C# service and data layers.

3. Deployment and Hosting: With hosting in Microsoft Azure, recommend scaling patterns, production configuration, and observability.

4. Performance: Ensure the architecture supports multi-threading for improved performance.

• Technical guides

• Installation and configuration instructions

• Troubleshooting tips

Delivery Approach, Milestones, and Risk Management

1. Phased Migration Plan: A work-breakdown with milestones tailored to Web Forms migration.

2. Risk Register: Top migration risks and mitigations.

3. Cutover and Coexistence: Strategies for parallel run, feature toggles, and rollback.

4. Performance Benchmarks: Baseline establishment and post-migration KPIs.

5. Dependencies and Assumptions: Environment constraints, licensing, accessibility tooling, test data, and integration endpoints.

Training & Knowledge Transfer

1. Training Plan: Curriculum to upskill engineers from Web Forms to ASP.NET

Core/Blazor.

2. Mentored Implementation: Pair-programming/coaching models; component library standards; code reviews; style guides.

3. Architecture Review: Advise engineers on alignment of existing modernization paths for data and service layers (such as for Entity Framework) with UI path.

Requested Information

Keeping the details of the project in mind, please provide information on the following topics.

General Information:

1. Executive Summary: A brief overview of the vendor's solution and approach

2. Technical Approach: Detailed description of the proposed eGMS monitoring system and how it meets the specified requirements.

3. Project Plan: Timeline and milestones for the installation and configuration process.

4. Qualifications: Information on the vendor's experience and expertise in providing similar solutions.

5. Cost Proposal: Detailed breakdown of all costs associated with the project, including software, professional services, documentation, and training

6. References: Contact information for at least three references from previous clients who have implemented similar solutions

HOW TO RESPOND

Interested organizations responding to this RFI may provide a Capabilities Statement or other relevant information regarding the organization’s capabilities as they relate to the information contained herein. All responses should include the following information:

• Company name, address and website, SAM UID

• Company business size, socio-economic status

• Any contracts the organization currently holds (GSA Schedule, NASA SEWP, etc.),

• Point-of-Contact name, position, telephone number and e-mail address

• Organizational experience and technical capabilities of the organization which meets the stated objectives.

• An overview of the leading solution(s) options your firm would recommend that take into account the information provided herein.

• Concerns that should be considered by the USITC as part of any potential solicitation.

Interested organizations may submit a response to this RFI, with the information requested above, and any other applicable information, on or before 4PM EST, Thursdau, November 19, 2026. Please submit all documentation VIA EMAIL to cydennis@neh.gov and jkennedy@neh.gov

Please include in the subject line of the email RFI eGMS Modernization Strategy

Organizations are discouraged from submitting any information deemed proprietary. However, if elected to submit proprietary information, the organization bears sole responsibility for marking said information as proprietary to ensure appropriate safeguarding by the Government. The Government shall not be held liable for any damages incurred if proprietary information is not properly identified. All submissions become the property of the Government and will not be returned.

mailto:cydennis@neh.gov