RFI_Instructions_INFO_ONRR_ITMod_Integrator_Support_v3_1.pdf

RFI # DOIDFBO250003 ONRR IT Mod Integrator Support Page 1 of 26

Request For Information (RFI) RFI# DOIDFBO250003 – ONRR IT Modernization (IT Mod) Integrator Support

Contents

1.0 RFI

1.1 Introduction:

1.2 Actions:

1.3 General Information:

1.4 RFI Purpose

1.5 Submission Instructions

2.0 ONRR IT Mod Project Overview

2.1 Background

2.2 MRMSS (2000 – Present)

2.3 Business Process Re-engineering 2017-2020

2.4 IT Mod Vision & Objective

2.5 IT Mod Efforts (2021 – Present)

2.6 IT Mod Goal Moving Forward

3.0 Vendor ONRR IT Mod Integrator RFI Survey Response

1.0 RFI

1.1 Introduction:

The Department of the Interior (DOI) Office of Natural Resources Revenue (ONRR) is seeking information from industry to assist with the planning and development of an acquisition strategy to holistically and seamlessly complete (develop/deliver/implement/maintain) the modernization of their IT system(s) environment to align with their Business Process Reengineering (BPR) findings. To prepare for this, ONRR has conducted a business process review, prototype exploration, and even some systems development. The next step is to acquire long-term vendor(s) support in the areas of system development services and software tools to complete (develop/deliver/implement/maintain) the new modernized state for ONRR.

1.2 Actions:

1. Review this document and the referenced attachments in full.

2. Complete the Survey provided in section 2.0 entitled “Vendor ONRR IT Mod Integrator RFI

Survey Response”. An editable survey template (attachment 7) is provided as a separate document to this RFI.

3. Provide an OPTIONAL Capability Statement, Advice, and Considerations response. (DO NOT submit marketing brochures and/or generic company literature as this documentation will not be reviewed)

RFI # DOIDFBO250003 ONRR IT Mod Integrator Support Page 2 of 26

1.3 General Information:

This Request for Information (RFI) is issued solely for information and planning purposes - it does not constitute an invitation for bid, request for quotation, request for proposal, 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 notice will be solely at the interested party's expense. Not responding to this notice 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 or reviewed and should not be sent in response to this notice.

• Anticipated Solicitation Date: Late 3rd quarter FY25 (subject to change)

• Anticipated Award Date: 4th quarter FY2026 (subject to change)

The BPR attachments/study of ONRR processes and systems contains certain vendor recommendations that ONRR has and may continue to consider as a possible solution, but ONRR does not want to be constrained by any single solution set and/or recommendation. In fact, this RFI indicates our intentions and expectations of future interaction with the commercial market, ensuring we continue to pursue holistic solutions for ONRR IT Modernization (IT MOD) that present the overall best value to ONRR's mission and operations.

The redacted study is attached to assist vendors in gaining a deeper understanding of ONRRs operational circumstances, current systems, and IT Mod efforts to date.

1.4 RFI Purpose

The goal of this RFI is to utilize industry feedback to assist the Government in developing an acquisition strategy to implement a modernized business system(s) for ONRR.

The results of the RFI will allow the government to:

1. Obtain industry experience, best practices, recommendations, and lessons learned from the vendor community.

2. Better understand potential commercial solutions available to meet ONRR’s needs.

3. Assist the Government in drafting informed requirements documents.

4. Assist the Government in developing an acquisition strategy.

5. The Government may meet with a limited number of potential industry partners who provide a comprehensive response to the RFI. These meetings will allow the Government to gather additional commercial market information.

Vendors should provide basic information regarding their experiences and capabilities and an indication of how they would approach working with ONRR to achieve its IT Modernization goals and objectives.

1.5 Submission Instructions

If you are interested in participating in this market research activity, you are requested to review this announcement and provide the requested information. The Government is very interested in industries’ feedback and encourages industry to provide specifics and details of additional information that may be required to improve and incorporate into documentation currently under development.

RFI # DOIDFBO250003 ONRR IT Mod Integrator Support Page 3 of 26

To provide an acceptable response to this RFI, respondents are requested to submit the following documents:

1. Complete the attached “Vendor ONRR IT Mod Integrator RFI Survey Response” limited to 45 pages and using no smaller than 11-point font to complete the form. An editable survey template (attachment 7) is provided as a separate document to this RFI.

2. (OPTIONAL) Provide a Capability Statement, Advice, and Considerations response – This vendor prepared document will provide additional vendor information and feedback to include specifics and details of information that may be required to improve the future solicitation to include documentation, MRMSS System (as defined in 2.2) introduction/demo, existing IT Mod Product introduction/demo, industry experience, best practices, recommendations, time frames required to respond, period of performance, and lessons learned from performance in a single vendor environment vs. multi-vendor for scope similar to ONNR’s requirement. Recommended COTS/Cloud solutions and/or products that would meet ONRR requirements with other known federal implementations of such/similar solutions (if any). Singular ERP vs multi-platform best in class thoughts for ONRR requirements. 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. This response is limited to 15 pages with no smaller than 11-point font.

The Government reserves the right to contact, or not contact, any party responding to this notice in order 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 and perform the services listed herein should submit the information requested electronically via email to shanda_georg@ibc.doi.gov and kimberly_rainey@ibc.doi.gov. Please reference RFI # DOIDFBO250003 ONRR IT Mod Integrator in the email subject line. No telephone, mail, or fax responses will be accepted. Inquiries for additional information and/or a request for a meeting to discuss this RFI will not be accepted. Responses must be received by Noon Eastern Time on 11/25/2024. No extension in the response date will be granted.

Please be advised that it is the responders’ responsibility to ensure the Government receives your RFI submission on or before the specified due date.

RFI # DOIDFBO250003 ONRR IT Mod Integrator Support Page 4 of 26

2.0 ONRR IT Mod Project Overview

2.1 Background

The U.S. Department of the Interior (DOI) Office of Natural Resources Revenue (ONRR) is responsible for the management of revenues owed for the development of the United States’ energy and natural resources on the Outer Continental Shelf and onshore Federal and Indian lands. ONRR’s primary mission is to provide for the efficient, timely, and accurate collection and disbursement of all royalty payments, rentals, bonuses, fines, penalties, assessments, and other revenue due to the Federal Government, Indian Tribes, States, and the American people from these lands. This effort is one of the Federal Government’s greatest sources of non-tax revenues. In support of its mission, ONRR performs revenue collection and disbursement; distribution; collection and validation of production and royalty reports; compliance and enforcement; and workload management of all case types defined by ONRR to include data validation cases, compliance cases, enforcement cases, and appeals cases.

Through the completion of a Business Process Re-engineering (BPR) exercise in the 2017-2020 timeframe, ONRR analyzed and documented the current system and process limitations and researched industry solutions that could be considered.

As a result of this BPR exercise and recommended next steps, ONRR initiated its ONRR Modernization (IT and Operational) effort to ensure that it is capable of continually fulfilling its core mission efficiently for the benefit of all Americans.

In 2021, with these BRP results and recommendations in mind, ONRR kicked off its IT Modernization (IT Mod) efforts with a primary goal of replacing the Minerals Revenue Management Support System (MRMSS) with new solution(s). The IT Mod initiative aims to improve operational efficiency by implementing industry best practices, streamlining business processes, and eliminating manual tasks.

ONRR stated that its high-level goals for IT Mod are to:

• Modernize ONRR systems to simplify industry interactions with DOI for energy and mineral revenue processes and increase overall compliance.

• Modernize ONRR systems to improve the accuracy, efficiency, and timeliness of energy and mineral revenue processes.

• Reduce energy and mineral revenue data errors, compliance issues, and the need for enforcement.

• Modernize ONRR systems to take advantage of IT Automation efforts such as but not limited to

Artificial Intelligence/Machine Learning (AI/ML) and Robotic Process Automation (RPA).

To achieve these goals, ONRR must modernize not only the MRMSS but also all ONRR IT systems that support revenue collection and disbursement processes.

The next step is to acquire long-term vendor(s) (IT Mod Integrator) support in the areas of system development services and software tools to complete (develop/deliver/implement/maintain) ONRR's new modernized state.

2.2 MRMSS (2000 – Present)

ONRR currently performs the vast majority of its mission work through the Minerals Revenue Management Support System (MRMSS) and various ONRR stand-alone systems and offline processes.

The MRMSS system was deployed to operation in the year 2000. MRMSS is a mixed financial system, which includes the hardware and software that ONRR uses to perform its revenue collection, verification, and disbursement-related duties. Over the years MRMSS has come to rely heavily on major customizations of PeopleSoft, including custom-built accounts payable, accounts receivable, and general ledger modules

RFI # DOIDFBO250003 ONRR IT Mod Integrator Support Page 5 of 26 that were built over a decade ago and are updated as needed. Due to its mission-essential function to collect and disburse revenues, MRMSS is considered a high-value asset as defined by criteria established by the Department of Homeland Security.

The current number of users within the MRMS Community is estimated at: ONRR and other government users ~1,000 and external users ~3,000

The MRMSS is comprised of 3 major mission components including:

1. Financial component (MRMSS-Financial)

a. The strategic goal of the MRMSS-Financial function is to collect, account for, and disburse Federal and Native American mineral lease revenues to the proper recipients in a timely and accurate manner per applicable laws, regulations, and lease terms, approximately $10 billion in annual revenues are processed through the MRMSS.

b. MRMSS-Financial accounts for all Federal and most Native American minerals rents, royalties, bonuses and their distribution/disbursement to the U.S. Treasury, counties, States (states generally receive 50% of the revenues collected in their state), and Native Americans (Native Americans receive 100% of their revenues).

c. The MRMSS-Financial also issues bills for late payment or non-payment of royalties and other lease term obligations. Most of the input data for MRMSS-Financial consists of royalty reports and production reports received from the industry via an electronic reporting contractor.

d. MRMSS-Financial relies on major customizations of PeopleSoft®, and Oracle’s Business Process Management SOA Suite (BPM SOA) utilizing Oracle Business Rule (OBR) engine.

MRMSS-Financials PeopleSoft® financials is composed of several modules, including Production, Reference, Royalty, Accounts Receivable, Accounts Payable, Billing, Lease Account Balance, Appeals Tracking System (ATS), General Ledger, Distribution & Disbursement, and Exception Processing.

2. Compliance components (MRMSS-Compliance)

The compliance functions consist of custom-built tools aimed at assuring that ONRR has collected every dollar due and all required reporting. These tools include basic case management tools (tracking assignments and progress by employee and property), targeting tools, electronic work papers, and other specialized tools for analyzing variances between reported and expected values, and documentation. Compliance activities result in coverage of a significant portion of the royalty revenues paid each year. Many of the components are customized utilizing .Net framework.

3. MRMSS Analytical and Report Page (MRMSS-MART)

The MRMSS MART provides a repository of historical financial and production information used by ONRR users, BLM, BOEM, Bureau of Safety and Environmental Enforcement (BSEE), other Federal agencies, State and Tribal entities, and Industry. The MART also provides data-mining tools for ONRR, States and Tribes, other government agencies, and industry to run queries and reports and download the results of their royalty and production data and revenues received and disbursed.

Most of the input data for MRMSS consists of reference data received from Federal and Indian land management agencies in various formats (e.g., text files, email, and physical mail), and royalty reports, production reports, and payment information received from industry via an electronic

RFI # DOIDFBO250003 ONRR IT Mod Integrator Support Page 6 of 26 reporting contractor (eCommerce). Initial validation of industry reports occurs in eCommerce and MRMSS; additional validation and compliance actions are performed in offline processes and stand-alone systems such as the Volume Comparison Tool.

ONRR believes that it will, over time, become less effective at its core mission if it continues to invest in heavily customized systems that tend to carry increased technical debt over the years. That said in 2024, ONRR successfully migrated MRMSS to the Oracle Cloud Infrastructure (OCI) to address the aging Exa hardware support concerns. Since OCI went live, ONRR has seen significant advantages, performance improvements, and hosting cost benefits. In addition, it appears barriers to eliminating technical debt/customization in the OCI environment may be much more feasible than prior to migration. It is possible some of the new OCI benefits could assist or streamline modernization initiatives if deemed to be the best holistic fit or value to ONRR.

In addition, across the government, flexible cloud-based ERPs/systems are replacing traditional, on-premises ERPs. ONRR recognizes that simply investing in a modern ERP is not enough, however, as many agencies will not see a return on this investment if they do not have a strong integration governance strategy. Adopting a new approach will require new organizational governance as well as modernized business and system processes.

2.3 Business Process Re-engineering 2017-2020

The Business Process Re-engineering (BPR) exercise completed during the 2017-2020 timeframe analyzed and documented the current system and process limitations, as well as researched industry solutions that could be considered.

The results/reports of BPR*, as outlined below, are the core foundation of ONRR Modernization (IT and Operational) efforts:

• Attachment 1 – ONRR BPR As-Is Final Report.pdf

• Attachment 2 – ONRR BPR To-Be State Report Final.pdf

• Attachment 3 – ONRR BPR Finalization Report.pdf

• Attachment 4 – ONRR IT Modernization Functional Modules Final.pdf

• Attachment 5 – ONRR IT Modernization Requirements Document Final.pdf

• Attachment 6 – ONRR IT Modernization Requirements Final.xlsx *These six attachments represent the summary-level deliverables from BPR efforts. As alluded to in these documents, ONRR received a process map and narrative for each of the As-Is and To-Be which may be made available as part of the larger solicitation reading room.

BPR and the resulting artifacts, recommendations, and process map represent a significant modernization milestone for ONRR. In the context of the system development lifecycle (SDLC), BPR represents a key component of up-front planning and analysis needed to scope the future system. In addition, the work the BPR team has done to date provides a strong platform for ONRR to modernize its processes and system;

ONRR’s core mission of mineral revenue collection, verification, enforcement, and reporting is fundamentally dynamic and ever-changing. The successful implementation of a modernized system will not halt this constant change or fully address every BPR recommendation, as several are nontechnical in nature. ONRR can only achieve lasting success by harnessing a spirit of continuous improvement.

Please note that while these documents are slightly dated, ONRR believes they remain a solid foundation of ONRR Modernization efforts (IT and Operational) and commits to continually evaluate, update, and prioritize this foundational information to help set priorities and objectives. Moving forward, an important

RFI # DOIDFBO250003 ONRR IT Mod Integrator Support Page 7 of 26 part of the process and partnership will require ONRR and Integrator(s) to discover/revalidate with Subject Matter Experts (SME’s) and Product Teams for accuracy and validity prior to pursuing operational changes and/or product development. Not all requirements/recommendations will be technical in nature and may fall outside the scope of IT Modernization.

2.4 IT Mod Vision & Objective

As previously noted, with the current state of MRMSS, BPR results and recommendations, and IT Modernization Goals, ONRR recognizes without further proactive action, the current MRMSS state poses the following challenges:

• Applications are complex and difficult to maintain. Many of the applications are highly customized due to regulations, necessary tasks or business process, and incremental enhancements that have occurred since the inception of the system. ONRR conducted a business process review to revise its processes.

• ONRR has an outdated user interface for external and internal users. Users expect and should experience a modern computing experience. With the introduction of new technologies, ONRR can enhance the user experience with a focus on a human centric design.

• There is a lack of real-time updates to the system. Nightly batch processing results in a lack of real-time data updates within the system. Such real-time updates will require both technical, business process, and requirement changes.

• There is a lack of integration with other DOI systems. Seamless integration with other DOI systems (e.g. Mineral and Land Records System (MLRS), Technical Information Management System (TIMS), Trust Asset and Accounting Management System (TAAMS), Automated Fluid Minerals Support System (AFMSS), etc.) is needed to improve how data can be used, reduce data errors and submission rejections, and streamline processes.

As a result, ONRR initiated its IT modernization effort to implement alternative technologies to ensure that it is capable of continually fulfilling its core mission efficiently for the benefit of all Americans. It is expected this will result in the following:

1. Reduced technical complexity of business rules, business processes, and data.

2. Reduced costs to the agency for equipment, development, business operations, information technology, and staffing.

3. Reduced customization of technical solutions/products.

4. Increased Operations & Maintenance capabilities and flexibilities related to functional modules.

5. Reduced burden to energy and extractive industry participants, most importantly the reporting community and revenue payors.

6. Clarified and streamlined data needed for ONRR and for sharing with other Department of Interior (DOI) and external entities and stakeholders.

7. Improved business process flow significantly reduced customized coding, and maximized delivered software.

8. Gained advantages from automation to reduce or eliminate duplication and errors, unnecessary business functions, external stand-alone databases, and the manual manipulation of data external to the system of record.

9. Implementation of commercial software to eliminate custom coding in favor of a simplified system with a low-code platform to address the to-be functional modules.

RFI # DOIDFBO250003 ONRR IT Mod Integrator Support Page 8 of 26

2.5 IT Mod Efforts (2021 – Present)

Building upon the BPR Module recommendation, a vision for using the best-in-class platform(s) to form the ONRR product(s) foundation was pursued. An ONRR Product overlay to BPR Modules is depicted in Figure 1, with each ONRR Product being built on best-in-class platforms/applications to sustain the foundation of ONRRs future modernized state:

Figure 1 An overlay of the BPR Recommended Modules and ONRR Specific visioned platforms.

Over the last 3 years (12/2021-Present), ONRR has conducted several stand-alone procurements to select system development partners and best-in-class software tools/platforms to deliver module/product specific capabilities. The results of these efforts to date have been three different/independent contract partners (one per ONRR Product) building and integrating simultaneously on three separate platforms utilizing the Scrum/SAFe framework with ONRR acting as the main ‘integrator’.

RFI # DOIDFBO250003 ONRR IT Mod Integrator Support Page 9 of 26

A brief overview of the Product progress to date includes:

• ONRR Connect

Salesforce: The Salesforce Software as a Service (SaaS) tools were selected for their robust Customer Relationship Management (CRM) capabilities, Self Service Portal for industry/community access, and the operational/mission interaction between the two.

Active development since 2022 leading to successful deployments of CRM initial operating capability/minimal viable product (MVP) (September 2023) and many subsequent value features releases (R1.1 November 2023, Release 1.2 December 2023, Release1.4 February 2024 etc.).

Developed and supported to date by Accenture Federal Services, LLC

• ONRR DASH (Data Analytics Solutions Hub)

Snowflake, Power BI, Qlik, and Azure Data Lake: The Snowflake application, coupled with Azure Data Lake and Power BI tool, was selected for the DASH requirements.

Active development since 2021, leading to successful deployment in September 2024 of initial operational capabilities.

Developed and supported to date by CGI Federal

• OFMS (ONRR’s Financial Management System)

SAP S4HANA: After studying the industry, ONRR intended to integrate/build upon the DOI Financial Business Management System (FBMS), which is a configured version of SAP S4HANA. The financial processes in FBMS are comprehensive and encompass broad business functions, both financial and mission, across DOI, e.g., disbursements through the Treasury, federally compliant fund management capabilities, and many bureaus' mission-specific capabilities. Some of these features presented attractive foundational architecture for ONRR’s OFMS vision, leading to the initial partnership/exploration. That said, ONRR-specific requirements not currently configured or operational in FBMS would require shared service configuration and customization unique to ONRR. In the end, ONRR did not implement FBMS but did explore prototypes of S4HANA. These prototypes showed great promise in S4HANA ability, meeting ONRR’s OFMS requirements.

Active prototyping and exploration since 2023. No true development.

Support to date by CACI Inc and DOI Business Integration Office (BIO)

RFI # DOIDFBO250003 ONRR IT Mod Integrator Support Page 10 of 26

To date (October 2024), ONRR has only partially implemented some of the recommended modules. The table below further outlines the status of each:

Functional Module Implementation Status as of October 2024

Item Module Description Partial Not Started

1 Customer Relationship Management

Organizes stakeholder contact and relationship information and tracks interactions with them x

2 Self-Service Portal Provides a digital interface for ONRR and its stakeholders to access and submit information x

3 Mission Inquiry Management

Funnels the majority of ONRR inquires to a centralized, tiered location for resolution x

4 Financial Management Facilitates the accounting, verification, disbursement, and reporting of mineral resource revenues

Prototypes in

FBMS/SAP

x

5 Case Management Organizes relevant information collected and streamlines workflows from initiation to resolution x

6 Data Management Supports all ONRR processes by providing a single consistent and accepted source for all data items x

7 Business Intelligence Enables reporting and analytics across ONRR data to generate meaningful business insights.

x

8 Risk Analytics Applies data science tools to quantitatively identify potential compliance cases.

x

Functional Module Status as of October 2024

2.6 IT Mod Goal Moving Forward

Application development (often called software development) is the process of developing software products that directly meet a need of the customer's business responsibilities/mission. The process can include a single mobile application, a stand-alone application/product, an Enterprise Resource Planning (ERP) system, and everything in between. While there isn’t a single set definition, most agree on the common best practice activities of requirements gathering, design, implementation, testing, and maintenance performed using methodologies/approaches such as Agile, Scrum, Waterfall, etc.

The objective of ONRR's future requirement will be to obtain IT Mod Integrator support for Application Development IT Services, that will include at a minimum:

Immediately take over and sustain the Operations and Maintenance (O&M) of partially implemented modules.

Complete Application Development and implementation of modernized solutions.

Maintain the implemented solution(s)

RFI # DOIDFBO250003 ONRR IT Mod Integrator Support Page 11 of 26

It shall be noted while ONRR believes it has selected and partially implemented best-in-class platforms that can sustain the full vision of modernization, it is open to further discussion and recommendations for best-value solutions (i.e.. not utilizing Connect/DASH current platforms, partially using the existing platforms, and or single ERPs) that could potentially lead to better holistic value to the ONRR mission and IT Modernization goals. ONRR seeks the knowledge share of industry partners' expertise and experiences in this RFI to help set the course of achieving Modernization visions.

RFI # DOIDFBO250003 ONRR IT Mod Integrator Support Page 12 of 26

3.0 Vendor ONRR IT Mod Integrator RFI Survey Response

Vendor ONRR IT Modernization & Replacement RFI Survey

• Please provide answers to all questions based on your proposed solution and any customization required to meet the specifics of this RFI.

• The response is limited to 45 pages with no smaller than 11-point font. However, you may use the Optional Capability Statement, Advice, and

Considerations (item 2 under section 1.5 Submission Instructions) to augment your response. This optional item is limited to 15 pages.

• If the information is not applicable to your company, indicate “X” in the “N/A” column.

• In a response that requires ONLY a Yes or No response, indicate an “X” in the appropriate column.

# RI # Requested Information (RI) N/A YES NO Vendor Response

GENERAL (G)

1 G1 Company name

Company name:

Company address Company address:

2 G2 Unique Entity Identifier (UEI)

3 G3

Name and contact information of the individual responsible for the information contained in this RFI response.

Name (First, Last):

Name (First, Last) Position Title Position Title:

Phone number. Phone number:

E-mail address. E-mail address:

Web site URL Web site URL:

4 G4 Company physical location (City and State) – i.e., where is the office located that would support this requirement.

5 G5

Which business categories do you fall under? Please select all that apply in the ‘yes’ or ‘no’ column.

1. Large Business

2. Small Business (SB)

3. Small Disadvantaged Business (SDB)

4. Section 8(a) Business

5. Woman-Owned Small Business (WOSB)

6. Economically Disadvantaged Woman-Owned Small Business (EDWOSB)

7. Historically Underutilized Business Zone (HUBZone) Small Business

8. Veteran-Owned Small Business

RFI # DOIDFBO250003 ONRR IT Mod Integrator Support Page 13 of 26

• Please provide answers to all questions based on your proposed solution and any customization required to meet the specifics of this RFI.

• The response is limited to 45 pages with no smaller than 11-point font. However, you may use the Optional Capability Statement, Advice, and

Considerations (item 2 under section 1.5 Submission Instructions) to augment your response. This optional item is limited to 15 pages.

• If the information is not applicable to your company, indicate “X” in the “N/A” column.

• In a response that requires ONLY a Yes or No response, indicate an “X” in the appropriate column.

# RI # Requested Information (RI) N/A YES NO Vendor Response

9. Service-Disabled Veteran-Owned Small Business

(SDVOSB)

10. Indian economic enterprise (IEE)

11. Indian Small Business Economic Enterprise (ISBEE)

6 G6

What Government-Wide Acquisition Contracts (GWACs) or General Services Administration (GSA) Federal Supply Schedule(s) (FSS) Multiple Award Schedules (MAS) do you currently hold that could support this requirement? Provide each overarching GWAC/GSA FSS contract number.

GWACS (List all that apply):

GSA MAS (List all that apply):

7 G7 Recommended period of performance for this type of requirement.

8 G8 Recommended type of contract vehicle for this type of requirement

9 G9 Recommended North American Industry Classification System (NAICS)

10 G10

The requirement is anticipated to be a commercial type acquisition.

“X” the applicable Block LH T&M FFP What is the recommended price arrangement for each of the following items. The choices are: LH, T&M, FFP.

• Discovery

• Discovery

• Development

• Postproduction Support • Development

• O&M • Postproduction Support

• O&M # Integrator Experience (IE)

11 IE.1

What is your experience with delivering similar federal modernization projects on time and within budget, and how do you mitigate risks related to project delays or cost overruns?

RFI # DOIDFBO250003 ONRR IT Mod Integrator Support Page 14 of 26

• Please provide answers to all questions based on your proposed solution and any customization required to meet the specifics of this RFI.

• The response is limited to 45 pages with no smaller than 11-point font. However, you may use the Optional Capability Statement, Advice, and

Considerations (item 2 under section 1.5 Submission Instructions) to augment your response. This optional item is limited to 15 pages.

• If the information is not applicable to your company, indicate “X” in the “N/A” column.

• In a response that requires ONLY a Yes or No response, indicate an “X” in the appropriate column.

# RI # Requested Information (RI) N/A YES NO Vendor Response

12 IE.2

What risk mitigation strategies do you typically employ when replacing legacy systems of similar scope & complexity to

ONRR MRMSS?

13 IE.3

Describe your preferred methodology (development and acquisition) for completing holistic modernized projects of similar scope and size.

14 IE.4 What metrics would you recommend utilizing for measuring the success of this effort?

15 IE.5

How do you ensure effective stakeholder engagement, communication, and alignment throughout a significant modernization effort like this?

16 IE.6

What is your strategy for managing data consistency, synchronization, and flow across multi-cloud platforms? Do you have experiences doing this with Salesforce, Snowflake, and financial platforms?

17 IE.7

How would you recommend integrating a new cloud-based financial system with both ONRRs Salesforce and Snowflake?

Can you provide a high-level architecture and concepts for this integration?

18 IE.8

How do you recommend balancing the need for customization and functionality with the desire to minimize development costs and avoid unnecessary complexity?

19 IE.9

What innovative tools or approaches do you bring to this project to ensure continuous optimization and improvement of the systems involved?

# Platform/Product Specific (PS)

RFI # DOIDFBO250003 ONRR IT Mod Integrator Support Page 15 of 26

• Please provide answers to all questions based on your proposed solution and any customization required to meet the specifics of this RFI.

• The response is limited to 45 pages with no smaller than 11-point font. However, you may use the Optional Capability Statement, Advice, and

Considerations (item 2 under section 1.5 Submission Instructions) to augment your response. This optional item is limited to 15 pages.

• If the information is not applicable to your company, indicate “X” in the “N/A” column.

• In a response that requires ONLY a Yes or No response, indicate an “X” in the appropriate column.

# RI # Requested Information (RI) N/A YES NO Vendor Response

20 PS.1

Do you have experience implementing Salesforce Platforms with similar scope/complexity of ONRR Connect in the federal sector? If yes please provide an overview of your experience to include:

1) Salesforce Product,

2) Proof of Principle,

3) Agency/Department,

4) System Description/Overview,

5) Alignment to ONRR Vision,

6) Total value: $

a) O&M Value

b) Development Value

21 PS.2

a) Do you have experience implementing Snowflake with similar scope/complexity of ONRR DASH in the federal sector?

b) If yes please provide an overview of your experience to include:

1) Snowflake Product,

2) Proof of Principle,

3) Agency/Department,

4) System Description/Overview,

5) Alignment to ONRR Vision,

6) Total value: $

a. O&M Value

b. Development Value

RFI # DOIDFBO250003 ONRR IT Mod Integrator Support Page 16 of 26

• Please provide answers to all questions based on your proposed solution and any customization required to meet the specifics of this RFI.

• The response is limited to 45 pages with no smaller than 11-point font. However, you may use the Optional Capability Statement, Advice, and

Considerations (item 2 under section 1.5 Submission Instructions) to augment your response. This optional item is limited to 15 pages.

• If the information is not applicable to your company, indicate “X” in the “N/A” column.

• In a response that requires ONLY a Yes or No response, indicate an “X” in the appropriate column.

# RI # Requested Information (RI) N/A YES NO Vendor Response

22 PS.3

What other Business Intelligence, Business Warehouse, Data Lake, and or Analytical platforms have you successfully implemented for a federal market that could deliver ONRR Connect/Modernization vision?

23 PS.4

If you successfully implemented a Business Intelligence, Business Warehouse, Data Lake, and or Analytical platforms project in a federal environment, was it reliant on data that is routinely ingested from external sources and organizations?

24 PS.5

a) Have you ever operated or developed in an environment (preferably federal) as a prime vendor where Snowflake and Salesforce were primary platforms and highly coupled to a Federal Financial System?

b) If so, please elaborate.

25 PS.6

a) Have you ever supported an Oracle Peoplesoft instance (development, conversion, or O&M) within the Federal Government?

b) If so, please elaborate.

26 PS.7

How would you approach immediate operations and maintenance for both ONRR Connect/Salesforce and ONRR DASH/Snowflake-PowerBI environments that are partially operational while ensuring continued progress and unity in IT Modernization development?

27 PS.8

Which financial systems have you successfully integrated, developed, or maintained with tight couplings to Salesforce and/or Snowflake in the federal sector?

RFI # DOIDFBO250003 ONRR IT Mod Integrator Support Page 17 of 26

• Please provide answers to all questions based on your proposed solution and any customization required to meet the specifics of this RFI.

• The response is limited to 45 pages with no smaller than 11-point font. However, you may use the Optional Capability Statement, Advice, and

Considerations (item 2 under section 1.5 Submission Instructions) to augment your response. This optional item is limited to 15 pages.

• If the information is not applicable to your company, indicate “X” in the “N/A” column.

• In a response that requires ONLY a Yes or No response, indicate an “X” in the appropriate column.

# RI # Requested Information (RI) N/A YES NO Vendor Response

28 PS.9

a) Considering ONRR’s vision to integrate Snowflake and Salesforce with the current and future financial systems, do you foresee any challenges with these platforms’ integration capabilities?

b) How would you address potential integration challenges with legacy systems or other third-party tools, and are there better platform choices that might offer smoother integration in the long term?

29 PS.10

a) From your perspective, how scalable and future-proof are Snowflake and Salesforce in meeting the evolving needs of

ONRR?

b) Do these platforms offer the flexibility needed for potential new functionality, user growth, or integration with other systems in the future?

c) If not, do you have a recommendation we should consider?

30 PS.11

a) Based on your understanding of ONRR’s BPR foundation, IT Mod progress in the platforms selected (Snowflake/PowerBI & Salesforce/MuleSoft), and future financial system desires, do you recommend continuing with these platforms for the remaining development, or would you suggest transitioning to different solutions (e.g., alternative platform(s), ERP, or something different)?

b) Please explain your reasoning, including any risks or benefits.

31 PS.12

a) Given your experience with both Snowflake and Salesforce, do you believe these platforms are the right fit for ONRR’s BPR Modules & IT Mod vision, particularly for the ONRR Connect and ONRR DASH components?

b) Why or why not?

RFI # DOIDFBO250003 ONRR IT Mod Integrator Support Page 18 of 26

• Please provide answers to all questions based on your proposed solution and any customization required to meet the specifics of this RFI.

• The response is limited to 45 pages with no smaller than 11-point font. However, you may use the Optional Capability Statement, Advice, and

Considerations (item 2 under section 1.5 Submission Instructions) to augment your response. This optional item is limited to 15 pages.

• If the information is not applicable to your company, indicate “X” in the “N/A” column.

• In a response that requires ONLY a Yes or No response, indicate an “X” in the appropriate column.

# RI # Requested Information (RI) N/A YES NO Vendor Response

c) Are there specific features or limitations of these platforms that could impact the successful completion of ONRR's efforts?

# Migration Research (MR)

32 MR.1

a) What criteria do you use to recommend a “best-in-class” cloud-based financial platform that integrates seamlessly with Salesforce and Snowflake?

b) Can you provide examples of platforms you have implemented in similar contexts?

33 MR.2

Based on your industry experience and all things considered in our current MRMSS and Modernization environment, what Financial Management Platforms should ONRR consider and why?

34 MR.3

What challenges have you encountered when deploying modern financial systems (i.e. Oracle Fusion, SAP S/4HANA, Momentum, Workday etc.) in a federal environment, and how did you overcome them to meet the needs of federal agencies (e.g., compliance, scalability, user adoption)?

35 MR.4

How do you approach the transition from an Oracle/Peoplesoft based financial system to a new financial system to minimize disruptions and ensure continuity of operations?

36 MR.5

a) Have you worked with financial management systems, particularly SAP S4HANA, Oracle Fusion, Momentum, or Workday, in the federal Government?

b) If so, please elaborate and indicate which one’s you have worked with and which ones you have not worked with.

RFI # DOIDFBO250003 ONRR IT Mod Integrator Support Page 19 of 26

• Please provide answers to all questions based on your proposed solution and any customization required to meet the specifics of this RFI.

• The response is limited to 45 pages with no smaller than 11-point font. However, you may use the Optional Capability Statement, Advice, and

Considerations (item 2 under section 1.5 Submission Instructions) to augment your response. This optional item is limited to 15 pages.

• If the information is not applicable to your company, indicate “X” in the “N/A” column.

• In a response that requires ONLY a Yes or No response, indicate an “X” in the appropriate column.

# RI # Requested Information (RI) N/A YES NO Vendor Response

37 MR.6

a) Do you have experience implementing Oracle Financial Products in the federal sector?

b) If so, which specific products?

c) If yes, please provide an overview of your experience to include –

1) The products implemented,

2) Period of performance,

3) Agency/Department,

4) System Description/Overview,

5) Alignment to ONRR Vision,

6) Total value: $

38 MR.7

a) Do you have experience implementing SAP Financial Management Products in the federal sector?

b) If so which specific products?

c) If yes, please provide an overview of your experience to include –

1) The products implemented,

2) Period of performance,

3) Agency/Department,

4) System Description/Overview,

5) Alignment to ONRR Vision,

6) Total value: $

RFI # DOIDFBO250003 ONRR IT Mod Integrator Support Page 20 of 26

• Please provide answers to all questions based on your proposed solution and any customization required to meet the specifics of this RFI.

• The response is limited to 45 pages with no smaller than 11-point font. However, you may use the Optional Capability Statement, Advice, and

Considerations (item 2 under section 1.5 Submission Instructions) to augment your response. This optional item is limited to 15 pages.

• If the information is not applicable to your company, indicate “X” in the “N/A” column.

• In a response that requires ONLY a Yes or No response, indicate an “X” in the appropriate column.

# RI # Requested Information (RI) N/A YES NO Vendor Response

39 MR.8

a) What other Financial Management (FM) products do you have experience implementing, developing, and maintaining in the federal sector?

b) Please provide an overview of your experience to include –

1) The Products implemented,

2) Period of performance,

3) Agency/Department,

4) System Description/Overview,

5) Alignment to ONRR Vision,

6) Total value: $

40 MR.9

a) Provide an overview of your experience as the prime contractor converting a federal partner off Peoplesoft onto another Financial product.

b) Provide project overviews - time, cost, desc, alignment to our requirement.

41 MR.10

Based on your industry experience and all things considered in our current MRMSS and Modernization environment, are there significant cost, or technical reasons ONRR should consider staying within its current production Oracle Ecosphere vs.

migrating off?

42 MR.11

How do you handle data migration from Oracle/Peoplesoft to the new financial system while ensuring minimal disruption and data integrity?

RFI # DOIDFBO250003 ONRR IT Mod Integrator Support Page 21 of 26

• Please provide answers to all questions based on your proposed solution and any customization required to meet the specifics of this RFI.

• The response is limited to 45 pages with no smaller than 11-point font. However, you may use the Optional Capability Statement, Advice, and

Considerations (item 2 under section 1.5 Submission Instructions) to augment your response. This optional item is limited to 15 pages.

• If the information is not applicable to your company, indicate “X” in the “N/A” column.

• In a response that requires ONLY a Yes or No response, indicate an “X” in the appropriate column.

# RI # Requested Information (RI) N/A YES NO Vendor Response

43 MR.12

a) Can you describe your experience in migrating clients from Oracle PeopleSoft to non-Oracle financial platforms?

b) What were the key challenges you faced, and how did you address them to ensure a successful migration? Please provide project specifics (Dates, Overviews, Cost and Schedule ranges, outcomes) where able.

44 MR.13

What is your approach to data migration from Oracle PeopleSoft to a new financial platform? Specifically, how do you ensure that data integrity is maintained, and that federal compliance standards (e.g., GAO standards, OMB) are adhered to throughout the migration process?

45 MR.14

a) How do you manage the risk of disruption when transitioning off Oracle PeopleSoft?

b) What steps do you take to ensure continuity of financial operations during the migration process and post-migration stabilization?

46 MR.15

What lessons learned from past PeopleSoft migrations would you apply to this project in terms of minimizing downtime, ensuring user adoption, and avoiding common pitfalls in the migration to a new financial system?

47 MR.16 How do you manage the training and adoption process for federal employees transitioning to new financial system?

# Estimates & Timelines (ET)

48 ET.1

What strategies do you employ to mitigate the risk of cost overruns or delays during the development of each platform, and how do you ensure that the project stays within the proposed budget and timeline?

RFI # DOIDFBO250003 ONRR IT Mod Integrator Support Page 22 of 26

• Please provide answers to all questions based on your proposed solution and any customization required to meet the specifics of this RFI.

• The response is limited to 45 pages with no smaller than 11-point font. However, you may use the Optional Capability Statement, Advice, and

Considerations (item 2 under section 1.5 Submission Instructions) to augment your response. This optional item is limited to 15 pages.

• If the information is not applicable to your company, indicate “X” in the “N/A” column.

• In a response that requires ONLY a Yes or No response, indicate an “X” in the appropriate column.

# RI # Requested Information (RI) N/A YES NO Vendor Response

49 ET.3

a) Can you provide examples of how you have optimized cloud costs in previous projects, particularly in environments that integrate multiple platforms like Salesforce, Snowflake, and a financial system?

b) Were data or transaction relays across multi-cloud / platform environments a concern?

50 ET.4

Based on your experience with similar IT modernization projects, can you provide a ballpark cost estimate for developing the Salesforce platform to meet the vision and requirements for the BPR (Business Process Reengineering) ONRR Connect product modules? Please break down costs for customization, integration, and any third-party tools or services required.

51 ET.4

Based on your experience with similar IT modernization projects, can you provide a ballpark cost estimate for the development of the Snowflake Power BI platform to meet the vision and requirements for the BPR (Business Process Reengineering) ONRR DASH product modules? Please break down costs for customization, integration, and any third-party tools or services required.

52 ET.5

a) Based on your experience with similar federal IT modernization projects, how cost-efficient do you think continuing with Snowflake and Salesforce will be for ONRR, both in terms of development and long-term maintenance (O&M)?

b) Would you recommend any alternative platforms that could offer better resource utilization, cost control, or faster time-to-value for the BPR modules?

RFI # DOIDFBO250003 ONRR IT Mod Integrator Support Page 23 of 26

• Please provide answers to all questions based on your proposed solution and any customization required to meet the specifics of this RFI.

• The response is limited to 45 pages with no smaller than 11-point font. However, you may use the Optional Capability Statement, Advice, and

Considerations (item 2 under section 1.5 Submission Instructions) to augment your response. This optional item is limited to 15 pages.

• If the information is not applicable to your company, indicate “X” in the “N/A” column.

• In a response that requires ONLY a Yes or No response, indicate an “X” in the appropriate column.

# RI # Requested Information (RI) N/A YES NO Vendor Response

53 ET.6

Based on your industry experience in federal financial system deployments, what are the estimated costs for implementing a new cloud-based financial system that integrates seamlessly with Salesforce and Snowflake, including licensing, development, data migration, and customization to meet BPR requirements?

54 ET.7

Based on your experience, what is the estimated timeline to fully develop and deploy the proposed ONRR Products and associated modules to meet the vision and BPR module requirements, from project initiation to go-live, noting that some are partially deployed?