A plant control system is a network of systems, cabinets, field devices, power sources, and operating locations. A clear system architecture diagram lets engineers review those relationships before cable schedules and interface details are frozen. This practical guide draws on InstrumentationTools' “Design Document for Project Systems Architecture” and uses Foxboro I/A Series hardware as an example.
What the architecture diagram represents
An academic block diagram often describes functional behavior. An industrial systems architecture drawing identifies actual equipment groups, locations, connections, and boundaries at an appropriate level of detail. It is a coordination document, not a substitute for wiring drawings, network designs, safety requirements, or interface specifications.
Represent the DCS, safety instrumented system (SIS), fire and gas system, package PLCs, operator stations, engineering facilities, field I/O, and power distribution as distinct elements wherever they exist. For example, a Foxboro FCP270 field control processor belongs in the DCS control layer, while remote I/O and third-party package interfaces need their own locations and connections.
Cover the locations that matter
Show the main control room, cabinet and auxiliary rooms, engineering areas, field locations, electrical substations, motor-control centers, UPS or battery rooms, offsite links, and project-specific areas such as compressor houses or loading facilities where relevant. Mark the boundary between buildings and field, indicate indoor or outdoor placement, and identify remote I/O sites. The exact scope follows the project's control philosophy and document register; a universal checklist cannot replace them.
Define every interface
Each line should identify its endpoints and reference the detailed interface document. Record the communication or signal type, direction, owner, redundancy where applicable, and any cybersecurity or safety boundary. A Foxboro FBM223 Ethernet communication module illustrates an interface component, but a line on the drawing does not establish its protocol, permitted data flow, or security controls. A Foxboro FBM214B HART input interface illustrates field-device integration and belongs in the appropriate I/O context.
Package-vendor interfaces deserve particular care. Confirm protocol, revision, point list, data quality, time synchronization, failure behavior, and delivery responsibility before purchasing gateways or assigning cable routes.
Show independence honestly
Draw DCS, SIS, and fire and gas functions separately when their independence matters. Identify shared and separate power, networks, cabinets, sensors, final elements, and engineering access. A diagram can reveal a potential common dependency, but it cannot by itself prove functional independence. Verify the actual design against the hazard assessment, safety requirements, electrical drawings, and installed configuration. Do not assume every SIS and F&G implementation must have entirely separate physical resources; document the approved separation and any justified shared services.
Use symbols and titles consistently
Choose a readable symbol for each system type, define every abbreviation in a controlled legend, and show quantities and redundancy explicitly. Two drawn blocks are not proof of a redundant pair unless their function and connections say so. Whether the document register calls it “System Architecture,” “Systems Architecture,” or “Control System Block Diagram,” use one approved title and revision scheme across disciplines.
A practical review sequence
- Compare the drawing with the control philosophy and equipment list; identify missing systems and package units.
- Trace each interface to a named owner, protocol or signal type, and detailed destination document.
- Check equipment locations against the plot plan, room allocation, remote-I/O list, and building boundaries.
- Review SIS, DCS, and fire and gas boundaries for common dependencies and approved data flow.
- Confirm each symbol, abbreviation, quantity, and redundancy note against the legend.
- Trace power sources and UPS-backed loads to the electrical design and documented autonomy requirement.
- Review the sheet jointly with controls, electrical, network, cybersecurity, safety, package, and layout teams as needed.
- Revise and reissue the architecture after approved changes, then reconcile affected cable, network, and interface documents.
Conclusion
The value of a system architecture diagram is not artistic polish. It is a shared, revision-controlled view of where systems live, how they connect, who owns each boundary, and what detailed documents prove the design. Keep the Foxboro DCS, safety systems, field I/O, power, and package interfaces legible and traceable, then test the drawing against the real plant as the project evolves.