Section 4
Cross-System Comparison Matrix
Side-by-side comparison of every system covered in this paper.
| System | Service/Owner | COTS Platform | Primary Network | Current Status |
|---|---|---|---|---|
| GFEBS | Army | SAP ECC (β S/4HANA) | NIPR (+ SIPR-equiv. GFEBS-SA) | Mature / fully fielded |
| Navy ERP | Navy | SAP ECC | NIPR | Mature / fielded at SYSCOMs |
| DEAMS | Air Force / USTRANSCOM | Oracle EBS R12 | NIPR | Mature / fully fielded |
| DAI | Defense Agencies (DLA-hosted) | Oracle EBS R12 | NIPR | Mature / expanding (USMC onboarding) |
| STARS-FL/HCM | Navy | Legacy mainframe (DB2/CICS) | NIPR | Largely retired / residual |
| DLA EBS | DLA | SAP ECC + CRM/BW | NIPR | Operational / modernizing (WMS) |
| GCSS-Army | Army | SAP R/3 + NetWeaver | NIPR (tactical disconnect capable) | Mature / fully fielded |
| LMP | Army (AMC) | SAP ECC | NIPR | Mature / operational (AWCF GL) |
| GCSS-MC | Marine Corps | Oracle EBS | NIPR | Operational |
| SABRS | Marine Corps | Legacy (non-COTS) | NIPR | Active retirement β DAI |
| SOMARDS | Army | Legacy | NIPR | Retired ~2020β2021 |
| STANFINS | Army | Legacy | NIPR | Retired (pre-2015) |
| WAAS | DISA General Fund (WHS-owned) | Legacy (non-COTS) | NIPR | Active, acknowledged legacy limitations |
| FAMIS | DISA Working Capital Fund | Legacy (non-COTS) | NIPR | Active, being replaced by DAI-based βWCF Coreβ |
| DCSA (financial system) | DCSA | DAI (inferred, not directly sourced) | NIPR | Operational (accounting); NBIS feeder system badly delayed |
| DeCA (financial system) | DeCA | DAI (Re-Sale Accounting) | NIPR | Operational; DIBS/CARTS are the retail feeder layer |
| Combatant Commands (O&M) | Whichever Service is executive agent | GFEBS, DEAMS, or SABRS depending on COCOM | NIPR | No COCOM-owned system; rides on parent Service ERP |
Classified/SIPRNet and JWICS financial processing: unlike weapon-systems and intelligence data architectures, mainstream DoD general-fund financial accounting is predominantly an unclassified (NIPRNet) function, because most appropriated-fund transactions themselves are unclassified even when the underlying program is sensitive. The one clearly documented exception among the systems above is GFEBS-Sensitive Activities (GFEBS-SA), a fully separate, security-hardened instance for classified/sensitive-activity Army funding lines. Special Access Program (SAP-the-acronym-collision, i.e., Special Access Program) financial tracking and intelligence-community (IC) mission funding are handled through separate IC financial-management channels (outside the scope of the conventional-forces systems in this paper) and are not documented in open sources with the same level of system-architecture detail; where sensitive-activity funding must be tracked, DoD's approach has generally been a parallel hardened instance of the same COTS platform (as with GFEBS-SA) rather than a wholly distinct financial system.