Graphical user interface (GUI) system and method for refactoring full-size process plant displays at various zoom and detail levels for visualization on mobile user interface devices - Patents.com

The GUI-based system efficiently displays full-size process plant information on mobile devices by regionalizing and refactoring displays, addressing inefficiencies and safety risks associated with small screen devices, ensuring operators can quickly access critical alarms and data.

JP7590137B2Active Publication Date: 2024-11-26FISHER ROSEMOUNT SYST INC
View PDF 14 Cites 0 Cited by

Patent Information

Application Number
JP2020149122
Authority / Receiving Office
JP · JP
Patent Type
Patents
Current Assignee / Owner
Priority Date
2019-09-17
Filing Date
2020-09-04
Publication Date
2024-11-26
Estimated Expiration
2040-09-04

AI Technical Summary

Technical Problem

Displaying large process displays on small screen devices such as mobile phones and tablets is inefficient, leading to reduced situational awareness and increased risk of missed critical alarms due to limited processing power and memory, making it difficult for operators to locate necessary information during emergencies.

Method used

A GUI-based system and method for regionalizing and refactoring full-size process plant displays on mobile user interface devices, involving automatic detection and rendering of display portions, allowing operators to view relevant information at various zoom levels and details without requiring new graphics development.

Benefits of technology

Enhances situational awareness by efficiently displaying critical process information on mobile devices, reducing processing and memory requirements, and enabling quick navigation to alarm information, thus improving operational safety.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure 0007590137000001
    Figure 0007590137000001
  • Figure 0007590137000002
    Figure 0007590137000002
  • Figure 0007590137000003
    Figure 0007590137000003
Patent Text Reader

Abstract

To provide GUI-based systems and methods for regionizing full-size process plant display for rendering on mobile user interface devices.SOLUTION: A regionizer application receives full-size process plant display that graphically represents at least a portion of a process plant that includes graphic representations of a plurality of process plant entities. The regionizer application determines display regions of the full-size process plant display that define corresponding view portions of the full-size process plant display. The display regions are transmitted to a mobile user interface device for rendering by a mobile display navigation application.SELECTED DRAWING: None
Need to check novelty before this filing date? Find Prior Art

Description

[Technical field]

[0001] The present disclosure relates generally to guided user interface (GUI) based systems and methods for rendering a full-sized process plant display on a mobile user interface device, and more specifically to systems and methods for regionalizing a full-sized process plant display for rendering on a mobile user interface device, systems and methods for automatically detecting graphical process control loop display portions within a full-sized process plant display for rendering on a mobile user interface device, and systems and methods for refactoring a full-sized process plant display at various zooms and levels of detail for visualization on a mobile user interface device. [Background technology]

[0002] A distributed process control system, such as those used in chemical, petroleum, industrial, or other processes, generally includes one or more process controllers and input / output (I / O) devices communicatively coupled to at least one host or operator interface and one or more field devices via an analog, digital, or mixed analog / digital bus, or via a wireless communication link or network. The field devices, which may be, for example, valves, valve positioners, switches, transmitters (e.g., temperature sensors, pressure sensors, water level sensors, and flow sensors), are positioned within the process environment and typically perform physical or process control functions, such as opening and closing valves, measuring process parameters that control one or more process executions within a process plant or system. Smart field devices, such as field devices conforming to the well-known Fieldbus protocol, may also perform control calculations, alarm functions, and other control functions typically implemented within a controller. A process controller, also generally located within a plant environment, executes a controller application that executes different control modules that receive signals indicative of process measurements made by sensors or field devices and / or other information regarding the field devices, e.g., make process control decisions and generate control signals based on the received information, and interface with control modules or blocks that execute in the field devices, such as HART®, Wireless HART®, and FOUNDATION® Fieldbus field devices. The control modules within the controller send control signals over communication lines or links to the field devices, thereby controlling the operation of at least a portion of a process plant or system.

[0003] Information from the field devices and controllers is typically made available via 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, which are generally located in a control room or other location away from the harsher plant environment. Each of these hardware devices is generally, but not always, centralized across the process plant or across portions of the process plant. These hardware devices execute applications that may enable operators to perform functions related to the control of the process and / or operation of the process plant, such as, for example, changing settings of process control routines, modifying the operation of control modules in controllers or field devices, viewing the current state of the process, viewing alarms generated by field devices and controllers, simulating the operation of the process for purposes of training personnel or testing process control software, maintaining and updating configuration databases, etc. Utilizing the data highway by the hardware devices, the controllers and field devices may include wired communication paths, wireless communication paths, or a combination of wired or wireless communication paths.

[0004] As an example, the DeltaV™ control system sold by Emerson Process Management includes multiple applications stored in and executed by different devices located at various locations within a process plant. Each of these applications provides a user interface (UI) that allows a user (e.g., configuration engineers, operators, maintenance technicians, etc.) to view and / or modify aspects of the operation and configuration of the process plant. Throughout this specification, the terms “user interface,” “UI,” and / or “guided user interface (GUI)” are used to refer to an application or screen that allows a user to view or modify the configuration, operation, or status of the process plant. Similarly, the terms “user interface device” or “UI device” and / or “GUI device” are used to refer to the device on which the user interface is operating, 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.). Configuration applications residing in one or more operator workstations or computing devices enable users to create or modify process control modules and download these process control modules over a data highway to dedicated distributed controllers. Generally, these control modules are made up of communicatively interconnected function blocks that perform functions within a control scheme based on inputs thereto and provide outputs to other function blocks in the control scheme. The configuration application may also enable the configuration engineer to create or modify operator interfaces that are used by the viewing application to display data to the operator and to enable the operator to change settings, such as set points, within the process control routines.Each dedicated controller, and in some cases one or more field devices, stores and executes a respective controller application that executes the control modules assigned to and downloaded thereto to implement the actual process control function. A viewing application may be executed on one or more operator workstations (or one or more remote computing devices communicatively connected to the operator workstations and the data highway) that receives data from the controller applications over the data highway and displays this data to a process control system engineer, operator, or user using a UI that may provide any of several different views, such as an operator's view, an engineer's view, a technician's view, etc. While the data history application is generally stored on and executed by a data history device that collects and stores some or all of the data provided across the data highway, a configuration database application may be executed on a more remote computer attached to the data highway to store the current process control routine configuration and data associated therewith. Alternatively, the configuration database may be located in the same workstation as the configuration application.

[0005] As discussed above, operator display applications are generally implemented on a system broadly based on one or more workstations to provide displays to an operator or maintenance personnel based on the operational status of devices within a control system or plant. Generally, these displays take the form of alarm displays that receive alarms generated by a controller or devices within the process plant, control displays that indicate the operational status of the controller and other devices within the process plant, maintenance displays that indicate the operational status of devices within the process plant, and the like. These displays are generally configured to display information or data received from the process control modules, or devices within the process plant, in a known manner. In some known systems, the display has graphics associated with physical or logical elements that are communicatively coupled to the physical or logical elements to receive data regarding the physical or logical elements. The graphics may be changed on the display screen based on the received data, for example, to illustrate a half-full tank or to illustrate a flow rate measured by a flow sensor.

[0006] In known implementations, the UI may be configured to display a graphical representation of the process plant or portions thereof, commonly referred to as a "process display." Process displays are typically designed to be displayed on large screens, such as standard 21-inch or 27-inch monitors with an aspect ratio of 16:9. As a result, process displays are typically configured for large screens and typically contain a large amount of graphics and information related to the process plant. For example, a single process display may contain a large amount of graphics and information about one or more processes operating within the process plant. These processes are typically maintained and controlled by a control module for the process plant. The control module, in turn, generates or provides important information about the processes, such as process values, alarm information, and other diagnostic information about the operating status of the process plant.

[0007] However, problems arise when displaying or providing large process displays on small screen devices such as mobile phones and tablets. When a process display originally configured for a large process display is displayed on a small area screen device, it becomes difficult for plant operators to find information specific to the plant, especially during an emergency such as an emergency with an active alarm. For example, on a small surface device, only a small subset of the visualization is rendered on the screen at a given time. Operator effectiveness is reduced when they have to find the required visualization. Furthermore, small screen devices typically have limited processing power and memory capacity, making it impossible to render large process displays on such devices.

[0008] Furthermore, having standard out-of-the-box UI gestures such as pan and zoom to navigate within a process display usually does not solve the problem. This is especially true for more detailed and / or large process displays with numerous control modules, field devices, or other process plant entities, each with their own detailed measurements and values, many of which are constantly changing. Operating such a large process display on a small screen device requires the user to constantly zoom and pan to find and read the value they need at that time. This not only creates inefficiencies but also reduces situational awareness among plant operators who use mobile devices to monitor the process plant. For these reasons, this can also lead to dangerous situations in the process plant. For example, it is not uncommon for operators to miss alarms or for the mobile device to notify the operator properly of values ​​reaching critical thresholds, since process displays rendered on small screens are not always fully visible and / or due to physical (e.g., mobile device processing and memory limitations). Failure to detect these critical readings can lead to damage to the process plant and / or damage to operators, personnel, or other assets within the process plant.

[0009] For the foregoing reasons, there is a need for a system and method for regionalizing a full-sized process plant display for rendering on a mobile user interface device.

[0010] Moreover, for the foregoing reasons, there is a further need for a system and method that automatically detects portions of a graphical process control loop display within a full-sized process plant display for rendering on a mobile user interface device.

[0011] Additionally, for the aforementioned reasons, there is a further need for systems and methods for refactoring full-sized process plant displays at various zoom and detail levels for visualization on mobile user interface devices. Summary of the Invention

[0012] The present disclosure generally describes embodiments of systems and methods for rendering large process displays, or portions delimited or generated therefrom, in an efficient and effective manner on small surface devices, such as mobile user interface devices. The present disclosure overcomes problems in the prior art by describing efficient resource usage (e.g., processor and memory usage) and visualization systems and methods for determining and rendering display areas, view portions, and other graphical representations of large process displays on small screen devices with reduced surface area.

[0013] For example, as disclosed for various embodiments, the systems and methods of the present application address the problems presented by novel graphics determination, detection, and rendering techniques for enabling an operator to view large process displays on a small screen device (e.g., a mobile user interface device) while attempting to maintain or at least reduce the impact on situational awareness. In various embodiments, the systems and methods described by the present application determine and render graphics and displays for a small screen device without requiring a graphics developer or computer programmer to develop new code, graphics, or display graphics for the small screen device. That is, instead of a graphics developer or computer programmer having to redesign, redesign, and maintain a new set of process displays configured for the small screen device, the systems and methods described herein automatically use the large process displays originally designed for the full-sized display screen of the process plant and, as described herein, regionalize, refactor, and / or automatically introspect the full-sized display screen to determine selected graphic display areas and view portions of the full-sized display screen and render them on the small screen device.

[0014] Additionally, because the systems and methods described herein are configured to operate with existing process displays (e.g., large process displays), the systems and methods described herein can enhance existing UI products typically used in process plants, such as DeltaV Mobile offered by Emerson Process Management.

[0015] Accordingly, in various embodiments disclosed herein, a graphical user interface (GUI) based system and method for regionalizing a full-sized process plant display for rendering on a mobile user interface device is disclosed. The GUI based system and method may include receiving, at a regionalizer application (app) executing on one or more processors, a full-sized process plant display that graphically represents at least a portion of the process plant. The full-sized process plant display may include a graphical representation of a plurality of process plant entities within the process plant. The full-sized process plant display may include a GUI adapted for rendering on a full-sized display screen of the process plant. The GUI based system and method may further include determining, by the regionalizer app, one or more display areas of the full-sized process plant display. Each of the one or more display areas may define a view portion of the full-sized process plant display. Further, each of the one or more display areas may include at least one graphical representation of a process plant entity selected from the plurality of process plant entities. The GUI based system and method may further include transmitting, by the one or more processors, the one or more display areas to a mobile user interface device. The mobile user interface device may execute a mobile display navigation app. The mobile display navigation app may render each of the one or more display regions on a display screen of a mobile user interface device, the mobile user interface device having a surface area that is less than the full-sized surface area of ​​a full-sized display screen.

[0016] In additional embodiments disclosed herein, GUI-based systems and methods are disclosed for automatically detecting and rendering a graphical process control loop display portion within a full-sized process plant display on a mobile user interface device. The GUI-based systems and methods may include receiving, at a display automatic introspection routine executing on one or more processors, a full-sized process plant display graphically representing at least a portion of the process plant. The full-sized process plant display may include a graphical representation of a plurality of process plant entities within the process plant. Additionally, the full-sized process plant display may include a GUI adapted for rendering on a full-sized display screen of the process plant. The GUI-based systems and methods may further include automatically detecting, by the display automatic introspection routine, a graphical process control loop display portion depicted within the full-sized process plant display. The graphical process control loop display portion may include a graphical representation of one or more process plant entities selected from the plurality of process plant entities. The GUI-based systems and methods may further include generating, by the one or more processors, a selectable display list representing the one or more process plant entities depicted within the graphical process control loop display portion. The GUI-based systems and methods may further include transmitting, by the one or more processors, the graphical process control loop display portion and the selectable display list to a mobile user interface device. In various embodiments, the mobile user interface device may execute a mobile display navigation app. The GUI-based systems and methods may further include rendering, by the mobile display navigation app, the selectable display list within a first area of ​​a display screen of the mobile user interface device.Additionally, the GUI based systems and methods may further include rendering, by the mobile display navigation app, the graphical process control loop display portion within a second area of ​​the display screen of the mobile user interface device. In various embodiments, the mobile display navigation app may be adapted to adjust a zoom level to focus the particular process plant entity within the graphical process control loop display portion for display in the second area of ​​the display screen of the mobile user interface device upon receiving a selection from the selectable display list of the one or more process plant entities corresponding to the particular process plant entity.

[0017] In additional embodiments disclosed herein, GUI-based systems and methods are disclosed for refactoring a full-sized process plant display at various zoom and detail levels for visualization on a mobile user interface device. The GUI-based systems and methods may include transmitting, by one or more processors, the full-sized process plant display to a mobile user interface device. The full-sized process plant display may graphically represent at least a portion of the process plant. Further, the full-sized process plant display may include a graphical representation of a plurality of process plant entities within the process plant. In various embodiments, the full-sized process plant display may be a GUI adapted to render on a full-sized display screen of the process plant. The GUI-based systems and methods may further include rendering, by a mobile display navigation app executing on a processor of the mobile user interface device, a first view portion of the full-sized process plant display on a display screen of the mobile user interface device. The first view portion may define a first zoom level and a first detail level of a process plant entity selected from the plurality of process plant entities. In various embodiments, the display screen of the mobile user interface device may include a surface area that is less than a full-sized surface area of ​​the full-sized display screen. The GUI-based system and method may further include receiving, in the mobile display navigation app, a gesture command corresponding to a user manipulation of a surface area of ​​the mobile user interface device. The GUI-based system and method may further include, upon receiving the gesture command, rendering, by the mobile display navigation app, a second view portion of the full-sized process plant display on a display screen of the mobile user interface device. The second view portion may define a second zoom level and a second detail level of the process plant entities.In various embodiments, the first zoom level may be different from the second zoom level and / or the first level of detail may be different from the second level of detail.

[0018] In accordance with the above and the disclosure herein, the present disclosure includes improvements in computer functionality or other technologies. That is, the present disclosure describes improvements in the functionality of the computer itself or "any other technology or technical field" since only the necessary view portion of the relevant display area needs to be shown on the display screen of the mobile UI device. This reduces the processing resources required for the mobile UI device. Furthermore, the improvements described herein reduce the payload and traffic of the computer network since (at least in some embodiments) the full-sized process representation does not need to be transferred over the network backbone. Furthermore, the GUI-based system and method for refactoring full-sized process plant representations at various zoom and detail levels improves the performance of the mobile user interface device by rendering less visualization and / or graphics by the user interface device, reducing the processing power required and the memory usage required by the user interface device.

[0019] Additionally, the present disclosure relates to improvements over other techniques or technical fields, at least generally, because by determining and / or adjusting the display areas, as described herein, an end user of a mobile display navigation application can experience that the display areas are "custom built" for their respective mobile user interface device, without the need for a computer programmer or designer to create and / or maintain additional process displays for each of the display areas. Additionally, in some embodiments, the process modules may be rendered in a scrollable list format, for example, by the mobile display navigation app. In further embodiments, visualizations related to alarm information may be rendered in a scrollable list format. In this manner, display auto-introspection helps an operator maintain or even improve the experience of operation even on a small surface. For example, in an embodiment implementing a display auto-introspection routine, valuable information (e.g., measured parameters) is exposed to an operator of the process plant by analyzing a full-sized process plant display to determine visualizations of process modules as part of a graphical process control loop display. Additionally, this also allows an operator to quickly and efficiently navigate to value information on the display, for example, tapping on an item in a selectable display list automatically zooms the display and visualizes the display.

[0020] The disclosure includes application of certain claim elements in or by use of certain machines, for example, a user can adjust any graphic detail, measurement parameter detail, on a screen where the current zoom level corresponds to the level of detail of information displayed on the display screen of the mobile UI device. Thus, a user of a mobile user interface device can view process or alarm information on a display screen that is native to the process control system in an efficient manner on a mobile user interface device having a small screen. Additionally, process plant entities of a process plant may be configured from a mobile UI device. For example, by using configuration options, such as through configuration commands, a user or program application may select regions of operator graphics that are automatically displayed as scrollable pages on the mobile device. These regions may be selected in sizes that reflect the size and resolution of the screen of a mobile phone or tablet, and may be displayed in a variety of ways depending on whether the mobile device is using a browser or native browser. Bumo When you launch a mobile app, the app may automatically detect the screen size of your mobile device and render graphics at a resolution and / or size that matches your mobile device.

[0021] Additionally, the present disclosure includes translating or reducing a particular article to a different state or thing, such as a command that can be sent to a server of the process plant to adjust or modify a parameter of a process plant entity. In this manner, monitoring and control of the process plant can be performed on a small screen device, such as a mobile user interface device as described herein.

[0022] The advantages will become more apparent to those skilled in the art from the following description of preferred embodiments shown and described by way of example. As will be understood, the present embodiments are capable of other and different embodiments, and their details are capable of modification in various respects. Accordingly, the drawings and description are to be regarded as illustrative in nature, and not as restrictive. [Brief description of the drawings]

[0023] [Figure 1A] 1 is a block diagram of an example process control network operating in a process control system or process plant as described in various embodiments herein. [Figure 1B] FIG. 1B is a block diagram of an example user interface device communicatively coupled to the process control network of FIG. 1A. [Figure 1C] FIG. 1B is a block diagram of an example server of the process control network of FIG. 1A. [Diagram 2] 1B is an embodiment of a full-sized display screen showing an example full-sized process plant view that is a graphical representation of at least a portion of the process plant of FIG. 1A. [Figure 3A] 3 is an embodiment of a mobile user interface device that renders a first display region of the example full-sized process plant display of FIG. 2 on a display screen of the mobile user interface device. [Figure 3B] 3B is the mobile user interface device of FIG. 3A rendering a second display area of ​​the example full-sized process plant display of FIG. 2 on a display screen. [Figure 4] 3 is a flow diagram representing an example GUI-based method for regionalizing a full-sized process plant representation, such as the example full-sized process plant representation of FIG. 2, for rendering on a mobile user interface device. [Figure 5A] 3 is an embodiment of a mobile user interface device rendering an example graphical process control loop display portion of the example full-size process plant display of FIG. 2 on a display screen of the mobile user interface device, and an example selectable display list including measurement parameters of one or more process plant entities depicted within the example graphical process control loop display portion. [Figure 5B]5B is a diagram of a mobile user interface device of FIG. 5A that renders the example graphical process control loop display portion of FIG. 5A and further renders an example selectable display list including alarm indicators for one or more process plant entities depicted within the example graphical process control loop display portion. [Figure 6] 5C is a list of example measured parameters of one or more process plant entities of FIGS. 5A and 5B. [Figure 7] FIG. 3 is a flow diagram illustrating an example GUI-based method for automatically detecting portions of a graphical process control loop display depicted within a full-sized process plant display, such as the example full-sized process plant display of FIG. 2, by a display auto-introspection routine. [Figure 8A] 3 is an embodiment of a mobile user interface device that renders a first view portion of the example full-sized process plant display of FIG. 2 on a display screen of the mobile user interface device, the first view portion defining a first zoom level and a first level of detail of the process plant entities. [Figure 8B] 8A is a mobile user interface device of FIG. 8A rendering a second view portion of the example full-sized process plant display of FIG. 2, the second view portion defining a second zoom level and a second level of detail of the process plant entities. [Figure 9] FIG. 8 is a flow diagram representing an example of an exemplary GUI-based method for refactoring a full-sized process plant display, such as the full-sized process plant display of FIG. 2, at various zoom and detail levels for visualization on a mobile user interface device, such as shown in FIGS. 8A and 8B. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0024] 1A is a block diagram of an example process control network 100 operating in a process control system or process plant 10 as described in various embodiments herein. The process control network 100 may include a network backbone 105 that provides connectivity directly or indirectly and / or wired or wirelessly between various other devices. Devices coupled to the network backbone 105, in various embodiments, include combinations of access points 72, gateways 75 to other process plants (e.g., via an intranet or corporate-wide area network), gateways 78 to external systems (e.g., to the Internet), UI devices 112 that may be fixed (e.g., traditional operator workstations) or mobile computing devices (e.g., mobile devices, tables, cell phones, smartphones, etc.), servers 150, controllers 11, input / output (I / O) cards 26 and 28, wired field devices 15-22, wireless gateways 35, and wireless communication networks 70. The communication network 70 may include wireless devices 40-58, including wireless field devices 40-46, wireless adapters 52a and 52b, access points 55a and 55b, and a router 58. The wireless adapters 52a and 52b may be connected to non-wireless field devices 48 and 50, respectively. The controller 11 may include a processor 30, a memory 32, and one or more control routines 38. Although FIG. 1A depicts only one of several of the devices connected to the network backbone 105, it will be understood that each of the devices may have multiple instances on the network backbone 105 and, in fact, the process plant 10 may include multiple network backbones 105.

[0025] The UI device 112 may be communicatively connected to the controller 11 and the wireless gateway 35 via the network backbone 105. The controller 11 may be communicatively connected to the wired field devices 15-22 via the input / output (I / O) cards 26 and 28, and may be communicatively connected to the wireless field devices 40-46 via the network backbone 105 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-46. The controller 11, which may be a DeltaV™ controller sold by Emerson Process Management, by way of example, is communicatively connected to the process control network backbone 105. The controller 11 may also be communicatively connected to the field devices 15-22 and 40-46 using any desired hardware and software, for example, standard 4-20 mA devices, I / O cards 26, 28, and / or associated with any smart communication protocol, such as FOUNDATION® Fieldbus protocol, HART® protocol, Wireless HART® protocol, etc. In the embodiment illustrated in FIG 1A, the controller 11, field devices 15-22 and I / O cards 26, 28 are wired devices and the field devices 40-46 are wireless field devices.

[0026] In operation of the UI device 112, the UI device 112, in some embodiments, may execute a user interface ("UI"), where the UI device 112 may accept input via an input interface and provide output to a display. The UI device 112 may receive data (e.g., data related to a process, such as process parameters, log data, sensor data, and / or any other data that may be captured and stored) from the server 150. The server 150 may comprise one or more processors and / or memory for executing instructions, implementing software, or otherwise implementing or invoking the flow diagrams, methods, or other aspects disclosed herein. In some embodiments, the server 150 may be part of or located within the process plant 10. In other embodiments, the server 150 may be a server, such as a cloud server, external to the process plant 10. For example, the server 150 may be a third party cloud server, such as a Microsoft Azure-based cloud server, an Amazon Web Services (AWS) server, or the like.

[0027] In other embodiments, the UI may be executed, in whole or in part, on the server 150, which may transmit display data to the UI device 112. The UI device 112 may receive UI data (which may include display data and process parameter data) from other nodes in the process control network 100, such as the controller 11, the wireless gateway 35, or the server 150, via the backbone 105. Based on the UI data received at the UI device 112, the UI device 112 may provide output (i.e., a visualization or graphic) that represents aspects of a process associated with the process control network 100, allowing a user to monitor the process. A user may also affect control of the process by providing input at the UI device 112. To illustrate, the UI device 112 may provide a graphic that represents, for example, a tank filling process. In such a scenario, a user may read a water level measurement in a tank and determine that the tank needs to be filled. The user may interact with a graphic of an inlet valve displayed on the UI device 112 and enter a command that the inlet valve open.

[0028] In an embodiment, the UI device 112 may implement any type of client, such as a thin client, a web client (e.g., via a browser), or a thick client. For example, the UI device 112 may rely on other nodes, computers, UI devices, or servers for most of the processes required for the operation of the UI device 112 if the UI device has limited memory, battery power (e.g., in a wearable device). In such an example, the UI device 112 may communicate with a server 150 or another UI device, which may then communicate with one or more other nodes (e.g., servers) on the process control network 100 to determine graphics, display data, and / or process data to send to the UI device 112. Additionally, the UI device 112 may pass any data associated with received user input to the server 150 so that the server 150 may process the data associated with the user input and act accordingly. In other words, the UI device 112 need only render graphics and may act as a portal to one or more nodes or servers that store data and execute routines required for the operation of the UI device 112. A thin-client UI device offers the advantage of minimal hardware requirements of the UI device 112. The thin-client UI may be implemented via a browser, which may be a web browser application, to render various displays or GUIs as described herein.

[0029] In various embodiments, the UI device 112 may be a web client. In such an embodiment, a user of the UI device 112 may interact with the process control system via the control unit 94 or the mobile display navigation app 95 of the UI device 112. The control unit 94 and / or the mobile display navigation app 95 may enable the user to access data and resources of another node or server 150 (such as the server 150) via the backbone 105. For example, the mobile display navigation app 95 may be a web browser that can receive and render graphics / UI data, such as display data and process parameter data, from the server 150, allowing the mobile display navigation app 95 to depict graphics used to control and / or monitor the mobile display navigation app 95. The mobile display navigation app 95 (e.g., functioning as a browser) may also receive user input (such as a mouse click or a gesture command on a graphic). The user input may cause the mobile display navigation app 95 to retrieve or access information resources stored on the server 150. For example, a mouse click or gesture command may cause the mobile display navigation app 95 to retrieve (from the server 150) and display information about the graphic that was clicked or manipulated.

[0030] In yet other embodiments, the majority of the processing of the UI device 112 may occur at the UI device 112. For example, the UI device 112 may execute the UIs discussed previously. The UI device 112 may also store, access, and analyze data locally.

[0031] In operation, a user may interact with the UI device 112 to monitor or control one or more devices in the process control network 100, such as any of the field devices 15-22 or devices 40-48. The user may interact with the UI device 112, for example, to 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 control loops. The processor 30 may communicate with the field devices 15-22 and 40-46, as well as other nodes communicatively connected to the backbone 105. 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 implemented or performed by different controllers or other devices, if desired. Similarly, the control routines or modules described herein that are implemented within a process control system may take any form, including software, executable instructions, firmware, hardware, etc. The control routines may be implemented in any desired software format, such as using object-oriented programming, ladder logic, sequential function charts, functional block diagrams, or any other software programming language or design paradigm. In particular, the control routines may be implemented by a user via the UI device 112. The control routines may be stored in any desired type of memory, such as random access memory (RAM) or read-only memory (ROM). Similarly, the control routines may be hard-coded, for example, in one or more EPROMs, EEPROMs, application specific integrated circuits (ASICs), or any other hardware or firmware elements. Thus, the controller 11 may be configured (in an embodiment, by a user using the UI device 112) to implement the control strategies or control routines in any desired manner.

[0032] In some embodiments of the UI device 112, a user interacts with the UI device 112 to implement a control strategy in the controller 11 using what are generally referred to as function blocks, each of which is an object or other portion (e.g., a subroutine) of an overall control routine and which operates with other function blocks (through communications called links) to implement a process control loop within the process control system. A control-based function block generally performs one of the following: an input function associated with a transmitter, sensor or other process parameter measurement device; a control function associated with a control routine that controls 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 control system. Of course, hybrid and other types of function blocks exist. The function blocks may have a graphical representation provided on the UI device 112, allowing a user to easily modify the type of function block, the connections between the function blocks, and the inputs / outputs associated with each of the function blocks implemented in the process control system. The function blocks may be stored within and executed by the controller 11, which is generally the case when these function blocks are used for or associated with certain types of smart field devices, such as standard 4-20 mA devices and HART devices, or the function blocks may be stored within and implemented by the field device itself, which may be the case for Fieldbus devices. The controller 11 may include one or more control routines 38 that may implement one or more control loops. Each control loop, generally referred to as a control module, may be implemented by executing one or more function blocks.

[0033] Still referring to FIG. 1A, the wireless field devices 40-46 communicate within the wireless network 70 using a wireless protocol, such as the Wireless HART protocol. In certain embodiments, the UI device 112 may be capable of communicating with the wireless field devices 40-46 using the wireless network 70. Such wireless field devices 40-46 may communicate directly with one or more other nodes of the process control network 100 that are also configured to communicate wirelessly (e.g., using a wireless protocol). To communicate with one or more other nodes that are not configured to communicate wirelessly, the wireless field devices 40-46 may utilize a wireless gateway 35 connected to the backbone 105. Of course, the field devices 15-22 and 40-46 may conform to any other desired standard(s) or protocol, such as any standard or protocol developed in the future, or any other wired or wireless protocol.

[0034] The wireless gateway 35 is an example of a provider device that may provide access to the various wireless devices 40-58 of the wireless communication network 70. In particular, the wireless gateway 35 provides a communicative coupling between the wireless devices 40-58 and other nodes of the process control network 100 (including the controller 11 of FIG. 1A). The wireless gateway 35 provides the communicative coupling while tunneling one or more shared layers of the wired and wireless protocol stacks, in some cases, by providing routing, buffering, and timing services to the lower layers of the wired and wireless protocol stacks (e.g., address translation, routing, packet segmentation, prioritization, etc.). In other cases, the wireless gateway 35 may translate commands between wired and wireless protocols that do not share protocol layers.

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

[0036] In some scenarios, the wireless network 70 may include non-wireless devices. For example, the field device 48 of FIG. 1A may be a legacy 4-20 mA device, and the field device 50 may be a conventional wired HART device. To communicate within the network 70, the field devices 48 and 50 may be connected to the wireless communication network 70 via wireless adapters (WA) 52a or 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 wired communication with the wireless gateway 35 or may be provided within the wireless gateway 35 as an integrated device. The wireless network 70 may also include one or more routers 58 that forward packets from one wireless device to another wireless device within the wireless communication network 70. The wireless devices 32 - 46 and 52 - 58 may communicate with each other and with the wireless gateway 35 via wireless links 60 of the wireless communication network 70 .

[0037] In some embodiments, the process control network 100 may include other nodes connected to the network backbone 105 that communicate using other wireless protocols. For example, the process control network 100 may include one or more wireless access points 72 that use other wireless communication protocols, such as WiFi or other IEEE 802.11 compliant wireless local area network protocols, mobile communication protocols such as Worldwide Interoperability for Microwave Access (WiMAX), Long Term Evolution (LTE) or other ITU-R (International Telecommunication Union Radio Communication Sector) compatible protocols, shortwave wireless communications such as Near Field Communication (NFC) and Bluetooth, or other wireless communication protocols. Generally, such wireless access points 72 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 112 communicates over the process control network 100 using the wireless access points 72. 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-58) may also communicate using the wireless network supported by access point 72.

[0038] Additionally or alternatively, the provider device may include one or more gateways 75, 78 to systems external to the instant process control system. In such an embodiment, the UI device 112 may be used to control, monitor, or otherwise communicate with the external systems. Generally, such systems are customers or providers of information generated or manipulated by the process control system. For example, a plant gateway node 75 may communicatively connect the instant process plant 10 (with its own respective process control data network backbone 105) to another process plant with its own respective network backbone. In an embodiment, a single network backbone 105 may serve multiple process plants or process control environments.

[0039] In another example, the plant gateway node 75 may communicatively connect the immediate process plant to a legacy or conventional process plant that does not include the process control network 100 or backbone 105. In this example, the plant gateway node 75 may convert or translate messages between a protocol utilized by the process control big data backbone 105 of the plant 10 and a different protocol utilized by the legacy system (e.g., Ethernet, Profibus, Fieldbus, DeviceNet, etc.). In such an example, the UI device 112 may be used to control, monitor, or otherwise communicate with systems or networks within the legacy or conventional process plant.

[0040] The provider device may include one or more external system gateway nodes 78 to communicatively connect the process control network 100 with external public or private systems, such as laboratory systems (e.g., a Laboratory Information Management System, or LIMS), personnel round databases, material handling systems, maintenance management systems, product inventory control systems, production management systems, weather data systems, shipping and handling systems, packaging systems, the Internet, another provider's process control system, or other external systems. The external system gateway nodes 78 may, for example, facilitate communications between the process control system and personnel outside the process plant (e.g., personnel at home).

[0041] 1A illustrates a single controller 11 with a finite number of field devices 15-22 and 40-46, this is merely an exemplary and non-limiting embodiment. Any number of controllers 11 may be included in the provider devices of the process control network 100, and any controller 11 may communicate with any number of wired or non-wired field devices 15-22, 40-46 to control the process of 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 72, and / or gateways 75, 78.

[0042] FIG. 1B is a block diagram of an example user interface device 112. The user interface device 112 may be communicatively coupled to the process control network 100 of FIG. 1A. The UI device 112 may be a desktop computer, such as a conventional operator workstation, a control room display, or a laptop computer, a tablet computer, a mobile phone (e.g., a smartphone), a personal digital assistant (PDA), a wearable computing device, and / or any other suitable client computing device. The UI device 112 may include a display screen 84. Additionally, the UI device 112 includes one or more processors or CPUs 88, memory 90, which may be, for example, a random access memory (RAM) 90r, input / output (I / O) circuitry 91, and a communication unit 89 for transmitting and receiving data over a local area network, a wide area network, or any other suitable network. The UI device 112 may communicate with the controller 11, a server 150, and / or any other suitable computing device.

[0043] The memory 90 may include an operating system 92, a control unit 94, and a mobile display navigation (app) 95 to control and / or render graphics on the display screen 84 and communicate with the controller 11 to control the online operation of the process plant. In some embodiments, the server 150 may transmit a graphical representation of a portion of the process plant to the UI device 112, and the control unit 95 may then cause the display screen 84 to present the graphical representation of the portion of the process plant. For example, in various embodiments, the mobile display navigation app 95 may render graphics (e.g., a display area, a view portion, a GUI, a graphical display, or a graphical representation) of the process plant on the display screen 84. The control unit 94 obtains user input from the I / O circuitry 91, such as user input from an operator (also referred to herein as a user), and translates the user input into a request to display a preview of a process section that is not currently displayed, a request to display a full view of a process section that is not currently displayed, a request to switch from a preview mode to a full view mode and display one of the process sections in the full view mode, a request to display an adjustment of a process parameter included in one of the process sections, etc.

[0044] In some embodiments, the control unit 94 may communicate the translated user input to the server 150, which may generate a requested UI and send it to the UI device 112 for display. The mobile display navigation app 95 may generate a new UI based on the translated user input and present the new UI on the display screen 84 of the UI device 112. If the translated user input is a request to display an adjustment to a process parameter included in one of the process sections, the control unit 94 may determine whether the process parameter is locked. If the process parameter is locked, the control unit 94 may not adjust the process parameter and the mobile display navigation app 95 may present a message indicating that the process parameter is locked and cannot be adjusted on the display screen 84 of the UI device 112. If the process parameter is not locked, the control unit 94 may adjust the process parameter value on the display screen 84 according to the user input from the operator and provide instructions to the controller 11 to adjust the process parameter in the process plant. In other embodiments, the control unit 94 may communicate the translated user input to a server 150 which may generate and transmit adjusted process parameter values ​​to the UI device 112 for display by the mobile display navigation app 95 and provide instructions to the controller 11 to adjust the process parameters in the process plant.

[0045] 1C is a block diagram of an example server 150 of the process control network 100 of FIG. 1A. The server 150 may be a computer or a series of computers (e.g., a server farm or redundant servers) configured to receive and respond to requests from any device in the process control network 100. Such requests and responses may be data packet transmissions, such as over a computer network, such as the network backbone 105. The server 150 includes one or more processors or CPUs 160, memory 152, which may be, for example, random access memory (RAM) 152r, input / output (I / O) circuitry 162 for receiving administrator commands, and a communication unit 89 for transmitting and receiving data over a local area network, a wide area network, or other suitable network in the process control network 100, such as the network backbone 105.

[0046] The memory 152 of the server 150 may include an operating system 154, web applications 155, web services 156, and / or a mobile display navigation app 95 for regionalizing and generating display regions and transmitting display regions and other graphics, display, or graphical information to a UI device as described herein. For example, in some embodiments, the web services 156 may communicate with the native UI of a client device (e.g., the UI device 112). BumoThe web app 155 may include a Simple Object Access Protocol (SOAP)-based web service or a Representational State Transfer (RESTful) web service configured on the server 150 to receive requests from a mobile application. The web service 156 can then respond with the requested information, where the request may originate from a GUI (e.g., a user request) or by an application or component of the process plant 10. In other embodiments, the web app 155 may include web applications such as Java Server Pages (JSP), Ruby on Rails, Active Server Pages (ASP), PHP, and Node.js, or other web applications that generate dynamic web pages, displays, or graphics, as described herein, and provide such web pages, displays, or graphics to a client device (e.g., the UI device 112), as described herein. For example, in some embodiments, the server 150 may send a graphical representation of a portion of the process plant to a browser implemented on the UI device 112, as described herein.

[0047] The server 150 may also include a regionalizer app 158 for determining one or more display areas of the full-sized process plant display. This generally involves defining one or more view portions of the full-sized process plant display for each of the display areas, as described herein. In various embodiments, the regionalizer application can determine X and Y coordinates (e.g., pixel values) of the full-sized process plant display to define boundaries for graphics, generate graphics, or map graphics for transmission to and / or rendering on a mobile user interface device (e.g., UI device 112).

[0048] The server 150 may also include a communication unit 166 under the control of the operating system 154 of the server 150 to communicate with the controller 11 to control the online operation of the process plant. The server 150 may communicate via the communication unit 166, the UI device 112, and / or any other suitable computing device. For example, the UI device 112 may provide instructions to the server 150, which may in turn provide instructions to the controller 11 to, for example, adjust or modify process parameters of the process plant to control process plant entities within the process plant.

[0049] Regionalizer 2 is an embodiment of a full-size display screen 202 illustrating an example full-size process plant view 204 that graphically depicts at least a portion of the process plant 10 of FIG. 1A. In various embodiments, the full-size display screen 202 may be the display screen 84 of the UI device 112 of the process control network 100. In various embodiments, the process plant view 204 may be a GUI configured for operator or user manipulation. For example, an operator of the process control network 100 and / or the process plant 10 may interact with the full-size process plant view 204 via the full-size display screen 202. For example, in various embodiments, the full-size process plant view 204 is implemented as a GUI that an operator may manipulate via gestures (e.g., touch, pinch, swipe), via a cursor guided by a keyboard / mouse, and / or via other input devices configured to receive instructions (e.g., via I / O 91 circuitry) and provide commands to a CPU (e.g., CPU 88). In any of these embodiments, the instructions may cause the control unit 94 / mobile display navigation app 95 to receive, render, update, generate, or otherwise present a full-sized process plant view 204 on a full-sized display screen 202 as described herein. In some embodiments, the full-sized process plant view 204 includes: may be natively integrated into the process control network of the process plant;For example, a full-sized process plant representation 204 may be located within a process plant (e.g., process plant 10), and / or 、 Used to monitor or control a process plant and / or its process control network.

[0050] In various embodiments, the graphics and information of the process plant representation 204 are rendered in HyperText Markup Language (HTML) based graphics (e.g., HTML5 graphics). The HTML graphics may be provided from the server 150, for example, as described herein. For example, in various embodiments, the graphics and / or information of the full-sized process plant representation 204 may be rendered in, for example, HTML " <svg>" element, or may be rendered as vector-based graphics, for example, by HTML " <canvas>" element. In yet another embodiment, the graphics and / or information of the full-sized process plant representation 204 may be provided via rasterized or pre-generated graphics, such as via a file (e.g., JPEG, PNG, etc.) provided by the server 150.

[0051] As shown by the embodiment of FIG. 2, the full size process plant view 204 graphically represents numerous entities and related information of a process plant (e.g., process plant 10) and its process control network (e.g., process control network 100) including one or more processes within the process plant. These processes are generally maintained and controlled by control modules that generate and / or provide information about the processes. Such information may include process values, alarm information, and other diagnostic information. The graphics of the full size process plant view 204 are typically rendered on the full size process plant view 204 display and are in the form of discrete visualizations that represent one or more process plant entities or information or graphics associated with the process plant entities, process values, alarm information, diagnostic information, or other information as described herein.

[0052] For example, as shown in Figure 2, the full-sized process plant representation 204 graphically represents a number of process plant entities 212-218 of the process plant 10 of Figure IA. That is, the process plant entities 212-218 graphically represented in the full-sized process plant representation 204 correspond to real-world process plant entities of the process plant 10. For example, the process plant entities including heat exchanger 214, pump 216, and valve 218 of the full-sized process plant representation 204 of Figure 2 may be graphically represented by any of the field devices 15-22, as well as any of the field devices 15-22 and / or 40-46 of the process plant 10 of Figure IA. Similarly, the distillation column 212 of the full-sized process plant representation 204 of Figure 2 may graphically represent a distillation column (not shown) of the process plant 10 of Figure IA.

[0053] In general, a "display area," as used herein, is a view portion or sub-area of ​​a full-sized process plant display (e.g., full-sized process plant display 204) that is selected (either automatically, such as by a program or application, or manually, such as by a user) for transmission to and rendering on a mobile user interface device as described herein. In some embodiments, the full-sized process plant display may be a comprehensive representation of the process plant (e.g., process plant 10) that may include most or all process plant entities. However, in other embodiments, the full-sized process plant display may be a less comprehensive representation of the process plant that may include only a portion of the process plant and relevant portions of its process plant entities.

[0054] 2, exemplary display areas 221-224 are determined and / or generated for full-size process plant display 204. Each of display areas 221-224 defines a view portion of full-size process plant display 204. Additionally, each of display areas 221-224 includes at least one graphical representation of a process plant entity selected from a plurality of process plant entities graphically represented within full-size process plant display 204. For example, first display area 221 defines a first view portion of full-size process plant display 204. The first view portion of first display area 221 includes a graphical representation of a distillation tower, i.e., distillation tower 212. First display area also includes other graphical representations of process plant entities including each of heat exchanger 214, pump 216, and valve 218, each of which are directly or indirectly connected to distillation tower 212 as shown.

[0055] Similarly, as a second example, the second display area 222 defines a second view portion of the full-sized process plant representation 204. The second view portion of the second display area 222 includes graphical representations of gauges 232-236 of process plant entities depicted within the full-sized process plant representation 204. For example, in one embodiment, the gauges 232-236 may graphically represent each of the heat exchanger 214, the pump 216, and the valve 218, each of which is directly or indirectly connected to the distillation column 212, as shown. More generally, in various embodiments, the gauges 232-236 indicate key performance indicators (KPIs) of the various process plant entities (e.g., the process plant entities 212-218). The KPIs may include measurement parameters, such as temperature, level, pressure, etc., of the various process plant entities. A list of exemplary measurement parameters is shown, for example, in FIG. 6 as described herein.

[0056] As a third example, the third display area 223 defines a third view portion of the full-sized process plant display 204. The third view portion of the third display area 223 includes a graphical representation of a valve. In particular, the third display area 223 shows a video stream or image 217 of a valve of the process plant 10, the value of which is any of the field devices 15-22 and / or 40-46. In some embodiments, the video stream and / or image 217 may be a rotating video stream showing video of multiple devices (e.g., each of the field devices 15-22 and / or 40-46 at different times) and shows a graphical depiction (via the video) of a valve operating within the process plant 10. Thus, the display area may include a video stream or image of a process plant entity as one type of graphical representation on the full-sized process plant display 204.

[0057] As a fourth example, fourth display area 224 defines a fourth view portion of full-sized process plant representation 204. The fourth view portion of fourth display area 224 includes a graphical representation of tank 211. Tank 211 may be a tank for holding heavy chemicals or compounds, e.g., "heavies," such as hydrocarbons.

[0058] In some embodiments, the determination of the display areas is performed by a regionalizer application (app) that automatically detects or determines the location of one or more display areas (e.g., display areas 221-224) within a full-sized process plant display (e.g., full-sized process plant display 204). The location may be detected or determined, for example, by analyzing x and y pixel coordinates in the full-sized process plant display 204. In various embodiments, the regionalizer app includes a software application that includes computer instructions for determining a display area, such as display areas 221-224. In some embodiments, the regionalizer application 158 executes in memory 152 of the server 150 and facilitates the determination of the display areas 221-224 by receiving requests and providing responses through web applications 155 and / or web services 156 as described herein. In other embodiments, the regionalizer app may execute in memory 90 of the UI device 112.

[0059] In some embodiments, the regionalizer application may automatically determine the display areas (e.g., display areas 221-224) by detecting an access frequency corresponding to a view portion of each of one or more display areas (e.g., display areas 221-224) of the full-size process plant display (e.g., full-size process plant display 204). In certain embodiments, for example, the regionalizer app computer may determine a collection of interconnected graphical process plant entities comprising the full-size process plant display 204. For example, the first display area 221 may correspond to an area that defines a group of interconnected process plant entities (e.g., heat exchanger 214, pump 216, and valve 218) generally with respect to the distillation column 212. The regionalizer app computer detects that these process plant entities form a collection of interconnected graphical process plant entities and, therefore, determines the view portion that defines the first display area 221.

[0060] In another embodiment, the regionalizer app may automatically determine the display area (e.g., display areas 221-224) by analyzing portions of the full-sized process plant display 204 that have common zoomed-in areas. For example, the regionalizer app may track portions of the full-sized process plant display 204 that users frequently zoom in on by counting the number of times the user zooms in on a view portion, i.e., an area of ​​pixels of the full-sized process plant display 204 that the user typically zooms in on. Based on the frequency, the regionalizer app may determine a given area, e.g., a view portion of the second display area 222, that the user frequently zooms in to view the measured parameters of the gauges 232-236. In a related embodiment, the regionalizer app may suggest to the user (via a suggestion engine) that a particular view portion become a display area if they are commonly zoomed in on. For example, a user who is zoomed in on a view portion of display area 223 or 224 may receive a graphical popup with a suggestion to generate one or both of these view portions into the display area and generate and transmit to a mobile user interface device as described herein.

[0061] In some other embodiments, the determination of one or more of the display regions 221-224 is performed by a regionalizer application (app) that receives one or more user (e.g., an operator or configuration engineer) selections. In some embodiments, the regionalizer app includes a software application that includes computer instructions for identifying the display regions 221-224 and receiving user selections of locations. In some embodiments, the regionalizer application 158 may execute in the memory 152 of the server 150 to facilitate sectioning of the regions 221-224 by receiving requests and providing responses through the web application 155 and / or web services 156 as described herein. In other embodiments, the regionalizer app may execute in the memory 90 of the UI device 112.

[0062] A user selection may define one or more corresponding locations (e.g., x and y pixel-based coordinates) of one or more display areas 221-224 within the full-sized process plant display 204. In some embodiments, for example, the selection may be received at a processor (e.g., CPU 88) of the UI device 112 (e.g., a UI device having the full-sized display screen 202 of FIG. 2). For example, a user (e.g., an operator or configuration engineer) may place a display area anywhere on an existing process display (e.g., the full-sized process plant display 204). Thus, in such embodiments, display areas such as display areas 221-224 may be added by a configuration engineer during configuration time. In this manner, a user configures the display areas such that various view portions of the full-sized process plant display 204 may be rendered on a mobile user interface device as described herein, either in a single view or as a series of consecutive, user-swiped pages that the user can easily swipe through on the mobile device.

[0063] In some embodiments, a GUI profile may be predefined for a user. For example, the GUI profile may be determined based on one or more selections provided by a user. In some embodiments, a GUI profile may be created or accessed by selecting option 241, full size process plant view 204. The GUI profile may include GUI settings that define an amount of one or more display areas, i.e., the number of display areas to display for a given user. In further embodiments, the GUI settings may define one or more locations of the display areas (e.g., display areas 221-224) within the full size process plant view. In yet another embodiment, the GUI settings may define one or more zoom levels of the one or more display areas (e.g., display areas 221-224). In various embodiments, the GUI settings may be transmitted to a mobile user interface device. The mobile user interface device may then configure one or more display areas based on the GUI settings.

[0064] In some embodiments, the GUI profile or GUI settings may be determined based on the device type of the mobile user interface device. For example, mobile user interface devices typically have different sizes, shapes, etc., whereby display areas (display areas 221-224) that are compatible with those different sizes, shapes are stored as part of the GUI profile. In such embodiments, the display areas 221-224 may be selected by a user or automatically by a regionalizer app to be compatible with a given size or shape of the mobile user interface device.

[0065] Figure 3A is an embodiment of a mobile user interface device 112 rendering a first display region 221 of the example full-sized process plant view 204 of Figure 2 on a display screen 84. In various embodiments, the mobile user interface device 112 may be a UI device 112 used by an operator of the process plant 10, as described for Figure 1A. In the embodiment of Figure 3A, the mobile user interface device 112 is a mobile phone or smartphone device.

[0066] 3A , a first display area 221 of the full-sized process plant view 204 is rendered on the display screen 84. In various embodiments, a mobile display navigation app 95 renders the display screen 84 in the first display area 221. In some embodiments, the mobile display navigation app 95 may be a browser app (such as a Safari or Chrome application configured to run on a mobile user interface device). In other embodiments, the mobile display navigation app 95 may be a native browser app running on the processor 88 of the UI device 112. Bumo It can be a mobile app (such as Apple's iOS app or Google's Android app).

[0067] The mobile user interface device 112, e.g., via the mobile display navigation app 95, is configured to receive the first display region 221 from the server 150. For example, in a browser-based embodiment, the server 150 executes a web application 155. In such an embodiment, the mobile display navigation app 95 may receive all or a portion of the full-sized process plant display 204 from the server 150 as HTML-compatible graphics (e.g., HTML5-based graphics), which may include vector and / or rasterized graphics. In such an embodiment, the server 150 may further transmit HTML instructions, which may be part of or separate from the graphics of the full-sized process plant display 204, the HTML instructions being configured to cause the processor 88 to render the first display region 221 on the display screen 84 of the UI device 112.

[0068] As a further example, Nathi Bumo In a mobile app embodiment, the server 150 runs a web service 156. Bumo In a mobile app embodiment, the mobile view navigation app 95 is implemented as a native application (such as an iOS or Android mobile application) and receives all or a portion of the full-sized process plant view 204 as rasterized graphics from the vector and / or server 150 by requesting graphics from a web service 156. In such an embodiment, the mobile view navigation app 95 may include native instructions (e.g., iOS or Android based instructions, such as SWIFT®, Objective-C, or Java based instructions) configured to cause the processor 88 to render the first display region 221 on the display screen 84 of the UI device 112.

[0069] In the embodiment of Figure 3A, the mobile user interface device 112 is a mobile phone, such that the surface area of ​​the display screen 84 is less than (e.g., less than half) the surface area of ​​the full-sized display screen 202 of Figure 2. As a result, as shown in Figure 3A, the mobile display navigation app 95 renders the first display area 221 at a zoom level relative to the display screen 84. This results in a greater focus or zoom level of the first display area 221 that generally shows more detail, information, or measurements than the full-sized process plant view 204.

[0070] For example, as shown by FIG. 3A, the first display area 221 is rendered at a larger zoom level with the same information and graphics as the full-sized process plant view 204 of FIG. 2, as well as additional information. For example, the mobile display navigation app 95 renders the first display area 221 of FIG. 3A depicting the process plant entities 212-218 (i.e., distillation tower 212, heat exchanger 214, pump 216, valve 218, etc.) also shown by the full-sized process plant view 204 of FIG. 2. The mobile display navigation app 95 also renders the additional information at the more focused zoom level shown in FIG. 3A. For example, FIG. 3A also includes an alarm decorative graphic 239 indicating that an alarm has been activated for the distillation tower 212. In some embodiments, the mobile display navigation app 95 may render a view focused on when the alarm decorative graphic has been triggered for display (e.g., when the alarm decorative graphic 239 has been activated for the distillation tower 212). More generally, in various embodiments, a display area (e.g., first display area 221) may be rendered by the mobile display navigation app 95 to include an alarm decorative graphic (e.g., alarm decorative graphic 239) or a measurement parameter (e.g., the measurement parameter of FIG. 6 as described in the specification) of a process plant entity selected from a plurality of process plant entities (e.g., process plant entities of process plant 10).

[0071] In some embodiments, the mobile display navigation app 95 may be configured to render alarm decorative graphics and / or measurement parameters in real-time or near real-time. In such embodiments, a change in an alarm state or measurement parameter of an associated process plant entity causes a display area (e.g., first display area 221) to be updated on the mobile user interface device 112. For example, in the embodiment of FIG. 3A, a change in an alarm state of the distillation column 212 may cause the server 150 to forward the alarm state information to the mobile display navigation app 95. The mobile display navigation app 95 may then not render an alarm decorative graphic 239 on the display screen 84.

[0072] In further embodiments, the mobile display navigation app 95 may be configured to render a display area (e.g., the first display area 221) with an overview panel that indicates the location of the display area within the full-sized process plant display. For example, as shown in FIG. 3A, the mobile display navigation app 95 renders the first display area 221 to include an overview panel 304 that indicates the location (in view portions) of the first display area 221 within the full-sized process plant display 204. In some embodiments, the overview panel 304 and its associated view portions may be determined by a regionalizer app running on the server 150. In other embodiments, the mobile display navigation app 95 may determine and position the view portions when the first display area 221 is rendered on the display screen 84.

[0073] In various embodiments, the mobile UI device 112 may be confirmed to receive a selection corresponding to a process plant entity. The selection may initiate control of the process plant entity within the process plant (e.g., process plant 10). For example, as shown in FIG. 3A, the mobile display navigation app 95 may receive a selection on the display screen 84 corresponding to the location of the distillation tower 212. The selection may cause a control window (not shown) to be displayed on the display screen 84. The control window may include graphic controls and / or input boxes for receiving commands or inputs. For example, in the embodiment of FIG. 3A, the control window may receive a command to adjust or modify a parameter of the distillation tower 212 in response to an alarm decoration graphic 239 on the display screen 84. The command may be transmitted to the server 150, which may transmit the command to the distillation tower 212 via the process control network 100. In some embodiments, the commands may be transmitted via voice commands, where the mobile user interface device 112 receives audible instructions (voice) at a microphone (not shown) of the mobile UI device 112, and a processor (e.g., CPU 88) translates the audible instructions (e.g., via natural language processing) into commands that are transmitted to the server 150 to adjust or modify parameters of the distillation column 212 as described herein above. In this manner, monitoring and control of a process plant (e.g., process plant 10) can be performed on a small screen device such as the mobile user interface device 112 as described herein.

[0074] In various embodiments, the display regions may be configured to be rendered sequentially. For example, as shown in FIG. 3A, when the mobile display navigation app 95 receives the display regions 221-224, the first display region 221 is shown first. In some embodiments, the mobile display navigation app 95 may include a navigation panel for switching the rendering of the display regions, for example, sequentially. For example, as shown in FIG. 3A, the mobile display navigation app 95 renders navigation panels 302n1 and 302n2 on the display screen 84. Selection of the navigation panel 302n1 causes the mobile display navigation app 95 to render the next region (e.g., the second display region 222) on the display screen 84. Selection of the navigation panel 302n2 causes the mobile display navigation app 95 to render the previous region or the last region (e.g., the fourth display region 224) on the display screen 84. By using the navigation panels 302n1 and 302n2, an operator may easily move or navigate between the display areas 221-224 as determined for the full-sized process plant display 204.

[0075] In other embodiments, the user may move or navigate between display regions 221-224 by swiping left or right. In such embodiments, the mobile display navigation app 95 detects the user's swipe gesture as a command to switch between display regions 221-224.

[0076] 3B is the mobile user interface device 112 of FIG. 3A rendering a second display region (e.g., second display region 222) of the example full-sized process plant view 204 of FIG. 2 on the display screen 84. In various embodiments, the mobile display navigation app 95 can be configured to size the view portion of the view to be full screen on the display screen of the mobile user interface device. For example, in the embodiment of FIG. 3B, the mobile display navigation app 95 sizes the view portion of second display region 222 to be full screen on the display screen 84. Because the rendering is at a higher zoom level and / or higher resolution, the full-sized rendering allows a user of the mobile user interface device 112 to better view second display region 222 and its associated information, as provided by, for example, graphical gauges 232-236.

[0077] In some embodiments, the mobile display navigation app 95 may associate with each display area (e.g., display areas 221-114) of the full-sized process plant display with a variable zoom level value corresponding to a level of detail (e.g., a graphics level and / or a measurement parameter level) of the view portion. For example, in the embodiment of FIGS. 3A and 3B, the first display area 221 may be associated with a first variable zoom level value and the second display area 222 may be associated with a second variable zoom level value. The second variable zoom level value may be a zoom level value of “3” and the first variable zoom level value may be a zoom level of “2”. The different zoom level values ​​may be interpreted by the mobile display navigation app 95 as different zoom levels, which may also be different focus levels of the graphics of the full-sized process plant display 204, depending on when each of the first display area 221 and the second display area 222 is rendered. For example, as shown in FIG. 3B, the second display area 222 is shown with a higher focus and the graphic gauges 232-236 are rendered full screen on the display screen 84 corresponding to a larger zoom level value of 3. In contrast, as shown in FIG. 3A, the first display area 221 is shown with a lower focus and the process plant entities 212-218 are rendered on the display screen 84 with bounding graphics or graphical areas corresponding to a smaller zoom level value of 2. In some embodiments, an operator or configuration engineer may determine or adjust the zoom level values ​​of the various display areas to accommodate different types of mobile user interface device surfaces. In other embodiments, the regionalizer app 158 may automatically determine or adjust the zoom level values ​​of the various display areas to accommodate different types of mobile user interface device surfaces.Generally, by determining and / or adjusting the display areas, end users of the mobile display navigation app 95 may experience that the display areas are "custom built" for their respective mobile user interface devices, as described herein, without the need for computer programmers or designers to create and / or maintain additional process displays for each display area.

[0078] FIG. 3B illustrates an embodiment in which the display regions may be rendered in consecutive order relative to one another. For example, the first display region may be sequentially ordered relative to the second display region, and the mobile user interface device is adapted, via the mobile display navigation app 95, to render the first display region before the second display region. For example, in the embodiment of FIG. 3B, the first display region 221 may be sequentially ordered relative to the second display region 222. The mobile user interface device 112 may be adapted, via the mobile display navigation app 95, to render the first display region 221 before the second display region 222. As shown in FIG. 3B, the navigation panel 314 is rendered by the mobile display navigation app 95. The navigation panel 95 is configured to receive a selection (e.g., at 312n1 or 312n2) to switch between rendering the first display region 221 and the second display region 222 on the display screen 84 of the mobile user interface device 112. As described herein for selections from navigation panels 302n1 and 302n2 described in FIG. 3A, selections 312n1 and / or 312n2 cause the mobile display navigation app 95 to switch between rendering the first display area 221 and the second display area 222.

[0079] The navigation panel 314 also includes a zoom control 316. The zoom control 316 allows a user to adjust the zoom level and / or zoom level value of the second display region 222 such that the mobile display navigation app 95 renders a more focused or unfocused view portion of the full-size process display 204 on the display screen 84. For example, in the embodiment of FIG. 3B , a user may have accessed the zoom control 316 to adjust the zoom level rendering of the second region 222, in full screen, within the display screen 84 when the user moved from the first region 221 to the second region 222.

[0080] 4 is a flow diagram depicting an example GUI-based method 400 for regionalizing a full-sized process plant display (e.g., full-sized process plant display 204) for rendering on a mobile user interface device. For example, in at least one embodiment, FIG. 4 illustrates a method for regionalizing a first display area 221 and a second display area 222 of a full-sized process plant display 204 for rendering (e.g., by a mobile display navigation app 95) on a mobile user interface device 112, as described in FIGS. 3A and 3B herein. As used herein, the term "regionalize" generally refers to defining one or more view portions of a full-sized process plant display (e.g., full-sized process plant display 204) for generating or otherwise determining a display area (e.g., display areas 221-224). In various embodiments, the regionalizer application (e.g., regionalizer app 158) may determine or identify x and / or y coordinates (which may correspond to pixel values, for example) of a full-sized process plant representation (e.g., full-sized process plant representation 204) and generate, bound, map, or otherwise determine graphics for transmission to a mobile user interface device (e.g., UI device 112) as described herein. In some embodiments, the display area (e.g., display areas 221-224) may be determined by user selection. In other embodiments, the display area (e.g., display areas 221-224) is automatically determined by the regionalizer app 158.

[0081] At block 402 of FIG. 4, a regionalizer application (e.g., the regionalizer app 158 executing on the server 150) receives a full-sized process plant view (e.g., the full-sized process plant view 204) that graphically represents at least a portion of a process plant (e.g., the process plant 10). The full-sized process plant view may include a graphical representation (e.g., the graphical process plant entities 212-218) of a plurality of process plant entities (e.g., the process plant entities 15-22 and 40-46) within the process plant (e.g., the process plant 10). The full-sized process plant view (e.g., the full-sized process plant view 204) may be a GUI adapted to render on a full-sized display screen (the full-sized display screen 202) of the process plant. For example, the full-sized display screen may be a UI device 112 communicatively coupled to the process control network 100 and / or the network backbone 105 as described herein with respect to FIG. 1A. The full-size process plant representation (eg, full-size process plant representation 204) may be an existing full-size process plant representation that was previously created or designed for the process plant.

[0082] At block 404, the regionalizer app 158 determines one or more display regions of the full-sized process plant display. For example, the display regions may include any one or more of the display regions 221-224 of FIG. 2. Each of the one or more display regions (e.g., 221-224) defines a view portion of the full-sized process plant display (e.g., full-sized process plant display 204). For example, as shown in FIG. 2, each display region 221-224 defines a rectilinear view portion that defines dimensions (e.g., x and y coordinates, such as x and y pixel coordinates) corresponding to a sub-area of ​​the full-sized process plant display (e.g., full-sized process plant display 204). In other words, the view portion maps or defines a region or area of ​​the full-sized process plant display to a particular display region. Each of the one or more display regions (e.g., display regions 221-224) includes at least one graphical representation of a process plant entity selected from the plurality of process plant entities. For example, each display area 221-224 includes a process plant entity such as those described herein with respect to FIG.

[0083] At block 406, one or more processors, such as CPU 160, of server 150 may transmit one or more display areas (e.g., display areas 221-224) to a mobile user interface device (e.g., mobile user interface device 112), as shown in the examples of Figures 3A and 3B.

[0084] In various embodiments disclosed herein, the mobile user interface 112 may execute a mobile display navigation app (e.g., the mobile display navigation app 95). In some embodiments, the mobile display navigation app 95 may be a browser app (such as a Safari or Chrome application configured to run on a mobile user interface device). In other embodiments, the mobile display navigation app 95 may be a native browser app that runs on the processor 88 of the UI device 112. Bumo It can be a mobile app (such as Apple's iOS app or Google's Android app).

[0085] The mobile user interface device 112, for example via the mobile display navigation app 95, is configured to receive the display regions (e.g., display regions 221-224) from the server 150. For example, in a browser-based embodiment, the server 150 executes a web application 155. In such an embodiment, the mobile display navigation app 95 may receive all or a portion of the full-sized process plant display 204 from the server 150 as HTML-compatible graphics (e.g., HTML5-based graphics), which may include vector and / or rasterized graphics. In such an embodiment, the server 150 may further transmit HTML instructions, which may be part of or separate from the graphics of the full-sized process plant display 204, the HTML instructions being configured to cause the processor 88 to render the display regions (e.g., display regions 221-224) on the display screen 84 of the UI device 112.

[0086] As a further example, Nathi Bumo In a mobile app embodiment, the server 150 runs a web service 156. Bumo In a mobile app embodiment, the mobile view navigation app 95 is implemented as a native application (e.g., an iOS or Android mobile application) and receives all or a portion of the full-sized process plant view 204 as rasterized graphics from the vector and / or server 150 by requesting graphics from a web service 156. In such an embodiment, the mobile view navigation app 95 may include native instructions (e.g., iOS or Android based instructions, such as SWIFT, Objective-C, or Java based instructions) configured to cause the processor 88 to render a display area (e.g., display areas 221-224) on the display screen 84 of the UI device 112.

[0087] At block 408, the mobile display navigation app 95 renders each of the one or more display areas (e.g., display areas 221-224) on a display screen (e.g., display screen 84) of the mobile user interface device 112. In various embodiments, the display screen 84 of the mobile user interface device 112 includes a surface area that is less than the full-sized surface area of ​​a full-sized display screen (e.g., full-sized display screen 202). For example, this is illustrated by FIGS. 2, 3A, and 3B, where the display screen 84 of the mobile user interface device 112 of FIGS. 3A and 3B includes a surface area that is less than the full-sized surface area of ​​the full-sized display screen 202 of FIG.

[0088] The mobile view navigation app 95 may render a display area (e.g., display areas 221-224) on the display screen 84 of the mobile user interface device using different techniques as disclosed herein for different embodiments. In a first rendering embodiment, one or more processors (e.g., CPU 160) of the server 150 may transmit a full-sized process plant display (e.g., full-sized process plant display 204) to the mobile user interface device. In some embodiments, the mobile user interface device 112 may store a copy of the full-sized process plant display (e.g., full-sized process plant display 204) in memory 90. The mobile view navigation app 95 may access the full-sized process plant display (e.g., full-sized process plant display 204) from memory 90 when rendering or otherwise manipulating the full-sized process plant display 204 (e.g., graphics, display areas, view portions, etc. associated with the full-sized process plant) as described herein.

[0089] In some embodiments, the mobile display navigation app 95 may render one or more display areas (e.g., display areas 221-224) on the display screen 84 of the mobile user interface device 112 by bounding a corresponding view portion of each of the one or more display areas (e.g., display areas 221-224) to the full-sized process plant view (e.g., full-sized process plant view 204). For example, the mobile display navigation app 95 may access the full-sized process plant view (e.g., full-sized process plant view 204) from the memory 90 and map the view portion including zooming, panning, and / or positioning the view portion to the full-sized process plant view (e.g., full-sized process plant view 204). Thus, in such an embodiment, the mobile display navigation app 95 would have accessed the full-sized process plant view 204 from the memory 90, but only the view portion of the display area shown in FIG. 3A (e.g., the first view portion of the first display area 221 as shown in FIG. 3A or the second view portion of the display area 222 as shown in FIG. 3B) is shown on the display screen 84. This reduces the processing resources required by the mobile UI device 112.

[0090] In some embodiments, the mobile display navigation app 95 may be configured to automatically detect a mobile screen size and automatically render a determined or generated display area (e.g., first display area 221) on the display screen 84 of the mobile user interface device 112 based on the screen size and / or resolution of the display screen 84. The determination or generation of the display area (e.g., display areas 221-224) may occur before or during transmission of the display area (e.g., display areas 221-224) to the mobile display navigation app 95. For example, the determination or generation of the display area 221-224 may occur when the mobile user interface device 112 requests the display area from the server 150.

[0091] In a second rendering embodiment, the newly generated display region may be created from a full-sized process plant representation (e.g., full-sized process plant representation 204). In such an embodiment, each new display may be generated by server 150 and may be separate from the full-sized process plant representation, such that each new display is independent of the full-sized process plant representation (e.g., full-sized process plant representation 204). Such an embodiment reduces computer network payload and traffic because the full-sized process representation does not need to be transferred (e.g., across network backbone 105).

[0092] In new view embodiments, one or more processors (e.g., CPU 160 of server 150) generate one or more new views based on a determination of one or more display areas (e.g., display areas 221-224) of a full-sized process plant view (e.g., full-sized process plant view 204). In such embodiments, each new view may be generated by server 150 to correspond to a view portion of the corresponding display area. For example, the server may determine a view portion of each of display areas 221-224 and generate a new view for each area. In new view embodiments, server 150 may transmit the one or more display areas by transmitting the one or more new views to mobile user interface device 112. Mobile view navigation app 95 may render the one or more new views on a display screen of the mobile user interface device. For example, each of first display area 221 of FIG. 3A and / or second display area 222 of FIG. 3B may represent a new view generated by server 150 and transmitted to mobile user interface device 112. The generation of a new view corresponding to a display area (e.g., display areas 221-224) may occur before or during transmission of the display area (e.g., display areas 221-224) to the mobile display navigation app 95. For example, the determination or generation of a new view for display areas 221-224 may occur when the mobile user interface device 112 requests the display area from the server 150.

[0093] Automatic introspection display In various embodiments, GUI-based systems and methods are disclosed for automatically locating display portions of graphical process control loops within a full-sized process plant display for rendering on a mobile user interface device. In such embodiments, graphical information within a display (e.g., full-sized process plant display 204) is automatically introspected (without user intervention) by a processor (e.g., CPU 88 of mobile UI device 112 or CPU 160 of server 150) and provided to a mobile display navigation app for rendering process plant related visualizations, views, and / or graphics configured for a small screen device such as mobile user interface device 112.

[0094] In various embodiments, the display auto introspection routine may analyze a full-sized process plant display (e.g., full-sized process plant display 204) to determine visualizations of process modules as part of a graphical process control loop display. In some embodiments, the process modules may be rendered in a scrollable list format, for example, by the mobile display navigation app 95. In further embodiments, visualizations related to alarm information may be rendered in a scrollable list format. In this manner, the display auto introspection helps the operator maintain or even improve the operational feel on a small surface.

[0095] FIG. 5A is an embodiment of a mobile user interface device 112 rendering on a display screen 84 an example graphical process control loop display portion (e.g., graphical process control loop display portion 204) of the full-sized process plant display (e.g., graphical process control loop display portion 240) illustrated in FIG.

[0096] As shown in Figure 5A, the graphical process control loop display portion 240 includes selected process plant entities from the full-sized process plant display 204. These include, for example, the process plant entities 212-218 described herein with respect to Figure 2. The mobile display navigation app 95 may also render an overview panel 304 with the graphical process control loop display portion 240 that operates in the same manner as described herein with respect to Figures 3A and 3B.

[0097] 5A further illustrates an example selectable display list (e.g., selectable display list 502) that includes measurement parameters (e.g., measurement parameters 510-514) of one or more process plant entities that are displayed within the example graphical process control loop display portion. As shown, the selectable display list 502 is displayed in a first area of ​​the display screen 84 and the graphical process control loop display portion 240 is displayed in a second area of ​​the display screen 84.

[0098] As shown in the embodiment of FIG. 5A, the mobile display navigation app 95 may render measured parameters 510-514 of one or more process plant entities on the display screen 84 of the mobile user interface device 112. In FIG. 5A, the graphical process control loop display portion 240 focuses on the process control loop of the distillation column 212. For example, as shown in FIG. 2, the distillation column 212 takes in an input stream and distills it into two fractions, a first fraction exiting the top of the distillation column (not shown) and a second fraction exiting the bottom 213 of the distillation. The graphical process control loop display portion 240 shows details of the bottom 213 of the process, specifically the bottom reboiler loop of the distillation column 212. The measured parameters 510-514 may correspond to the process plant entity of the bottom reboiler loop / bottom 213 of the distillation column 212. In particular, as shown in FIG. 5A, measured parameter 510 corresponds to a bottoms flow rate of process plant entity (FC701_03) having a value of 1.44 MBPD. Similarly, measured parameter 512 corresponds to a bottoms composition parameter of process plant entity (AC701_01) having a value of 50.2%. Additionally, measured parameter 514 corresponds to a minimum level parameter of process plant entity (AC701_01) having a value of 10.9%. As shown for measured parameter 514, an alarm indicator may be shown in selectable display list 502 for measured parameters that are above or below an acceptable alarm condition or threshold. In the embodiment of FIG. 5A, the value of 10.9% of the minimum level of distillation column 212 is below the acceptable threshold, and therefore, mobile display navigation app 95 renders an alarm indicator for measured parameter 514. In some embodiments, an alarm associated with the measured parameter 514 may correspond to a decorative graphic 239 shown in the graphical process control loop display portion 240 of the bottom reboiler loop / bottom 213 of the distillation column 212 .

[0099] Selecting the measured parameter 514 causes the mobile view navigation app 95 to zoom or focus on the bottom 213, allowing the user to better see additional details, values, or graphics of the bottom reboiler loop / bottom 213 of the distillation column 212. For example, additional information such as any or all of the measured parameters of FIG.

[0100] Thus, the display auto-introspection routine exposes valuable information (e.g., measured parameters) to a process plant operator by analyzing a full-sized process plant display (e.g., full-sized process plant display 204) to determine visualizations of process modules as part of a graphical process control loop display. Additionally, it also allows the operator to quickly and efficiently navigate to value information on the display by tapping an item in a selectable display list (e.g., selectable display list 502) and automatically zooming the display to visualize the display.

[0101] In additional embodiments, an operator may control a process plant entity in the graphical process control loop display portion 240 by selecting a graphical representation of the process plant entity on the display screen 84 or by selecting a measurement parameter (e.g., measurement parameters 510-514) from the selectable display list 502. In such embodiments, the mobile user interface device 112 may receive a selection corresponding to a process plant entity of the multiple process plant entities, which selection may initiate control of the process plant entity within the process plant (e.g., process plant 10).

[0102] 5B is the mobile user interface device 112 of FIG. 5A rendering the example graphical process control loop display portion 240 of FIG. 5A. FIG. 5B also depicts the mobile user interface device 112 rendering an example selectable display list 503. The selectable display list 503 includes a list of alarms currently active in the graphical process control loop display portion 240. In the embodiment of FIG. 5B, the mobile display navigation app 95 has rendered a representation of an alarm indicator 521 for a particular process plant entity on the display screen 84 of the mobile user interface device 112. In some embodiments, the alarm indicator 521 may correspond to the measurement parameter 514 of FIG. 5A and the graphic 239 of FIG. 3A. As shown in FIG. 5B, the alarm indicator 521 indicates and displays the reason for the alarm, i.e., the minimum level is low and the alarm was triggered (e.g., by falling below a threshold) in the past 18 minutes. Alarm information may be displayed or triggered with respect to other or additional measurement parameters, values, etc., including, for example, the measurement parameters of FIG. 6 as described herein.

[0103] 5B, the graphical process control loop display portion 240 includes selected process plant entities from the full-sized process plant display 204. These include, for example, the process plant entities 212-218 described herein with respect to FIGURE 2. The mobile display navigation app 95 may also render an overview panel 304 with the graphical process control loop display portion 240 that operates in the same manner as described herein with respect to FIGURES 3A and 3B.

[0104] In some embodiments, the mobile display navigation app 95 may be configured to switch between multiple graphical process control loop display portions. For example, the second graphical process control loop display portion (not shown) may include a different graphical process control loop display portion of the full-sized process plant display 204 than that shown by the graphical process control loop display portion 240. For example, the second graphical process control loop display portion may include the top of the distillation tower 212, as shown in FIG. 2. In such an embodiment, the display automatic introspection routine may automatically detect the second graphical process control loop display portion depicted within the full-sized process plant display 204. The second graphical process control loop display portion may include a graphical representation of a second one or more process plant entities selected from the multiple process plant entities of the full-sized process plant display 204. One or more processors (e.g., the CPU 160 of the server 150 or the CPU 88 of the mobile UI device 112) may generate a second selectable display list representing the second one or more process plant entities shown within the second graphical process control loop display portion. The one or more processors may then transmit the second graphical process control loop display portion and the second selectable display list to the mobile user interface device 112. Upon receiving a user selection from the display screen, the mobile display navigation app may be configured to switch between rendering the graphical process control loop display portion (e.g., the graphical process control loop display portion 240) in a second area of ​​the display screen of the mobile user interface device and rendering a second graphical process control loop display portion (not shown) in a second area of ​​the display screen of the mobile interface device. The selection may be a swipe or other gesture, or may be from a navigation panel (not shown) as described herein with respect to FIGS. 3A and 3B.In such an embodiment, rendering of the graphical process control loop display portion causes the mobile display navigation app 95 to render a selectable display list in a first area of ​​the display screen 84. Similarly, rendering of a second graphical process control loop display portion causes the mobile display navigation app 95 to render a second selectable display list in the first area of ​​the display screen 84.

[0105] 6 is a list of example measured parameters 602 of one or more process plant entities of FIGS. 5A and 5B. Additionally, the measured parameters may represent values ​​or device diagnostic information that may be generated, controlled, measured, and / or displayed with respect to any of the embodiments of FIGS. 2, 3A, 3B, 5A, 5B, 8A, and / or 8B as described herein. For example, the measured parameters 602 represent key performance indicators (KPIs) associated with the process plant entities (e.g., process plant entities 15-22 and 40-46) of the process plant 10. The measured parameters (including the measured parameters 602) may be read, displayed, or visualized on any display herein, including in real time or near real time.

[0106] In the embodiment of FIG. 6, the measured parameters 602 may correspond to the bottom reboiler loop / bottom 213 of the distillation column 212, as described herein with respect to FIGS. 5A and 5B. For example, as shown in FIG. 6, the measured parameters 602 include a minimum flow rate 604 for process plant entity FC701_03 having a value of 1.44 MBDP that may flow to multiple destinations in the process plant 10, including T-721, T-722, and T-723. Additionally, the measured parameters 602 include a minimum level value 605 for process plant entity LC701_01 having a value of 0.5. Additionally, the measured parameters 602 include a lower control temperature 606 for process plant entity TC701_01 having a value of 668 degrees Fahrenheit. Additionally, the measured parameters 602 include a heater control for a reboiler 607 for process plant entity FC701_01 having a value of 1000 cubic feet per second. Additionally, the measured parameters 602 include a minimum composition 608 for the process plant entity AC701_01 that has a value of 0.5.

[0107] Any or all of the measurement parameters 602 may be displayed on the display screen 84 of the mobile user interface device 112. In various embodiments, more or fewer measurement parameters 602 may be displayed on the display screen 84 as the zoom level is changed, for example, by gesture commands that update the zoom level value to zoom the display in and out.

[0108] Figure 7 is a flow diagram depicting an example GUI-based method 700 for automatically detecting, via a display auto-introspection routine, a graphical process control loop display portion 240 depicted within a full-sized process plant display, such as the example full-sized process plant display of Figure 2 (e.g., full-sized process plant display 204). Method 700 may be used to generate the displays and embodiments of Figures 5A and 5B, as described herein.

[0109] At block 702, a display auto-browsing routine executing on one or more processors (e.g., CPU 88 of mobile user interface device 112 or CPU 160 of server 150) to receive a full-sized process plant view (e.g., full-sized process plant view 204) that graphically represents at least a portion of a process plant (e.g., process plant 10). The full-sized process plant view (e.g., full-sized process plant view 204) may include graphical representations (e.g., graphical process plant entities 212-218) of a plurality of process plant entities (e.g., process plant entities 15-22 and 40-46) within the process plant (e.g., process plant 10). Additionally, the full-sized process plant view (e.g., full-sized process plant view 204) may include a GUI adapted to render on a full-sized display screen (e.g., full-sized display screen 202) of the process plant (e.g., process plant 10).

[0110] In various embodiments, the display auto-introspection routine may be computer instructions and / or software stored in the memory 90 of the mobile user interface device 112 or the memory 152 of the server 150. In some embodiments, the graphical process control loop display portion may correspond to a process control module of a process plant (e.g., process plant 10). In such embodiments, the display auto-introspection routine may analyze the process control module and detect or determine the graphical process control loop display portion from the variables, functions, attributes, or other information of the process control module that corresponds to the graphics or process visualization of the full-sized process plant display 204. The display auto-introspection routine may then determine a view portion of the full-sized process plant display 204 that may be mapped to the graphical process control loop display portion and transmitted to the mobile display navigation app 95 for rendering on the mobile user interface device 112, as described herein.

[0111] At block 704, the display auto-introspection routine automatically detects a graphical process control loop display portion (e.g., graphical process control loop display portion 240) depicted within a full-sized process plant display (e.g., full-sized process plant display 204). The graphical process control loop display portion (e.g., graphical process control loop display portion 240) may include a graphical representation of one or more process plant entities (e.g., graphical process plant entities 212-218) selected from a plurality of process plant entities.

[0112] At block 706, one or more processors (e.g., of the mobile UI device 112 and / or the server 150) generate a selectable display list (e.g., the selectable display list 502 of FIG. 5A ) representing one or more process plant entities depicted within the graphical process control loop display portion (e.g., the graphical process control loop display portion 240).

[0113] At block 708, one or more processors (e.g., of the mobile UI device 112 and / or server 150) transmit the graphical process control loop display portion (e.g., graphical process control loop display portion 240) and the selectable display list (e.g., selectable list 502 of FIG. 5A ) to the mobile user interface device 112. In various embodiments, the mobile user interface device may execute a mobile display navigation app (e.g., mobile display navigation app 95).

[0114] At block 710, the mobile display navigation app 95 may render a selectable display list (eg, the selectable display list 502 of FIG. 5A) in a first area of ​​the display screen 84 of the mobile user interface device 112.

[0115] At block 712 , the mobile display navigation app 95 may render the graphical process control loop display portion (eg, the graphical process control loop display portion 240 ) within a second area of ​​the display screen 84 of the mobile user interface device 112 .

[0116] In various embodiments, upon receiving a selection from a selectable display list (e.g., selectable display list 502 of FIG. 5A ) corresponding to a particular process plant entity (e.g., distillation tower 212), the mobile display navigation app 95 may be adapted to adjust a zoom level to focus on the particular process plant entity (e.g., distillation tower 212) within a graphical process control loop display portion (e.g., graphical process control loop display portion 240) as displayed in a second area of ​​the display screen 84 of the mobile user interface device 112, for example, as described herein with respect to FIG. 5A .

[0117] Refactoring the full-size process plant view The present disclosure further provides GUI-based systems and methods for refactoring full-sized process plant views at various zoom and detail levels for visualization on a mobile user interface device. In particular, such GUI-based systems and methods may enable a mobile user interface device 112 and its user to refactor an existing full-sized process plant view (e.g., full-sized process plant view 204) in real-time or near real-time on a mobile user interface device 112 to visualize process data, measurement parameters, alarm information, or other information at different zoom and detail levels, as described herein. Such systems and methods for refactoring full-sized process plant views may be deployed and / or implemented in existing mobile applications and / or process plant-based applications and products offered by Emerson Process Management, such as DeltaV™ Mobile and / or DeltaV™ Live.

[0118] 8A and 8B depict an example embodiment of a full-sized process plant view refactoring. Figures 8A and 8B show the user interface device 112 as a tablet device displaying a refactored visualization of the full-sized process plant view 204 of Figure 2. In the embodiment of Figures 8A and 8B, the surface area of ​​the display screen 84 of the mobile user interface device 112 is less than half the surface area of ​​the full-sized display screen 202 of Figure 2.

[0119] Figure 8A is an embodiment of a mobile user interface device 112 rendering a first view portion 802 of the example full-sized process plant display 204 of Figure 2 on a display screen 84. The first view portion 802 defines a first zoom level and a first level of detail of a process plant entity (e.g., distillation column 212). In the Figure 8A embodiment, the first view portion 802 is displayed on the display screen 84 in a "zoomed out," lower resolution view as compared to a second view portion 852 of Figure 8B, described further herein.

[0120] 8A and 8B, each of the first view portion 802 and the second view portion 852 are sized to be rendered full screen on the display screen 84 of the mobile user interface device 112 such that the entire or nearly the entire surface area of ​​the display screen of FIG. 84 is occupied by each of the first view portion 802 and the second view portion 852, respectively. This allows for a greater zoom and level of detail in each of the first view portion 802 and the second view portion 852 compared to a fully zoomed out view of the full-sized process plant view 204 that shows all of the process plant entities of the process plant view 204. That is, when the first view portion 802 and the second view portion 852 are displayed in a full screen view, the mobile user interface device 112 does not display, and the mobile display navigation app 95 does not render, all of the visualizations or graphics of the full-sized process plant view 204. Thus, the GUI-based system and method for refactoring full-size process plant displays at various zoom and detail levels improves the performance of the mobile user interface device 112 by enabling the user interface device 112 and the mobile display navigation app 95 to perform less visualization and / or rendering of graphics, thereby improving the performance of the user interface device 112 by reducing the processing power required (e.g., of the CPU 88) and the amount of memory (memory 90) usage required by the user interface device 112.

[0121] 8A and 8B include embodiments relating to automated refactoring of graphics of the full-sized process plant view 204, which, at least in some embodiments, may be natively integrated with a process control network (e.g., process control network 100) of various mobile device screen sizes and resolutions. In the embodiment of FIG. 8A and 8B, a mobile device command gesture on the display screen 84 of the mobile user interface device 112 requests graphics and / or data (e.g., real-time or near real-time graphics or data) from the server 150. The mobile display navigation app 95 may then render the rendered graphics and data on the display screen 84 of the mobile user interface device 112. In this manner, the view portions (e.g., first view portion 802 and / or second view portion 802) may represent a “live snapshot” of actual data and / or status of various process plant entities of the process plant 10.

[0122] Additionally, a particular (e.g., programmatically defined or user defined) view portion of the graphics and / or data may be rendered based on the size of the display screen 84 of the 112 accessing the graphics and / or data from the server 150.

[0123] In some embodiments, the full-sized process plant representation 204 as displayed in FIG. 8A may be a comprehensive representation of a process plant (e.g., process plant 10) that may include most or all process plant entities. However, in other embodiments, the full-sized process plant representation 204 (e.g., as displayed in FIG. 8A) may be a less comprehensive representation of a process plant that may include only a portion of the process plant and its associated process plant entities. In some embodiments, the full-sized process plant representation 204 (e.g., as shown in FIG. 8A) may be natively integrated with a process plant's process control network, for example, with which the full-sized process plant representation 204 is co-located within the process plant (e.g., process plant 10) and / or used to monitor or control the process plant and / or its process control network.

[0124] In a further embodiment, the mobile UI device 112 may be acknowledged to receive a selection corresponding to a process plant entity (e.g., distillation tower 212). This selection may initiate control of the process plant entity within the process plant (e.g., process plant 10). For example, as shown in FIGS. 8A and 8B, the mobile display navigation app 95 may receive a selection on the display screen 84 corresponding to the location of the distillation tower 212. This selection may cause a control window (not shown) to be displayed on the display screen 84. The control window may include graphic controls and / or input boxes for receiving commands or inputs. For example, in the embodiment of FIG. 3A, the control window may receive a command to adjust a parameter of the distillation tower 212 in response to an alarm decoration graphic 239 on the display screen 84. The command may be transmitted to the server 150, which may transmit the command to the distillation tower 212 via the process control network 100. In some embodiments, the commands may be transmitted via voice commands, where the mobile user interface device 112 receives audible instructions (voice) at a microphone (not shown) of the mobile UI device 112, and a processor (e.g., CPU 88) translates the audible instructions (e.g., via natural language processing) into commands that are transmitted to the server 150 to adjust parameters of the distillation column 212 as described herein above. In this manner, monitoring and control of a process plant (e.g., process plant 10) can be performed on a small screen device such as the mobile user interface device 112 as described herein.

[0125] 8B is the mobile user interface device 12 of FIG. 8A rendering a second view portion 852 of the example full-sized process plant display (e.g., full-sized process plant display 204) of FIG. 2 that defines a second zoom level and a second level of detail of a process plant entity (e.g., distillation column 212). The second view portion 852 represents a "zoomed in" and / or more focused zoom level having a greater level of detail compared to the first view portion 802 of FIG. 8A. In various embodiments herein, including those of FIGS. 8A and 8B, mobile touch gestures such as pinch, swipe, and / or zoom may cause a change in the screen (e.g., display screen 84) content, such as lower / higher resolution and / or graphics and / or data detail, as the user zooms in and out of the various view portions (e.g., first view portion 802 and second view portion 802).

[0126] 8B, the mobile display navigation app 95 renders the second view portion 852 with a focused view (e.g., a more detailed view and / or a higher resolution view) of the process plant entity (e.g., distillation tower 212) at a second zoom level of the second view portion 802 compared to the first zoom level of the second view portion 852. The focused view of the second view portion 852 includes more detailed / higher resolution graphics and measurement parameters of the process plant 10 compared to the first view portion 802. For example, upon zooming into the second view portion 852, the mobile display navigation app 95 renders more information including the bottom 213 of the distillation tower 212, decorative graphics 239, and additional measurement parameters 860 (which may be any of the measurement parameters 602, for example).

[0127] As shown in FIGS. 8A and 8B, the first view portion 802 includes a first graphic resolution and the second view portion 852 includes a second graphic resolution. In some embodiments, the first graphic resolution of the first view portion 802 may be different from the second graphic resolution of the second view portion 852. In other embodiments, the first graphic resolution and the second graphic resolution are the same but are rendered at different zoom levels by the mobile zoom navigation app 95. In yet another embodiment, the mobile display navigation app 95 may determine each of the first graphic resolution and the second graphic resolution based on the size of the display screen 84 of the mobile user interface device 112. In such an embodiment, a mobile user interface device 112 having a larger screen size may be configured with a larger or higher resolution view portion than a mobile user interface device 112 having a smaller screen size.

[0128] Additionally, the mobile display navigation app 95 renders detailed information of the process plant entity (e.g., distillation column 212) at a second level of detail on the display screen 84 of the mobile user interface device 112. In various embodiments, the detailed information may include at least one of an alarm decorative graphic (e.g., Adler graphic 239) or a measurement parameter (e.g., measurement parameter 602) of the process plant entity. In some embodiments, the mobile display navigation app 95 renders the detailed information in real time or near real time on the display screen 84 of the mobile user interface device 112. For example, the detailed information may be retrieved from the server 150 upon request from the mobile user interface device 112, as described herein.

[0129] More generally, as shown in FIGS. 8A and 8B, graphics and data may be rendered and displayed on the display screen 84 at various levels of detail and / or resolution depending on the screen resolution. In such an embodiment, the level of detail may be automatically adjusted depending on the screen size or resolution of the mobile device and the mobile pinch / zoom touch gestures received from the user on the display screen 84. For example, on a small screen size with low resolution (e.g., the tablet device of FIG. 8A), only a few parameters are shown. To see more details, the user may use touch gestures to zoom in or out, causing the data and graphics to be refactored (e.g., refetched from the server 150 or re-rendered if the full-sized process plant view 204 is in memory 90) to display different and / or higher resolution content on the mobile user interface device 112). In such an embodiment, the mobile display navigation app 95 may initially render a lower resolution view for smaller mobile screen sizes and render a more detailed view with higher resolution content once the user zooms in. In this manner, the user may adjust either the graphical detail or the measurement parameter detail on the screen where the current zoom level corresponds to the current level of detail of the information being displayed on the display screen 84. Thus, a user of the mobile user interface device 112 may view process or alarm information on the display screen 84 that is native within the process control system (e.g., the process control network 100) in an efficient manner on a mobile user interface device 112 having a small screen.

[0130] In some embodiments, each of the zoom levels is defined by a different graphical view layer. In such embodiments, a full-sized process plant display (e.g., full-sized process plant display 204) may include multiple graphical view layers. For example, in FIGS. 8A and 8B, a first view portion 802 may be associated with a first graphical layer having a first zoom range, and a second view portion 852 may be associated with a second graphical layer having a second zoom range. Upon receiving a gesture command from the mobile user interface device 112, the mobile display navigation app 95 detects a transition from the first zoom range to the second zoom range. The detected transition may correspond to the length or extent of a swipe, pinch, or other such gesture command. A transition command based on the length or extent may cause the mobile display navigation app 95 to render the second view portion 852 in a second graphical layer on the display screen 84.

[0131] In certain embodiments, a graphical view layer or layout may be generated from the full-sized process plant display 204 based on the type of device. For example, a "cell phone view," such as a mobile phone graphical view layer or layout, may be configured by a user or may be automatically determined (e.g., by the regionizer 158). In such embodiments, view portions corresponding to the shape or area of ​​a given mobile user interface device 112 may be determined and generated as graphical view layers, layouts, and / or regions. As an additional example, a "tablet view" graphical view layer or layout may be generated based on the full-sized process plant display 204 showing greater detail of the full-sized process plant display 204 where the tablet screen size is larger than the mobile phone screen size for the "cell phone view." When a user opens from a mobile user interface device 112 to access the full-sized process plant display 204, the view displayed may be based on automatic detection of the type of mobile device. In such embodiments, if the user is using a tablet, the "tablet view" is automatically displayed. If the user is using a mobile phone, the "cell phone view" is automatically displayed.

[0132] In a further embodiment, the server 150 and / or the mobile user interface device 112 may provide the server 150 and / or the mobile user interface device 112 with: (a) a view section; Minute( For example, first view portion 802 and / or second view portion 852 Predefine the graphics resolution of , (b) modifying the detailed information of the view portion (e.g., the first view portion 802 and / or the second view portion 852 About ), and / or (c) define a set of view layers associated with a first zoom level and a second zoom level of the view portion (e.g., first view portion 802 and / or second view portion 852 About ) 、 Execute the command to Receive configuration commands Thus, for example, such configuration options, via configuration commands, may allow a user or program application to select regions of the operator graphics that are automatically displayed as scrollable pages on the mobile device. These regions may be selected in sizes that reflect the size and resolution of the mobile phone or tablet screen, and may be displayed in a browser or native browser. Bumo When you launch a mobile app, the app may automatically detect the screen size of your mobile device and render graphics at a resolution and / or size that matches your mobile device.

[0133] FIG. 9 is a flow diagram illustrating an example GUI-based method 900 for refactoring a full-size process plant display (e.g., full-size process plant display 204) at various zoom and detail levels for visualization on a mobile user interface device 112 as depicted and described herein with respect to FIGS. 8A and 8B.

[0134] At block 902, the method 900 includes transmitting, by one or more processors (e.g., CPU 160 of server 150), a full-sized process plant representation (e.g., full-sized process plant representation 204) to the mobile user interface device 112. The full-sized process plant representation (e.g., full-sized process plant representation 204) may graphically represent at least a portion of a process plant (e.g., process plant 10). Further, the full-sized process plant representation (e.g., full-sized process plant representation 204) may include a graphical representation of a number of process plant entities (e.g., process plant entities 15-22 and 40-46) within the process plant (e.g., process plant 10). In various embodiments, the full-sized process plant representation 202 is a GUI adapted to render on a full-sized display screen (e.g., full-sized display screen 202) of the process plant (e.g., process plant 10).

[0135] At block 904, the method 900 may include rendering, by a mobile display navigation app (e.g., mobile display navigation app 95) executing on a processor (e.g., CPU 88) of the mobile user interface device 112, a first view portion (e.g., first view portion 802) of a full-sized process plant display (e.g., full-sized process plant display 204) on the display screen 84 of the mobile user interface device 112. The first view portion (e.g., 802) may define a first zoom level and a first detail level of a process plant entity (e.g., 212) selected from the multiple process plant entities (e.g., process plant entities 212-218). In various embodiments, the display screen 84 of the mobile user interface device 112 may include a surface area that is less than the full surface area of ​​the full-sized display screen (e.g., full-sized display screen 202).

[0136] At block 906, the method 900 may further include receiving, in a mobile display navigation app (e.g., the mobile display navigation app 95), a gesture command corresponding to a user manipulation of a surface area of ​​the mobile user interface device 112 (e.g., corresponding to the length or force of a touch, pinch, or swipe gesture).

[0137] At block 908, the method 900 may further include, upon receiving the gesture command, rendering, by the mobile display navigation app (e.g., mobile display navigation app 95), a second view portion (e.g., second view portion 802) of the full-sized process plant view (e.g., full-sized process plant view 204) on the display screen 84 of the mobile user interface device 112. The second view portion (e.g., second view portion 852) may define a second zoom level and a second level of detail of the process plant entity (e.g., process plant 10). In various embodiments, the first zoom level may be different from the second zoom level and / or the first level of detail may be different from the second level of detail.

[0138] In some embodiments, the full-sized process plant display (e.g., full-sized process plant display 204) may be a browser-based display (e.g., an HTML5 browser-based display comprised of HTML5 browser-based graphics and / or instructions). In such embodiments, the mobile display navigation app (e.g., mobile display navigation app 95) may comprise a browser, such as a web browser, for receiving HTML-based graphics and / or instructions. The browser (e.g., mobile display navigation app 95) may render the first view portion (e.g., first view portion 802) on the display screen 84 of the mobile user interface device 112. In such embodiments, upon receiving a gesture command at the browser (e.g., mobile display navigation app 95) / display screen 84, the browser may execute instructions requesting electronic transmission of detailed information (e.g., graphics such as vector-based information / images or rasterized images, and / or data such as measurement parameters) from a server (e.g., server 150) associated with the process plant (e.g., process plant 10). Upon receiving the detailed information, the browser (eg, mobile display navigation app 95) can render a second view portion (eg, second view portion 802) with the detailed information.

[0139] In a further embodiment, the mobile display navigation app (e.g., the mobile display navigation app 95) may be a native Bumo This includes mobile apps (e.g. Apple iOS or Google Android applications). Bumo The mobile app may render the first view portion (e.g., first view portion 802) on the display screen 84 of the mobile user interface device 112. In such an embodiment, the native Bumo Upon receiving the gesture command at the native app (e.g., mobile display navigation app 95) / display screen 84, the browser may execute instructions to request an electronic transmission of detailed information (e.g., graphics such as vector-based information / images or rasterized images, and / or data such as measurement parameters) from a server (e.g., server 150) associated with the process plant (e.g., process plant 10). Upon receiving the detailed information, the native app (e.g., mobile display navigation app 95) may render a second view portion (e.g., second view portion 802) with the detailed information.

[0140] Aspects of the Disclosure Aspects of the Regionizer 1. A graphical user interface (GUI) based method for regionalizing a full-sized process plant view for rendering on a mobile user interface device, comprising: receiving, at a regionalizer application (app) executing on one or more processors, a full-sized process plant view that graphically represents at least a portion of the process plant, the full-sized process plant view including a graphical representation of a plurality of process plant entities within the process plant, the full-sized process plant view being a GUI adapted for rendering on a full-sized display screen of the process plant; and determining, by the regionalizer app, one or more display areas of the full-sized process plant view. determining, by one or more processors, that each of the one or more display areas defines a view portion of a full-sized process plant display, each of the one or more display areas including at least one graphical representation of a process plant entity selected from a plurality of process plant entities; and transmitting, by one or more processors, the one or more display areas to a mobile user interface device, the mobile user interface device executing a mobile display navigation app; and rendering, by the mobile display navigation app, each of the one or more display areas on a display screen of the mobile user interface device, the display screen of the mobile user interface device including a surface area that is less than the full-sized surface area of ​​the full-sized display screen.

[0141] 2. The GUI-based method of aspect 1, further comprising transmitting, by one or more processors, the full-sized process plant display to a mobile user interface device, wherein a mobile display navigation app of the mobile user interface device renders the one or more display areas on a display screen of the mobile user interface device by bounding a view portion of each of the one or more display areas to the full-sized process plant display.

[0142] 3. The GUI-based method of aspect 1, further comprising generating, by the one or more processors, one or more new displays based on determining one or more display areas of the full-sized process plant display, each new display corresponding to a view portion of its corresponding display area, and sending the one or more display areas to the mobile user interface device includes sending another new display to the mobile user interface device, and a mobile display navigation app of the mobile user interface device renders the one or more new displays on a display screen of the mobile user interface device.

[0143] 4. The GUI-based method of any of aspects 1-3, wherein determining the one or more display areas of the full-size process plant display includes a regionalizer app receiving one or more user selections that define one or more corresponding locations of the one or more display areas within the full-size process plant display.

[0144] 5. The GUI-based method of any one of aspects 1-4, wherein determining the one or more display areas of the full-size process plant display includes a regionalizer app that automatically detects the location of the one or more display areas within the full-size process plant display.

[0145] 6. The GUI-based method of embodiment 5, wherein each of the one or more display areas is detected based on a frequency of access to a view portion of each of the one or more display areas of a full-sized process plant display.

[0146] The GUI-based method of any one of aspects 1-6, wherein each of the one or more display areas is associated with a variable zoom level value corresponding to a level of detail of a view portion of each of the one or more display areas of a full-sized process plant display.

[0147] 8. The GUI-based method of aspect 7, wherein the one or more display areas include at least a first display area and a second display area, and the mobile user interface device renders the first display area at a first zoom level and renders the second display area at a second zoom level, the first zoom level being different from the second zoom level.

[0148] 9. The GUI-based method of any one of aspects 1-8, wherein the one or more display areas include at least a first display area and a second display area, the first display area being sequentially ordered relative to the second display area, and the mobile user interface device being adapted to render the first display area before the second display area.

[0149] 10. The GUI-based method of claim 9, wherein each of the one or more display areas is rendered by a mobile user interface device having a navigation panel, the navigation panel configured to receive a selection to switch between rendering the first display area and rendering the second display area.

[0150] 11. The GUI-based method of any one of aspects 1 to 10, further comprising: accessing, by the regionalizer app, a predefined GUI profile including GUI settings, the GUI settings defining at least one of an amount of one or more display areas, one or more locations within a full-sized process plant view of the one or more display areas, or one or more zoom levels of the one or more display areas; and transmitting the GUI settings to a mobile user interface device, wherein the mobile user interface device is adapted to configure the one or more display areas based on the GUI settings.

[0151] 12. The GUI-based method of aspect 11, wherein the predefined GUI profile is determined based on one or more selections provided by a user.

[0152] 13. The GUI-based method of aspect 11, wherein the predefined GUI profile is determined based on a device type of the mobile user interface device.

[0153] 14. A GUI-based method according to any one of aspects 1 to 13, wherein a view portion of at least one display portion of the one or more display areas is sized to be rendered full-screen on a display screen of a mobile user interface device.

[0154] 15. The GUI-based method of any of aspects 1-14, wherein the surface area of ​​the display screen of the mobile user interface device is less than half the surface area of ​​the full-sized display screen.

[0155] 16. The GUI-based method of any of aspects 1-15, wherein the full-size process plant representation is a comprehensive representation of the process plant.

[0156] 17. The GUI-based method of any of aspects 1-16, wherein at least one display area includes an alarm decorative graphic or a measurement parameter of a process plant entity selected from the plurality of process plant entities.

[0157] 18. The GUI-based method of aspect 17, wherein the mobile display navigation app is configured to render alarm decorative graphics or measurement parameters in real-time or near real-time.

[0158] 19. The GUI-based method of any of aspects 1-18, wherein at least one display area includes a video stream or image of a process plant entity.

[0159] 20. The GUI-based method of any of aspects 1-19, wherein the at least one display area includes an overview panel that indicates the location of the at least one display area within a full-sized process plant display.

[0160] 21. The GUI-based method of any of embodiments 1-20, wherein the full-size process plant representation is natively integrated with a process control network of the process plant.

[0161] 22. The GUI-based method of any of aspects 1-21, further comprising receiving a selection from the mobile user interface device, the selection corresponding to a process plant entity among a plurality of process plant entities, the selection initiating control of the process plant entity within the process plant.

[0162] 23. The GUI-based method of any of aspects 1-22, comprising: automatically detecting, by a display automatic introspection routine executing on the one or more processors, a graphical process control loop display portion depicted within the full-sized process plant display, where determining the one or more display areas includes defining a particular display area as the graphical process control loop display portion; generating, by a regionalizer app or a mobile display navigation app, a selectable display list representing one or more process plant entities depicted within the graphical process control loop display portion; rendering, by the mobile display navigation app, the selectable display list within a first area of ​​a display screen of the mobile user interface device; and rendering, by the mobile display navigation app, the graphical process control loop display portion within a second area of ​​the display screen of the mobile user interface device, where the mobile display navigation app adjusts a zoom level to focus on the particular process plant entity within the graphical process control loop display portion upon receiving a selection from the selectable display list corresponding to the particular one of the process plant entities.

[0163] 24. The GUI-based method of aspect 23, further comprising rendering, via a mobile display navigation app, a representation of one or more measured parameters of the particular process plant entity on a display screen of the mobile user interface device.

[0164] 25. The GUI-based method of aspect 23, comprising: rendering, by a mobile display navigation app, a representation of one or more alarm indicators of a particular process plant entity on a display screen.

[0165] 26. A graphical user interface (GUI) based system configured to regionalize a full-sized process plant display for rendering on a mobile user interface device, the system comprising: a server including one or more processors, the server communicatively coupled to a process control network of a process plant including a plurality of process plant entities; a regionalizer application (app) executing on the one or more processors, the regionalizer application configured to determine one or more display areas of the full-sized process plant display, each of the one or more regionalizer applications defining a view portion of the full-sized process plant display, each of the one or more display areas including at least one graphical representation of a process plant entity selected from the plurality of process plant entities, the full-sized process plant display being a GUI adapted to be rendered on a full-sized display screen of the process plant; and a mobile display navigation app executing on the one or more processors of a mobile user interface device, the mobile user interface device configured to receive the one or more display areas, the mobile display navigation app configured to render each of the one or more display areas on a display screen of the mobile user interface device, the display screen of the mobile user interface device comprising a surface area that is less than a full-sized surface area of ​​the full-sized display screen.

[0166] 27. The GUI-based system of aspect 26, wherein the one or more processors are configured to transmit the full-sized process plant display to a mobile user interface device, and a mobile display navigation app of the mobile user interface device renders the one or more display areas on a display screen of the mobile user interface device by bounding a view portion of each of the one or more display areas to the full-sized process plant display.

[0167] 28. The GUI-based system of aspect 26, wherein the one or more processors are configured to generate one or more new views based on determining one or more display areas of the full-sized process plant view, each new view corresponding to a view portion of its corresponding display area, and sending the one or more display areas to the mobile user interface device includes sending another new view to the mobile user interface device, and a mobile view navigation app of the mobile user interface device renders the one or more new views on a display screen of the mobile user interface device.

[0168] 29. The GUI-based system of any one or more of aspects 26-28, wherein determining one or more display areas of the full-size process plant display includes a regionalizer app receiving one or more user selections that define one or more corresponding locations of the one or more display areas within the full-size process plant display.

[0169] 30. The GUI-based system of any one or more of aspects 26-29, wherein determining the one or more display areas of the full-size process plant display includes a regionalizer app that automatically detects the location of the one or more display areas within the full-size process plant display.

[0170] 31. The GUI-based system of aspect 30, wherein each of the one or more display areas is detected based on a frequency of access to a respective view portion of the one or more display areas of a full-sized process plant display.

[0171] 32. A GUI-based system according to any one or more of aspects 26-31, wherein each of the one or more display areas is associated with a variable zoom level value corresponding to a level of detail of a view portion of each of the one or more display areas of a full-sized process plant display.

[0172] 33. The GUI-based system of aspect 32, wherein the one or more display areas include at least a first display area and a second display area, and the mobile user interface device renders the first display area at a first zoom level and renders the second display area at a second zoom level, the first zoom level being different from the second zoom level.

[0173] 34. The GUI-based system of any one or more of aspects 26-33, wherein the one or more display areas include at least a first display area and a second display area, the first display area being sequentially ordered relative to the second display area, and the mobile user interface device being adapted to render the first display area before the second display area.

[0174] 35. The GUI-based system of aspect 34, wherein each of the one or more display areas is rendered by a mobile user interface device having a navigation panel, the navigation panel configured to receive a selection for switching between rendering of the first display area and rendering of the second display area on a display screen of the mobile user interface device.

[0175] 36. A GUI-based system according to any one or more of aspects 26-35, wherein the regionalizer app is configured to access a predefined GUI profile including GUI settings defining at least one of an amount of one or more display areas, one or more locations within a full-sized process plant display of the one or more display areas, or one or more zoom levels of the one or more areas, and the one or more processors are configured to send the GUI settings to a mobile user interface device, wherein the mobile user interface device is adapted to configure the one or more display areas based on the GUI settings.

[0176] 37. The GUI-based system of aspect 36, wherein the predefined GUI profile is determined based on one or more selections provided by a user.

[0177] 38. The GUI-based system of aspect 36, wherein the predefined GUI profile is determined based on a device type of the mobile user interface device.

[0178] 39. A tangible, non-transitory computer-readable medium storing instructions for regionalizing a full-sized process plant view for rendering on a mobile user interface device, the instructions, when executed by one or more processors of a computing device, including: receiving, on the computing device, a full-sized process plant view that graphically represents at least a portion of the process plant, the full-sized process plant view including a graphical representation of a plurality of process plant entities within the process plant, the full-sized process plant view being a GUI adapted for rendering on a full-sized display screen of the process plant, and receiving, on the computing device, a full-sized process plant view that graphically represents at least a portion of the process plant, the full-sized process plant view including a graphical representation of a plurality of process plant entities within the process plant, the full-sized process plant view being a GUI adapted for rendering on a full-sized display screen of the process plant, and determining, by one or more processors, display areas, where each of the one or more display areas defines a view portion of a full-sized process plant display, where each of the one or more display areas includes at least one graphical representation of a process plant entity selected from a plurality of process plant entities; and transmitting, by one or more processors, the one or more display areas to a mobile user interface device, where the mobile user interface device executes a mobile display navigation app; and rendering, by the mobile display navigation app, each of the one or more display areas on a display screen of the mobile user interface device, where the display screen of the mobile user interface device includes a surface area that is less than a full-sized surface area of ​​the full-sized display screen.

[0179] Automatic introspection aspect display 40. A guided user interface (GUI) based method for automatically detecting a display portion of a graphical process control loop within a full-sized process plant display for rendering on a mobile user interface device, comprising: receiving, with a display automatic introspection routine executing on one or more processors, a full-sized process plant display graphically depicting at least a portion of a process plant, the full-sized process plant display including a graphical representation of a plurality of process plant entities within the process plant, the full-sized process plant display being a GUI adapted for rendering on a full-sized display screen of the process plant; and automatically detecting, with the display automatic introspection routine, a graphical process control loop display portion depicted within the full-sized process plant display, the graphical process control loop display portion including a graphical representation of one or more process plant entities selected from the process plant entities; and detecting, by the one or more processors, the graphical process control loop display portion. generating a selectable display list representing one or more process plant entities depicted within the graphical process control loop display portion; and transmitting, by the one or more processors, the graphical process control loop display portion and the selectable display list to a mobile user interface device, the mobile user interface device executing a mobile display navigation app; rendering, by the mobile display navigation app, the selectable display list in a first area of ​​a display screen of the mobile user interface device; and rendering, by the mobile display navigation app, the graphical process control loop display portion in a second area of ​​the display screen of the mobile user interface device, wherein the mobile display navigation app adjusts a zoom level to focus on the particular process plant entity within the graphical process control loop display portion upon receiving a selection from the selectable display list corresponding to the particular one of the process plant entities.Guided user interface (GUI) based method.

[0180] 41. The GUI-based method of aspect 40, further comprising rendering, via a mobile display navigation app, a representation of one or more measured parameters of a particular process plant entity on a display screen of the mobile user interface device.

[0181] 42. The GUI-based method of any one or more of aspects 40-41, comprising: rendering, by a mobile display navigation app, a representation of one or more alarm indicators of a particular process plant entity on a display screen of a mobile user interface device.

[0182] 43. The GUI-based method of any one or more of aspects 40-42, wherein the graphical process control loop display portion corresponds to a process control module of the process plant.

[0183] 44. The GUI-based method of any one or more of aspects 40-43, further comprising: automatically detecting, by a display automatic introspection routine, a graphical process control loop display portion depicted within the full-sized process plant display, the graphical process control loop display portion including a graphical representation of one or more process plant entities selected from the process plant entities; generating, by the one or more processors, a second selectable display list representing a second one or more process plant entities depicted in the second graphical process control loop display portion; and transmitting, by the one or more processors, the second graphical process control loop display portion and the second selectable display list to the mobile user interface device, wherein the mobile display navigation app is configured to switch between rendering of the graphical process control loop display portion and rendering of the second graphical process control loop display portion within a second area of ​​the display screen of the mobile user interface device upon receiving a user selection from the display screen, wherein the rendering of the graphical process control loop display portion causes the selectable display list to be rendered in the first area and the rendering of the second graphical process control loop display portion causes the second selectable display list to be rendered in the first area.

[0184] 45. The GUI-based method of any one or more of aspects 40-44, further comprising receiving from the mobile user interface device a selection corresponding to the process plant entity among a plurality of process plant entities, the selection initiating control of the process plant entity within the process plant.

[0185] 46. ​​A guided user interface (GUI) based system for automatically locating a display portion of a graphical process control loop within a full-sized process plant display for rendering on a mobile user interface device, the system comprising: a server including one or more processors, the server communicatively coupled to a process control network of a process plant including a plurality of process plant entities; a display automatic introspection routine executing on the one or more processors of the server; and a mobile display navigation app executing on the one or more processors of a mobile user interface device, the mobile display navigation app communicatively coupled to the server, the display automatic introspection routine receiving a full-sized process plant display that graphically represents at least a portion of the process plant, the full-sized process plant display including a graphical representation of a plurality of process plant entities within the process plant, the full-sized process plant display being displayed on a full-sized display screen of the process plant. a mobile user interface device adapted to receive a graphical process control loop display portion depicted within the full-sized process plant display, the graphical process control loop display portion including a graphical representation of one or more process plant entities selected from the process plant entities; and generating a selectable display list representing the one or more process plant entities depicted within the graphical process control loop display portion; the server configured to transmit the graphical process control loop display portion and the selectable display list to a mobile user interface device; and a mobile display navigation app configured to render the area selectable display list within a first area of ​​a display screen of the mobile user interface device and render the graphical process control loop display portion within a second area of ​​the display screen of the mobile user interface device;and adjusting a zoom level to focus on the particular process plant entity within the graphical process control loop display portion upon receiving a selection from a selectable display list of the above process plant entities corresponding to the particular process plant entity.

[0186] 47. The GUI-based system of aspect 46, wherein the mobile display navigation app is configured to render a representation of one or more measurement parameters of a particular process plant entity on a display screen of a mobile user interface device.

[0187] 48. The GUI-based system of any one or more of aspects 46-47, wherein the mobile display navigation app is configured to render a representation of one or more alarm indicators of a particular process plant entity on the display screen.

[0188] 49. The GUI-based system of any one or more of aspects 46-48, wherein the graphical process control loop display portion corresponds to a process control module of the process plant.

[0189] 50. The GUI-based system of any one of aspects 46-49, wherein the display automatic introspection routine is configured to automatically detect a graphical process control loop display portion depicted within the full-sized process plant display, the second graphical process control loop display portion including a graphical representation of one or more process plant entities selected from the process plant entities, the one or more processors generate a second selectable display list representing the second one or more process plant entities depicted within the second graphical process control loop display portion, the one or more processors transmit the second graphical process control loop display portion and the second selectable display list to the mobile user interface device, and the mobile display navigation app is configured to switch between rendering of the graphical process control loop display portion and rendering of the second graphical process control loop display portion within a second area of ​​the display screen of the mobile user interface device upon receiving a user selection from the display screen, wherein the rendering of the second graphical process control loop display portion causes the second selectable display list to be rendered in the first area and the rendering of the second graphical process control loop display portion causes the second selectable display list to be rendered in the first area.

[0190] 51. The GUI-based system of any one or more of aspects 46-50, wherein the mobile display navigation app is configured to receive from the mobile user interface device a selection corresponding to a process plant entity among a plurality of process plant entities, the selection initiating control of the process plant entity within the process plant.

[0191] 52. A tangible, non-transitory computer readable medium storing instructions for automatically detecting a graphical process control loop display portion within a full-sized process plant display for rendering on a mobile user interface device, the instructions, when executed by one or more processors of a computing device, causing the computing device to: receive, with a display automatic introspection routine executing on the one or more processors, a full-sized process plant display graphically depicting at least a portion of a process plant, the full-sized process plant display including a graphical representation of a plurality of process plant entities within the process plant, the full-sized process plant display being a GUI adapted for rendering on a full-sized display screen of the process plant; and automatically detecting, with the display automatic introspection routine, a graphical process control loop display portion depicted within the full-sized process plant display, the graphical process control loop display portion representing one or more process plant entities selected from the process plant. and automatically detecting, by one or more processors, a graphical representation of the process plant entity, the process plant entity being represented in the graphical process control loop display portion; generating, by one or more processors, a selectable display list representing the one or more process plant entities depicted in the graphical process control loop display portion; and transmitting, by the one or more processors, the graphical process control loop display portion and the selectable display list to a mobile user interface device, the mobile user interface device executing a mobile display navigation app, causing the mobile display navigation app to render, by the mobile display navigation app, the selectable display list within a first area of ​​a display screen of the mobile user interface device, and rendering, by the mobile display navigation app, the graphical process control loop display portion within a second area of ​​the display screen of the mobile user interface device, wherein upon receiving a selection from the selectable display list corresponding to a particular one of the process plant entities, the mobile display navigation app:A tangible, non-transitory computer readable medium for adjusting a zoom level to focus on a particular process plant entity within a graphical process control loop display portion.

[0192] Refactoring the full-size process plant view 53. A graphical user interface (GUI) based method for refactoring a full-sized process plant view at various zoom and detail levels for visualization on a mobile user interface device, comprising: transmitting, by one or more processors, a full-sized process plant view to a mobile user interface device, the full-sized process plant view graphically representing at least a portion of the process plant, the full-sized process plant view including a graphical representation of a plurality of process plant entities within the process plant; transmitting, by a mobile display navigation app executing on the processor of the mobile user interface device, a first view portion of the full-sized process plant view on the display screen of the mobile user interface device; 11. A GUI-based method comprising: rendering, wherein a first view portion defines a first zoom level and a first level of detail of a process plant entity selected from a plurality of process plant entities; a display screen of a mobile user interface device having a surface area that is less than a full-sized surface area of ​​a full-sized display screen; receiving, at a mobile display navigation app, a gesture command corresponding to a user manipulation of the surface area of ​​the mobile user interface device; and upon receiving the gesture command by the mobile display navigation app, rendering a second view portion of the full-sized process plant display on the display screen of the mobile user interface device, wherein the second view portion defines a second zoom level and a second level of detail of the process plant entity; the first zoom level differs from the second zoom level and the first level of detail differs from the second level of detail.

[0193] 54. The GUI-based method of aspect 53, wherein the mobile display navigation app renders a focused view of the process plant entity at a second zoom level compared to the first zoom level, and the mobile display navigation app renders detailed information of the process plant entity at the second level of detail on a display screen of the mobile user interface device.

[0194] 55. The GUI-based method of aspect 54, wherein the detailed information includes at least one of an alarm decorative graphic or a measurement parameter of the process plant entity.

[0195] 56. The GUI-based method of any one of aspects 54 to 55, wherein the information includes an alarm decorative graphic, and the mobile display navigation app renders a focused view when the alarm decorative graphic is triggered for display.

[0196] 57. The GUI-based method of any one or more of aspects 54-56, wherein the mobile display navigation app renders detailed information in real-time or near real-time on the display screen of the mobile user interface device.

[0197] 58. The GUI-based method of any one or more of aspects 54-57, wherein the first view portion includes a first graphics resolution and the second view portion includes a second graphics resolution, the first graphics resolution being different from the second graphics resolution.

[0198] 59. The GUI-based method of any one or more of aspects 54-58, wherein the mobile display navigation app determines each of the first graphics resolution and the second graphics resolution based on a size of the display screen of the mobile user interface device.

[0199] 60. The GUI-based method of any one or more of aspects 54-59, wherein the full-sized process plant display is comprised of multiple graphical view layers, a first view portion associated with a first graphical layer having a first zoom range and a second view portion associated with a second graphical layer having a second zoom range, and upon receiving a gesture command, the mobile display navigation app detects a transition from the first zoom range to the second zoom range, the transition causing the mobile display navigation app to render the second view portion in the second graphical layer.

[0200] 61. The GUI-based method of any one or more of aspects 54-60, further comprising receiving, at the one or more processors, a configuration command that causes the one or more processors to execute instructions to implement one or more of: (a) predefining a graphics resolution of the first view portion or the second view portion; (b) modifying the detailed information; or (c) defining a set of view layers associated with the first zoom level and the second zoom level.

[0201] 62. The GUI-based method of any one or more of aspects 54-61, wherein the full-sized process plant display is a browser-based display, the mobile display navigation app includes a browser, the browser renders a first view portion on a display screen of the mobile user interface device, and receiving a gesture command on the mobile display navigation app causes the browser to execute instructions requesting an electronic transmission of detailed information from a server associated with the process plant, and the browser, upon receiving the detailed information, renders a second view portion including the detailed information.

[0202] 63. Mobile display navigation app is native Bumo Includes mobile apps and native Bumo The mobile app renders a first view portion on a display screen of the mobile user interface device, and receiving a gesture command at the mobile display navigation app corresponds to a native Bumo and having the mobile app execute instructions requesting electronic transmission of detailed information from a server associated with the process plant, Bumo The GUI-based method of any one or more of aspects 54-62, wherein the mobile app, upon receiving the detailed information, renders a second view portion including the detailed information.

[0203] 64. The GUI-based method of any one or more of aspects 53-63, wherein the surface area of ​​the display screen of the mobile user interface device is less than half the surface area of ​​the full-size display screen.

[0204] 65. The GUI-based method of any one or more of aspects 53-64, wherein each of the first view portion and the second view portion is sized to be rendered full-screen on a display screen of a mobile user interface device.

[0205] 66. The GUI-based method of any one or more of aspects 53-65, wherein the full-size process plant display is a comprehensive representation of the process plant.

[0206] 67. The GUI-based method of any one or more of aspects 53-66, wherein the full-size process plant display is natively integrated with a process control network of the process plant.

[0207] 68. The GUI-based method of any one or more of aspects 53-67, including receiving a selection from a mobile user interface device, the selection corresponding to a process plant entity of a plurality of process plant entities, the selection initiating control of the process plant entity within the process plant.

[0208] 69. A graphical user interface (GUI) based system configured to refactor a full-sized process plant view at various zoom and detail levels for visualization on a mobile user interface device, the system comprising: a server including one or more processors, the server communicatively coupled to a process control network of a process plant including a plurality of process plant entities; and a mobile view navigation app executing on the one or more processors of the mobile user interface device, the mobile view navigation app communicatively coupled to the server, the server configured to transmit a full-sized process plant view to the mobile user interface device, the full-sized process plant view graphically representing at least a portion of the process plant, the full-sized process plant view including a graphical representation of a plurality of process plant entities within the process plant, the full-sized process plant view configured to be rendered on a full-sized display screen of the process plant. a display mobile navigation app configured to: render, on a processor of the mobile user interface device, a first view portion of the full-sized process plant view on a display screen of the mobile user interface device, the first view portion defining a first zoom level and a first level of detail of a process plant entity selected from the plurality of process plant entities, the display screen of the mobile user interface device having a surface area less than the full-sized surface area of ​​the full-sized display screen; receive a gesture command corresponding to a user manipulation of the surface area of ​​the mobile user interface device; and upon the mobile display navigation app receiving the gesture command, render a second view portion of the full-sized process plant view on the display screen of the mobile user interface device, the second view portion defining a second zoom level and a second level of detail of the process plant entity;A GUI-based system in which a first zoom level is different from a second zoom level and a first level of detail is different from a second level of detail.

[0209] 70. The GUI-based system of aspect 69, wherein the mobile display navigation app renders a focused view of the process plant entity at a second zoom level compared to the first zoom level, and the mobile display navigation app renders detailed information of the process plant entity at the second level of detail on a display screen of the mobile user interface device.

[0210] 71. The GUI-based system of any one or more of aspects 69-70, wherein the detailed information includes at least one of an alarm decorative graphic or a measurement parameter of the process plant entity.

[0211] 72. The GUI-based system of any one or more of aspects 69-71, wherein the information includes an alarm decorative graphic, and the mobile display navigation app renders a focused view when the alarm decorative graphic is triggered for display.

[0212] 72. A GUI-based system according to any one or more of aspects 71-72, wherein the mobile display navigation app renders detailed information in real-time or near real-time on the display screen of the mobile user interface device.

[0213] 73. The GUI-based system of any one or more of aspects 71-72, wherein the first view portion includes a first graphics resolution and the second view portion includes a second graphics resolution, the first graphics resolution being different from the second graphics resolution.

[0214] 74. The GUI-based system of aspect 73, wherein the mobile display navigation app determines each of the first graphic resolution and the second graphic resolution based on a size of the display screen of the mobile user interface device.

[0215] 75. The GUI-based system of any one or more of aspects 70-74, wherein the full-sized process plant display is comprised of multiple graphical view layers, a first view portion associated with a first graphical layer having a first zoom range and a second view portion associated with a second graphical layer having a second zoom range, and upon receiving a gesture command, the mobile display navigation app detects a transition from the first zoom range to the second zoom range, the transition causing the mobile display navigation app to render the second view portion in the second graphical layer.

[0216] 76. The GUI-based system of any one or more of aspects 70-75, further comprising receiving, at the one or more processors, a configuration command that causes the one or more processors to execute instructions to implement one or more of: (a) predefining a graphics resolution of the first view portion or the second view portion; (b) modifying the detailed information; or (c) defining a set of view layers associated with the first zoom level and the second zoom level.

[0217] 77. The GUI-based system of any one or more of aspects 70-76, wherein the full-sized process plant display is a browser-based display, the mobile display navigation app includes a browser, the browser renders a first view portion on a display screen of the mobile user interface device, and receiving a gesture command on the mobile display navigation app causes the browser to execute instructions requesting an electronic transmission of detailed information from a server associated with the process plant, and the browser, upon receiving the detailed information, renders a second view portion including the detailed information.

[0218] 78. Mobile display navigation app is native Bumo Includes mobile apps and native Bumo The mobile app renders a first view portion on a display screen of the mobile user interface device, and receiving a gesture command at the mobile display navigation app corresponds to a native Bumo and having the mobile app execute instructions requesting electronic transmission of detailed information from a server associated with the process plant, Bumo The GUI-based system of any one or more of aspects 70 to 77, wherein the mobile app, upon receiving the detailed information, renders a second view portion including the detailed information.

[0219] 79. The GUI-based system of any one or more of aspects 69-78, wherein the surface area of ​​the display screen of the mobile user interface device is less than half the surface area of ​​the full-size display screen.

[0220] 80. The GUI-based system of any one or more of aspects 69-79, wherein each of the first view portion and the second view portion is sized to be rendered full-screen on the display screen of the mobile user interface device.

[0221] 81. The GUI-based system of any one or more of aspects 69-80, wherein the full-size process plant display is a comprehensive representation of the process plant.

[0222] 82. The GUI-based system of any one or more of aspects 69-81, wherein the full-size process plant display is natively integrated with the process control network of the process plant.

[0223] 83. The GUI-based system of any one or more of aspects 69-82, wherein the mobile display navigation app receives a selection from the mobile user interface device, the selection corresponding to a process plant entity among a plurality of process plant entities, and the selection initiates control of the process plant entity within the process plant.

[0224] 84. A tangible, non-transitory computer readable medium storing instructions for refactoring a full-sized process plant display at various zoom and detail levels for visualization on a mobile user interface device, the instructions, when executed by one or more processors of a computing device, transmitting, by the one or more processors to the computing device, the full-sized process plant display graphically representing at least a portion of the process plant, the full-sized process plant display including a graphical representation of a plurality of process plant entities within the process plant, the full-sized process plant display being a GUI adapted for rendering on a full-sized display screen of the process plant, and displaying the full-sized process plant display on the display screen of the mobile user interface device by a mobile display navigation app executing on the processor of the mobile user interface device. a display screen of the mobile user interface device having a surface area that is less than a full-sized surface area of ​​the full-sized display screen; receiving, at the mobile display navigation app, a gesture command corresponding to a user manipulation of the surface area of ​​the mobile user interface device; and upon receiving the gesture command by the mobile display navigation app, rendering a second view portion of the full-sized process plant display on the display screen of the mobile user interface device, the second view portion defining a second zoom level and a second level of detail of the process plant entities, the first zoom level being different from the second zoom level and the first level of detail being different from the second level of detail.

[0225] Additionally, the foregoing aspects of the disclosure are merely illustrative and are not intended to limit the scope of the present disclosure.

[0226] 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 according to machine-readable instructions. The machine-readable instructions may be stored on and retrieved from a memory device communicatively coupled to the processor. In other words, the methods described herein may be embodied by a series of machine-executable instructions stored on a computer-readable medium (i.e., on a memory device), as illustrated in Figures 1B and / or 1C. 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 a computer-readable medium, the terms "stored" and "saved" are intended to exclude transitory signals.

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

[0228] 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 have been 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 the example configurations may be implemented as combined structures or components. Similarly, structures and functions presented as single components may be implemented as separate components. These and other variations, modifications, additions, and improvements are within the scope of the subject matter of this specification.

[0229] Unless specifically stated otherwise, discussions herein using words such as "processing," "operating," "calculating," "determining," "identifying," "presenting," "causing to present," "displaying," "displaying," and the like may refer to the actions or processes of a machine (e.g., a computer) that manipulates or transforms 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.

[0230] 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, laser disk, solid-state memory device, molecular memory storage device, or other storage medium, such as in the RAM or ROM of a computer or processor. It should be noted that while the exemplary systems disclosed herein are disclosed to include software and / or firmware running on hardware, among other components, such systems are merely exemplary and should not be considered limiting. For example, it is contemplated that any or all of these hardware, software, and firmware components may be embedded solely in hardware, solely in software, or in any combination of hardware and software. Thus, one skilled in the art will readily appreciate that the examples provided are not the only ways to implement such a system.

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

[0232] 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 express or implied, to limit the meaning of the term beyond its plain or ordinary meaning, and such term should not be construed as being limited in scope based on any statement made in any section of this patent (other than the claim language). If any term recited in the final claim of this patent is referred to in this patent in a manner consistent with a single meaning, it is done merely for clarity so as not to confuse the reader, and it is not intended that such claim term be limited, by implication or otherwise, to that single meaning. Finally, unless a claim element is defined by the 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 based on application of 35 U.S.C. 112(f) and / or pre-AIA 35 U.S.C. 35 U.S.C. 112, paragraph 6.

[0233] Moreover, although the above text describes detailed descriptions of many different embodiments, it should be understood that the scope of this patent is defined by the language of the claims set forth at the end of this patent. The detailed description should be construed as merely exemplary and does not describe all possible embodiments, as describing all possible embodiments 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.< / canvas> < / svg>

Claims

1. 1. A graphical user interface (GUI) based method for refactoring a full-sized process plant display at various zoom and detail levels for visualization on a mobile user interface device, comprising: transmitting, by one or more processors, a full-sized process plant representation to a mobile user interface device, the full-sized process plant representation graphically representing at least a portion of a process plant, the full-sized process plant representation including a graphical representation of a plurality of process plant entities within the process plant; transmitting the full-sized process plant representation, the full-sized process plant representation being a GUI adapted for rendering on a full-sized display screen of the process plant; rendering, by a mobile display navigation app executing on a processor of the mobile user interface device, a first view portion of the full-sized process plant display on a display screen of the mobile user interface device, the first view portion defining a first zoom level and a first detail level of a process plant entity selected from the plurality of process plant entities; rendering the display screen of the mobile user interface device having a surface area that is less than a full-sized surface area of ​​the full-sized display screen; receiving, at the mobile display navigation app, a gesture command corresponding to a user manipulation of the surface area of ​​the mobile user interface device; and rendering, by the mobile display navigation app, a second view portion of the full-sized process plant display on the display screen of the mobile user interface device upon receiving the gesture command, the second view portion defining a second zoom level and a second detail level of the process plant entities; at least one of the first view portion or the second view portion includes a predefined graphics resolution view portion of the full-size process plant representation; the first zoom level is different from the second zoom level; and rendering the first level of detail different from the second level of detail.

2. the mobile display navigation app renders a focused view of the process plant entity at the second zoom level compared to the first zoom level; The GUI-based method of claim 1 , wherein the mobile display navigation app renders detailed information of the process plant entity at the second level of detail on a display screen of the mobile user interface device.

3. The GUI-based method of claim 2 , wherein the detailed information includes at least one of an alarm decorative graphic or a measurement parameter of the process plant entity.

4. The GUI-based method of claim 3 , wherein the detailed information includes the alarm decorative graphic, and a mobile display navigation app renders the focused view when the alarm decorative graphic is triggered for display.

5. The GUI-based method of claim 2 , wherein the mobile display navigation app renders the detailed information in real-time or near real-time on the display screen of the mobile user interface device.

6. 6. The GUI-based method of claim 2, wherein the first view portion includes a first graphics resolution and the second view portion includes a second graphics resolution, the first graphics resolution being different from the second graphics resolution.

7. The GUI-based method of claim 6 , wherein the mobile display navigation app determines each of the first and second graphics resolutions based on a size of the display screen of the mobile user interface device.

8. the full-sized process plant representation is comprised of multiple graphical view layers; the first view portion is associated with a first graphical layer having a first zoom range, and the second view portion is associated with a second graphical layer having a second zoom range; Upon receiving the gesture command, the mobile display navigation app detects a transition from the first zoom range to the second zoom range; The GUI-based method of claim 2 , wherein the transition causes the mobile display navigation app to render the second view portion in the second graphics layer.

9. In the one or more processors, (a) predefining a graphics resolution of the first view portion or the second view portion; (b) change those details; or (c) defining a set of view layers associated with the first zoom level and the second zoom level.

10. the full-sized process plant view is a browser-based view, and the mobile view navigation app includes a browser; the browser renders the first view portion on the display screen of the mobile user interface device; receiving the gesture command at the mobile display navigation app causes the browser to execute instructions requesting an electronic transmission of the detailed information from a server associated with the process plant; The GUI-based method of claim 2 , wherein the browser, upon receiving the detailed information, renders the second view portion with the detailed information.

11. the mobile display navigation app comprises a native mobile app; the native mobile app renders the first view portion on the display screen of the mobile user interface device; receiving the gesture command at the mobile display navigation app causes the native mobile app to execute instructions requesting an electronic transmission of the detailed information from a server associated with the process plant; The GUI-based method of claim 2 , wherein the native mobile app, upon receiving the detailed information, renders the second view portion with the detailed information.

12. The GUI-based method of claim 1 , wherein a surface area of ​​the display screen of the mobile user interface device is less than half the surface area of ​​the full-sized display screen.

13. 13. The GUI-based method of claim 1, wherein each of the first view portion and the second view portion is sized to be rendered full-screen on the display screen of the mobile user interface device.

14. The GUI-based method of claim 1 , wherein the full-size process plant representation is a comprehensive representation of the process plant.

15. The GUI-based method of claim 1 , wherein the full-sized process plant representation is natively integrated with a process control network of the process plant.

16. receiving a selection from the mobile user interface device, the selection corresponding to the process plant entity of the plurality of process plant entities; The GUI-based method of claim 1 , wherein the selection initiates control of the process plant entity within the process plant.

17. 1. A graphical user interface (GUI) based system configured to refactor full-sized process plant displays at various zoom and detail levels for visualization on a mobile user interface device, comprising: a server including one or more processors, the server communicatively coupled to a process control network of a process plant including a plurality of process plant entities; a mobile display navigation app executing on one or more processors of a mobile user interface device, the mobile display navigation app communicatively coupled to the server; the server is configured to transmit a full-sized process plant representation to the mobile user interface device, the full-sized process plant representation graphically representing at least a portion of the process plant, the full-sized process plant representation including a graphical representation of the plurality of process plant entities within the process plant, the full-sized process plant representation being a GUI adapted for rendering on a full-sized display screen of the process plant; The mobile display navigation app includes: rendering, on a processor of the mobile user interface device, a first view portion of the full-sized process plant display on a display screen of the mobile user interface device, the first view portion defining a first zoom level and a first detail level of a process plant entity selected from the plurality of process plant entities, the display screen of the mobile user interface device having a surface area that is less than a full-sized surface area of ​​the full-sized display screen; receiving a gesture command corresponding to a user manipulation of the surface area of ​​the mobile user interface device; and upon receiving the gesture command, the mobile display navigation app is configured to render a second view portion of the full-sized process plant display on the display screen of the mobile user interface device, the second view portion defining a second zoom level and a second detail level of the process plant entity; at least one of the first view portion or the second view portion includes a predefined graphics resolution view portion of the full-size process plant representation; the first zoom level is different from the second zoom level; A GUI-based system, wherein the first level of detail is different from the second level of detail.

18. the mobile display navigation app renders a focused view of the process plant entity at the second zoom level compared to the first zoom level; 20. The GUI-based system of claim 17, wherein the mobile display navigation app renders detailed information of the process plant entity at the second level of detail on the display screen of the mobile user interface device.

19. The GUI-based system of claim 18 , wherein the detailed information includes at least one of an alarm decorative graphic or a measurement parameter of the process plant entity.

20. 20. The GUI-based system of claim 19, wherein the detailed information includes the alarm decorative graphic, and a mobile display navigation app renders the focused view when the alarm decorative graphic is triggered for display.

21. 21. The GUI-based system of claim 18, wherein the mobile display navigation app renders the detailed information in real-time or near real-time on the display screen of the mobile user interface device.

22. 22. The GUI-based system of claim 18, wherein the first view portion includes a first graphics resolution and the second view portion includes a second graphics resolution, the first graphics resolution being different from the second graphics resolution.

23. 23. The GUI-based system of claim 22, wherein the mobile display navigation app determines each of the first graphics resolution and the second graphics resolution based on a size of the display screen of the mobile user interface device.

24. the full-sized process plant representation is comprised of multiple graphical view layers; the first view portion is associated with a first graphical layer having a first zoom range, and the second view portion is associated with a second graphical layer having a second zoom range; Upon receiving the gesture command, the mobile display navigation app detects a transition from the first zoom range to the second zoom range; 24. The GUI-based system of claim 18, wherein the transition causes the mobile display navigation app to render the second view portion in the second graphical layer.

25. In the one or more processors, (a) predefining a graphics resolution of the first view portion or the second view portion; (b) change those details; or (c) defining a set of view layers associated with the first zoom level and the second zoom level.

26. the full-sized process plant view is a browser-based view, and the mobile view navigation app includes a browser; the browser renders the first view portion on the display screen of the mobile user interface device; receiving the gesture command on the mobile display navigation app causes the browser to execute instructions requesting an electronic transmission of the detailed information from a server associated with the process plant; 26. The GUI-based system of claim 18, wherein the browser, upon receiving the detailed information, renders the second view portion with the detailed information.

27. the mobile display navigation app comprises a native mobile app; the native mobile app renders the first view portion on the display screen of the mobile user interface device; receiving the gesture command at the mobile display navigation app causes the native mobile app to execute instructions requesting an electronic transmission of the detailed information from a server associated with the process plant; The GUI-based system of claim 18 , wherein the native mobile app, upon receiving the detailed information, renders the second view portion with the detailed information.

28. 28. The GUI-based system of claim 17, wherein the surface area of ​​the display screen of the mobile user interface device is less than half the surface area of ​​the full-sized display screen.

29. 29. The GUI-based system of claim 17, wherein each of the first view portion and the second view portion is sized to be rendered full-screen on the display screen of the mobile user interface device.

30. 30. The GUI-based system of claim 17, wherein the full-size process plant representation is a comprehensive representation of the process plant.

31. 31. The GUI-based system of claim 17, wherein the full-sized process plant representation is natively integrated with a process control network of the process plant.

32. the mobile display navigation app receives a selection from the mobile user interface device, the selection corresponding to the process plant entity of the plurality of process plant entities; 32. The GUI based system of claim 17, wherein the selection initiates control of the process plant entity within the process plant.

33. 1. A tangible, non-transitory computer readable medium storing instructions for refactoring a full-sized process plant display at various zoom and detail levels for visualization on a mobile user interface device, the instructions, when executed by one or more processors of a computing device, causing the computing device to: transmitting, by one or more processors, a full-sized process plant representation to a mobile user interface device, the full-sized process plant representation graphically representing at least a portion of a process plant, the full-sized process plant representation including a graphical representation of a plurality of process plant entities within the process plant; transmitting the full-sized process plant representation, the full-sized process plant representation being a GUI adapted for rendering on a full-sized display screen of the process plant; rendering, by a mobile display navigation app executing on a processor of the mobile user interface device, a first view portion of the full-sized process plant display on a display screen of the mobile user interface device, the first view portion defining a first zoom level and a first detail level of a process plant entity selected from the plurality of process plant entities; rendering the display screen of the mobile user interface device having a surface area that is less than a full-sized surface area of ​​the full-sized display screen; receiving, at the mobile display navigation app, a gesture command corresponding to a user manipulation of the surface area of ​​the mobile user interface device; and rendering, by a mobile display navigation app, a second view portion of the full-sized process plant display on the display screen of the mobile user interface device upon receiving the gesture command, the second view portion defining a second zoom level and a second detail level of the process plant entities; at least one of the first view portion or the second view portion includes a predefined graphics resolution view portion of the full-size process plant representation; the first zoom level is different from the second zoom level; and rendering, wherein the first level of detail is different from a second level of detail.

Citation Information

Patent Citations

  • Back-side gate electrode and manufacture thereof

    JP1984083677A

  • Automatic sequence system for vehicle assembly components

    JP1988097476A

  • Monitor control system

    JP2002268733A

  • Water treatment plant monitoring system

    JP2009181436A

  • Controller and display control method

    JP2009187071A