Simulation libraries
Simulation libraries your modelers build on
We build and curate libraries of equipment blocks and objects that work inside your simulation tool, so every model of a filler, conveyor or palletizer behaves the same way, and the next model starts half built.
One line, six library blocks. Each block carries its own speeds, failures and changeovers, tested once and reused in every model.
Why a library
Why build a library instead of another model
A library is the part of simulation work that keeps paying off after the project ends.
Every model agrees
When each plant models its filler the same validated way, results from two sites can be compared, and nobody argues about whose model is right.
New models start half built
Modelers drag in tested equipment instead of rebuilding logic from scratch, so a new line study takes weeks instead of months.
Your experts' knowledge stays
The way your equipment really behaves gets written into the blocks, where it survives staff changes and tool upgrades.
What we do
Build it, then keep it working
Libraries don't stay useful on their own. Tools release new versions, equipment changes and modelers find edge cases. We do both halves of the job:
- Build: equipment blocks and objects for your lines, such as fillers, conveyors, accumulation, labelers, case packers, palletizers, tanks and changeovers, with the parameters your engineers already use.
- Connect to data: blocks that read speeds, failure data and schedules from a database or spreadsheet, so models change with a data update, not a rebuild.
- Curate: test each block against measured line behavior, document it, keep versions, and carry the library forward through tool upgrades. See the model migration guide.
- Train: show your modelers how to use and extend the library, so it keeps growing after we leave.
In which tools
Libraries inside the tools you run
ExtendSim: custom blocks written in ModL, grouped into libraries, including rate-based blocks for high-speed and bulk flow.
Siemens Plant Simulation: object libraries and line integration libraries built and managed for manufacturing teams, with SimTalk methods behind each object.
Other tools: we are tool agnostic. The same approach works wherever your modelers work.
Licenses for the tools come from the vendor. We build what you run on them.
Libraries we have built
We have been building simulation libraries since the early 1990s
Our Bulk Flow (Rate) and Database libraries for Extend, now ExtendSim, sold more than 700 licenses and were the origin of ExtendSim's Discrete Rate and Database libraries. Supply Chain Builder carried the same idea to whole networks.
Today our modelers build and manage Plant Simulation libraries for manufacturing lines alongside the ExtendSim work.
- 1990s
SDI Industry and Bulk Flow (Rate)
The first commercial discrete rate library, built on Extend for continuous and high-speed operations.
- 1990s
SDI DB (Database library)
Models driven by tables instead of hand-set parameters.
- Late 1990s
SDI Supply Chain Builder
Network-scale blocks. The first VINLogic model was built with it. Read the case.
- Today
Plant Simulation libraries
Line integration and equipment libraries for manufacturing teams.
Tell us your problem
Want every model to start from the same tested blocks?
Tell us which tool your team uses and which equipment you model most. We'll suggest what a first library should cover.
- A straight answer on whether simulation is the right tool
- Which tool fits, even if it isn't one we use every day
- A rough scope and timeline, before any commitment