Production Optimisation
Run-state and fill levels from the line itself, shown on a 3D model of the floor, with alerts on the limits your process needs.
Night shift reports that line two stopped twice. By the time day shift looks it is running again, nothing was logged, and the cause depends on who you ask.
How Twinise Solves This
Nodes on the machines report movement, and with time-of-flight the fill level, clearance and position of parts, plus the air around the work. Twinise stores the readings and raises alerts on the limits you set. The Unreal twin (pilot) draws them on the floor.
What You Get
- Running or stopped. Movement through the IMU shows whether a machine is running, and raises an alert when it moves harder than the threshold you set. Compare shifts and lines.
- Fill level and clearance. Time-of-flight reads fill in bins, tanks and hoppers, clearance around moving equipment, and the position of a part through its travel.
- The air around the work. Temperature and humidity at the line, alerted against the window your process needs.
- On the floor in the twin. The Unreal plugin (pilot) shows equipment condition where the equipment is, with mesh tint and heatmaps.
Recommended Hardware
The Starter Kit is 8 nodes, enough for a single production line. Larger deployments use the same nodes and are scoped with you. Hardware is currently supplied as a pilot, by arrangement. Vibration and opening/contact sensing are tested on our nodes and can be integrated on request.
Where To Start
Start with the line behind the most handover arguments. A node on the main machine shows when it ran, and a time-of-flight node over the feed hopper shows when it emptied. Put both on one dashboard and set the alarm limits after a normal week.
Want to try this on your own site?
Hardware is supplied as a pilot, by arrangement. Tell us about your site and we will scope production optimisation with you.
Request a pilot