MABSM_Sustainment__Implementation_SAM_RFI_31Aug2026.pdf

REQUEST FOR INFORMATION (RFI) /

SOURCES SOUGHT

Maintenance and Business System Modernization (MABSM) Sustainment & Implementation Services

1.0 BACKGROUND & SYSTEM OVERVIEW

The MABSM application is a highly customized, mission-critical Commercial Off- The-Shelf (COTS) Enterprise Resource Planning (ERP) and Maintenance, Repair, and Overhaul (MRO) system. Originally built on a baseline commercial Impresa MRO/ERP software foundation, the system has undergone extensive, continuous customization over the past 24 years.

To date, the MABSM baseline includes over 242,000 custom code changes, program specifications, testing criteria, and complex interface logic. These modifications enable real-time communication with 17 legacy Department of Defense (DoD) systems. This highly specialized, proprietary configuration of the COTS software bears little structural resemblance to its commercial progenitor and operates as a unique hybrid system.

MABSM operates and is sustained within the Department of the Air Force's Cloud 1 enterprise cloud environment, leveraging DoD Impact Level 4/5 (IL4/IL5) secure cloud infrastructure. Sourcing specialized contractors who can operate seamlessly within Cloud 1's DevSecOps frameworks, managed services, and security boundaries is crucial to system stability.

MABSM dictates the real-time tracking of critical assets, including aircraft parts, financial transactions, and Nuclear Weapons-Related Material (NWRM) items. Due to the high-tempo depot environments in which it is deployed, the system requires a performance baseline exceeding 95% system uptime and near-zero code degradation. Furthermore, national security mandates dictate 100% real-time accountability of NWRM items within any given 24-hour period.

2.0 PURPOSE OF THIS RFI

The Government is performing market research to identify potential sources that possess the highly specialized technical capability, organic expertise, and experience required to assume, continue, and complete MABSM system implementation and sustainment efforts.

The scope of this potential effort includes:

• System Sustainment: Maintenance, helpdesk support, bug fixes, and continuous baseline support for existing MABSM deployments.

• Cloud 1 Environment Management: Managing, configuring, and optimizing MABSM infrastructure, virtual environments, and CI/CD pipelines hosted within the Air Force Cloud 1 environment, ensuring strict compliance with DoD cloud security mandates.

• System Implementation: Expanding and deploying MABSM to new depots and organizational units.

• Special Projects: Executing rapid-response technical integration, software modifications, and emergent data environment configurations to support evolving depot requirements.

• Transition Planning: Establishing structured, documented off-ramping and knowledge-transfer provisions to support future competitive actions.

The Government is interested in identifying all potential contracting vehicles and sources for this requirement under North American Industry Classification System (NAICS) code 541513 (Computer Facilities Management Services) or 541519 (Other Computer Related Services). The services required are considered commercial in nature.

3.0 CAPABILITY QUESTIONNAIRE

Interested parties are requested to submit a Capability Statement addressing the technical and administrative questions below. Please ensure your responses are supported by specific, verifiable corporate experience.

Please provide a cover sheet with the following information:

Company Information Company Name:

Designated Point of Contact:

Name:

Title:

Email:

Phone:

Mailing Address:

Business Type/Size:

CAGE code:

Unique Entity Identifier:

Facility Security Clearance:

1. Describe your organization's corporate experience in maintaining, modifying, and troubleshooting highly customized, proprietary configurations of Commercial Off-The-Shelf (COTS) ERP or industrial MRO systems (specifically Impresa ERP or functionally equivalent large-scale industrial platforms).

2. Detail your technical approach to executing software development, regression testing, and interface management within a code base containing over 242,000 custom changes that must communicate seamlessly in real-time with 17 distinct legacy DoD systems.

3. Explain your methodology for maintaining strict software quality standards (specifically targeting metrics such as code duplication under 12%, cyclicality under 3.3%, and 100% modularity) while maintaining a system uptime exceeding 95% in an active depot environment.

4. Describe your organization's direct experience managing, deploying, and optimizing enterprise systems hosted specifically within the Department of the Air Force's Cloud 1 enterprise cloud environment. Explain your familiarity with Cloud 1's system architecture, security onboarding processes, Authority to Operate (ATO) packages, impact levels (IL4/IL5), DevSecOps pipelines, and the utilization of cloud-native services in a DoD-managed environment.

5. Describe your experience managing, securing, and maintaining transactional integrity for systems tracking highly sensitive, strictly accountable national security assets, specifically Nuclear Weapons-Related Material (NWRM), under a mandatory 100% physical and digital accountability threshold within any 24-hour period.

6. Describe your organization's transition-in strategy to assume full operational command and development control of the MABSM baseline without causing degradation to active depot maintenance operations.

• Clearly describe how you will manage code and database administration transition with undivided technical accountability to prevent "split-code development" conflicts and safeguard the 24-hour, 100% NWRM accountability window.

• Clearly describe your estimated dependency on current contractor support.

7. Detail your approach to establishing a comprehensive, repeatable knowledge-transfer and off-ramping protocol during your performance. What artifacts, source-code documentation, and training structures will you develop to enable future competitive transitions of the system baseline?

8. Are the specialized software sustainment and implementation services described herein regularly offered to the commercial public or other federal agencies as a standard commercial service? Please provide examples of similar commercial contract structures.

9. The Government historically has a recurring, unpredictable requirement to execute "Special Projects" to address emergent technical needs, typically requiring rapid transition from requirement identification to contract execution within 30 to 60 days.

• Describe your organization's capability to execute rapid-response projects under this timeline.

• What pricing models (e.g., Firm-Fixed-Price, Time-and-Materials, or Labor- Hour) does your organization utilize commercially to execute such unpredictable, rapid-turnaround integration efforts?