ISA-95 Manufacturing + critical infrastructure
See how operations data moves, gains context, and creates value.
Explore manufacturing integration or switch to a hyperscale data center to inspect compute, cooling, power, water, BMS, EPMS, DCIM, Kubernetes, and cloud coordination.
01 Interactive architecture
From the machine to the enterprise
Click a node to understand its role. The selected use case is highlighted through every handoff.
02 Hyperscale cooling basis of design
12 MW modular chiller architecture
Select a cooling technology to compare heat paths, equipment ratings, hydraulic conditions, local controls, and N+1 resilience.
Concept-level interview design. Final ratings require site weather, IT-vendor coolant limits, water quality, piping pressure drop, electrical fault studies, local codes, and licensed engineering review.
03 Industrial and critical-infrastructure protocol guide
Choose communication by function and risk
A separate reference for manufacturing and hyperscale data centers. Filter by domain, search a protocol, then inspect its use, transport, ISA-95 placement, and security boundary.
Ports shown are common defaults, not firewall permission rules. Confirm vendor profiles, editions, multicast needs, timing behavior, certificates, segmentation, and local life-safety requirements before deployment.
04 Network and data transport
Match the path to latency, risk and distance
Switch environments and use cases to compare local industrial Ethernet, redundant facility networks, message transport, private WAN, direct cloud links and wireless connectivity.
Transport and application protocol are separate decisions. Fiber or Ethernet carries IP; TCP or UDP provides transport behavior; protocols such as OPC UA, BACnet, Modbus TCP and MQTT define the application exchange.
05 Purdue security architecture
Zones, conduits, trust boundaries
Switch between manufacturing and data-center environments. Select a zone or trace an incident to see how segmentation limits movement without interrupting local protection.
The Purdue model is used here as a defense-in-depth zoning reference. Functional safety, electrical protection, fire/life safety and equipment interlocks remain independent and local even when monitoring data moves upward.
06 Multi-site infrastructure as a service
One operating model, many locations
Trace how containerized applications are built, governed, deployed and observed across cloud regions, manufacturing plants and data centers without moving local control into Kubernetes.
Kubernetes is an application orchestrator, not a PLC, protective relay or safety system. Local equipment controls continue through loss of WAN, cloud, regional services or the enterprise management plane.
07 Common data paths
Trace a real manufacturing use case
Choose a flow to highlight it above, then inspect each handoff below.
08 Edge application stack reference
What runs on an industrial edge computer
Select a layer to see its job, common products, data handoffs, failure effect, and control boundary. These are software roles; one product may cover several roles.
Example products are reference options, not a mandatory bundle. Confirm supported protocols, operating system, hardware resources, licensing, patch policy, offline behavior, cybersecurity approval and vendor lifecycle before selection.
09 Protocols in context
OPC UA and MQTT Sparkplug solve different problems
They complement each other. OPC UA is strong for rich, secure access near equipment. MQTT Sparkplug is strong for distributing current state to many consumers.