WebVLIPS — Web Visual Logistics Information Processing System (Complete Reference)

WebVLIPS — the Web Visual Logistics Information Processing System — is the web-based query tool that lets a logistician see what happened to a logistics transaction after it entered the DoD supply pipeline. Operated by DLA Transaction Services, the Defense Logistics Agency activity that runs the Defense Automatic Addressing System (DAAS), WebVLIPS is an access-controlled application usable from any internet-attached PC. Where DAASINQ and eDAASINQ resolve the reference and routing data DAAS uses to move a transaction, WebVLIPS surfaces the status and history of the transaction itself — letting you track a requisition by document number, TCN, NSN, project code, or unit activity from its release into the pipeline until the materiel is posted to the accountable records at the destination activity. This page is the canonical reference for what WebVLIPS is, the LOTS database behind it, how it relates to the other DAAS tools, how to reach it, and how to use it.

At a glance

| Attribute | Value | | --- | --- | | Full name | Web Visual Logistics Information Processing System (WEBVLIPS) | | What it does | Web query tool for the status and history of logistics transactions (requisitions and excess) routed through DAAS | | Operator | DLA Transaction Services (Defense Logistics Agency) | | Data source | Logistics On-line Tracking System (LOTS), a DAAS relational database | | Search keys | Document number, unit activity, project code, TCN, NSN | | Access | CAC required; user ID and password requested through DLA Transaction Services | | Companion tools | DAASINQ / eDAASINQ (routing/reference data); WebFLIS (catalog data) | | Governing standards | DLM 4000.25 / DLM 4000.25-4 (DAAS); MILSTRIP status and document procedures |

What it is

WebVLIPS is a read-only tracking and inquiry application. It does not create, route, or modify transactions — that is the job of DAAS. Instead, it lets a logistician, supply technician, or transportation specialist answer one high-frequency question with authority: where is this document, and what has happened to it?

Given an identifier, WebVLIPS returns the assembled life cycle of a logistics action:

• By document number — the most common entry point; the document number uniquely identifies a requisition, and WebVLIPS returns its full transaction history and pipeline view.
• By TCN, NSN, project code, or unit activity — alternate keys for finding or grouping related transactions when you do not have the exact document number.

WebVLIPS presents what it finds through two complementary views. The History tab shows the underlying transaction data in legacy MILS format — even for transactions that were exchanged in the modern DLMS format, the display is normalized to MILS. The Pipeline tab provides a snapshot of milestones derived from that transaction data, giving a visual sense of where the document sits in its life cycle rather than the raw transaction stream.

To make those views meaningful, WebVLIPS integrates a range of reference data behind the transactions it shows — including DoDAAD (activity address) data, MILRI, source of supply, DoD project code, port code, transaction status code, unit of issue code, signal code, hold code, advice code, condition code, and mode code — so that the codes appearing on a tracked document can be interpreted in context.

Because WebVLIPS reads the DAAS-maintained LOTS database, it reflects the transactions DAAS actually routed for a document — which is what makes it trustworthy for answering "what happened" rather than "what should happen."

Why it exists

DoD logistics runs on a federated set of supply, maintenance, transportation, and finance systems that exchange standardized transactions constantly, and DAAS routes that traffic between them. But the act of routing a transaction is not the same as being able to see a transaction after the fact. A requisition that has left a customer's system disappears into a pipeline of status updates, shipment notices, and receipt confirmations spread across multiple systems and trading partners. Without a consolidated view, the customer cannot easily tell where the materiel is or why it has stalled.

WebVLIPS solves that visibility problem. Because DAAS sits in the middle of nearly all standard DoD logistics transaction traffic, it is uniquely positioned to assemble the scattered transactions for a single document into one tracked life cycle — which is exactly what the LOTS database does and what WebVLIPS presents. The value is transaction visibility and status research: confirming that a requisition was received and is being processed, finding the supply or shipment status that explains a delay, verifying that materiel was posted at the destination, or following a report of excess to its destination depot or disposal.

It is read-only by design. WebVLIPS exposes the routed transaction record for inspection; it does not let a user originate, change, or cancel the underlying transactions. Those actions happen in the requisitioning, shipping, and accountability systems of record; WebVLIPS lets you watch the result.

History and lineage

WebVLIPS inherits the long lineage of DAAS and of its own pre-web predecessor.

• VLIPS, the predecessor. Before the web interface, the capability existed as VLIPS — the Visual Logistics Information Processing System. The "Web" prefix on WEBVLIPS marks the modernization of that legacy capability into a browser-based application, the same modernization impulse that gave DAAS its other "Web"-prefixed tools (WebSDR, WEB REQ, WEBLOTS).

• DAAS, the system behind it. The Defense Automatic Addressing System is one of the longest-running pieces of DoD logistics infrastructure — the central message switch that edits, validates, addresses, and routes DoD logistics transactions. WebVLIPS is one of the family of web tools DAAS operators built to expose DAAS data to users over the web.

• The operator's name lineage. DAAS was historically run by the Defense Automatic Addressing System Center (DAASC), redesignated DLA Transaction Services in 2010 as part of DLA's consolidation of information operations. The tracking mission carried over intact across the renaming; the activity that routes the transactions also operates WebVLIPS.

The throughline matches the rest of the DAAS toolset: the tracking mission and the data are stable; the brand name, the front end, and the access URL are not. When a saved link fails, reach the current tool through the DLA Transaction Services site.

How it works

To use WebVLIPS well, it helps to understand the layers beneath it.

DAAS routes; LOTS records

DAAS receives, edits, validates, addresses, and routes the daily stream of MILSTRIP and DLMS logistics transactions between trading partners. As it does, the transactions for a given document — the requisition itself, the supply status, the shipment status, the receipt and confirmation transactions — are captured into the Logistics On-line Tracking System (LOTS), a DAAS relational database that portrays the life cycle of a logistics action. LOTS is the data; it stitches the scattered transactions for one document into a single trackable life cycle.

WebVLIPS is the window into LOTS

WebVLIPS sits on top of LOTS as the web query interface. (The same database is also reached through WEBLOTS; LOTS is the underlying system, WebVLIPS and WEBLOTS are access paths to it.) When you search by document number, TCN, NSN, project code, or unit activity, WebVLIPS reads the assembled life cycle from LOTS and presents it through its History and Pipeline tabs.

MILS display, and the DLMS limitation

WebVLIPS normalizes the display of transaction data to the legacy MILS format on the History tab, even when the original transaction was exchanged in DLMS. This keeps the presentation consistent and readable for users fluent in MILS document and status formats. The tradeoff is that WebVLIPS does not surface the additional data that only DLMS carries — for that richer DLMS-native detail, the Logistics Data Gateway (LDG) is the tool of record, not WebVLIPS.

There is no separate "WebVLIPS database" that drifts from DAAS — WebVLIPS reflects what LOTS captured from the routed transactions, which is what makes it a trustworthy record of what happened to a document.

Public vs authenticated access

WebVLIPS is an access-controlled application; it is not a public, no-login lookup. Access requires a Common Access Card (CAC), internet access, and a current web browser, and — beyond the CAC — a WebVLIPS user ID and password obtained through the DLA Transaction Services site. The transaction-status and history data WebVLIPS exposes is operational logistics data tied to specific documents and activities, which is consistent with it being gated rather than open.

There is no meaningful public tier to document: routine use assumes an authenticated user with provisioned WebVLIPS credentials.

How to get access

Access to WebVLIPS follows the standard DoD pattern for CAC-gated DAAS applications, plus an application-specific credential request:

1. Hold a valid CAC / PKI certificate. This is the baseline credential for DoD authenticated applications and is required for WebVLIPS.
2. Reach the DLA Transaction Services site. Navigate to the DLA Transaction Services / DAAS applications entry point (under dla.mil / transactionservices.dla.mil) rather than relying on a bookmarked legacy URL.
3. Request WebVLIPS login credentials. Use the site's request-login option to obtain a WebVLIPS user ID and password, selecting WebVLIPS as the application.
4. Authenticate with your CAC and the issued WebVLIPS credentials when prompted.

Common tasks

WebVLIPS supports a small set of high-frequency tracking 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 a requisition by document number

The most common task. You have a document number — from a requisition, a status report, or a customer inquiry — and you need to know where the requisition is and what has happened to it. The document-number search returns the assembled life cycle for that document; the History tab shows the transaction stream in MILS format and the Pipeline tab shows the milestone snapshot.

Finding a transaction without the document number

You do not have the exact document number but you do know the unit activity, project code, TCN, or NSN. Searching by one of those alternate keys returns the related set of transactions, from which you open the specific document of interest. This is how you locate a requisition when the customer gave you a TCN or an NSN rather than a document number.

Reading status and history to diagnose a delay

When a requisition appears stalled, WebVLIPS is the research instrument. Read the supply and shipment status transactions on the History tab, check the Pipeline milestones, and interpret the status, condition, advice, hold, and mode codes WebVLIPS surfaces. Those codes usually explain the holdup — a backorder, a rerouting, a hold, or a shipment in transit — which you then act on through the appropriate system of record.

Common gotchas

• An old WebVLIPS bookmark is your enemy. The DAAS and DLA Transaction Services entry points have moved across reorganizations and DoD hosting/cloud migrations. A saved direct URL is the single most common reason people think "WebVLIPS is down." Reach it through the current DLA Transaction Services site.
• WebVLIPS shows MILS, not the full DLMS picture. The History tab normalizes everything to legacy MILS format. If a transaction was exchanged in DLMS, the extra DLMS-only data is not shown here — use the Logistics Data Gateway when you need the DLMS-native detail.
• WebVLIPS is status, not routing. If your question is "where will this route" or "who owns this DoDAAC/RIC," that is a DAASINQ / eDAASINQ question, not a WebVLIPS one. WebVLIPS tells you what happened to a document; DAASINQ tells you the addressing behind where it goes.
• WebVLIPS is read-only. It is a window into the routed transaction record. You cannot correct, resubmit, or cancel a transaction from WebVLIPS — those actions go through the requisitioning, shipping, or accountability system of record.
• Know your search key. The document number is the precise key; the alternate keys (unit activity, project code, TCN, NSN) can return broad result sets. Pick the most specific key you have to avoid sifting through unrelated documents.
• Decode the codes. A WebVLIPS record is dense with MILSTRIP coding. Keep the relevant code references handy — for example the Supply Status Codes and Document Identifier Codes that appear throughout a tracked document.

When to use this vs alternatives

WebVLIPS is the right tool when your question is about the status or history of a specific transaction — "where is this requisition," "was it received," "why is it delayed," "where did this excess go." It is the wrong tool for several adjacent questions, which have their own systems:

• For routing and addressing reference data — who a DoDAAC belongs to, what activity a RIC identifies, where a transaction will route — use DAASINQ / eDAASINQ, not WebVLIPS. DAASINQ resolves the addressing data; WebVLIPS shows the routed result. This is the most important distinction to keep straight: DAASINQ is reference/routing data, WebVLIPS is transaction status/history.
• For an item's catalog and management data — NSN identification, source of supply on the record, unit of issue, management codes — use WebFLIS or PUB LOG / FedLog. WebFLIS identifies the item; WebVLIPS tracks a document that cites it.
• For the DLMS-native detail behind a transaction — the additional data WebVLIPS does not surface — use the Logistics Data Gateway.
• For excess and disposal processing actions (as opposed to tracking) — the DLA Disposition Services systems handle the disposal process itself; WebVLIPS lets you track the movement of excess toward a depot or disposal, but it does not perform the disposal action.
• To understand the document and status formats WebVLIPS displays, see the MILSTRIP formats reference; WebVLIPS shows these transactions, it does not define them.

In short: reach for WebVLIPS to see what happened to a document, and reach for the reference, catalog, and processing systems to look up data or take action.

Training and authoritative references

WebVLIPS itself is simple enough that most users learn it by tracking documents, but the transactions it displays and the system behind it are governed by formal standards. The authoritative source for the Defense Automatic Addressing System is DLM 4000.25-4 (Defense Automatic Addressing System), part of the DLM 4000.25 Defense Logistics Management Standards manual set that governs the MILSTRIP and DLMS transactions WebVLIPS shows — maintained by the Defense Logistics Management Standards Office. The DLA DAAS application overview describes the DAAS mission and its family of tools. The status, document-identifier, and related code families that appear on a tracked document are governed by the MILSTRIP procedures within DLM 4000.25 and are documented on logtool's dedicated reference pages. Links to the primary sources are in the references list on this page.

Last verified

This page is a draft prepared for subject-matter-expert review against live DLA Transaction Services sources. The factual core — WebVLIPS as the web query front end to the LOTS DAAS database, its search keys (document number, unit activity, project code, TCN, NSN), the History (MILS) and Pipeline tabs, CAC-gated access with a requested user ID/password, and its role tracking requisitions and excess through the pipeline — is corroborated across the DLA WebVLIPS application page (Article/2923173), the DLA Transaction Services site (transactionservices.dla.mil/daashome/webvlips.asp), the DLA WEBLOTS/LOTS page (Article/2935261), and Defense Logistics Management Standards Office training material. The 2026-06-21 source-verification pass confirmed: the credential-request workflow ("Request Login_ID and Password → WEBVLIPS"), the CAC/Internet-attached-PC framing, the MILS-display-of-DLMS behavior and the Logistics Data Gateway comparison, the LOTS-as-underlying-database relationship, and the DAASC → DLA Transaction Services redesignation (2010). Items that remain honestly downgraded — the exact current direct access URL behind CAC, the VLIPS predecessor history and transition date, the page-level WebVLIPS-vs-WEBLOTS functional distinction, and any WebVLIPS-specific DD2875/AMPS provisioning requirement — could not be confirmed from authoritative public sources (the primary DLA pages 403/refuse automated fetching) and are not asserted as sourced fact. Corrections and access-path updates can be submitted through the site's correction path.

Last verified: 2026-06-21.