DoD Logistics Software Systems Cannot Share Data Across Services

The U.S. Department of Defense operates over 500 logistics information systems across the four military services and defense agencies. The Army uses GCSS-Army (Global Combat Support System-Army). The Air Force uses DEAMS (Defense Enterprise Accounting and Management System) and others. The Navy uses Navy ERP. The Marine Corps has its own systems. These systems were developed independently over decades, use different data standards, different architectures, and in many cases cannot exchange information without manual intervention. A joint force commander trying to get a common logistics picture across all services in real time cannot do so. This matters because modern warfare is joint by design. No service fights alone. When the Air Force needs to know whether the Army has excess fuel at a forward base, or the Marine Corps needs to draw ammunition from a Navy ship, or TRANSCOM needs to track a shipment across service boundaries, the information must flow seamlessly. It does not. Logisticians resort to phone calls, emails, spreadsheets, and manual re-entry of data from one system to another. In peacetime, this friction causes inefficiency and waste. In wartime, it causes delays that cost lives. During exercises, joint logistics coordination consistently emerges as one of the most significant friction points. The consequence is that the Department of Defense cannot achieve true logistics visibility — the ability to see where everything is, what condition it is in, and when it will arrive. Without visibility, you cannot make good decisions. Commanders over-order supplies as a hedge against uncertainty, creating excess at some locations and shortages at others. Items are lost in transit because tracking breaks at service boundaries. The entire logistics enterprise operates with less information than a typical commercial supply chain, despite spending tens of billions of dollars on IT systems. This problem persists because each military service has its own acquisition authority, its own budget, and its own institutional culture around logistics. The Army, Navy, Air Force, and Marine Corps have each built systems optimized for their own service-specific workflows, and there is no authority short of the Secretary of Defense that can compel them to adopt a common system. Previous attempts at common logistics systems — like the failed Expeditionary Combat Support System (ECSS), which the Air Force cancelled in 2012 after spending $1 billion — have cratered spectacularly. Structurally, the defense IT acquisition process is fundamentally broken for enterprise-scale integration. Programs are managed as individual system acquisitions rather than as parts of an integrated architecture. Requirements are written by individual services, funded by individual services, and tested by individual services. The Joint Staff can mandate interoperability standards, but enforcement is weak and waivers are common. Each new system adds to the complexity rather than reducing it, and legacy systems cannot be retired because operational units depend on them. The result is an accretion of incompatible systems that resists integration at every level.