From OPC UA signals to actionable production insight
Timestamped events, machine states and dashboards with operating context
Our role
We defined the signal model, OPC UA integration, event storage, and role-based interface so scattered control data became a traceable operational product rather than another isolated dashboard.
The Problem
When a production line stops, an alarm rarely tells the full story. PLC signals exist, but they are scattered across controllers, HMIs and log files. Without aligned timestamps and state transitions, fault analysis depends on who happened to be standing by the line.
- Critical signals sit in silos with no common timeline across machines and shifts
- Post-incident analysis depends on whoever was on the floor, not a reliable event record
- Dashboards are either too technical for daily operations or too shallow for improvement work
Why It Matters
A dashboard is more than graphs. Signals need clear names, units, time bases and machine context; otherwise a normal operator stop can look like a process failure. Event history should make the sequence before and after a deviation inspectable.
- Ability to explain stops with evidence instead of assumptions
- Visibility of recurring fault patterns across shifts and lines
- Alignment between shop-floor reality and management reporting
Our Solution
Event-store architecture capturing alarms, state changes, and selected process values on a searchable common timeline
OPC UA ingestion and normalization layer that maps mixed machine signals into a documented operational data model
Role-appropriate dashboards giving operators a live view while leadership sees the same underlying facts
Signal dictionary with units, context, and naming conventions so data stays interpretable as the system grows
Results
Data exists everywhere but nowhere in a form teams can trust during or after an incident
Unified event history and live dashboards that turn machine behavior into shared operational insight
- A consistent signal and event model for understanding stops and sequences
- Historical machine-state and process data with timestamps for technical troubleshooting
- Role-based views of the same event, from shop-floor overview to engineering detail
Project context
A manufacturing environment with multiple production cells and mixed control platforms needed a practical way to reconstruct line behavior and support daily decisions. neexo scoped the signals with automation and operations teams, implemented the ingestion and event-recording architecture, and delivered views tailored to operators, maintenance, and leadership.
Deliverables
- OPC UA data capture setup with documented signal mapping
- Flight-recorder event database and search interface
- Role-based live and historical dashboards for operations, maintenance, and management
Want to explain production behavior with evidence, not gut feeling?
We can help analyze your situation and identify opportunities for similar solutions.