The scenarios described in this chapter demonstrate how CitectSCADA can be used to support typical processes found in primary production, utilities delivery, and manufacturing.
In reality, a project will incorporate a combination of the scenarios described here, with a high degree of customization and scalability. However, these examples have been simplified to demonstrate how CitectSCADA can be configured and deployed to meet the specific requirements of a production system.
Every component of a system runs on a single computer. See Standalone system.
Distributed I/O system
CitectSCADA is used to monitor and manage distributed devices that are each connected to remote I/O Servers. See Distributed I/O system.
Redundant server system
One or more of the servers associated with a system are duplicated and defined as primary and standby units, allowing the system to keep running in the event one of the servers becomes inoperative. See Redundant server system.
The servers and clients associated with a system are independently distributed across a number of computers on a network, offering greater accessibility and performance benefits. See Client-Server system
Redundant and distributed control system
Remote or geographically separate sections of a production system have fully operational sub-systems in place that are monitored and controlled locally. If such a sub-system becomes partially or wholly inoperative in a manner preventing local control, this arrangement allows remote Control Clients to take control of the affected sub-system. See Redundant and distributed control system.
Cluster controlled system
A production system is organized into discrete areas being monitored by operators within each area. However, there is also a level of control that supervises every area of the system. See Clustered control system.
Load sharing system
The system splits the load of an otherwise stressed system across multiple machines, better utilizing the available infrastructure. See Load sharing system.