About this file

This document is a Sources Sought (SS)/Request for Information (RFI) for Maintenance, Repair, and Overhaul (MRO) and Maintenance, Repair, Overhaul and Supply (MRO-S) integration and implementation support. The Air Force Materiel Command (AFMC), Air Force Life Cycle Management Center (AFLCMC) is conducting market research to identify vendor interest and capabilities in these areas. This RFI is for planning purposes only and is not a solicitation. Interested parties must demonstrate experience with Oracle EBS platforms, agile methodologies, and cloud environments. Responses are due by 12:00 PM EDT on April 22, 2024. The anticipated period of performance is up to 5 years. The contract type and competition type have not yet been determined. The attached Statement of Objectives (SOO) provides additional details on the MRO and MRO-S requirements, which are intended to be similar in size and scope to the anticipated future solicitation.

View the file

Other files

File Type Posted
Industry Questions and Responses.pdf PDF
MRO Current State.pdf PDF
MRO and MRO-S RFI Rev 2.pdf PDF
MRO and MRO-S SOO.pdf PDF
MRO and MRO-S RFI.pdf PDF

On GovTribe

Work with this file

  • Download the original file
  • Contacts named in this file
  • Similar government files
  • Ask GovTribe AI about this file

Text version

SOURCES SOUGHT (SS)/ REQUEST FOR INFORMATION (RFI)

Maintenance, Repair, and Overhaul (MRO) and

Maintenance, Repair, Overhaul and Supply (MRO-S)

05 April 2024

1. SYNOPSIS

THIS IS A REQUEST FOR INFORMATION (RFI) ONLY. THERE IS NO SOLICITATION

AVAILABLE AT THIS TIME. REQUESTS FOR A SOLICITATION WILL NOT RECEIVE A

RESPONSE.

The Air Force Materiel Command (AFMC), Air Force Life Cycle Management Center (AFLCMC) Business and Enterprise Systems Directorate (BES) Enterprise Logistics Systems (GB4) Contracting Division (GBK), Wright-Patterson Air Force Base (WPAFB), Ohio is conducting market research seeking vendor interest for Maintenance, Repair, Overhaul and Supply integration and implementation support.

This RFI is for planning purposes only and shall not be considered as an invitation for bid, request for quotation, request for proposal (RFP), or as an obligation on the part of the Government to acquire any products or services. Your response to this RFI will be treated as information only. No entitlement to payment of direct or indirect costs or charges by the Government will arise as a result of contractor submission of responses to this announcement or the Government use of such information. This request does not constitute a solicitation for proposals or the authority to enter into negotiations to award a contract. No funds have been authorized, appropriated, or received for this effort.

The information provided is considered market research and may be used by the Air Force in developing its acquisition strategy, Statement of Objectives (SOO) or Performance Work Statement (PWS), and performance specifications. Interested parties are responsible for adequately marking proprietary or competition sensitive information contained in their response. The Government reserves the right to contact the submitting parties, on an as-required basis, for further clarification on material provided. The Government reserves the right to contact additional customers to obtain information that will be used to evaluate the offeror’s interest.

2. BACKGROUND AND DESCRIPTION

MRO provides a foundational baseline to satisfy complex depot maintenance requirements and positions the Air Force to expand Enterprise Resource Planning (ERP) capabilities across Logistics and other business domains as determined by future-state requirements. The integration and implementation of the wholesale and depot retail supply capability builds upon the current MRO baseline and will provide a holistic solution for integrated depot maintenance, Air Force Working Capital Fund (AFWCF) financials, and wholesale and depot retail supply. This supply effort will be referred to as MRO-S. The attached example SOO will assist interested vendors in understanding the full scope of the MRO and MRO-S requirements.

This SOO does not represent the exact requirements that will be provided with any future official RFP but is considered similar in size and scope to the anticipated requirement.

3. REQUIREMENTS OVERVIEW

The Government’s intent is for this requirement to operate under a phased approach between MRO and MRO-S. The initial phase is to begin MRO-S efforts utilizing MRO’s Oracle EBS solution as the baseline. MRO’s Oracle EBS platform has been selected as the USAF solution and shall be used for both MRO and MRO-S. A form of a test database or MRO clone Oracle EBS environment will be available for use as the baseline for initial MRO-S efforts towards a fully integrated product. Agile principles shall be used to develop, configure, integrate, and deploy MRO-S with a final product that is fully integrated, deployed, and operational within MRO’s Oracle EBS environment utilizing DevSecOps pipeline. MRO-S will mandate a data-driven approach, along with BPR, to ensure MRO-S satisfies applicable DoD and DAF policies.

The Government’s intent for the second phase is to continue with MRO-S integration and implementation while adding existing and ongoing design, development and implementation of MRO requirements, this transition will take place at a to-be-determined Most Viable Product (MVP) state and result in a fully integrated maintenance and supply ERP utilizing the Oracle EBS.

The USAF has selected Oracle EBS as the ERP solution, which provides application services, implementation services, operations support, training, sustainment, and workstream preparation activities. Program requirements are contained within an agile requirements hierarchy called the program backlog. The product allows the Government to manage the program by utilizing agile principles to develop, configure, integrate, and deploy the product. In this second phase, the Government will take a structured approach to identify an optimal time to ramp existing MRO efforts onto this contract effort. The second phase of ramping on MRO requirements may require continued MRO development of the Oracle EBS environment. This includes sustainment of the current MVP release, continued development, configuration, and deployment of future MVP releases through full deployment. This would be accomplished while simultaneously incorporating the MRO-S capability into the EBS platform.

4. PURPOSE

The purpose of this RFI is for the AFLCMC Enterprise Logistic Systems (GB4) Program Management Offices (PMOs) to gather information about industry interest and capability to provide integration and implementation support for MRO-S.

In responding to the Contractor Capability Statements detailed in Section 9., contractors must take into account all the experience and competencies as identified by the Government below:

Must have cloud experience.

Must have experience working with Oracle EBS platforms.

Must have experience following Agile development principles. Experience in DevSecOps pipeline preferred.

Experience and ability transitioning from an existing System Integrator (SI), if required, and continuing Agile development while utilizing the existing directed solution without impeding schedule or cost.

Must have Security+ Certificate or ability to obtain required certification.

Experience in performing automated testing.

Experience integrating Supply modules in an existing Oracle EBS environment that already has Maintenance modules active, including configurations and enhancements.

Experience sustaining Oracle EBS solutions including help desk support and implementation support at multiple locations.

Experience creating training materials across the software development lifecycle.

Ability to mitigate schedule and risks identified in the Contractor Capability Statements below (Section 9).

DoD experience preferred.

5. PREQUALIFICATION REQUIREMENTS FOR SCHEDULED ONE-ON-ONE Q&A

SESSION NLT 15 APR

AFLCMC/GB4 is leading an initiative in order to share information on the above Government requirement and obtain industry feedback during an open-forum, one-on-one session industry day for qualified companies. Only companies planning to submit a response as a prime contractor are permitted to request a one-on-one session. To qualify for a one-on-one session, a company must submit a response to the Government demonstrating they meet the following qualifications.

Companies that do not request a one-on-one are still required to respond to pre-qualification questions below in an RFI response

a) Adequately demonstrate your company’s experience working on Oracle EBS Platforms.

This is required to ensure interested parties are familiar with the USAF’s solution to include sustainment, development, and configuration of the Oracle EBS platform and minimize any potential delays and challenges in transition between SI’s. Please provide contract number, name of customer/organization supported, customer/organization POC including contact information.

b) Provide adequate evidence of your company’s successful experience as a system integrator

(SI) using agile methodologies and responsible for development, configuration, integration, testing, and deploying software solutions. This is required to demonstrate a company’s ability to successfully manage a program and software development utilizing agile methodologies. Please provide contract number, name of customer/organization supported, customer/organization POC including contact information.

c) Adequately demonstrate your company’s familiarity and capability of operating, managing delivery, tuning, optimization, and performance of workloads and Information Technology (IT) services that run on a cloud environment. This is required to meet USAF requirements as IT operations have shifted from on-premises to cloud-based infrastructure.

In order for a one-on-one meeting, companies must submit a written response to the above pre-qualifications, not to exceed three (3) pages (questions not included in page count), to Contracting Officer, Scott MacDonald at scott.macdonald.2@us.af.mil and Gene Eastman at gene.eastman.2@us.af.mil NLT 12:00 PM EDT 11 April 2024. One-on-One sessions will be scheduled NLT 15 April depending on availability on a first come, first served basis. Upon review of your submission, the Government will schedule a one-on-one meeting and work with that vendor to establish a suitable time.

Notifications of scheduled one-on-one times will be forwarded to the individuals listed in the requesting e-mails. Each company/team will be allotted up to one (1) hour for the one-on-one sessions. All meetings will be conducted on Microsoft Teams, and a calendar invite will be sent out.

Any initial questions must be submitted in advance and in writing with your prequalification submissions. Any follow-up or new questions during one-on-one sessions will be added to the list of questions. All questions received will be recorded. At the Government’s discretion and in order to clarify the Government’s intent for this acquisition, a written response to all questions (excluding questions regarding proprietary and contractor unique solutions) will be submitted to all those who qualified for one-on-one sessions.

6. PERIOD OF PERFORMANCE

The anticipated Period of Performance (PoP) will be up to five (5) years should a contract be awarded.

7. CONTRACT TYPE

The contract type has yet to be determined but will account for Agile methodologies. Contractors are encouraged to submit recommended contract strategies for Agile software development. (See Section 12)

8. COMPETITION TYPE

The competition type has not yet been determined. Based on the responses to this market research survey and other market research results, the Government will decide to utilize existing resources and capabilities, issue a Full and Open Competition (open to Large and Small Businesses), or a Small Business or Socio-economic Set-Aside, as deemed appropriate through market research.

Both large and small businesses are encouraged to participate in this market research.

9. CONTRACTOR CAPABILITY STATEMENTS

AFLCMC/GB4 is conducting an RFI to identify companies who are interested in providing development, integration, implementation, and sustainment support to the MRO and MRO-S system.

Technical:

T1. Demonstrate your different cloud experience.

T2. Demonstrate your experience with integrating Supply modules in an existing Oracle EBS environment that already has Maintenance modules active, including configurations and enhancements.

T3. Provide case studies or references where you have successfully integrated new modules into an existing Oracle EBS suite.

T4. Demonstrate your approach or experience to customizations within Oracle EBS to ensure seamless integration between Supply and Maintenance modules when you do not own the baseline for the Maintenance modules and the customizations cannot be fully provided.

T5. Demonstrate your approach or experience with Oracle EBS subledger accounting and the financial modules.

T6. Describe technical challenges you typically encounter when activating and configuring Supply modules in Oracle EBS, and how you overcome them.

T7. Demonstrate your team capability to perform automated testing on Oracle EBS platform.

T8. Describe your Agile methodology and implementation with specific examples.

Functional:

F1. Describe your approach or experience analyzing an existing Legacy System for integration and implementation into Oracle EBS.

F2. Describe your approach or experience mapping legacy Supply software functionalities to Oracle EBS Supply modules such as inventory management, order management, procurement, and supplier collaboration.

F3. Describe your approach or experience ensuring Oracle EBS Supply modules are configured to support both existing business processes and potential future state processes.

Schedule:

S1. Describe your approach or experience in phasing the implementation of Supply modules to the existing MRO sustainment and development effort to minimize disruption of on-ramping to the second phase of the requirement.

S2. Describe the technical, schedule, cost and any other challenges of transitioning from a current SI and your approach or experience in overcoming them. Provide a timeline that demonstrates your approach in overcoming these challenges.

S3. Provide a high-level project plan, indicating key milestones, from initial analysis to go-live and post-implementation support.

Business Process Reengineering (BPR) and Integration:

B1. Describe the methodologies you have or would employ for BPR when integrating new ERP modules and how you ensure that BPR leads to enhanced efficiency and effectiveness.

B2. Describe how you have or would ensure that the BPR aligns legacy systems with the new Oracle EBS Supply modules for a seamless integration.

B3. Describe the strategies you have or would use to document and reengineer existing business processes when integrating new ERP modules.

B4. Describe how you have or would maintain data integrity and continuity of operations during the BPR and ERP integration phases.

B5. Describe your approach to change management and user acceptance during the BPR process.

Data and System Integration:

D1. Describe how you have or would plan to migrate data from the legacy Supply system to the new Oracle EBS modules.

D2. Tools and techniques you have or would use to ensure that the integrated system provides accurate and real-time data across the Supply and Maintenance modules.

D3. Describe how you have or would approach testing the integration between the new Supply modules and existing Maintenance modules.

D4. Describe how you have or would ensure that the integrated Oracle EBS system will be scalable and adaptable to future business requirements and technological advancements.

Vendor Capability and Support:

V1. Describe existing support and maintenance services you have or would offer for post-implementation of the Oracle EBS Supply modules.

V2. Describe how you have or would ensure knowledge transfer to our internal IT team for ongoing system maintenance and enhancements.

V3. Describe your experience or anticipated strategy for providing continuous support, improvement, and updates to the Oracle EBS modules as our business evolves.

10. CLEARANCES

Contractor personnel shall be required to have and maintain the appropriate level of investigation and security clearance for the site at which they are located during the performance of duties. All contractor personnel are to have a completed favorable background check. The contractor personnel shall be required to obtain Common Access Cards (CACs) for the purpose of encryption and physical and digital identification for logical and physical access to Government information.

The contractor shall not involve any foreign nationals (resident aliens exempt) in work performed under this requirement.

11. ORGANIZATIONAL CONFLICT OF INTEREST

Organizational Conflict of Interest (OCI), as defined and discussed in FAR 9.5, Organizational and Consultant Conflicts of Interest, is a concern in all acquisitions across the Department of Defense. Early involvement with our industry partners is a key element of the OCI process, and it is critical for the Government to be able to identify any potential OCI issues as early as possible for an acquisition. This would allow ample time to address and evaluate any potential OCI issues, if required, prior to contract award with minimal impact to critical acquisition schedules.

Interested vendors are requested to evaluate your potential OCI issues with regard to this requirement for capability support services for MRO and MRO-S, and the contractor is encouraged to identify any OCI issues, as stated in FAR 9.5 to the Contracting Officer (CO). This will assist the CO in determining if the contractor will need to submit an OCI Mitigation Plan for any solicitation that might result from this notice.

12. SUBMISSION REQUIREMENTS

Interested sources are requested to submit a response to this RFI. Contractor's submittal shall be:

1. 20 pages or less (cover page is not included in page count)

2. Times New Roman 12 font

3. One (1) -inch margins

4. Page size should be 8.5 x 11 inches.

Contractors responding to this RFI shall include the following information:

1. Provide any questions or comments concerning MRO and MRO-S requirements described in the SOO for prequalification/one-on-one scheduled meetings NLT 12:00 PM EDT 11 April 2024.

2. Provide responses to the Contractor Capability Statements, Section 9 above.

3. Provide any recommendations and rationale for contract strategy, contract type, and contract vehicle(s) for providing MRO and MRO-S capability support requirements described in the

SOO.

4. Both large and small businesses are encouraged to participate in this Market Research.

5. Include Contractor Capability Survey information in your response.

CONTRACTOR CAPABILITY SURVEY

Please provide the following business information for your company/institution and for any teaming or joint venture partners.

Company/Institute Name CAGE Code Address Point of Contact Phone Number E-mail Address Web Page URL

Size of business pursuant to North American Industry Classification System (NAICS) Code:

541511: $34 Million

Based on the above NAICS Code, state whether your company is certified as:

Small Business (Yes / No) Small Disadvantaged Business (Yes / No) Woman Owned Small Business (Yes / No) Economically Disadvantaged Woman Owned Small Business (Yes / No) 8(a) Certified (Yes / No) HUBZone Certified (Yes / No) Veteran Owned Small Business (Yes / No) Service-Disabled Veteran Small Business (Yes / No)

Note: All interested contractors must be registered in SAM in order to be eligible for award of Government contracts. The Government reserves the right to consider a small business set-aside based upon responses hereto for any subsequent action.

A statement as to whether your company is domestically or foreign owned (if foreign, please indicate the country of ownership).

Please provide a statement that the respondent will allow or will not allow the Government to release proprietary data.

Due Date: Responses should be submitted electronically to the Contracting Officer, Mr. Scott MacDonald at scott.macdonald.2@us.af.mil and Mr. Gene Eastman at gene.eastman.2@us.af.mil by 12:00 PM EDT 22 April 2024. Late responses may not be reviewed.

13. SUBMISSIONS/QUESTIONS

If submitting company Proprietary Information or competition sensitive information, please make sure it is CLEARLY MARKED. To aid the Government, please segregate Proprietary Information to the maximum extent possible. All segregated proprietary information will be protected by the Government.

THIS IS AN RFI ONLY. The information provided in this RFI is subject to change and is not binding on the Government. The AF has not made a commitment to procure any of the items discussed, and release of this RFI should not be construed as such a commitment or as authorization to incur cost for which reimbursement would be required or sought. All submissions become Government property and will not be returned.

Any questions should be directed to the Contracting Officer as identified above.

Attachment 1: MRO and MRO-S Statement of Objectives (SOO)

1184487256C Highlight

File details come from the government source that posted it. Updated .