What Industry 4.0, IIoT and digital twins mean

For a 50-person plant, Industry 4.0 means running production on live data from your machines. The Industrial Internet of Things (IIoT) is the sensors, networks and software that carry that data, and a digital twin is a software copy of a machine that exchanges data with it automatically in both directions. A small plant can start one step short of a twin, with a live digital shadow of every machine.

Each term below comes with its source, a shop-floor example and a rule for when you need it.

What Industry 4.0 means#

The name comes from Germany’s Industrie 4.0 program. Its working group handed recommendations to the German Chancellor at Hannover Messe on 8 April 2013, and the BITKOM, VDMA and ZVEI industry associations founded the Plattform Industrie 4.0 the next day.^[1] The “4.0” frames the program as a fourth industrial revolution.

On the floor, the change is concrete. Without connected machines, a supervisor walks the floor at 2 p.m. and learns that a Haas VF-2 has waited on material since 11:40. With them, the stop shows up as it happens, with a reason attached.

Industry 4.0 isn’t a standard, and no body certifies a plant against it. The closest document is RAMI 4.0, the Reference Architecture Model Industrie 4.0, published as DIN SPEC 91345 in April 2016 and free to download.^[2] It’s a three-dimensional layer model that shows at which level, and in which phase of its life, each Industry 4.0 component plays a role.

How IIoT differs from IoT#

The Internet of Things (IoT) covers any connected device. IIoT is the industrial subset, and the difference is what sits at the end of the wire. A connected thermostat that drops offline costs a few degrees of comfort. A monitor on a 350-ton press that drops offline hides every stop until someone walks past the press.

IIoT also touches operational technology (OT): programmable systems and devices that interact with the physical environment, detecting or causing a direct change by monitoring or controlling devices, processes and events.^[3] A CNC control and the PLC on a packaging line are OT. The ERP server in the office is IT.

Two ways to get machine data#

Machine data leaves a machine by one of two paths. A sensor on the outside reads a physical signal, such as vibration, sound, current or a laser beam, and infers whether the machine is running and how many parts it made.

A connection to the machine’s controller, over a protocol such as MTConnect or OPC UA, reads what the control already holds: program name, alarms, axis positions and process values. The PLC glossary entry explains what a controller is.

Choose a sensor when you need the same data from every machine, old or new. Add a controller connection when you need alarms, programs or process values, and bring IT in early, as the security section explains.

What a digital twin is#

NIST describes digital twin technology as electronic representations of real-world entities that let you view their states and the transitions between those states.^[4] The word gets stretched. A CAD file, a status dashboard and a closed-loop controller can all carry the label, and only the controller fits the definition above.

A 2018 review of digital twin research in manufacturing sorted these uses into three levels with one test: which way data flows automatically between the machine and its copy.^[5]

Digital model, digital shadow and digital twin#

• Digital model: no data flows automatically in either direction. People type values in and carry decisions out, as with a CAD model or a capacity spreadsheet.
• Digital shadow: data flows automatically from the machine to the copy, so changes on the floor appear without anyone typing them. A car’s dashboard showing live speed and mileage is the standard example,^[6] and a screen showing each machine’s live status works the same way.
• Digital twin: data also flows automatically back, so a change in the copy changes the machine. A controller that adjusts a setpoint from a model’s output closes that loop.

In decision support, such as predictive maintenance, the return path runs through people. A technician carries out the maintenance action, so that half of the loop isn’t fully automatic; control applications are the ones that need both directions automatic.^[7] On a job-shop floor, the live view is where the value starts.

How the three terms fit together#

The three terms describe layers of one system. Industry 4.0 is the goal of running a plant on live data. IIoT is the plumbing that moves the data, and a digital shadow or twin is what the data builds at the end of the path.

For example, a stamping press stops at 9:12 with a misfed strip. The sensor records the stop, the network carries it, and the platform shows the press as stopped. The supervisor sends a setter, and that action is the return path.

Automating that last step would turn the shadow into a twin. A misfed strip has no automatic fix, so the press stays a shadow, and loses nothing by it.

What each one is worth to a small plant#

The value of each level shows up in hours. Take a hypothetical shop with 10 CNC machining centers.

A digital model earns its keep before you commit capacity. Say a customer asks for 600 parts a week at an 8-minute cycle: 600 × 8 = 4,800 minutes, or 80 hours of cutting.

At the measured 50% uptime, those 80 hours need 160 planned hours, two machines’ full weeks. The spreadsheet is the digital model, and the shadow’s measured uptime is what makes its answer trustworthy.

A full digital twin pays off where software can safely change the process on its own, such as a controller holding a temperature setpoint on a continuous line. In a job shop running mixed parts on mixed machines, the return path stays with people.

Common obstacles and how to handle them#

Old machines#

Many plants run machines older than their network. A 1998 lathe has no Ethernet port, and its control speaks no modern protocol.

A sensor on the outside gets state and counts from it anyway, because it reads the machine rather than the control. The same approach scales to a whole line: production line monitoring without PLCs shows how.

Too much data, too few answers#

Collecting every signal is the quickest way to stall. Start with three things every machine can report: whether it’s running, how many parts it made and why it stopped. The guide to manufacturing data collection ranks what to add after them.

For example, 10 machines that report their state once a second produce 10 × 86,400 = 864,000 readings a day. The useful output is a short list of stop reasons ranked by hours lost, the Pareto view of downtime.

Security#

Every connected device adds a path for data, so ask where the data goes before anything ships. A sensor that reads the machine from the outside never touches the control.

A controller connection is a security concern for many plants, and IT usually reviews it first. Bring IT in at the start with three questions for any vendor: where the data goes, which port it leaves on and whether the device touches the control.

People and skills#

Data changes nothing until someone acts on it, and skilled people are scarce. Deloitte and the Manufacturing Institute estimate that US manufacturing could need as many as 3.8 million more employees between 2024 and 2033, and that 1.9 million of those jobs could go unfilled if the skills and applicant gaps aren’t addressed.^[8]

So pick tools an operator can use at the machine without training, and put one person in charge of the stop reasons. A 15-minute Monday review of last week’s top three reasons is enough to start.

See machine state live#

IoTFlows builds the digital shadow from a sensor on the outside of each machine. SenseAi mounts with a magnet, reads vibration and sound, and decides running or stopped every second on the device, with no PLC connection. The data path from sensor to dashboard shows where each decision is made.

Every machine then reports its status, uptime, downtime with reasons and part counts in machine monitoring. Where a plant wants controller data too, the IoTFlows edge device on Enterprise reads only the controls the plant chooses to connect.

Hilco Vision runs SenseAi and BeamTracker on its floor and increased production more than 20% by analyzing and adjusting in real time instead of waiting days for reports.

Where a small plant should start#

Match the level to the question you need answered.

1. Pick your costliest machines

   Choose five to ten machines whose stops cost the most, such as the bottleneck cell.

2. Capture state and counts

   Put a sensor on each machine, or connect a controller where IT has approved it.

3. Name the stops

   Give operators a short list of stop reasons and have them tag each stop at the machine.

4. Review every week

   Rank last week’s stops by hours lost and fix the top one.

5. Feed your model

   Put the measured uptime into your capacity spreadsheet before you quote the next job.

If you’re weighing a monitoring system against an MES or a CMMS, machine monitoring vs MES vs CMMS sets out the question each one answers.