Who wrote this. ChiAha makes ReliaSim, a discrete rate tool for production lines, and offers simulation consulting. This is the guide we would want as buyers, including where a different kind of tool fits better.
Does its method match your system?
Simulation software is built around a modeling method, and the method decides what the tool finds easy, what it finds slow, and what it can only approximate. Start here, before features.
When individual items matter
Each part, order or load is tracked as an entity. The natural fit for job shops, routed parts, assembly, material handling and warehouses, and queues where the identity of each item carries the answer.
When material moves as flow
Material moves at a rate and the engine only works when a rate changes. Created by Andrew Siprelle in 1990, originally as “bulk flow,” for high-speed filling, packaging, converting, bulk and continuous process lines.
When the question is behavior or policy
Agent-based models simulate many interacting decision-makers; system dynamics models aggregate stocks and flows with feedback. Useful for markets, adoption and long-horizon policy questions rather than machine-level detail.
The mismatch to watch for is a high-speed line in an item-based tool. When every unit is an event, run time grows with line speed, and a common workaround is to fold micro-stops into one downtime factor, which averages away the cascade effects that often dominate a fast line. The reverse holds too: if the answer depends on which job goes to which machine, a good discrete event package is the right choice and a rate-based tool is not. For a longer comparison of the methods, see simulation methodologies compared.
- Show me a model of a system like mine, at our real line speed, not a teaching example.
- Which parts of my system does your method represent natively, and which by workaround?
- How are short stops and blocking and starving represented: explicitly, or averaged?
Can the vendor show validation against measured data?
Most accuracy claims are a vendor’s word. Ask instead for a model that was compared against a real plant’s measured history, and ask how the comparison was done. A single aggregate figure can match for the wrong reasons, with one failure mode overstated and another understated until the errors cancel. Comparison failure mode by failure mode cannot hide that.
A useful bar: within 1% of measured OEE. That is achievable for a line model when the model and the data are handled correctly, with data kept per failure mode, distributions fitted properly, and the model checked against the plant’s own history before it predicts. It is not something any tool delivers on its own, which is exactly why it makes a good question.
A published example shows what that evidence looks like. At the 2020 Winter Simulation Conference, Lawrence Fischel and Tom Lange reported a discrete rate and reliability model of a multi-line food plant, built in ExtendSim, with more than twenty unit operations and up to twenty failure modes on each. That model was rebuilt in ReliaSim and independently validated by Tom Lange: the ReliaSim model performed within 1% of both the plant’s measured OEE and the original ExtendSim model, and ran the same one-year simulation roughly 1,200× faster on the same laptop. Read the published-validation case study.
- Can you show a model validated within 1% of a plant’s measured OEE?
- Was the validation published, or done by a customer, or only by you?
- Was it compared per failure mode, or only in aggregate? Over what period?
- Does the software help me validate my own model against my own history?
What data will the model need, and do you have it?
For a production line, the most important input is the stop-by-stop event record your historian or downtime system already keeps: where it stopped, why, and when. That record is separated by failure mode and fitted into a time-to-failure and a time-to-repair distribution for each one. Averages alone are not enough. Two machines with the same MTBF and MTTR can affect a line very differently, because how many stops outlast a buffer depends on the spread of the distribution, not its mean.
Real exports are messy, with day-first dates, planned stops and idle weekends to handle. Find out who does that work, and how the tool fits or imports distributions. Downtime data analysis walks through the whole path from stop log to distributions.
- Which distribution types are supported, and can several failure modes be attached to one machine?
- Can failure modes run on operating time, calendar time, or cycle counts?
- When an input is missing, does the tool flag it, or quietly use a default?
How fast does it run, and how many runs will you need?
Run time sets how many questions you can afford. A one-year run that takes overnight is a run you do three of, and the meeting becomes an argument about which three. When it takes seconds, you can sweep buffer sizes, line speeds and every failure mode, with replications.
For a low-volume system with a handful of scenarios, any competent tool may be fast enough. For high-speed lines, sensitivity studies and optimization, speed is often the deciding factor.
- Time a full-length run of a model at my scale and speed, in front of me.
- Does run time grow as line speed goes up?
- Are runs reproducible from a fixed seed, and how are replications and sweeps set up?
Who builds and maintains the model?
A model is only useful while it matches the line, and lines change. Decide early whether an engineer in house will own it, a consultant will build it, or both. In-house ownership needs modeling skill that survives staff turnover; a consultant-built model needs a clean handover or it goes stale when the engagement ends.
- How long does it take a process engineer, not a simulation specialist, to build a first useful model?
- Can stakeholders open and run a model without a full license?
- If a consultant builds it, do we receive the model in a tool we can keep running?
Where does it have to run?
Models encode proprietary process knowledge, and many plants run segmented OT networks. Involve IT early, because this question can end an evaluation late. Some tools are desktop software that can run air-gapped; others are cloud services.
- Does the software need internet access to run? Is offline licensing available?
- Where are models, historian extracts and results stored?
- If there are AI features, what model content leaves the machine, and can a local model be used?
What does it really cost to own?
The license price is the visible part. The larger costs are usually the hours to build and validate models, the training to keep someone capable, and the work of updating a model when the line changes. Compare total cost of ownership over the life of the decisions you expect to make, not the first-year quote.
- Subscription or perpetual? Per named user, or concurrent? What does annual maintenance cover?
- Are the methods, libraries or optimizers I need in the base product or priced separately?
- What do training, stakeholder viewer licenses, and vendor hours for a first model typically add?
Well-known tools, grouped by primary method
A starting map, not a ranking. Each tool is grouped by the method its vendor leads with; most general-purpose packages reach beyond it, so check current capabilities with the vendor.
| Tool | Primary method | Areas its own materials emphasize |
|---|---|---|
| Arena | Discrete event | Manufacturing, packaging, food and beverage, supply chain, logistics |
| FlexSim | Discrete event, 3D | Manufacturing, material handling, supply chain |
| Simul8 | Discrete event | Manufacturing, bottlenecks, lean and Six Sigma, process improvement |
| Simio | Discrete event | Digital twins, planning and scheduling |
| Siemens Plant Simulation | Discrete event | Throughput optimization, factory and line design, logistics |
| ExtendSim | Discrete event, discrete rate, and reliability block diagrams | General-purpose modeling, high-speed consumer goods, reliability engineering, process flows |
| AnyLogic | Multimethod: discrete event, agent-based, system dynamics | Manufacturing, supply chains, warehouses, mining, business processes |
| ReliaSim Ours | Discrete rate, with per-failure-mode reliability | High-speed filling, packaging, bottling, converting and continuous process lines |
Product names are trademarks of their respective owners. They are referenced for identification only; no affiliation or endorsement is implied. Descriptions summarize each vendor’s own public product pages as of September 2026. If you are weighing a discrete rate tool for a production line, ReliaSim’s manufacturing simulation software page also lists the problems it is not built for.