Interactive example · fictional data

A delay changes the inventory network

Connect demand, reservations, batches and delivery dates to assess a transfer between sites.

Conceptual demonstration. It does not represent a customer case or prove available features.

Objective Assess a supply alternative and track dispatch and receipt separately.

Team Site A · Site B · Site C · Inventory and purchasing team

Explore the scenario. No action reaches a real system.

physical units · 6 reserved

12 available · expected demand: 24

Demand shortfall: 12.

physical units · 12 reserved

28 available · expected demand: 12

Batch B-02: valid throughout the horizon.

physical units · 4 reserved

6 available · expected demand: 6

No surplus within the horizon.

Purple: reserved. Teal: available stock. Future consumption is a projection; it has not been deducted from physical stock.

Site BNo transfer proposedSite A

NOWA: 12 available

DAY 1Expected delivery: +24

DAYS 1–3Demand at A: 24

DAY 4Review actuals

Expected delivery

Data and batch condition

What we know now · v1

Delivery expected tomorrow. The projection depends on this deadline; monitor receipt.

Example inputs, parameters and limits

Choices and handoffs will appear here, only in this session.

Brings together the work, owners, pending items and process artifacts.

Supports context, integrations and controls at the points defined by the deployment. Confirmation comes from the destination system.

Compare expected demand, consumption and delays to review replenishment and record updates.

Features, rules and integrations must be confirmed for each deployment.