Capabilities
What the Engine Can Actually Represent
The Methodology covers how you get from line data to a defensible decision. This page covers the thing underneath it: why ReliaSim models flow rather than individual items, the handful of node types a model is built from, and what that architecture buys you in speed and fidelity.
Pieces and parts, or rates and flow
Most simulation was built for discrete assembly, where every item is tracked as its own entity. Point that at a filler running hundreds of units a minute and the model becomes slower than the line it describes.
"For years, simulation has worked well in discreet industries like automotive, where each piece of material is treated as an entity. The models are based on item architecture, which is all about pieces and parts. But if you apply that to food production, the model will take longer to run than the actual product, which would make it useless."— Andrew J. Siprelle, founder, in Food Engineering
The answer was to model flow rather than items — a rate-based architecture suited to high-speed packaging and continuous process. It is why the sweeps on the Methodology page finish in seconds rather than overnight, and why a statistical answer is affordable at all.
What that buys is worth stating plainly. A thousand one-year runs of the five-machine bottling line finish here in about two and a half minutes on a laptop — measured at 0.154 seconds per simulated year. When we reproduced the same model in the tool the published validation used, it ran about 1200× slower — a wall-clock figure from our own validation test, not from the paper, which reports the model rather than its run time. At that rate one single one-year run takes roughly three minutes, and the same thousand runs would still be going two days later.
That is the whole argument. It is not that the answers are different — both tools model the same line. It is that one of them lets you ask a thousand questions before the meeting, and the other makes you pick three and defend the choice.
The nodes a model is built from
A production graph is assembled from three constructs. That is deliberately a short list — a small, opinionated vocabulary is easier to reason about, and it is what makes a model something you can read a year later.
Constraint
A unit operation with a rate limit and its own reliability. It runs at its nominal rate until something interrupts it, and it blocks or starves its neighbours when it cannot keep up.
On the bottling line: the capper and the labeler.
Converter
Changes the unit of flow. Material arrives measured one way and leaves measured another, with the conversion ratio held in equilibrium across the change.
On the bottling line: the filler turns liquid into filled bottles, the case packer turns bottles into cases, the palletizer turns cases into pallets.
Buffer
Accumulation between operations. A buffer decouples what is upstream from what is downstream, which is what stops one machine’s stop from immediately becoming everyone’s stop.
On the bottling line: bulk storage ahead of the fillers, and the warehouse after the palletizer.
Every constraint and converter carries its own interrupt signature — multiple failure modes per unit operation, each with its own time-to-failure and time-to-repair distribution. That is where the reliability data lands, and it is what makes blocking and starving emerge from the model rather than being assumed.
Where the interrupt numbers come from
Every interrupt needs a shape and its parameters. There are two ways to get them, and you do not need both.
Enter them directly
The Interrupt Designer ships with every license. Choose a distribution for time‑to‑failure and time‑to‑repair, set the parameters, and the unit operation carries them from that point on.
The route for a line that does not exist yet, or a failure mode nobody has clean history on.
Fit them from line event data
When you do have historian or event‑log data, fitting it is ReliaStats’ job: import the raw events, fit across all eight distribution types, and hand ReliaSim parameters it reads directly.
The difference between choosing a shape and measuring one.
ReliaStats is optional — helpful, not required. Nothing in ReliaSim depends on it, and a model parameterized by hand is still a valid model. It earns its place the moment you have event data worth fitting, because a measured interrupt signature is the thing that makes validation possible.
It runs two ways: as a desktop application in its own right, or as a feature inside ReliaSim — much the way a library extends ExtendSim rather than replacing it. Same fitting either way; the choice is whether you want it at your elbow while you model.
What that gets you
✓ Rate-Based Modeling
Discrete Rate Simulation has been trusted by top Fortune-listed companies for decades to simulate high-speed and large-volume bulk flow systems with extreme accuracy.
✓ Parsimonious Construction
A handful of simple, opinionated concepts makes it easier to think about your production process model. Build faster with fewer abstractions.
✓ Pre-Built Components
Modular, reusable constructs -- Constraints, Buffers, and Conveyors -- let you assemble production models rapidly with built-in rate control and accumulation behavior.
✓ Integrated Factory Physics
Nodes automatically simulate blocking and starving behavior based on the dynamics of the line through time. Dominant cause of failure is resolved during simulation.
✓ Reliability-Focused Design
Integrated reliability interrupts with multiple failure modes per unit operation drive high-fidelity behavior using competing, cumulative, and wall-clock criteria.
✓ No-Code Model Building
No drag-and-drop required. Models are built from text-based markdown and click-connect, so they diff and version like source code.
✓ Unit Conversions
Establish automatic equilibrium of flow for unit conversions at any stage in the process, and optionally represent in-line additions or losses.
✓ Model-Literal Animation
Automatically produced animation for every run executed. Playback and scrub controls let you review all nodes' states through time.
Your data never leaves your network. Models, historian extracts and results all stay inside your firewall; nothing but license and version checks crosses the internet. The full posture is on the security page.
Now see it on your line
The Sandbox runs eight ready-made bottling-line models in the browser — no download, no license — and is the fastest way to judge whether this architecture fits the way your plant actually behaves. If you would rather start from the method, the three-step sequence walks Build, Validate and Predict end to end.