System and method for graphical display configuration design validation in a process plant - Patents.com
The graphical display configuration system addresses the complexity of operator HMIs in industrial process control systems by enabling local customization of display views, reducing network load and simplifying maintenance, thus improving operator performance and plant efficiency.
Patent Information
- Application Number
- JP2023191294
- Authority / Receiving Office
- JP · JP
- Patent Type
- Patents
- Current Assignee / Owner
- Priority Date
- 2018-09-04
- Filing Date
- 2023-11-09
- Publication Date
- 2024-11-13
- Estimated Expiration
- 2038-10-02
AI Technical Summary
Current operator display configuration architectures in industrial process control systems require significant communication load due to independent management of alarms and real-time data across multiple operator workstations, leading to complex and time-consuming customization and maintenance of operator HMIs, especially with increased process complexity and the need for multiple monitors.
A graphical display configuration system that allows for centralized definition and customization of display views, enabling operators to modify appearances and behaviors locally on workstations without re-downloading configurations, reducing network load and simplifying maintenance.
Facilitates efficient and flexible customization of operator HMIs across multiple workstations, reducing communication load and simplifying maintenance while adhering to ergonomic standards, thereby enhancing operator performance and plant efficiency.
Smart Images

Figure 0007583142000001 
Figure 0007583142000002 
Figure 0007583142000003
Abstract
Description
[Technical field]
[0001] CROSS-REFERENCE TO RELATED APPLICATIONS This application claims the benefit of priority to and the filing date of U.S. Provisional Patent Application No. 62 / 566,679, entitled "Systems And Methods For Graphical Display Configuration and Usage in Process Control Plants," filed October 2, 2017, the entire disclosure of which is expressly incorporated herein by reference.
[0002] The present disclosure relates generally to process control systems, and more specifically, to systems and methods for configuring graphics utilized by operators to view and respond to real-time conditions within the operation of an on-line industrial process plant. [Background technology]
[0003] Distributed process control systems are used within chemical, pharmaceutical, petroleum, oil and gas, metals and mining, pulp and paper, or other types of industrial process plants to control one or more industrial processes to thereby generate or produce one or more physical products from raw materials and / or other types of ingredients. Thus, 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 bus, a digital bus, or a mixed analog / digital bus, or via a wireless communication link or network. The field devices, which may be, for example, valves, valve positioners, switches, and transmitters (e.g., temperature, pressure, level, and flow rate sensors), are located within the process environment and generally perform physical or process control functions, such as opening or closing a valve or measuring a process parameter, 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. Process controllers are also typically located within the plant environment and execute controller applications that run different control modules that receive signals indicative of process measurements made by sensors or field devices and / or other information related to the field devices, e.g., make process control decisions and generate control signals based on the received information, and interface with the control modules or blocks embodied in the field devices, such as HART®, Wireless HART®, and FOUNDATION® Fieldbus field devices. The control modules of the controllers 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.
[0004] Information from the field devices and controllers is usually made available over a data highway 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, typically, but not always, located in a control room or other location away from the more hostile plant environment. Each of these hardware devices typically, but not always, operates across the process plant or within a portion of the process plant. The hardware devices run applications that may enable operators to, for example, view the current state and operation of processes running in 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 a process for purposes of training personnel or testing process control software, maintain and update configuration databases, and perform other functions related to controlling the process and / or operating 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.
[0005] As an example, the DeltaV™ control system, sold by Emerson, includes multiple applications stored in and executed by different user interface devices located at various locations within the process plant and, in some cases, remotely from the process plant. Each of these applications provides a user interface (UI) to enable a user (e.g., a configuration engineer, an operator, a maintenance technician, etc.) to view and / or modify aspects and configurations of the process plant operations. Throughout this specification, the phrase "user interface" or "UI" is used to mean an application or screen that enables a user to view or modify the configuration, operation, or status of the process plant. Similarly, the phrase "user interface" or "UI" is used herein to mean the device on which the user interface operates, whether the device is fixed (e.g., a workstation, a wall-mounted display, a process control device display, etc.) or portable (e.g., a laptop computer, a tablet computer, a smartphone, etc.).
[0006] Configuration applications residing within one or more user workstations or computing devices contained within the configuration environment of the process plant enable configuration engineers and / or other types of users to create or modify process control modules and download these process control modules via a data highway to dedicated distributed controllers operating within the operational environment of the process plant (also referred to interchangeably herein as the "operational environment" of the process plant) to control one or more processes during run-time or real-time operation. Typically, these control modules are comprised 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 in some cases, one or more field devices, stores and executes a respective controller application that executes the downloaded control modules assigned to them to implement the actual process control functions.
[0007] The configuration application also enables configuration engineers and / or other users to create or modify an operator man-machine interface (HMI) or display view that is used by the operator viewing application to display data (e.g., as data is generated in real-time during run-time operation of the process plant) to an operator and to enable the operator to modify various settings, such as set points, within the process control routines during run-time operation. The operator viewing application that provides the operator HMI or display view may be one or more computing devices contained within the process plant's operational environment (or on one or more computing devices communicatively connected to the operator workstations and data highways). The controller application may run on one or more of the user interface devices (e.g., an operator workstation, an operator tablet, an operator mobile device, etc.). The operator HMI or display view receives data from the controller application via the data highway and displays this data to the operator or other user using a UI in a user interface. Similarly, the operator HMI or display view may also receive data (e.g., real-time data) from other control components or elements contained within the process plant's operating environment other than the control modules, such as controllers, process controllers, field devices, I / O cards or devices, other types of hardware devices, units, areas, etc. The data historian application is typically stored in and executed by a data historian device that collects and stores some or all of the data provided across the data highway, while the configuration database application may run in yet another computer attached to the data highway to store the current process control routine configuration, the current operator display configuration, and the data associated therewith. Alternatively, the configuration database may be located on the same workstation as the configuration application.
[0008] As noted above, operator viewing applications typically execute within one or more of the operator user interface devices and provide an operator HMI or display view to an operator or maintenance personnel 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 24 / 7 operation, for example) of processes running within the process plant to view and respond to real-time conditions within the process 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 display the operational status of controllers and other devices within the process plant, maintenance displays that display the operational status of devices within the process plant, and the like. Display views typically execute within the run-time or real-time operating environment of the process plant and are generally configured to present information or data received from process control modules, devices, and / or other control objects also operating within the run-time or real-time operating environment of the process plant in a known manner. In some known systems, the display view has graphical elements (e.g., graphical representations or graphics) associated with physical or logical elements contained within the operating environment and communicatively coupled to the physical or logical elements to receive data regarding and updates thereto over time, e.g., during run-time operation of the process plant. The graphical element may be configured or defined to dynamically change its appearance on the display screen based on received data, e.g., to illustrate that a tank is half full, to illustrate the flow measured by a flow sensor, etc.In this manner, as data provided by physical or logical elements within the process plant's operating environment changes over time (e.g., is repeatedly or continuously updated over time), the appearance of the corresponding graphical elements is changed accordingly on the display screen.
[0009] In some currently known operator display configuration architectures for industrial process control systems, each operator workstation independently manages its own alarms and accesses real-time control data generated by process control modules, devices, and / or other control objects. In this manner, the operator HMI or display view for a particular operator workstation can be customized. To customize the display view, custom graphical properties, values, and / or configurations of the various display view elements (e.g., graphical and other types of elements) that will be presented on the runtime display view are defined and associated with the display view in the graphical composition environment, and the display view definition or configuration is downloaded from the composition environment into a particular operator workstation of the operating environment for execution. Often, custom scripts are programmed into the display view's configuration such that the desired behavior and / or appearance of the various display view elements and / or the display view itself is executed on the particular workstation. In addition, if it is desired that the display view appearance or behavior be modified or changed for a particular operator workstation, typically the modifications must be applied to the display view's configuration in the graphical composition environment, and then the modified configuration must be downloaded from the composition environment for execution on the particular operator workstation. In most cases, this requires that the particular operator workstation finishes its execution of the current display view in order for the modified display view configuration to be received and executed on the particular operator workstation.
[0010] In other current operator display configuration architectures for industrial process control systems, a common configuration for a display view is downloaded from a graphical configuration environment to multiple operator workstations. Even during run-time, to enable a particular customized appearance and / or behavior of a display view at a particular operator workstation, the particular operator workstation on which the display view is executing must query or otherwise communicate with the graphical configuration environment to obtain the necessary information (the particular configuration of various graphics, run-time values, and / or other information) to enable or implement the desired customized appearance and / or behavior of the display view at the particular operator workstation. Because modern process plants can include hundreds of operator workstations, messages sent or received between the operator workstations and a back-end display configuration server add a significant load to the process plant communication network.
[0011] Recently, the Center for Operator Performance (COP), a research consortium that overcomes human capabilities and limitations in industrial process control operating environments through research, collaboration, and ergonomics, and the International Society of Automation (ISA) have conducted research to help advance industrial process control system man-machine interfaces (HMIs) and their usability, for example, by proposing human-centered design (HCD) improvements and guidelines. For example, the American National Standard ANSI / ISA-101.01.-2015, entitled "Human Machine Interfaces for Process Automation Systems" and approved on July 9, 2015, addresses "the principles, design, implementation, operation, and maintenance of human-machine interfaces (HMIs) for process automation systems involving multiple work processes throughout their life cycle...The standard defines evolving terminology and models and HMIs within work processes that are recommended for effectively maintaining the HMIs throughout their life cycle" (ANSI / ISA-101.01-2015, page 9). Summary of the Invention
[0012] As described above, generally speaking, an operator man-machine interface (HMI) or display view is a system that allows an operator to view and respond to conditions within the process and / or process plant during run-time operation of the process. Operator HMIs are used by operators to display information to process control systems. The effectiveness of a process plant operator in safely and effectively operating a process, as well as in detecting and responding to various process and process plant conditions, depends in large part on how well the operator HMI or display view is designed (e.g., by a configuration engineer or other operator HMI designer). However, recent changes in how industrial process plants are operated have a significant impact on the design of operator HMIs. For example, continuing competitive pressures in the process control industry have led to a significant expansion of the scope of the portion of a process for which a single operator is responsible. With this expansion, the number of process graphics that a single operator must monitor and utilize to run a process safely and efficiently has increased several fold. In fact, in today's process plants, operators are typically expected to navigate through hundreds of process graphics. In addition, trends such as increased plant equipment information and more automation and advanced control logic in the process control industry have led to a significant increase in the level of complexity of the portion of a process for which a single operator is responsible.
[0013] Furthermore, a workspace utilized by a single operator may include one to many consoles or monitors of various sizes. The number and size of monitors and / or consoles is often determined by the size and complexity of the portion of the process being monitored by the operator. In addition, when an operator's workspace includes multiple monitors, each monitor typically has a custom layout defined for each monitor's respective monitor size, position, and portion of the process being monitored. For example, the custom layout defines what displays are open on which monitor, how displays on different monitors interact with each other, etc.
[0014] Furthermore, in practice, when no two process plants or operational segments within a plant are alike, each process plant often develops and designs its own custom operating principles, graphics, and / or graphical standards for efficient operation. Thus, operator HMI graphics, strategies, designs, layouts, navigation, and / or operator actions can be highly custom configured for different operational segments and / or different process plants.
[0015] These and other factors have always made the job of configuration engineers who design operator HMIs difficult. Often, configuration engineers must create complex program extensions to customize or enhance various capabilities for a particular operation segment and / or plant. Typically, configuration engineers must utilize programming languages such as Visual Basic or C, and / or other custom programs to create the desired operator HMI. This results in complex operator HMI suites that are difficult and time-consuming to develop, extend, repair, and maintain.
[0016] At least some of the aspects of the novel graphical display configuration and usage systems and methods disclosed herein solve these and other modern HMI challenges and provide a platform for industrial process control HMI design and usage that is not only flexible, easy to use, and easy to maintain, but also helps engineers design and implement process plant operating environment HMIs in light of current process automation HMI standards and best practices.
[0017] In one embodiment, a graphical display configuration and use system for an industrial process plant (also referred to interchangeably herein as a "graphical configuration system" or a "graphical configuration and use system") is a graphical display configuration and use system for an industrial process plant that executes within a configuration environment of the process plant. Graphical display configuration applications include a user interface through which various operator HMI or display views can be created, defined, designed, and / or published, e.g., by a configuration engineer. The configured or defined display views, when downloaded and executed within the process plant's operational or operating environment, provide an operator or other user with real-time (e.g., continuously or repeatedly updated) operational states and statuses of various components and operations associated with the process. As such, the display views typically include respective links between one or more display view elements presented on the display view and one or more control modules, devices, or control objects executing to control the process within the process plant's operational environment, such that upon download and execution of a published configuration of the display view at a user interface device (e.g., an operator workstation, a remote computing device, a mobile device, etc.) communicatively coupled to the process plant's operational environment, respective representations of one or more values or other data provided or generated by one or more control modules, devices, or control objects during execution within the process plant's operational environment are presented and repeatedly updated, e.g., via the linked display view elements, on the running display view.
[0018] The graphical display configuration system also includes a centralized configuration database or library that stores published configurations or definitions of display views and published configurations or definitions of display view elements that are available to be included on or otherwise associated with various display views. In some embodiments, the centralized configuration database or library also stores draft configurations or definitions of the display views and / or display view elements. Examples of display view elements include graphics, properties, control modules, devices, objects and / or links to other control components or elements disposed within the operating environment, global variables, parameters, areas or subsections of the display view, and / or other elements and / or portions of the display view. In one example, for a particular display view, the centralized configuration database or library stores the published configuration of the particular display view and optionally one or more working or draft configurations of the particular display view. The published configuration of the particular display view may include one or more published configurations of various display views for displaying on the running display view, and the published display view configurations are available for download and execution within the operating environment of the process plant. Meanwhile, one or more working or draft configurations of a particular display view are excluded from downloading and execution within the operational environment of the process plant, i.e., the working or draft configurations of the display views and display view elements are prevented from being downloaded and executed within the operational environment of the process plant and instead are maintained within the configuration environment, e.g., for editing, modification, testing, etc.
[0019] The published configuration or definition of a particular display view may include one or more user controls, through which operators or users of user interface devices included within the operational environment of the process plant may modify the appearance of the display view running online at their respective user interface devices during run-time operation. For example, an operator may modify, through one or more user controls at their respective user interface devices, the appearance of a graphic, properties of a graphic, areas of a display view, properties and / or contents of areas of a display view, the position of a graphic on a display view, the particular data derived from a control module, device or control object to be displayed, and the like. The graphics configuration system may modify the appearance of the display view, the graphics data, and / or other appearance of elements, areas, or portions of the running display view. Notably, the graphics configuration system allows changes to the appearance of a display view running within the operating environment to be implemented at the operator workstation based solely on the contents of the published configuration or definition of the display view running at the operation workstation. That is, the downloaded and published configuration of the display view allows an operator to customize or modify the appearance of the display view at the operator's workstation while running online within the operating environment without requiring the display view to stop running, without requiring the display view to download a different configuration of the display view, and without requiring the display view and / or the operator workstation to retrieve data from the configuration environment to implement the desired changes.
[0020] Thus, when the published configuration or definition of a particular display view is downloaded to multiple user interface devices or operator workstations included within the process plant's operating environment, each operator or user can customize or modify the local appearance of the instance of the display view running on his or her workstation, independent of the other operators or users, and without his or her workstation communicating with the graphical display configuration application and configuration library. Some of the operator-initiated modifications or customizations may be implemented in a mutually exclusive manner on a particular workstation, e.g., the fill property of a graphic is selected by the operator to be either gray or blue, but not both gray and blue. Some of the modifications may not be mutually exclusive on a particular workstation (e.g., the modifications may be applied cumulatively or independently), such as when the operator drags and drops a graphic depicting a particular control element that the operator wants to actively (and easily) monitor into an Active Monitor or Watch window included on the display.
[0021] In one embodiment, a method for configuring a graphical display of run-time or real-time operations of a process plant includes receiving a definition of a display view via a user interface of a graphical display configuration application executing within a configuration environment of the process plant. The display view typically includes various graphical elements that represent respective control modules, devices, and / or other control components (also referred to interchangeably herein as control elements or control objects) that execute or operate within the operational environment of the process plant to control at least a portion of a process, such as, for example, controllers, process controllers, field devices, I / O cards or devices, other types of hardware devices, units, areas, etc. The display view definition thus defines links between the graphical elements presented on the display view and the control components or objects, such that upon download and execution of the display view within the operational environment of the process plant, one or more values or other data generated by the control components or control objects while executing within the operational environment of the process plant to control a process are presented and repeatedly updated on the running display view via the linked graphical elements. The graphical elements may be, for example, graphics that show or represent a particular control module, device, or other control component or object.
[0022] In addition, a display view definition typically includes a set of variables that define the graphics, text, properties of the graphics and / or text (e.g., color, contrast, animation, etc.), global variables, parameters, different areas of the display view, display and / or definitions of each of the various other graphical portions, elements, or components (and / or combinations thereof) that may be included on and / or otherwise associated with the display view, such as the respective properties and / or content of different areas of the play view, the different locations of various graphics, text, and / or areas on the display view, and / or specific operational data derived from control modules, devices, and / or other control objects and their binding to the respective graphics or other elements on the display view, etc. Other such graphical portions, elements, and / or components that may be included on and / or otherwise associated with the display view may include, for example, display view hierarchy, display view layout, timers, embedded links, animation conversion functions, data references, project or plant standards, display themes, content language and / or their representation, application language and / or their representation, tab areas on the display view, tooltips and / or other annotation representations, trends and other representations of historical parameters, gaze or active monitoring areas, and / or other features, aspects, and / or functions provided by the present graphical configuration and use systems and methods described herein.Still other graphical portions, elements, and / or components that may be included on and / or otherwise associated with the display view may include custom and / or default Graphic Element Module (GEM) configurations (such as those described in commonly owned U.S. patent application Ser. No. 15 / 692,450, entitled "Derived and Linked Definitions with Override," filed Aug. 31, 2017) and / or operator display switching preview configurations and / or objects associated therewith (such as those described in commonly owned U.S. patent application Ser. No. 15 / 243,176, entitled "Operator Display Switching Preview," filed Aug. 22, 2016).
[0023] At least for ease of reading this specification, such graphical portions, elements, or components (and combinations thereof) that are included on and / or otherwise associated with a display view are generally referred to herein interchangeably as “graphical display view elements,” “graphical elements,” “graphical components,” “display view elements,” “display elements,” or “display view components.” Typically, each display view element may be defined by or composed using its own separate object, which may be created, modified, stored, and published via the graphical composition and usage systems and methods described herein.
[0024] Some of the display element definitions may define mutually exclusive choices, for example, that overall color theme of a display view may be selectively changed by the operator between various defined color themes, or the language used on the display view may be switched by the operator between Arabic and French. Some of the display view element definitions may not be mutually exclusive, such as when the operator drags and drops a graphic showing a particular control element that the operator wants to actively (and easily) monitor into an active monitor or watch window included on the display.
[0025] With particular reference to a display view configuration or definition that defines a plurality of properties that are selectable within the operational environment in a mutually exclusive manner for application to a particular portion of an active display view, the method includes, via a user interface of a graphical display configuration application included within the operational environment of a process plant and configured to select the display view. The method includes receiving an indication of a selection of a subset of a plurality of user interface devices (e.g., operator workstations) to which a respective instance of the display view definition will be downloaded for execution. The selected subset of user interface devices may include more than one user interface device, if desired. The method downloads the display view definition (the published definition) into each user interface device included within the selected subset of user interface devices for execution within the operational environment of the process plant, thereby allowing specific portions of the running display view to be selectively modified independently at each user interface device in a mutually exclusive manner among the multiple properties. Thus, each user interface device implements its respective change based solely on the content of the downloaded definition of the display view running at the user interface device and without communicating with any other devices included within the configuration environment of the process plant to activate or implement the change. Thus, a first operator may select "blink" for a particular property of a particular graphic to be included on the display view of his workstation, while another operator may select "no blink" for a particular property of a particular graphic to be included on the display view of his workstation. Both options are fully supported and implemented solely by the respective downloaded definitions of the display views running on the workstation, without requiring stopping execution of the display view on the workstation, without requiring downloading different configurations of the display view to the workstation, and without the display view and / or the operator workstation retrieving data or other information from a configuration environment to implement the desired changes.
[0026] It should be noted that while the disclosure herein refers to graphical display views and graphical display view elements, this is for illustrative and discussion purposes only and is not meant to be limiting. Indeed, any one or more of the aspects discussed herein with respect to graphical display views may be readily applied to, for example, a graphical element module (GEM) class. Similarly, any one or more of the aspects discussed herein with respect to graphical display view elements may be readily applied to, for example, a GEM. As is commonly known, a GEM is a linked graphically configurable shape that is reusable and can be combined with other shapes and / or behaviors. Typically, a GEM provides one or more visual representations or views of a configurable shape, and the definition or configuration of a GEM is stored separately from the definition or configuration of a use / instance of the GEM in a particular display view and other objects (e.g., to enable sharing of the GEM definition / configuration). Thus, the graphical configuration system and method described herein and any one or more aspects thereof may be readily applied to GEMs and GEM classes. [Brief description of the drawings]
[0027] [Figure 1A] FIG. 1 is a block diagram of a distributed process control network located within a process plant including the graphics configuration and use system and method of the present disclosure. [Figure 1B] FIG. 1B is a block diagram of an example of a user interface device as generally illustrated in FIG. 1A. [Figure 2A] FIG. 1B is a block diagram of an example implementation of a graphical display configuration and use system within a configuration environment and an operating environment of a process plant, such as the process plant of FIG. 1A. [Figure 2B] FIG. 2B is a block diagram of an example implementation of a graphical configuration library that may be included within the graphical configuration and use of the system of FIG. 2A. [Figure 2C]2B illustrates a block diagram of an example of a snapshot during ongoing configuration of a display view using the graphical configuration and use system of FIG. 2A; [Figure 3A] 1 illustrates an example view of a graphical display composition application for defining graphics and an example view of an operator application for presenting the graphics according to the definition from the graphical display composition application. [Figure 3B] 1 is an example of a detailed view of a graphical display configuration application for defining graphics. [Figure 4A] 1 illustrates a flow diagram of an example method for assessing the completeness of a target graphical display view of a process control system. [Figure 4B] 1 illustrates an example of a completeness assessment of a target graphical display view of a process control system that may be provided by a graphical display configuration application. [Figure 4C] 1 illustrates an example of a completeness assessment of a target graphical display view of a process control system that may be provided by a graphical display configuration application. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS
[0028] 1A is a block diagram of a representative process control network or system 2 operating within a process control system or process plant 10 that includes and / or may utilize embodiments of the novel graphical display configuration and use system described herein. The process control network or system 2 may include a network backbone 5 that provides direct or indirect connectivity between various other devices. The devices coupled to the network backbone 5, in various embodiments, 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., to the Internet), one or more user interface (UI) devices 8 that may be fixed (e.g., traditional operator workstations) or portable (e.g., mobile device smartphone) computing devices, one or more servers 12 (e.g., may be implemented as a bank of servers, a cloud computing device, or another suitable configuration), 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 in combination. 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. The controller 11 may include a processor 30, a memory 32, and one or more control routines 38. Although FIG. 1A illustrates only a single one of several of the devices directly and / or communicatively connected to the network backbone 5, it will be understood that each of the devices may have multiple instances on the network backbone 5, and indeed the process plant 10 may include multiple network backbones 5.
[0029] The UI device 8 may be communicatively connected to the controller 11 and the wireless gateway 35 via the network backbone 5. The controller 11 may be communicatively connected to the wired field devices 15-22 via input / output (I / O) cards 26 and 28, and 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 or continuous process using at least some of the field devices 15-22 and 40-50. The controller 11, which may be, by way of example, a DeltaV™ controller sold by Emerson, is communicatively connected to the process control network backbone 5. The controller 11 may also be communicatively connected to the process control network backbone 5, for example. , standard 4-20 mA devices, I / O cards 26, 28, and / or any desired hardware and software associated with any smart communication protocol, such as the FOUNDATION® Fieldbus protocol, the HART® protocol, the Wireless HART® protocol, etc.
[0030] In operation of the UI device 8, the UI device 8, in some embodiments, may execute a user interface ("UI") that allows the UI device 8 to receive input via an input interface and provide output to a display. The UI device 8 may receive data (e.g., process-related data, such as process parameters, log data, sensor data, and / or any other data that may be captured and stored) from the server 12. In other embodiments, the UI may execute in whole or in part on the server 12, which may transmit display data to the UI device 8. The UI device 8 may receive UI data (which may include display data and process parameter data) from other nodes in the process control network or system 2, such as the controller 11, the wireless gateway 35, and / or the server 12, via the backbone 5. Based on the UI data received at the UI device 8, the UI device 8 provides output (i.e., visual representations or graphics, some of which may be updated during run-time) that represent aspects of a process associated with the process control network or system 2 that allows a user to monitor the process. A user may also affect control of the process by providing input to the UI device 8. To illustrate, the UI device 8 may provide graphics depicting, for example, a tank filling process. In such a scenario, a user may read a tank level measurement and determine that the tank needs to be filled. The user may interact with an inlet valve graphic displayed on the UI device 8 to input a command to cause the inlet valve to open.
[0031] In certain embodiments, the UI device 8 may implement any type of client, such as a thin client, a web client, or a thick client. For example, the UI device 8 may rely on other nodes, computers, UI devices, or servers for the bulk of the processing required for the operation of the UI device 8, when the UI device is limited in memory, battery power, etc. (e.g., in a wearable device). In such an example, the UI device 8 may communicate with the server 12 or another UI device, which may communicate with one or more other nodes (e.g., servers) on the process control network or system 2 and determine display data and / or process data to send to the UI device 8. Additionally, the UI device 8 may pass any data associated with received user input to the server 12 so that the server 12 may process and act accordingly on the data associated with the user input. In other words, the UI device 8 may act as a portal to one or more nodes or servers that do a little more than render graphics, store data, and execute routines necessary for the operation of the UI device 8. A thin-client UI device offers the advantage of minimal hardware requirements for the UI device 8.
[0032] In other embodiments, the UI device 8 may be a web client. In such embodiments, a user of the UI device 8 may interact with the process control system through a browser on the UI device 8. The browser allows the user to access data and resources of another node or server 12 (such as server 12) through the backbone 5. For example, the browser may receive UI data, such as display data or process parameter data, from the server 12, allowing the browser to render graphics for controlling and / or monitoring some or all of the process. The browser may also receive user input, such as a mouse click on a graphic. User input may be displayed on the browser, such as a mouse click on a graphic. A mouse click may cause the browser to retrieve or access information resources stored on the server 12. For example, a mouse click may cause the browser to retrieve (from the server 12) and display information pertaining to the graphic that was clicked.
[0033] In yet other embodiments, the bulk of the processing for UI device 8 may be performed on UI device 8. For example, UI device 8 may execute the UIs described above. UI device 8 may also store, access, and analyze data locally.
[0034] In operation, a user may interact with the UI device 8 to monitor or control one or more devices in the process control network or system 2, such as any of the field devices 15-22 or devices 40-50. A user may interact with the UI device 8 to, for example, modify or change parameters associated with a control routine stored in the controller 11. The processor 30 of the controller 11 implements or oversees one or more process control routines (stored in memory 32), which may include a control loop. The processor 30 may communicate with the field devices 15-22 and 40-50, as well as other nodes communicatively connected to the backbone 5. It should be noted that any control routine or module described herein (including quality prediction and fault detection modules or function blocks) may have portions thereof implemented or performed by different controllers or other devices, if desired. Similarly, the control routines or modules described herein that are to be implemented in a process control system may take any form, including software, firmware, etc. The control routines may be implemented in any desired software format, such as using object-oriented programming, ladder logic, sequential function charts, functional block diagrams, or using any other software programming language or design paradigm. In particular, the control routines may be defined and 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) of the controller 11. 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 of the controller 11. Thus, the controller 11 may be configured (in certain embodiments, by a user using the UI device 8) to implement (e.g., receive, store, and / or execute) a control strategy or control routine in any desired manner.
[0035] In some embodiments of the UI device 8, a user may interact with the UI device 8 to define and implement a control strategy in the controller 11 using what are commonly referred to as function blocks, each of which is an object or other portion (e.g., a subroutine) of an overall control routine that operates in conjunction with other function blocks (through communications called links) to implement a process control loop within the process control system. Control-based function blocks typically perform one of the following functions: an input function, such as those associated with a transmitter, sensor, or other process parameter measurement device; a control function, such as those associated with a control routine that implements control, such as PID, fuzzy logic, etc.; or an output function that controls the operation of some device, such as a valve, to perform some physical function within the process plant 10. Of course, hybrid and other types of function blocks exist. The function blocks may have a graphical representation provided on the UI device 8, allowing a user to easily modify the function blocks, the connections between the function blocks, and the inputs / outputs associated with each of the function blocks implemented within the process control system. The function blocks can be downloaded to, stored in, and executed by the controller 11, which typically consists of function blocks for standard 4-20 mA devices and some types of smart field devices such as HART devices. The control routines 38 may be used or associated with a fieldbus device, or may be stored in and implemented by the field device itself, which may be the case with 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 of the function blocks.
[0036] 1A, the wireless field devices 40-46 communicate within the wireless network 70 using a wireless protocol such as the WirelessHART protocol. In certain embodiments, the UI device 8 may be able to communicate 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, which are also configured to communicate wirelessly (e.g., using a wireless protocol). To communicate with one or more nodes 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 may conform to any other desired standard or protocol, such as any wired or wireless protocol, including any standard or protocol developed in the future.
[0037] The wireless gateway 35 may provide access to various wireless devices or nodes 40-46, 52-58 of the wireless communication network 70. In particular, the wireless gateway 35 provides a communicative coupling between the wireless devices 40-46, 52-58 and other nodes of the process control network or system 2 (including the controllers of FIG. 1A). In one implementation, the wireless gateway 35 provides a communicative coupling by tunneling through shared layers of the wired and wireless protocol stacks, and in some cases by providing routing, buffering, and timing services (e.g., address translation, routing packet segmentation, prioritization, etc.) to lower layers of the wired and wireless protocol stacks. In other cases, the wireless gateway 35 may translate commands between wired and wireless protocols that do not share any protocol layers.
[0038] Like the wired field devices 15-22, the wireless field devices 40-46 of the wireless network 70 may perform a physical control function within the process plant 10, such as opening or closing a valve or taking a measurement of a process parameter. However, the wireless field devices 40-46 are configured to communicate using the wireless protocol of the network 70. In this manner, the wireless field devices 40-46, the wireless gateway 35, and the other wireless nodes 52-58 of the wireless network 70 are producers and consumers of wireless communication packets.
[0039] In some scenarios, the wireless network 70 may include non-wireless devices 48, 50, which may be wired devices. For example, the field device 48 in FIG. 1A may be an old 4-20 mA device, and the field device 50 may be a traditional wired HART device. To communicate with the network 70, the field devices 48 and 50 may connect to the wireless communication network 70 via respective wireless adapters (WA) 52a, 52b. In addition, the wireless adapters 52a, 52b may support other communication protocols, such as Foundation® Fieldbus, PROFIBUS, DeviceNet, etc. Furthermore, the wireless network 70 may include one or more network access points 55a, 55b, which may be separate physical devices in the wired communication including the wireless gateway 35, or may be provided with the wireless gateway 35 as an integrated device. The wireless network 70 may also include one or more routers 58 to route packets from one wireless device to another in the wireless communication network 70. The wireless devices 40-46 and 52-58 are connected to the wireless links 6 of the wireless communication network 70. 0, they can communicate with each other and with the wireless gateway 35.
[0040] In certain embodiments, 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 Telecommunications Union Radiocommunication Sector) compliant protocols, short wavelength wireless communications such as Near Field Communication (NFC) and Bluetooth, and / 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 that supports a different wireless protocol than the wireless network 70. In some embodiments, the UI device 8 communicates over the process control network or system 2 using the wireless access points 7a. In some scenarios, in addition to portable computing devices, one or more process control devices (e.g., controller 11, field devices 15-22, or wireless devices 35, 40-46, 52-58) may also communicate using the wireless network supported by access point 7a.
[0041] 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. In such an embodiment, the UI device 8 may be used to control, monitor, or otherwise communicate with the external systems. Typically, such systems are consumers and / or providers of information generated or manipulated by the process control system. For example, a plant gateway node 7b may communicatively connect the immediate process plant 10 (having its own respective process control data network backbone 5) with another process plant, which has its own respective network backbone. In one embodiment, a single network backbone 5 serves multiple process plants or process control environments.
[0042] In another example, the plant gateway node 7b may communicatively connect the immediate process plant to an older or prior art process plant that does not include the process control network or system 2 or backbone 5. In this example, the plant gateway node 7b may convert or translate messages between a protocol utilized by the process control big data backbone 5 of the plant 10 and a different protocol utilized by the older system (e.g., Ethernet, Profibus, Fieldbus, DeviceNet, etc.). In such an example, the UI device 8 may be used to control, monitor, or otherwise communicate with a system or network within the older or prior art process plant.
[0043] 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 rotation database, a material handling management system, a maintenance management system, a product inventory control system, a production planning system, a weather data system, a shipping and handling system, a packaging system, the Internet, another provider's process control system, and / or other external systems. The external system gateway node 7c may, for example, provide communication between the process control system and personnel outside the process plant (e.g., personnel at home). It may facilitate communication.
[0044] 1A illustrates a single controller 11 with a finite number of field devices 15-22, 40-46, and 48-50 communicatively connected thereto, but this is merely an exemplary and non-limiting embodiment. Any number of controllers 11 may be included within the process control network or system 2, and any of the controllers 11 may communicate with any number of wired or wireless field devices 15-22, 40-50 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 communications networks 70, access points 7a, and / or gateways 7b, 7c.
[0045] FIG. 1B illustrates a block diagram of one example of a UI device 8 that may be utilized in conjunction with an embodiment of the novel graphical display configuration and usage system described herein. The UI device 8 may be a desktop computer, such as a conventional operator workstation, a control room display, or a mobile computing device, such as a laptop computer, a tablet computer, a mobile device, a smart phone, a personal digital assistant (PDA), a wearable computing device, or any other suitable client computing device. The UI device 8 may execute graphical display configuration applications utilized by configuration engineers in a configuration environment to create, generate, and / or edit various display view definitions or configurations, as well as to create, generate, and / or edit various display view element definitions or configurations. The UI device 8 may also execute operator applications utilized by operators to monitor, observe, and react to various statuses and conditions of processes in the operating environment. The UI device 8 may include a display 72. Additionally, UI device 8 includes one or more processors or CPUs 75, memory 78, random access memory (RAM) 80, input / output (I / O) circuitry 82, and communication units 85 for transmitting and receiving data over a local area network, a wide area network, and / or any other suitable network, which may be wired and / or wireless. UI device 8 may be in communication with controller 11, server 12, and / or any other suitable computing device.
[0046] The memory 78 may include an operating system 88, applications running on the operating system 88, such as a graphical display configuration application and an operator application, as well as a control unit 90 that controls the display 72 and communicates with the controller 11 to control the on-line operation of the process plant. In some embodiments, the server 12 may send a graphical representation of a portion of the process plant to the UI device 8, and the control unit 90 may then cause the graphical representation of the portion of the process plant to be presented on the display 72. Additionally, the control unit 90 may obtain user input from the I / O circuitry 82, such as user input from an operator or configuration engineer (also referred to herein as a user), and translate the user input into a request to present a graphical display view in a particular language, a request to include graphics showing a particular control element in an active monitor or watch window to be included on the display view, a request to display an adjustment to a process parameter to be included in one of the process sections, etc.
[0047] In some embodiments, the control unit 90 may communicate the translated user input to the server 12, which may generate and send the requested UI to the UI device 8 for display. In other embodiments, the control unit 90 may generate a new UI based on the translated user input and present the new UI on the display 72 of the UI device 8. When the translated user input is a request to display an adjustment to a process parameter included within one of the process sections, the control unit 90 may adjust the process parameter value on the display 72 according to the user input from the operator and provide instructions to the controller 11 to adjust the process parameter within the process plant. In other embodiments, the control unit 90 may communicate the translated user input to the server 12, which may generate and transmit the adjusted process parameter value to the UI device 8 for display and provide instructions to the controller 11 to adjust the process parameter within the process plant.
[0048] 2A illustrates a high-level block diagram illustrating one possible manner of implementing embodiments and / or aspects of the graphical display configuration and use system 100 described herein within the configuration environment 102 and operation or operational environment 105 of a process plant or process control system, for example, of the process plant 10 of FIG. 1A. The configuration environment 102 of the process control system is referred to interchangeably herein as the "offline" environment 102 or "back-end" environment 102 of the process control system, and the operational environment 105 of the process control system is referred to interchangeably herein as the "operation," "online," "front-end," or "field" environment 105 of the process control system.
[0049] As illustrated in FIG. 2A, the configuration environment 102 includes a graphical display configuration application 110 that includes a user interface through which a configuration engineer or user may create, generate, and / or edit various display view definitions or configurations 112 and create, generate, and / or edit various display view element definitions or configurations 115. For example, the graphical display configuration application 110 may execute on an instance of the user device 8 of FIG. 1A and / or 1B. Each display view configuration 112 and each display view element configuration 115 may be implemented, for example, as a respective object. Generally speaking, a display view definition 112 may be configured to include one or more display element definitions 115 (among other components). Typically, a display view definition 112 is configured to include at least one display element (e.g., a graphical element) that is linked to a particular control module, device, or other type of control object such that runtime data associated with the particular control module, device, or control object in the operating environment 105 may be represented via the linked display element on the running display view, for example, in a continuous or recurring update manner. A particular control module, device, or control object is typically defined in a control configuration database 118 (e.g., its configuration is stored in the control configuration database 118) and may be represented in the display view definition 112, for example, by a designated control tag or other suitable indicator. As shown in Figure 2A, display view related definitions or configurations 112, 115 are stored in a centralized graphical configuration database or library 120 such that the graphical display related configurations 112, 115 are available for download and execution within the operating environment 105, thereby enabling an operator or user to monitor, observe, and react to various statuses and conditions of processes within the operating environment 105.It should be noted that while the graphical configuration database 120 and the control configuration database 118 are illustrated in FIG. 2A as separate databases within the configuration environment 102 of the process control system 10, in some implementations at least a portion or all of the configuration databases 120, 118 may be implemented together as a single database or library.
[0050] At least in FIG. 2A , a display view configuration 112 may be defined to specify one or more control objects 118 to be associated with or coupled to each display view element 115 included on the display view 112, and then: The definitions of the display view elements 115 and their respective associated control objects 118 are instantiated and provided (e.g., downloaded) to one or more different operator workstations or user interface devices 122 included within the operational environment 105 of the process plant 10. In one example, the user interface devices or workstations 122 take the form of the user interface devices 8 of FIG. 1B. The instantiated display views 112 executing on the user interface devices 122 communicate with a control module runtime environment 125 that may be executing within the controllers and field devices associated with the process to access or otherwise obtain data or other information from the control module runtime environment 125, for example, as defined by the associated control objects 118 of the display views 112. The user interface devices 122 may communicate with the control module runtime environment 125 using any desired or pre-configured communications network, such as the data highway 5 and / or wireless communications network 70 of FIG. 1A.
[0051] In some embodiments, user interface device 122 uses download script parser 128 to parse at least some of the downloaded display view configuration 112 during its execution (e.g., when performing object code conversion), although use of download script parser 128 by user interface device 122 is not necessary or required, for example, when the downloaded display view configuration 112 does not contain any script.
[0052] In some embodiments, the user interface device 122 uses the rule-based execution engine 130 to execute process flow algorithms or other rule-based procedures (e.g., provided by the process flow runtime environment 132) depicted by or coupled to the display view element objects 115 and / or display view objects 112, such as when one or more of the display view element objects 115 are smart process objects. Generally speaking, smart process objects are defined or configured to include data storage for storing data belonging to and received from other entities in the process plant 10, and inputs and outputs for communicating with other smart process objects and methods that may be executed on the stored and received data, for example, to detect plant or device conditions. In some configurations, smart process objects are communicatively connected together to create process flow modules that provide display views for plant entities, such as areas, devices, elements, modules, etc., and implement sets of rules for the plant entities, which are executed in runtime by the process flow runtime environment 132, for example, by using the execution engine 130. It should be noted that use of the execution engine 130 by the user interface 122 is not necessary or required, for example, when the downloaded display view configuration 112 does not include any smart process objects. It should be further noted that other methods of integrating display views and display view elements with runtime control objects within the operating environment 105 other than those discussed herein are additionally or alternatively contemplated and may be utilized by the graphical display composition and usage system 100. For simplicity of discussion, the instantiated display views that execute or are provided to the user interface devices 122 of the operating environment 105 are generally referred to herein as operator or operation applications 135.
[0053] FIG. 2B illustrates a detailed block diagram of one embodiment of a graphical configuration library 120 included within the graphical display configuration and use system 100 of FIG. 2A. As illustrated in FIG. 2B, the graphical configuration library 120 stores both display view definitions or configurations 112 and display view element definitions or configurations 115. Each definition or configuration 112, 115 may have associated therewith a published version and optionally one or more draft versions (interchangeably referred to herein as “in progress” or “work in progress” versions) stored in the library 120. As shown in FIG. 2B, view 1 has two corresponding draft configurations and one corresponding published configuration stored in the graphical configuration database 120. In addition, the graphical configuration database 120 is shown to store one draft configuration and two published configurations for view 2, one published configuration for view 3, and no draft configurations, and m draft configurations and one published configuration for view N. Generally speaking, only published configurations or definitions are enabled or permitted to be downloaded into the operating environment 105 from the graphical configuration library 120 or elsewhere in the configuration environment 102. A draft configuration or definition may be maintained, stored, and edited solely within the configuration environment 102 in some embodiments. If a draft configuration or definition is stored within the configuration environment 102, the draft is blocked from being downloaded into the operating environment 105. When a configuration engineer is satisfied with a draft display-related configuration or definition 112, 115, the engineer may explicitly publish (e.g., change its state to “Published”) the display-related configuration or definition 112, 115 so that it becomes available for download and execution within the runtime process plant 10. In some embodiments, a single user control may implement both publishing and subsequent downloading following publishing. In other embodiments, the publish user control or command and the download user control or command are different and separate user controls provided by the configuration application 110.
[0054] In this manner, multiple configuration engineers can create, modify, and test (in some circumstances simultaneously) graphical configurations and definitions without affecting runtime operation of the target configuration, as exemplified, for example, by the m draft configurations of view N and the published configuration of view N. Additionally, different versions of the same display view can be published and made available for runtime operation, for example, when the same display view is configured to have different combinations of operator customizations downloaded to different areas of the plant, as exemplified, for example, by the two publications of view 2. (Of course, graphical configuration system 100 allows a configuration engineer to rename the different publications of view 2 as separate views instead of different publications of the same view, if so desired.) In some embodiments, at least some of the published display views and published display view elements are available as is, i.e., at least some of the published display views and published display view elements are provided as defaults in library 120. Such default views and elements may be edited or modified by a configuration engineer using the graphical display configuration application 10, and the modified views or elements may be published as additional or alternative published versions of the default objects 112, 115.
[0055] A particular display view configuration may be defined, for example, by a configuration engineer or a user via the graphical display configuration application 110, to include (e.g., cite, specify, or reference) one or more display view element configurations, among other components. Similarly, in some instances, a particular display view element configuration may be defined to include (e.g., cite, specify, or reference) one or more other display view elements. Notably, various display-related configurations or definitions (whether display views and / or display view elements) may be updated without the need to create and / or download revised configurations and without the need to update the display view. Each may define a set of operator-selectable customizations that are made available to an operator to modify the appearance of the corresponding display view or display view element during run-time as desired by the operator, without the user interface device on which the view is running having to obtain additional configuration data indicating the modifications from another computing device (e.g., from a computing device or database included within configuration environment 102, or from a computing device or database included within operating environment 102 that stores the configuration data or a copy thereof locally). Additionally, in some embodiments, a particular display view configuration may also include one or more global variables or scripts in addition to other display view elements referenced therein.
[0056] For illustrative purposes, FIG. 2C illustrates a snapshot of one example of a display view 150 being configured by a user on a canvas provided by the graphical display configuration application 110. In this regard, during its configuration, the display view 150 is defined as including several display view elements 152a-168a. Specifically, the display view 150 includes a tabbed display element including four tabs 152a-1, 152a-2, 152a-3, and 152a-4, where tab 152a-1 includes a graphic of a tank 155a including an input flow connection 158a and an output flow connection 160a. In addition, the tank graphic 155a includes a fill animation in which the liquid level within the tank is represented. The presentation of the display view 150 may be influenced at least in part by one or more user controls included therein, such as a language user control 165a and a theme user control 168a, which may be manipulated by an operator for customization at his or her workstation or user interface 8. Additionally or alternatively, one or more similar user controls 165a, 168a may be provided on a workstation or user interface 8 via an operator application 135 running a display view 150 on the workstation 8 (not shown in FIG. 2C).
[0057] The configuration of one example of display view 150 is captured or defined within a corresponding display view object 172a, which in FIG. 2C is a draft, work in progress, or in-progress configuration object 172a (or is otherwise unpublished). Similarly, the configuration of each of display views 152a-168a is captured or defined within one or more respective display view element objects 152b-170b (each of which may or may not be published, either individually or as a whole comprising display view 150, at the time illustrated by FIG. 2C). For example, tabs 152a-1, 152a-2, 152a-3, and 152a-4 are defined by graphical tab display elements, which are themselves defined by instances of tab object 152b, with each tab object instance specifically configured (not shown), for example, to display different text on its respective tab 152a-1, 152a-2, 152a-3, and 152a-4, and to include other display characteristics and properties therein. In some embodiments, each tab 152a-1, 152a-2, 152a-3, and 152a-4 may each be configured to change its appearance (e.g., indicators, background color, text color, animation, etc.) in response to live data, and thereby may be linked to one or more control elements within the operational environment 105 of the process plant 10. The tank graphic 155a is defined by an instance of a tank object 155b, which is specifically configured to be associated with a particular control tag LT 123. In addition, the fill animation 162a is defined by an instance of a fill animation object 162b that specifies that the fill animation is a bottom to top fill. Furthermore, the colors of the fill animation 162a may be selected from blue, red, white, and blue. The fill colors are defined by instances of the fill color object 170b such that the operator can select between the colors green and red. For example, the fill colors may be individually selectable or may be selectable by the operator by selecting a particular theme that defines the fill colors.
[0058] 2C, a configuration of a graphical object instance may be defined using other graphical objects and / or object instances. For example, an instance of a tab object 152b defining a tab 152a-1 is defined to include therein an instance of a tank graphic object 155b defining a tank graphic 155a (including, among other things, an explanation therein of the control tag LT123). Similarly, the instance of the tank graphic object 155b defining the tank graphic 155a is itself defined to include an instance of a fill animation object 162b for a fill animation 162a, which in this example is specifically configured to be a bottom-to-top fill animation. Additionally, the instance of the fill animation object 162b that defines the fill animation 162a is itself defined to include an instance of a fill color object 170b, which defines a selection of operator-selectable fill colors (e.g., blue, red, white, and green) and additionally defines the mutually exclusive selection and application thereof.
[0059] Generally speaking, a first graphical element object may be defined or configured to refer to (e.g., specify, reference, etc.) a second graphical element object, and the configuration of the second graphical element object defines the appearance and / or behavior of the first graphical element object. In some embodiments, the configuration or definition of the first graphical element object may additionally include one or more object property values and / or scripts, if desired. The first graphical element object and the second graphical element object are independent and separate objects; that is, the first graphical element object and the second graphical element object are not included within the same object class, are not derived from each other, are not related by a parent / child object relationship, etc. In fact, the second graphical element object may be referenced by another graphical element object and appropriately configured to thereby define the appearance and / or behavior of the other graphical element object.
[0060] In some scenarios, the second graphical element object may itself reference a third graphical element object, the configuration of which defines the appearance and / or behavior of the second graphical element object. If desired, the configuration of the second graphical element object may additionally include one or more object property values and / or scripts.
[0061] Returning to FIG. 2C , at least, an instance of a display view object 172a defining a view 150 may be configured to display one or more user controls 165a, 168a therein. (As noted above, in some embodiments, one or more of the user controls 165a, 168a may be provided by an operator application 135 executing the configured display view object 172a in a user interface 8 within the operating environment 105, which is not shown in FIG. 2C .) At least, each of the user controls 165a, 168a, whether provided by the display view object 172a and / or by the operator application 135, may be configured to display one or more user controls 165a, 168a therein by its respective object 165b, 168b. 2C, language user control 165a is defined by an instance of a multi-language object 165b, which in this example is configured to allow text to be presented in any one of English, Arabic, or French. Thus, during runtime, an operator may manipulate language user control 165a to selectively change the language appearing in display view 150 to / from English, Arabic, or French. Similarly, theme user control 168a is defined by an instance of a theme object 168b, which in this example is defined to allow an operator to selectively change the theme of display view 150 from among theme 1, theme 2, and theme 3 during runtime. Thus, during runtime, an operator may manipulate theme user control 168a on operator application 135 to change the theme appearing in display view 150 from among theme 1, theme 2, and theme 3. Each of the languages and themes may be defined anywhere in the graphical configuration database 120, for example, in the manner described anywhere in this disclosure.
[0062] Further, the display view 150 may be capable of being included within various other display view elements 115. For example, a particular layout 1 (e.g., which may be configured as a particular instance of a layout object) may be defined to present the display view 150 in a first area, e.g., by linking a configuration 172a of the display view 150 to a graphical object that defines a first area of the layout 1. Another particular layout 2 (e.g., which may be configured as another particular instance of a layout object) may be defined to present the display view 150 in a second area, e.g., by linking a display view configuration 170 to a graphical object that defines a second area of the layout 2. In additional or alternative implementations, an instance of the display view object 172a may reference one or several layouts (e.g., which may be configured as a particular instance of a layout object) that include the display view 150. Each of the layouts that include the display view 150 may be specifically configured to be presented or not presented to an operator when presenting the display view 150 during execution within the runtime environment. In other words, during execution within the runtime environment, operator application 135 may present display view 150 according to one of the layouts based on the configuration of display view objects 172a. Additional discussion of layouts that may be provided by graphical display configuration system 100 is provided elsewhere in this disclosure. Similarly, display view 150 may be linked or otherwise associated with various display hierarchies, additional discussion of display hierarchies provided by graphical display configuration system 100 is also provided elsewhere in this disclosure.
[0063] Returning to FIG. 2C, when the configuration engineer is satisfied with the display view object 172a that defines the content, appearance, and behavior of the display view 150 in the runtime environment 105, the configuration engineer may publish the display view object, as represented in FIG. 2C by reference numeral 172b.
[0064] In embodiments in which display view element objects may be published individually, upon publishing of display view object 172b, any display view element objects 152b-170b that are not already in a published state may be automatically published, and / or the user may be instructed to manually publish display view element objects that are still in a draft or in progress state. Any display elements that are attached to or linked to it must also be in the published state.
[0065] In another embodiment where the display view element objects are not individually publishable, upon publishing of the display view object 172b, the published configuration 172b of the display view 150 is stored in the graphical configuration database 120, thereby making the published configuration 172b available for downloading into the operating environment 105 of the process plant 10, such as shown in Figure 2C. In some embodiments, upon publishing of the display view object 172, the published configuration 172b is automatically downloaded into the operating environment.
[0066] The published configuration of display view objects 172b may be downloaded to one or more user interface devices included within the operating environment for execution, as represented in FIG. 2C by user interface devices UI-1, UI-2, UI-3. Each of user interface devices UI-1, UI-2, UI-3 may take the form of, for example, user interface device 8 or user interface device 122, and the particular set of user interface devices to which published display view configuration 172b is to be downloaded (and executed) may be specified by a user, for example, via graphical display configuration application 110 or another user interface of configuration environment 120. In this manner, each downloaded instance of published display view configuration 172b may execute independently within runtime environment 105 on its respective host user interface device UI-1, UI-2, UI-3.
[0067] Importantly, the published display view configuration 172b allows an operator or user to customize the appearance and behavior of each running display view 150 as desired within the runtime environment 105 and independent of other users' runtime customizations when running on its host device UI-1, UI-2, UI-3. As shown in FIG. 2C, in UI-1, the user of UI-1 has changed the color of the fill animation 162a of the tank graphic 155 on the display view 150 to be blue, selected the text displayed on the display view 150 to be presented in French, and selected the display view 150 to be presented using Theme 3. In UI-2, the user has changed the color of the fill animation 162a to be white, selected the text to be presented in Arabic, and selected Theme 1. In UI-3, the user has changed the color of the fill animation 162a to be red, selected the text to be displayed in English, and selected Theme 2. User selections and customizations implemented in user interface devices UI-1, UI-2, and UI-3 are enabled solely using the respective published display view configurations 172b running on host devices UI-1, UI-2, and UI-3, respectively. That is, none of UI-1, UI-2, or UI-3 need to obtain additional configuration data from a configuration environment or any other computing device in order to implement the operator's desired changes. Furthermore, an updated configuration of display view 150 is not required to be downloaded and executed in order to implement the operator's desired changes. Rather, each operator implements the desired changes in accordance with the runtime execution of display view 150 on his or her respective user interface device UI-1, UI-2, UI-3 without the need to, for example, stop and restart display view 150.For example, if a user of UI-1 subsequently desires to change the theme displayed from Theme 3 to Theme 2, the user can do so by simply making a selection via the active Theme user control 168a on UI-1 (as described above). In response to the execution of the configuration data 120 (which may be provided by operator application 135 or display view 150, as described above), display view 150 will implement the changes without, for example, having to communicate with any other computing devices included within configuration environment 102 and / or any other computing devices that may have access to configuration data 120 or a copy thereof.
[0068] Of course, the example scenario depicted in Figure 2C is intended to be illustrative and not limiting, and is merely one of many possible usage scenarios for the display configuration and use system 100. Indeed, as illustrated within this disclosure, the graphical display configuration and use system 100 provides a configuration environment 102 that is flexible, intuitive, and easy to maintain, while simultaneously providing an operational experience that supports independent online operator customization of the display views and / or display elements contained therein. Various features and aspects of the graphical display configuration and use system 100 (either alone or in combination) that provide these and other benefits are described in more detail below.
[0069] Display Navigation Hierarchy
[0070] 3A, examples of the types of display view elements provided by the graphical display configuration and use system and method described herein are hierarchical display view elements and layout display view elements. As mentioned above, to generate graphics in a process control system, the graphical display configuration application 110 in the configuration environment 102 includes graphical user controls for defining hierarchies and layouts, thereby allowing a configuration engineer to graphically define the hierarchies and layouts. Each display view may be made up of display view elements that define the display view. For example, a "main tank" display view may include several display view elements, each representing a different tank. A display view element in one display view may also be the subject of another display view at a higher level of detail, which has its own display view elements. In this manner, a plant operator may navigate from a display view that depicts an overview of the process plant at the lowest level of detail to a display view that depicts a single alarm or device in the process plant at one of the highest levels of detail.
[0071] In some embodiments, the display view depicts a section of a process plant, and the display view elements include graphical representations of process plant entities, such as tanks, mixers, valves, pumps, and / or any other suitable equipment in the process plant. The display view may also include graphical representations of process plant connection entities, such as pipes, electrical wiring, conveyor belts, etc., that connect one piece of equipment to another.
[0072] In some embodiments, the configuration engineer may define the alarms, trends, and / or process parameter values within a display view at a particular level of detail. In some other embodiments, the configuration engineer may define the number of alarms, trends, and / or process parameter values within a display view at a particular level of detail. The graphical display configuration application 110 or the operator or operations application 135 running on the operator user interface device 122 may then automatically determine which alarms, trends, and / or process parameter values to include on the display view based on the priority level of each alarm, trend, and / or process parameter value. For example, the configuration engineer may indicate that five process parameter values are to be presented at a particular location within the display view. Each of the process parameter values corresponding to a view may be ranked according to a priority level, and the top five ranked process parameter values may be presented in the display view. The priority level may be determined by a configuration engineer, an operator, or may be determined automatically based on a set of rules, such as whether a particular process parameter value will trigger an alarm.
[0073] To create a hierarchy of display views for navigating from a display view depicting an overview of a process plant to a display view depicting a section of the process plant at a higher level of detail, the graphical display configuration application 110 includes graphical user controls for defining relationships or links between the display views. The graphical display configuration application 110 may present a user interface or a portion thereof for creating the hierarchy. The hierarchy UI includes a representation of each of the display views defined within the configuration environment. A configuration engineer may then drag and drop display views into the hierarchy section (or use any other suitable graphical user controls) to define relationships or links between the display views. For example, by dragging and dropping a representation of the “Tank 1” display view (e.g., name “Tank 1”, icon, etc.) onto a representation of the “Main Tank” display view, the graphical display configuration application 110 may determine that Tank 1 is a subview with a higher level of detail than the “Main Tank” display view. In another example, by dragging and dropping the representation of the “Tank Supply” display view above or below the representation of the “Main Tank” display view in a hierarchy section, the graphical display configuration application 110 may determine that the “Tank Supply” and “Main Tank” display views are at the same level of detail in the hierarchy.
[0074] Display view hierarchies may also be created for trend display views that represent historized process parameter values. For example, a process parameter such as flow rate through a valve may depend on one or several input or output process parameters, such as the inlet pressure of the valve and the outlet pressure of the valve. A level 1 trend display view may depict the flow rate through a valve over time, while a level 2 trend display sub-view of the level 1 trend display view may depict the inlet and outlet pressures at the valve over time. A configuration engineer may create trend display view hierarchies in the configuration environment 102, and an operator may navigate (e.g., via navigation buttons) between the resulting trend display views and sub-views in the operating environment 105 with increasing or decreasing levels of detail.
[0075] In some embodiments, a display view hierarchy may resemble a tree structure where the display view at the lowest level of detail (e.g., level 1) is the root node of the tree structure. The display views at the second lowest level of detail (e.g., level 2) may be child nodes to the root node, each having its own child node at the third lowest level of detail (e.g., level 3), which may be a grandchild node to the root node. A configuration engineer may create several display view hierarchies, each corresponding to a different area within the process plant or a different process plant. In this manner, each operator may view a display view hierarchy that represents his or her area of responsibility.
[0076] In addition to defining a display view hierarchy, the graphical display configuration application 110 includes graphical user controls for defining a layout. As used herein, a "layout" refers to a set of controls for presenting several display views on a display screen or multiple display screens for an operator workstation. The layout may indicate the manner in which to divide the display screen area of the operator workstation. For example, the operator workstation may include multiple monitors or display screens, and the layout may cause the operator workstation to present a different display view on each of the display screens, so that the operator can view several display views at once. In another example, the operator workstation may include a single monitor or display screen, and the layout may cause the operator workstation to divide the display screen into several regions (e.g., frames, subareas, or portions) and present a different display view on each region of the display screen. The graphical display configuration application 110 may include graphical user controls for selecting the number of display screens and the display areas within each display screen for the layout. For example, a configuration engineer may create a first layout having two display screens, each display screen divided into two display areas. The configuration engineer may then define display view types, such as viewing area, alarm area, historized parameters, nameplate, hierarchical level (e.g., level 1, level 2, level 3), etc., for each of the divided display areas.
[0077] Additionally, a layout may include relationships or links between display regions within the layout. For example, a first display region within the layout may present a display view of a type of hierarchy level 1, and a second display region within the layout may present a display view of a type of hierarchy level 2. The second display region may be configured to present a display view of hierarchy level 2 when an operator navigates away from hierarchy level 1 within the first display region. The display view of the second display region depends on the operator's actions relative to the first display region, and the first display region continues to present a display view of the type of hierarchy level 1. In another example, a display region within the layout depicting an alarm list or a historized parameter display view may depend on a display region within the layout depicting a control module, such that the alarm list or historized parameter display view includes the alarms or parameters that are displayed within the control module.
[0078] 3A illustrates an example of a side-by-side view 300 of a graphical display composition application UI 302 (which may be, for example, an instance of the graphical display composition application 110) and an operator application UI 304 (which may be, for example, an instance of the operator application 135) that renders display view elements during runtime as defined by the graphical display composition application UI 302. More specifically, the graphical display composition application UI 302 includes a hierarchy pane 310 that shows a hierarchy of a set of display views. For example, the "Tank Ovw" display view may be at level 1 of the display view hierarchy, and the "Tank Supply" and "Main Tank" display views may be at level 2. The "Supply Ht X" and "Supply Mixr" display views may be subviews of the "Tank Supply" display view, and the "Tank 1", "Tank 2", and "Surge" display views may be subviews of the "Main Tank" display view at level 3. Additionally, the "T2SOP" display view may be a subview of the "Tank 2" display view at level 4. As described above, a configuration engineer may define a display view hierarchy by dragging and dropping display view representations into hierarchy pane 310 presented by graphical display configuration application 110, or using any other suitable graphical user control. New display view representations may also be defined within the display view hierarchy before the corresponding display view is created. A configuration engineer may define where the new display view is located in the display view hierarchy and then create the new display view.
[0079] In addition to depicting the hierarchy section 310, the graphical display configuration application UI 302 depicts a layout 312 that divides the display into four display screens and four display regions 314a-d (also referred to interchangeably herein as "display subareas" or "display portions"), each display region 314a-d having a corresponding display view type. For example, the upper left corner display region 314a is defined to present a hierarchical level 1 display view. The lower left and upper right corner display regions 314b-c are defined to present hierarchical level 2 and level 3 display views, and the upper right corner display view 314d is defined to present an alarm list display view. The layout 312 also defines relationships or links between the display regions. For example, the lower left corner display region 314b automatically presents an operator hierarchical level 2 display view in the upper left corner display region 314a in response to an operator navigating from the hierarchical level 1 display view to the hierarchical level 2 display view. In another example, the top right corner display area 314d may automatically display an alarm list of alarms that are included in one or more of the display views in the other display areas 314a-c.
[0080] The operator application UI 304 includes a layout 312 defined by the graphical display configuration application 110 that divides the operator workstation display into four display screens and four display regions 318a-d. The upper left corner display region 318a presents a display view of hierarchical level 1. The lower left and upper right corner display regions 318b-c present display views of hierarchical levels 2 and 3, and the upper right corner display view 318d presents an alarm list display view. The operator application UI 304 may present the display views according to the hierarchy, layout, and / or other display view elements defined by the graphical display configuration application 110.
[0081] The graphical display configuration application UI 302 also includes an administration section 316 (which may be related to administration of the operations applications / environments 304, for example) for assigning hierarchies, layouts, and / or themes to a particular operator workstation or set of operator workstations. In this manner, an operator workstation for an operator overseeing one segment of the process plant may present the hierarchies associated with that segment and may restrict access to hierarchies for other segments of the process plant. In some embodiments, a configuration engineer may assign all hierarchies and layouts to each operator workstation via the administration section 316, and the operators may select the layouts and hierarchies to present on their respective operator workstations.
[0082] 3B illustrates a home tab 350 of the graphical display composition application 110 for generating display views to be executed on an operator workstation. The home tab 350 includes a new display button 352 for creating a display view, a new layout button 354 for creating a layout, and a new display hierarchy button for creating a hierarchy of display views. The home tab 350 also includes a composition canvas 366 for composing display view elements within a display view. The display view elements may be viewed in a composition mode upon selection of a compose button (not shown) and / or in a preview mode upon selection of a preview button 364. In an alternative embodiment, a draft or working composition of the display view elements may be displayed on a canvas provided by the composition application 110. In one embodiment, a preview mode may be presented (e.g., by default or continuously) or only a preview button 364 may be presented (e.g., as illustrated by FIG. 3B ), the activation of which causes a preview of the display view to be displayed in another area or window of the user interface provided by configuration application 110. The preview mode or separate display of the preview presents a preview of the display view as it will appear during runtime so that the configuration engineer can see how the display view and display view elements will appear to an operator. For example, the display view elements may be presented in the theme, colors, etc. selected in the configuration mode. The configuration engineer toggles graphical user controls, such as a navigation bar, tab bar, etc., on the display view in the preview mode to see how the display view changes in response to user interactions.
[0083] To create a display view, the home tab 350 includes graphical user controls for selecting display view elements, such as basic display element buttons 360 including shapes such as rectangles, squares, circles, etc., arrows, connectors, text boxes, charts, or any other suitable basic display elements. A display view element selection pane or palette 370 may also be included for selecting display view elements, such as a nameplate element, a tab element, a bar graph element, a data element, a data link element, a write element, a button slider, an alarm element, an alarm details element, a function block element, a navigation bar element, a GEM element (such as those described in commonly-filed U.S. patent application Ser. No. 15 / 692,450, entitled "Derived and Linked Definitions with Override," filed Aug. 31, 2017, the entire disclosure of which is incorporated herein by reference), or any other suitable display view element. The configuration engineer may select a display view element by dragging and dropping the display view element into the configuration canvas 366 or by using any other suitable graphical user controls. For example, in FIG. 3B, a configuration engineer may select the New Display button 352 to create a display view for Display 1 (reference numeral 368 ) and drag and drop a rectangle 374 from the Basic Display Elements button 360 into the configuration canvas 366 .
[0084] When rectangle 374 is selected, properties of rectangle 374 are presented in edit pane 380. Edit pane 380 may show several properties of the rectangle, such as the name of the rectangle (Rectangle 1), fill color (white), fill percentage (100%), line color (black), line thickness (1 pt), line style (solid), etc. Each of the properties may be adjusted in edit pane 380 via a graphical user control, such as a drop-down menu or a free-form text field. For example, the line thickness property may include a drop-down menu for selecting one of several line thickness values, such as 0.5 pt, 1 pt, 1.5 pt, etc. The fill color property may include a color palette for selecting one of several colors or a free-form text field for entering an RGB color value. In some embodiments, properties may also be adjusted via a graphical user control of rectangle 374, such as a pop-up menu in response to a right-click or double-click on rectangle 374. The properties included in edit pane 380 are just a few examples of the properties of rectangle 374. Additional or alternative adjustable properties may also be presented.
[0085] Additionally, relationships or links between display view elements may be established, for example, by connecting the display view elements via lines or other connectors. Relationships or links may also be established by referencing other display view elements within the properties of the display view elements. For example, a first display view element may reference another display view element in the properties of the display view element. A first display view element may represent a tank in a process plant. A second display view element may represent a process parameter value of the tank, such as a fill percentage. In some scenarios, a configuration engineer may reference a first display view element in the properties of a second display view element such that the first and second display view elements are associated and included together in one or several display views. In some embodiments, each of the linked display view elements associated with a process plant entity or process control element may reference a control module, node, device (e.g., field device), and / or control tag that references a signal received and / or transmitted by a device, control module, or node corresponding to the process plant entity.
[0086] In any event, the home tab 350 also includes a publish button 358 that publishes the graphics (display view, layout, or display view hierarchy) to the graphical configuration database 120. The published graphics can then be provided to a set of operator workstations and presented to a corresponding operator during run-time.
[0087] Graphical display configuration design verification
[0088] 4A and 4B, the graphical display configuration application 110 may provide a graphical display validation tool that may be utilized by a configuration engineer to assess the completeness of one or more draft graphical display views and find any faults, warnings, and / or errors therein (particularly with respect to control configurations) while the configuration engineer is configuring the graphical display views. In this manner, the graphical display configuration application 110 improves the efficiency of using the user interface device 8 by flagging and presenting to the configuration engineer faults, warnings, or errors associated with several draft graphical display views, which may include a draft of the entire graphical configuration of the process plant or a portion thereof. Instead of the configuration engineer having to review each draft graphical display view individually looking for errors and determine how an error in one draft graphical display view affects another draft graphical display view in the set, the graphical display configuration application 110 analyzes each of the draft graphical display views and presents faults, warnings, or errors for each of them in a single, comprehensive completeness assessment report. In some embodiments, the graphical display validation tool identifies warnings rather than errors based on the severity of the condition. An error in a graphical display view may refer to a serious condition that prevents the graphical display view from being issued. On the other hand, a warning may refer to a moderate or minor condition such that a graphical display view is not issued. For example, missing or mismatched control references in a graphical display view may be an example of a condition that may trigger a warning.
[0089] In one embodiment, the graphical display validation tool may be implemented as a set of computer-executable instructions that may be stored in one or more tangible, non-transitory memories of the graphical display configuration system 100 and executed by one or more processors of the graphical display validation tool. For example, the graphical display validation tool may be invoked or called by the graphical display configuration application 110, either automatically or in response to a user request.
[0090] In an example scenario, a graphical display verification tool is The tool may be invoked via user controls provided by the play configuration application 110, where the configuration engineer can indicate which set of draft display views (which may include drafts of the entire graphical configuration of the process plant or portions thereof) will be operated on by the tool and / or whether an integrity assessment will be performed on a set of targets of the draft display views. Additionally or alternatively, the tool may be automatically invoked by the graphical display configuration application 110 when the configuration engineer saves a draft display view and evaluates the integrity of the entire graphical configuration of the process plant in the saved draft view. In some embodiments, the graphical display configuration application 110 can automatically invoke the tool periodically to operate on the draft display views showing the entire graphical configuration of the process plant and evaluate the integrity of each of them.
[0091] 4A illustrates a flow diagram of an example of a method 400 for evaluating the completeness of a collection of draft display views (which may include a draft of an entire graphical configuration of a process plant or a portion thereof). The method 400 may be implemented by a graphical display validation tool, for example, when invoked by a configuration engineer and / or when invoked by the graphical display configuration application 110. At block 401, the method 400 may include obtaining a representation of a set of draft display views corresponding to a draft of an entire graphical configuration of the process plant or a portion thereof. Obtaining the set of draft display views may include receiving or obtaining a list of display views expected to be included in the draft graphical configuration of the process plant. The representation of the set of expected display views may be obtained, for example, manually via a user interface and / or automatically from the control configuration database 118 of the process plant 10.
[0092] The method 400 may include, for each draft display view included in the set of draft display views, e.g., for each “target” draft display view (block 402), obtaining a representation of a set of control references corresponding to the target draft display view (block 404). The control references may include, for example, control tags that refer to control modules, nodes, devices (e.g., field devices), and / or signals received and / or transmitted by the devices, control modules, or nodes. The control references may also include control parameters that are parameters of various control modules, nodes, devices, signals, etc. Generally speaking, as used herein, a “node” of the process control system 10 refers to a physical component (e.g., a component including hardware) that communicates with one or more other nodes. For example, the process control system 10 may include nodes such as process controllers, I / O cards, workstations, access points, user interface devices, etc., such as the nodes illustrated in FIG. 1. Obtaining a set of control references corresponding to the target draft display view (block 404) may include receiving or obtaining a list of expected control modules associated with the target display view, e.g., including one or more control tags and / or control parameters that will be referenced by the target graphical display view. The indication of the expected set of control references may be obtained, e.g., manually via a user interface and / or automatically from the control configuration database 118 of the process plant 10. Alternatively, obtaining the set of control references (block 404) may include retrieving the control references included in the draft configuration of the target graphical display view.
[0093] For each control reference in the set of control references, e.g., for each "target" control reference After (block 405), the method 400 may include determining whether a target control reference is included or otherwise associated with the target graphical display view (block 408). That is, in block 408, the method 400 configures the target graphical display view (or a graphical display view element included therein) to include or otherwise be associated with the target control reference. A warning or error corresponding to a target control reference that is missing from or not associated with the target graphical display view configuration may be flagged when the target control reference is not included in the configuration of the target graphical display view, e.g., when a graphical display element (which may represent, e.g., a module, device, node, name, property, etc.) of the target display view is not configured with the target control reference and a graphical representation, script, or other function included in the target display view does not indicate the target control reference (block 410). For example, if a target display view is intended to be a primary control display, a nameplate display, or a detailed display of a target control reference, the target control reference need not actually be configured on a graphical element of the display view, but the display view may nevertheless store or be configured with an indication of an association with the control reference (e.g., which may appear at run-time on the display view as a label, name, etc.).
[0094] It should be noted that in some embodiments, block 408 may be omitted from method 400 if the set or list of control references corresponding to the target display view is obtained directly from the configuration of the target graphical display view (block 404).
[0095] At a minimum, if the target graphical display view includes a subject control reference, the method 400 may determine whether the control reference itself has been configured (block 412), e.g., whether the control reference has been found or stored in the control configuration database 118 of the process control system 10. If the control reference has been configured and found in the control configuration database 118, then in block 412 the method 400 may additionally determine whether the configuration of the control reference stored in the control configuration database 118 matches that reference and / or its use on the target graphical display view. If the control reference has not been configured, or if the control reference included in the target graphical display view does not match its configuration stored in the control configuration database 118, then a warning or error corresponding to the subject control reference is flagged (block 410). For example, a corresponding warning or error flag may indicate that the control reference is unresolved.
[0096] If a control reference is configured and its configuration stored in the control configuration database 118 matches its reference / use on the target graphical display view (e.g., as determined in block 412), the method 400 determines whether an associated graphical display view and / or display view element corresponding to the control reference is defined or configured (block 415). For example, in the case of a control tag referenced on a nameplate display view, in block 415 the method 400 may determine whether a corresponding detail display view and a corresponding primary control display view utilizing the control tag are defined within the graphical display configuration system 100. If one or more associated graphical display views and / or elements are not defined for the target control reference, a warning or error corresponding to the target control reference and / or the missing graphical display view and / or element may be flagged (block 410). For example, a corresponding warning or error flag may indicate that the associated graphical display view and / or element is missing or unresolved.
[0097] It should be noted that blocks 408, 412, 415 may be performed sequentially for the target control references in any desired order and / or may be performed at least partially in parallel in some embodiments. After at least the target control references have been processed (e.g., blocks 408-415), the method 400 may determine whether there are any additional control references corresponding to the target draft display view to process (block 418). If so, the method 400 may return to block 405 to process another control reference. If not, the method 400 may determine whether there are any additional target draft display views in the family of draft display views corresponding to a draft of the entire graphical configuration of the process plant or a portion thereof (block 419). If so, the method 400 may return to block 402 to process another target draft display view. If not, the method 400 may proceed to indicate any flagged warnings or errors (block 420). It should be noted that blocks 404, 405, 408, 412, 415 may be performed sequentially on the target draft display views in any desired order, and / or in some embodiments may be performed at least partially in parallel.
[0098] The flagged warning or error may be indicated by using one or more suitable indications (block 420). A particularly useful indication to a configuration engineer is an in-line highlighted or otherwise prominent control reference included in the target graphical display view to which the warning or error pertains. For example, a flagged control reference may be indicated by a visual signal displayed on the graphical configuration display canvas, e.g., near the control reference or near the graphical element utilizing the control reference, and / or by applying a visualization (e.g., graying out, highlighting, blinking, etc.) to the control reference and / or to its host graphical element. Different visual symbols and / or visualizations may represent different types of warnings or errors and may be so defined as needed. Similarly, a flagged control reference may be indicated, e.g., via a visual symbol, visualization, etc., in an accompanying text-based area (such as an edit pane, banner, and other area of a user interface provided by the graphical display configuration application 110 that provides textual information describing the target graphical display view and / or the elements contained therein). Thus, during the design or development of the target display view, a configuration engineer can easily determine which portions of the target draft display view are not yet complete, particularly with respect to binding, referencing, or otherwise linking graphical elements and control references to control configuration objects or definitions. Additionally or alternatively, flagged warnings or errors can be displayed on a user interface, for example, as part of the completeness assessment, and / or via a file, report, or other suitable format that may be output for storage on another computing device, analysis, and / or printing (block 420). In some circumstances, the completeness assessment, or at least a portion of its contents, can be provided for documentation purposes.
[0099] In some embodiments, method 400 may be applied to a graphical reference instead of a control reference. That is, method 400 may be applied to a reference to a graphical display element object, parameter, or variable included in a target graphical display view and / or a graphical display element object, parameter, or variable configured and stored in graphical configuration library or database 120. For example, when method 400 is applied to a graphical reference, block 404 may include obtaining a graphical reference corresponding to the graphical display view, block 412 may include determining whether a target graphical reference is defined in graphical configuration database 120, and block 418 may include determining whether there are any further graphical references to process. Thus, in these embodiments, method 400 may evaluate the graphical display view configuration and the graphical references contained therein against the configured graphical displays, graphical display elements, graphical parameters, and / or graphical variables stored in graphical configuration library 120. Inconsistencies and / or omissions between the graphical display view configuration and the information stored in graphical configuration database 120 may be flagged as warnings or errors by method 400.
[0100] The method 400 can be readily applied to any set of control references, for example, all configured control references stored in the control configuration database 118 of the process plant 10, in a particular area or region of the process plant 10, or in some embodiments, for all control references. Thus, any one or more portions of the graphical configuration database 120 may be cross-checked against any one or more of the control configuration database 118, or vice versa, to assess the completeness of a draft graphical display view configuration.
[0101] 4B illustrates an example of a completeness assessment 425 that may be generated by a graphical display validation tool provided by the graphical display configuration application 110, for example, in block 420 of method 400. The example completeness assessment 425 is shown implemented as a spreadsheet or table, although other suitable implementations and / or representations may be possible (e.g., graph, chart, text, report, file, etc.). Assessment 425 includes columns 428a listing various display views evaluated by the tool, columns 428b listing various control references (e.g., control tags and / or control parameters) included in the displayed display views, columns 428c indicating whether the displayed control references were flagged with a warning or error, and columns 428d including a description of each of the flagged warnings or errors (or an indication of no errors if so found by the tool). Possible types of flagged warnings or errors and their corresponding descriptions may include, for example, the following: ● Control reference 428b is not used by any display views stored in graphical configuration library 120 (eg, as shown in row 2 of table 425). • A detailed display view corresponding to control reference 428b does not exist in the graphical configuration library 120. • A nameplate display view corresponding to control reference 428b does not exist in the graphical configuration library 120. The first control display view associated with the control reference 428 does not exist in the graphical configuration library 120. - The primary control display view 428a does not utilize a control reference 428b, for example when the control reference 428b indicates a control module. A particular display view 428a utilizes or is associated with a control reference 428b, but the control reference 428b does not exist in the control configuration database 118; and / or • Another type of error, warning, or inconsistency between the graphical configuration library 120 and the control configuration database 118.
[0102] Possible types of no errors and corresponding descriptions that may be displayed in column 428d may include, for example: - The primary control display utilizes or is associated with control reference 428b. ● A particular display view 428a utilizes a control reference 428b. A particular display view 428a is a nameplate display view of a control reference 428b. It is. The particular display view 428a is a detailed display view of the control reference 428b; and / or ● A particular display view 428a is the primary control display for a control reference 428b, for example when the control reference 428 represents a device or node and the control reference is not included in the display view 428.
[0103] 4C illustrates another example of an integrity assessment 430 that may be generated by a graphical display validation tool provided by the graphical display configuration application 110, for example, in block 420 of method 400. The example integrity assessment 430 is implemented as a spreadsheet or table, although other implementations and / or representations can be utilized as desired. This example integrity assessment 430 generally presents only the warnings or errors (and not no errors) flagged by the tool. For example, assessment 430 includes column 432a listing the various display views evaluated by the tool, column 432b indicating the severity of the particular warning or error found for each display view, column 432c describing the category or type of the particular warning or error, column 432d including a description of the particular warning or error, and column 432e indicating the particular location or graphical element of the display view where the particular warning or error was discovered. Notably, any of the information included in assessment 430 may include active links that allow a configuration engineer to navigate to a location where they can take steps to correct the warning or error. For example, referring to the first row of evaluation 430, when a configuration engineer selects "LibraryStandardsColor1 does not exist" in column 432d, a window to the standards library automatically opens, through which the configuration engineer can configure or define Color1. Alternatively, the configuration engineer may select "Group1Rectangle1Fill Color" in column 432e, which can result in a window to the configuration pane of Group1Rectangle1 where the configuration engineer can change the fill color from "Color1" to some predefined color.Similarly, in the second line of evaluation 430, a configuration engineer can select "FIC-1 / PROCESSVALUE" which can be automatically placed into the configuration partition for FIC-1 where the engineer can change the data reference or path to the PV of FIC-1, or the configuration engineer can select "GEM1\Rectangle1\Fill Percent\Fill Value" which can change the control reference contained in Rectangle1 of GEM1 from FIC-1 / PROCESSVALUE to some other defined or configured control tag.
[0104] In one embodiment, a graphical display validation tool provided by the graphical display configuration application 110 can prevent issuance of a target graphical display view if one or more integrity errors are associated with it. In some embodiments, an error can prevent issuance of a target graphical display view, while a warning can not prevent issuance of a target graphical display view. For example, the tool can identify or discover faults, warnings, or errors in the draft graphical configuration of the process plant 10 and / or the control configuration of the process plant as control configuration actions relate to the graphical configuration. The detected faults or errors can be corrected by a configuration engineer and / or automatically before the configuration(s) are downloaded and executed at run-time of the process 10. On the other hand, the target graphical display view can still be issued when a warning is detected, for example, due to a mismatch and / or omission between the target graphical display view and the control references stored in the graphical configuration database 120. Also, in some embodiments, the graphical display configuration application 110 can call the graphical display validation tool to speed up the configuration process. The method may include user controls to turn off some or all of the fault or error checking when calling the method.
[0105] Embodiments of the techniques described in this disclosure may include any number of the following aspects, either alone or in combination.
[0106] 1. A method for assessing completeness of a graphical display configuration of a process plant, comprising: obtaining, by a computing device executing a graphical display configuration application in a configuration environment of the process plant, a representation of a plurality of display views to be combined to represent the process plant, each display view including a representation of a process control element; obtaining, by the graphical display configuration application, a representation of a set of control or graphical references corresponding to the plurality of display views, each set of control or graphical references corresponding to one of the plurality of display views, each control or graphical reference in the set of control or graphical references referencing a process control element or display view element displayed in the corresponding display view; and, for each control or graphical reference in each of the sets, determining: (i) whether a representation of the control or graphical reference is included in the corresponding display view; (ii) whether a representation of the control or graphical reference is included in the corresponding display view; and presenting, by the graphical display configuration application, an integrity assessment report indicating one or more warnings or errors in the multiple display views, wherein the one or more warnings or errors are identified based on at least one of: (i) a display of a control or graphical reference in the set of controls or graphical references is not included in the corresponding display view, (ii) a control or graphical reference in the set of controls or graphical references is not stored in the control configuration database, or (iii) an associated display view or display view element corresponding to a control or graphical reference in the set of controls or graphical references is not included in the multiple display views.
[0107] 2. The method according to aspect 1, further comprising: for each control or graphical reference in each of the sets of controls or graphical references, generating a warning or error corresponding to the control or graphical reference in response to determining that a corresponding display view does not include a display of the control or graphical reference, that the control or graphical reference is not stored in the control configuration database, or that an associated display view or display view element corresponding to the control or graphical reference is not included in the multiple display views.
[0108] 3. Determining at least one of (I) whether a representation of the control or graphical reference is included in a corresponding display view, (ii) whether the control or graphical reference is stored in a control configuration database, or (iii) whether an associated display view or display view element corresponding to the control or graphical reference is included in a plurality of display views, determining whether a representation of the control or graphical reference is included in a corresponding display view, and in response to determining that a representation of the control or graphical reference is included in the corresponding display view, determining whether the control or graphical reference is stored in the control configuration database, and in response to determining that the control or graphical reference is stored in the control configuration database, determining whether an associated display view or display view element corresponding to the control or graphical reference is included in a plurality of display views. 3. The method according to any one of aspects 1 or 2, comprising:
[0109] 4. The method according to any one of aspects 1-3, wherein presenting the completeness assessment report includes, for each of one or more warnings or errors in the plurality of display views, presenting an indication of the display view in which the warning or error occurred, presenting an indication of a control or graphical reference corresponding to the warning or error, and presenting a description of the warning or error.
[0110] 5. The method according to any one of aspects 1-4, further comprising presenting an indication of the particular display view element of the display view in which the warning or error was discovered.
[0111] 6. The method according to any one of aspects 1-5, wherein presenting the integrity assessment report includes automatically generating and presenting the integrity assessment report by a graphical display configuration application in response to receiving a request to save one or more of the multiple display views.
[0112] 7. A method according to any one of aspects 1 to 6, wherein obtaining a representation of a set of controls or graphical references corresponding to a plurality of display views includes obtaining a representation of a set of controls or graphical references expected to be included in the plurality of display views.
[0113] 8. A method according to any one of aspects 1 to 7, wherein determining whether an indication of a control or graphical reference is included in the corresponding display view includes determining whether a display view element in the corresponding display view is configured with the control or graphical reference, or determining whether a feature included in the corresponding display view indicates the control or graphical reference.
[0114] 9. The method according to any one of aspects 1-8, wherein the control reference refers to a control module, a node, a process control device, or a signal transmitted or received by a control module, a node, or a process control device.
[0115] 10. The method according to any one of aspects 1-9, wherein the representation of the multiple display views is obtained from a centralized graphical configuration database storing display view elements each defining a configuration of a respective display view.
[0116] 11. A computing device for evaluating completeness of a graphical display configuration of a process plant, comprising: one or more processors; a user interface; a communication unit; and a non-transitory computer readable medium coupled to the one or more processors, the user interface, and the communication unit, the non-transitory computer readable medium having stored thereon a graphical display configuration application for executing within a configuration environment of the process plant, the graphical display configuration application, when executed by the one or more processors, causing the computing device to obtain a representation of a plurality of display views combining each display view including a representation of a process control element to represent the process plant, obtain a representation of a set of control or graphical references corresponding to the plurality of display views, each set of control or graphical references corresponding to one of the plurality of display views, each control or graphical reference in the set of control or graphical references referencing a process control element or display view element displayed in the corresponding display view, and for each control or graphical reference in each of the sets, determine whether the representation of the control or graphical reference is included in the corresponding display view, and (ii) whether the control or graphical reference is included in control configuration data. and presenting, via a user interface, an integrity assessment report indicating one or more warnings or errors in the plurality of display views, wherein the one or more warnings or errors are identified based on at least one of: (i) a representation of a control or graphical reference in the set of controls or graphical references is not included in a corresponding display view, (ii) a control or graphical reference in the set of controls or graphical references is not stored in a control configuration database, or (iii) an associated display view or display view element corresponding to a control or graphical reference in the set of controls or graphical references is not included in the plurality of display views.
[0117] 12. A computing device according to aspect 11, wherein the graphical display configuration application further causes the computing device to generate a warning or error corresponding to the control or graphical reference in response to determining that, for each control or graphical reference in each of the sets of controls or graphical references, the corresponding display view does not include a display of the control or graphical reference, the control or graphical reference is not stored in the control configuration database, or an associated display view or display view element corresponding to the control or graphical reference is not included in the multiple display views.
[0118] 13. A computing device according to any one of aspect 11 or aspect 12, wherein the graphical display configuration application causes the computing device to determine whether a display of the control or graphical reference is included in the corresponding display view, (ii) whether the control or graphical reference is stored in a control configuration database, or (iii) whether an associated display view or display view element corresponding to the control or graphical reference is included in multiple display views, in response to determining that a display of the control or graphical reference is included in the corresponding display view, determines whether the control or graphical reference is stored in the control configuration database, and in response to determining that the control or graphical reference is stored in the control configuration database, determines whether an associated display view or display view element corresponding to the control or graphical reference is included in multiple display views.
[0119] 14. A computing device according to any one of aspects 11 to 13, wherein, to present the completeness assessment report, the graphical display configuration application causes the computing device to present, for each of one or more warnings or errors in a plurality of display views, a display of the display view in which the warning or error occurred, present, via the user interface, a display of a control or graphical reference corresponding to the warning or error, and present, via the user interface, a description of the warning or error.
[0120] 15. A computing device according to any one of aspects 11-14, wherein the graphical display configuration application further causes the computing device to present, via a user interface, an indication of the particular display view element of the display view in which the warning or error was discovered.
[0121] 16. To present the integrity assessment report, a graphical display configuration application configures the computing device to display one or more of a plurality of display views. 16. A computing device according to any one of aspects 11 to 15, further comprising: a computing device configured to automatically generate and present an integrity assessment report in response to receiving a request to store the above.
[0122] 17. A computing device according to any one of aspects 11 to 16, wherein to obtain a display of a set of controls or graphical references corresponding to the multiple display views, a graphical display configuration application causes the computing device to obtain a display of a set of controls or graphical references expected to be included in the multiple display views.
[0123] 18. A computing device according to any one of aspects 11 to 17, wherein to determine whether a display of a control or graphical reference is included in the corresponding display view, the graphical display configuration application causes the computing device to determine whether a display view element in the corresponding display view is configured with a control or graphical reference, or to determine whether a function included in the corresponding display view indicates a control or graphical reference.
[0124] 19. A computing device according to any one of aspects 11 to 18, wherein to determine whether a display of a control or graphical reference is included in the corresponding display view, the graphical display configuration application causes the computing device to determine whether a display view element in the corresponding display view is configured with a control or graphical reference, or to determine whether a function included in the corresponding display view indicates a control or graphical reference.
[0125] 20. A computing device according to any one of aspects 11-19, wherein the representation of the multiple display views is obtained from a centralized graphical configuration database storing display view elements each defining a configuration of a respective display view.
[0126] Additionally, the above-described aspects of the present disclosure are merely representative and are not intended to limit the scope of the present disclosure.
[0127] 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. That is, the methods described herein may be embodied by a set of machine-readable instructions stored on a computer-readable medium (i.e., on a memory device), such as the one illustrated in FIG. 1B. The instructions, when executed by one or more processors of a corresponding device (e.g., a server, a user interface 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 words "stored" and "saved" are intended to exclude transitory signals.
[0128] Additionally, the terms "operator," "personnel," "people," "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, and these terms are not intended to be limiting. When a particular term is used in the description, the term is used in part for traditional activities engaged in by plant personnel, but is not intended to limit the personnel who may engage in a particular activity.
[0129] Additionally, throughout this specification, multiple instances may implement the structures described as components, operations, or single instances. Although 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 an example configuration 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 fall within the scope of the subject matter of this specification.
[0130] Unless specifically stated otherwise, discussions herein using words such as "processing," "computing," "calculating," "determining," "identifying," "presenting," "causing to present," "displaying," "displaying," and the like may refer to mechanical (e.g., computer) acts 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.
[0131] When 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, a laser disk, a solid-state memory device, a molecular memory storage device, or other storage medium in the RAM or ROM of a computer or processor. Although an example of a system disclosed herein has been disclosed as including software and / or firmware running on hardware, among other components, it should be noted that such a system is merely exemplary and should not be considered as 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, one skilled in the art will readily appreciate that the provided example is not the only way to implement such a system.
[0132] Thus, while the invention has been described with reference to specific examples, these are merely illustrative and are not intended to be limitations of the invention, and it will be apparent to those skilled in the art that modifications, additions or deletions may be made to the disclosed embodiments without departing from the concept and scope of the invention.
[0133] It should also be understood that unless a term is expressly defined in this patent using the sentence "As used herein, the term '_____' is defined herein to mean ..." or a similar sentence, there is no intention, either expressly or by implication, to limit the meaning of the term 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 language of the claims). To the extent that any term recited in the final claims of this patent is recited in a manner consistent with a single meaning in this patent, this is done solely for clarity so as not to confuse the reader, and is not intended to limit such claim term, implicitly or otherwise, to that single meaning. Finally, unless a claim element is defined by the words "means" and a recitation of a function without any recitation of structure, the scope of any claim element is not intended to be construed under 35 U.S.C. § 112(f) and / or pre-AIA 35 U.S.C. § 112, section 6.
[0134] Furthermore, while the above text reveals detailed descriptions of many different embodiments, the present patent application It should be understood that the scope is defined by the terms of the claims set forth at the end of this patent. The detailed description should be construed as merely representative and does not describe all possible embodiments, 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, which would still fall within the scope of the claims.
Claims
1. 1. A method for assessing completeness of a graphical display configuration of a process plant, comprising: obtaining, by a computing device executing a graphical display configuration application in a configuration environment of a process plant, a representation of a plurality of display views to be combined to represent the process plant, each display view including a representation of a process control element; obtaining, by the graphical display configuration application, a display of sets of controls or graphical references corresponding to the plurality of display views, each set of controls or graphical references corresponding to one of the plurality of display views, and each control or graphical reference in the set of controls or graphical references referencing a process control element or display view element displayed in the corresponding display view; For each control or graphical reference in each of said sets: determining whether a representation of the control or graphical reference is included in the corresponding display view; in response to determining that the representation of the control or graphical reference is included in the corresponding display view, determining whether an associated display view or display view element corresponding to the control or graphical reference is included in the plurality of display views; presenting, by the graphical display configuration application, a completeness assessment report indicating one or more warnings or errors in the plurality of display views based on an analysis of each of the plurality of display views, wherein the one or more warnings or errors are identified based on at least one of: (i) a representation of a control or graphical reference in the set of controls or graphical references is not included in a corresponding display view, or (ii) an associated display view or display view element corresponding to a control or graphical reference in the set of controls or graphical references is not included in the plurality of display views.
2. 2. The method of claim 1, further comprising: generating a warning or error corresponding to each control or graphical reference in each of the sets of controls or graphical references in response to determining that the corresponding display view does not include the display of the control or graphical reference, that the control or graphical reference is not stored in a control configuration database, or that an associated display view or display view element corresponding to the control or graphical reference is not included in the plurality of display views.
3. Presenting an integrity assessment report includes, for each of the one or more warnings or errors in the plurality of display views: presenting an indication of the display view in which the warning or error occurred; and presenting an indication of said control or graphical reference corresponding to said warning or error; and providing an explanation of the warning or error.
4. The method of claim 3 , further comprising presenting an indication of the particular display view element of the display view in which the warning or error was discovered.
5. Presenting the integrity assessment report includes configuring the graphical display configuration application in response to receiving a request to save one or more of the plurality of display views. automatically generating and presenting said integrity assessment report via a obtaining a representation of a set of controls or graphical references corresponding to the plurality of display views includes obtaining a representation of a set of controls or graphical references expected to be included in the plurality of display views; determining whether the indication of the control or graphical reference is included in the corresponding display view includes determining whether a display view element in the corresponding display view is configured with the control or graphical reference, or determining whether a feature included in the corresponding display view indicates the control or graphical reference; The method according to any one of claims 1 to 4, wherein the method is at least one of the following:
6. 6. The method of claim 1, wherein the representation of the plurality of display views is obtained from a centralized graphical configuration database storing display view elements each defining a configuration of the respective display view.
7. 1. A computing device for evaluating the completeness of a graphical display configuration of a process plant, comprising: one or more processors; A user interface; A communication unit; a non-transitory computer readable medium coupled to the one or more processors, the user interface, and the communication unit; the non-transitory computer readable medium storing a graphical display configuration application for executing within a configuration environment of a process plant; A computing device, wherein the graphical display configuration application, when executed by the one or more processors, causes the computing device to perform each of the steps of the method of any one of claims 1 to 6.
Citation Information
Patent Citations
Monitoring screen verification device
JP2012168776A
Monitoring control system
JP2014153794A
Measurement device and measurement system
JP2015022569A
