ERP CS - RFI - FINAL.docx
DOCX document 23 KB Posted
- Attached to
- Request for Information for Enterprise Resource Planning Common Services (ERP CS) Software Federal contract opportunity
- Solicitation number
- ERPCS-FY25-0001
About this file
This Request for Information (RFI) from the Air Force Business and Enterprise Systems Division seeks market research for IT services supporting the Enterprise Resource Planning Common Services (ERP CS) software, with an anticipated contract value between $50M-$100M. The future firm-fixed-price contract will require developing, integrating, and sustaining capabilities within Oracle Cloud Infrastructure, including environment development, testing, cybersecurity, maintenance, and transition management.
The contract includes a 12-month base period (July 2025-July 2026) with two 12-month options and potential 6-month extension. Key objectives include obtaining Authority to Operate, developing scalable architecture, sustaining current DISA and ERP CS environments, migrating Air Force systems (AFIPPS, DEAMS, MRO), and expanding Splunk and ServiceNow functionality. Work will primarily be performed at contractor facilities with travel to Wright-Patterson AFB, Maxwell AFB-Gunter Annex, and Randolph AFB. The anticipated NAICS code is 518210 (Data Processing, Hosting, and Related Services). The RFI requests information about company qualifications, experience with DoD contracts, ERP implementations, and ability to meet timeline requirements.
View the file
On GovTribe
Work with this file on GovTribe
- Download the original file
- Contacts named in this file
- Similar government files
- Ask GovTribe AI about this file
Text version
Introduction The United States Air Force Business and Enterprise Systems Division seeks a partner to develop, innovate, integrate, upgrade and sustain current and future capabilities provided by the Enterprise Resource Planning Common Services (ERP CS) software. The ERP CS Program Management Office (PMO) establishes, develops, integrates and sustains common services and capabilities within the Oracle Cloud Infrastructure (OCI), provisioned by Cloud One. By providing a standardized and shared services model, the PMO enhances collaboration across stakeholders, to improve efficiency and effectiveness of business functions, and spearhead innovations and integrations across mission systems.
The ERP CS PMO has adopted the scaled agile framework for management purposes.
To respond to this RFI, submit answers to the questions starting on page 4 to the primary and secondary contacts listed on the SAM.gov posting.
Purpose The purpose of this contract is to provide information technology (IT) services to the ERP CS PMO, a branch of the United States Air Force Business and Enterprise Systems Division. The contract type will be a firm-fixed-price contract, and the contractor will be responsible for performing the work described in this Request for Information (RFI). The anticipated dollar amount for this effort will be between $50M and $100M. The purpose of this RFI is to perform market research to identify companies that can perform this work on the rigid timeline below as a follow-on to the existing ERP CS Contract.
Scope This work covers a comprehensive range of services aimed at ensuring the effective management, enhancement, and operation of the ERP CS environments. The Contractor shall provide IT services for a wide range of tasks, while adhering to Government-mandated standards and industry and Government best business practices in the disciplines of environment development, testing, integration, cybersecurity, maintenance and sustainment of ERP CS capabilities and services, and transition management.
· The Contractor shall proactively cooperate on topics related to common infrastructure services with ERP CS PMO, DISA, Cloud One and other stakeholders including OEMs such as Oracle and other companies providing products and support for ERP CS.
· The Contractor shall design, develop, deploy, document, implement, operate, and sustain ERP common services.
· The Contractor shall support, manage, and operate the continued performance of the assets deployed in the existing DISA environment and ERP CS environments.
· The Contractor shall provide sustainment activities to encompass service management, storage management & administration, database management, capacity management, backup and restore management, patching, disaster recovery, incident management, and troubleshooting.
· The Contractor shall provide continued operations and sustainment support for the capabilities and services. The contractor shall provide subject matter advice and leverage the Department of Defense (DoD) Enterprise Services Management Framework (DESMF).
· The contract scope shall, to the maximum extent practicable, encompass all IT disciplines to include new innovations and advances in technology, processes, and procedures within the context of the awarded contract.
· The Contractor must ensure that all tasks are aligned with the System Lifecycle and agile policies and executed in accordance with the Government’s agile strategy.
Objectives The objectives of this contract are:
· Obtaining and sustaining the Authority to Operate.
· Develop a scalable and resilient architecture aligned with business goals.
· The sustainment of current capabilities and services deployed in the DISA environment.
· The sustainment of current and future capabilities and services deployed in the ERP CS environment.
· The delivery of new capabilities and services to deploy in the ERP CS environment.
· The continuation and completion of migration of United States Air Force ERP mission systems into the ERP CS environment. Specifically, the Air Force Integrated Personnel and Pay System (AFIPPS),Defense Enterprise Accounting Management System (DEAMS), and Maintenance, Repair, and Overhaul (MRO).
· Increased reliability and quality of capabilities and services deployed in the ERP CS environment.
· The implementation of capabilities and services using the “as a Service” model.
· The expansion of Splunk dashboard development and usage.
· The expansion of ServiceNow usage to develop the asset management, knowledge management, license and software management and service desk functionality.
Contractor Responsibilities The Contractor shall provide cleared personnel capable of achieving program requirements within 30 days after contract award and for the duration of the contract.
The Contractor shall identify a Program Manager or a Project Manager who shall be the primary representative responsible for all work awarded under this task order and ensuring all standards referenced herein are adhered to.
The Contractor shall maintain a current listing of employees assigned to this project or task. The list shall include employee's name, EIDTR number, and level of security clearance. The list shall be validated and signed by the company Facility Security Officer (FSO) and provided to the contracting officer, Quality Assurance Evaluator (QAE/QAP), PEO BES and the 42nd SFS/SFAI prior to the contract start. Updated listings shall be provided when an employee's status or information changes.
The Contractor shall ensure identification items required for contract performance are obtained for Contractor personnel to include a Common Access Card and Contractor badge.
The Contractor shall ensure Contractor personnel are current with training, certifications, and investigations.
The Contractor shall provide annual security training to the Contractors personnel in compliance with government regulations and mandates.
The Contractor shall provide a status of training by Contractor personnel upon request to the ERP CS PMO.
The Contractor and Contractor personnel shall comply with local installation and facility procedures for entry to controlled or restricted areas when Contractor personnel work on government installations and facilities.
The Contractor and Contractor personnel shall provide all required forms and follow Government requirements and regulations when working on government installations and facilities.
Contractor personnel shall have a Contractor badge that displays the Contractor name, The Contractor personnel’s name, and a photo while in Government facilities.
Period of Performance The Period of Performance of this task order shall be for one (1) Base Year of 12 months and two (2) 12-month option years. The period of performance is detailed below:
| Period |
| Duration |
| Months |
| Base Period |
| 24 July 25 – 23 July 26 |
| 12 |
| Option Period 1 |
| 24 July 26 – 23 July 27 |
| 12 |
| Option Period 2 |
| 24 July 27 – 23 July 28 |
| 12 |
| Extension of Services* |
| 24 July 28 – 23 January 29 |
| 6 |
*Government requests this additional service period but does not intend to exercise this option except in extenuating circumstances.
Place of Performance The primary place of performance shall be at the Contractor's facility, with travel anticipated to Wright-Patterson Air Force Base (AFB), Ohio; Maxwell AFB-Gunter Annex, Alabama; Randolph AFB, Texas, and other locations as required.
Anticipated Acquisition Approach: To be determined Anticipated NAICS Code: 518210 - Data Processing, Hosting, and Related Services
Request for Information:
1) Please provide your Company Name and Address:
2) Please provide Point of Contact Information:
3) What is your company's UEI number?
4) What is your company's CAGE code?
5) Is your company a registered small business under SAM.gov?
6) If a solicitation were issued with requirements similar in scope to those listed in the “Program Description” section of the RFI, would your company bid on this effort or pursue subcontracting opportunities?
7) If your company were to bid, would your company subcontract any portion of the effort? If so, what percentage would be subcontracted?
8) Does your company have any experience acting as a prime contractor and managing one or more subcontractors on a Department of Defense (DoD) or other Government contract? If so, when, and what are the contract numbers?
9) Is your company a registered contractor under a Government Wide Acquisition Contract? If so, what are the contract numbers?
10) In the past five years, has your company worked closely with Government teams in the past on large scale efforts? If so, please describe the experience, articulate the roles among Government (ex. Product Owner, Engineering, Test, etc.) that you interfaced with, and how frequently these interactions took place?
11) Provide the following information for up to three Government Wide Acquisition Contracts on which your company performed as the prime contractor for similar efforts: Contract Vehicle, Contract, and Task Order Number.
12) On your largest ERP project, what percentage of software development involved customization (versus out of the box functionality)?
13) What was the maximum number of users on the largest ERP system of which your company performed similar work?
14) How long do you estimate it would take to be able to ramp up your company to be able to perform an effort such as this?
15) Provide any other information you think the Government should be aware of.
File details come from the government source that posted it. Updated .