RFI_26I4414_160426.pdf

DISTRIBUTION: DoD COMMUNITY ONLY

REQUEST FOR INFORMATION (RFI)

GCSS-MC Capability Support and Decommissioning Services

1.0 Introduction

Marine Corps Systems Command (MCSC), on behalf of the Portfolio Acquisition Executive Mission Systems (PAE MS) (formerly Program Executive Office for Manpower, Logistics, and Business Solutions (PEO MLB) is issuing this Request for Information (RFI) to conduct market research under Federal Acquisition Regulation Part 10 to identify sources with interest and capability to provide services for the capability support and decommissioning of the Global Combat Support System Marine Corps (GCSS-MC). GCSS-MC is an Oracle-based Enterprise Resource Planning (ERP) software system with significant Java form and HTML form customizations used to manage, track, and automate logistics, supply, and maintenance operations worldwide supporting over 25,000 users.

The scope of this RFI is strictly limited to the capability support of the current system and its decommissioning; no enhancements or modernization efforts are being considered under this RFI.

This RFI is issued for information and planning purposes only and does not constitute a Request for Proposal (RFP) or a promise to issue an RFP in the future. The Government is not seeking proposals at this time and will not accept unsolicited proposals. This request for information does not commit the Government to contract for any supply or service whatsoever. The information provided in the RFI is subject to change and is not binding on the Government. The 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.

2.0 Background

GCSS-MC is the Accountable Property System of Record (APSR) for enterprise-level logistics for the United States Marine Corps. GCSS-MC is built upon the Oracle E- Business Suite. GCSS-MC provides a single, integrated system for logistics and supply chain management, supporting every aspect of Marine Corps logistics, including supply, maintenance, and financial management. The system has 34 customized Java Forms and 12 HTML forms which must be maintained until decommissioning.

GCSS-MC is a critical enabler of operational readiness for Ground Combat Operations within the Marine Air-Ground Task Force (MAGTF). It provides near real-time visibility of assets and resources, enabling commanders to make informed decisions and ensure warfighters have the supplies and equipment necessary to accomplish their mission.

The system supports users in every clime and place and is integral to the daily operations of the Marine Corps' logistics community.

The Marine Corps is currently planning for the future of its logistics information systems.

However, the scope of this RFI is strictly limited to the capability support of GCSS-MC and its decommissioning; no enhancements or modernization efforts are being considered under this RFI.

3.0 Scope of Work

The Government is seeking information on industry's interest in providing services across multiple efforts: transition-in; capability support of the existing GCSS-MC system;

and its eventual, complete decommissioning. The decommissioning process is expected to be completed within the next two to four years.

3.1 Transition-In

During the Transition-In, the Government will provide the vendor with access to the systems, databases, repositories, and existing hardware facilities as required to execute transition to the vendor’s full support status of the GCSS-MC. This process will be managed by the Government. The Transition-In period shall begin upon award and continue until the Government deems the risk of full turnover to be minimal but is not expected to exceed six months. During the Transition-In period, the vendor shall acquire knowledge of and experience with the full scope of the capability support required of the GCSS-MC system and services, transition efforts, and processes sufficient to commence full performance of required services.

3.2 Capability Support Services

This effort involves all activities necessary to maintain the GCSS-MC system in its current state, ensuring operational availability, reliability, maintainability, and security.

GCSS-MC currently has over 25,000 users; 98.7% availability rate, with 99.9% reliability; and a 95% customer satisfaction rating. The anticipated threshold for Operational Availability is 95.0%, and reliability is 99.44%. GCSS-MC currently has an average of 288 Maintenance Change requests averaging 9 hours for change request (CR) implementation. This RFI does not include system enhancements or functional upgrades.

• System Maintenance: Troubleshoot and resolve issues with all layers (such as web services, application, database, operating system, hosting platform, etc.).

Interface Management, which includes maintaining the internal and external interfaces necessary for system operation and capability support. GCSS-MC Enterprise exchanges information via more than 36 interfaces across 20+ external parties in all GCSS-MC environments. The vendor shall design, build, test, and implement code, configuration, and other Government approved design changes/fixes into the GCSS-MC Production and Production Support System

(PSS).

• Help Desk and User Support: The Enterprise Service Desk (ESD) is the initial customer Point of Contact for worldwide GCSS-MC Enterprise user support. The ESD responds to a variety of requests via a shared Marine Corps IT Service Management (ITSM) Remedy Tool, including, but not limited to, user account and access support, functional issue support, transactional processing questions, report issues, requests for change, and other system service issues. On average, the ESD processes more than 60 REMEDY requests daily. Maintain an integrated ESD that supports Access, Event, Incident, and Problem Management.

• System Monitoring and Performance Management: Full responsibility for the operation and management of the GCSS-MC Operations Center (GOC). This responsibility includes the comprehensive execution of core ITSM processes such as Access, Event, Incident, and Problem Management, and all user community communications for GCSS-MC.

• Work with the Government to manage, schedule, and coordinate both planned and unplanned outages, and initiate user notifications with the Government in the event of planned emergency outages. The GOC shall coordinate with the Government to develop user notifications, including planned and unplanned outages and changes to the system’s functionality.

• Perform health checks and monitor system database integrity and usability utilizing established system database operating procedures. Monitor database performance; maintain database integrity; apply Configuration Management (CM) approved patches; and perform Government approved preventive and corrective actions to sustain system performance. The vendor shall review, coordinate, and manage the execution of automated Build Release patches, Patch Sets, Emergency patches, and Oracle quarterly CPUs/IA Vulnerability Alerts (IAVAs).

The vendor shall perform roll-back activities of Build Release patches in the event of an issue with a release.

• Cybersecurity and Information Assurance: Protect Marine Corps and GCSS-MC information from internal and external threats and attacks, while ensuring the confidentiality, integrity, and availability of information. Review, coordinate, and manage the GOC execution of CM approved Build Releases, patches, Patch Sets, Emergency patches, and Oracle quarterly Critical Patch Updates (CPUs)/IA Vulnerability Alerts (IAVAs). Support system record accuracy and completeness within EMASS and produce system accreditation documentation necessary to achieve and sustain full authorization.

3.3 Decommissioning Services

This effort would require the vendor to plan, execute, and complete the full decommissioning of the GCSS-MC system and a methodical approach to ensure a seamless transition for all stakeholders, the preservation of critical data, and secure disposition of all system components. The vendor will perform, in conjunction with the Government, the decommissioning in accordance with the Department of Navy Chief Information Officer Decommissioning Checklist.

• Decommission Planning - Develop a detailed Decommission Plan that outlines the steps, timelines, and responsibilities for decommissioning the system. This plan shall include procedures for archiving data, securely disposing of hardware, and documenting all shutdown activities.

• Data Management - Ensure all critical data from the legacy system are securely archived for future reference or compliance purposes. This includes identifying and prioritizing data for archiving, validating its integrity, and storing it in a secure and accessible format.

• Hardware Management - Ensure all hardware associated with the legacy system is securely disposed of or repurposed in accordance with applicable regulations and policies. This includes wiping sensitive data from devices, securely recycling or destroying hardware, and documenting disposal activities to prevent unauthorized access or data breaches.

• Documentation Management - Provide detailed documentation of all shutdown activities to ensure traceability and compliance. This includes creating records of archived data, hardware transition and disposal, and system decommissioning steps. The documentation must be comprehensive and submitted to the Government for approval, auditing and future reference.

• Stakeholder Communication - Ensure all stakeholders are informed of the shutdown process and its impact, maintaining clear communication throughout the decommissioning effort.

3.4 Attached Legacy Performance Work Statement (PWS)

• The attached PWS is provided to offer insight into the historical context of the program and should be considered for reference only. This document is not a draft PWS for a future requirement and is not binding on the Government. The Government is currently contemplating a successor effort that will be substantially narrower in scope, focusing exclusively on minimum essential sustainment activities required to transition the system to its end-of-life and subsequent decommissioning. Respondents should not base their RFI submissions on the attached PWS, but rather on their capabilities to provide streamlined, bare-bones sustainment and decommissioning support.

4. Information Requested from Respondents

To allow the Government to accurately assess industry interest relevant to this RFI, interested parties are requested to submit a response that includes the information detailed below:

Information Category

Description

Company Information

A brief overview of the company, including Company Name, Address, CAGE code, and Unique Entity Identity (UEI). State the business size under NAICS code 541512 (Computer Systems Design Services) and list any other relevant NAICS codes your company operates under. Include your company's socio-economic status.

Point of Contact Name of the company representative, their title, and contact information (phone and email).

Contract Vehicles

A list of any existing Government-wide contracts or other Federal Government contract vehicles your firm participates in (e.g., NASA SEWP, GSA Alliant, Federal Supply Schedules, etc.).

Past Performance

A list of Government contracts with past performance on similar projects with Oracle ERP and system decommissioning.

Capability Narrative

A narrative, including a technical approach, describing your company’s ability to meet the requirements outlined in Section 3.0, Scope of Work. Please address your experience with: a) Transition-In: Experience with similar system transitions. b) Capability Support: Expertise in maintaining Oracle-based ERP systems, managing enterprise help desks, and ensuring system availability and cybersecurity. c) Decommissioning Services:

Proven methodology for system decommissioning, data archiving, and hardware disposition in a government environment.

5. RFI Response Format and Submission

• Limit questions or comments to the information contained in Section 3. There is no limitation on the questions or comments. Participation is purely voluntary, and participation shall not be construed as a promise for future action or special consideration on any future procurements. However, the Government may use submitted responses to modify or clarify the information that may come out with a future solicitation. Similar questions may be paraphrased or combined with other submissions. Questions and comments shall be submitted in accordance with the format in table 1 below.

Table 1: Question and Comment Format Question # Company Name Page # Comment/Question

• Vendor questions and comments must be submitted no later than 12:00pm on

FRIDAY, 1 MAY 2026. Submit questions regarding this RFI to the points of contact listed below. Questions and comments should be prepared in either Microsoft Word (.docx) or Adobe PDF format. Any additional information or future industry engagements will be announced on SAM.gov as necessary.

• RFI Responses are limited to 20 pages to ensure consistency and a timely review.

• RFI responses are due no later than 5:00 PM EST on THURSDAY, 14 MAY 2026. Responses must be submitted electronically via email to the points of contact listed below. Telephone inquiries will not be accepted.

Contract Specialist Ms. Hannah

Thompson hannah.thompson@usmc.mil

Contracting Officer Ms. Allison Passanita allison.passanita@usmc.mil

• Email Limitations: Files sent by email must be limited to 2MB or less each.

Multiple files may be submitted; however, the total file size of a single email should not exceed 8MB. Emails larger than 8MB will not be received by the government email system. Files must not be submitted in a .ZIP file.

• Proprietary Information: All proprietary information and trade secrets must be clearly marked. All information received that is marked as proprietary will be handled accordingly. Submissions will not be returned. The Government shall not be held liable for any damages incurred if proprietary information is not properly identified.

Attachment:

1. Legacy GCSS-MC Post Deployment System Support (PDSS) Performance Work Statement (PWS) dated 15 AUG 2024 – M6785419D7614 mailto:hannah.thompson@usmc.mil mailto:allison.passanita@usmc.mil

4. Information Requested from Respondents