Running versus stopped
Use a signal that represents productive runtime rather than simply controller power or automatic mode.
PLC MONITORING OVERVIEW
Using PLC data for production monitoring.
PLCs often contain useful production information. Where the controller, network and site policies allow it, selected operational data can support production visibility without duplicating information already available in the machine.
Use information that answers a business question
The goal is not to collect every available controller value. Useful production monitoring focuses on information that helps explain status, output, rate, downtime or another defined operational need.
Validate the meaning of the data
A controller value should be understood in the context of the real process. Names alone do not guarantee that a signal represents productive runtime, finished output or another KPI definition.
Fit the site architecture
PLC connectivity should be assessed with the customer’s engineering and IT/OT requirements in mind. Controller type, protocol, network design and access policy all influence the appropriate approach.
WHAT DATA IS USEFUL
Start with production signals that answer an operating question.
A PLC may expose hundreds or thousands of values, but production monitoring normally needs only a small validated set. A reliable run state and production count are often enough to establish runtime, output, rate and the timing of stops. Additional values are useful only when they explain a real production loss or operating condition.
The key step is confirming what each value means on the real machine. A tag called “Running” might represent motor power, automatic mode or actual production depending on the control program. Likewise, a counter may increment per cycle, per pack or per finished unit. Clear definitions prevent misleading OEE and production reports.
Completed production
Validate whether the count represents cycles, pieces, packs, kilograms or another production unit before using it in output and rate calculations.
Product and operating mode
Add context only where it improves interpretation, such as product, order or machine mode when targets differ between runs.
SAFE INTEGRATION APPROACH
Production monitoring should read the machine, not take control of it.
For monitoring, the preferred design is normally read-only access using the minimum permissions required. The PLC remains responsible for machine control and safety logic while the monitoring layer collects selected operational values. Network segmentation, credentials, firewall rules and protocol settings should follow the site’s IT/OT requirements.
Where controller access is not practical, external or discrete signals can provide a simpler path. An older machine may still expose a reliable run indication and count pulse even when the PLC is unsupported, locked down or unavailable.
Prefer read-only controller access
Collect only required production values
Validate every tag against the physical process
Keep machine control and safety logic unchanged
Use site-approved IT/OT network architecture
Test counter reset, rollover and restart behaviour
Confirm timestamps and reconnect behaviour
Use direct I/O where PLC access adds unnecessary complexity
PROTOCOLS AND COMMISSIONING
OPC UA and Modbus are useful when the machine already supports them.
OPC UA can provide structured controller data with authentication and security features where supported. Modbus TCP is common on industrial equipment and gateways and can provide simple register-based access. Neither protocol makes the data automatically correct: node names, register addresses, data types, scaling and update behaviour still need to be checked against the machine.
A commissioning test should compare the digital record with the real production process. Start and stop the machine through normal operation, confirm the count increments exactly as expected, verify the calculated rate and then check reconnect behaviour after a communications interruption.
COMMON QUESTIONS
Frequently asked questions.
Can any PLC be used for production monitoring?
Compatibility depends on the controller, available interfaces, network architecture and the information required.
Is PLC data always necessary?
No. Some machines can be monitored using other suitable production signals.
EXPLORE MORE
Related ClearRivet information.
See it. Then prove it.