Skip to content
AGENTIC Data Mining
● Public TOOL dla.lead_time LAST SYNC —

DLA published administrative and production lead time

DLA's published administrative (ALT) and production (PLT) lead time in days, one row per NSN. Use it to judge whether a solicitation delivery schedule is feasible against DLA's own planning figure.

These are planning figures, not delivery dates. A published zero is a real value, not “unknown”. The source file has no date column — file_stamp is the time reference.

Source & conduct: Source: DLA FOIA lead-time bulk file. Owner browser download. Export-control and classification carve-outs at ingestion.

There is a portal for this: DIBIQ puts DLA award and item context in front of a bidder as pages rather than tool calls. Same subscription, same refusals.

Records

—

One unique NSN per row

Coverage

—

Populates from /api/dataset-coverage when a row exists

Scope

NSNs

FOIA Electronic Reading Room · export-control carve-out

Freshness

Monthly

Human drop + ingest · JSON · Public · included in subscription

Coverage figures populate from the ingestion pipeline after bin/refresh-coverage.py writes a dataset_coverage row for dla.lead_time.

Query parameters

nsnstring

National Stock Number, dashed or bare 13-digit -- both work. This table stores the BARE form; the tool matches either.

niinstring

National Item Identification Number, bare or dashed 9-digit.

fscstring

Federal Supply Class (4-digit), exact match. Export-controlled classes are withheld regardless of what is passed here.

max_total_daysinteger

Return only items whose ALT+PLT is at or below this many days. Use to find items whose published lead time fits a delivery schedule.

limitinteger

Max records to return (default 25, max 50)

offsetinteger

Rows to skip before the page starts (0-based, default 0).

The full input schema is served by the MCP server at connection time.

Example call

Request · dla.lead_time 
{
  "tool": "dla.lead_time",
  "params": {
    "nsn": "5340-01-000-0001",
    "limit": 10
  }
}

What you can ask

  • Is this solicitation's delivery schedule achievable against DLA ALT+PLT?
  • Filter items whose published total lead time fits a production window
  • Compare administrative vs production lead time when planning capacity
Full tool reference →

Schema

Fields from the live catalog entry for dla.lead_time. Sample values below are synthetic schema shapes — not live FOIA rows.

Field Type Description
nsn13stringNational Stock Number, BARE 13-digit — UNIQUE in this table, one row per item.
niinstringNational Item Identification Number, bare 9-digit (last 9 of nsn13).
fscstringFederal Supply Class, the first 4 digits of nsn13. Export-controlled classes are withheld.
alt_daysnumberAdministrative lead time in DAYS. A published 0 is DLA's own value, NOT 'unknown'.
plt_daysnumberProduction lead time in DAYS. A published 0 is DLA's own value, NOT 'unknown'.
file_stampdatePublication stamp of the monthly file, from the FILENAME. The file carries no date column of its own, so this is also the record timestamp.

Sample record

Sample · dla.lead_time · synthetic 
{
  "nsn13": "5340000000001",
  "niin": "000000001",
  "fsc": "5340",
  "alt_days": 90,
  "plt_days": 140,
  "file_stamp": "2026-08-17"
}

Illustrative synthetic record from catalog.json — identifiers are fabricated so a real FOIA row is never reproduced on this public page.

Use it for

  • Check whether a solicitation's delivery schedule is achievable against DLA's own lead-time figure
  • Filter items to those whose published lead time fits a production window
  • Compare administrative against production lead time when planning capacity

Related in Financial & Government Contracts