Interactive example · fictional data

The stock said yes. The reservation changed the answer.

Stock, reservations and transfers change what the operation can promise; dispatch, transit and receipt are separate facts.

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

Video

Transcript

[Illustrative example · fictional data] [“Do we have stock to fulfill this order?”] [Material M-01 · Site A] The team asks whether there is stock for an order.

[NebulaOS · Starya builds and connects within the scope of the operation · ERP and inventory · Replenishment forecast] [Illustrative interface · Features and integrations depend on the deployment.] On NebulaOS, connected by Starya within the scope of the operation, the flow relates ERP and inventory to the replenishment forecast.

[Site A: 18 physical · Replenishment delayed until day 4] [Flow · 12 free · Demand of 24 over three days] Site A has 18, and the replenishment is delayed. The stock said yes, but 6 are reserved: 12 free against a demand of 24.

[Site B: 40 physical] [Transfer authorized · Transfer request] [ERP and shipping · 28 physical] [12 in transit, still unavailable at A] The flow proposes transferring 12 from site B, and the person responsible authorizes it. With dispatch recorded, 12 are in transit, still unavailable at A.

[ERP and receiving · Receipt at A confirmed · 30 physical] [Fulfilling the customer order is the next operation.] Site A checks and confirms receipt. Fulfilling the customer order is the next operation.

[Which source distinguishes physical stock from available stock?] [Starya · We accelerate your AI strategy. NebulaOS is the operating foundation.] Which source distinguishes physical stock from available stock?

Talk about this situation

What confirms completion

The destination site confirms receipt in the ERP.

What NebulaOS supports in this scenario

In this scenario, NebulaOS relates the ERP and inventory, the replenishment forecast, the transfer request, shipping and receiving, connected within the scope of the operation, and keeps proposal, dispatch and receipt as separate facts. Which balances and movements can be read or recorded depends on the deployment.

NebulaWorks Brings together the work, owners, pending items and process artifacts.
Starya / FDE Compares expected demand, consumption and delays to review replenishment and record updates.

Try it yourself

Walk through the steps of this scenario and see what changes with each choice. Fictional data; no system is accessed.

Open the simulation

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.

01Analyze
02Propose
03Authorize
04In transit
05Receive

Site A

18

physical units · 6 reserved

12 free · expected demand: 24

Demand shortfall: 12.

Site B

40

physical units · 12 reserved

28 free · expected demand: 12

Batch B-02: valid throughout the horizon.

Site C

10

physical units · 4 reserved

6 free · expected demand: 6

No surplus within the horizon.

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

Site B12 proposed · no movementSite A

NOWA: 12 free

DAY 1Replenishment delayed

DAYS 1–3Demand at A: 24

DAY 4New forecast

Replenishment forecast

Transfer option

Data and batch condition

What we know now · v1

Transferring 12 from B to A meets the three-day projection; it depends on authorization, transit and expiry.

Example inputs, parameters and limits

Inputs

Fictional material M-01
Stock and reservations at three sites
Three-day demand
Batch B-02 and expected replenishment

Fictional parameters

A: 18 units, 6 reserved; demand 8/day
B: 40 units, 12 reserved; demand 4/day
C: 10 units, 4 reserved; demand 2/day
Proposed transfer: 12 units; transit time 1 day

Exploration history

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

Questions to take to your team

Systems and data Which source distinguishes physical stock from available stock?
Authority Who authorizes a transfer between sites?
Owner Who follows the transfer while it is in transit?
Result Which event confirms receipt at the destination?

Use these questions with the guide How to organize operational monitoring

Steps

Owner, system, state and pending item of the experience’s 5 steps, with decisions and limits

Step 1 · Analyze
Check availability
Physical stock is related to reservations and expected replenishment. The reservation changes what can be promised.
Owner
Planning
System
ERP and inventory
State
Availability checked
Pending
Physical stock alone is not enough to promise fulfillment.
Step 2 · Propose
Reassess the delay
A replenishment is delayed. The flow finds an alternative between sites and prepares a transfer.
Owner
Planning
System
Replenishment forecast
State
Alternative proposed
Pending
The proposal does not move stock.
Step 3 · Authorize
Authorize the transfer
The person responsible checks origin, destination and the conditions of the movement.
Owner
Inventory management
System
Transfer request
State
Transfer authorized
Pending
Dispatch still needs to be recorded.
Step 4 · In transit
Record dispatch
The origin site confirms shipment. The material moves to in transit.
Owner
Origin site
System
ERP and shipping
State
In transit
Pending
The destination cannot record receipt yet.
Step 5 · Receive
Confirm at the destination
The destination site checks the material and confirms receipt.
Owner
Destination site
System
ERP and receiving
State
Receipt confirmed
Pending
Fulfilling the customer order is the following operation.

Decisions to explore

Replenishment on time or delayed
Suitable or unsuitable batch
Transfer proposed, authorized, in transit or received

Pending items and limits

A transfer proposal does not reduce stock.
Dispatch does not automatically become receipt.
An item in transit is not available at the destination.

Text version

The main content, without depending on the video or the simulation.

Initial request “Do we have stock to fulfill this order?”

A delayed replenishment changes how an order can be fulfilled. The flow relates physical stock, reservations, expected demand and alternatives between sites. A transfer is proposed and authorized; dispatch and receipt happen at different times, and changing an assumption does not erase facts already recorded.

The team asks whether there is stock for an order. Physical stock exists, but part of it is reserved and the replenishment is delayed. The flow proposes a transfer between sites, which the person responsible authorizes. The origin records dispatch and the material is in transit; only when the destination site checks and confirms receipt is it available there. Fulfilling the customer order is the following operation.