Request for Information (RFI) #140D0426R0032 Department of the Interior (DOI), Interior Business Center (IBC) – Human

Resources Directorate (HRD), IBC-HRD – AI Tools and Automations

General Information This RFI notice is issued solely for information and planning purposes - it does not constitute an invitation for bid, request for quotation (RFQ), request for proposal (RFP), or an obligation on behalf of the Government or a promise to issue a solicitation in the future. The Government is not seeking proposals and will not accept unsolicited proposals at this time. Vendors responding to this notice are advised that the U.S. Government will not pay for any information or administrative costs incurred in response to this RFI; all costs associated with responding to this RFI will be solely at the interested party's expense. Not responding to this RFI does not preclude participation in any future solicitation, if issued. Interested parties are responsible for CLEARLY MARKING proprietary or competition sensitive information contained in their response. No classified, confidential, or sensitive information should be included in your response. Please be advised that all submissions become Government property and will not be returned. Marketing brochures and/or generic company literature will not be considered and shall not be sent in response to this RFI.

Purpose of RFI IBC’s Human Resources Directorate seeks information from industry on AI tools and applications capable of securely supporting a mainframe-centric, payroll-focused, PII-regulated environment across the full systems software development lifecycle and operational landscape. HRD maintains and enhances an integrated personnel and payroll system, along with multiple supporting subsystems, that interface with numerous Federal systems and serve more than 300,000 employees across multiple agencies and commissions.

HRD is seeking solutions that can automate testing (script, unit, regression, load, performance), strengthen batch processing and JCL scripting/job-run comparisons, and support comprehensive database management (configuration, capacity and space utilization, security recognition, forecasting and drift detection, patching, migrations, conversions, and integrity). HRD also requires capabilities tailored to payroll operations, including payroll calculations, retroactive processing, W-2 and ACA processing, annual pay adjustments, and file generation and transmission.

Additional areas of interest include AI-enabled code and infrastructure analysis and refactoring (mainframe module assessment, call-routine mapping, bug identification, historical change analysis, and LLM-based scanning), automated generation of system documentation, training materials, and analytical reports, and customer service workflow automation (ticket creation and routing, self-service tools, legal and payroll guidance). Solutions must support cross-platform integration with Federal partners such as OPM, IRS, and shared service providers; operate in a non-multi-tenant environment; align with FedRAMP controls; meet

Section 508 requirements; and provide governance, auditability, scalability, and deployment options suitable for IBC HRD.

Responses to this RFI will help HRD identify viable industry solutions and vendors capable of meeting these mission needs and will inform the development of future procurement strategies.

Background: IBC as a Shared Services Provider IBC is an Office of Personnel Management (OPM) authorized Shared Service Provider (SSP) that provides systems and services to its parent, DOI, and 54 other federal agencies (customers). HRD fully maintains and enhances its integrated personnel/payroll system and its supporting sub systems. HRD’s integrated personnel and payroll system and sub systems interface with several Government computer systems which service more than 300,000 employees (customers) from numerous Federal agencies and commissions.

The operational environment includes:

• Large-scale mainframe and batch processing ecosystems

• Mission-critical payroll and personnel systems containing Personally Identifiable Information (PII)

• Extensive JCL, ADBAS, batch scheduling, and interface dependencies

These sub systems complement HRD’s integrated mainframe personnel/payroll system in various ways to include:

• Payroll/personnel data warehousing

• Service management ticketing

• Timekeeping and attendance

• Workforce tracking

• Learning, development, and performance management

• Planning, hiring, tracking

Our systems provide thorough support throughout the entire development and maintenance life cycle. This includes the creation and implementation of methodologies and standards, in-depth requirements analysis, and comprehensive business process evaluation. Additionally, we conduct extensive technology research, manage communications effectively, and design robust system architecture. Our expertise extends to system development and maintenance, software development, application re-hosting, and the conversion of legacy systems. By integrating these diverse elements, we ensure that our solutions are both innovative and reliable, while meeting the highest standards of quality and performance.

Objectives

IBC-HRD is seeking a Vendor who provides an AI-Tool or Application which will compliment HRD systems in their ability to:

• Automate and Produce o Script test software o Unit test software o Regression test o Load test o Performance test o Batch processing capabilities o Database configuration – preserving integrity and infrastructures o Database space utilization o Database security recognition o Patch upgrades o New client migrations

• Online/Production – Automated job run and compares o QA (Quality Assurance) processing and testing o Production script case – data input o W2s o Annual pay raise implementation o ACA (Affordable Care Act) processing o Software version release cadence o File creation, generation. Transmission (internal and external) o Payroll calculation and retroactive processing o Workflow generation

• Assess Production and Test Databases o Conversions of software o Data transfer and conversion o Integration o Database performance o Capacity o Usage logs o Security o JCL scripting

• Analyze code and infrastructures o Ability to scan various LLMs (large language models) in its entirety o Mainframe o Refactoring code o Module assessment o Call routines o Bug fixes o Historical pinpoints of software modifications o Mapping

• Create system documentation and training materials

• Generate data analysis reports among systems

• Customer Service Ticket Generation o Situational customer ticket creation o Assigning of ticket to corresponding branch or working group o Associated and relevant resources applicable for usage with ticket generation

Legal documents Payroll or personnel guides o Job aids o Bots

• Self Help Feature o Situational customer inquiry for payroll or personnel processing o Associated and relevant resources applicable for payroll or personnel processing o Bots

• Cross platform compatibility o Assess HRD’s systems and ability to work in partnership supporting HRD functions o Integrate with non HRD systems and Federal Agency partnering

OPM – Office of Personnel Management IRS – Internal Revenue Service SSPs – Shared Service Providers AQD – Acquisitions Services Directorate (IBC) FMD – Financial Management Directorate (IBC) OMB – Office Management Budget

IBC-HRD Essentials

• Non-Sole Source methods for IBC-HRD’s determination of partnering with an AI- Tool/Application or Vendor.

• Non-multi-tenant environments o The AI-Tool/Application will not be a multi-tenant environment for users outside of IBC-

HRD.

• IBC Policies and Security o Support the enforcement of IBC IT and Security Policies and Procedures.

o FedRAMP-aligned controls o 508 Compliance o System security plans and policies provided

Submission Requirements Vendors interested in participating in this market research activity are requested to submit the following (Note: if vendors are proposing more than one solution, please provide a separate response for each proposed solution):

1. Corporate Information requested in Section 1.

2. Narrative capability statements addressing the business requirements in Section 2. Please limit your response to each business requirement to 2 pages (font no smaller than 11pt). General marketing information or reference to vendor web site as a response to any of the business requirements will not be considered responsive to this notice. (7-page maximum)

3. Rough Order of Magnitude in Section 3.

Vendors must identify any proprietary information submitted in response to this RFI. The proprietary information must be clearly marked as proprietary. The government will not treat any other information as proprietary.

The Government reserves the right to contact, or not contact, any party responding to this RFI to obtain further information for market research purposes. The government will not notify respondents of the results of the information received and will not return submittals to the sender.

All interested sources must respond to any potential future solicitation announcements separately from responses to this RFI.

Interested sources that believe they have the ability to provide the solution to the requested functionality listed herein should submit responses electronically via email to Christina Lene (christina_lene@ibc.doi.gov) and Lilian Huyen (lhuyen@ibc.doi.gov). Please reference “HRD AI Tools and Automations RFI # 140D0426R0032 ” in the email subject line. No telephone, mail, or fax responses will be accepted. Other than the opportunity to ask questions as detailed below, inquiries for additional information and/or a request for a meeting to discuss this RFI/sources sought notice will not be accepted. Responses must be received by 5:00pm EST, April 17th, 2026. Please be advised that it is the responders’ responsibility to ensure the Government receives your RFI submission on or before the specified due date.

Questions Written questions are to be submitted via email to the contact information listed below, by no later than March 17th, 2026, 3:00pm EST.

Christina Lene at christina_lene@ibc.doi.gov and Lilian Huyen at lhuyen@ibc.doi.gov

All questions must be submitted by the date and time listed above or they may not be addressed before the RFI closing date. All questions received by the due date will be answered via an amendment to the RFI.

Section 1 – Corporate Information

Corporate Information Template

CORPORATE INFORMATION TEMPLATE

REQUESTED INFORMATION VENDOR RESPONSE

1) Organization Name, Address, Website

2) Organization Unique Entity Identifier (UEI) number

3) Point of Contact, Title of point of contact, Email Address, Telephone Number

4) Please provide the name of your solution(s)

5) Is the solution FedRAMP authorized (if applicable)?

a. Provide the Package ID

6) Which business categories do you fall under?

Large Business Small Business (SB) Small Disadvantaged Business (SDB) Section 8(a) Business Woman-Owned Small Business (WOSB) Economically Disadvantaged Woman-Owned Small Business (EDWOSB) Historically Underutilized Business Zone (HUBZone) Small Business Veteran-Owned Small Business mailto:christina_lene@ibc.doi.gov mailto:lhuyen@ibc.doi.gov mailto:christina_lene@ibc.doi.gov mailto:lhuyen@ibc.doi.gov

CORPORATE INFORMATION TEMPLATE

REQUESTED INFORMATION VENDOR RESPONSE

Service-Disabled Veteran-Owned Small Business (SDVOSB)

7) What Government-Wide Acquisition Contracts (GWACs) or General Services Administration (GSA) Multiple Award Schedule(s) (MAS) or NASA SEWP do you currently hold that would support this requirement?

a. Provide each overarching GWAC, GSA

MAS or FSS or NASA SEWP contract number and expiration date that would support this requirement.

8) Would you have to partner with other industry partners to support this requirement?

a. If yes, please provide the longest duration pricing can be obtained.

9) Please provide the duration of available pricing (software, labor, etc.). Example, if the Government determines it requires a 10, 7, 5, etc. year contract, will pricing be available?

10) Identify Government agencies of a similar size for which the vendor has implemented the solution(s) identified in this response.

a. Indicate whether you were the prime or the sub.

b. If the sub, indicate the % or work performed, and the specific work performed.

c. Include Agency reference and contact information (name, title, phone, and email).

11) Describe any third-party alliances, relationships, or dependencies you would utilize to implement or provide the solution(s)

Section 2 – HRD AI Tools and Automations Requirements Vendors shall provide written responses describing how their AI tools or applications meet the objectives and essentials defined by IBC-HRD. Responses must address both the objective perspective (how the solution advances HRD’s mission) and the essentials perspective (how the solution meets required technical, security, and operational standards). Responses should be detailed enough for IBC-HRD to determine solution suitability, while not exceeding seven total pages.

IBC-HRD welcomes a wide range of submission formats to help the organization understand the capabilities, maturity, and applicability of AI tools and applications that may support its mission. Vendors may include any combination of the following categories to demonstrate the breadth and depth of their solutions.

• Written Submissions o Demonstrating your technical approach and methodology o User story papers showing real-world applications o Case studies highlighting implementation success o Capability statements

• Visual Demonstrations o Product videos o Solution architecture diagrams o Interface screenshots o Process flow visualizations

• Access to sandbox environment for hands-on exploration o Guided demo sessions o Sample data sets o Interactive tutorials

• Supporting Evidence o Client testimonials and statements o Performance metrics o Success stories o Industry supported improvements and figures o How does your AI-Tool/Application improve other systems alike

Save money and time

• Corporate and Solution Overview o Company profile and Federal experience o AI platform overview and maturity

• Architecture and Deployment o Platform architecture diagram o Multi-agent design and orchestration o Deployment options and network models

• Security and Compliance o FISMA posture and ATO experience o NIST control coverage mapping o Zero Trust alignment description

• Functional Capabilities o Capability descriptions by domain o Mainframe and payroll-specific experience o Integration approach

• Governance and Controls o Human-in-the-loop processes o Audit and logging architecture o Model lifecycle management

• Scalability and Performance o Throughput and concurrency limits o High-availability design o Disaster recovery posture

Section 3 – Rough Order of Magnitude Funding constraints require vendors to present a pricing approach that aligns with federal acquisition realities while supporting a large-scale AI tools and automations solution. Vendors shall describe their preferred pricing structure for each major cost component and identify where firm-fixed-price, labor-hour, subscription, or transaction-based models are most appropriate. The response must also address options that reduce or defer upfront government investment.

Pricing Structure Requirements Vendors shall identify the pricing model recommended for each component of the proposed AI solution. Examples include firm-fixed-price for predictable implementation tasks and labor-hour or usage-based pricing for variable or ongoing services. The structure should reflect how the vendor typically delivers enterprise-scale AI platforms and automations.

Creative Pricing Expectations Vendors shall describe innovative pricing approaches that minimize large upfront expenditures.

Examples include deferred-cost recovery, subscription-based implementation, or transaction-based pricing tied to recurring HRD processes such as payroll, training completions, or automated document generation. These models may allow the government to invest a notional amount upfront while the vendor recovers remaining costs through usage-based fees.

• Migration, Setup, and Conversion Cost Requirements Vendors shall provide rough estimates and preferred pricing structures for:

o Program and project management o Requirements analysis and system configuration o Data conversion and data-load activities o Interface development and integration o Testing activities o Training for end users and administrators o Hosting and infrastructure setup o Change-management support o Expected timelines for each activity shall be included.

• Annual Operations and Maintenance Costs

Vendors shall provide ROM estimates and pricing structures for ongoing O&M, including:

o Hosting and storage o Core application support o Hardware, if applicable o Network connectivity o Technology refresh cycles o Interface support, including Section 508 compliance o Security operations o Audit support o Ongoing training o Tier 1, 2, and 3 customer support

• Estimated Timeframe for Return on Investment (ROI) Vendors shall describe typical ROI timelines based on prior implementations, including:

o How long does it typically take for organizations to recoup the upfront investment through operational efficiencies, cost savings, and reduced maintenance costs?

o What are the primary cost drivers that influence this ROI timeline?

• Benchmarked Data and Case Studies

If available, vendors shall provide anonymized benchmark data or case studies from federal, state, or large enterprise implementations demonstrating:

o ROI timelines o Financial impacts o Efficiency gains o Cost-avoidance outcomes

• Licensing, if applicable If licensing applies, vendors shall identify supported models:

o Fixed enterprise licensing o Per-user licensing o Transaction-based licensing o

• Creative Pricing Solutions, if applicable Vendors may propose any additional pricing innovations that reduce upfront investment, distribute costs across fiscal years, or align payment with usage, outcomes, or performance.

Section 4 – HRD Vendor one-on-one sessions IBC-HRD may conduct vendor one-on-one sessions after reviewing RFI submissions. These sessions are intended to help HRD validate vendor capabilities, clarify solution approaches, and assess how well proposed AI tools and automations align with HRD’s mission needs. Sessions may take several forms, including in-person pilots, workshops, virtual demonstrations, or document exchanges.

Sessions may range from 1 to 6 hours depending on the depth of the capability being reviewed. Activities may include walkthroughs of AI features, demonstrations of automation workflows, evaluation of training or knowledge-management functions, or review of lessons learned from similar implementations. If held, these one-on-one sessions are anticipated to occur in mid-2026.

DISCLAIMER

The purpose of this market research is to survey prospective vendors in order to collect data, comments, and other information pertaining to this industry. The information submitted in response to this announcement will assist IBC in determining the appropriate procurement strategy in the future.

The Government is under no obligation to award a contract as a result of this announcement. No funds are available to pay for any information received from potential sources. All information submitted in response to this announcement is strictly voluntary.

Only electronic mail will be acceptable for vendors’ submissions. The Government does not intend to provide feedback or evaluate submissions.