Production Tracking Panel and OEE Dashboard
We show line status on operator screens, recurring stoppages on maintenance screens, and shift and OEE indicators on management screens. For each indicator, we document the signal used, the calculation rule and the update frequency. For management reports outside production, see our corporate dashboard and reporting service.
Downtime analysisGrafanaRole-based dashboardsAlertsData validation
What problem does this service solve?
Screens nobody looks at
There are dozens of charts, but none of them is tied to a decision.
Disputed OEE
OEE calculated without defining how planned downtime is counted and what the ideal cycle time is gives different results for different teams.
Information arriving late via Excel
An Excel report compiled at the end of the shift or day shows the problem only after it has grown.
Unclear data sources
If nobody knows which signal and which calculation produce an indicator, a wrong value goes unnoticed.
What we cover, and within what limits
A production dashboard presents collected machine and process data according to a specific decision of a specific role. The operator sees the current line status and deviation from target; maintenance sees fault frequency and duration; managers see OEE, capacity utilisation and trends. OEE (Overall Equipment Effectiveness) is generally calculated as availability × performance × quality. The definitions of planned production time, ideal cycle time, total count and good count should be set in writing by the organisation. The dashboard’s update frequency is measured in the project and the last update time is shown next to each indicator. Tools such as Grafana are widely used for time-series visualisation; the tool is chosen according to the existing infrastructure and permission requirements.
Technical scope
Roles and decisions
Who each dashboard is for, which question it answers and which action it should trigger.
Indicator definitions
OEE components, downtime classes, targets and calculation rules; written approval together with production and quality.
Data source and validation
The source of each indicator is documented; in the initial period, values are compared with manual records. If data is missing or stale, the dashboard flags it.
Dashboard design
Layout, colour and threshold rules readable from a distance for line screens; analysis dashboards for desktops.
Alerts
Notifications that reach the right person for threshold breaches, long stoppages or data flow interruptions.
Permissions and deployment
Role-based access, kiosk setup for line screens and secure access from the corporate network.
Examples of role-based dashboards
Line screen (operator)
Current status, shift target and actual, active stoppage and its duration; large indicators readable from a distance.
Maintenance dashboard
Fault frequency, mean time to repair, recurring alarms and comparison by machine.
Production management
OEE and its components, distribution of downtime reasons, line and shift comparisons.
Energy and resources
Consumption per line or machine, energy per unit produced, and trends.
Prerequisites: what we need to get started
We identify missing information and access together in the first meeting and complete them during the survey.
- A reliable data source (if there is none, we start with IIoT and data collection work)
- Definition work with the production, maintenance and quality leads
- Planned downtime, shift and target information
- Location, display and network connection for line screens
- IT support for user and permission management
Deliverables
Role–decision–indicator matrix
Written indicator and OEE calculation definitions
List of validated data sources
Line, maintenance and management dashboards
Alert rules and recipient list
Dashboard editing and administration guide
Representative scenario: making OEE mean the same thing to everyone
The production and maintenance teams report different OEE values. First, the definitions of planned production time, ideal cycle time, total count and good count are written down together. The calculation is done in one place and the source signals become visible. The line screen shows only information the operator can influence; the management dashboard focuses on trends and comparisons.
This is a representative project flow; it is not a completed customer reference.
Service summary
IIoT and Production Data Collection
We determine the signals and sampling rates needed for production, quality, energy or maintenance.
Scope limit
Dashboards are for decision support; they do not take on control or safety functions. Sending commands from a dashboard to a machine is not part of our design. MES product selection and licensing are assessed separately.
How do we proceed?
No step that affects production is carried out until the maintenance window, configuration backup and rollback plan are clear.
Definition
Roles, decisions and indicators are written down.
Prototype
The first dashboards are built with real data.
Verification
Values are compared with manual records.
Rollout
Line screens and alerts are put into operation.
Improvement
Dashboards are simplified based on usage feedback.
Questions about Production Monitoring and Dashboards
Is an MES always needed for a dashboard?
No. If status, counter and downtime data are collected reliably, basic production monitoring and OEE dashboards can be set up without an MES. If work order, traceability and quality flows are needed, the need for an MES is assessed separately.
How do you calculate OEE?
The general formula is availability × performance × quality; we define together with you, in writing, how planned production time, ideal cycle time, total count and good count are counted. The calculation rule is kept visible on the dashboards.
Can tools other than Grafana be used?
Yes. Your existing reporting and business intelligence tools, SCADA screens or historian clients are also considered. The tool is chosen after the indicator definitions and data sources have been set.
Is it safe to access line screens from the corporate network?
Dashboards read from the data layer; they do not require direct access to the control network. Access is provided through the OT DMZ or the data layer with role-based permissions.
Work that can be planned together
IIoT and Production Data Collection
We determine the signals and sampling rates needed for production, quality, energy or maintenance.
SCADA, MES and ERP Connectivity
We identify which system production orders come from and where production quantity and scrap data are generated.
OPC UA, MQTT and Data Integration
We read the data model a machine exposes via OPC UA and, in projects that need MQTT, distribute this data to applications through a broker.
Knowledge Center
Technical guides for this service
Let's plan a technical survey for production monitoring and dashboards
Briefly describe your line, the PLC and network equipment you use and your goal; we will respond with a written proposal covering scope, assumptions and deliverables.