Skip to content
Digital Shop Floor | Part 9 of 10

IT and OT Architecture and Security, in Plain Words

Five layers, one source per data item, separated network zones and six security basics for connected machines.

Architecture discussions about the shop floor quickly fill with acronyms. Yet the decisions that matter can be explained on one page, and the people who run the area should understand that page.

Five layers

A common way to describe the shop floor follows the layer idea of the ISA-95 standard:

  • Business systems: orders, materials, costs and planning, usually in the ERP.
  • Shop floor applications: order execution, boards, work instructions, Andon and traceability. Often called MES functions.
  • Edge: a gateway close to the machines that collects and buffers their data.
  • Control: the CNC and PLC controls that run the machines.
  • Field: sensors, drives, stack lights and counters.

Information technology (IT) usually runs the upper layers, operational technology (OT) the lower ones. A digital shop floor connects both, so both teams belong in the project from the first day.

Three architecture rules

One source per data item. Orders come from the ERP, machine states from the edge, stop reasons from the terminal. Nothing is typed twice.

Interfaces are written down. For every data flow: which system sends what, when, in which format, owned by whom. A list of a dozen lines replaces a lot of guessing.

Buffer at the edge. Machines keep running when the network fails. Their data must survive several hours of outage without loss.

A manufacturing execution system is not one product you must buy at once. It is a set of functions. Start with the functions your use cases need.

Master data decides the quality

Most data problems on the shop floor are master data problems: an ideal cycle time from an old routing, a machine moved to another hall with its old ID, every area with its own reason list. Give each type of master data one owner and one place where it is changed. A performance value above 100 percent is not a success. It is a wrong cycle time.

Six security basics

Connected machines are part of the attack surface. Six rules prevent most incidents:

  1. Know your assets: a current list of connected machines, gateways and software versions.
  2. Separate the networks: machines in their own zones, no direct internet access.
  3. One path for remote access: suppliers connect through one controlled and logged access.
  4. Personal accounts and roles: no shared passwords.
  5. Updates with a plan: tested, scheduled, recorded. Old systems that cannot be updated are isolated.
  6. Backups and recovery: tested once per year.

The IEC 62443 series is the common reference for industrial security. Involve the security officer of your organization from the start and follow its rules.

Plan the bad day

Write down before go-live what happens when the network or the server is down: machines keep running, the edge buffers the data, the team uses a printed board. Test that fallback once a year. A shop floor that stops when the screen goes dark has traded one risk for a bigger one.

Newsletter

One Lean idea.
Every week.