"How much will this line actually make?"
A discrete-event simulator for serial and assembly lines. It propagates the variability a real line has: breakdowns, setups, scrap, blocking, starvation. So the answer is what the line will deliver, not what the cycle times promise.
In every run, with no special mode. The engine advances event by event, so how often you poll it cannot change the answer: a test sweeps that by 2,400× and demands bit-identical results.
There is also a suite of model invariants: series adds, parallel is the maximum, the operator limits, variability never creates capacity. A number can be right by accident. A law cannot.
The line itself. What gets in its way. The statistical discipline that keeps a run from being an anecdote. And the conversion into money.
the physical topology
why the line does not deliver what the arithmetic promises
a run is not an anecdote
a line decision becomes a financial one
The recording travels as events, not as frames. The browser rebuilds the line at any instant: 1× to 300×, pause, drag back. None of that touches the server. And before recording, the app tells you how many hours fit your connection.
There is also a flow view over a photo of your plant: your stations laid on the real drawing, with per-product markers, buffer queues and the live bottleneck. And the same run in 3D: the 2D diagram, a 3D view or both side by side on one clock, with the 3D layout saved with the line.
Chasing every feature of a general-purpose platform would make it complex and slow, and it still would not out-power the specialists. So some things are deliberately out.
A part choosing its own way through shared machines, or branching on a test result. RASQI follows a route you declare per product, and that is what keeps it simple. Coming back to the same station for each pass is a different thing, and it is supported — what stays out is a path that differs from piece to piece.
It does not move throughput, OEE or $/year. By Little's Law any work-conserving discipline gives the same. It changes lateness per order, which is scheduling, and that is a different job.
Sub-second cycles are accepted — the floor is one millisecond — and the reason to think twice is cost, not accuracy. The engine advances event by event, so a run costs what it costs because of how many pieces it makes: halving a cycle doubles the pieces per simulated hour, and doubles the run with them. Below a 5 s line cycle the advanced stochastic mode also turns its two stop tiers off, and says so. A whole batch per cycle is fully supported.
We model the material handling that drives flow: conveyor transit and parts moving in batches. Fleet dispatch and secondary constrained resources stay out.
Removed in August 2026, and we would rather say so than leave it implied. It cost up to 186 runs and only fitted a short horizon, which overstates the main lever by about 25%.
Every limit, with its reason, on the capabilities page. Is your line somewhere in between? Tell us about it and we will say honestly whether it fits as it is.
The simulator says so on its own screen. Its financial page is an engineering estimate for screening and prioritisation: no working capital, no financing, no sales taxes, no inflation, no FX, no ramp-up, no residual value. Before any commitment of funds, the business case must be reviewed and approved by your finance function.
One free month with the real software. If it does not find money, do not buy it.