Are you buying an animation, or a reusable simulation model?

When a machine or line needs to be shown, the conversation often starts with a concrete request. A film for a trade show. A sequence for a sales meeting. A visualisation of a machine that has not been built yet. An animation can answer that request well. It can explain a hidden function, show a process that is hard to film, and present the machine from angles that do not exist on the shop floor.

The next request usually arrives from another department. Engineering wants to check a changed mechanical layout. Automation wants to try a sequence. Sales needs a second variant. Marketing needs stills and clips for a new campaign. If the first delivery was only a locked animation, each of those needs starts new scenes and new production work.

If the machine is built as a simulation model instead, several of those deliveries can come from the same digital core. Price the follow-on work as part of the first purchase. The look of the first clip is one output. The question is what the organisation can still do with the asset after that clip is handed over.

An animation follows a planned course. Movements, camera angles and timing are set in advance. The result is delivered as film or stills. The viewer can see the process and, as a rule, cannot change it.

A simulation model is built around the machine's functions and states. Conveyors can start and stop. Robots can take commands. Sensors can change status. Different scenarios can run without animating the whole sequence again.

An animation can be one of the outputs produced from the simulation model. The buying choice is whether you pay for a finished sequence, or for a core that can still produce that sequence later.

Special machines change through the project. Mechanics move. Processes are adjusted. The customer may pick another configuration. At the same time, different departments look at the same machine from different angles.

Engineering cares about structure, motion and access. Automation works with signals, sequences and interlocks. Sales has to make the solution understandable. Marketing has to turn the same technique into material that can travel across channels.

If each department orders its own visualisation, several versions of the same machine appear. Geometry drifts. Processes go stale. A change has to be applied in more than one place. A shared simulation model does not remove the need for different outputs. It gives those outputs a common origin, so each department can get what it needs without rebuilding the machine digitally from scratch.

Reuse starts with a shared origin for geometry, functions, motion and the central processes. It does not mean everyone works in the same interface or at the same level of detail.

Engineering uses the model to review reach, access, motion paths, product flow and how stations interact. Photorealism is optional. Correct geometry, kinematics and the mechanical limits that matter for the review are not. The model does not replace mechanical calculation or the authoritative CAD. It gathers the parts that have to be seen in motion, or judged across mechanics, process and operator access. When the machine changes, the affected geometry, model version and scenarios should move together. Otherwise the organisation decides from a convincing picture of an old machine.

Automation gets value when the model can respond to commands and return sensor status, positions and acknowledgements. That can support sequence tests, mode changes, interlocks, alarms and central HMI flows before the physical machine is finished. A model that only moves is not virtual commissioning. The coupling, the test scope and the actual code still have to match the verification the project needs.

Sales can pick variants, show a station, or run a process that matches the customer's product. A technical model with hundreds of signals is rarely the right surface for a customer meeting. Keep the core. Design the navigation and the scenarios for the meeting. Training and service need realistic procedures, states and operator context. Marketing can record the same processes from new cameras once the functions already exist, then still do the creative work on message, pace and visual style.

No. The terms should stay distinct. A 3D model shows geometry. A simulation model adds behaviour, functions and scenarios. A digital twin also has a defined relation to the system it represents, for example through control logic, configurations, or data from the physical machine.

Projects do not have to start with a complete digital twin. A machine builder can begin with a simulation model for one bounded purpose and later add PLC coupling, test scenarios or operating data. Describe what the model actually does: what is shown visually, what is simulated, and what is connected to a controller or data source.

A shared core is also not one heavy scene that tries to satisfy every requirement at once. Engineering needs precise motion. Automation needs stable signals. Marketing needs materials, light and rendering. Mixed without architecture, the model becomes hard to maintain and slow to run. Keep geometry, structure and central behaviour in a core. Put PLC integration, customer demonstration, training or photoreal content in separate layers. That takes modular build and clear boundaries. It is how reuse stays possible without forcing every department into the same product.

If the need is one film with a fixed message, and nobody expects later interaction, test or variants, a conventional animation is often the cheaper and faster delivery. It can concentrate on story and visual quality without paying for functions that will not be used. That fit is common for a single product launch, a concept film, or a process that is already stable and clearly defined.

The simulation model earns its cost when more than one department will use it, when the machine exists in variants, or when processes need to change and be tested. Start from the expected use. The most capable model is not automatically the right buy.

Start with the expected uses in the first year. If the model will only ever produce one film, do not overbuild it. If it later has to support virtual commissioning, interactive demonstration or training, the architecture has to allow that without a rebuild.

A bounded pilot is a practical start. Pick one station or one central process that has both technical and commercial value. Use it to set standards for geometry, functions and reuse before the model grows. Assign ownership for CAD updates, behaviour and scenarios. A model that does not follow machine revisions loses value even if the original plan named many uses.

Judge value across the deliveries the model replaces or supports. A film-versus-model price comparison misses later visualisations, variants and tests. Count how often the machine will be visualised, how many variants exist, which tests can happen earlier, and which departments will actually use the result. Leave time for upkeep. Platform choice, including real-time 3D environments such as Unity, comes after those decisions. The platform does not fix scope, ownership or versioning on its own.