Classifications

• • G—PHYSICS
  • G05—CONTROLLING; REGULATING
  • G05B—CONTROL OR REGULATING SYSTEMS IN GENERAL; FUNCTIONAL ELEMENTS OF SUCH SYSTEMS; MONITORING OR TESTING ARRANGEMENTS FOR SUCH SYSTEMS OR ELEMENTS
  • G05B19/00—Programme-control systems
  • G05B19/02—Programme-control systems electric
  • G05B19/04—Programme control other than numerical control, i.e. in sequence controllers or logic controllers
  • G05B19/042—Programme control other than numerical control, i.e. in sequence controllers or logic controllers using digital processors
  • G05B19/0423—Input/output
• • G—PHYSICS
  • G05—CONTROLLING; REGULATING
  • G05B—CONTROL OR REGULATING SYSTEMS IN GENERAL; FUNCTIONAL ELEMENTS OF SUCH SYSTEMS; MONITORING OR TESTING ARRANGEMENTS FOR SUCH SYSTEMS OR ELEMENTS
  • G05B19/00—Programme-control systems
  • G05B19/02—Programme-control systems electric
  • G05B19/418—Total factory control, i.e. centrally controlling a plurality of machines, e.g. direct or distributed numerical control [DNC], flexible manufacturing systems [FMS], integrated manufacturing systems [IMS] or computer integrated manufacturing [CIM]
  • G05B19/4185—Total factory control, i.e. centrally controlling a plurality of machines, e.g. direct or distributed numerical control [DNC], flexible manufacturing systems [FMS], integrated manufacturing systems [IMS] or computer integrated manufacturing [CIM] characterised by the network communication
  • G05B19/4186—Total factory control, i.e. centrally controlling a plurality of machines, e.g. direct or distributed numerical control [DNC], flexible manufacturing systems [FMS], integrated manufacturing systems [IMS] or computer integrated manufacturing [CIM] characterised by the network communication by protocol, e.g. MAP, TOP
• • G—PHYSICS
  • G06—COMPUTING OR CALCULATING; COUNTING
  • G06F—ELECTRIC DIGITAL DATA PROCESSING
  • G06F11/00—Error detection; Error correction; Monitoring
  • G06F11/07—Responding to the occurrence of a fault, e.g. fault tolerance
  • G06F11/14—Error detection or correction of the data by redundancy in operation
  • G06F11/1479—Generic software techniques for error detection or fault masking
  • G06F11/1482—Generic software techniques for error detection or fault masking by means of middleware or OS functionality
  • G06F11/1484—Generic software techniques for error detection or fault masking by means of middleware or OS functionality involving virtual machines
• • G—PHYSICS
  • G05—CONTROLLING; REGULATING
  • G05B—CONTROL OR REGULATING SYSTEMS IN GENERAL; FUNCTIONAL ELEMENTS OF SUCH SYSTEMS; MONITORING OR TESTING ARRANGEMENTS FOR SUCH SYSTEMS OR ELEMENTS
  • G05B2219/00—Program-control systems
  • G05B2219/10—Plc systems
  • G05B2219/13—Plc programming
  • G05B2219/13144—GUI graphical user interface, icon, function bloc editor, OI operator interface
• • G—PHYSICS
  • G06—COMPUTING OR CALCULATING; COUNTING
  • G06F—ELECTRIC DIGITAL DATA PROCESSING
  • G06F11/00—Error detection; Error correction; Monitoring
  • G06F11/07—Responding to the occurrence of a fault, e.g. fault tolerance
  • G06F11/16—Error detection or correction of the data by redundancy in hardware
  • G06F11/20—Error detection or correction of the data by redundancy in hardware using active fault-masking, e.g. by switching out faulty elements or by switching in spare elements
  • G06F11/202—Error detection or correction of the data by redundancy in hardware using active fault-masking, e.g. by switching out faulty elements or by switching in spare elements where processing functionality is redundant
  • G06F11/2023—Failover techniques
  • G06F11/203—Failover techniques using migration
• • G—PHYSICS
  • G06—COMPUTING OR CALCULATING; COUNTING
  • G06F—ELECTRIC DIGITAL DATA PROCESSING
  • G06F2201/00—Indexing scheme relating to error detection, to error correction, and to monitoring
  • G06F2201/805—Real-time
• • G—PHYSICS
  • G06—COMPUTING OR CALCULATING; COUNTING
  • G06F—ELECTRIC DIGITAL DATA PROCESSING
  • G06F2201/00—Indexing scheme relating to error detection, to error correction, and to monitoring
  • G06F2201/815—Virtual
• • G—PHYSICS
  • G06—COMPUTING OR CALCULATING; COUNTING
  • G06F—ELECTRIC DIGITAL DATA PROCESSING
  • G06F9/00—Arrangements for program control, e.g. control units
  • G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
  • G06F9/46—Multiprogramming arrangements
  • G06F9/48—Program initiating; Program switching, e.g. by interrupt
  • G06F9/4806—Task transfer initiation or dispatching
  • G06F9/4843—Task transfer initiation or dispatching by program, e.g. task dispatcher, supervisor, operating system
  • G06F9/485—Task life-cycle, e.g. stopping, restarting, resuming execution
  • G06F9/4856—Task life-cycle, e.g. stopping, restarting, resuming execution resumption being on a different machine, e.g. task migration, virtual machine migration
• • Y—GENERAL TAGGING OF NEW TECHNOLOGICAL DEVELOPMENTS; GENERAL TAGGING OF CROSS-SECTIONAL TECHNOLOGIES SPANNING OVER SEVERAL SECTIONS OF THE IPC; TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
  • Y02—TECHNOLOGIES OR APPLICATIONS FOR MITIGATION OR ADAPTATION AGAINST CLIMATE CHANGE
  • Y02P—CLIMATE CHANGE MITIGATION TECHNOLOGIES IN THE PRODUCTION OR PROCESSING OF GOODS
  • Y02P90/00—Enabling technologies with a potential contribution to greenhouse gas [GHG] emissions mitigation
  • Y02P90/02—Total factory control, e.g. smart factories, flexible manufacturing systems [FMS] or integrated manufacturing systems [IMS]
• • Y—GENERAL TAGGING OF NEW TECHNOLOGICAL DEVELOPMENTS; GENERAL TAGGING OF CROSS-SECTIONAL TECHNOLOGIES SPANNING OVER SEVERAL SECTIONS OF THE IPC; TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
  • Y02—TECHNOLOGIES OR APPLICATIONS FOR MITIGATION OR ADAPTATION AGAINST CLIMATE CHANGE
  • Y02P—CLIMATE CHANGE MITIGATION TECHNOLOGIES IN THE PRODUCTION OR PROCESSING OF GOODS
  • Y02P90/00—Enabling technologies with a potential contribution to greenhouse gas [GHG] emissions mitigation
  • Y02P90/80—Management or planning

Definitions

• the present disclosure relates generally to process control systems and, more particularly, to methods and apparatus to virtualize a process control system.
• Process control systems like those used in chemical, petroleum or other processes, typically include one or more process controllers and input/output (I/O) devices
• the field devices which may be, for example, valves, valve positioners, switches and transmitters (e.g., temperature, pressure and flow rate sensors), perform process control functions within the process such as opening or closing valves and measuring process control parameters.
• the process controllers receive signals indicative of process measurements made by the field devices, process this information to implement a control routine, and generate control signals that are sent over the buses or other communication lines to the field devices to control the operation of the process. In this manner, the process controllers may execute and coordinate control strategies using the field devices via the buses and/or other communication links communicatively coupling the field devices.
• Process information from the field devices and the controllers may be made available to one or more applications (i.e., software routines, programs, etc.) executed by the operator workstation (e.g., a processor-based system) to enable an operator to perform desired functions with respect to the process, such as viewing the current state of the process (e.g., via a graphical user interface), evaluating the process, modifying the operation of the process (e.g., via a visual object diagram), etc.
• Many process control systems also include one or more application stations. Typically, these application stations are implemented using a personal computer, workstation, or the like that is communicatively coupled to the controllers, operator workstations, and other systems within the process control system via a local area network (LAN).
• Each application station may include a graphical user interface that displays the process control information including values of process variables, values of quality parameters associated with the process, process fault detection information, and/or process status information.
• An example process control system includes a server cluster including one or more servers.
• the server cluster when operating, provides a virtual workstation or virtual server, a virtual controller to interoperate with the virtual workstation or server and to implement process control operations, and a virtual input/output device to interoperate with the virtual controller and coupled to one or more field devices within the process control system.
• Another example process control system a multi-core processing unit.
• the multi-core processing unit when operating, provides a virtual controller to interoperate with a workstation or server and to implement process control operations, and a virtual input/output device to interoperate with the virtual controller and coupled to one or more field devices within the process control system.
• An example method of controlling a process system involves establishing a virtual workstation or virtual server, establishing a virtual controller to interoperate with the virtual workstation or server and to implement process control operations, and establishing a virtual input/device to interoperate with the virtual controller.
• FIG. 1 depicts a known control system architecture.
• FIG. 2 depicts a known control system architecture having a remote portion.
• FIGS. 3A and 3B depict another known control system architecture including fully integrated plant functions.
• FIG. 4 depicts another known control system architecture.
• FIGS. 5A and 5B depict physical aspects of a digital control system.
• FIG. 6 depicts display, control strategy and alarms configuration that may be used with a control system.
• FIG. 7 depicts an example manner of virtualizing workstations and/or servers.
• FIG. 8 depicts an example manner in which a control system may be virtualized.
• FIGS. 9 and 10 depict example architecture that may be used to perform the virtualization shown in FIG. 8.
• FIG. 11 depicts physical aspects of a virtualized control system.
• the example methods and apparatus described herein may be used to virtualize an entire process control environment or system, including such environments or systems employing embedded processing units. More specifically, the example methods and apparatus described herein may provide a process control system architecture that enables workstations, servers, controllers, input/output devices, and field devices to be virtualized via a server cluster having one or more servers. Thus, an entire process control system may be implemented within such a virtualization environment or architecture, thereby significantly increasing the flexibility and robustness of the process control system.
• any of the virtualized portions of the process control system can be easily migrated from one server within the server cluster to another server or servers during operation of the process control system for maintenance purposes, in response to the failure of a server, in response to a need to otherwise shut down a server, a need to balance resources within the server cluster, etc.
• Such migration can occur without any loss of data and without having to interrupt communications between, for example, a virtualized operator interface and other virtualized portions of the process control system such as the input/output devices and/or controllers.
• the servers of the server cluster may be co- located and/or may be in different geographic areas.
• a process control system may be implemented with a server cluster including one or more servers, where the server cluster, when operating, provides a virtual workstation or virtual server, a virtual controller to interoperate with the virtual workstation or server and to implement process control operations, and a virtual input/output device to interoperate with the virtual controller and coupled to one or more field devices within the process control system.
• the virtual workstation may, for example, provide a user interface to the process control system such as an operator interface, a diagnostics interface or a
• the virtual server may, for example, provide a backend service to the process control system such as data storage or collection, a configuration function, a calculation function, or an interface to another system.
• the architecture of the server cluster may employ at least one virtual machine server to interoperate with guest operating systems corresponding to each of the virtual workstation or server, the virtual controller, and the virtual input/output device. Additionally, the architecture may include a storage area network to store data for the guest operating systems. Users may access the virtual workstation or server via a remote desktop service implemented via a personal computer, another workstation, or a thin client device. Further, in addition to virtualizing workstations, servers, controller and I/O devices, the architecture may also be used to virtualize field devices, thereby facilitating simulation and/or any other testing.
• the foregoing example architecture may be extended for use with embedded systems and, alternatively or additionally, the virtual workstation or server, the virtual controller and/or the virtual input/output device may be implemented via one or more multi-core processing units.
• DCSs digital control systems
• FIGS. 1, 2 and 3 a discussion of digital control systems is provided below in connection with FIGS. 1, 2 and 3.
• DCSs are deployed in configurations ranging from a standalone laptop, which is primarily used for focused training and design activities, to multi- zone configurations to control an entire plant.
• a DCS may extend over a wide geographic area with, for example, a portion of the system covering onshore operations and offshore components controlling platforms many kilometers offshore.
• the DCS is integrated with business systems providing real-time access to lab data, scheduling, maintenance systems, etc.
• FIG. 1 illustrates a known control system 100.
• workstations and servers 102 provide a variety of functions including operator interfaces, maintenance, historical data collection, and integration with the plant network.
• users are provided with remote access to the DCS via thin clients 104 using terminal services, for example, via a virtual private network (VPN) connection.
• VPN virtual private network
• portions of the system 100 may be remote from the main control system.
• the network connecting these remote operations may include communication links via an Ethernet backhaul, phone lines, cable, fiber, microwave, and/or satellite. Security, sampling times, and reliability are generally considered for such remote connections.
• FIG. 2 illustrates another known control system 200 with a remote operation.
• the DCS may be fully integrated into the overall plant operation, and it is not uncommon for the DCS, safety systems, burner management, and machine health functions to be integrated.
• FIGS. 3A and 3B illustrate a system 300 with fully integrated plant functions.
• Distributed control systems such as the one shown in FIGS. 3 A and 3B are made of workstations and servers, controllers, input/output devices, field devices, control technology, and applications such as plant data historians. As described in greater detail below, the example system in FIGS. 3 A and 3B may be virtualized by the example methods and apparatus described herein.
• Virtualizing the example system 300 enables, among other tasks, process control personnel to simulate and test system configurations. Further, virtualizing the example system 300 may improve disaster recovery. For example, if resources hosting the virtualized system are located in an area expected to be impacted by a hurricane, other resources in a different location may be used to host the virtualized system, thereby preventing system downtime from the hurricane. Additionally, virtualizing the example system 300 enables system scenarios to be tested prior to a physical system upgrade. [0029] A known process control system architecture 400 is shown in FIG. 4. As shown in FIG. 4, the architecture 400 includes workstations and servers 402 and 404. The workstations 402 may support user interface functions such as an operator interface, diagnostics, and/or configuration. The servers 404 support backend functions such as data collection and storage, configuration, calculations, and interfaces to external systems.
• An operator interface to the process typically includes or involves the workstations 402 and the servers 404, keyboards, mice, and liquid crystal display (LCD) monitors.
• LCD liquid crystal display
• multiple monitors may be used in various arrangements.
• Large LCD monitors may be used to support plant overview displays.
• known operating systems such as Windows Server 2008 and Windows 7 may be utilized because of the broad support available to manufacturers for these systems.
• Equipment that an operator uses to monitor process conditions and manipulate setpoints of the process operation may be located in a central control room or distributed on the plant floor close to the equipment. From these locations, the operator can view information transmitted from the processing area and displayed on operator displays and change control conditions, assuming proper security privileges for the operator, from an input device.
• Operator display applications are typically implemented on a system wide basis in one or more of the workstations 402 and provide preconfigured displays to the operator or
• these displays take the form of alarm summary displays that receive alarms generated by controllers 406 and 408 or devices 410 within the process plant, control displays indicating the operating state of the controllers and other devices within the process plant, maintenance displays indicating the operating state of the devices within the process plant, etc.
• Displays may be created through the use of objects that have an associated graphic.
• the object may animate the graphic on the display screen based on the received data to illustrate, for example, that a tank is half full, to illustrate the flow measured by a flow sensor, etc.
• the information for the displays is sent from the devices or configuration database within the process plant, the information is used to provide a display to the user containing that information.
• all information and programming that is used to generate alarms, detect problems within the plant, etc. may be generated by and configured within the different devices associated with the plant, such as controllers and field devices during configuration of the process plant control system.
• Programming the process control system instructions involves several configuration activities such as physical configuration, control strategy configuration, display configuration, and historical data collection configuration. These activities are generally performed in parallel and then integrated as the process control system is engineered.
• a configuration database enables users (e.g., plant operators) to create and modify control strategies and download these strategies via a control network 412 to the distributed controllers 406 and 408, consoles, and devices 410.
• the control strategies are made up of interconnected function blocks, SFCs, equipment and unit representations, etc that perform functions within the control scheme based on inputs and which provide outputs to other function blocks and/or input/output devices within the control scheme.
• the configuration application also allows a designer to create or change operator interfaces that are used by a viewing application to display data to an operator and to enable the operator to change settings within the process control system.
• Each of the controllers 406 and 408 and, in some cases, field devices 410 stores and executes a controller application that runs the control modules assigned and downloaded to implement actual process control functionality.
• the configuration may be versioned.
• the version and audit trail application records all changes, who made the changes, and when the changes were made.
• a DCS may also include the ability to collect batch, continuous, and event data.
• a centrally defined history database may be available for the storage of historical data. The value of any attribute, alarm of any control strategy, alert, or process condition can be recorded in the history database along with its status.
• the data values are collected as an integrated feature of the system. Events are collected and time stamped at their source. For example, the data may be collected and recorded with a resolution of a few milliseconds. Users and layered applications can retrieve the batch, continuous, and event data in a time-ordered fashion. For security reasons, values may not be edited without leaving behind an audit trail.
• Security is generally a part of a DCS architecture.
• the DCS manages what a user is able to do by user, plant area, unit, and workstation.
• Layered applications may be authenticated before they are allowed access into the system.
• Security within a DCS may involve an authentication process by which access to the DCS for users and layered applications are controlled through the use of password protected user accounts.
• DCS security may also involve user-related aspects such as requiring a user of the DCS to have a user account on the system in order to gain access, naming all user accounts, providing unique names to all user accounts within the scope of a site, and requiring all user accounts to have a password to be provided in conjunction with the account name in order to start a DCS session.
• DCS security may involve plant area security aspects such as permitting or denying access to make changes within zero or more areas within a process control plant based on user account. For each plant area where access is permitted, access can be restricted at runtime according to the classification of the runtime attribute data can be changed. For each plant area where access is permitted, the ability to make configuration changes can be restricted. A user account can also be permitted or denied access to view or modify user account and privilege information. In some systems it is also possible to enable authorization. In these cases, one or more users may confirm by password the changing of certain parameters, starting/stopping a batch, etc.
• Integrated diagnostics may be a feature of a DCS. Such diagnostics may cover the hardware, redundancy, communications, control, and to some extent, the software of the DCS.
• the control network 412 is used to connect the controllers 406 and 408, remote input/output, and the workstations 402 and the servers 404.
• Some DCS systems use proprietary networks. However, these have been largely replaced in most process control systems by inexpensive Ethernet interfaces operating at communication rates of 10Mbps, 100Mbps, and lGbps.
• Segmenting network on the control network is achieved by using switches 414 and 416.
• Standard switches have given way to smart switches with built-in firewall capabilities.
• the control network 412 may include redundant switches, redundant Ethernet cards, and/or redundant network cabling.
• the controllers 406 and 408 are connected to the field devices 410 via analog, digital or combined analog/digital buses.
• the field devices 410 may be, for example, valves, valve positioners, switches and transmitters (e.g., temperature, pressure, level and flow rate sensors), are located within the process environment and perform process functions such as opening or closing valves, measuring process parameters, etc.
• Smart field devices such as the field devices conforming to the input/output bus protocols, may also perform control calculations, alarming functions, and other control functions.
• the controllers 406 and 408 implement control strategies, which read measurements from the field devices 410, perform control functions, and send signals over the communication lines to actuators, motors, etc. to control the operation of the process.
• Information from the field devices 410 and the controllers 406 and 408 is made available over the control network 412 to the operator workstations 402, the data historians 404, report generators, centralized databases, etc.
• These nodes run applications that may, for example, enable an operator to perform functions with respect to the process, such as changing settings of the process control routine, modifying the operation of the control modules within the controllers 406 and 408 or the field devices 410, viewing the current state of the process, viewing alarms generated by the field devices 410 and the controllers 406 and 408, simulating the operation of the process for the purpose of training personnel or testing the process control software, keeping and updating a configuration database, etc.
• One approach that may be used to develop the layout of the control system involves maintaining the input/output devices with the unit and unit operations of the process, for example, locating a chemical reactor and a distillation column in the same physical controller. If this approach is selected, the process remains under control as long as the controller 406, 408 is functioning. To increase the reliability of this scenario, the controller 406, 408 and input/output modules, cards or devices 418 can be made redundant.
• the controllers 406 and 408 are further described in 'Terry Blevins, Mark Nixon. Control Loop Foundation - Batch and Continuous Processes, Research Triangle Park: ISA, 2010,' the entirety of which is incorporated by reference.
• the input/output cards or devices 418 may address a variety of field measurements and actuators.
• Example types of input/output cards or devices include (1) Analog Input (isolated) 1-5 volt DC, 4-20ma, (2) Analog Output 4-20 niA, (3) Isolated RTD input (2, 3, or 4 wire) and Thermocouple Input (B, E, J, K, N, R, S, T ), (4) Discrete Input 24 VDC, 120/230 VAC, (5) Discrete Output 24 VDC, 120/230 VAC, ( 6) Pulse Count Input, and (7) Pulse Duration Output.
• Digital transmitters and actuators may use a variety of available communication protocols and physical interfaces.
• Example communication interface cards include (1) HART AI-Card, 4 to 20 mA, (2) HART AO Card, 4 to 20 mA Series, (3) DeviceNet (Baud rate 125 250 500 kbit/sec), (3) FOUNDATION Fieldbus, (4) AS-Interface, (5) Profibus DP Baud rate (9.6 19.2 93.75 187.5 500 1500 kbit/sec), and (6) Serial Interface (Modbus or Allen Bradley's Data Highway Plus protocol).
• SOE input cards are used to capture process- upset events received directly from devices in the field. Because events are captured and temporarily stored locally on the SOE input card, faster recording for each of the channels on the card is possible. For example, events captured by an SOE input card are time stamped using a 1 ⁇ 4-millisecond resolution.
• Input and output terminations are made at terminals that may be part of the electronic mounting frames or on separate terminal boards.
• terminals may be part of the electronic mounting frames or on separate terminal boards.
• a cable connection between the terminal board and the electronic controller file may be used.
• Connections may be made from the front of the cabinet.
• a separate termination cabinet filled with rows of terminal strips may be used. This alternate approach involves additional wiring from the termination cabinet to the terminals in the remote controller cabinet but enables the field wiring to be completed before the distributed control housings are delivered and installed.
• Analog input and output signals may be conveyed via shielded, twisted pairs of copper wire.
• Digital inputs and outputs either 120 volt AC or 24 volt DC, can be conveyed via twisted pairs, which do not have to be shielded.
• Analog signals may not be run in proximity to alternating current wiring.
• Many controllers are configured to process 1 to 5 volt direct current (DC) signals.
• DC direct current
• one often used input is a 4 to 20 mA current signal, which develops a 1 to 5 volt input across a 250 ohm resistor mounted on the input terminal board.
• Some distributed control systems can accept low-level signals from RTDs and thermocouples and perform signal amplification in their input electronic circuitry.
• Some systems can accept pulse input with frequencies sufficiently high to allow signals from turbine flow meters to be used directly.
• Separate terminal boards may also be supplied for digital input and output signals. Optical isolation for these signals may be provided.
• a DC input signal (or a rectified alternating current (AC) input signal) causes a light emitting diode (LED) in the isolating relay to be energized.
• a photoelectric device energized from the LED actuates a transistor in transistor- transistor logic (TTL) input circuitry to signal a digital input.
• a digital output signal is similarly isolated to actuate a transistor driver circuit for DC outputs or a triac for AC outputs.
• the solid- state relay from which the output is generated functions similar to a dry contact, and the output is powered from a separate power source.
• the requirements for redundancy and interfacing for input/output processing may result in a custom hardware design for the process controller(s). Multiple processors are often used to address the communication and input/output processing and control execution. Also, a real-time operating system for embedded applications may be used to provide deterministic scheduling and execution of control systems.
• the term “devices” may collectively refer to transmitters such flow meters and final control elements such as valves. Smart devices provide both measurement data and diagnostic information.
• the diagnostic information can be used to monitor the health of the device, and to some extent, the health of the process that the devices are monitoring. To enable the entire system to run reliably, the information may be monitored on a continuous basis.
• Devices with a control bus interface can be connected directly to the control bus. Such devices include flow computers, gas chromatographs, anti-surge control systems and other complex field devices. Alternatively, field buses may be used. Devices with field bus capabilities can be connected by means of a DCS controller or a linking device (Gateway). Field buses include Foundation Fieldbus HI , HART, Profibus, and ASi (Actuator Sensor interface).
• the configuration before it is deployed on the actual equipment.
• Various techniques have been used to achieve such testing.
• the configuration may be tested on a virtual or simulated controller.
• such testing results in a substantial amount of additional work and may not test the overall performance of the system due to the very limited nature of the virtualization.
• To simulate the process dynamics several forms of dynamic process simulations have been used. For the majority of cases it is possible to use specially configured control strategies to represent the process. These process simulations can be run in controllers or in virtual controllers that are part of the application/integration stations.
• the example apparatus and methods to virtualize process control systems described herein may be employed without changing the core functions and features of a process control system. Instead, the example apparatus and methods described herein may be used to implement a process control system architecture that separates the functions and features from the underlying hardware. In doing so, the example apparatus and methods described herein and the DCS architecture provided thereby, enables an entire control system, or a portion of the control system, to be implemented (e.g., run) on a single server or a cluster of servers.
• FIGS. 7, 8, 9 and 10 An example architecture implemented in accordance with the example methods and apparatus described herein is illustrated in FIGS. 7, 8, 9 and 10.
• virtualization enables a guest operating system, or multiple guest operating systems, to operate on a cluster of servers.
• the virtualized process control system or environment combines a collection of infrustructure components such as central processing units (CPUs), storage, and networking into a seamless and dynamic operating environment.
• the virtulized system or environment includes infrastructure services, which abstract, aggregate, and allocate hardware and infrastructure resources such as CPUs, memory, storage, and networking.
• the virtualized system or environment also includes application services, which ensure availability, security, and scalability for applications.
• the virtualized system or environment further includes management services, which provides a single point of control for the virtualized environment.
• Virtualization techniques that may be applied or adapted to implement the example architecture described herein are generally described in ' VMware, Introduction to VMware vSphere, Palo Alto, CA, 2009,' and 'VMware, ESXi Installable and vCenter Server Setup Guide, Palo Alto, CA, 2009,' the entirety of which is incorporated by reference.
• FIG. 7 illustrates an example manner of virtualizing workstations and/or servers 700 into a single host computer 702.
• a plurality of thin clients 704 may be communicatively coupled to the host computer 702 via a LAN.
• software708 within the host computer 702 is structured to provide a virtual machine server layer 710 interposing virtual workstations 712 and operating system 714 and hardware 716 layers.
• Each of the virtual workstations 712 includes an encapsulated application and operating system within which the application is to be executed.
• the workstations 700 may be consolidated to operate within a single host computer (e.g., the computer 702).
• FIG. 8 depicts an example manner in which a control system 800 may be virtualized.
• Virtualization of input/output devices 802 is depicted in the system corresponding to reference 804.
• Controllers 806 may additionally or alternatively be virtualized as depicted in the system corresponding to reference 808.
• workstations 810 may additionally or alternatively be virtualized as depicted in the system coressponding to reference 812.
• field devices may undley or additionally be virtualized in a similar manner.
• the various software layers resulting from virtualization of the input/output devices 802, the controllers 806 and the workstations 810 are depicted in the block corresponding to reference 814.
• FIGS. 9 and 10 The architecture for the virtualized environment of FIG. 8 is further illustated in FIGS. 9 and 10.
• virtual workstations or servers 900 run on a cluster of physical servers 902 having one or more servers.
• a storage area network 904 provides common storage for the guest operating systems which are running on the cluster of physical servers 902.
• the cluster of servers 902 provides an environment in which guest workstations or virtual desktops 906 such as operator stations and configuration stations and guest servers or the virtualized servers 900 (such as the PROPlus and Application Station) may be executed.
• Users may access servers and clients through remote desktop services 908, which may be lauched from a users laptop, workstation, or thin client device.
• the cluster 902 may also be used to store images, which may be streamed out to physical desktops 910. In this case the cluster 902 may be used to manage physical images that are stored on physical hard drives.
• controllers 912 and CIOCs 914 may also be virtualized. In this case, the controllers and CIOC's are virtualized and run on the cluster 902 and, when run in Fault Tolerant (FT) mode, provide same reliability as when run in dedicated hardware.
• FT Fault Tolerant
• FIG. 11 depicts physical aspects of a virtualized control system.
• a hierarchical arrangement of clustered severs 1100, an active directory and domain controller 1102, a workstation 1104, virtual machine software 1106 and workstation templates 1108 are depicted.
• an infrastructure bus may be used to synchronize distributed systems, controllers, and/or other distributed process control components.
• the example methods and apparatus described herein may use asynchronous and/or synchronous memory state and/or data state transfers. For example, to transfer operation of one set of controllers to another set of controllers, a disk and/or memory state of the controllers may be transmitted asynchronous initially. Then, after the initial disk and/or memory transfer, the set of controllers may transfer the remaining disk and/or memory state synchronously using any optimization routine to reduce total amount of data transferred and/or to reduce transfer times.
• the example methods and apparatus described herein may route traffic to the second set of controllers, stop the first set of controllers and transfer the remaining memory and/or disk state to the second set.
• the methods and apparatus described herein may use redundant systems, controllers, and/or other distributed process control components to transfer processes.
• a redundant back plane may be utilized by a virtualized switch so that any process may be substantially seamlessly transferred between systems, controllers, and/or other distributed process control components as computing loads and/or client requirements change.
• Multi-core technology allows chip manufactures to increase computational capacity without having to increase clock speeds, which would increase heat, radio
• Such multi-core technology may be used to leverage virtualization.
• a hypervisor may execute on the hardware to enable multiple guest operating systems to use the hardware capabilities.
• Such benefits include extended system life that minimizes upgrades due to hardware and software obsolescence, simplified migrations that reduces disruption of system upgrades and minimizes installation and maintenance costs, increased system availability including availability during maintenance and backups, increased system performance due to maximized resource utilization and scalability, improved maintenance and support due to easy patch management and security updates as well as easy remote software support.
• the benefits of the example methods and apparatus described herein further include cost effective workstation deployment due to maximum utilization of computing resources and lower hardware and installation costs; lower maintenance costs due to centralized back-up and storage, easy virus protection operating system updates, and easy process control system software upgrades; improved availability due to redundant computing and data storage for critical applications and fast recovery from workstation failures; improved security due to an additional security level to limit access and provide audit and control; quicker response to threat situations; improved flexibility due to more flexible training and development systems, reduced hardware required for FAT and reduced project schedule with parallel FAT and site input/output checkout; improved support due to non-intrusive remote maintenance and troubleshooting; improved packaging as controllers can be packaged together as a cluster without having to run input/output to individual controllers; reduced engineering costs due to the ability to move control strategies between controllers without having to retest large portions of the control strategy; improved availability because clustered controllers and input/output servers can be moved between available controller and input/output computing platforms without loss of access to the system; simplified FAT because any controller loading problems can

Landscapes

• Engineering & Computer Science (AREA)
• Theoretical Computer Science (AREA)
• Physics & Mathematics (AREA)
• General Physics & Mathematics (AREA)
• Quality & Reliability (AREA)
• General Engineering & Computer Science (AREA)
• Automation & Control Theory (AREA)
• Manufacturing & Machinery (AREA)
• Testing And Monitoring For Control Systems (AREA)
• Hardware Redundancy (AREA)

Priority Applications (6)

Applications Claiming Priority (2)

Related Child Applications (2)

Publications (1)

Family

ID=44764235

Family Applications (1)

Country Status (6)

Cited By (17)

Families Citing this family (28)

Citations (2)

Family Cites Families (51)

• 2011
  • 2011-09-27 US US15/517,891 patent/US11320797B2/en active Active
  • 2011-09-27 JP JP2013531724A patent/JP2013540317A/ja active Pending
  • 2011-09-27 GB GB1305343.4A patent/GB2498659B/en active Active
  • 2011-09-27 DE DE112011103241T patent/DE112011103241T5/de active Pending
  • 2011-09-27 CN CN201180056199.4A patent/CN103238143B/zh active Active
  • 2011-09-27 WO PCT/US2011/053467 patent/WO2012047654A1/en not_active Ceased
• 2016
  • 2016-09-26 JP JP2016187112A patent/JP6461062B2/ja active Active
• 2022
  • 2022-05-02 US US17/734,751 patent/US20220260961A1/en not_active Abandoned

Patent Citations (2)

Non-Patent Citations (6)

Also Published As

Similar Documents

Legal Events