
What Is Machine Data Collection (MDC)?
Machine Data Collection (MDC) means that the running status, quantity produced, alarm codes and process values of production machines are read from the machine automatically, without human intervention, and recorded in a central system. MDC is the reliable data source for OEE and downtime analysis.
- Core data collected: status (running/stopped/alarm), count, cycle time, alarm code, process parameters.
- Connection paths: OPC UA, MTConnect, Modbus, vendor protocols (Mitsubishi MC, Omron FINS, Euromap) or sensors/counters.
- Users: production, maintenance and industrial engineering teams.
- Benefits: real-time machine visibility, objective OEE, detection of minor stops.
What Is MDC?
Every machine produces a series of signals while running: the running bit in its controller, the part counter, the alarm log, spindle speed, temperature. MDC reads these signals at regular intervals or on events, adds a timestamp and writes them to a database. Raw signals are turned into “events”: the running bit dropping is the start of a stop, a counter increment is the production of a part.
Within shop-floor data collection, MDC is the automatic part on the machine side. Operator entries (downtime reason, scrap explanation) fall outside MDC’s scope, but MDC events trigger the operator’s entry: when the machine stops, the terminal asks for a reason.
Which Data Is Collected?
| Data | Source | Use |
|---|---|---|
| Machine status | Running/idle/alarm bits, program status | Availability, downtime duration |
| Production count | Part counter, cycle-complete signal | Performance, work order progress |
| Cycle time | Difference between two cycle signals | Speed loss, verifying standard time |
| Alarm code | Controller alarm list | Automatic assignment of downtime reason |
| Process values | Temperature, pressure, speed, injection pressure | SPC, predictive maintenance |
| Program / mould information | Active NC program, mould number | Product matching, mould life |
How Is the Connection Made?
Direct connection via protocol
Most modern machines offer a communication interface. MTConnect or vendor APIs are common for CNC machines; protocols such as OPC UA, Modbus TCP, EtherNet/IP, Mitsubishi MC and Omron FINS for PLCs; and Euromap 63/77 for plastic injection moulding machines. With this method the data is rich and accurate, but the machine manufacturer must have opened the interface.
Signal-level connection
On machines without communication capability, the green/yellow/red signal lamp, a relay output or motor current is connected to an input module. A counter giving one pulse per cycle provides count information. Wireless IoT nodes carry these signals to the centre without cabling. The data is simpler (status + count) but enough for OEE.
MDC and OEE
The three components of OEE rely directly on MDC data: Availability is calculated from machine status durations, Performance from the ratio of actual cycle time to standard time, and Quality from the difference between the counted and approved quantity. OEE calculated from manually collected data usually comes out higher than it should; when MDC goes live, the first shock is “OEE dropped”. In fact it is not OEE that dropped, it is invisible losses becoming visible.
Common Mistakes
- Going live without signal validation: compare the MDC count with the production report for a week.
- Leaving alarm codes unmapped to downtime reasons: code 4711 tells nobody anything; “material ran out” does.
- Choosing the wrong short-stop threshold: too low a threshold swamps the operator with constant requests for reasons, too high a threshold hides minor stops.
- Neglecting network infrastructure: IP conflicts, switch capacity and security segmentation in the OT network should be planned from the start.
Frequently Asked Questions
What is the difference between MDC and MES?
Can MDC be applied to every machine?
How often should MDC data be collected?
Machine Data Collection in EFFIX MES
EFFIX MES collects data from CNCs, PLCs and counters directly with OPC UA, MQTT, Modbus, EtherNet/IP, MTConnect, Mitsubishi MC, Omron FINS and Euromap 63/77 protocols, and from machines without communication via the Inolink wireless IoT network. Machine status is monitored on real-time screens and Andon boards, stops open automatically and the operator completes the reason on the HMI terminal. The same data feeds OEE, cycle time screens, MTTR/MTBF and predictive maintenance anomaly detection. For details, see the EFFIX MES page or request a demo.
