OPERATOR CONSOLE WITH DYNAMIC FUTURE REPRESENTATIONS FOR PROCESSING EQUIPMENT
20210389748 · 2021-12-16
Assignee
Inventors
- Rohan James McAdam (Walang, AU)
- Graeme John Laycock (Hunters Hill, AU)
- Berty Jacques Alain Bhuruth (Bankstown, AU)
Cpc classification
Y02P90/80
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
International classification
Abstract
A method includes generating a future state reflecting predicted values for a future time for a plurality of processing equipment for an industrial process run by an industrial process control and automation system (IPCS) configured to control the industrial process including at least one process controller coupled to input output (I/O) modules coupled to field devices including sensors and actuators that are coupled to processing equipment including the plurality of processing equipment. The method includes displaying in a human machine interface (HMI) associated with an operator computing system that is coupled to the process controller a dynamic time-based representation for each of the plurality of the processing equipment including beginning from a time beginning in the past including historical values, a value at a current time, and the predicted value at the future time.
Claims
1. A method comprising: generating a future state reflecting predicted values for a future time for a plurality of processing equipment for an industrial process run by an industrial process control and automation system (IPCS) configured to control the industrial process including at least one process controller coupled to input output (I/O) modules coupled to field devices including sensors and actuators that are coupled to processing equipment including the plurality of processing equipment; displaying in a human machine interface (HMI) associated with an operator computing system that is coupled to the process controller a dynamic time-based representation for each of the plurality of the processing equipment including from a time beginning in the past comprising historical values, a value at a current time, and the predicted value at the future time.
2. The method of claim 1, wherein data for the generating of the future state is obtained from at least one of operations planning systems, maintenance systems, and weather services, and wherein the future state includes at least one projected future event.
3. The method of claim 2, wherein the projected future event comprises at least one of production activities, maintenance activities, weather, and predicted critical alarms associated with a process parameter associated with the plurality of processing equipment.
4. The method of claim 1, wherein a time period from the current time to the future time is adjustable to enable showing a longer or shorter time period measured from the current time to the future time.
5. The method of claim 2, wherein the projected future event also appear on trends to create a visual correlation between information shown in different areas of the HMI.
6. The method of claim 1, wherein the time-based representations comprise a roadway including a plurality of lanes, with one of the lanes for each of the plurality of processing equipment.
7. A non-transitory computer readable medium containing instructions that when executed cause at least one operator console comprising an operator computer system including at least one processor device coupled to a human machine interface (HMI) causes the operator computer system to implement a method comprising: generating a future state reflecting predicted values for a future time for a plurality of processing equipment for an industrial process run by an industrial process control and automation system (IPCS) configured to control the industrial process including at least one process controller coupled to input output (I/O) modules coupled to field devices including sensors and actuators that are coupled to the plurality of processing equipment; displaying in a human machine interface (HMI) associated with an operator computing system that is coupled to the process controller a dynamic time-based representation for each of the plurality of the processing equipment including from a time beginning in the past comprising historical values a value at a current time, and the predicted value at the future time.
8. The computer readable medium of claim 7, wherein data for the generating of the future state is obtained from at least one of operations planning systems, maintenance systems, and weather services, and wherein the future state includes at least one projected future event.
9. The computer readable medium of claim 8, wherein the projected future event comprises at least one of production activities, maintenance activities, weather, and predicted critical alarms from a process parameter associated with the plurality of processing equipment.
10. The computer readable medium of claim 7, wherein a time period from the current time to the future time is adjustable, to enable showing a longer or shorter time period measured from the current time to the future time.
11. The computer readable medium of claim 8, wherein the projected future event also appear on trends to create a visual correlation between information shown in different areas of the HMI.
12. The computer readable medium of claim 7, wherein the time-based representations comprise a roadway including a plurality of lanes, with one of the lanes for each of the plurality of processing equipment.
Description
BRIEF DESCRIPTION OF THE DRAWINGS
[0013]
[0014]
[0015]
[0016]
DETAILED DESCRIPTION
[0017] Disclosed embodiments are described with reference to the attached figures, wherein like reference numerals, are used throughout the figures to designate similar or equivalent elements. The figures are not drawn to scale and they are provided merely to illustrate aspects disclosed herein. Several disclosed aspects are described below with reference to example applications for illustration. It should be understood that numerous specific details, relationships, and methods are set forth to provide a full understanding of the embodiments disclosed herein.
[0018] Also, the terms “coupled to” or “couples with” (and the like) as used herein without further qualification are intended to describe either an indirect or direct electrical connection. Thus, if a first device “couples” to a second device, that connection can be through a direct electrical connection where there are only parasitics in the pathway, or through an indirect electrical connection via intervening items including other devices and connections. For indirect coupling, the intervening item generally does not modify the information of a signal but may adjust its current level, voltage level, and/or power level.
[0019] As used herein an IPCS air's an industrial process involving a tangible material that disclosed embodiments apply. For example, oil and gas, chemical, beverage, pharmaceutical, pulp and paper manufacturing, petroleum processes, electrical power including renewable energy, and water. An IPCS is distinct from a data processing system that only performs data manipulations.
[0020]
[0021] Optional step 103 comprises providing data to the operator computing system that is obtained from at least one of operations planning systems, maintenance systems, and weather services for the generating of the future state, wherein the future state includes at least one projected future event. The projected future events can comprise at least one of production activities, maintenance activities, weather, and predicted critical alarms from the process parameter associated with the processing equipment. If everything is determined to be running smoothly in the process, there may be nothing on the roadway for the time period into the future shown.
[0022]
[0023] The IPCS 200 includes field devices comprising one or more sensors 202a and one or more actuators 202b that are coupled between the controllers 206, 207 and 208 and the processing equipment, shown in simplified form as process unit 201a coupled by piping 209 to process unit 201b. Each of the controllers include a processor and a memory, shown as processor 206a and memory 206b for controller 206. The sensors 202a and actuators 202b represent components in a process system that may perform any of a wide variety of functions. For example, the sensors 202a can measure a wide variety of characteristics in the processing system, such as flow, pressure, or temperature. Also, the actuators 202b can alter a wide variety of characteristics in the processing system, such as valve openings. Each of the sensors 202a includes any suitable structure for measuring one or more characteristics in a process system. Each of the actuators 202b includes any suitable structure for operating on or affecting one or more conditions in an IPCS.
[0024] At least one network 204 is shown providing a coupling between the controllers 206 and the sensors 202a and actuators 202b. The network 204 facilitates controller interaction with the sensors 202a and actuators 202b. For example, the network 204 can transport measurement data from the sensors 202a to the controllers 206-208 and provide control signals from the controllers 206-208 to the actuators 202b. The network 204 can represent any suitable network or combination of networks. As particular examples, the network 204 can represent at least one Ethernet network (such as one supporting a FOUNDATION FIELDBUS protocol), electrical signal network (such as a (Highway Addressable Remote Transducer (HART) network which is a hybrid analog plus digital industrial automation open protocol), pneumatic control signal network, or any other or additional type(s) of network(s).
[0025] The process controllers 206-208 are generally configured in multiple Purdue model levels that may be present at all levels besides level 0, where level 0 generally only includes the field devices (sensors and actuators) and the processing equipment. The process controllers 206-208 can be used in the IPCS 200 to perform various functions in order to control one or more industrial processes.
[0026] For example, a first set of process controllers 206-208 corresponding to level 1 in the Purdue model may refer to smart transmitters or smart flow controllers, where the control logic is embedded in memory associated with these controllers. Level 2 generally refers to a distributed control system (DCS) controller, such as the C300 controller from Honeywell International. These level 2 controllers can also include more advanced strategies including machine level control built into the C300 controller, or another similar controller. Level 3 is generally reserved for controllers implemented by the server 216. These controllers interact with the other level (1, 2 and 4) controllers.
[0027] The level 1 controllers in the case of smart devices, or level 2 controllers such as the C300 controller, may use measurements from one or more sensors 202a to control the operation of one or more actuators 202b. The level 2 process controllers 206 can be used to tune the control logic or other operations performed by the level 1 process controllers. For example, machine-level controllers, such as DCS controllers, at Purdue level 2 can log information collected or generated by process controllers 206 that are on level 1, such as measurement data from the sensors 202a or control signals for the actuators 202b.
[0028] A third set of controllers implemented by the server 216 corresponding to level 3 in the Purdue model, known as unit-level controllers which generally perform MPC control, can be used to perform additional functions. The process controllers 206 and controllers implemented by the server 216 can collectively therefore support a combination of approaches, such as regulatory control, advanced regulatory control, supervisory control, and advanced process control. In one arrangement, the third set of controllers implemented by the server 216 comprises an upper-tier controller corresponding to level 4 in the Purdue model, which generally also performs MPC control, also known as a plant-level controller, coupled to a lower-tier controller corresponding to level 3 in the Purdue model.
[0029] The server 216 is shown including a model process control (MPC) simulation model generally resides in a memory (shown as MPC model 216c stored in memory 216b as shown in
[0030] At least one of the process controllers 206-208 shown in
[0031] At least one network 209 couples the process controllers 206 and other devices in the IPCS 200. The network 209 facilitates the transport of information between to components. The network 209 can represent any suitable network or combination of networks. As particular examples, the network 209 can represent at least one Ethernet network.
[0032] Industrial console operator access to and interaction with the process controllers 206-208 and other components of the system 200 including the server 216 can occur via various disclosed operator consoles 210 which comprise an HMI 210a coupled to an operator computer system 210b. Each operator console 210 can be used to provide information to an industrial console operator and receive information from the operator. For example, each operator console 210 can provide information identifying a current state of an industrial process to the industrial consul operator, such as values of various process variables and warnings, alarms, or other states associated with the industrial process.
[0033] Each operator console 210 can also receive information affecting how the industrial process is controlled, such as by receiving setpoints or control modes for process variables controlled by the process controllers 206-208 or a process controller implemented by the server 216, or other information that alters or affects how the process controllers control the industrial process. Each operator console 210 includes any suitable structure for displaying information to and interacting with an operator. For example, the operator computing device can run a WINDOWS operating system or other operating system.
[0034] Multiple operator consoles 210 can be grouped together and used in one or more control rooms 212. Each control room 212 could include any number of operator consoles 210 in any suitable arrangement. In some embodiments, multiple control rooms 212 can be used to control an industrial plant, such as when each control room 212 contains operator consoles 210 used to manage a discrete part of the industrial plant.
[0035] The IPCS 200 generally includes at least one data historian 214 that generally includes event logs that are entered by operators or technicians, and generally includes at least one server 216. The server 216 is generally in level 3 or 4 in the Purdue model. The processor 216a can comprise a digital signal processor (DSP), a microcontroller, an application specific integrated circuit (ASIC), a general processor, or any other combination of one or more integrated processing devices.
[0036] The data historian 214 represents a component that stores various information about the IPCS 200. The data historian 214 can, for instance, store information that is generated by the various process controllers 206-208 during the control of one or more industrial processes, as well as event logs. The data historian 214 includes any suitable structure for storing and facilitating retrieval of the information it stores. Although shown as a single component here, the data historian 214 can be located elsewhere in the IPCS 200, such as in the cloud, or multiple data historians can be distributed in different locations in the IPCS 200.
[0037] The server's 216 processor 216a executes applications for users (operators) of the operator consoles 210 or other applications. The applications can be used to support various functions for the operator consoles 210, the process controllers 206, or other components of the system 200. Each server 216 can represent a computing device running a WINDOWS operating system or other operating system. Note that while shown as being local within the IPCS 200, the functionality of the server 216 can be remote from the system 200. For instance, the functionality of the server 216 can be implemented in a computing cloud 218, or in a remote server communicatively coupled to the system 200 via a gateway 220.
[0038] Although
[0039] The presentation of future events can have information and guidance associated with them for the operator that further enhances an operator's ability to anticipate and deal with the future course of events to raise their SA. For example, a planned raw material feed switch may have a potentially detrimental effect on the operation of the process when the switch occurs unless the operator takes an appropriate action such as adjusting process flows, temperatures, pressures, to account for differing raw material qualities. A visualization based on an explicit representation of the predicted value at the future time for the production process provided by disclosed aspects makes it easy to see what the planned activity is, what its effect is likely to be, and what the operator may need to do to avoid unnecessary disturbance to the process.
[0040] A disclosed operator console can be constructed by integrating information from a variety of data sources into future-based visualizations for the operator. For example, data from operations planning systems, maintenance systems, and weather services can provide information on planned or expected future events. Predictions of the future evolution of individual process parameters can be provided by model-based predictions, such as those available from MPC algorithms.
EXAMPLES
[0041] Disclosed embodiments of the invention are further illustrated by the following specific Examples, which should not be construed as limiting the scope or content of this Disclosure in any way.
[0042]
[0043] A disclosed “roadway” typically provides a dynamic representation of aggregates of process parameters, such as for major pieces of processing equipment or entire process units. The trends on the left and right provide a view of individual process parameters. The “roadway” shows upcoming events related to the items represented by each lane (a process unit, or a major piece of processing equipment), such as production activities, maintenance activities, weather, and predicted critical alarms from process parameters associated with the equipment/process unit. The detailed view of individual process parameters is shown in the trends rather than the “roadway”. In the primary mode of operation of an HMI associated with a disclosed operator computing system, the operator “travels” down the “roadway” in real-time.
[0044] Objects automatically come into view on the HMI as time passes. Optionally an operator might use a mouse, their voice, or some other interaction mechanism to advance themselves into the future to be able see what is occurring up ahead in time (future time). “Travel” along the roadway with future events as a result brings into view in the distance, reaching the present, and ultimately disappearing from a view “behind” the operator with the passage of time. The “roadway” is only one possible disclosed representation of the future events. Another possible future events representation is a “flight path” representation which allows a three-dimensional (3D) arrangement of information rather than the two-dimensional representation provided by a disclosed “roadway” shown in
[0045] Other HMI elements shown that complement this visualization include time series trends that scroll right to left as time passes with the time=NOW shown at the center of the trend for the feed and for the product. Data points to the left of NOW represent the history of a process parameter up until the present time. Data points to the right of NOW represent the predicted values for the time series into the future. Events that appear on the “roadway” at the bottom of the HMI also appear on the trends that create a strong visual correlation for an operator between the information shown in the different parts of the HMI.
[0046]
[0047] The right hand edge indicates the time at points along the roadway. The left hand edge indicates the weather over time expressed in ° C. There is one lane on the roadway for each major piece of processing equipment (or production process unit). The lane for the process unit currently shown in the HMI (Crude Tower in this case) can be optionally highlighted such as being bolded. The process flow sheet for the process unit currently shown in the HMI in the center of the HMI. Time series trends for key process parameters for the process unit currently shown in the HMI, including predicted future parameter values, are shown to the left and to the right of the process flowsheet as feed trends and product trends, respectively.
[0048] Each lane shows upcoming events for the respective processing equipment/process unit represented by the unit including production activities, Maintenance activities, predicted critical alarms, and periods of equipment/process unit outage (see
[0049] Events on the roadway also appear on the process parameter trends to which they apply to the left and right of the HMI to create a visual correlation. Events on the roadway dynamically “travel” toward the viewer as time passes. As future events approach the current time (NOW) associated information appears adjacent to the event icon (see
[0050] The passage of time represented by the movement of icons on the roadway need not be constant. Icons in the distance may move slower and speed up as they approach the current time to help provide the operator/viewer a sense of motion when the natural time scale of events is relatively slow.
[0051] The operator/viewer may also change the time scale of the roadway. Although
[0052] While various disclosed embodiments have been described above, it should be understood that they have been presented by way of example only, and not as a limitation. Numerous changes to the disclosed embodiments can be made in accordance with the Disclosure herein without departing from the spirit or scope of this Disclosure. Thus, the breadth and scope of this Disclosure should not be limited by any of the above-described embodiments. Rather, the scope of this Disclosure should be defined in accordance with the following claims and their equivalents.