From Supply Visibility to Executable Availability

A visible unit may still be unavailable

A supply-network dashboard can show stock, orders, work centers, lanes, and estimated arrivals. It does not, by itself, answer the operating question: how many qualifying units can this network deliver against an accepted commitment, through a feasible production and transport path, before the cutoff?

The answer changes when a lot enters inspection hold, a supplier corrects its ready quantity, a line window contracts, a carrier revises an arrival, or an authorized commercial owner accepts a new commitment. Each local fact can be accurate while the combined conclusion is stale: inventory may be positive although releasable units or timely parts are short.

Official federal sources establish context for freight visibility, aggregate flow data, and manufacturing traceability. The separate Grid proposition is to represent inventory, production, transport, commitments, time, evidence, and authority in one bounded executable model. The sources do not establish its performance; only a controlled evaluation can test it.

What official sources establish—and what they do not

The U.S. Department of Transportation describes Freight Logistics Optimization Works as a public-private partnership intended to build a forward-looking, integrated view of U.S. supply-chain conditions. FLOW collects purchase-order information and logistics supply, demand, and throughput data from participants; USDOT anonymizes, regionally segments, and aggregates those data. Participants receive a broad daily view of overall network conditions beyond their own operations.

Its scope also marks a boundary. Aggregated regional conditions do not show whether a supplier lot passed inspection, a production slot remains authorized, or a customer revision was accepted. Treating FLOW as context rather than plant execution follows its published scope.

The Federal Highway Administration's Freight Analysis Framework provides another scale of visibility. Produced with the Bureau of Transportation Statistics, FAF integrates multiple sources to describe freight movement among states and major metropolitan areas across modes. FAF5 begins with the 2017 Commodity Flow Survey and Census international-trade data, and provides regional estimates of tonnage and value by origin, destination, commodity, and mode, plus scenarios through 2050. Those data inform network analysis; they do not promise that a named carrier, route, dock, or shipment is available at a decision time.

The Census Bureau says the Commodity Flow Survey is the primary source of national and state-level data on domestic freight shipments by American businesses. The 2022 survey sampled 165,000 establishments; selected establishments reported sampled or all shipments during a specified week in each quarter. Census describes noise infusion as a disclosure-avoidance method used for the published 2022 data, while its current CFS glossary says that, under Department Administrative Order 216-26, noise infusion will not be used for future statistical products after June 4, 2026. CFS supports statistical freight analysis, not a transactional inventory, production, or commitment feed.

Manufacturing adds a provenance problem. NIST Internal Report 8419, a final 2022 publication, observes that growing supply-chain complexity makes product origins harder to discern and examines exchanging traceability records through blockchain and related technologies. It supports provenance exchange, not the truth of a physical assertion, a required technology, or executable availability.

Together, these sources establish a layered context: broad freight conditions, regional flow estimates, protected shipment statistics, and cross-organization traceability are different information products. None replaces the operating evidence needed to commit a particular quantity by a particular time.

Availability is a conclusion across four changing records

For a bounded decision, executable availability can be stated as the quantity that passes every authored gate for a named commitment and time. At minimum, four records must resolve together.

Inventory must distinguish item and revision, site and bin, lot or serial identity where required, ownership, reservation, inspection state, usable quantity, unit of measure, observation time, and source. On-hand is not the same as unreserved, conforming, or releasable.

Production must connect bills of material, eligible substitutions, material consumption, work-center windows, setup or changeover, rate assumptions, expected or measured holds, quality release, and completion time. A schedule is represented capacity, not authority to run the line and not a prediction that output will conform.

Transport must connect origin, destination, equipment, capacity, cutoff, transit window, handoffs, route restrictions, and delivery evidence. A booking is not receipt. An estimated arrival is a source assertion with an observation time, not a guarantee.

Commitments must identify the authorized record, customer or destination, quantity, required configuration, due time, priority, acceptance state, and governing commercial or program constraints. A requested order and an accepted commitment are different facts. The model must not silently decide which customer wins when supply is scarce.

The conclusion needs a common clock and semantics. 80 can mean pieces, packs, kilograms, gross output, or released output. “Friday” can hide a time zone. “Available” can mean physically present, supplier-promised, production-planned, or deliverable. Joining labels without governing their meaning can distribute disagreement faster.

The Grid proposition, bounded

Grid proposes a reactive dependency graph. Configured connectors or controlled imports map named source revisions into typed records. Formulas and predicates calculate material balance, production limits, transport windows, and commitment coverage. A changed fact recalculates the affected path. Explanations show accepted, rejected, or unresolved inputs; different views can present the same revision to operations, logistics, commercial, quality, and decision owners.

That is a proposition for evaluation, not a claim about a live supply network. Grid does not integrate systems automatically, establish supplier truth, authorize production schedules, make procurement or contract decisions, or prove optimization or prediction accuracy. It does not claim deployment, regulatory or contractual compliance, cost savings, service levels, or business outcomes. It does not guarantee source availability, connector continuity, physical delivery, or the correctness of rules an organization has not supplied and validated.

The model calculates only within represented alternatives and constraints. A solver can return feasible, infeasible, or unresolved for that formulation; it cannot certify global optimality or discover unmodeled capacity. Releasing a lot, changing a schedule, tendering freight, accepting an order, issuing a purchase order, or communicating a promise remains behind authenticated controls.

Fictional exercise: Aster-4 modules

This fictional, deterministic exercise describes no customer, supplier, product, Grid deployment, or measured performance. Its purpose is to make the arithmetic and changed-fact path auditable.

A Tier 2 supplier provides sensor packs to a Tier 1 plant that assembles Aster-4 control modules. Each module requires one housing and two sensor packs. The Tier 1 plant holds finished inventory and ships accepted customer commitments through a confirmed outbound handoff. All times use the same declared time zone.

At revision R0, the accepted plant-handoff commitments are 60 modules for Customer North and 30 for Customer West for tender to the outbound carrier by Friday at 19:00: total demand is 60 + 30 = 90. The fixture does not represent transport after that handoff or customer receipt.

The plant's opening balance, measured before and explicitly excluding the morning batch, is 28 finished modules, of which four are on quality hold. Usable opening inventory is 28 - 4 = 24. The separate completed morning batch contains 48 modules, of which four are held under the exercise's fixed inspection fixture, leaving 48 - 4 = 44 releasable. Before the afternoon run, the available total is therefore 24 + 44 = 68.

For the afternoon run, the plant has 32 eligible housings. The Tier 2 source initially confirms 80 conforming sensor packs at the line-side receipt point at 13:00, before the 14:00 line window. In this fixture, that timestamp already includes inbound receiving and movement to line side; no additional inbound duration is hidden. At two packs per module, the record represents floor(80 / 2) = 40 possible starts. The line window is four hours at an authored eight completed modules per hour, or 4 × 8 = 32 completions by 18:00. The material-and-line limit is min(32 housings, 40 sensor-supported starts, 32 line slots) = 32. A fixed 30-minute inspection-and-staging step follows the final line block; the fixture holds two afternoon outputs, leaving 32 - 2 = 30 releasable by 18:30. The outbound handoff has 104 module positions and a 19:00 tender cutoff, so it does not bind. Revision R0 produces 24 + 44 + 30 = 98 executable units against 90 accepted units: a represented margin of eight.

Three authorized source changes then arrive.

First, the Tier 2 quality source corrects ready sensor packs from 80 to 56 after 24 fail inspection. Sensor-supported starts become floor(56 / 2) = 28. The afternoon limit becomes min(32, 28, 32) = 28; after the fixed two-unit hold, 26 are releasable. Total availability becomes 24 + 44 + 26 = 94, leaving a margin of four.

Second, the carrier revises completed line-side receipt from 13:00 to 15:00. The line window remains 14:00–18:00, so only three production hours remain: 3 × 8 = 24 completions by 18:00. The limit is now min(32 housings, 28 sensor-supported starts, 24 line slots) = 24; after the two-unit hold and fixed 30-minute inspection-and-staging step, 22 are releasable by 18:30 for the 19:00 handoff. Availability becomes 24 + 44 + 22 = 90, exactly covering the accepted 90.

Third, the authorized commercial owner records that Customer West's accepted commitment increased by 12. Accepted demand becomes 60 + 30 + 12 = 102. No supply fact changes. Executable availability remains 90, so the represented shortfall is 102 - 90 = 12.

Revision	Accepted change	Exact represented availability	Accepted demand	Margin or shortfall
R0	80 conforming sensor packs available at 13:00	24 + 44 + 30 = 98	90	Margin 8
R1	Sensor packs corrected from 80 to 56	24 + 44 + 26 = 94	90	Margin 4
R2	Line-side receipt corrected from 13:00 to 15:00	24 + 44 + 22 = 90	90	Margin 0
R3	Customer West accepted commitment rises from 30 to 42	24 + 44 + 22 = 90	102	Shortfall 12

The model should not hide that sequence behind a red indicator. A reviewer should trace the eight-unit margin, four-unit margin, zero margin, and 12-unit shortfall to exact source revisions and binding constraints. The model should not choose a customer allocation, expedite freight, reschedule production, or buy material. Those actions require appropriate people, policies, contracts, and authenticated systems.

Uncertainty, staleness, authority, and security

Every assertion needs observed_at, source, unit, identity, and a validity rule. Supplier quantity may expire at a shift boundary. A carrier ETA may be a range. A line rate may be an assumption, while a run count is measured. Conflicting claims should remain visible until a designated authority resolves them; “latest wins” is not a universal truth policy.

The model should distinguish known, stale, missing, contradicted, and not applicable. Unknown data should not become zero, and a stale commitment should not silently remain firm. Sensitivity runs can show what changes if an ETA moves or a hold grows, but those runs are scenarios, not predictions.

Authority stays with source and decision owners. Suppliers attest to records; quality releases material; production leaders authorize schedules; carriers and receivers provide movement evidence; commercial or contract roles accept commitments; procurement authorizes sourcing. Grid can expose a gate and retain an authored request-and-response evidence record when the configured integration returns one. That record is not a universal receipt contract, and Grid confers none of those authorities.

Security and integration are system properties. Each connection needs identity, access, data minimization, error handling, secrets management, logging, and recovery appropriate to its environment. Proprietary, export-controlled, personal, or regulated data may impose more rules. A signed package or traceable record can support integrity and provenance; it does not establish legal sufficiency, compliance, or authorization to exchange data.

A bounded evaluation with evidence, not promises

Start with one product family, two or three tiers, a declared bill of material, a small route set, one commitment horizon, and named authorities. Freeze a manual baseline using the same source files, timestamps, transformations, decisions, rekey steps, conflicts, elapsed time, and availability calculation. It is a comparison record, not a claim that the existing process is deficient.

Seed failures: a duplicated lot; mixed pieces and packs; stale inventory; a supplier correction; an inspection hold; reduced line time; a double-booked work center; late inbound arrival; an outbound cutoff breach; a commitment revision; an unauthorized priority change; a connector timeout; and conflicting quantities. Require refusal when a mandatory fact or authority is absent.

Measure bounded behavior:

• arithmetic agreement with a hand-verified oracle for every revision;
• correct feasible, infeasible, or unresolved status within the declared model;
• changed-fact propagation to every affected result and no unrelated result;
• detection of stale, missing, contradictory, duplicated, or unit-incompatible evidence;
• binding-constraint and rejection explanations that a reviewer can reproduce;
• correct refusal of unauthorized schedule, purchase, contract, allocation, or transport effects;
• connector-failure behavior, recovery behavior, and prevention of silent partial updates;
• elapsed time and manual touch count for baseline and modeled runs, reported descriptively rather than as promised improvement.

Preserve receipts for the fixture version, source revisions, mappings, units, timestamps, model and package hash, evaluated alternatives, formulas, solver status, explanations, user role, authorization decision, external acknowledgment where a test integration exists, errors, and run environment. A screen showing the final quantity is not enough.

Use an evidence ladder that prevents a successful exercise from becoming an operational claim:

1. Source-established context: an official publication supports a stated institutional fact.
2. Declared proposition: architecture and intended behavior are documented but not yet tested.
3. Fixture result: deterministic arithmetic passes controlled cases such as Aster-4.
4. Product demonstration: an inspectable Grid build passes declared tests in a nonproduction environment.
5. Customer-controlled result: the customer validates its data mappings, rules, security, authorities, and acceptance criteria.
6. Independently validated outcome: a qualified independent party evaluates a defined operational claim over a stated period.

This paper provides levels one and two; the fictional arithmetic is a proposed level-three fixture, not evidence that a Grid implementation passed it. Claims of savings, service levels, or business outcomes would require separately defined measures and higher evidence.

Teams can run the applied workflow in Turn Operational Signals into a Deliverable Commitment, carry the portable field guide into review, map one revision through From a Changed Fact to Coordinated Action, compare the inventory boundary in Inventory Is Not Availability, and define acceptance evidence with Evaluating Executable Decision Infrastructure and the decision evaluation worksheet. Grid Developers provides implementation-oriented guidance for explaining and validating a changing decision and canonical examples.

Visibility answers what the network reports. Executable availability is a time-bound, evidence-backed conclusion about what can satisfy an accepted commitment through represented, authorized constraints. Keeping those claims separate is the first control in making the model accountable.