Truth modes

Know whether you are looking at live state, a snapshot or a simulation.

Ysend places warehouse geometry, inventory, people and equipment overlays in one spatial model, but every view keeps its data mode explicit. A saved plan and a simulated scenario never masquerade as current operations.

Review a twin use case

Three modes

Each view carries its own evidence contract

Live

Operational overlay

Current warehouse and equipment signals are shown with freshness and source context.

Saved

Layout snapshot

A versioned plan captures structure for review and structural comparison; it is not live telemetry.

Computed

Simulation

A scenario produces modeled outcomes from declared inputs and assumptions; it is not an observed result.

Live overlays

Live operations appear on the warehouse layout

Inventory and work

Locations, stock context, tasks and work areas share the same spatial references.

Mobile equipment

Robot positions, missions, alarms and keepout context appear with freshness labels.

Fixed equipment

Conveyor, cell, station and machine state is bound to the modeled facility.

RTLS and heat layers

Position and density overlays retain source, timestamp and scope instead of implying perfect coverage.

Snapshot diff

Compare plans without calling them live

Saved warehouse plans preserve structural intent for design review, including zone presentation and a structural diff between snapshots.

Capture

Save the layout and how it is displayed at a known point in time.

Compare

Review added, removed or changed structures between two saved plans.

Decide

Use the diff as design evidence; a separate approved change path updates operations.

Replay window

Reconstruct an exception from persisted events

  1. Select Choose a bounded event window

    The replay starts from persisted warehouse, mission and equipment records.

  2. Align Place sources on one timeline

    Work decisions, telemetry, interventions and outcomes keep source attribution.

  3. Explain Inspect divergence

    The review distinguishes missing data, stale state, controller refusal and warehouse exceptions.

Scenario lab

Change assumptions without changing the live warehouse

Scenarios can explore topology, work mix, resource policy and automation behavior before an approved operational change.

Input

A versioned topology, demand set, resource model and policy assumptions.

Run

A deterministic scenario or optimizer produces a candidate result with its configuration.

Compare

Candidate outcomes are compared with the declared baseline, never silently merged into live KPIs.

Promote

Any operational change follows its own review, authority and rollout path.

Calibration rule

Calibrate simulations to your warehouse

Mode labels stay visible

Use your layout, equipment speeds and handling constraints to compare scenarios. Saved demonstrations explain the interface; live warehouse decisions use current site data.

  • Snapshot mode is always identified as saved data.
  • Simulation assumptions remain inspectable.
  • Production decisions require site-specific input quality and approval.

Define the decision your twin must support

Bring the facility model, signal sources, required freshness, replay window and scenario assumptions. We will keep every truth mode explicit.

Review my twin scope