USTRANSCOM IGC — IDE/GTN Convergence (In-Transit Visibility)

IGC — the Integrated Data Environment (IDE) / Global Transportation Network (GTN) Convergence — is the Department of Defense system of record for In-Transit Visibility (ITV). A joint program of United States Transportation Command (USTRANSCOM) and the Defense Logistics Agency (DLA), it fuses transportation and movement data from the military services, commercial carriers, DLA, and USTRANSCOM's components into a single authoritative view of where DoD cargo, passengers, and unit equipment are as they move through the Defense Transportation System. Where a catalog system like WebFLIS tells you what an item is and a routing tool like DAASINQ / eDAASINQ tells you how a transaction for it is addressed, IGC tells you where the materiel physically is once it is moving. This page is the canonical reference for what IGC is, the GTN and IDE systems it converged, how it works, how to reach it, and how it differs from the routing and catalog tools it is often confused with.

At a glance

What it is

IGC is a data-fusion and visibility platform. It does not move cargo, book transportation, or originate requisitions — it ingests movement and transportation data from many source systems and presents a single, authoritative picture of where DoD materiel and people are as they move. Its defining role is stated plainly in DoD descriptions of the system: IGC is the DoD system of record for in-transit visibility, enabling users to track the identity, status, and location of unit and non-unit cargo and passengers.

The platform fuses data from a wide set of feeders: the military services' transportation and movement systems, commercial carriers, DLA, USTRANSCOM, and USTRANSCOM's components. It also ingests automatic-identification data — notably Radio Frequency Identification (RFID) reads that report in-transit visibility events as shipments pass through transportation nodes. The point of pulling all of this together is to give logisticians, movement controllers, and planners one place to answer the question "where is it?" without querying a dozen unrelated systems.

Beyond pure in-transit tracking, IGC is described as serving asset visibility (AV) as well — a single place to access common data and business services about materiel asset visibility "whether in-storage or in-transit." That broader framing reflects the convergence goal: not just a transportation tracker, but a common, authoritative data environment for distribution and logistics information shared by USTRANSCOM and DLA.

Why it exists

DoD moves an enormous volume of cargo, equipment, and people through a federated transportation system run by multiple services, multiple commercial carriers, and multiple commands. Historically, the data about those movements lived in many separate transportation and supply systems that did not talk to each other, so no single user could see an end-to-end picture of where a shipment was. The cost of that blindness is not abstract — it is the difference between a commander knowing a unit's equipment will arrive on time and a commander reordering supplies that are already in the pipeline.

The requirement IGC (and GTN before it) exists to satisfy is in-transit visibility: a single, integrated view of the identity, status, and location of materiel and personnel in motion. The lesson that drove this into a formal DoD program came from the first Gulf War, where the lack of in-transit visibility produced one of the most-cited logistics failures in modern DoD history — thousands of containers arriving in theater whose contents were unknown, forcing units to open, inventory, and reship them. That experience made ITV a command priority and put USTRANSCOM in charge of providing a DoD-wide capability.

IGC carries that mission forward in converged form. By the mid-2000s, USTRANSCOM's GTN and DLA's IDE were tracking overlapping streams of distribution data, and the convergence program was launched to eliminate redundancy, streamline access to data, and optimize resources — merging two visibility platforms into one so that USTRANSCOM and DLA draw from a single authoritative source rather than maintaining parallel ones.

History and lineage

IGC is the latest layer on a visibility mission that goes back more than thirty years.

• Desert Shield / Desert Storm (1990–1991) — the catalyst. The Gulf War exposed a severe in-transit visibility gap: materiel poured into theater faster than anyone could track it, and a large share of containers had to be opened and inventoried because their contents were unknown. The episode is routinely described as the birthplace of the Global Transportation Network and the reason USTRANSCOM was tasked with a DoD-wide ITV system.

• Global Transportation Network (GTN) — operational late 1990s. USTRANSCOM built GTN as an automated command-and-control information system that collected data from the services' and DLA's transportation systems, integrated it into a single database, and provided in-transit visibility of personnel, materiel, and military forces. GTN integrated supply, cargo, passenger, and unit movements with airlift, air-refueling, and sealift schedules. It went through developmental and operational testing at Scott AFB in the mid-1990s and reached operational status in the late 1990s, with Lockheed Martin as the prime contractor.

• IDE — DLA's Integrated Data Environment. In parallel, DLA developed the Integrated Data Environment (IDE) as its data environment for distribution and asset information — the DLA-side counterpart whose visibility scope overlapped GTN's.

• IGC — the convergence (2008 onward). A joint USTRANSCOM/DLA program office was stood up to converge GTN and IDE into one platform. On June 30, 2008, Lockheed Martin was awarded the initial convergence contract, valued at $89 million (with future task orders), to build IDE/GTN Convergence (IGC) as "a common information platform" providing "a single repository and universal access to logistics data."

• A current, actively-sustained program. IGC remains in active operation and re-competition. In 2025, USTRANSCOM awarded an IGC task order — reported as a roughly $27 million award to D&G Support Services, LLC (award date February 28, 2025; selected over 13 other bidders) — confirming the system is current and being sustained, not retired.

The throughline mirrors the rest of DoD logistics infrastructure: the in-transit visibility mission is stable across decades; the system name, the prime contractor, and the access path are not. GTN became IGC; the requirement to know where DoD materiel is in motion never changed.

How it works

To use IGC well, it helps to understand the platform behind the screen.

A fusion of feeder systems

IGC is fundamentally an integration platform. It does not generate movement data itself — it collects that data from the many systems that do and fuses it into one view. The feeders include the services' transportation and movement systems, commercial carrier data, DLA distribution data, and USTRANSCOM-component systems. As materiel moves, in-transit events are reported into the platform — including automatic-identification reads such as RFID scans at transportation nodes — and IGC stitches those events into a coherent movement history for each shipment, passenger movement, or unit deployment.

What a visibility record shows

Against that fused data, a user can resolve the three things in-transit visibility is defined around: the identity of the cargo or passengers (what is moving), the status (where it is in the movement lifecycle), and the location (its current or last-reported position and the nodes it has cleared). This is the operational payoff of the convergence — a single query returns what previously required reconciling several unrelated transportation systems.

One authoritative source for two commands

The convergence design point is that USTRANSCOM and DLA draw from the same converged data rather than parallel platforms. IGC is described as the single source for HQ DLA and USTRANSCOM in-transit visibility across supply chain, distribution, and operations — which is what makes it the "system of record" rather than one of several competing visibility tools.

Public vs authenticated access

IGC is not a public website. It is an authenticated DoD logistics application that exposes operational movement data — cargo identities, locations, and statuses — which is sensitive in aggregate and is therefore gated behind DoD authentication and account provisioning. There is no general-public in-transit-visibility lookup; reaching IGC requires a DoD credential and an approved account.

This is by design. In-transit visibility data — where DoD forces and materiel are moving, and on what schedule — is operationally significant, so the platform follows the standard DoD posture for logistics applications: CAC/PKI authentication plus a provisioned, role-based account, with access scoped to what a given user's role requires.

How to get access

Access to IGC follows the standard DoD pattern for CAC-gated logistics applications, with the wrinkle that IGC is a joint USTRANSCOM/DLA system, so the precise provisioning path depends on which side of the house you fall under.

1. Hold a valid CAC / PKI certificate. This is the baseline credential for any authenticated DoD logistics application.
2. Request a provisioned account through the correct system. For DLA-hosted access, the path is a role request in DLA's Account Management and Provisioning System (AMPS) — the standard provisioning service for DLA web applications. USTRANSCOM-side users may follow a command-specific provisioning path.
3. Have the request approved by the designated approver/supervisor in the provisioning workflow, identifying your organization, role, and the visibility data you need.
4. Reach IGC through the current authorized entry point and authenticate with your CAC — not through a bookmarked legacy URL, which may have moved across the program's hosting changes.

If you only need to know what an item is (its NSN, characteristics, and management data) rather than where it is in transit, you do not need IGC at all — use WebFLIS or PUB LOG, which carry catalog data and require no operational ITV access.

Common tasks

IGC supports a small set of high-frequency visibility tasks. The canonical step-by-step workflows are presented on this page as structured HowTo procedures; the prose below frames when and why you would run each one.

Tracking an in-transit shipment

The core task. You have a movement identifier — a transportation control number, a document number, or another shipment reference — and you need to know where the materiel is and where it has been. The in-transit visibility query resolves the identity, status, and current/last-reported location of the shipment and shows the movement history (the nodes it has cleared). This is how a movement controller confirms a shipment is progressing, or how a receiving activity anticipates an arrival.

Watching a unit deployment or non-unit cargo stream

Beyond a single shipment, IGC was built to provide visibility of unit and non-unit cargo and passengers — meaning a planner can watch a unit's equipment and personnel move through the Defense Transportation System as a deployment unfolds, not just individual parcels. This is the combatant-command planning use case that justified the system in the first place.

Requesting and scoping access

Because IGC is gated, getting and right-sizing access is itself a recurring task — requesting the appropriate role through the provisioning workflow so that a user sees the visibility data their job requires without over-provisioning. The access workflow above is the canonical procedure.

Common gotchas

• IGC is not DAASINQ, and the confusion is common. IGC tracks where materiel physically is in transit; DAASINQ / eDAASINQ resolves the addressing and routing reference data (DoDAACs, Routing Identifier Codes) behind how a transaction is sent. If your question is "where is my shipment," that is IGC. If it is "what does this RIC point to" or "why did DAAS reroute this," that is DAASINQ.
• IGC is visibility, not movement or ordering. It does not book transportation, originate requisitions, or move cargo. It reports on movements that other systems execute. To order catalog items use FedMall; to identify items use WebFLIS; to submit and track requisitions use your component's requisitioning system and standard MILSTRIP processes.
• "GTN" references usually mean IGC now. Older documentation, training, and even system menus may still say "GTN." The in-transit visibility capability converged into IGC, so treat legacy GTN references as pointing at the IGC capability unless a source specifically distinguishes them.
• Visibility is only as good as the feeder data. IGC fuses data reported by many source systems and carriers. If an in-transit event was never reported into a feeder (a missed RFID read, a carrier that did not transmit), IGC cannot show it. A "no recent location" result is often a feeder-reporting gap, not a lost shipment — check the source system before assuming the worst.
• Don't rely on a saved URL. Like other DoD logistics applications, IGC's hosting and entry points have shifted across the program's life. Reach it through the current authorized USTRANSCOM/DLA entry point rather than a bookmark.
• Access is role-scoped. What you can see in IGC depends on the role you were provisioned. If expected data is missing, the cause may be your access scope rather than the data — confirm your role covers the visibility you need.

When to use this vs alternatives

IGC is the right tool when your question is about the physical movement and location of DoD materiel or personnel in transit. It is the wrong tool for the adjacent questions that have their own systems:

• To see where a shipment, unit, or passenger movement physically is — use IGC. This is its purpose as the DoD system of record for in-transit visibility.
• To resolve the routing/addressing reference data behind a transaction (DoDAAC, Routing Identifier Code, source-of-supply routing) — use DAASINQ / eDAASINQ. IGC tracks the movement; DAASINQ resolves how the transaction was addressed.
• To identify an item and read its catalog/management data (NSN, characteristics, source of supply, unit of issue) — use WebFLIS or PUB LOG. IGC shows where the item is; WebFLIS shows what it is.
• To order catalog items — use FedMall. IGC does not transact orders.
• To check requisition processing and status reporting — use your component's requisitioning system and standard MILSTRIP status, or DLA's WebVLIPS for logistics intelligence on requisition history and status. IGC reports physical movement, which is related to but distinct from requisition status.

In short: reach for IGC to answer "where is it as it moves," and reach for the routing, catalog, ordering, and requisition-status systems to address, identify, order, and track the paperwork behind it.

Training and authoritative references

The mechanics of an IGC query are learned in the application, but the mission and the policy behind it are governed by formal authority. USTRANSCOM is the DoD Distribution Process Owner and the lead for the in-transit visibility mission; its program descriptions and the Defense Transportation Regulation (DTR 4500.9-R) set the movement and transportation context IGC reports against. The convergence program and its current application entry are documented through DLA's Working-With-DLA Applications catalog and USTRANSCOM program material. The broader materiel-management policy that frames asset and in-transit visibility requirements is set in DoD Manual 4140.01. Access to DLA-hosted applications runs through DLA AMPS. Links to each are in the references list on this page; confirm the IGC-specific entry point and access path against the live DLA/USTRANSCOM sources, which are CAC-gated and not publicly fetchable.

Interesting context

In-transit visibility is one of the rare logistics capabilities with a clear origin story, and it is not a flattering one. The first Gulf War is remembered in the supply community as the war that buried the theater in unmarked containers — so much materiel arrived so fast, with so little visibility into what was inside, that units resorted to opening, inventorying, and reshipping a huge share of it just to find out what they had. The phrase "iron mountain" entered the logistics vocabulary to describe the heaps of supplies that accumulated because no one could see what was already in the pipeline. The Global Transportation Network was the institutional answer: give USTRANSCOM the job of building a single system that could tell a commander where everything was. IGC is the modern continuation of that answer.

The convergence itself tells a quieter story about how DoD logistics systems evolve. By the 2000s, USTRANSCOM's GTN and DLA's IDE had grown to track overlapping streams of the same distribution data from two different institutional vantage points — the transportation command's and the supply agency's. Rather than keep two platforms racing to describe the same reality, the two commands stood up a joint program to converge them, with a single contractor (Lockheed Martin, which had built GTN) tasked to fuse "information from myriad systems" into "a single data source." The "I-G-C" name is itself a small monument to that merger: the Integrated data environment, the Global transportation network, Converged. Underneath the renames and recompetes, the job has never changed — take everything that is moving, and let the people who need to know see where it is.

Last verified

This page is a draft prepared for subject-matter-expert review against live USTRANSCOM and DLA sources. A source-verification pass (2026-06-21) confirmed the core facts against authoritative public material: IGC as the DoD system of record for both in-transit visibility (ITV) and asset visibility (AV); the feeder set (services, commercial carriers, DLA, USTRANSCOM and its components, plus RF-ITV/RFID); the "single/sole source for HQ DLA and USTRANSCOM" framing; the 2008 Lockheed Martin $89M convergence contract (June 30, 2008) and the earlier 2006 program-office stand-up; the GTN "operational August 1997" date; the Gulf War "20,000 of 40,000 containers" catalyst narrative; the 17-position TCN under DTR 4500.9-R Part II, App L; and the 2025 IGC task order (~$27M, D&G Support Services, LLC). The remaining items genuinely unconfirmed against primary material — because dla.mil and the CAC-gated IGC application reject automated retrieval — are flagged inline and are: the exact current access path/entry point (CAC-only vs. CAC plus AMPS/SAAR, and whether provisioning is DLA-side, USTRANSCOM-side, or both), which drives the access_type value; the exact in-app query identifiers and visibility-record layout; and the precise IDE↔EBS architectural relationship. Corrections and access-path updates can be submitted through the site's correction path.