Machine Monitoring
A digital twin application that shows the machines of a seed processing line in a 3D scene and reflects their status data in real time.
Design and development · 2026
Demo login: izleyici / izleyici123
The brief
On a production line you had to walk to the control board to see the state of the machines. Which machine slowed down, where the buffer is filling up, when maintenance is due: these questions could only be answered on the shop floor. What was needed was a system that presents the same information in the browser, instantly and visually.
What I did
I built a digital twin of the line. Every machine stands in a 3D scene, its colour changes with its status, and its motor and fan spin when running. The line screen has a nine-gauge summary strip, machine cards and a line output chart. Alarm history, maintenance plan, energy tracking and recipe management are on separate screens. There are three roles: the viewer only sees, the operator starts and stops machines, the administrator manages everything.
Result
The app is live on its own subdomain and can be explored with the viewer account. It runs on in-memory sample data and starts clean on every launch; on a real site the same code switches to persistent data with SQL Server.
Technical decisions
In the background a simulation service that ticks once a second runs the machine physics: as speed rises the temperature increases, past a threshold a protection reduces the speed, and at a critical threshold a fault occurs. Results are pushed to the browser with SignalR and the page changes without reloading. The 3D scene is Three.js, the control panels are Blazor. Permissions are enforced by checks on the server, not by hiding menus.
- ASP.NET Core
- SignalR
- Blazor
- Three.js
Highlights
- Live machine status in a 3D scene
- A simulation ticking once a second
- Alarm history, maintenance plan, energy tracking, recipes
- Viewer, operator and administrator roles
- Updates without page reloads via SignalR
Thinking of something similar?
