Fast-Slow Drain · tank view
Same physical tank rendered three ways. Watch how each worldview's level updates as the simulation runs — smooth, stepped, or snapped.
Fast-Slow Drain · level over time
Discrete event is a staircase (one step per integer-% change). Discrete rate is piecewise-linear — just two anchors per fill-empty cycle (FULL and EMPTY). Pick a run length and watch the event-density strip below: continuous and discrete-event counts climb with the clock while discrete-rate tracks only the cycles.
Fast-Slow Drain · run it longer
DRS fires an event only when a rate changes — about twice per fill-empty cycle. So it doesn't matter how long you run: turn the knob and watch continuous and discrete-event counts explode while discrete-rate stays a sliver. DRS counts are real engine output; continuous / DES are illustrative comparisons.
Hamburger Duo · line view
5-stage line, two worldviews on the same clock. DES (top) tracks each burger; DRS (bottom) shows stage rates as bars. An Amber DRS bar = stage throttled by downstream backpressure.
Hamburger Duo · cumulative throughput
Same plant, same simulated clock, both worldviews. DES renders as a staircase (one step per burger arrival). DRS renders as a smooth diagonal (continuous flow). Both reach the same place at the same time — calibration holds.
Valdez Tanker · harbor view
Pipeline (flow) fills the tank; tankers (items) arrive, dock, and load. The flow-to-item transition is where pipeline oil becomes ship cargo.
Valdez Tanker · geographic view
The real Valdez Marine Terminal in Prince William Sound, Alaska. Watch the tanker traverse the canonical route — Marine Terminal → Valdez Narrows (the actual narrow bay) → past Bligh Reef → through Hinchinbrook Entrance to the Gulf of Alaska, then ~1,800 nautical miles south to Seattle (off-map).
Vegetable Plant · distribution view
Two Making lines feed five Packing lines through a bank of eight surge bins. A single DRS rate solver splits the flow across the bins and rebalances continuously — the layer Plant Builder adds on top of the three primitives. Bins and delivered totals below are engine-faithful; the motion is illustrative.
Vegetable Plant · campaign schedule
Plant Builder runs the plant as a sequence of campaigns, not one steady rate. Each bar is a real campaign (Excel-serial dates from the model), colored by product; the cursor sweeps the active window. Every campaign in this run hit 100% of its goal.
Chocolate Processing · DES↔DRS bridge
Three systems in series — Bean Processing → Cocoa Powder → Chocolate — run as a joint DES ↔ DRS model: DES schedules the campaigns and the equipment failures (discrete events); a DRS rate solver carries the continuous flow between them; the bridge couples the two. Attainment, downtime, and utilization below are engine-faithful; the motion is illustrative.
Chocolate Processing · campaign schedule
The same plant as a campaign schedule. Each bar is a real campaign (colored by product); the red portion is engine-reported equipment downtime within that campaign — the failures the DES side injects and the DRS flow has to absorb. The cursor sweeps the active window.
Bottling Line · where the losses really are
One line, six stations in series — a material supply feeding a Filler, Capper, Labeler, Case Packer and Palletizer. Each station is modeled down to its individual loss events — the LEDS level. Press play: stations drop offline at their real failure rates and starve everything downstream. Watch the Capper — it's offline nearly a third of the time. Anonymized generic line; per-station availability engine-faithful, downtime motion illustrative.
Tissue Line · a strategic decision
Three capital decisions for one line — bypass the converter, run it, or add a storage tower. Pick one and watch the throughput. The surprise: it barely moves — because the binding constraint is upstream, at the parent-reel supply. Anonymized; throughput as % of nameplate.