DBR77 Digital Twin

Production simulation in Factory Sim

Factory Sim is a deterministic discrete-event simulation of your production week: stations, routings, buffers, transport, shifts and the production plan. Times are fixed nominal values, so the same input always gives the same result. You see throughput, WIP, lead time, on-time delivery, station utilization and the bottleneck before you change the line.

The report of a run starts with a management summary and the key figures. Illustrative scene from a demo project. It does not show a client's plant.

In short

Factory Sim is a deterministic discrete-event simulation of your production week: stations, routings, buffers, transport, shifts and the production plan. Times are fixed nominal values, so the same input always gives the same result. You see throughput, WIP, lead time, on-time delivery, station utilization and the bottleneck before you change the line.

When to use

When this helps

You need to know whether the line can deliver the production plan on time with the current shifts.

You want to find the real bottleneck, see why it limits the line and test what removing it gives you.

You compare investments, layouts or line changes on the same measures.

Films

See it in action

Short films from the DT 2.0 demo project. Narration and transcripts are in English.

How to play a simulation run | DBR77 Digital Twin · Demo project
Transcript

A run is a simulation of production over time. Press play to watch it in the 3D model. Switch the speed to ten times or sixty times to get through a shift faster. Click the timeline to jump to any moment of the run. The live results panel shows what has been produced, the throughput, line utilisation, work in progress and blocking.

How to read the simulation report | DBR77 Digital Twin · Demo project
Transcript

Open the report to get the analysis of a run. The header gives the process, the period and the shifts that were simulated. The management summary names the most loaded resource and gives the key figures: output, on-time delivery, lead time and work in progress. Load against takt shows how busy each station and operator is. What to improve lists the next steps. Export the report as a PDF to share it.

Find the bottleneck before you build | DBR77 Digital Twin · Demo project
Transcript

Where does your line really lose output? Averages hide waiting, blocking and shared machines. Run the shift in DBR77 Digital Twin and watch the flow in 3D, queue by queue. Live results show output, utilisation, work in progress and blocking. The analysis report points to the most loaded resource. Then test the change on the model first. Try it for free.

What it does

What you can do with it

The model

  • Items, BOMs, routings, products and a production plan with due dates and priorities.
  • Stations with input and output buffers and setup matrices.
  • Shifts, and transport with forklifts, hand trolleys and AGVs.
  • Cycle and setup times as fixed nominal values. The model has no randomness, so the same input always gives the same result.
  • A production plan with due dates and a shift calendar that the run follows.

The results

  • Throughput until the plan is done, units completed and mean WIP.
  • The bottleneck with its cause and the periods when it limited the line.
  • On-time delivery, lead time, WIP over time and utilization per station.
  • TOC recommendations from the run, such as a buffer before the bottleneck, a shorter cycle or a parallel station.
  • Every analysis table can be downloaded as CSV.
The end of a run: the live panel shows the final figures for the plan.

Compare variants and experiments

Keep the current state as the base model and test each idea on a copy. The base does not change until you decide.

  • Simulation variants: a version tree of the base and its copies, with the configuration differences listed field by field.
  • Results side by side for each version, with the change against the base and the best version marked.
  • The same input always gives the same result, so a difference between two variants comes from the change you made.
  • Experiments that change one thing, such as a sweep of the cycle time at one station.
  • Results side by side for each variant: throughput, WIP, lead time, on-time delivery and utilisation.

Getting started

How to start

  1. 1

    Start from data or the demo

    Enter routings, stations and nominal times by hand, bring them in by import (import scope to be confirmed) or open the Demo Factory.

  2. 2

    Fix what the checks flag

    The run starts when stations, routings, buffers and shifts fit together.

  3. 3

    Run, read, change

    Read the bottleneck and the TOC recommendations, then test the change in a variant.

What it does not do

  • Factory Sim does not read live machine data during a run. It works on the model data you imported or entered.
  • It does not simulate warehouse stock or picking. Stock is treated as unlimited.
  • Times are fixed nominal values, so every run of the same input gives the same result.
  • It suggests changes from a TOC catalog. It does not run an optimization solver.

Questions

Have a question about this topic?

Tell us what it is about. We will reply within one business day.

We use your data only to answer your request. See our Privacy Policy.

Next step

See it on your plant

Talk to an expert. We will go through your layout, your process and the data you already have.

Frequently asked questions

What is Factory Sim?
The discrete-event simulation in DBR77 Digital Twin. It runs your stations, routings, buffers, transport, shifts and production plan through time and reports throughput, WIP, lead time, on-time orders, station utilisation and the bottleneck.
What does deterministic simulation mean?
Times are fixed nominal values, so the same input always gives the same result. A difference between two variants therefore comes from the change, not from noise. Simulating over time instead of using averages also shows queues, shared machines and due dates.
What data do I need to start?
Items, routings and stations with cycle times, a production plan and shifts. Nominal times are enough to start. Enter them by hand or bring them in by import (import scope to be confirmed). Integration with ERP, MES or other systems is an individual project.
How do I compare options?
Create a variant on a copy of the base model for each option, run it and compare the results with the base side by side: throughput, WIP, lead time, on-time delivery and utilisation. Because the simulation is deterministic, a difference comes from the change.