Systems and methods for implementing standard operating procedures in graphical display configurations

Abstract

To provide a system for and a method of generating a SOP object to implement the SOP object.SOLUTION: A SOP object may have (a) a first element corresponding to description for use in implementing one or more steps of a SOP, (b) a second element corresponding to a link to process control data associated with a first process control element included in an operation environment of a process plant for receiving a real-time data corresponding to a process controlled in the process plant, and (c) a layout for defining visual expression of the first and second elements.SELECTED DRAWING: Figure 2B

Description

[Technical Field]

[0001] FIELD OF THE DISCLOSURE The present disclosure relates generally to process control systems and, more particularly, to systems and methods for implementing standard operating procedures (SOPs) in graphical display configurations. [Background technology]

[0002] Distributed process control systems are used in chemical, pharmaceutical, petroleum, oil and gas, metals and mining, pulp and paper, or other types of industrial process plants to generate or produce one or more physical products from raw materials and / or other types of source materials by controlling one or more industrial processes. As such, a distributed process control system typically includes one or more process controllers and input / output (I / O) devices communicatively coupled to at least one host or operator interface device and one or more field devices via an analog, digital, or combination analog / digital bus or via a wireless communication link or network. Field devices, which may be, for example, valves, valve positioners, switches, and transmitters (e.g., temperature, pressure, level, and flow sensors), are located within the process environment and generally perform physical or process control functions, such as opening and closing valves or measuring process parameters, to control one or more industrial processes running within the process plant or system. Smart field devices, such as field devices conforming to the well-known Fieldbus protocol, may also perform control calculations, alarm functions, and other control functions typically implemented within a controller. A process controller, also typically located within a plant environment, receives signals indicative of process measurements made by sensors or field devices and / or other information regarding the field devices, e.g., makes process control decisions, generates control signals based on the received information, and communicates with HART (登録商標) , WirelessHART (登録商標) , and FOUNDATION(登録商標) A controller application executes a controller application that executes different control modules that interface with control modules or blocks implemented in field devices, such as Fieldbus field devices. The control modules in the controller send control signals over communication lines or links to the field devices, thereby controlling the operation of at least a portion of the process plant or system.

[0003] Information from field devices and controllers is typically made available via data highways to one or more other hardware devices, such as operator interfaces, personal computers or computing devices, data historians, report generators, centralized databases, or other centralized computing devices, which are typically located in a control room or other location away from the more hostile plant environment. Each of these hardware devices is typically, but not always, centralized across the process plant or across portions of the process plant. These hardware devices run applications that may enable operators to, for example, view the current status and operation of processes running within the plant, change settings of process control routines, modify the operation of control modules in controllers or field devices, view alarms generated by field devices and controllers, simulate the operation of processes for purposes of training personnel or testing process control software, maintain and update configuration databases, and perform other functions related to the control of the process and / or the operation of the process plant. The data highways utilized by the hardware devices, controllers, and field devices may include wired communication paths, wireless communication paths, or a combination of wired and wireless communication paths.

[0004] As an example, the DeltaV™ control system sold by Emerson Automation Solutions includes multiple applications stored in and executed by different user interface devices located at various locations within a process plant, and in some cases remotely from the process plant. Each of these applications provides a user interface (UI) that allows a user (e.g., a configuration engineer, an operator, a maintenance technician, etc.) to view and / or modify aspects of the operation and configuration of the process plant. Throughout this specification, the phrase “user interface” or “UI” is used to refer to an application or screen that allows a user to view or modify the configuration, operation, or status of the process plant. Similarly, the phrase “user interface device” or “UI device” is used herein to refer to the device on which the user interface is running, regardless of whether the device is fixed (e.g., a workstation, a wall-mounted display, a process control device display, etc.) or mobile (e.g., a laptop computer, a tablet computer, a smartphone, etc.).

[0005] Configuration applications, resident on one or more user workstations or computing devices included in the configuration environment of the process plant, operate in the operating environment of the process plant and enable configuration engineers and / or other types of users to create or modify process control modules and download these process control modules over data highways to dedicated distributed controllers that control one or more processes during run-time or real-time operation. The configuration environment of a process control system is considered to be the "offline" or "back-end" environment of the process control system, and the operating environment of a process control system is considered to be the "operational," "online," "front-end," or "field" environment of the process control system.

[0006] Typically, these control modules are made up of communicatively interconnected function blocks that perform functions within a control scheme based on inputs thereto and provide outputs to other function blocks in the control scheme. Each dedicated controller, and possibly one or more field devices, stores and executes a respective controller application that runs the control modules assigned to and downloaded thereto to implement the actual process control functions.

[0007] The configuration application also enables configuration engineers and / or other users to create or modify operator human-machine interfaces (HMIs) or display views used by operator applications to display data (e.g., as data is generated in real time during runtime operation of the process plant) and enable operators to change various settings, such as set points, within process control routines during runtime operation. The operator applications providing the operator HMIs or display views execute on one or more UI devices (e.g., operator workstations, operator tablets, operator mobile devices, etc.) included in the process plant's operating environment (or on one or more remote computing devices in communicative communication with the operator workstations and data highways). The operator HMIs or display views receive data from the controller applications via the data highway and display this data to operators or other users using the UI of the UI devices. Similarly, the operator HMIs or display views can also receive data (e.g., real-time data) from other control components or elements included in the process plant's operating environment other than control modules, such as controllers, process controllers, field devices, I / O cards or devices, other types of hardware devices, units, and areas. While the data historian application is typically stored and executed on a data historian device that collects and stores some or all of the data provided over the data highway, the configuration database application may execute on yet another computer connected to the data highway to store the current process control routine configuration, the current operator display configuration, and associated data. Alternatively, the configuration database may be located in the same workstation as the configuration application.

[0008] As described above, operator applications typically execute on one or more of the operator UI devices and provide operators or maintenance personnel with operator HMI or display views regarding the operational status of control systems, control components, and / or devices within a plant, for example, while the plant is operating in real time or run time to control one or more industrial processes. Generally speaking, operator HMIs or display views are used by operators in the day-to-day operation (which may be, for example, 24 / 7 operation) of processes running in the process plant to view and respond to real-time conditions within the process plant and / or process plant. At least some of these operator HMIs or display views may take the form of, for example, alarm displays that receive alarms generated by controllers or devices within the process plant, control displays that show the operational status of controllers and other devices within the process plant, maintenance displays that show the operational status of devices within the process plant, etc. Display views typically execute in the process plant's run time or real-time operating environment and are generally configured to present information or data received from process control modules, function blocks, and / or devices also operating within the process plant's run time or real-time operating environment, in a known manner. In some known systems, display views are associated with physical or logical process control elements included in the operating environment, communicatively coupled to receive data regarding the physical or logical process control elements, and have graphical elements (e.g., graphical representations or graphics) that are updated over time, for example, during runtime operation of the process plant. The graphical elements dynamically change their appearance on the display screen based on the received data, and may be configured or defined to, for example, indicate that a tank is half full, indicate the flow rate measured by a flow sensor, etc.Thus, as the data provided by the physical or logical process control elements within the process plant operating environment changes over time (e.g., is repeatedly or continuously updated over time), the appearance of the corresponding graphical elements changes accordingly on the display screen.

[0009] A standard operating procedure (SOP) refers to a step-by-step description or instruction of tasks to be performed in a specific situation, such as starting / stopping a unit or field device, starting up / shutting down a plant, or repairing or replacing a field device. SOPs are typically used during process plant runtime or in critical situations where procedures must be followed precisely in a real-time operating environment to avoid production loss or safety hazards. SOPs may be established by standardization organizations, such as the International Organization for Standardization (ISO), which specifies quality control standards for process plants to consistently deliver products and services that meet customer and regulatory requirements. One such standard, ISO 9001, requires the documentation of all operating procedures used in any process that may affect product quality.

[0010] Traditionally, SOPs are documented on paper (i.e., non-electronic media) and operators print, read, and follow them as needed. Paper SOP documents typically provide instructions that require operators to look away from the paper SOP document to check specific data on the operator HMI and / or perform a task within the process plant, then return to the paper SOP document to proceed with subsequent instructions. As a result, operators can easily lose their place in the paper SOP document as they switch back and forth between the paper SOP document and the operator HMI or unit or field device. Operators can misread process control data from the wrong operator HMI or perform the wrong task, potentially causing errors with disastrous process control consequences. As process industries face talent loss due to retirement, mistakes like these are likely to become more common. Summary of the Invention

[0011] The graphical display configurations and SOP display systems and methods described herein provide an interactive SOP display view that embeds process control information along with descriptions of instructions for implementing steps of an SOP in the same display view, allowing an operator to seamlessly view SOP instructions and process control information for executing those SOP instructions. The interactive SOP display view may include one or more different types of process control information. For example, the process control information includes data elements linked to process control data received from process control modules, function blocks, and / or devices operating within the runtime or real-time operating environment of the process plant. As another example, the process control information includes graphical elements that are associated with physical or logical process control elements and communicatively coupled to the physical or logical process control elements included in the operating environment to receive data regarding the physical or logical process control elements and update it over time, e.g., during runtime operation of the process plant, and / or send signals to the physical or logical process control elements to act on the physical or logical process control elements, e.g., during runtime operation of the process plant. In yet another example, the process control information includes both data elements and graphical elements. By using an interactive SOP display view that has process control information embedded along with instructional descriptions for implementing the steps of the SOP, an operator does not need to navigate away from the interactive SOP display view because the process control information that would otherwise be found on a dedicated operator HMI is readily available on the SOP display view. Consequently, and advantageously, the interactive SOP display view provides the operator with a more seamless user experience when implementing the SOP, reducing mistakes and enhancing understanding that the SOP instructions are being properly followed. Other features and advantages will become apparent to those skilled in the art from the following detailed description, which takes reference to the accompanying drawings and appended claims.

[0012] The graphical display configuration and SOP display system and method disclosed herein provide an SOP display system for executing an SOP object to render an interactive SOP display view on a display. The SOP display system includes a memory configured to store the SOP object. The interactive SOP display view may include one or more elements of various types. For example, the SOP object may include: (a) a first element corresponding to a description for performing one or more steps of the SOP when monitoring or controlling the process plant; (b) a second element corresponding to a link to process control data associated with a first process control element included in the operating environment of the process plant to receive real-time data corresponding to a process being controlled within the process plant; and (c) a layout defining a visual representation of the first element and the second element. The SOP display system further includes a display interface application including computer-executable instructions stored in the memory. The computer-executable instructions cause one or more processors to receive an SOP object from memory and execute the SOP object to cause a first element and a second element to be presented on a display according to a layout, and to cause an indication of process control data associated with the first process control element executing within an operating environment of the process plant to be presented on the display by the second element.

[0013] As another example, an SOP object includes (a) a first element corresponding to a description for performing one or more steps of the SOP when monitoring or controlling the process plant, (b) a second element corresponding to a process control function associated with a first process control element included in the process plant's operating environment to affect a process being controlled within the process plant, and (c) a layout defining a visual representation of the first element and the second element. The SOP display system includes a display interface application including computer-executable instructions stored in memory that cause one or more processors to receive the SOP object from the memory and execute the SOP object to present the first element and the second element on a display according to the layout and, upon selection of the second element, affect the first process control element executing within the process plant's operating environment.

[0014] The graphical display configuration and SOP display systems and methods disclosed herein also provide a configuration system for configuring SOP objects, such as any of the SOP objects described above. The configuration system includes a configuration application that includes computer-executable instructions stored in one or more tangible, non-transitory memories. The computer-executable instructions cause one or more processors to (a) receive first information regarding a description for implementing one or more steps of the SOP when monitoring or controlling the process plant, (b) create a first element defining the description, (c) receive second information regarding process control data associated with a first process control element included in the operating environment of the process plant, (d) create a second element defining a link to the process control data, (e) receive third information regarding a layout defining a visual representation of the first element and the second element, and (f) configure an SOP object according to the first element, the second element, and the layout such that, upon execution of the SOP object, the first element and the second element are presented on a display according to the layout and an indication of the process control data associated with the first process control element executing in the operating environment of the process plant is presented by the second element on the display. The configuration system includes a database configured to store the SOP object.

[0015] The graphical display arrangement and SOP display system and method disclosed herein also provide a maintenance system for executing an SOP object, such as any of the SOP objects described above. The maintenance system includes a database configured to store a plurality of SOP objects, each of the SOP objects including: (a) an identifier; (b) a first element corresponding to a description for performing one or more steps of the SOP when monitoring or controlling the process plant; (c) a second element corresponding to a link to process control data associated with a first process control element included in the operating environment of the process plant to receive real-time data corresponding to a process being controlled within the process plant; and (d) a layout defining a visual representation of the first element and the second element. The maintenance system also includes a maintenance application including computer-executable instructions stored in a memory. The computer-executable instructions cause one or more processors to (a) receive instructions to retrieve one of a plurality of SOP objects from a database; (b) retrieve the SOP object from among the plurality of SOP objects having an identifier that matches the instructions; and (c) execute the retrieved SOP object to cause a first element and a second element to be presented on a display according to a layout, and to cause an indication of process control data associated with the first process control element executing within an operating environment of the process plant to be presented on the display by the second element.

[0016] The graphical display configurations and SOP display systems and methods disclosed herein also provide a computer-implemented method for executing an SOP object, such as any of the SOP objects described above, including: (a) receiving, by one or more processors, an SOP object stored in memory, the SOP object comprising: a first element corresponding to a description for performing one or more steps of the SOP when monitoring or controlling the process plant; a second element corresponding to a link to process control data associated with a first process control element included in the operating environment of the process plant for receiving real-time data corresponding to a process being controlled within the process plant; and a layout defining a visual representation of the first element and the second element; and (b) executing, by the one or more processors, the SOP object to cause the first element and the second element to be presented on a display in accordance with the layout, and to cause an indication of the process control data associated with the first process control element executing within the operating environment of the process plant to be presented on the display by the second element. [Brief explanation of the drawings]

[0017] [Figure 1] FIG. 1 is a block diagram of a distributed process control network located within a process plant including the graphics configuration and SOP display system and method of the present disclosure. [Figure 2A] 1 depicts an operator application for presenting an exemplary interactive SOP display view within a display screen of a user interface device, such as the interface device shown in FIG. [Figure 2B] 1 depicts an operator application for presenting an exemplary interactive SOP display view within a display screen of a user interface device, such as the interface device shown in FIG. [Figure 2C]1 depicts an operator application for presenting an exemplary interactive SOP display view within a display screen of a user interface device, such as the interface device shown in FIG. [Figure 3] FIG. 2 is a block diagram of an SOP object, the execution of which presents an interactive SOP display view, such as the exemplary interactive SOP display views shown in FIGS. 2A-2C. [Figure 4] FIG. 4 is a block diagram of an example implementation of a graphical display composition system in a composition environment used to generate an SOP object such as the SOP object shown in FIG. [Figure 5] 1 is a flow diagram of an exemplary method for generating an SOP object. [Figure 6] FIG. 2 is a block diagram of an example implementation of a graphical display configuration and SOP display system in a configuration environment and an operating environment of a process plant, such as the process plant of FIG. 1 . [Figure 7] FIG. 2 is a block diagram of the exemplary user interface device shown generally in FIG. 1. DETAILED DESCRIPTION OF THE INVENTION

[0018] 1 is a block diagram of an exemplary process control network or system 2 operating within a process control system or process plant 10, in which a graphical display configuration and SOP display system may be used to provide interactive SOP display views. The process control network or system 2 may include a network backbone 5 that provides direct or indirect connectivity between various devices. The devices coupled to the network backbone 5 include one or more access points 7a, one or more gateways 7b to other process plants (e.g., via an intranet or enterprise wide area network), one or more gateways 7c to external systems (e.g., the Internet), one or more user interface (UI) devices 8, which may be fixed (e.g., traditional operator workstations) or mobile computing devices (e.g., mobile device smartphones), one or more servers 12 (which may be implemented, for example, as a bank of servers, a cloud computing system, or another suitable configuration), databases 13-14, a controller 11, input / output (I / O) cards 26 and 28, wired field devices 15-22, a wireless gateway 35, and a wireless communication network 70. The communication network 70 may include wireless devices 40-58, including wireless field devices 40-46, wireless adapters 52a and 52b, access points 55a and 55b, and a router 58. The wireless adapters 52a and 52b may be connected to non-wireless field devices 48 and 50, respectively. While FIG. 1 depicts only one of several devices connected to the network backbone 5, it should be understood that each of the devices may have multiple instances on the network backbone 5, and in fact, the process plant 10 may include multiple network backbones 5.

[0019] 1 , the UI device 8 may be communicatively connected to the controller 11 and the wireless gateway 35 via the network backbone 5. As part of the distributed process control system 3, the controller 11 may be communicatively connected to the wired field devices 15-22 via input / output (I / O) cards 26 and 28, and may be communicatively connected to the wireless field devices 40-46 via the network backbone 5 and the wireless gateway 35. The controller 11 may operate to implement a batch process or a continuous process using at least some of the field devices 15-22 and 40-46. As an example, the DeltaV sold by Emerson Automation Solutions may be used. (商標) The controller 11 may be a controller, communicatively connected to the process control network backbone 5. The controller 11 may also be connected to, for example, standard 4-20 mA devices, I / O cards 26, 28, and / or FOUNDATION (登録商標) Fieldbus protocol, HART (登録商標) Protocol, Wireless HART (登録商標) The controller 11 may be communicatively coupled to the field devices 15-22 and 40-46 using any desired hardware and software associated with any smart communication protocol, such as the IEEE 802.11a protocol. As shown in Figure 1, the controller 11, the field devices 15-22, and the I / O cards 26, 28 are wired devices, while the field devices 40-46 are wireless field devices. The controller 11 may include a processor 30, a memory 32, and one or more control routines 38.

[0020] The historian database 14 may be connected to the network backbone 5 and operates to collect and store process control data (e.g., process variables, process parameters, status, and other suitable process control data) associated with the controller 11, the field devices 15-22 and 40-46, and any other devices within the plant 10. During operation of the process plant 10, the historian database 14 may receive process control data from the controller 11 and indirectly from the field devices 15-22 and 40-46 via the network backbone 5. The data historian 14 may also store events, alarms, comments, and courses of action taken by operators while monitoring various devices within the plant 10. The events, alarms, and comments may relate to individual devices (e.g., valves, transmitters), communication links (e.g., wired Fieldbus segments, WirelessHART communication links), or process control functions (e.g., a PI control loop for maintaining a desired temperature setpoint).

[0021] The configuration database 13 stores the current configuration of the distributed control system 3 in the plant 10, as downloaded to and stored in the controller 11 and the field devices 15-22 and 40-46. The configuration database 13 stores process control functions that define one or more control strategies for the distributed control system 3, configuration parameters for the devices 15-22 and 40-46, assignments of the devices 15-22 and 40-46 to process control functions, device names, device tags, data format information (e.g., scaling information, unit types, etc.), which variables are associated with each control loop, and other configuration data related to the process plant 10. As described further below, the configuration database 13 may store SOP objects associated with various interactive SOP display views that can reference configuration parameters, process control functions, and other suitable configuration data. Some of the stored SOP objects may correspond to process control functions (e.g., a process graphic developed for a particular PID loop), while other SOP objects may be device-specific (e.g., a graphic corresponding to a pressure sensor).

[0022] Each of databases 13-14 can be any desired type of data storage or collection unit having any desired type of memory and any desired or known software, hardware, or firmware for storing data. Of course, databases 13-14 need not reside in separate physical devices. Thus, databases 13-14 can be implemented on a shared data processor and memory. In general, more or fewer databases can be utilized to store the data collectively stored and managed by databases 13-14 in the exemplary system of FIG. 1 .

[0023] The controller 11 implements control strategies using what are generally referred to as function blocks, each of which is an object or other portion (e.g., a subroutine) of an overall control routine and operates in cooperation with other function blocks (through communications called links) to implement process control loops within the process control system. Control-based function blocks typically perform one of the following functions: input functions associated with transmitters, sensors, or other process parameter measurement devices; control functions associated with control routines that implement control such as PID, fuzzy logic, etc.; or output functions that control the operation of some device, such as a valve, to perform some physical function within the process control system. Of course, hybrid and other types of function blocks exist. The function blocks may have graphical representations provided in the UI device 8, allowing a user to easily monitor the inputs / outputs associated with each of the function blocks implemented in the process control system. The function blocks may be stored within and executed by the controller 11, which is typically the case when these function blocks are used for or associated with certain types of smart field devices, such as standard 4-20 mA devices and HART devices, or the function blocks may be stored within and implemented by the field device itself, which may be the case for Fieldbus devices. The controller 11 may include one or more control routines 38 that may implement one or more control loops. Each control loop, typically referred to as a control module, may be implemented by executing one or more function blocks.

[0024] The processor 30 of the controller 11 implements or oversees one or more process control routines 38 (stored in memory 32), which may include control loops. The processor 30 may communicate with the field devices 15-22 and 40-46, as well as other nodes communicatively connected to the backbone 5. Note that any control routines or modules described herein may be implemented or executed in part by different controllers or other devices, if so desired. Similarly, the control routines or modules described herein implemented within the process control system may take any form, including software, firmware, hardware, etc. The control routines may be implemented in any desired software format, such as using object-oriented programming, ladder logic, sequential function charts, function block diagrams, or any other software programming language or design paradigm. In particular, the control routines may be implemented by a user through the UI device 8. The control routines may be stored in any desired type of memory, such as random access memory (RAM) or read-only memory (ROM). Similarly, the control routines may be hard-coded, for example, in one or more EPROMs, EEPROMs, application specific integrated circuits (ASICs), or any other hardware or firmware elements. Thus, controller 11 may be configured (e.g., by a user using UI device 8) to implement control strategies or control routines in any desired manner.

[0025] The UI device 8 may include various applications used for a variety of different functions performed by personnel within the plant 10. The UI device 8 may include an operator display application (interchangeably referred to as an "operator application") that enables an operator of the UI device 8 to monitor specific process control information regarding the operation of specific areas of the process plant 10 and control the operation of the process plant 10 in accordance with step-by-step SOP instructions via an interactive SOP display view. That is, the interactive SOP display view incorporates SOP instruction data and process control information in a single view. The interactive SOP display view is rendered on the UI device 8 and references process control data received from the controller 11 and field devices 15-22 and 40-46, as well as the process control functions assigned to such devices. The interactive SOP display view may be any type of interface that enables an operator to manipulate (e.g., read or write) data values ​​to monitor or alter the operation of the field devices 15-22 and 40-46, control routines 38, function blocks, and the process control system 3 and process plant 10 as a whole, for example. The interactive SOP display views may be stored in memory of the UI device 8 or in the configuration database 13. As described below with respect to Figure 3, the UI device 8 may include a configuration application 108 that can create or configure the interactive SOP display views.

[0026] Continuing with FIG. 1 , the wireless field devices 40-46 communicate within the wireless network 70 using a wireless protocol, such as the Wireless HART protocol. The UI device 8 may be capable of communicating with the wireless field devices 40-46 using the wireless network 70. Such wireless field devices 40-46 may communicate directly with one or more other nodes of the process control network or system 2 that are also configured to communicate wirelessly (e.g., using a wireless protocol). To communicate with one or more other nodes that are not configured to communicate wirelessly, the wireless field devices 40-46 may utilize a wireless gateway 35 connected to the backbone 5. Of course, the field devices 15-22 and 40-46 can conform to any other desired standard(s) or protocol, including any wired or wireless protocol, including any standard or protocol developed in the future.

[0027] The wireless gateway 35 can provide access to the various wireless devices 40-58 of the wireless communication network 70. In particular, the wireless gateway 35 provides a communicative coupling between the wireless devices 40-58 and other nodes of the process control network or system 2 (including the controller 11 of FIG. 1 ). In some cases, the wireless gateway 35 provides a communicative coupling by tunneling through shared layer(s) of the wired and wireless protocol stacks with routing, buffering, and timing services to the lower layers of the wired and wireless protocol stacks (e.g., address translation, routing, packet segmentation, prioritization, etc.). In other cases, the wireless gateway 35 may translate commands between wired and wireless protocols that do not share protocol layers.

[0028] Like the wired field devices 15-22, the wireless field devices 40-46 of the wireless network 70 may perform physical control functions, such as opening and closing valves, or obtain measurements of process parameters within the process plant 10. However, the wireless field devices 40-46 are configured to communicate using the wireless protocol of the network 70. As such, the wireless field devices 40-46, the wireless gateway, and the other wireless nodes 52-58 of the wireless network 70 are producers and consumers of wireless communication packets.

[0029] In some scenarios, wireless network 70 may include non-wireless devices. For example, field device 48 of FIG. 1 may be a legacy 4-20 mA device, and field device 50 may be a conventional wired HART device. To communicate within network 70, field devices 48 and 50 may be connected to wireless communication network 70 via wireless adapters (WA) 52a or 52b. Additionally, wireless adapters 52a, 52b may be Foundation (登録商標) Other communication protocols, such as Fieldbus, PROFIBUS, DeviceNet, etc., may be supported. Additionally, the wireless network 70 may include one or more network access points 55a, 55b, which may be separate physical devices in wired communication with the wireless gateway 35 or may be provided within the wireless gateway 35 as an integrated device. The wireless network 70 may also include one or more routers 58 that forward packets from one wireless device to another wireless device within the wireless communication network 70. The wireless devices 32-46 and 52-58 may communicate with each other and with the wireless gateway 35 via wireless links 60 of the wireless communication network 70.

[0030] In some cases, the process control network or system 2 may include other nodes connected to the network backbone 5 that communicate using other wireless protocols. For example, the process control network or system 2 may include one or more wireless access points 7a that utilize other wireless protocols, such as WiFi or other IEEE 802.11-compliant wireless local area network protocols, mobile communication protocols such as WiMAX (Worldwide Interoperability for Microwave Access), LTE (Long Term Evolution), or other ITU-R (International Telecommunication Union Radiocommunication Sector)-compatible protocols, short-wavelength wireless communications such as near-field communication (NFC) and Bluetooth, or other wireless communication protocols. Typically, such wireless access points 7a enable handheld or other portable computing devices to communicate over a respective wireless network that is different from the wireless network 70 and supports a different wireless protocol than the wireless network 70. UI devices 8 may communicate over the process control network or system 2 using the wireless access points 7a. In some scenarios, in addition to the portable computing device, one or more process control devices (e.g., controller 11, field devices 15-22, or wireless devices 35, 40-58) may also communicate using the wireless network supported by access point 7a.

[0031] Additionally or alternatively, the process control network or system 2 may include one or more gateways 7b, 7c to systems external to the immediate process control system. The UI devices 8 may be used to control, monitor, or otherwise communicate with the external systems. Typically, such systems are customers and / or providers of information generated or acted upon by the process control system. For example, a plant gateway node 7b may communicatively connect the immediate process plant 10 (with its own respective process control data network backbone 5) to another process plant with its own respective network backbone. In some cases, a single network backbone 5 may serve multiple process plants or process control environments.

[0032] In another example, plant gateway node 7b may communicatively connect the immediate process plant to a legacy or prior art process plant that does not include a process control network or system 2 or backbone 5. In this example, plant gateway node 7b may convert or translate messages between a protocol utilized by the process control backbone 5 of plant 10 and a different protocol utilized by the legacy system (e.g., Ethernet, Profibus, Fieldbus, DeviceNet, etc.). In such an example, UI device 8 may be used to control, monitor, or otherwise communicate with a system or network within the legacy or prior art process plant.

[0033] The process control network or system 2 may include one or more external system gateway nodes 7c to communicatively connect the process control network or system 2 to a network of external public or private systems, such as a laboratory system (e.g., a Laboratory Information Management System or LIMS), a personnel rounds database, a material handling system, a maintenance management system, a product inventory management system, a production scheduling system, a weather data system, a shipping and handling system, a packaging system, the Internet, another provider's process control system, or other external systems. The external system gateway node 7c may, for example, facilitate communication between the process control system 2 and personnel outside the process plant (e.g., personnel at home).

[0034] 1 shows a single controller 11 with a finite number of field devices 15-22 and 40-46, this is merely an exemplary and non-limiting embodiment. Any number of controllers 11 may be included in the process control network or system 2, and any controller 11 may communicate with any number of wired or wireless field devices 15-22, 40-46 to control processes within the plant 10. Additionally, the process plant 10 may also include any number of wireless gateways 35, routers 58, access points 55, wireless process control communication networks 70, access points 7a, and / or gateways 7b, 7c.

[0035] During operation of the process plant 10, the server 12 may obtain process control data from any of the controllers 11 or field devices 15-22, 40-48, from the historian database 14, or otherwise communicated over the process plant network 10. The process control data may be generated by or derived from information generated by components of the process control system 3. For example, the process control data may include real-time process parameter values, log data, sensor data, and / or any other data that may be captured and stored in the historian database 14 to indicate the status of the controllers 11 or any of the field devices 15-22, 40-48. The process control data may also include historical data of past operations of the process plant, summary data associated with past or current operation of the plant, batch data associated with batches run or scheduled in the process plant, schedule data associated with the operation of the plant, maintenance data associated with the process plant, business data related to the efficiency or profitability of the process plant, or other information associated with the operation of the process plant 10. The UI device 8 may execute an operator application configured to receive process control data from the server 12 as input via an input interface of the UI device 8 .

[0036] FIG. 2A illustrates an exemplary interface for an operator application 71 executing on the UI device 8. The operator application 71 may present process control information, such as various control modules, faceplates, process flows, and process plant entities associated with the plant 10. By way of example, as shown in FIG. 2A , the operator application 71 depicts a flow diagram illustrating a process for converting crude oil into other fuel products. At the entry point to the refining process, a crude oil unit separates components and distributes them for further downstream processing by other units. The crude oil unit may include various equipment, such as pumps, compressors, heat exchangers, reactors, tanks, separation and distillation columns, as well as various field devices, such as temperature, level, and pressure transmitters and valves. Each field device, each group of devices, each process unit, and / or each process area may have a corresponding display graphic that is used by the operator application 71 to represent it to an operator during operation of the process plant 10 and to include information specific to that operation. Parameters associated with each display graphic are also depicted, although it should be understood that the parameters may vary depending on the specific placement and use of the depicted equipment. For example, a radiant firebox may be represented as a graphic 77 in the operator application 71 having a limited set of parameters including temperature (e.g., 813.89°F), as shown in Figure 2A. As will be appreciated, the operator application 71 may provide multiple process plant displays to the operator. As such, the operator may need to monitor multiple process plant display views, with each process plant display view including multiple display graphics.

[0037] When tasked with monitoring a process via the operator application 71, an operator may wish to refer to the SOP for the process. For example, an operator may wish to refer to SOP instructions for monitoring a crude oil supply. Rather than retrieving a traditional paper SOP document known in the art, the operator may access and view the SOP instructions directly from the UI device 8. As shown in FIG. 2A , the operator application 71 may include a user control, such as an SOP icon 73, that, when selected by the operator, causes the operator application 71 to present an interactive SOP display view 74 for monitoring a process, such as a crude oil supply. As shown in FIG. 2A , the interactive SOP display view 74 may be presented as a pop-up window overlaid on the operator application 71. The operator may be able to move the interactive SOP display view 74 by dragging it with an input mechanism, such as a mouse. As another example, the interactive SOP display view 74 may be presented and anchored in a pre-defined portion of the operator application 71, such as portion 79.

[0038] In any event, as shown, interactive SOP display view 74 includes step-by-step SOP instructions depicted as SOP instruction display elements 75. Thanks to the SOP instruction display elements 75 included in interactive SOP display view 74, an operator does not have to go back and forth between a traditional paper SOP document and an operator HMI or unit or field device. An operator can advantageously view interactive SOP display view 74 within operator application 71 to execute the SOP instructions provided within interactive SOP display view 74.

[0039] Additionally, the interactive SOP display view 74 may generally have process control information embedded therein, such that the operator does not need to refer to other process plant display views presented by the operator application 71 when following the SOP instructions provided within the interactive SOP display view 74. In this manner, process control information for which the operator would otherwise need to refer to other process plant display views presented by the operator application 71 when following the SOP may be contained within the interactive SOP display view 74, thereby enhancing the user experience of the interactive SOP display view 74 for the operator. In other words, the process control information embedded in the interactive SOP display view 74 serves as a preview corresponding to a subset of the process control information shown in other portions of the operator application 71. In this manner, the interactive SOP display view 74 may provide only the process control information necessary to monitor the process in accordance with the SOP instructions in the SOP instruction display element 75. Thus, the operator does not need to search for all of the process control information provided by the operator application 71.

[0040] 2A , the interactive SOP display view 74 includes an SOP process control data display element 76 that depicts a process control parameter value for the radiant firebox (e.g., a temperature value of 813.89°F). The SOP process control data display element 76 is adjacent to one of the SOP steps depicted via the SOP instruction display element 75 that is related to the temperature value for the radiant firebox. To this end, the operator does not need to refer to the graphic 77 corresponding to the radiant firebox represented within the operator application 71 (or any other information outside of the interactive SOP display view 74) in order to follow the SOP instructions. The proximity between the SOP process control data display element 76 and the SOP instruction display element 75 further contributes to the ease of use of the interactive SOP display view 74.

[0041] In some cases, the SOP for a process may instruct the operator to manipulate specific parameters or devices within the operator's area of ​​responsibility. For example, SOP instruction display element 75 may include a step indicating that the operator must open a valve if the temperature of a radiant firebox is below 1000°F before the operator can proceed to the next instruction. To perform such a step without requiring the operator to look away from interactive SOP display view 74, interactive SOP display view 74 includes SOP process function display element 78 that depicts a button for remotely opening a valve. Selection of the button may automatically control (e.g., open or close) a physical valve located within plant 10. For this purpose, the operator does not need to physically attend to the valve to control it or otherwise control the valve using other mechanisms separate from interactive SOP display view 74. The proximity between SOP process function display element 78 and SOP instruction display element 75 further contributes to the ease of use of interactive SOP display view 74. The interactive SOP display view 74 may lock access to any of the next instructions contained in the SOP until the interactive SOP display view 74 receives an indication that the SOP process function display element 78 has been selected. In this manner, the interactive SOP display view 74 can prompt the operator to perform step-by-step instructions of the SOP.

[0042] 2A illustrates interactive SOP display view 74 as a window specific to process plant specific operator application 71, further including display elements 75-76 and 78, which are merely exemplary and non-limiting embodiments. Any number of display elements may be included in interactive SOP display view 74 to communicate SOPs for any type of process for monitoring various types of process control information and / or for remotely controlling any number of devices.

[0043] For example, as shown in FIG. 2B , interactive SOP display view 84 includes step-by-step SOP instructions via SOP instruction display element 85 instructing the operator to check the crude oil level in the tank and the pressure level in the desalter. In contrast to interactive SOP display view 74, which displays SOP process control data display element 76 in text form, interactive SOP display view 85 may include SOP process control data display elements 86 and 88 in the form of graphics corresponding to the respective tank and desalter. The graphics may display animations, such as pictorial fill representations of oil and pressure levels and corresponding numerical representations. Like interactive SOP display view 74, interactive SOP display view 84 may be presented as a pop-up window overlaid on operator application 71, or alternatively, may be presented and anchored in a pre-defined portion of operator application 71, such as portion 89.

[0044] 2C , interactive SOP display view 94 may be provided by an operator application separate from the process plant-specific operator application 71. As shown, interactive SOP display view 94 is provided by a spreadsheet application (e.g., Microsoft Excel), although other suitable third-party applications, such as word processing applications, are contemplated. Interactive SOP display view 94 includes step-by-step SOP instructions via SOP instruction display element 95, as presented in column A. SOP process control data display element 96 and SOP process function display element 98 may be presented in column B adjacent to column A.

[0045] In addition to the operator applications described above, the UI device 8 may also include one or more configuration applications, including, for example, a control module creation application that can be accessed by any authorized configuration engineer to create control routines or modules 38 and store the control routines or modules 38 in the configuration database 13. The authorized configuration engineer can also download the control routines or modules 38 to the controllers 11 and field devices 15-22 and 40-46 of the plant 10.

[0046] Similarly, a configuration engineer may use one or more configuration applications to configure (e.g., create, generate, and / or edit) an interactive SOP display view (e.g., any of the interactive SOP display views 74, 84, or 94 described above) and then download the completed interactive SOP display view to UI device 8. Generally, a configuration application may include a user interface through which a configuration engineer can provide user input for configuring the interactive SOP display view using graphical user controls provided by the configuration application. A particular interactive SOP display view configuration may be defined to include (e.g., refer to, point to, or reference) one or more SOP display view elements. Each SOP display view element may be defined as a data element, a data link element, a function block element in the form of a button (including shapes such as a rectangle, square, circle, etc.), a slider, a navigation bar element, or any other suitable display element. The above-described SOP instruction display elements 75, 85, and 95 may be data elements, the above-described SOP process control data display elements 76, 86, 88, and 96 may be data link elements, and the above-described SOP process function display elements 78 and 98 may be function block elements. In general, the interactive SOP display views described herein may include multiple display view elements associated with sets of SOP instructions, process parameters, and / or process control functions.

[0047] 3, UI device 8 may include a configuration application 108 that can create or configure interactive SOP display views by generating one or more SOP objects 100 in an object-oriented programming protocol, each corresponding to a configuration of a unique interactive SOP display view. One or more SOP objects 100 may also be stored in a database (e.g., configuration database 13) such that when one or more SOP objects 100 are instantiated in the runtime environment of process plant 10, the interactive SOP display views are automatically displayed in a runtime environment, such as operator application 71, presented on UI device 8. For example, configuration database 13 may store SOP object 100a, SOP object 100b, and SOP object 100c, which may correspond to interactive SOP display views 74, 84, and 94, respectively.

[0048] Each SOP object 100 may contain or reference one or more sub-objects, each of which defines how a particular display element of the SOP object 100 is displayed to an operator of the plant 10.

[0049] As shown in Figure 3, several SOP objects 100, such as SOP object 100a and SOP object 100b, can each include or reference a respective text object 102a and text object 102b, each of which defines a respective SOP instruction display element corresponding to a respective description for performing one or more steps of the SOP to assist a user in monitoring or controlling a process plant. For example, text object 102a defines SOP instruction display element 75 of interactive SOP display view 74 shown in Figure 2A, where SOP instruction display element 75 corresponds to an SOP step related to checking the temperature at a radiant firebox and opening a valve if the temperature falls below a predetermined threshold. Text object 102b defines SOP instruction display element 85 of interactive SOP display view 84 shown in Figure 2B, where SOP instruction display element 85 corresponds to an SOP step related to checking the crude oil level in a tank and ensuring that the pressure level in a desalter is below a threshold.

[0050] Several SOP objects 100, such as SOP object 100a and SOP object 100b, may each include or reference a respective data link object 103a and data link object 103b, each of which defines a respective SOP process control data display element corresponding to a link to process control data (e.g., real-time data, stored historized data) associated with a particular control module, function block or object, device, or control parameter. The links define locations within the process control system (e.g., server 12, historian database 14, controller 11, field devices 15-22, and 40-46) from which particular process control data can be obtained. For example, data link object 103a defines SOP process control data display element 76 of interactive SOP display view 74 shown in FIG. 2A that corresponds to a process control parameter value (e.g., a temperature value of 813.89°F) for a radiant firebox. The data link object 103a defines the SOP process control data display element 86 of the interactive SOP display view 84 shown in FIG. 2B that corresponds to the process control parameter value (eg, 51.4% crude oil level).

[0051] In some cases, a process control parameter value may be accompanied by a graphic. For example, SOP process control data display element 86 of interactive SOP display view 84 may be accompanied by a graphic representing a crude oil storage tank that enhances the visual depiction of a 51.4% crude oil level in a graphical manner. In such a case, an SOP object, such as SOP object 100b, may include or reference graphics object 104b, which defines the graphic associated with SOP process control data display element 86. SOP objects that do not have such similar graphics, such as SOP object 100a, need not include a graphics object.

[0052] Some SOP objects 100, such as SOP object 100a, may include or reference action objects 105a, which define SOP process function display elements that correspond to particular control modules, function blocks, or objects, or process control functions of a device. The process control functions may be stored, for example, in configuration database 13. A process control function generally defines the inputs and outputs of physical or logical process control elements (i.e., particular control modules, function blocks, or objects, or devices) to control one or more industrial processes running within a process plant or system, such as by sending signals or commands to particular function blocks or objects in a field device or to particular control modules or objects running within a controller application in response to a trigger (e.g., user selection of a SOP process function display element). The control modules or objects running in the controller application may then generate and send control signals to control modules or function blocks running in the field devices to ultimately affect the process, such as activating a field device (e.g., opening or closing a valve or filling a tank), shutting down a field device, or setting a setpoint in the controller application that affects the operation of the field device. For example, action object 105a defines an SOP process function display element 78 of interactive SOP display view 74 shown in Figure 2A that corresponds to a button for opening a valve. Selection of the button can automatically control a physical valve located in plant 10 to open.

[0053] Several SOP objects 100, such as SOP object 100a and SOP object 100b, may each include or reference a respective layout object 106a and layout object 106b, each of which defines the visual representation of an interactive SOP display view. The layout objects may define the positional relationship of various display elements contained within the interactive SOP display view relative to one another. For example, layout object 106a defines the layout of interactive SOP display view 74, in which SOP instruction display element 75 is positioned to the left of and adjacent to SOP process control data display element 76, which is positioned above and adjacent to SOP process function display element 78. As another example, layout object 106b defines the layout of interactive SOP display view 84, in which SOP instruction display element 85 is positioned to the left of and adjacent to SOP process control data display element 86, which is positioned above and adjacent to SOP process control data display element 88.

[0054] In some cases, the layout object may also define the location of the interactive SOP display view itself relative to other process plant display views provided by the operator application. For example, layout object 106a may specify a portion of operator application 71, such as portion 79, as the location where interactive SOP display view 74 is anchored. Layout object 106b may specify a portion of operator application 71, such as portion 72, as the location where interactive SOP display view 84 is initially placed. However, layout object 106b may also define interactive SOP display view 84 to be “free-form,” allowing the operator to drag or otherwise move interactive SOP display view 84 to any location on operator application 71.

[0055] Some SOP objects 100, such as SOP object 100a and SOP object 100b, may each include or reference a respective version object 107a and version object 107b, which each specify a version number or identifier for the respective SOP object 100a and SOP object 100b. Accordingly, a particular set of any of the display elements described above, including layout, may be associated with a version. The configuration application 108 may provide each SOP object 100 with a unique identifier to facilitate version control and tracking, and to identify which SOP objects 100 to download to the UI device 8.

[0056] It should be noted, however, that the above SOP object 100 is merely an example. In general, the SOP object 100 described herein may include any one, some, or all of the sub-objects described above (e.g., text object 102a, data link object 103a, graphics object 104b, action object 105a, layout object 106a, and version object 107a), or variations thereof.

[0057] FIG. 4 illustrates an exemplary configuration application 108 for enabling a configuration engineer to build a SOP object 100 corresponding to an interactive SOP display view 111. Generally, a configuration engineer utilizes the configuration application 108 to define the SOP object 100 by dragging and dropping instances of various display view elements (e.g., display view elements 112-117) from an editing pane 109 onto a configuration canvas 110 presented by the configuration application 108, or by using any other suitable graphical user controls, and may further configure instances of the display elements (e.g., display view elements 112a-117a) as needed. The display view elements 112-117 function as templates with properties that can be further customized for each instance of the display view elements 112a-117a. In this manner, the configuration engineer can define where the display view elements are located within the interactive SOP display view 111 and specify attributes or properties of each of the instances of the display view elements. Each of the display view elements 112a-117a, which may correspond to a respective instance of a sub-object (e.g., text object 102a, data link object 103a, graphics object 104b, action object 105a, layout object 106a, and version object 107a), may be bound by an instance of the SOP object 100 and defined with properties or attributes.

[0058] A configuration engineer may define properties or attributes in the configuration application 108 for each of the display view elements 112a-117a, and therefore for the corresponding sub-objects. In general, each of the display view elements 112a-117a may include properties that are static or dynamic. For example, the SOP display view element 112a may have a static property, in that the SOP display view element 112a is configured to statically display the text of the SOP instructions to the user. The configuration engineer may enter the text of the SOP instructions into a free-form text field generated by the configuration application 108 as a result of dragging the text element 112a to the configuration canvas 110. In some cases, if the SOP instructions already exist (e.g., in a file stored in the configuration database 13), the SOP display view element 112a may correspond to a reference or path to a data source (e.g., the configuration database 13) where the SOP instructions reside. The configuration engineer may provide a file path for the SOP instructions so that the text of the SOP instructions can be migrated and displayed via the text element 112a. The text (or the path to the text), as well as modifications to the text such as its size or font, may be stored as properties 122a associated with the SOP display view element 112a.

[0059] As another example, the SOP display view element 113a may have dynamic properties in that the SOP display view element 113a is configured to dynamically display linked process control data. A configuration engineer may configure the properties 123a associated with the SOP display view element 113a, such as a reference or path to a data source (e.g., the historian database 14, the configuration database 13, the controller 11, or field devices 15-22 and 40-46 identified by control tag numbers) that stores or generates the value of the corresponding process parameter, a data type of the data source, such as a process variable value or an array of process variable values, such as a set of historized process variable values, the number of decimals to include when displaying the value of the data source, etc. Thus, a configuration engineer may effectively assign process parameter inputs to the SOP display view element 113a so that when the SOP display view element 113a is instantiated in a runtime environment, obtained process parameter values, such as the current process parameter value of a process control element (e.g., a tank) (e.g., a tank fill rate of "54%), the current process parameter value of the state (e.g., "off") of a process control element (e.g., a pump) to the user, or the historized process parameter values ​​of a valve's flow rate, inlet pressure, and outlet pressure, are displayed via the SOP display view element 113a.

[0060] Process control data need not be limited to being displayed in a textual representation. For example, the configuration application 108 may enable a configuration engineer to click and drag a SOP display view element 114a depicting a graphical representation of a process control element (e.g., a valve, a pump, a tank, etc.) and set properties 124a associated with the SOP display view element 114a to reference any one or more of the following: the name of the process control element identified by a control tag number; the name of a process parameter; a description of the process parameter; a process parameter value of the process control element (e.g., a tank fill rate, a tank setpoint, a tank output process parameter value such as the flow rate of liquid entering the tank); a historized parameter value for a threshold period; or any suitable combination thereof. The referenced process parameter value may be visually depicted via the SOP display view element 114a when the SOP display view element 114a is instantiated in the runtime environment, for example, by an animation of a fluid level hovering midway in a tank to indicate that the tank is “54%” full of fluid, a static graphic of a valve in an open position to indicate that the valve state is “off,” etc.

[0061] To allow an operator to control any of the process control elements described above, a configuration engineer may drag and drop SOP display view elements 115a and further define properties 125a associated with the SOP display view elements 115a in the configuration environment. The properties 125a may define the behavior of the SOP display view elements 115a when manipulated by a user in the operational environment. Such properties 125a may define the SOP display view elements 115a as actuation mechanisms that dynamically affect the process, such as activating a process control element (e.g., a valve, pump, tank, etc.) in response to a trigger condition, such as a mouse click on the SOP display view element 115a in the form of a graphical button, and optionally displaying a result via the SOP display view element 115a or a process parameter value via the display view elements 113a and / or 114a in response to a trigger, such as a confirmation message indicating that the process control element has been activated. For example, user selection of SOP display view element 115a may initiate a pumping process for a particular pump identified in property 125a by an assigned control tag, followed by changing a process parameter value of "off" corresponding to a "current pump state" process parameter to "on" via display view element 113a, or displaying a graphic of the pump in an open position via display view element 114a. Property 125a associated with display view element 115a, like properties 123a and 124a, may include a control tag assigned to SOP display view element 115a, which references a particular control module, function block or object, or device defined in configuration database 13, such that when display view element 115a is instantiated in the runtime environment, user manipulation (e.g., selecting, clicking, pushing) of SOP display view element 115a will initiate the function of the particular control module, function block or object, or device in the runtime environment identified by the control tag.

[0062] A configuration engineer may determine where display view elements 112a-115a are located relative to one another within interactive SOP display view 111. Thus, the above-described display view elements 112a-115a may be included in interactive SOP display view 111 according to a layout defined by SOP display view element 116a. That is, as specified by its properties 126a, SOP display view element 116a may define a layout that defines the visual representation of one or more display view elements 112a-115a.

[0063] As one example, the layout can be based on the relative positions between display view elements 112a-115a within interactive SOP display view 111. A configuration engineer may define a particular layout to drag and drop display view elements 112a-115a onto canvas 110, thereby presenting display view elements 113a and 114a adjacent to display view element 112a, as shown in Figure 4, allowing a user (e.g., an operator) of interactive SOP display view 111 to easily determine that display view elements 113a and 114a correspond to the SOP instruction depicted in display view element 112a. The proximity between each of display view elements 113a and 114a and display view element 112a may convey an inherent relationship that is apparent to the user, such as when display view elements 113a and 114a correspond to process parameter values ​​for a tank and display view element 112a corresponds to an SOP instruction for checking the process parameter value for the tank.

[0064] The layout may also indicate how the interactive SOP display view 111 is presented compared to other process plant display views within an operator application (e.g., operator application 71 shown in FIG. 2A ). For example, the interactive SOP display view 111 may be configured to be a free-form window that can be moved and overlaid on any region (e.g., frame, area, or portion) of the layout of the operator application 71. Alternatively, the layout of the operator application 71 may be divided into several regions, one of which may be dedicated to anchoring the interactive SOP display view 111 and other regions may be dedicated to anchoring other process plant display views, allowing a user of the interactive SOP display view 111 to simultaneously view the interactive SOP display view 111 and the other process plant display views on a single screen.

[0065] Of course, configuring the interactive SOP display view 111 in the manner depicted in Figure 4 is meant to be exemplary, but not limiting, and is only one of many possible scenarios for using the graphical display configuration 108. Indeed, as demonstrated within this disclosure, the configuration application 108 provides an operating experience that is flexible, intuitive, and easy to use, while at the same time supporting the integration of SOP instructions and process control information in a single interactive SOP display view.

[0066] During configuration, the example interactive SOP display view 111 of FIG. 4 may be considered a draft, work-in-progress, or in-progress SOP object 100 (e.g., not published). Once the configuration engineer is satisfied with the SOP object 100, which defines the content, appearance, layout, and behavior of the display view elements 112a-115a included in the interactive SOP display view 111, the configuration engineer may publish the SOP object 100. Upon publishing the SOP object 100, sub-objects that are not yet in a published state may be automatically published, and / or the user may be prompted to manually publish sub-objects that are still in a draft or in-progress state. That is, for the SOP object 100 to be published, any sub-objects contained therein or linked to it must also be in a published state. The published SOP object 100 is stored in the configuration database 13, thereby making the published SOP object 100 available for download to the operating environment of the process plant 10.

[0067] Each SOP object 100 may be associated with a published version stored in the configuration database 13, and optionally one or more draft versions (interchangeably referred to herein as “in progress” or “work-in-progress” versions). Generally speaking, only published SOP objects 100 are permitted or allowed for download from the configuration database 13 to the UI devices 8 of the operating environment. Draft SOP objects 100 are maintained and edited only within the configuration environment and are prevented from being downloaded into the UI devices 8. For example, the configuration application 108 may allow a configuration engineer to click and drag SOP display view elements 117a depicting version numbers or other suitable version identifiers in the interactive SOP display view 111 and further set properties 127a associated with the SOP display view elements 117a. Different versions of the same SOP object 100, or different SOP objects, may be defined and represented by unique version identifiers, which may be implemented by numbers, alphanumeric strings, user-friendly names, or other desired identifiers. Different versions of the same SOP object 100 may be published, stored, and tracked. For example, configuration application 108 may replace a previous version of SOP object 100 stored in configuration database 13 with an updated version, or may generate a new, updated version of SOP object 100 to store a previous version of SOP object 100 in configuration database 13. Different versions of SOP object 100 may be necessitated by updates to the SOP (e.g., adding, deleting, or changing one or more steps of the SOP), updates to software used to develop or execute SOP object 100 (e.g., configuration application 108, operator application 71), etc.Properties 127a may define a nomenclature for the version identifier, including, for example, the name of the SOP object 100, the status of the SOP object 100 (e.g., "published," "draft"), or the version of the SOP object 100, or the version of the software used to develop or execute the SOP object 100. The version identifier may be stored centrally, for example, in configuration database 13, thereby formalizing the version identifier for the process plant 10. Each interactive SOP display view corresponding to a respective SOP object executed in the runtime environment may reference a respective version identifier.

[0068] 5 shows a flow diagram of an example method 130 for generating and storing SOP objects 100 to define an interactive SOP display view (e.g., interactive SOP display view 111). Method 130 may be implemented in UI device 8 via configuration application 108 in communication with server 12.

[0069] In block 131, the configuration application 108 presents user controls in a user interface. The user controls may include mechanisms for dragging and dropping various display view elements (e.g., display view elements 112-117) from the edit pane 109 to various locations on the configuration canvas 110 of the configuration application 108. The user controls may also include mechanisms for editing properties associated with each of the various display view elements.

[0070] In block 132, the configuration application 108 receives user input via user controls for configuring the SOP object 100. The user input may be provided by a user responsible for configuring the interactive SOP display view, such as a configuration engineer.

[0071] In block 133, the configuration application 108 determines that the user input is to configure a text element (e.g., display view element 112a), e.g., drag and drop the text element into the configuration canvas 110 and specify the position or location of the text element (e.g., coordinates of the display view element 112a relative to the interactive SOP display view 111). The user input may also specify properties of the text element (e.g., properties 122a).

[0072] At block 134, the configuration application 108 generates a text object (e.g., text object 102a), which may store properties associated with the text element as specified by user input. Then, at block 135, the configuration application 108 assigns the position or location of the text object to a layout object (e.g., layout object 106a) and proceeds to block 136.

[0073] In block 136, the configuration application 108 determines whether the user input configures a data link element (eg, display view element 113a) and / or a graphics element (eg, display view element 114a).

[0074] In some scenarios, in block 136, the configuration application 108 determines that the user input configures data link elements and / or graphics elements, e.g., dragging and dropping the data link elements and / or graphics elements into the configuration canvas 110 to specify the position or location of the data link elements and / or graphics elements (e.g., coordinates of display view element 113a and / or display view element 114a relative to the interactive SOP display view 111). The user input may also specify properties of the data link elements and / or graphics elements (e.g., properties 123a, 124a). In block 137, the configuration application 108 generates respective data link objects (e.g., data link object 103a) and / or graphics objects (e.g., graphics object 104b), which may store the properties associated with the data link elements and / or graphics elements specified by the user input. Subsequently, in block 138, the configuration application 108 assigns the position or location of the data link objects and / or graphics objects to layout objects and proceeds to block 139.

[0075] In other scenarios, the configuration application 108 in block 136 determines that the user input does not configure a data link element and / or a graphics element and proceeds to determine in block 139 whether the user input configures an action element.

[0076] In some scenarios, the configuration application 108 in block 139 determines that the user input is to configure an action element, e.g., drag and drop the action element onto the configuration canvas 110 to specify the position or location of the action element (e.g., coordinates of the display view element 115a relative to the interactive SOP display view 111). The user input may also specify properties of the action element (e.g., properties 125a). In block 140, the configuration application 108 generates an action object (e.g., action object 105a) that may store properties associated with the action element specified by the user input, such as a communication path or link that defines where in the process control system a particular control module, function block, or object, or process control function of a device, resides, to provide a signal or command to a particular control module, function block, or object, or process control function of a device, in the plant, to take some action. Subsequently, in block 141, the configuration application 108 assigns the position or location of the action object to a layout object and proceeds to block 142.

[0077] In other scenarios, configuration application 108 in block 139 determines that the user input does not configure an action element and determines whether user input indicating completion of the SOP object has been received in block 142. If configuration application 108 determines that user input indicating completion of the SOP object has not been received, method 130 may proceed to block 132. Otherwise, in block 143, configuration application 108 may generate a version object (e.g., version object 107a), which may store properties associated with the version element (e.g., version element 107a) that may be specified by user input.

[0078] In block 144, the configuration application 108 generates a SOP object based on the sub-objects generated in blocks 134, 137, 140, and 143. The configuration application 108 then stores the SOP object in a database (e.g., configuration database 13) in block 145, making the SOP object available for download to an operator workstation (e.g., UI device 8).

[0079] Although the generated SOP object of FIG. 5 is described as including a single text element, data link element, graphics element, and / or action element for ease of illustration, the configuration application 108 can receive user input via user controls to configure the SOP object 100 to include any number of text elements, data link elements, graphics elements, and / or action elements necessary to provide an overall interactive SOP display view.

[0080] FIG. 6 shows a high-level block diagram illustrating one possible way of implementing embodiments and / or aspects of the graphical display configuration and SOP display system described herein within the configuration environment 152 and operating environment 155 of a process plant or process control system, such as the process plant 10 of FIG. 1 .

[0081] 6, the configuration environment 152 includes a configuration application (e.g., configuration application 108) that a configuration engineer can use to generate draft SOP objects 100, which are stored in the configuration database 13, as described in FIG. 5, making the SOP objects 100 available for download and execution within the operating environment 155, which may enable an operator or user to view the SOP instructions, monitor various status and conditions of the process, and, if necessary, control the process. Each SOP object 100 (e.g., 100a, 100b, 100c) corresponds to a different area within the process plant or different process plants, and upon download and execution within the operating environment 155, each operator may display an interactive SOP display view that represents his or her area of ​​responsibility.

[0082] Once satisfied with the draft SOP object 100, the configuration engineer may explicitly publish the SOP object 100 (e.g., change its state to “published”), making it available for downloading and execution within the runtime process plant 10. Any of the published SOP objects 100 may be instantiated and provided (e.g., downloaded) to one or more different UI devices 8 for execution, as represented by UI device 8 in FIG. 1 . In one example, SOP objects 100a-100c, which may be configured to provide the same or different sets of SOP instructions for three respective portions of the plant, may be downloaded to three different UI devices 8 located in three respective portions of the plant. Thus, each downloaded instance of the published SOP object 100 may be independently executed in the operator application 71 of the UI device 8. As another example, SOP objects 100a-100c, which may be configured to provide three different sets of SOP instructions for one portion of the plant, may be selectively downloaded to a single UI device 8 by operator(s) residing on the single UI device 8 who are responsible for executing all three SOPs collectively.

[0083] The particular set of UI devices 8 to which the published SOP object 100 is downloaded (and executed within) may be specified by a user, for example, via the configuration application 108 or via another user interface (e.g., operator application 71, maintenance application, etc.) of the operating environment 155. If each of the SOP objects 100a-100c is identified by a unique version identifier, an application (e.g., configuration application 108, operator application 71, maintenance application) executing on the UI device 8 may receive an indication of a particular version identifier from a configuration engineer(s) or operator(s) and then retrieve and execute the particular SOP object having an identifier matching the indication from a database (e.g., configuration database 13) configured to store the SOP objects 100a-100c.

[0084] As a result of the SOP object 100 executing on the UI device 8, as defined by the SOP object 100 corresponding to the interactive SOP display view, the instantiated interactive SOP display view displays the SOP instruction data on the UI device 8 and communicates with a runtime environment 158 ​​that may execute on the controllers and field devices associated with the process to access process control data for display in the user interface 8 or to control the process of the plant. The UI device 8 may communicate with the runtime environment 158 ​​using any desired or pre-configured communications network, such as the data highway 5 and / or the wireless communications network 70 of FIG. 1 .

[0085] In accordance with the SOP objects 100 published by the configuration engineer, the operator application 71 may receive any of the SOP objects 100 from a database (e.g., configuration database 13) that stores SOP objects 100, and during runtime, automatically identify relevant attributes or properties (e.g., associated text, referenced process parameters, process control functions, or trigger conditions to actions, etc.) of the included or referenced sub-objects (e.g., objects 102a-107a) described above, and display an interactive SOP display view (e.g., interactive SOP display view 111) containing display view elements (e.g., display view elements 112a-117a) accordingly. When a particular SOP object 100 is instantiated at runtime of a process plant in the operating environment 155, process control data associated with a particular control module, function block or object, or device may be represented via linked display view elements on the interactive SOP display view, for example, in a continuously or recurringly updated manner (e.g., every millisecond, every two seconds, every minute, etc.). That is, the SOP object may be configured to plot the parameter value of the process parameter in real time while the plant is operating. In some cases, the SOP object may be configured to plot historized process parameter values ​​in near real time, such as the process parameter value for the past five minutes.

[0086] For example, when the SOP object 100 is instantiated at runtime in a process plant of the operating environment 155, the UI device 8 displays an interactive SOP display view 111 that includes a text element 112a and a data link element 113a. The text element 112a may be linked to SOP instruction data, and the data link element 113a may be linked to process control data. The UI device 8 may receive the SOP instruction data and process control data from the server 12 or other nodes of the process control network or system 2, such as the controller 11, any of the field devices 15-22, 40-48, or the wireless gateway 35, via the backbone 5. Based on the SOP instruction data and process control data received at the UI device 8, the UI device 8 provides output (i.e., visual representations or graphics) representing the SOP instruction data via the text element 112a and the process control data via the data link element 113a, allowing a user to monitor the displayed process control data in accordance with the displayed SOP instructions. Additionally, when the SOP object 100 is instantiated during runtime of the process plant of the operating environment 155, the interactive SOP display view 111 may include an action element 115a, and user selection of the action element 115a causes the SOP object 100 to communicate with the controller 11 for controlling the field devices 15-22 and 40-46 (e.g., valves) or to communicate directly with the field devices 15-22 and 40-46.

[0087] In this manner, an operator monitoring or managing a process plant may display process control information and / or act on the process using the same interface that displays SOP instructions. For example, the UI device 8 may display a set of SOP steps or instructions and graphics for a user to monitor a tank filling process. In such a scenario, the user may read one of the steps of the SOP displayed by the UI device 8 and instruct the user to verify that the tank level measurement meets a certain threshold. The UI device 8 may display the tank level measurement along with the SOP step so that the user does not have to navigate away from the UI device 8. The user can verify that the tank level measurement indeed meets the certain threshold indicated within the SOP step and seamlessly proceed to the next SOP step again without navigating away from the UI device 8. In some embodiments, the UI device 8 may prevent the user from proceeding to the next SOP step if the user fails to take appropriate action in any of the preceding SOP steps. Advantageously, by integrating SOP instructions and process control data into one UI of UI device 8, a user is prevented from, for example, misreading steps out of sequence, manually tracking which steps the user has already performed, reading incorrect process control data, or proceeding to the next SOP step before taking appropriate action with respect to the preceding SOP step.

[0088] The UI device 8 may also enable a user to control a process by providing input at the UI device 8 according to SOP instructions. Extending the scenario described above with respect to monitoring a tank filling process, the UI device 8 may display an SOP step to instruct the user to fill the tank if the tank level measurement does not meet a particular threshold. If the user determines that the process control data corresponding to the tank level measurement displayed by the UI device 8 does indeed meet the threshold, the user may manipulate a graphic displayed at the UI device 8 alongside the displayed SOP step (e.g., mouse click on a graphic button) to cause the UI device 8 to remotely control (e.g., open) an inlet valve to allow fluid to flow into the tank. In another scenario, the user may interact with the UI device 8 to, for example, change parameters associated with a control routine stored in the controller in real time. In embodiments in which the UI device 8 prevents the user from progressing to the next SOP step if the user fails to take appropriate action at any of the preceding SOP steps, the UI device 8 may request user input corresponding to the SOP step so that the user can continue execution to the next SOP step.

[0089] Importantly, the published SOP object 100, when executed on the UI device 8, allows the operator or user to follow the SOP instructions without navigating away from the interactive SOP display view, because the process control information found on the dedicated operator HMI is readily available on the SOP display view. As a result, and advantageously, the interactive SOP display view provides the operator with a more seamless user experience when implementing the SOP, reducing mistakes and enhancing the understanding that the SOP instructions are being properly followed. Furthermore, advantageously, the interactive SOP display view serves as a method for electronically storing and accessing SOP instructions, so that as process industries face talent loss due to retirement, the next generation of operators can be equipped with the knowledge, via the interactive SOP display view, captured by more experienced personnel to prevent situations that arise from not properly implementing certain sequences, such as plant shutdowns, maintenance performance, etc.

[0090] In some cases, users, such as maintenance personnel, who are typically tasked with directly addressing issues such as repair or maintenance of process control elements (e.g., controllers, field devices), may be assigned to a back-end system device or a handheld (portable) device that can be moved around the plant, such as represented by UI device 8 in FIG. 1. After repairing or maintaining the process control element(s), the maintenance personnel may wish to test the process control element(s) to ensure that they are functioning properly. As part of the testing process, the maintenance personnel may utilize a maintenance application running on their assigned back-end system device or handheld (portable) device (e.g., UI device 8) to download any of the SOP objects from a database (e.g., configuration database 13) that affect the process control elements. Because some of the SOP objects stored in the database may not be configured to affect the process control elements, the maintenance personnel need only selectively download the SOP objects that affect the process control element(s) that the maintenance personnel repaired, such as SOP object 100b described above. The SOP object 100b may be identified by a version number or identifier that specifies the name or model of the process control element repaired by the maintenance technician. The maintenance technician may display a list of available SOP objects stored in a database via an assigned back-end system device or handheld (portable) device and provide an indication of the identifier of the target SOP object 100b to a maintenance application. The maintenance application may receive the indication of the identifier of the target SOP object 100b and retrieve and execute the target SOP object 100b having an identifier that matches the indication. The maintenance technician may then operate on the process control element according to the SOP instructions corresponding to the target SOP object 100b displayed via the maintenance application to verify that the process control element is functioning properly.

[0091] 7 shows a block diagram of an exemplary UI device 8. UI device 8 may be a desktop computer, such as a traditional operator workstation or control room display, or a mobile computing device, such as a laptop computer, tablet computer, mobile device, smartphone, personal digital assistant (PDA), wearable computing device, or any other suitable client computing device. UI device 8 may include a display 160, memory 164 for storing various applications, programs, and data structures described herein, one or more processors or CPUs 161 for executing any of the applications stored in memory 164, random access memory (RAM) 163, input / output (I / O) circuitry 162, and a communication unit 167 for transmitting and receiving data over a local area network, a wide area network, or any other suitable network. UI device 8 may communicate with controller 11, server 12, and / or any other suitable computing device.

[0092] In addition to the configuration application 108 and the operator application 71, the memory 164 may include an operating system 165 and a control unit 166 for controlling the display 160 and communicating with the controller 11 to control online operation of the process plant 10. The server 12 may transmit process control data of a portion of the process plant to the UI device 8, and the control unit 166 may then cause a graphical representation of the process control data to be presented on the display 160. Additionally, the control unit 166 may obtain user input from the I / O circuitry 162, such as user input from an operator, and convert the user input into a request to present a graphical display view, a request to display process control data, a request to control a field device, or the like. In some cases, the control unit 166 may communicate the converted user input to the server 12, which may generate and transmit the requested UI for display to the UI device 8. In other embodiments, the control unit 166 may generate a new UI based on the converted user input and present the new UI on the display 160 of the UI device 8.

[0093] The following additional considerations apply to the above discussion: Throughout this specification, actions described as being performed by any device or routine generally refer to the actions or processes of a processor that manipulates or transforms data in accordance with machine-readable instructions. The machine-readable instructions may be stored on and retrieved from a memory device communicatively coupled to the processor. In other words, the methods described herein may be embodied by a set of machine-executable instructions stored on a computer-readable medium (i.e., on a memory device), as shown in FIG. 1. The instructions, when executed by one or more of the processors of a corresponding device (e.g., a server, a UI device, etc.), cause the processor to perform the method. When instructions, routines, modules, processes, services, programs, and / or applications are referred to herein as being stored or saved on a computer-readable memory or computer-readable medium, the terms “stored” and “saved” are intended to exclude transitory signals.

[0094] Additionally, the terms "operator," "personnel," "person," "user," "technician," and other similar terms are used to describe persons within a process plant environment who may use or interact with the systems, apparatus, and methods described herein, but these terms are not intended to be limiting. Where particular terms are used in the description, the terms are used in part for traditional activities engaged in by plant personnel, but are not intended to limit the personnel who may engage in a particular activity.

[0095] Additionally, throughout this specification, multiple instances may implement structures described as components, operations, or single instances. While individual operations of one or more methods are illustrated and described as separate operations, one or more of the individual operations may be performed simultaneously, and the operations need not be performed in the order illustrated. Structures and functions presented as separate components in example configurations may be implemented as combined structures or components. Similarly, structures and functions presented as single components may be implemented as separate components. These and other variations, modifications, additions, and improvements are within the scope of the subject matter of this specification.

[0096] Unless specifically stated otherwise, discussions herein using words such as "processing," "operating," "calculating," "determining," "identifying," "presenting," "causing to present," "displaying," "displaying," and the like may refer to machine (e.g., computer) actions or processes that manipulate or transform data represented as physical (e.g., electrical, magnetic, biological, or optical) quantities in one or more memories (e.g., volatile memory, non-volatile memory, or a combination thereof), registers, or other machine components that receive, store, transmit, or display information.

[0097] If implemented in software, any of the applications, services, and engines described herein may be stored in any tangible, non-transitory computer-readable memory, such as a magnetic disk, laser disk, solid-state memory device, molecular memory storage device, or other storage medium, such as in the RAM or ROM of a computer or processor. It should be noted that while the exemplary systems disclosed herein are disclosed as including, among other components, software and / or firmware running on hardware, such systems are merely exemplary and should not be considered limiting. For example, it is contemplated that any or all of these hardware, software, and firmware components may be embodied exclusively in hardware, exclusively in software, or in any combination of hardware and software. Thus, those skilled in the art will readily appreciate that the provided examples are not the only ways to implement such systems.

[0098] Thus, while the present invention has been described with reference to specific examples, it will be apparent to those skilled in the art that these examples are illustrative only and are not intended to be limitations of the invention, and that modifications, additions, or deletions may be made to the disclosed embodiments without departing from the spirit and scope of the invention.

[0099] It should also be understood that unless a term is expressly defined in this patent using the sentence "As used herein, the term '______' is hereby defined to mean..." or similar, there is no intention to limit the meaning of the term, either expressly or by implication, beyond its plain or ordinary meaning, and such term should not be construed as limited in scope based on any statement made in any section of this patent (other than the claim language). If any term recited in the final claim of this patent is referred to in this patent in a manner consistent with a single meaning, this is done solely for clarity so as not to confuse the reader, and it is not intended that such claim term be limited, by implication or otherwise, to that single meaning. Finally, unless a claim element is defined by the word "means" and a recitation of a function without any recitation of structure, the scope of any claim element is not intended to be construed based on application of 35 U.S.C. 112(f) and / or pre-AIA 35 U.S.C. 35 U.S.C. 112, paragraph 6.

[0100] Furthermore, while the above text sets forth detailed descriptions of many different embodiments, it should be understood that the scope of this patent is defined by the language of the claims set forth at the end of this patent. The detailed description should be construed as merely exemplary and does not describe every possible embodiment, as doing so would be impractical, if not impossible. Many alternative embodiments could be implemented using either current technology or technology developed after the filing date of this patent, and would still fall within the scope of the claims.

Claims

1. 1. An operator application system for executing a standard operating procedure (SOP) object, said operator application system comprising: a memory configured to store the SOP object, the SOP object comprising: a first element corresponding to a description for performing one or more steps of the SOP when monitoring or controlling the process plant; a second element corresponding to a link to process control data associated with a first process control element included in an operating environment of the process plant for receiving real-time data corresponding to a process being controlled within the process plant; and a memory comprising a layout defining a visual representation of the first element and the second element; a display interface application including computer-executable instructions stored in the memory, the computer-executable instructions causing one or more processors to: executing an operator application user interface that presents process control information associated with one or more process control elements operating within the process; receiving the SOP object from the memory; and executing the SOP object to cause the first element and the second element to be presented on a display according to the layout, causing an indication of the process control data associated with the first process control element executing within the operating environment of the process plant to be presented on the display by the second element, and causing one or more SOP process function display elements to be presented in a pop-up window at a first position on the display according to the layout, and causing the pop-up window to be overlaid on the operator application user interface; in response to a move command, moving the pop-up window to a second position within the display, and in response to a selection of one of the one or more SOP process function display elements, executing a corresponding process control function; and a display interface application that causes the operator application system to:

2. the SOP object further comprises a third element corresponding to a process control function associated with the first process control element or a second process control element included in the operating environment of the process plant to affect the process being controlled within the process plant; the layout further defines the visual representation to include the third element with respect to the first element and the second element; 2. The operator application system of claim 1, wherein the computer-executable instructions further cause the one or more processors to execute the SOP object such that the third element is presented on the display according to the layout and, upon selection of the third element, affects the first process control element or the second process control element executing in the operating environment of the process plant.

3. The operator application system of claim 1 or 2, wherein the first process control element is a first field device or a first controller.

4. The operator application system of claim 2 , wherein the second process control element is a second field device or a second controller.

5. 3. The operator application system of claim 2, wherein the link defines where the process control data can be obtained within at least one of a data historian, a database, the first process control element, or the second process control element.

6. The operator application system of claim 2 , wherein the process control data is generated by at least one of the first process control element or the second process control element.

7. The operator application system of claim 1 , wherein the process control data includes at least one of a measurement value, a status value, or a set value.

8. The process control function comprises: activating the first process control element or the second process control element; shutting down the first process control element or the second process control element; or and setting a set point that affects operation of the first process control element or the second process control element.

9. 1. An operator application system for executing a standard operating procedure (SOP) object, said operator application system comprising: a memory configured to store the SOP object, the SOP object comprising: a SOP command display element including a plurality of SOP command steps when monitoring or controlling a process plant; one or more SOP process function display elements, each depicting a process control function that affects one or more process control elements included in the operating environment of the process plant; and a memory comprising: a layout defining a visual representation of one or more SOP process function display elements embedded within the SOP instruction display element, the layout configured to display at least one of the one or more SOP process function display elements adjacent to one of the plurality of SOP instruction steps; a display interface application including computer-executable instructions stored in the memory, the computer-executable instructions causing one or more processors to: displaying an operator application user interface on a display that presents the process control information; receiving the SOP object from the memory; executing the SOP object such that the SOP instruction display element and the one or more SOP process function display elements are presented in a pop-up window at a first position on the display according to the layout, and such that the pop-up window is overlaid on the operator application user interface; Responsive to a move command, moving the pop-up window to a second position within the display; and a display interface application responsive to selection of one of the one or more SOP process function display elements to cause a corresponding process control function to be executed.

10. the SOP object further comprises an SOP process control data display element depicting one or more process control parameter values ​​associated with the one or more process control elements included in the operating environment of the process plant; the layout further defines the visual representation to include the SOP process control data display element embedded within the SOP instruction display element, and is configured such that at least one of the one or more process control parameter values ​​is displayed adjacent to one of the plurality of SOP instruction steps; 10. The operator application system of claim 9, wherein the computer-executable instructions further cause the one or more processors to execute the SOP object and present the SOP process control data display elements on the display according to the layout.

11. An operator application system as described in claim 9 or claim 10, wherein at least one of the one or more process control elements is a field device.

12. The operator application system of claim 10, wherein at least one of the one or more process control elements is a controller.

13. The operator application system of claim 10, wherein the one or more process control parameter values ​​include one or more links to locations where the process control parameter values ​​can be obtained in a data historian, a database, or at least one of the one or more process control elements.

14. The operator application system of claim 10, wherein the one or more process control parameter values ​​are generated by at least one of the one or more process control elements.

15. The operator application system of claim 10, wherein the one or more process control parameter values ​​include at least one of a measurement value, a status value, or a set value.

16. performing the process control function, activating at least one of the one or more process control elements; shutting down at least one of the one or more process control elements; or 10. The operator application system of claim 9, further comprising causing a set point to be set that affects operation of at least one of the one or more process control elements.

17. 1. A configuration system for configuring an SOP object, said configuration system comprising: one or more tangible non-transient memories; one or more processors; and a configuration application including computer-executable instructions stored in the one or more tangible, non-transitory memories, the computer-executable instructions causing the one or more processors to: receiving SOP command information comprising a plurality of SOP command steps when monitoring or controlling a process plant; creating an SOP command display element depicting said SOP command information; receiving SOP process function information including one or more process control functions that affect at least one of one or more process control elements included in an operating environment of the process plant; creating one or more SOP process function display elements, each SOP process function display element depicting a corresponding process control function; receiving a visual representation of the one or more SOP process function display elements embedded within the SOP instruction display element, wherein at least one of the one or more SOP process function display elements is configured to be displayed adjacent to one of the plurality of SOP instruction steps; and a configuration application that configures the SOP object in accordance with the SOP instruction display element, the one or more SOP process function display elements, and layout information so that, upon execution of the SOP object, the SOP instruction display element and the one or more SOP process function display elements are presented in a pop-up window on a display in accordance with the layout information, the pop-up window is overlaid on an operator application, and selection of one or more SOP process function display elements causes execution of the corresponding process control function; a database configured to store the SOP object.

18. The computer-executable instructions further cause the one or more processors to: receiving SOP process control data information including one or more process control parameter values ​​associated with the one or more process control elements; creating an SOP process control data display element depicting the SOP process control data information; 20. The configuration system of claim 17, further comprising: configuring the SOP object according to the SOP instruction display element, the one or more SOP process function display elements, the SOP process control data display element, and the layout information, wherein the layout information further defines a visual representation of the SOP process control data display element embedded within the SOP instruction display element, wherein at least one of the one or more process control parameter values ​​is displayed adjacent to one of the plurality of SOP instruction steps, and wherein upon execution of the SOP object, the SOP process control data display element is presented on the display according to the layout information.

19. 20. The configuration system of claim 18, wherein the computer-executable instructions causing the one or more processors to create the SOP process function display element further comprise computer-executable instructions for configuring the SOP process function display element to display process control parameter values ​​received from at least one of a data historian, the database, or the one or more process control elements.

20. 20. The configuration system of claim 17, wherein the computer-executable instructions that cause the one or more processors to create the one or more SOP process function display elements further comprise computer-executable instructions that configure the one or more SOP process function display elements, upon selection, to send a signal to a function block or control module associated with at least one of the one or more process control elements.

21. The process control function comprises: activating at least one of the one or more process control elements; shutting down at least one of the one or more process control elements; or 21. The configuration system of claim 17, further comprising at least one of: setting a set point that affects operation of at least one of the one or more process control elements.

22. 1. A maintenance system for executing an SOP object, said maintenance system comprising: Memory and one or more processors; 1. A database configured to store a plurality of SOP objects, each of said SOP objects comprising: identifier, a SOP command display element including a plurality of SOP command steps when monitoring or controlling a process plant; one or more SOP process function display elements, each depicting a process control function that affects one or more process control elements included in the operating environment of the process plant; and a database including a layout defining a visual representation of the one or more SOP process function display elements embedded within the SOP instruction display elements, the layout configured such that at least one of the one or more SOP process function display elements is displayed adjacent to one of the plurality of SOP instruction steps; 1. A maintenance application comprising computer-executable instructions stored in a memory, the computer-executable instructions causing one or more processors to: displaying a maintenance application user interface presenting the process control information on a display; receiving instructions to retrieve one of the plurality of SOP objects from the database; obtaining the SOP object from among the plurality of SOP objects having the identifier that matches the instruction; executing the retrieved SOP object such that the SOP instruction display element and the one or more SOP process function display elements are presented in a pop-up window at a first position on a display according to the layout, and the pop-up window is overlaid on the maintenance application user interface; Responsive to a move command, moving the pop-up window to a second position within the display; and in response to a selection of one of the one or more SOP process function display elements, causing execution of the corresponding process control function; and a maintenance application that causes the maintenance system to perform the above.

23. each of the SOP objects further comprising an SOP process control data display element depicting one or more process control parameter values ​​associated with the one or more process control elements included in the operating environment of the process plant; the layout further defines the visual representation to include the SOP process control data display element embedded within the SOP instruction display element, and is configured such that at least one of the one or more process control parameter values ​​is displayed adjacent to one of the plurality of SOP instruction steps; 23. The maintenance system of claim 22, wherein the computer-executable instructions cause the one or more processors to execute the retrieved SOP object and further cause the SOP process control data display elements to be presented on the display according to the layout.

24. 24. A maintenance system according to claim 22 or claim 23, wherein the identifier is associated with the name of the SOP object.

25. 25. A maintenance system according to any one of claims 22 to 24, wherein the identifier is associated with a version of the SOP object.

26. 26. A maintenance system according to any one of claims 22 to 25, wherein the identifier is associated with a version of a configuration application used to create the SOP object.

27. 1. A computer-implemented method for executing an SOP object, the method comprising: receiving, by one or more processors, the SOP object stored in memory, the SOP object comprising: a SOP command display element including a plurality of SOP command steps when monitoring or controlling a process plant; one or more SOP process function display elements, each depicting a process control function that affects one or more process control elements included in the operating environment of the process plant; and receiving a layout defining a visual representation of the one or more SOP process function display elements embedded within the SOP instruction display element, the layout configured to display at least one of the one or more SOP process function display elements adjacent to one of the plurality of SOP instruction steps; executing, by the one or more processors, the SOP object so that the SOP instruction display element and the one or more SOP process function display elements are presented on a display according to the layout, and so that the pop-up window is overlaid on an application user interface.

28. the SOP object further comprises an SOP process control data display element depicting one or more process control parameter values ​​associated with the one or more process control elements included in the operating environment of the process plant; the layout further defines the visual representation to include the SOP process control data display element embedded within the SOP instruction display element, and is configured such that at least one of the one or more process control parameter values ​​is displayed adjacent to one of the plurality of SOP instruction steps; 28. The computer-executable method of claim 27, wherein executing the SOP object causes the SOP process control data display elements to be presented on the display according to the layout.

Images