GCSS-MC — Global Combat Support System (Marine Corps)

GCSS-MC (Global Combat Support System – Marine Corps) is the U.S. Marine Corps' enterprise system for ground logistics — the single application Marines use to requisition supplies, manage equipment maintenance, and track assets and logistics readiness, in garrison and deployed. It is a commercial-off-the-shelf Enterprise Resource Planning (ERP) system built on the Oracle E-Business Suite, fielded under the Marine Corps' Logistics Chain Management (LCM) modernization program and managed by Marine Corps Systems Command (MCSC). GCSS-MC was created to retire four aging, single-purpose legacy systems — SASSY, MIMMS, PC-MIMMS, and ATLASS — and to put supply and maintenance on one integrated system with near-real-time data. It is the Marine Corps member of the Department of Defense's joint Global Combat Support System (GCSS) family. This page is the canonical reference for what GCSS-MC is, the logistics business areas it runs, its acquisition history and phased fielding, the legacy systems it replaced, how it connects to DLA and the wider supply system, and how access works.

At a glance

• What it is: The Marine Corps' enterprise ERP for ground logistics — supply/requisitioning, maintenance management, and asset/readiness visibility — providing a single point of entry for logistics requests in garrison and deployed.
• Built on: Commercial-off-the-shelf Oracle E-Business Suite (originally Oracle 11i; upgraded to Release 12 in 2018). Not SAP — unlike GCSS-Army and Navy ERP.
• Program/modernization: Fielded under the Logistics Chain Management (LCM) modernization program; Increment 1 is the fielded capability.
• Managed by: Overseen by the Department of the Navy Program Executive Office for Manpower, Logistics and Business Solutions (PEO MLB), with program-management (manpower and technical) support from Marine Corps Systems Command (MCSC), Quantico, VA. (PEO MLB stood up in 2020, taking over the manpower/logistics/business portfolio of the former PEO EIS.)
• Replaced: SASSY (Supported Activities Supply System), MIMMS (Marine Corps Integrated Maintenance Management System), PC-MIMMS, and ATLASS (Asset Tracking Logistics and Supply System).
• Joint family: The Marine Corps member of the DoD GCSS family, alongside GCSS-Army (SAP) and GCSS-J (Joint).
• External routing: Requisitions to outside sources of supply route through the DAASINQ / eDAASINQ Defense Automatic Addressing System (DAAS) in MILSTRIP format.
• Access: Authenticated DoD system; CAC plus an approved, role-based account. Not public.

What it is

GCSS-MC is an integrated logistics ERP, not a single-function tool. "Enterprise resource planning" describes a class of commercial software that runs an organization's core processes — supply, maintenance, procurement, and related back-office functions — in one shared system so the processes connect instead of being copied between separate applications. GCSS-MC is the Marine Corps' implementation of that idea, built on the Oracle E-Business Suite.

Concretely, GCSS-MC gives a supported unit a single point of entry for logistics requests and transactions. A unit can order supplies, source and track those requisitions, and schedule and record equipment maintenance and repair — all on one system — and logistics leaders can see the availability, condition, and location of equipment in near real time. The defining feature is integration of supply and maintenance: the same maintenance action that requires a part and the requisition for that part are handled in one system rather than reconciled between two.

It is governed within Marine Corps logistics policy and the DoD's supply-chain materiel-management framework (DoD Manual 4140.01), and as a Department of the Navy business system it sits inside the DoD/DON business-systems acquisition and oversight structure — which is why much of its public documentation comes from oversight bodies such as DOT&E and from Department of the Navy acquisition pages rather than only from the program itself.

Why it exists

Before GCSS-MC, Marine Corps ground logistics ran on a set of separate, decades-old legacy systems — supply in one application, maintenance in another, asset tracking in a third — that could not share data well and could not give logistics leaders a timely, integrated picture of what units had, what was broken, and what was on order. Two of the principal legacy systems, SASSY and MIMMS, had been in service for roughly forty years, and their inability to provide real-time information was a primary driver for replacing them.

GCSS-MC exists to fix that with one integrated logistics system. Its goals are consistent across the program's documentation: integrate supply and maintenance so they are managed together; give logistics planners and operators accurate, near-real-time data in both garrison and deployed environments; provide enterprise-wide visibility of logistics data so commanders can make informed decisions at operational tempo; and improve logistics response and customer wait time while reducing the Marine Corps' dependence on large forward-positioned stockpiles of materiel. Retiring the four legacy systems was both a goal in its own right and the measure of success for the first increment.

For a working Marine logistician, the bottom line is simple: GCSS-MC is the system where the daily logistics work — ordering, sourcing, fixing, and accounting for equipment — actually happens.

History and lineage

GCSS-MC has a well-documented acquisition history, much of it captured in DoD oversight reporting because it was a Major Automated Information System.

• Milestone A and the Oracle selection (2004). The Marine Corps received a Milestone A decision for GCSS-MC Block 1 in July 2004, selecting a commercial-off-the-shelf ERP approach and Oracle as the software vendor (the Oracle 11i E-Business Suite). This set GCSS-MC apart from the SAP path the Army and Navy took.

• Milestone B, cost/schedule breach, and a change of integrator (2007–2010). A favorable Milestone B decision was reached in June 2007. The program subsequently breached its acquisition program baseline on cost (more than 25% lifecycle-cost growth) and schedule, and the original lead systems integrator (Accenture) was replaced, with Oracle Consulting taking over integration. The program restructured and pressed on toward fielding.

• Milestone C, IOT&E, and Increment 1 fielding (2010–2013). Milestone C for Increment 1 was approved in May 2010, and Release 1.1 reached initial operational capability in June 2010. Garrison functionality was phased in beginning with III Marine Expeditionary Force in Okinawa, Japan, which used the system in garrison from roughly 2010; its first forward/deployed use came in 2011 during the Operation Tomodachi disaster-relief operations in Japan (units including 1st Marine Aircraft Wing at Atsugi and 3rd Marine Logistics Group at Sendai). III MEF reached Full Operational Capability, initiating the directed sunset of the four legacy systems (MIMMS, SASSY, PC-MIMMS, ATLASS) — completed by December 2012 — with full rollout of Increment 1 completed in 2013.

• Sustainment and continued modernization (2010s–present). After fielding, GCSS-MC moved into post-deployment system support and sustainment, with the Oracle E-Business Suite operated, sustained, and enhanced under contract (Oracle Consulting historically, and a five-year support award to CACI announced in 2019). The Marine Corps has continued to upgrade GCSS-MC to improve performance and shorten the time from data to logistics decision, and the long-term LCM vision anticipates extending integrated functionality beyond supply and maintenance.

The throughline: the integrate-supply-and-maintenance, near-real-time, deployable mission has been constant since Milestone A; the integrator, the contract vehicle, and the Oracle version underneath have evolved.

How it works / is structured

GCSS-MC is best understood as one Oracle E-Business Suite ERP carrying the Marine Corps' ground-logistics business areas, with a CAC-enabled, role-based access model and interfaces out to the wider DoD supply system.

The business areas it runs

Across its public documentation, GCSS-MC covers these core logistics functions:

• Supply and requisitioning — ordering parts and materiel, sourcing requisitions, and tracking them through the supply chain (retail and, through interfaces, wholesale).
• Maintenance management — scheduling, recording, and managing equipment maintenance and repair, with the maintenance and supply sides connected on one system.
• Asset and readiness visibility — monitoring the availability, condition, and location of equipment, giving logistics leaders enterprise-wide, near-real-time visibility to inform readiness decisions.

The longer-term LCM vision describes extending integrated logistics-chain functionality more broadly across the logistics enterprise; Increment 1 delivers the core supply-and-maintenance capability.

The Oracle foundation

GCSS-MC is built on commercial-off-the-shelf Oracle E-Business Suite software — fielded originally on the Oracle 11i E-Business Suite and upgraded to Release 12 (in 2018) as the ERP core — configured for Marine Corps logistics processes. This is the key technical distinction from its sister systems: GCSS-Army and Navy ERP are SAP; GCSS-MC is Oracle. The system is described as an integrated composite ERP with the Oracle E-Business Suite product at its core, a customized, CAC-enabled authentication architecture with role-based authorization, and a reporting capability built on the Oracle Analytics Server.

Deployable by design

A defining requirement of GCSS-MC is that it support expeditionary, deployed logistics, not just garrison operations. It was built to give logistics planners and operators accurate, near-real-time data in deployed environments and to reduce reliance on large forward-positioned stocks — which is why its first major operational use cases were with deployed Marine Expeditionary Forces.

Integration with the wider supply system

GCSS-MC is not an island. When a requisition must be sourced from outside the Marine Corps — from a Defense Logistics Agency depot or another service's inventory control point — it is transmitted in standard MILSTRIP transaction format and routed through the Defense Automatic Addressing System (DAAS), operated by DLA Transaction Services. DAAS is the DoD routing backbone that lets GCSS-MC, Navy ERP, GCSS-Army, and the DLA supply systems interoperate — validating, editing, and routing requisitions to the correct source of supply, and returning supply- and shipment-status transactions back to the requesting system.

Public vs authenticated access

GCSS-MC is an authenticated DoD system, not a public website. There is no public, no-login interface to the system: it carries Marine Corps supply, maintenance, and readiness data and is reachable only by provisioned users on authorized networks, through a CAC-enabled portal with role-based authorization.

What is public is the documentation and program information about GCSS-MC — the Department of the Navy acquisition pages, DOT&E oversight reports, Marine Corps news releases, and installation logistics pages that describe what the system is and how it is run. This page aggregates that public information. To actually transact in GCSS-MC — order materiel, manage a maintenance action, pull readiness data — you need a CAC and an approved, role-based account.

How to get access

Access to GCSS-MC follows the standard pattern for a controlled DoD logistics system: a Common Access Card plus a role-based account approved through your command.

1. Confirm the requirement. With your supervisor or unit logistics/supply point of contact, establish that GCSS-MC access is required for your duties and identify the specific functional roles you need (supply ordering, maintenance management, reporting, administration, etc.).
2. Have a valid CAC. GCSS-MC is CAC-authenticated; ensure your Common Access Card and PKI certificates are current.
3. Submit the account/role request through your command. Route the request through the current GCSS-MC access process for your unit, specifying the roles tied to your job. Roles are granted under a role-based authorization model, so you receive exactly the access your duties require.
4. Complete required training and approvals. Finish any GCSS-MC role training and obtain the command and security approvals the process requires.
5. Log in and verify your roles. Once provisioned, log in with your CAC through the GCSS-MC portal and confirm you can perform the transactions your roles authorize. Report missing or excess access back through the request process.

The practical takeaway: there is no self-service signup. GCSS-MC access is provisioned by your command for the specific logistics job you perform, and the role set you receive is scoped to that job.

Common tasks

Because GCSS-MC is a full Oracle E-Business Suite ERP, the universe of in-system transactions is large and role-specific — supply, maintenance, and reporting users each work a different set of screens, and those screens are behind authentication and change across upgrades. Rather than document role-specific Oracle EBS transactions that this page cannot verify against the live system, the structured tasks on this page cover the two things a Marine most reliably needs around GCSS-MC: requesting access, and understanding how a requisition that leaves the Marine Corps gets sourced and routed. For in-system transaction procedures, rely on your unit's current GCSS-MC role training and the program's official guidance.

Common gotchas

• GCSS-MC is Oracle, not SAP. This is the single most common misconception, because its sibling systems GCSS-Army and Navy ERP are SAP. GCSS-MC runs on the Oracle E-Business Suite. If you are transferring knowledge from an SAP system, the concepts (requisitions, maintenance work, master data) carry over, but the screens and terminology do not.
• "GCSS-MC" is not one screen. It is a full ERP spanning supply, maintenance, and reporting. What a user can see and do depends entirely on their assigned roles — two Marines can both be "in GCSS-MC" and have completely different access.
• It replaced four systems, so old habits and old data live elsewhere. SASSY, MIMMS, PC-MIMMS, and ATLASS were sunset; historical records and the workflows people remember from those systems do not transfer one-for-one. Don't expect a legacy screen to have a direct GCSS-MC twin.
• External requisitions route through DAAS — you don't address them by hand. When a requirement is sourced outside the Marine Corps, GCSS-MC formats it as MILSTRIP and DAAS routes it. If a requisition is not reaching the right source of supply, the issue is usually in the catalog/source-of-supply data or the transaction, not in manual addressing. See DAASINQ / eDAASINQ.
• It is not the catalog. GCSS-MC requisitions and manages materiel; it does not define what an NSN means. For catalog identity, characteristics, and DoD-wide management data, use WebFLIS and PUB LOG.
• Garrison and deployed are the same system, different conditions. GCSS-MC is built to work deployed, but connectivity and data-refresh realities differ in the field. Know your unit's procedures for operating GCSS-MC in a deployed or degraded-communications environment.
• Portal URLs and access paths change. Like most DoD systems, GCSS-MC's portal and access paths shift across upgrades and hosting changes. Reach the current portal and request paths through your unit's logistics/IT shop rather than a saved link.

When to use this vs alternatives

GCSS-MC is the Marine Corps' ground-logistics backbone, but it is one system among several a Marine logistician touches. Use the guide below to keep them straight.

• Use GCSS-MC when you are doing the Marine Corps' day-to-day supply, requisitioning, maintenance, and readiness work for the operating forces — ordering and sourcing materiel, managing equipment maintenance, and tracking assets and readiness in garrison or deployed.
• Use WebFLIS or PUB LOG to identify an item — its NSN, characteristics, part-number cross-references, and DoD-wide management data — before you requisition it in GCSS-MC. The DLA catalog defines the item; GCSS-MC consumes that identity.
• Use DAASINQ / eDAASINQ to resolve the routing and addressing behind a requisition — DoDAAC and Routing Identifier Code lookups. GCSS-MC sends external requisitions through DAAS; DAASINQ is how you inspect that routing layer.
• Compare with Navy ERP for the broader Department of the Navy picture: Navy ERP is the SAP-based financial and enterprise-supply system of record for the Navy's systems commands, while GCSS-MC is the Oracle-based ground-logistics system for the Marine Corps. They are separate programs; both route external requisitions through DAAS.
• Use NAVSUP P-485 Online when you need the Naval Supply Procedures that govern Navy/Marine afloat and unit-level supply — the procedural layer, distinct from the GCSS-MC application.

In short: reach for GCSS-MC to execute Marine Corps ground logistics; reach for the DLA catalog systems to identify items; and reach for DAASINQ to inspect requisition routing.

Training and authoritative references

GCSS-MC training is delivered through the Marine Corps and the program as role-based training tied to the transactions a user is authorized to perform; it is not generally available as open public courseware, because the system itself is authenticated. For authoritative public information about the program, the best sources are the Department of the Navy acquisition pages — the Assistant Secretary of the Navy (RDA) GCSS-MC program page, the Program Executive Office for Manpower, Logistics and Business Solutions (PEO MLB), the overseeing PEO, and the Marine Corps Systems Command (MCSC) GCSS-MC program page (MCSC provides program-management support). The oversight record is also useful: the Director, Operational Test and Evaluation (DOT&E) annual assessments document GCSS-MC's increment structure, testing, and fielding. The materiel-management policy context is set in DoD Manual 4140.01, and the requisitioning procedures that govern how GCSS-MC transactions route are in MILSTRIP (DLM 4000.25-1), executed through DLA Transaction Services / DAAS. Links to each are in the references list on this page.

Interesting context

GCSS-MC is, in part, a story about catching up. The two legacy systems it replaced — SASSY for supply and MIMMS for maintenance — had served Marines for roughly four decades, long enough that a Marine could spend an entire career inside them. They were built for a batch-processing, periodic-reporting world, and their inability to give commanders real-time logistics information was a central reason the Marine Corps decided to replace them. GCSS-MC's pitch was the opposite of batch: a single system, accurate and near-real-time, that a Marine could reach from garrison or from a forward node.

The program's other distinguishing trait is its road not taken. When the services modernized logistics in the 2000s, the Army and the Navy went to SAP (GCSS-Army and Navy ERP). The Marine Corps went to Oracle — the Oracle E-Business Suite — making GCSS-MC the Oracle member of a family otherwise dominated by SAP. That choice has consequences a working logistician feels: skills and screens do not transfer cleanly between GCSS-MC and the SAP systems, even though the underlying logistics concepts are the same. Like most large DoD ERP efforts, GCSS-MC also had a hard birth — a cost-and-schedule breach, a change of systems integrator, and years of restructuring between its 2004 Milestone A and its early-2010s fielding — a reminder that even commercial, off-the-shelf software becomes a major undertaking when it has to run the logistics of an expeditionary force. And there is a fitting first chapter to its operational life: among GCSS-MC's earliest real-world uses was supporting Marine forces during disaster-relief operations in Japan in 2011, logistics under pressure being exactly the problem the system was built to solve.

Last verified

This page was last reviewed on 2026-06-21 and is a draft prepared for subject-matter-expert review against live Marine Corps / Department of the Navy sources. The program's structure, technology base, and Increment 1 history are corroborated across the Marine Corps Systems Command (MCSC) PEO program page, DON PEO MLB, DOT&E annual assessments, Marine Corps news and MARADMIN releases, DTIC/IDA studies (incl. IDA AD1122521), CRS reporting on the Nunn-McCurdy/cost breach, and industry contract reporting (Oracle, Accenture, CACI). Key source-verification outcomes from this review: (1) Corrected the overseeing program-executive office to DON PEO MLB (PEO EIS was disestablished in 2020; MCSC continues program-management support). (2) Confirmed GCSS-MC runs on the Oracle E-Business Suite, not SAP, and corrected the production version note to reflect the 2018 upgrade from EBS Release 11 to Release 12 (a later "Modern UI" EBS upgrade is publicized but the exact current point-release is not publicly confirmable). (3) Confirmed Milestone A (July 2004 / Oracle), Milestone B (June 2007), the post-MS-B >25% cost and schedule breach, the Accenture→Oracle integrator change, Milestone C (May 2010), IOC (June 2010), the Dec 2012 legacy-system sunset, and the 2013 Increment 1 full rollout; corrected the III MEF / Operation Tomodachi 2011 forward-use framing. (4) Confirmed CAC + role-based access (now via Naval Identity Services) as the basis for cac_required. Items deliberately not asserted (downgraded, not cleared): the current sustainment contractor after the ~2025 recompete, any fielded "Increment 2," the precise current EBS point-release, the deployed-connectivity mechanism, and the exact account-request route/portal URL. To suggest a correction, use the site's correction path.