Why the supplier provides a diagram and for whom
The architecture diagram is the first document the plant's IT or OT department reads about the supplier's system. It shows in which network zone each element runs, what it uses and which connections are allowed. Without a diagram, the conversation about a pilot reduces to questions that the supplier answers orally and that nobody writes down.
The supplier hands the diagram to the person indicated by IT: the network architect, the administrator or the OT coordinator. The document must be understandable without a conversation, and at the same time short enough to attach to the risk assessment form.
Layout of the one-page PERA diagram
The diagram for the customer is one page in the PERA model layout with 8 levels: from 0 to 6 and DMZ 3.5. Levels 0-2 cover physical objects and control, level 3 covers production operations, level 3.5 the intermediate zone, levels 4-5 the plant network and business systems, and level 6 external services. This layout is familiar to OT departments and lets them quickly locate the system.
The OHS and location system does not control the process, so it should not run at levels 0-2. The diagram shows this clearly: beacons and mobile devices on site, a server or instance in the appropriate zone and a connection through DMZ 3.5 where the plant requires it.
- levels 0-6 and DMZ 3.5 with labels
- system elements marked in the appropriate zones
- directions of connections and protocols at each arrow
- description of which connections are outbound only
- legend in three sentences, without the supplier's jargon
Five zones and outbound traffic
Besides PERA, it is worth showing on the diagram or in the description a simplified model of five zones: the plant site, users, the plant network, the customer's systems and the cloud in the EU. The model makes conversation easier with people outside OT, because it does not require knowledge of the levels.
No inbound ports are opened in the plant network, and outbound traffic is limited to HTTPS 443 to the instance address. This is the most important sentence on the diagram, because IT departments first ask about changes to the firewall. If the plant requires hosting on its own premises, the diagram shows a variant in which the instance runs in Docker containers on the customer's server.
Two versions of the document: for the customer and internal
It is good practice to have two versions. The first, one page long, goes to the customer. The second, internal, contains the supplier's self-assessment and open points, and is not sent to the customer.
The separation makes sense, because the customer version must be stable and readable, while the internal version is the supplier team's working checklist. The customer receives a document the supplier is ready to defend, and open points go to the conversation with IT as a separate list.
What remains open until the site inventory
Before the meeting with the plant's IT department, the following remain to be settled: the classification of the system as IT or OT, the directory service, IP addressing, the network interfaces of the gate and application whitelisting. The detailed model is produced after the site inventory, not earlier.
The supplier should not guess these points. It is better to state on the diagram or in a note attached to it that the details of addressing and directory integration will be set after the inventory, than to place on the chart assumptions that turn out to be wrong.
- classification: IT or OT system, which decides the zone
- directory service and the way users log in
- IP addressing and network ranges
- network interfaces of the gate
- application whitelisting and destination addresses
Instance isolation on the diagram
The diagram should show that customer data is separated. Each customer has an isolated instance with its own database and its own mail system. The instance can run in Docker containers on the customer's server, and some environments run on Kubernetes.
For IT this is important information, because it affects the assessment of shared-hosting risk. If the instance is dedicated, the risk relative to other customers is different from a multi-tenant model, and the diagram should reflect this.
Mistakes in supplier diagrams and how to avoid them
The most frequent mistakes are a diagram without connection directions, a schema without marked zones, and mixing PERA levels with application layers. There is also a document that presents the target state as the current one, for example an integration with a directory that does not exist yet.
Good practice: every element on the diagram has one answer to the questions where, why and in which direction. If the answer is not known, the element is marked as an open point for the inventory.
Video
Frequently asked questions
Why does the diagram use the PERA layout?
The PERA model is familiar to OT departments and lets you indicate in which zone the system runs. Levels 0-6 and DMZ 3.5 give a language in which IT and OT can discuss the location of the system.
Do we send the customer the diagram with open points?
No. The customer receives the one-page version, while open points and the self-assessment are in the internal version. Open points are discussed with IT as a separate list.
When is the detailed network model produced?
After the site inventory. Until then the diagram shows the general architecture, and addressing, directory and gate interfaces are set together with the plant's IT team.
Need an architecture diagram for your IT department?
We will prepare a one-page PERA diagram and a list of points for the site inventory, ready to hand over to the IT department.
Let's talk