IT/OT architecture of a food plant
Ridgeback Foods’ IT/OT architecture on the Purdue model: corporate IT, an industrial DMZ with five conduits, and one bakery down to its oven burners.
Views in this map
- 1 L4–5 EnterpriseCorporate IT on top, the plants below, and one industrial DMZ between them.
- 2 L3 Plant operationsFresno’s site operations: MES, SCADA, the historian and four production lines.
- 3 IT/OT boundaryFive conduits cross the DMZ, each through both firewalls. Nothing else does.
- 4 L0–2 Oven lineOven line 3 from its HMIs down to the burners, under the plant’s own systems.
L4–5 Enterprise ▸ IT/OT boundary ‹ › L3 Plant operations ▸ L0–2 Oven line
Flows to play
- A production orderFrom SAP to the burners, and back up as a yield report. In the L0–2 Oven line view.
- A vendor sessionThe oven maker fixes a zone fault through one approved, recorded session. In the IT/OT boundary view.
- Oven data to the cloudZone temperatures reach the yield dashboards, one way only. In the L3 Plant operations view.
The model behind it
61 records of 14 types. Every box on the map is one of them, so the filters and the record panel read the same data.
Filters
Purdue level and Vendor: pick a value and everything else fades.
See you in the canvas
Unlock your team’s collaborative super powers.