DE102014103511A1 - Method and device for determining the position of a mobile control device in a process plant - Google Patents

Abstract

Methods, systems and devices for determining the position of a mobile device with respect to an anchor point by coupling. Data indicative of an anchor position within a process plant is captured and an anchor position is determined according to the captured data. Data indicating acceleration and orientation of the mobile device are received from circuits of the mobile device. A position of the mobile device is determined according to the received data and the anchor position.

Description

FIELD OF USE

 The present disclosure relates generally to process control systems and process plants, and more particularly to the use of mobile user interface devices in process control systems and process plants.

BACKGROUND

Decentralized process control systems, particularly in chemical, petroleum processing and other process plants, typically include one or more process control units connected to one or more field devices via analog, digital or analog / digital bus technology, a wireless communication link or a wireless network. The field devices, which are z. These can be valves, valve positioners, switches, and transducers (eg, temperature, pressure, level, and flow sensors), are in the process environment, and generally perform physical functions or process control functions such as valve opening and closing , measuring process parameters, etc. to control one or more of the processes executed in the process plant or in the process control system. In addition, intelligent field devices, eg. For example, field devices that conform to the well-known Fieldbus protocol perform control calculations, alarms, and other functions that are commonly implemented in the control unit. The process controllers, which are usually located in the plant environment, receive signals for the process measurements by sensors and / or field devices and / or other information for the field devices and execute a control application. This in turn leads z. B. different control modules from which make decisions for process control, generate control signals based on the received information and coordinate with the control modules or blocks that in the field devices, eg. Be carried out and FOUNDATION ^® Fieldbus devices - B. HART ^® - WirelessHART ^®. The control modules in the controller send control signals to the field devices via communication links to thereby control the execution of at least a portion of the process plant or processing system.

 The information from the field devices and the control unit i. d. R. via a data highway to one or more hardware devices, eg. For example, operator workstations, personal computers or other computers, data historians, report generators, central databases, or other centralized administrative computer that i. d. R. in control centers or other locations outside the actual system, transmitted. Each of these hardware devices will i. d. R. centrally used for the entire process plant or a section of the process plant. These hardware devices run applications that, for. B. allow an operator to perform functions for the control of a process and / or the operation of the process plant. These include changing settings of the process control routine, changing the operation of the control modules in the control units or field devices, displaying the current status of the process, displaying the alarms generated by field devices and control units, simulating the process to train employees, or the Testing and maintaining a configuration database, and so forth. The information highway used by the hardware devices, controllers, and field devices may be a wired communication path, a wireless communication path, or a combination of wired and wireless communication path.

For example, Emerson Process Management's DeltaV ^™ process control system includes multiple applications that are stored and executed by different devices, located at different locations within a process plant. Each of these applications has a user interface (UI) to allow the user (eg, configuration engineer, operator, service technician, etc.) to view and / or change aspects of the operation and configuration of the process plant. Throughout this specification, the term "UI" refers to an application or screen that allows the user to view or change the configuration, operation, or status of the process plant. Accordingly, the term "user interface device" or "UI device" refers to a device that has a user interface. This can be a stationary device (eg workstation, wall mounted display, display of a process control device, etc.) or a mobile device (eg laptop, tablet, smartphone, etc.). A configuration application on one or more operator workstations or computers allows users to create or modify process control modules and download these modules via a data highway to dedicated distributed control units. As a rule, these control modules consist of function blocks between which communication connections exist. These are objects in a log of Object-oriented programming that performs functions in the control scheme based on inputs to the schema and provides outputs to other function blocks in this control scheme. The configuration application may also enable a configuration developer to create or modify user interfaces with which a presentation application displays data to an operator and to allow the operator to change settings, e.g. From setpoints, in the process control routines. Each dedicated controller, and in some cases one or more field devices, store a corresponding control application executing on them. This executes the assigned and downloaded control modules to implement the actual process control. The presentation applications that can be run on one or more operator workstations (or on one or more remote computers connected to the operator workstations and the information superhighway) receive data from the control application via the information superhighway and use the UIs to display that data for developers, operators or users of the process control system. You can view a number of different views, such as B. an operator view, an engineer's view, a technician view, etc., provide. Typically, a data historian application is stored on and executed by a data history device. This captures and stores all or some of the data provided via the information superhighway. A configuration database application can be run on a remote computer that is connected to the information superhighway and stores the current configuration of the process control functionality as well as the associated data. Alternatively, the configuration database may reside on the same workstation as the configuration application.

The architecture of process plants and process control systems was heavily influenced by control unit and device memory limitations, the bandwidth of the communication link, and the capacity of controller and device processors. For example, the use of a dynamic and static persistent store in the controller is usually minimized or at least carefully controlled. Therefore, during system configuration (ie a priori) i. d. R. choose what data is archived or stored in the controller, how often it is stored, and whether compression is used. The control unit is configured with this limited set of data rules. As a result, data that might be useful for error handling and process analysis is often not archived, and if it has been captured, the helpful information may have been lost due to data compression.

Additionally, to minimize memory usage in currently known process control systems, data that is to be archived or stored is reported to the workstation or computer for use, e.g. B. in the appropriate Historian or data silo to save. Current data-reporting techniques are under-utilization of communications resources, which causes an excessive load on the control unit. Additionally, due to delays in communication and sampling in the Historian or Silo, data collection and timestamping are often out of sync with the actual process.

In batch process control systems, to minimize the use of the memory of the controller, batch recipes and snapshots of the controller configuration remain i. d. R. are stored on a central management computer or in a central storage location (eg in a data silo or data historian) and are only transferred to a control unit when needed. Such a strategy results in significant abrupt loads in the control unit and in the communication channels between the workstation or the central management computer and the control unit.

In addition, the capacity and performance limitations of relational databases of process control systems, combined with the high cost of disk storage, are of great importance in structuring application data into stand-alone instances or silos to serve the purposes of particular applications. For example, the DeltaV ^TM system stores and / or archives process models, continuous historical data, and batch and event data in three different application databases or data silos. Each silo has a different interface for accessing the data stored in it.

Such structuring of data limits access to and use of historical data. For example, perhaps the most important cause of product quality variation is related to data in one or more of these data files. However, due to the different file structures, it is not possible to provide tools that allow quick and easy access to this data for analysis. In addition, checking or synchronization functions must be performed to ensure cross-silo consistency of the data.

The limitations of process equipment and process control systems described above as well as other limitations may apply to Operation and optimization of process plants and process control systems, eg B. during operations in the system, in the error treatment or predictive modeling, lead to undesirable effects. For example, these limitations force tedious and lengthy workflows that must be performed to obtain data for error handling and for generating updated models. In addition, the data obtained may be corrupted due to data compression, insufficient bandwidth, or changed timestamps.

The present background description is intended to outline the context of the disclosure. The work of the present inventors described in this Background section, as well as aspects of the description that can not be considered as prior art at the time of application, are expressly or impliedly acknowledged as prior art in view of the present disclosure.

SUMMARY

 In one embodiment, a method for determining a location of a mobile device within a process control environment includes collecting data indicating an anchor position within the process plant and determining the anchor position according to the acquired data. The method also includes receiving data from the circuits of the mobile device indicating acceleration and orientation of the mobile device and determining a position of the mobile device according to the received data and the anchor position.

In another embodiment, a mobile device for performing control operations in a process control environment includes a first circuit for acquiring first data indicating an anchor position within a process plant, and a second circuit for determining the acceleration and orientation of the mobile device. The second circuit generates second data indicating acceleration and orientation. The apparatus also includes one or more processors, including at least one processor communicatively coupled to the first circuit and at least one processor communicatively coupled to the second circuit operable (i) based on the anchor position on the first data, and (ii) to determine a position of the mobile device according to the second data and the anchor position.

BRIEF DESCRIPTION OF THE DRAWINGS

1A Figure 12 is a block diagram of an exemplary process control network in a process control system or process plant.

1B is a block diagram of a broader control network.

2 Figure 4 is a block diagram illustrating a communication architecture, including a mobile switching center, as described herein.

3 FIG. 12 is a block diagram illustrating one embodiment of a monitoring module according to the present description. FIG.

In 4 a sample work task is presented by the monitoring module in 23 can be generated.

5 is a flowchart describing a method for assigning tasks to employees in a process plant.

6 is a flowchart describing a method for controlling a workflow in a process plant.

7 is a flowchart describing a method for performing tasks in a process plant.

8th is a block diagram of a UI device.

9A illustrates an aspect of an exemplary mobile control center.

9B illustrates devices in an exemplary mobile control center.

10 illustrates examples of device displays related to UI synchronization between UI devices.

11 Figure 10 is a flowchart illustrating an exemplary method for synchronizing UI devices.

12A Figure 13 is a block diagram illustrating exemplary data for UI devices in an exemplary mobile switching center.

12B Figure 13 is a block diagram illustrating exemplary data for UI devices in another example of a mobile switching center.

13 Figure 10 is a flowchart for an exemplary method of providing session data for a UI device.

14 Figure 10 is a flowchart for an exemplary method of generating a GUI configuration on a UI device.

15 Figure 13 is a flowchart of an exemplary method for the direct transmission of status information between two UI devices.

16 Figure 13 is a flowchart of an exemplary method for transmitting status information between two UI devices connected to a server.

17 Figure 12 is a flow chart of an additional method for transmitting status information between two UI devices.

18 is a flowchart illustrating yet another exemplary method of controlling a process plant using UI devices connected to a mobile control center.

19 Figure 10 is a flowchart illustrating a process performed on a server that enables mobile control of a process plant using UI devices.

20 FIG. 10 is a flowchart of a method for transmitting status information of a first UI device to a second UI device.

21 Figure 10 is a flowchart of a method for initiating a UI session on a first UI device.

22 Figure 12 is a flowchart of a second method for instantiating a UI session on a first UI device.

23 illustrates a second aspect of an exemplary mobile control center.

24 Figure 12 is a block diagram of an exemplary context sensitive UI device.

25 is a block diagram of another embodiment of a mobile control center in a process plant.

26 represents yet another exemplary mobile control center.

27 FIG. 10 is a flowchart of an exemplary method for generating a graphical user interface. FIG.

28 Figure 10 is a flowchart of an exemplary method performed by a UI device.

29 is a flowchart of a method for enabling mobile control of a process plant.

30 FIG. 10 is a flowchart of a method for determining the position of a mobile device in a process plant.

31 FIG. 10 is a flowchart of a method for contextually operating a mobile device in a process control environment.

32 Figure 10 is a flowchart illustrating a method for analyzing physical phenomena in a process plant.

DETAILED DESCRIPTION

 The decentralization and mobilization of the control and maintenance systems for a process plant offers many advantages. For example, mobile UI devices cooperate with stationary UI devices to make operators, maintenance personnel, and other plant personnel independent of a central location. Employees can move throughout the process plant without sacrificing access to information about the operation and status of the process plant. By implementing big data concepts (ie, collecting, storing, managing, and using one or more collections of data that is so large or complex that traditional database management programs and / or data processing applications can not handle the data sets within a reasonable amount of time) in combination with expert systems, monitoring systems and context sensitive UI devices, the process plant can be operated and maintained more efficiently (eg lower maintenance, higher yield, less downtime, less manpower, lower safety risks for workers and machinery, etc.) , This is described throughout this disclosure.

Basically, the cooperation between the context-sensitive mobile UI devices with the expert systems, monitoring systems and Big Data systems improves the operation of the process plant. Improving the operation of the plant may be implemented with one or more of the concepts described herein. These include aspects of collaboration, mobility, workflow management, human resource management, automation, liability, Verification and diagnosis. For example, the devices, systems, and methods described herein may enable seamless transfer between UI devices (eg, from a workstation to a tablet or from a tablet to a mobile phone). Users will then have the same or nearly the same information, even when switching between devices. Collaboration between different employees in the same location or different locations for which the same or different data is displayed is facilitated; and / or user sessions may be initiated or continued regardless of the device the user is currently using. Mobile versions of UI devices can be device-aware and / or location-aware so they automatically display relevant information (such as maps, procedures, charts, user guides), launch applications, and more. In addition, collaboration between the expert and monitoring system and the UI devices may allow automatic generation, assignment and management of work tasks for operator and / or maintenance activities. As described in more detail below, z. For example, analyze the information stored by the expert system in the big data system, determine that a particular task should be performed, and work with the monitoring system to create a work item, assign it to a person, and create a checklist of items required to complete the task to guide the instructed person through the execution of the assigned task and to track the progress of the task. These and other aspects are described throughout the document.

To first describe the general architecture of an exemplary process plant, in 1A a block diagram of an exemplary process control network 100 represented in a process control system or a process plant 10 is operated. The process control network 100 can be a backbone 105 which provides the direct or indirect connection between various other devices. The one with the backbone 105 Connected devices in various embodiments include combinations of access points 72 and gateways 75 to other process plants (eg via an intranet or a corporate WAN), gateways 78 to external systems (eg the Internet), UI devices 112 , Server 150 , Big data systems 102 (eg with big data historian), Big Data expert systems 104 , Monitoring modules 106 , Control units 11 , I / O cards 26 and 28 , Wired field devices 15 - 22 , Wireless gateways 35 and wireless communication networks 70 , The communication networks 70 can the wireless devices 40 - 58 to which the wireless field devices 40 - 46 , the wireless adapter 52a and 52b , the access points 55a and 55b as well as the router 58 counting. The wireless adapters 52a and 52b can each use the wired field devices 48 and 50 get connected. The control unit 11 can be a processor 30 , a store 32 and one or more control routines 38 contain. In 1A some will be with the backbone 105 Connected devices shown only as a single device, the skilled person will however see that in the backbone 105 multiple instances of each of the devices may be present. In addition, the process plant 10 several backbones 105 contain.

The UI devices 112 can over the backbone 105 for communication with the control unit 11 and the wireless gateway 35 get connected. The control unit 11 can via the I / O cards 26 and 28 with the wired field devices 15 - 22 and over the backbone 105 and a wireless gateway 35 with the wireless field devices 40 - 46 communicatively connected. The control unit 11 can by using at least one of the field devices 15 - 22 and 40 - 46 implement a batch process or a steady process. The control unit 11 which may be, for example, the Emerson Process Management DeltaV ^™ control unit, is a backbone with process control network 105 connected. The control unit 11 can also with the field devices 15 - 22 and 40 - 46 get connected. This can be done with any desired hardware and software for the control unit, for. With standard 4-20 mA devices, the I / O cards 26 and 28 and / or any intelligent communication protocol, e.g. As the FOUNDATION ^® Fieldbus protocol, the HART ^® protocol, the WirelessHART ^® protocol, etc. In the in 1A illustrated embodiment, the control unit 11 , the field devices 15 - 22 and the I / O cards 26 and 28 wired devices while the field devices 40 - 46 Wireless field devices are.

When operating the UI device 112 For example, in some embodiments, this may execute a user interface (UI) to the UI device 112 allows input to be accepted via an input interface and to display the output on a display. The UI device 112 may include data (eg, process data such as process parameters, log data, sensor data, and / or other data that is captured and in the big data system 102 saved) from the server 150 receive. In other embodiments, the UI may be completely or partially on the server 150 running, the server 150 Display data to the UI device 112 can send. The UI device 112 can over the backbone 105 UI data (which may include display data and process parameter data) from other nodes in the process control network 100 , z. B. from the control unit 11 , the wireless gateway 35 or the server 150 , received. The UI device 112 provides output (visuals or graphics) based on the data received on it, the aspects of the process control network 100 represent a linked process so that the user can monitor the process. The user can influence the control of the process by clicking on the UI device 112 Provides inputs. The UI device 112 can provide graphics for illustration, the z. B. represent the filling of a container. In such a scenario, the user can read a container level measurement and decide that the container needs to be filled. The user can use one on the UI device 112 displayed inlet valve graph and enter a command that causes the opening of the inlet valve.

The UI device 112 may continue to run a number of routines, modules, or services in addition to the UI. In one embodiment, the UI device may 112 execute a context sensitivity routine, the z. For example, various routines or subroutines may include location awareness, device awareness, or schedule awareness (as in 27 shown). These context routines can be used by the UI device 112 allow visualization of the configuration of a graphical user interface (GUI configuration) customized for a particular environment or context in which the UI device is located 112 is operated. The UI device 112 can also perform a state-determining routine that tells the UI device 112 allows to track and save its status, including the status of the applications running on the UI device 112 be executed (eg the UI). The UI device 112 By tracking the status of the applications running on it, a user can initiate a session on a first UI device to a user 112 and starting to use a second UI device 112 enable the workflow of the previous session to continue with minimal disruption.

The UI device 112 (or the server that has an application or screen for the UI device 112 can also execute routines for controlling asset inventories. For example, some routines may be used to install, replace, maintain, calibrate, diagnose, or commission inventory in the process plant. Other routines may be used to create or execute work orders for particular stocks and / or to notify plant personnel (eg, personnel near a particular device) about a work order. The UI device 112 can run routines to monitor the process. For example, some routines may be used for field logging instrument data, reporting laboratory samples, displaying real-time inventory parameters, and the like. Ä. Be used. The UI device 112 can also perform routines for compliance with plant procedures and workflow. For example, some routines may provide information about Standard Operating Procedures (SOPs), startup procedures, shutdown procedures, locking procedures, operating instructions, or other product / inventory documentation. If the UI device 112 Also connected to a network, additional routines can provide immediate job submission and immediate system availability for offline manually entered data. Communication routines may include e-mail routines, SMS routines, instant message routines, etc., to facilitate communication between plant personnel and / or external parties providing technical or other support.

The UI device 112 (or the server that has an application or screen for the UI device 112 may also contain routines that support and / or facilitate one or more validation processes. In the examination processes, it may be z. B. work checks and / or official inspections act. In embodiments, the routines may enable a user to display data and / or generate reports on data that is collected, managed, and / or aggregated to meet regulatory requirements. To illustrate, when deployed in a drug manufacturing facility, the mobile control center can facilitate the display or logging of data needed to meet regulatory compliance requirements for the safety of the equipment produced by the equipment. In embodiments, the routines may enable a user to view and / or generate reports for reviewing work orders, maintenance processes, or other asset processes.

In certain embodiments, the UI device may 112 any type of client, e.g. Thin Client, Web Client, or Thick Client. For example, the UI device 112 for the high processing power required for the operation of the UI device 112 necessary to need more nodes, computers or servers. In such an example, the UI device may 112 with the server 150 communicate with the server 150 with one or more other nodes in the process control network 100 communicates and determines the display and / or process data sent to the UI device 112 to be transferred. The UI device 112 can also send all data related to received user input to server 150 forward that to the server 150 process the data of the user input and act accordingly. In other words, the UI device 112 It merely represents graphics and acts as a portal to one or more nodes or servers that store the data and execute the routines necessary to operate the UI device 112 required are. A UI device implemented as a thin client has the advantage that the UI device 112 has minimal hardware requirements.

In other embodiments, the UI device may 112 be a web client. In such an embodiment, a user of the UI device may 112 via a browser on the UI device 112 interact with the process control system. The browser provides the user with the backbone 105 Access to data and resources on another node or server (eg server 150 ). For example, the browser may use UI data, e.g. For example, display data or process parameter data from server 150 receive and thus graphics for controlling and / or monitoring some or all processes. The browser can also receive user input (eg a mouse click on a graphic). The user input may cause the browser to be on the server 150 retrieves or invokes stored information resource. For example, the mouse click may cause the browser to retrieve information about the graphic that was clicked (from the server 150 ) and displays.

In other embodiments, mass processing may be for the UI device 112 on UI device 112 occur. For example, the UI device 112 execute the previously described UI, state determination routine, and context sensitivity routine. The UI device 112 can also store, access and analyze data locally.

During operation, a user can use the UI device 112 interact with one or more devices in the process control network 100 to monitor or control, for. B. one of the field devices 15 - 22 or the devices 40 - 48 , The user can use the UI device 112 interact to B. to modify or change a parameter, the one in the control unit 11 stored control routine is assigned. The processor 30 the control unit 11 implements or oversees one or more process control routines (in a memory 32 stored), which may contain control loops. The processor 30 can with the field devices 15 - 22 and 40 - 46 as well as communicate with other nodes that are connected to the backbone 105 are connected. It is to be understood that all control routines or modules described in this disclosure (including quality prediction and fault detection modules or function blocks) may include parts that may be executed by different controllers or other devices. The control routines or modules described here can also be used in the process control system 10 be implemented, have any shape, z. Software, firmware, hardware, etc. Control routines may be in any desired software format, eg. It can be implemented using object-oriented programming, ladder logic, flowcharts, function-language languages, any other programming language, or any other design model. In particular, the control routines may be from a user via the UI device 112 be implemented. The control routines can be stored in any type of memory, e.g. B. RAM (random access memory) or ROM (read-only memory). Additionally, the control routines may be hard-coded in one or more EPROMs, EEPROMs, application-specific integrated circuits (ASICs), or any other hardware or firmware elements. Therefore, the control unit can be 11 to configure (in certain embodiments, a user using a UI device 112 ) that the control strategy or routine can be implemented in any desired manner.

In some embodiments of the UI device 112 a user can use the UI device 112 interact by using a mechanism commonly referred to as function blocks on the control unit 11 implementing a control strategy, wherein each function block is an object or other part (eg, a subroutine) of a general control routine, and each function block is executed in conjunction with other function blocks (via communication links) to process control loops in the process control system 10 perform. Control-based function blocks execute an input function id R, z. B. is linked to a sensor, sensor or other process parameter measuring device, perform a control function, the z. B. is linked to a control routine that performs PID control, fuzzy logic control, etc., or perform an output function that allows the operation of a device, such. As a valve, controls to perform a physical function in the process control system. Of course, there are hybrid function blocks and other types of function blocks. For the function blocks can be on the UI device 112 provide graphical representations that allow a user to easily change the types of function blocks, the connections between the function blocks, and the inputs / outputs for each function block implemented in the process control system. Function blocks can be on the control unit 11 stored and executed by this. This is usually the case when the function blocks for standard 4-20 mA devices and some types of smart field devices such B. HART devices are used or assigned are. Or they can be stored on the field devices themselves and implemented by them. This can be the case with fieldbus devices. The control unit 11 can be one or more control routines 38 contain one or more control loops. Each control loop is usually called a control module and can be executed using one or more of the function blocks.

In certain embodiments, the UI device interacts 112 with the big data system 102 and / or the expert system 104 and / or the monitoring module 106 , The big data system 102 can handle all types of process control data from the process plant 10 including sensor data, control parameters, manually entered data (eg, data collected by employees when they are in the process plant 10 move), employee locations and command entries, timestamps for all data and any other type of data in the process plant 10 are available, capture and save. The big data system 102 connected expert system 104 can work on its own or according to specific user input, in the big data system 102 to store stored data of the process plant. The expert system 104 may develop and / or use models, recognize trends and / or correlations, alert plant personnel to existing or predicted problems, and / or abnormal situations and / or suboptimal conditions that may affect the process plant 10 impact, or soon, etc. In some embodiments, the expert system performs 104 these functions, without being specifically programmed to associate a particular set of data or trends with a particular problem or condition; instead, it recognizes that a current trend or occurrence occurred before or about the same time of an earlier condition (which may be a positive / desirable condition or a negative / undesirable condition). The expert system 104 can predict the condition by detecting the earlier occurrence of the trend or the data (forecast). The expert system 104 can also be based on the big-data system 102 stored data determine which process variables, sensor values, etc. (ie which data) in detecting, predicting, preventing and / or correcting an abnormal situation in the process plant 10 are particularly important. For example, the expert system recognizes 104 possibly, hydrocarbon escapes from a stack and can automatically determine the cause and / or generate work items (eg, through the monitoring module 106 ), and / or cause the generation of work tasks to inspect the equipment or observe / record a parameter that is not available over the network. In another example, the expert system determines 104 in that a trend indexed by a series of previous data points justifies the prediction of an abnormal situation, a maintenance problem, a disturbance, and so on.

As described in detail below, the monitoring module 106 with the big data system 102 and / or the expert system 104 interact to automatically perform and / or enable various monitoring activities. For example, the monitoring module 106 from the expert system 104 Monitor identified trends and create work tasks for the plant personnel. In another example, the monitoring module 106 Monitor the calibration status of process plant resources and create work items for plant personnel. The monitoring module 106 In conjunction with these features, it can also manage employee certifications, permissions to access equipment while performing scheduled work tasks, and timekeeping execution of work items. The monitoring module 106 can with the UI devices 112 interact to assign work tasks and track their execution, and follow-up on completion of a work task to verify that the status or indication that led to the work task creation (eg, the identified trend, the abnormal situation, etc.) has been corrected. For example, the monitoring module 106 based on the expert system 104 determine that a valve is malfunctioning and create a work item. Eventually, the monitoring module determines 106 later, that a maintenance worker who is a UI device 112 with it, is near the faulty valve, and request the assignment of the work task to the service person who is using the UI device 112 can accept the work task. The monitoring module 106 can verify that the service person has the appropriate skills to complete the work item and provide the required permissions to perform the task by the service person. In addition, the monitoring module 106 Reschedule process control activities to complete the work task. The monitoring module 106 may provide standard work instructions, manuals, and other documentation to the employee before and / or during the execution of the work task. These are just a few Examples of the monitoring module 106 , which will be explained in more detail below.

The wireless field devices 40 - 46 in 1A communicate in a wireless network 70 using a wireless protocol, such as Using the WirelessHART protocol. In certain embodiments, the UI device may 112 over the wireless network 70 with the wireless field devices 40 - 46 communicate. The wireless field devices 40 - 46 can connect directly to one or more other nodes of the process control network 100 communicate, which are also configured for wireless communication (eg with the wireless protocol). The wireless field devices may communicate with one or more other nodes that are not configured for wireless communication 40 - 46 a wireless gateway 35 use that with the backbone 105 connected is. Of course, the field devices 15 - 22 and 40 - 46 correspond to any other desired standard or protocol, e.g. Wired or wireless protocols, including standards or protocols developed in the future.

The wireless gateway 35 is an example of a provider device 110 to access different wireless devices 40 - 58 a wireless communication network 70 offers. The wireless gateway 35 In particular, provides a communication link between the wireless devices 40 - 58 and other nodes of the process control network 100 (including the control unit 11 in 1A ). The wireless gateway 35 provides a communication link, in some cases through the routing, buffering and timing services, with lower levels of the wired and wireless protocol stacks (eg, through address translation, routing, packet segmentation, prioritization, etc.) during one or more shared levels tunnel the wired and wireless protocol stacks. In other cases, the wireless gateway 35 Translate commands between wired and wireless protocols that have no shared log levels. The wireless gateway 35 In addition to protocol and command conversion, it can provide synchronized timing, which can be obtained from time slots and superframes (sets of equally spaced communication time slots) of a scheduling scheme for the wireless network 30 implemented wireless protocol is used. In addition, the wireless gateway 35 Network management and administrative functions for the wireless network 70 provide, for. Resource management, performance tuning, network error mitigation, traffic monitoring, security, and more. ä.

The wireless field devices 40 - 46 of the wireless network 70 can be like the wired field devices 15 - 22 physical control function in the process plant 10 execute, for. For example, opening or closing valves or measuring process parameters. The wireless field devices 40 - 46 however, they are for communication using the wireless protocol of network 70 configured. Therefore, the wireless field devices 40 - 46 , the wireless gateway and the wireless nodes 52 - 58 of the wireless network 70 Producers and consumers of wireless communication packages.

In some scenarios, the network can 70 Wired devices included. For example, a field device may be 48 in 1A by an older 4-20 mA device and a field device 50 to trade a conventional WiredHART device. The field devices 48 and 50 can for communication on the network 30 via a wireless adapter (wireless adapter, WA) 52a or 52b with the wireless communication network 70 get connected. The wireless adapters 52a and 52b Other communication protocols, eg. B. Foundation ^® Fieldbus, PROFIBUS, DeviceNet, etc. support. In addition, the wireless network 30 one or more network access points 55a and 55b contain. These can be their own physical devices that are wired to the wireless gateway 35 communicate, or they can as an integrated device with the wireless gateway 35 to be provided. The wireless network 70 can be one or more routers 58 included to packets between wireless devices in the wireless communication network 30 forward. The wireless devices 32 - 46 and 52 - 58 can over the wireless connections 60 of the wireless communication network 70 with each other and with the wireless gateway 35 communicate.

1A Thus, it contains several examples of provider devices that are primarily used to provide network routing and management functions to various networks of the process control system. For example, include the wireless gateway 35 , the access points 55a and 55b as well as the router 58 Functions for routing wireless packets in the wireless communication network 70 , The wireless gateway 35 performs traffic management and administrative functions for the wireless network 70 off and routes traffic between wired networks that have a communication link with the wireless network 70 feature. The wireless network 70 may use a wireless process control protocol that supports process control messages and functions, e.g. Eg WirelessHART.

In certain embodiments, the process control network may 100 other nodes included with the backbone 105 connected and using other wireless protocols communicate. Example: The process control network 100 can have one or more wireless access points 72 contain other wireless protocols, such as B. WiFi, or others with IEEE 802.11 compliant WLAN protocols, mobile communication protocols, eg. For example, WiMAX (World Wide Interoperability for Microwave Access) or LTE (Long Term Evolution), or other International Telecommunication Union Radiocommunication Sector (ITU-R) compliant protocols, shortwave radio communications such as Near Field Communication (NFC) and Bluetooth or other wireless communication protocols , The wireless access points 72 usually allow communication from handheld computers or other portable computers over an appropriate wireless network that is not compatible with the wireless network 70 is identical and a different wireless protocol than the wireless network 70 supported. In some embodiments, the UI device communicates 112 using a wireless access point 72 via the process control network 100 , In some scenarios, portable computers may also have one or more process control devices (eg, control unit 11 , Field devices 15 - 22 or wireless devices 35 and 40 - 58 ) also using the access point 72 supported wireless network.

Additionally or alternatively, the provider devices may have one or more gateways 75 and 78 to systems outside the immediate process control system 10 contain. In such embodiments, the UI device may 112 be used to control and monitor these external systems or for other communication with these systems. These systems are usually customers or suppliers of information provided by the process control system 10 generated or processed. For example, a plant gateway node 75 a communication link between the immediate process plant 10 (which has its own backbone 105 for process control data) and another process plant that has its own corresponding backbone. In one embodiment, a single backbone 105 be used for multiple process plants or process control environments.

In another example, the attachment gateway node 75 Establish a communication link between the immediate process plant and an older process plant or plant on the state of the art, neither a process control network 100 another backbone 105 contains. In this example, the attachment gateway node 75 Messages between one from the big data process control backbone 105 the plant 10 convert or translate the protocol used and a protocol used by the legacy system (eg, Ethernet, Profibus, Fieldbus, DeviceNet, etc.). In such an example, the UI device may 112 used to control and monitor systems or networks in the prior art or in the prior art process plant or for other communication therewith.

The provider devices can have one or more gateway nodes 78 for external systems, to provide a communication link between the process control network 100 and the network of an external public or private system, e.g. A laboratory system (eg, Laboratory Information Management System, LIMS), an employee tour database, a product inventory control system, a production planning system, a weather data system, a shipping cost system, a packaging system, the Internet, the network of another supplier's process control system, or the network of other external systems. The gateway nodes 78 For external systems z. This allows, for example, communication between the process control system and employees outside the process plant (eg employees at home). In such a case, an operator or service technician may use the UI device 112 use at home and over the home network (not shown), the internet and the gateway 78 a connection to the backbone 105 produce. In another case, an operator or service technician may use the UI device 112 use at any location and via a mobile network (not shown), the Internet and the Gateway 78 a connection to the backbone 105 produce. The gateway nodes 78 can also enable communication between plant personnel in the process plant and instances or persons outside the process plant. For example, a technician performing maintenance on a process control device in the process plant may have his UI device 112 communicate with a representative of the process control device manufacturer. In another example, the monitoring module 106 monitor the weather, track incoming replenishment deliveries, track financial data (eg, commodity futures transactions, etc.), schedule work items, manage production schedules, etc. through the monitoring module 106 to facilitate. Of course, all over the gateway 78 (or the gateway 75 or between any two devices) secure connections (e.g., encrypted connections, connections behind a firewall, etc.).

1A Although only shows a single control unit 11 with a limited number of field devices 15 - 22 and 40 - 46 however, the figure is merely illustrative, and is an unrestricted embodiment. To the provider devices of the process control network 100 can be any number of control units 11 be included, and each of the control units 11 can work with any number of wired or wireless field devices 15 - 22 and 40 - 46 communicate to a process in the plant 10 to control. In addition, the process plant 10 any number of wireless gateways 35 , Routers 58 , Access points 55 , Wireless Process Control Communication Networks 70 , Access points 72 and / or gateways 75 and 78 contain.

1B is a block diagram showing a broader control system 120 which may contain a variety of different systems or system functions. The control system 120 Contains the process plant 10 which may, for example, be an oil refinery (but also a completely different one). The system 120 can with underwater systems 122 , z. As drilling or research systems connected. In the system 120 can also use different security systems 124 , z. B. Fire and gas systems 126 , Surveillance systems 128 and transport systems 130 (eg for the transport of oil to the refinery). True, in 1B each of the elements 10 and 122 - 130 each as a separate aspect, however, different of these aspects can be combined. For example, in some embodiments, the process plant 10 the security systems 124 and / or the fire and gas systems 126 contain. 1B is intended to illustrate that the present description is not intended with respect to 1A described procedural system is limited and also to other control, monitoring, security systems u. Ä. Can be applied. This document describes embodiments with regard to the process plant 10 However, this is only for the sake of simplicity and should not be construed as a limitation.

In the following examples, various scenarios of implementing a process plant such as B. the process plant 10 describes the benefits of these implementations.

example 1

A first user assigned to a particular area of the facility oversees it via a fixed workstation in a control room. The first user monitors and controls the process through a browser or other application running on the workstation, and the browser or application communicates with a routine running on a server. The first user goes into the hall of the process plant, z. To inspect them. As the user moves from the control center to the facility, he / she takes along a touch-sensitive tablet (i.e., a second, mobile UI device). The tablet, like the workstation, provides the user with access to the routine on the server through a browser or an application running on the tablet. The first user is already authenticated on the tablet, or the tablet is associated with the first user. The tablet communicates with the server to set up an individual session for the first user. The server stores status information associated with the first user on the workstation and provides a user interface for the first user on the tablet via the browser or the application on the tablet according to the stored status information. This allows the first user to continue the workflow started on the workstation.

Under certain circumstances, a routine running on the mobile device generates a route for the first user. The routine, perhaps working with the expert and / or monitoring system, identifies asset inventories that need to be monitored or maintained. In some cases, each inventory that needs to be monitored or maintained is assigned a priority that indicates the urgency of monitoring or maintaining the inventory. The routine determines a route for the first user that enables the user to efficiently visit at least some of the inventory that needs to be monitored or maintained.

As the first user moves in the facility, a context sensitivity routine running on the tablet receives data from various sensors and receivers (eg, an NFC or RFID transceiver) on the tablet. The sensors and receivers detect devices, equipment and / or tags near the tablet. In other embodiments, the tablet may be a GPS receiver for positional data uploaded to the server for execution by the routine, taking into account the user's position. In either case, the routine identifies the position of the tablet or its proximity to particular devices and causes the tablet to display to the user an outline map / graphic of the process plant, the position of the first user and tablet being magnified. As the first user moves around the plant, the display of the plant's map dynamically changes to accommodate the To display the area of the map that corresponds to the position of the tablet.

In some cases, the map of the attachment may contain navigation features. Example: The first user selects a specific area / inventory / device of the plant as the destination. The routine then uses position data (eg, from a GPS receiver) to provide directions to that area / inventory / device of the facility.

The tablet can also display various process data or alarms while the first user is in the attachment 10 emotional. For example, the first user passes a pump and this causes the tablet to display operational data, graphics, and alarms for the pump, especially when the pump needs servicing. For example, the tablet may display a unique ID from an NFC or RFID tag on the pump or near the pump. The tablet can transmit the unique ID to the routine through the server. The routine receives the unique ID and accesses a database in which the unique ID elements in the process plant are assigned. For example, the unique ID may be the pump data, e.g. As display data, parameter data and alarm data of the pump, be assigned. After the routine has identified the pump data, it can send it to the tablet, which then generates graphics and provides graphics, parameters and / or alarms related to the pump.

In another example, the first user recognizes that the pump is malfunctioning. The first user interacts with a pump graphic or pump menu on the tablet display, taps the display position on the graphics position, and the graphic represents a shutdown command. The tablet recognizes the input of the first user (eg, entering on a capacitive) Touchscreen) and generates corresponding input data. The tablet then transmits the input data to the server, which receives it and sends a shutdown signal to the pump control unit. The control unit receives the signal and turns off the pump. The first user can create a task or work item for the pump. The work task may be, for example, a request to service personnel to inspect and / or repair the pump.

The routine on the tablet may also enable a blocking / power-off procedure. For example, the routine may indicate the appropriate blockage / power-off procedure for the pump. In some cases, the first user who wants to block the pump for security may interact with a to-do list displayed on the tablet, for example: For example, to indicate that a task has been completed in the blocking procedure. In other cases, the user may interact with the routine to test a failure safety condition for the pump. For example, a simulated signal may be generated to simulate the fault safety condition so that the first user can observe the response of the pump.

Example 2

The first user, who still carries the tablet, goes from the process plant to a control center of the process plant. The first user passes a steam boiler. When the first user gets near the boiler, the tablet makes an RFID connection with a boiler context ID device. The tablet receives a unique ID from the Context ID device and submits it to the server. The server identifies the boiler based on the unique ID. The server accesses the context data to determine that a work task is associated with the boiler and compares a qualification threshold associated with the work task with a qualification level associated with the profile of the first user. The server determines that the first user does not have the qualification to edit the work task associated with the boiler and refrains from changing the display of the tablet instead of updating the display with information about the work task.

The user continues to move in the system, still carrying the tablet with him and passing a valve. As described above, the tablet can connect to a valve context ID device. The tablet then receives a unique ID from the device and sends it to the server. The server identifies the valve based on the unique ID. The server then accesses context data to determine that the valve is assigned a schedule according to which the valve is currently decommissioned for maintenance. The server transmits the data to the tablet. This causes the tablet to provide information to the first user from whom the first user sees that the valve is currently being serviced on schedule.

Example 3

The first user continues to move in the system and still holds the tablet in his hand. A second user, who is in the control center and is now logged in to the workstation that was previously occupied by the first user (or at another workstation), determines that a critical oxygen reading for a blast furnace shaft is decreasing. The second user creates one Task requesting help for the blast furnace shaft. When the first user passes through the blast furnace shaft on his way back to the control center, the tablet automatically connects to a blast furnace context ID device so that the tablet receives a unique ID for the blast furnace shaft. The tablet transmits the unique ID to the server, which returns information associated with the unique ID (eg, information about the blast furnace shaft), including a notification graph stating that the blast furnace shaft requires action. The first user sees the notification graph and selects it to display information about the created work item. The first user selects a graphic to indicate the acceptance of the work item.

The work task requires the first user to take one or more pictures of the flame at the blast furnace (eg, because the color of the flame indicates inadequate air flow). The image of the flame is transmitted to the server. A routine executed on the server, in a big data system or as part of an expert system analyzes aspects of the image or compares the image of the flame with other images taken at other times and / or conditions and in big data System are stored. The analysis routine analyzes the images (for example, by comparing images with the collection of previous flame images and the corresponding operating data). The big data analysis routine indicates that the airflow at the blast furnace is too low. The expert system, based on the analysis, instructs the first user to increase the airflow to the blast furnace. In some embodiments, the user uses the tablet for retrieving and displaying work instructions to increase airflow to the blast furnace, and in embodiments, the tablet automatically displays the instructions when the expert system prompts the user to increase the airflow. If necessary, the user may take another image of the flame after the correction and send the image to the analysis routine to verify that the blast furnace shaft is operating correctly.

The first user can also use the tablet to create an audio record of the blast furnace and send it to the server, big data system, or expert system. For example, an analysis routine executed on the expert system compares the audio recording with a sound image of the blast furnace to determine if the blast furnace is operating smoothly. The analysis routine can also compare the audio recordings with audio recordings for known problems. For example, belt or engine problems may be associated with particular sounds, and the analysis routine may detect such problems by comparing the audio record to these sounds. The user may also place the tablet at or near the blast furnace to determine mechanical vibrations of the blast furnace. The tablet receives vibration data via a motion sensor and transmits it to a server or big data system. An analysis routine compares the detected mechanical vibrations with a characteristic vibration level of the blast furnace (or with vibration levels of known problems) to determine if the blast furnace is operating smoothly. By analyzing the audio recording / mechanical vibrations, no further problems with the blast furnace are recognized and / or the analysis confirms that the air flow at the blast furnace has to be increased.

As the first user increases airflow at the blast furnace, the second user queries the blast furnace to determine if in the past past shifts other users have also increased airflow. The query confirms that this is the case. The second user calls up a graph showing airflow in the blast furnace with event data about each time the airflow was increased, the user who made the changes in the big data system, and so on. The second user informs the first user of this information, e.g. By requesting a common UI session (user interface, user interface). The first user receives the request for the UI session through the server. When the first user accepts the request, the server acquires status information about the UI displayed for the second user and causes the tablet used by the first user to display data corresponding to the status information from the second user. The first and second users jointly review the blast furnace data and find that the blast furnace often encounters similar problems. The second user then polls the big data system for measurements of low oxygen levels at the blast furnace. The big data system provides data on a series of events, devices, users, times, and other factors that correlate with measurements of low blast furnace oxygen levels. For example, big data analysis may show that measurements of low oxygen levels have a strong correlation with events in related engineering units, with the correlated events often occurring before the low oxygen levels. In another example, the analysis yields that the measurements of low oxygen levels are highly correlated with a particular user. In other words, the analysis shows that this user is the blast furnace in a way that causes low oxygen levels. While this example illustrates a user who uses a UI device to request analysis and display of the analysis results; however, it should be noted that even the big data system can use data collected by the UI device (in this scenario a tablet) for further analysis, which need not necessarily be associated with the UI device. In either case, the second user can mark the work item for further review and create a maintenance ticket to check the blast furnace in the near future.

Example 4

Later, the blast furnace is inspected by maintenance personnel who determines that the cause of the failure is a location where the fuel supply line is connected to the blast furnace. The maintenance person creates a work item to fix the problem. With the task is the task linked to weld the fuel supply pipe to the fuel supply to the blast furnace. The task specifies the target equipment (the blast furnace) and the qualification required to complete the task (qualification for welding). Optionally, a deadline for the execution of the work task can be specified in the work task.

The monitoring module plans the execution of the work task. For example, the monitoring module may schedule the execution of the work task for a day on which the plant (or the area of the facility where the blast furnace is located) is scheduled for maintenance. The monitoring module may alternatively or additionally schedule the work task according to the availability of staff with the required qualifications. After the monitoring module has identified a welder with the appropriate qualification, it assigns the task to the welder and waits for the welder to accept the assigned work task. When the welder accepts the work item, the monitoring module creates permission tokens that give the welder access to the required equipment features and equipment at the time the work item is to be executed.

The welder arrives at a designated time in the equipment room with the mobile UI device assigned to him, which reminds him of the work task to be performed (i.e., the welding of the blast furnace connection). After acknowledging the reminder, the UI device displays a work item checklist generated by the monitoring module. The welder will see from the checklist that he has safety equipment (eg welding helmet and welder gloves), welding equipment (eg a welding power source, electrodes, filler material, etc.) and other objects needed to do the job (e.g. Spare parts). The checklist may also list specific tasks that must be performed before the welder goes to the target equipment. Once the welder has confirmed to the monitoring module (eg, via the UI device) that he has the full set of equipment listed in the checklist and performed the tasks specified in the checklist, he can leave the equipment room.

The UI device detects that the welder has left the equipment room, enters the map or navigation mode, and displays information about the position of the welder in the process plant and information that guides the welder to the target equipment (in this case the blast furnace) , When the UI device notices that the welder has reached the blast furnace, it automatically displays work task instructions (such as provided by the monitoring module). For example, the UI device may first display to the welder the safety instructions and information required to safely perform the work task, e.g. B. Information about the normally transported from the fuel pipe to be welded material, which material has flowed through the last pipe, whether the pipe has been emptied, whether the pipe is currently in operation and whether residues can be found in the pipe. The UI device may also display, step by step and / or in graphics, a work instruction for removing residue from the pipe to ensure that the welding operation can be performed safely (eg, without causing an explosion). The UI device may also include instructions for shutting down and / or blocking parts of the system, e.g. For example, upstream valves that allow the flow of gas into the pipe, igniters in the blast furnace, and other equipment that expose the process, welder, or process equipment to unnecessary risks, enable shutdown / stall. The welder then carries out the welding process. He follows the instructions or other instructions provided by the UI device before suspending any blocks that may be present and telling the monitoring module through the UI device that the process is complete. The monitoring module then automatically creates a work item so that a second person checks the welding work before putting the system (or a section of the system) back into service.

These examples illustrate some advantages of the systems, devices, and methods described in the remainder of this specification.

It is envisaged to integrate the concepts described here into systems that are already implemented in the process plant. This means that the implementation of these concepts in embodiments does not require a completely new process control system, but that the concepts can be seamlessly integrated into existing software and hardware elements of the plant.

The big data network

In certain embodiments, the disclosed UI devices, servers, and routines are implemented in a process control network that supports a big data infrastructure (eg, a big data network). The big data network supports data mining and data analysis of extensive process data. The big data network or system may also contain a plurality of big data network nodes to capture and store all (or almost all) data from devices operating in the process control system or in the process plant 10 are included, linked to, generated, received and / or observed. A big data network can be a big data system (for example, the big data system 102 ) contain. This, in turn, may include a unified, logical data storage area configured to store multiple types of data (sometimes in a common format) generated by the process control system or with the process control system, the process plant 10 and one or more of the process plant 10 related processes. In the uniform, logical data storage area z. Timestamped configuration data, steady state data, asset data, user action data, network management data, and data supplied from / to systems outside the process control system or process plant. This data may also include employee, commodity and / or processed product data, employee limitations, qualifications and certifications, calibration and maintenance schedule data, and the like. Ä. Include. The data collected by the big data network may be, for example, data logs that record the employees and the inputs received from these employees. This data can be helpful in improving plant operation and efficiency. The log data can be z. B. be searched and analyzed by the expert system to gain valuable insight into operator input in different situations. The results can be used to improve operator training and / or responses - automatically or manually - in different situations. In any case, these data are often required for regulatory purposes.

The word "uniform" in relation to the logical data storage area of the big data system 102 For the purposes of this application, this does not mean that it is a single storage device. As is well known, multiple (in fact numerous) memory devices of a particular size (or various sizes) can be connected to form a larger memory area. In the context of this description, these storage devices can nevertheless be regarded as a "uniform" logical storage area. In general, this is the big data system 102 for receiving data (eg, by streaming and / or other protocol) from the Big Data network Big Data network nodes and storing the received data. The big data system 102 The process control may include the unified logical storage area for archiving or storing the data received from the big data nodes, a plurality of system data receivers for receiving the data, and a plurality of system request services. The latter are described in U.S. Patent Application 13 / 784,041, which is hereby incorporated by reference in its entirety and throughout this document.

A process control Big Data system can automatically capture all data generated, received, or retrieved by the nodes at the rate at which they are generated, received, or retrieved. It may cause the captured data to be leaked to the big data system with high accuracy (eg, without the use of lossy data compression or other methods that may cause the loss of original information) 102 of the process control system to be stored (and optionally transmitted to other nodes of the network). The process control system's big data system may also be able to provide sophisticated data and trend analysis of any portion of the stored data. For example, the process control big-data system may provide automatic data analysis of process data (contained in prior art process control systems in various database silos) without requiring a priori configuration, translation or conversion. The process control system's big data system enables automated, thorough knowledge acquisition and can suggest changes to the process control system or additional elements for it. The process control system's big data system may alternatively or additionally perform actions based on knowledge acquisition (eg, regulatory or predictive maintenance, or both regulatory and predictive maintenance). The big data system of the process control system also enables Assist users in manual knowledge acquisition and planning, configuration, operation, maintenance and optimization of the process plant and its associated resources.

expert system

The expert system 104 is a collection of routines and / or modules that is configured to access and analyze data that is in the big data system 102 are stored. The expert system 104 Although described throughout the specification as a module that in the embodiments of the big data system 102 is disconnected, however it can be in the big data system 102 to get integrated. The expert system 104 may also include a variety of modules or routines executed in different process areas and / or in different process equipment. For example, the functionality of the expert system may be in one or more control units 11 in one or more process control systems 15 - 22 etc. are located. The expert system 104 always uses the big data system 102 collected and stored data to determine trends, perform diagnostics, monitor operator inputs, improve the modeling of the process plant and / or parts of the process plant, monitor output quality and quantity, various aspects of plant operation model and perform countless other activities. The expert system 104 may use predefined models to analyze the collected data and / or actively (and possibly automatically) generate models according to the analysis of the data. The expert system 104 can do many different types of analysis. Some examples are described below. The examples should not be the functional scope of the expert system 104 but illustrate some of the possible functions.

In one example, the expert system monitors 104 (in real time or after capture and storage) data from the big data system 102 captured and stored, and analyzes data for a particular alarm or alarm type. The expert system 104 Can be used to analyze the process parameters, process inputs, sensor data and everything else in the big data system 102 stored data to determine common features (trends, values, etc.) associated with a particular alarm. The assignment can be a time allocation, but the feature does not have to occur at the same time as the alarm. For example, the expert system 104 analyze the data to determine if a particular operator input occurs with a similar temporal relationship to the alarm. More precisely, the expert system 104 determine a common occurrence of several factors that precede or otherwise suggest the alarm condition. So can the expert system 104 For example, determine that the pressure in a particular container increases at a certain rate and causes the alarm condition when the temperature in the container increases and an operator puts a certain amount of catalyst into the container.

In another example, the expert system 104 to perform statistical analysis by the big data system 102 recorded and stored data programmed to determine the strength of the correlations between events and process parameters. For example, an operator with many years of experience may judge the relationships between different processing units according to their "gut feeling," but the operator's intuition is probably less reliable than a thorough analysis of the data. This may result in the operator responding to a process control situation (eg, increasing tank temperature, falling pressure, etc.) by changing process settings that aggravate or not correct the situation as quickly or to the extent that others have or additional corrections would be made. The expert system 104 Therefore, it can improve the overall control, security, quality, and output of the process by providing information to operators and other employees that would otherwise be unknown or unintelligible.

In yet another example, the expert system 104 programmed so that it according to the analysis (for example, according to the analysis described in the preceding sections) corrections to that in the process plant 10 carried out process. The expert system 104 detects a suboptimal or abnormal condition and corrects it by changing one or more process inputs and / or setpoints. The expert system 104 can also be used in other safety systems of the process plant 10 be integrated to stop and / or correct process conditions that could lead to safety risks for equipment and / or personnel.

monitoring module

Implementation of the mobile control center using the UI devices 112 facilitates the decentralization of control, maintenance and other aspects of the process plant (or other, similar environments). The operators are no longer tied to a workstation for optimal control of the process plant. As a result, the separation between operators and maintenance workers, who had previously worked in the plant rather than in the control center, blurs or disappears. There are more employees available who can move in the plant environment. At the same time, the Big Data system stores 102 more complete data about every aspect of the plant environment, and the expert system 104 provides more comprehensive analysis of the operation and condition of the process plant. The expert system 104 and the big data system 102 provide together information on the status of the processes running in the plant, the status of equipment in the plant, the positions and responsibilities of plant employees, and countless other aspects of asset management, materials management, human resource management, optimization, etc.

The monitoring module 106 uses the expert system 104 provided data and analysis for the steering of the employees in the process plant. In particular, the monitoring module 106 from the expert system 104 Monitor identified trends and create work tasks for the plant personnel. The monitoring module 106 Although described throughout the specification as a module, the Big Data system 102 and the expert system 104 However, in embodiments, it may be in the big data system 102 and / or the expert system 104 to get integrated. 2 Figure 4 is a block diagram of the communication architecture between the mobile UI devices 112 the control center, the monitoring module 106 as well as the expert system 104 and the big data system 102 , As described above, the expert system 104 Retrieve and analyze data in the big data system 102 stored, and in some embodiments, data in the big data system 102 to save. For example, the expert system 104 Retrieve data about one aspect of the process control system and perform one or more analyzes of the retrieved data. The expert system 104 may perform the analyzes on a pre-programmed model or in some embodiments without a model (ie, the expert system 104 searches in the data for unknown correlations and relationships). In any case, stores the expert system 104 Analysis data (such as regression data, correlated data, etc.) in the big data system 102 ,

The monitoring module 106 uses data from the expert system 104 and / or the big data system 102 received / retrieved. For example, the monitoring module 106 Data from the expert system 104 which indicate that a particular parameter is particularly closely correlated to a particular abnormal condition or optimal condition. In another example, the monitoring module receives 106 Data from the expert system 104 that indicate that a particular parameter should be checked or that a particular correction be made to a process control device / routine to avoid an abnormal condition. In yet another example, the monitoring module receives 106 Data from the expert system 104 that specify the expert system 104 has identified a trend that indicates maintenance is required now or at a predicted time. Alternatively or additionally, the monitoring module receives 106 Data from the big data system 102 , For example, one from the monitoring module 106 routine is related to regular scheduled maintenance (ie maintenance at regular scheduled intervals or at intervals determined by a parameter of the installation). This means that the monitoring module 106 monitors a parameter of the process plant or device in the process plant, for example, to determine how many hours since the last maintenance the device was in operation or how many times the device has been turned on since the last maintenance. This type of data can be in the Big Data system 102 stored and from the monitoring module 106 be received.

Creation of work tasks

The monitoring module 106 uses the received data to create work tasks for plant personnel and / or to trigger specific actions in the process plant. 3 is a block diagram illustrating an embodiment of the monitoring module 106 represents. The monitoring module 106 can be a work item manager 300 contain. At the work item manager 300 It may be a set of routines and / or instructions stored on a computer-readable medium, executed by a processor, and used to create work items. Each task may be a task or procedure that must be performed by one or more process plant operators. For example, a work task may include replacing or repairing a device, detecting a parameter value, making a setting on a device or parameter, checking an equipment or device, or any other action that requires personnel to perform. If the work item manager 300 Work items are generated in a work item list 302 stored in a the monitoring module 106 associated memory is located. As in 4 shown can be an example work task 400 contain a variety of information, such as a work type or a function 402 (eg, debugging a circuit, replacing equipment, calibrating equipment, maintenance (eg, lubrication, etc.), etc.), a list 404 with equipment required to perform the work task, a target equipment field 406 indicating the equipment to which the work relates, a target start date / time 408 , a target finish date / time 410 , a priority field 412 (eg "immediately", "within 12 hours", "within 24 hours", "according to current charge", "during next shutdown", "high", "medium", "low" etc.) , a field 414 for the required qualifications and / or a field for a required certificate (not shown) and a field 416 for the target equipment type. Of course, in the work task 400 less or more fields are included.

As in 3 shown, the monitoring module 106 also a sentence 304 of employee profiles 306 contain. Each of the employee profiles 306 Contains information about a specific operator, service technician, or other plant employee. The information in a staff profile 306 may record qualifications, certifications and / or credentials, roles (eg, operator, maintenance, safety), work time / work schedules, tour schedules (eg, regular and / or scheduled tours of employees in the facility to record parameter data or Include visual inspections of aspects of the process plant) and / or other information relevant to the performance of various tasks in the process plant.

Workflow Management

A work item scheduler 308 can be stored as a set of instructions on a computer readable medium. The instructions can be executed by a processor to schedule the work items in the work item list 302 perform. The work item scheduler 308 can plan work tasks based on a variety of factors. For example, the scheduling can be based on the following factors: The work item scheduler 308 plans work tasks based on the priority of the individual work tasks; the number of personnel scheduled to be in a position ("target position") near any equipment ("target equipment") to which the work relates; Based on the personnel currently at the target location near the target equipment, based on the current availability of personnel (eg, personnel in whose shift the desired time to start / finish the task is or will lie, and / or personnel who has not been assigned other tasks at the desired time to start / finish the work task); based on the required / desired qualifications, roles, certifications and / or certificates of personnel; based on maintenance schedules and / or shutdown schedules, etc. The Work Scheduler 308 may include, for example, the work items in the work item list 302 track and record the target positions and / or target equipment associated with the individual work items. The work item scheduler 308 can get information from an employee tracking routine 310 received through the UI devices 112 that are tracked by employees tracking employee positions. When the employee tracking routine 310 reports that a mobile operator is near a target location or equipment (eg, by determining the employee who is on a UI device 112 whose location is known, logged in or the UI device 112 is assigned), the work item scheduler 308 the employee profile 306 of the mobile operator to determine if the mobile worker has the qualifications and / or credentials required to perform the task associated with the work item ("objective function"). If the mobile employee has the appropriate qualifications and / or credentials, the Work Item Scheduler assigns 308 the work task to the mobile operator. When the worker accepts the work item, the work item scheduler creates it 308 any necessary permissions to allow the operator to perform the target function on the target equipment. Of course, one or more people can be assigned to a single work task because multiple people are required to perform certain tasks.

In embodiments, the permissions are called tokens or entries in a database 312 created in a the monitoring module 106 associated memory is located. Each authorization token defines the objective function (eg, the circuit debugging) in the target equipment, the worker's ID (s) assigned to the task, and optionally the expiration date and time of the token. Authorization tokens may be required for all work items, some work items, or work items that are associated with specific equipment or equipment types, with specific objective functions (ie, tasks within the work item), and so on. The permission token grants the mobile workforce assigned to the work item specific access rights and can be revoked at any time by the system. In some embodiments, entitlement may also depend on external factors. For example, a permission token may indicate that a mobile worker has the authority to perform an objective function during a particular period of time, during a particular plant event (eg, during shutdown of an area of the facility), and so on.

In addition, the monitoring module 106 and in particular the work item scheduler 308 Plan work tasks according to external factors, especially (but not exclusively) when the work tasks result in changes to the production schedule or significant downtime. For example, the monitoring module 106 over the backbone 105 and the gateway 78 Communicate with systems outside the actual process plant to obtain weather, raw or other supplies, supplies of parts, tools, or equipment necessary for the execution of the work task, product shipping schedules, and the like. Ä. Be required. For example, the work item scheduler 308 delays the scheduled execution of a work task if it hinders production and, according to schedule, receives a supply of perishable raw materials before the work task can be completed. In another example, a particular job at an outdoor location requires dryness (ie, no rain) for the objective function (eg, circuit debugging) to be performed and the work item scheduler 308 plans a work task according to the weather forecast.

In a flowchart in 5 is a procedure 500 to assign tasks to employees in a process plant. the procedure 500 can receive data from an expert system (block 505 ) and creating a work item defining a task corresponding to the data received from the expert system (block 510 ). the method may also include selecting a person to perform the task specified in the work item (Block 515 ), sending the work item to a device that is assigned to the selected person (Block 520 ), and receiving the information that the selected person has accepted the work task (Block 525 ). Receiving data from the expert system may include receiving data indicative of a predicted problem in the process plant, receiving data indicative of a trend for a process parameter, receiving a request to provide a parameter value to the expert system, receiving a Instruction for performing a specific action with respect to a process control device and the like. Ä. Include. While receiving data includes receiving a request to provide a parameter value, creating the work task may include creating a work task that includes the task of monitoring and recording a parameter value that is not automatically transmitted by a device that is transmitting the task Measured by sensor or otherwise receives the parameter. Creating a work item in embodiments includes creating a work item in which the defined task is performing a maintenance task, a calibration task, a replacement task, an inspection task, or a repair task. Creating a work item may also include specifying a finish item (eg, a piece of equipment for which the specified task will be performed) for the specified task. Selecting a person to perform the task may include selecting a person according to the location data associated with a device associated with the selected person (eg, a mobile UI device, a GPS device, a device with PICC card, etc.). ) are received. The procedure 500 may also include creating and storing a permission token associated with the specified task, a process control device associated with the specified task, or both. The permission token is required to allow the selected person to perform the specified task for the process control device associated with the specified task. The permission token may be an entry in a database, a single file, or any computer construct that is implemented to create and / or grant the authority for a person to perform an action on a piece of equipment. Selecting a person to perform the task may also include selecting a person according to the task specified in the task, according to a process control device associated with the task specified, or both, and according to multiple employee profiles accessible to the monitoring module. In embodiments, selecting a person according to multiple employee profiles includes selecting a person according to qualifications, a role, a certification, and / or a certificate. Selecting a person may also or alternatively include storing the work item in a database from which employees select a work item to perform, and / or receiving a request from a device associated with a person to perform the task and having a profile associated with the person Compare the work item stored information to determine if the person meets the requirements to perform the task.

Receiving data from the expert system may include receiving an instruction to perform an action, e.g. Monitoring and recording a parameter, reviewing a process control device, calibrating a process control device, creating an audio record, capturing an image or video, performing maintenance on a process control device, repairing a process control device, replacing a process control device, and / or setting a process control parameter. Creating a work item may include specifying tools or equipment needed to perform the specified task, a task priority level, required skills to perform the specified task, a required start time, and / or a required start date and / or end time and / or a required end date. The procedure 500 Also, scheduling the execution of the work task according to a planned route in the process plant associated with the selected person may predicted a scheduled delivery of inputs to a process executed by the process plant, a scheduled delivery of a product produced by the process plant Weather conditions, a scheduled shipping time of a product produced by the process plant, a predicted or planned completion time of a process plant process and / or a predicted or planned arrival of tools, equipment or parts needed to perform the specified task.

As in 3 shown, the monitoring module 106 also documentation, z. B. Equipment Manuals, Service Manuals and Standard Operating Procedures (SOPs) 316 save (or otherwise have access to). The documentation is about the UI devices 112 automatically provided to the mobile operators as these tasks perform tasks associated with the process plant or certain work items. In embodiments, at appropriate (ie, meaningful) times during the execution of an objective function associated with a work item, documents are provided to the mobile operators. For example, for personnel executing a function associated with a work task to debug a circuit, a standby operation statement for debugging the circuit may be displayed. In another example, for personnel performing routine maintenance on a valve (eg, lubrication, cleaning, etc.), standard operating instructions for each procedure and / or manual for the target valve are displayed. In some embodiments, each step of executing the objective function provides the relevant portions of the documentation to the employee. This means that for a maintenance technician z. For example, a standard operating instruction for blocking and decommissioning a valve is first displayed (via the mobile UI device 112 ). Subsequently, the pages of the operating instructions of the valve are displayed for the service technician, which describes the cleaning and / or greasing of the valve. Later, the service technician will see a standard operating procedure for restarting the valve and releasing the blockage. Of course, these are just examples of some of the many applications, as there are countless situations in which employees can see standard operating procedures and manuals while performing tasks.

When a mobile operator or technician performs the target tasks associated with a work item, the monitoring module may 106 and in particular a work item tracking module 318 track the progress of tasks associated with the work task. In some embodiments, the monitoring module performs 106 together with the mobile UI device 112 the mobile operator through the individual steps of the process or processes required to perform the work task. The instructions may include blocking procedures, shutdown procedures, disassembly of the device, repair of the device, maintenance steps such as calibration, lubrication, and the like. , debugging and acknowledgment procedures, device remounting, startup procedures, unblocking procedures, and other steps of the process. The work item tracking module 318 can with the mobile UI device 112 communicate and z. For example, information may be received when the mobile operator requests each of the sequential instructions, steps, or instructions. If the work item tracking module 318 receives the information on the request of each successive instructions, steps or instructions, it assumes that the previous step is completed, and thereby follows the execution progress of the work task. In embodiments, the work item tracking module may 318 communicate with the target equipment (ie the equipment for which the work task is intended) or with the equipment that is near or connected to the target equipment to verify that one or more steps have been completed. In another embodiment, two mobile operators work together. When a mobile operator completes the individual steps of the task, via the mobile UI device 112 presented to the technician marks the second technician the individual steps on another UI device 112 as completed and sends to the work item tracking module 318 the information about the completion of each step. That is, for two users using UI devices 112 work together, do not need to display the same display of information, and generally do not need to display the same information. In another example, the first user reads on a first UI device 112 the default worker instructions for performing a work task while another user is running on a second UI device 112 View live data about a piece of equipment associated with the work item. Upon completion of the work task, the monitoring module marks 106 and in embodiments, the work item tracking module 318 the work task as completed, removes it from the list of active work items, removes or terminates all work assignments assigned to the work task, assigns another work item, notifies employees that the work task is complete, notifies employees that a dependent work task (ie Work task, which can only be started when the previous task has been completed) can be started u. ä.

In 6 a flowchart describes a method 600 to control a workflow in a process plant. method 600 includes creating a work item that specifies a task to be performed in the process plant (block 605 ) determines a set of procedures for the execution of the work task based on the specified task (Block 610 ), a corresponding display is generated for each of the procedures in the set of procedures (Block 615 ) and display the set of corresponding displays in succession in the order in which the set of procedures is to be executed on a mobile UI device (Block 620 ). Creating a work item may include receiving data from an expert system and / or specifying a task according to the data received from the expert system. Receiving data from the expert system may include receiving an instruction to perform a particular action on a process control device. Alternatively, creating a work item may include specifying a maintenance task, a calibration task, a replacement task, an inspection task, and / or a repair task. Creating a work item may also include specifying a task that requires a security blocking procedure, a shutdown procedure, and / or a startup procedure, and so on. Generating a corresponding display may include generating a display representing a set of steps for executing the procedure, generating a display containing one or more figures of execution of the procedure, generating a display that includes a figure of a destination equipment item in context its environment includes, to facilitate a person's location of the equipment, generating a display including a parameter input field for recording a parameter associated with a target equipment item, and / or generating a display containing a set of standard operating instructions. The method may also include the figure of the location of a target equipment item in the context of the process plant on a display of the mobile UI device. In doing so, a UI control may be provided to increase the size of the target equipment and / or a set of UI controls may be provided that allow the user of the mobile UI device to navigate within the set of corresponding displays. In some embodiments, a procedure context area is displayed that indicates which procedure of the set of procedures is currently being performed for the specified task. The method may also include providing access to documentation about a target equipment item for the specified task. In addition, the method may include determining a set of tools and equipment required to execute the set of procedures, generating the display of a checklist that includes the list of the specified set of tools and equipment, and displaying the checklist , Generating the work item may include specifying a manual data collection task. Setting a set of procedures may include determining a route to manually acquire the data.

The monitoring module 106 can also store data related to the execution of the work task. In particular, the monitoring module 106 Data that is from one or more mobile UI devices associated with the work item execution 112 Data on the effects of the execution of the work task on the operation of the process plant (eg performance variations of the process plant caused by the execution of the work task or related to its execution) u. Save. In embodiments, the mobile UI devices subscribe 112 video, audio or vibration data as part of a diagnostic, repair or maintenance procedure, and the mobile UI devices transmit the recorded data back to the monitoring module 106 that stores the data associated with the task in question and alternatively or also the data in the big data system 102 stores.

checklists

As in 3 shown, the monitoring module 106 perform additional tasks for monitoring mobile personnel. For example, the monitoring module 106 a checklist generation routine 314 contain. The checklist generation routine 314 generates checklists for mobile personnel according to a work task assigned to mobile personnel. Among the routine 314 generated checklists include, for example, safety equipment (eg, respirators, harness, snap hooks, radiation detectors / dosimeters, etc.) needed for an area or procedure, tools required to perform a procedure, parts necessary to perform the procedure required (eg spare parts or maintenance parts such as seals, lubricants, etc.) u. ä. The checklist generation routine 314 generates the checklist and, in some embodiments, stores it as a checklist associated with the work item. Alternatively, the checklist generation routine 314 Generate and display the checklist in real time. In any case, the intention is to display the checklist just before the mobile work task is performed. For example, the checklist may be automatically displayed to a mobile operator indicating that he is preparing to perform the task. In other embodiments, the checklist is manually requested by the mobile operator as he prepares to perform the task. In some embodiments, the monitoring module determines 106 that the operator prepares to perform the task and automatically displays the checklist for the mobile operator. For example, the monitoring module receives 106 the information that the mobile operator is in the status of a workstation UI device at the time the work task is scheduled to run 112 to a mobile UI device 112 has transferred. If the monitoring module 106 When the status transfer has detected, it displays the checklist, prompting the mobile operator to confirm that they have the appropriate equipment and resources to perform the work task. Alternatively, the mobile UI device 112 retrieve the checklist automatically (eg from the monitoring module 106 ) when the mobile operator opens a work item, preferably before entering the process plant. In another embodiment, the mobile UI device recognizes 112 that it has entered a material or preparation room and automatically displays to the mobile operator the checklist so that he can assemble the necessary tools, equipment and materials.

In 7 a flowchart describes a method 700 to perform a task in a process plant. The method includes receiving a work item selected from multiple work items in a database (Block 705 ), and defining one or more elements of the selected work required to complete the work task (Block 710 ). From the element or elements, a checklist is generated that is to be displayed to a person performing the work task (Block 715 ), and the checklist is displayed to the person performing the work task (Block 720 ). In one embodiment, setting one or more work items from the selected work task includes reading one or more work task fields. This includes reading a field for required equipment, reading a field for required safety equipment, reading a field for required tools, and / or reading a field indicating a location of a destination equipment item in the process plant. Reading one or more fields may involve reading a field indicating a target task to be performed. The reading of a field may include reading a field indicating a target task to be performed and a target equipment or type of target equipment. Determining one or more items required to perform the task may include setting the task to be performed, the equipment for which the task is to be performed, or both. Generating a checklist of one or more items to be displayed to a person performing the work task may include generating a checklist that may include, for example: As a safety equipment, a tool, a process control device, a part for a process control device or a maintenance material or any combination of these elements. Generating the checklist may include retrieving information from one or more equipment manuals for a process control device associated with the work item, a tooling manual for a tool required to perform the work item, a security document, a standard operating statement, and / or a document for a position of a process control device associated with the work item. In embodiments, generating the checklist includes determining one or more locations associated with the task or that must be passed by the dispatched personnel to accomplish the task associated with the task, and retrieving Special safety equipment and / or special tools required for access to the position (s) or passing the position (s). Displaying a checklist for the person performing the work task may include receiving the information that a user who was instructed to perform the work task has activated a mobile UI device and displaying the check list on the activated mobile UI Device for the user. Receiving a selected work item may include receiving the portion on a first UI device, and displaying the checklist to the person performing the work task may be to receive the information that a status of the first UI device is to a second UI Device and display the checklist on the second UI device. method 700 may also include, for each item in the checklist, receiving the information that a person displaying the checklist has the item.

UI devices

8th is a block diagram of a UI device 803 in the context of a mobile control center 800 , The mobile control center 800 allows the UI device 803 transmitting an operational status to a system or device and / or receiving a UI status from another system or device. The mobile control center 800 can also have a UI device 803a , the server 150 and a UI device 803b contain. Each of the UI devices 803 . 803a and 803b may be of a different UI device type, as discussed below in the text 9B described. The server 150 can be a web service or a web routine 152 included in a memory on the server 150 stored and stored by a processor on the server 150 is performed. Each of the UI devices 803a and 803b (and possibly other UI devices 803 ) contains a processor 810 , a store 815 , a display 820 , a network interface 825 , an input interface 830 , a system bus 835 and one or more transceivers 850 , The UI devices 803a and 803 b may also contain one or more location systems, eg. B. a GPS receiver 832 (Global Positioning System, GPS) (or a receiver for any other satellite navigation system), an inertial location system chip 834 independent locating components like a compass 836 , Gyro instruments 838 , Vibration sensors 840 etc. The memory 815 can be an operating system 880 , a UI routine 882 (User interface, user interface), a context sensitivity routine 884 , a status determination routine 886 , a browser routine 888 , an image capture routine 890 , a tone detection routine 892 , a local memory of process control data 894 , UI status information 896 and further data included. In some embodiments, there are one or more instances of the operating system 880 , the UI routine 882 , the context sensitivity routine 884 and / or the status determination routine 886 in a memory outside the UI device 803 and they can be from a processor outside the UI device 803 (eg on a device or system like the server 150 ). It should be noted that the mobile control center described here 800 just an example. Other configurations are being considered. For example, the mobile control center 800 contain neither multiple UI devices nor a specific number of UI devices.

In certain embodiments of the memory 815 of the UI device 803 can the memory 815 include dynamic and / or persistent storage, and may be removable storage or fixed storage. For example, the memory 815 Computer storage medium in the form of RAM (Random Access Memory), ROM (Read-Only Memory), EEPROM, FLASH memory or other storage technology, CD-ROM, DVD (Digital Versatile Disk) or other optical disk storage, magnetic cassettes, magnetic tape, magnetic disk storage or others Magnetic storage devices or any other medium that may be used to store the desired information. The processor 810 is configured to retrieve and execute statements that reside in memory 815 are located. In the storage room 815 can z. B. operating system data or program data are stored.

The network interface 825 may include or be connected to one or more wireless communication antennas, one or more wired connections, or both. In some embodiments, the network interface may be with the GPS receiver 832 be connected, so the network interface 825 Position or coordinate data. The network interface 825 may also or instead include a Bluetooth transceiver, so the network interface 825 PAN (Personal Area Network) with an external device or system. The network interface may also or alternatively include an Near Field Communication (NFC) transceiver, a Radio Frequency Identification (RFID) transceiver, and / or a Local Area Network (LAN) transceiver (with which the network interface 825 for example, using the protocol IEEE 802.11 can communicate).

The network interface 825 can over a network such. B. the in 1A shown process control network 100 with the server 150 and / or one of the UI devices 803 communicate. Users can via the input interface 830 with the UI device 803 communicate. The input interface 830 can accept inputs by mechanical action (eg keyboard or mouse). Alternatively, or in addition, the input interface 830 Inputs by the detection of electromagnetic fields, by signals or properties (eg resistive or capacitive touchscreen) accept. In addition, the input interface 830 Inputs via the detection of sounds, light or movement (eg voice input via a microphone 842 , an image sensor or a camera 844 etc.). In addition, the input interface 830 Accept inputs from a Bluetooth device that is connected to the network interface 825 connected is. the display 820 can provide output in the form of pictures or video and use any type of monitor, projector or display technology, including CRT, LCD, plasma, LED and OLED technology.

In some embodiments, one or more input sources, e.g. B. the microphone 842 , the image sensor or the camera 844 or other sensors (eg, oxygen sensors, poison gas sensors, motion sensors, vibration sensors, RFID sensors) outside the UI device 803 and via wired communication channels (such as a headphone or USB port) or wireless communication channels (eg, wireless USB, Bluetooth, Wi-Fi, or proprietary protocols) with the UI device 803 be connected. For example, a user who owns the UI device 803 It also carries one or more of the input sources on an accessory belt, in a bag containing the UI device 803 transported, etc., with you.

With each of the routines 880 - 896 It may be one or more instructions, routines, modules, processes, services, programs, and / or applications, and may be stored on a computer-readable medium, e.g. B. the memory 815 be saved. The operating system 880 can support the basic functions and the resources of the UI device 803 manage. In particular, the operating system 880 the hardware and software of the UI device 803 manage. If the routine 882 Running from the processor, it can cause the display 820 Information for a user to be displayed and that the input interface 830 Receives inputs from the user or other external pulses. The context sensitivity routine 884 can cause that on the display 820 Information in response to contextual information displayed at the network interface 825 , the input interface 830 or received at one or more sensors. Additionally or alternatively, the context sensitivity routine 884 cause the UI device 803 identifies a context (eg, a location, a time, or a schedule) and / or the context of the system or device outside the UI device 803 receives.

The status determination routine 886 can provide information about the operation of the UI device 803 to capture. For example, the status determination routine 886 UI state information 896 capture it by the processor 810 running processes and monitors the data associated with the processes. The status determination routine 886 can the on display 820 identify the information displayed and process units associated with the displayed information. In some embodiments, the status determination routine 886 the captured UI status information to an external node, e.g. For example, the server 150 or the UI device 803b , transfer. In embodiments in which the UI device 803 implemented a thin client or web client, the status determination routine 886 in a store on the server 150 where they are stored by a processor on the server 150 is performed.

In the browser routine 888 it can be an application for calling and displaying and navigating one or more information resources. An information resource can be a web page, an image, a video, a document, or any other content. The browser routine 888 can use information resources on the UI device 803 or with information resources outside the UI device 803 to interact. For example, the UI device 803 over the World Wide Web or a network like the process control network 100 on information resources on other systems or devices (such as the server 150 or the UI device 803b ) access. In some embodiments, the browser routine may 888 on information with regard to one on the server 150 UI routine and / or information generated by this routine. In particular, the browser routine can 888 on the webservice 152 on the server 150 access, the web service 152 the on the server 150 executed UI routine can correspond. For example, the browser routine 888 an address or an ID, e.g. For example, a Uniform Resource Identifier (URI) or Uniform Resource Locator (URL) is received (eg, from a user via the input interface) 830 ). The address or ID can be the browser routine 888 to the web service 152 conduct. The browser routine 888 can via the webservice 152 UI data, eg. G. Display data or process parameter data, from the UI routine 882 receive, so the browser routine 888 Graphics to control and / or monitor the entire process or part of the process. The browser routine 888 can also receive user input (eg a mouse click on a graphic) and via the webservice 152 Data representing the user input to the UI routine 882 transfer. In alternative embodiments, the browser routine 888 a plug-in or a web client application.

The different routines 880 - 896 are as in the store 815 described routines described. The UI device 803 However, if necessary via the network interface 825 request, retrieve, receive and / or download additional routines (eg applications, applets, updates, patches etc.). In one of many imaginable examples, the UI device requires 112 Information about enabling direct (or indirect) communication between the UI device 112 and a process control device in the process plant and receive such information. In any case, it should be noted that the UI device 112 is not limited to applications, routines, and modules that are in memory 815 and described in this document.

The image capture routine 890 can be over the image sensor or the camera 844 capture an image. In some embodiments, the image is over the network interface 825 to a node in the network 100 which analyzes the image to identify process data. For example, in one embodiment, the image capture routine may be 890 cause the image sensor 844 take a picture of a flame. The image acquisition routine 890 transmits the image of the flame over the network 100 on a node (for example, the server 150 , the expert system 104 etc.), and the node analyzes the image to determine the color and the corresponding temperature of the flame. Accordingly, in the sound recording routine 892 one or more instructions or routines for sound recording via the microphone 842 act. The recorded sound data can be used for analysis on a node in the network 100 be transmitted.

The microphone 842 can record audio data for a piece of equipment. The audio recording can be used for identifying the plant part or for the diagnosis of the plant part. Example: A pump has an expected sound. In such an example, the UI device draws 803 The sounds generated during the operation of a piece of equipment and transmits the audio recording over the network 100 on a node (for example, the server 150 , the expert system 104 etc.) to determine the type of part, e.g. As a pump to determine. Under some conditions, the node may even be the UI device 803 tell which pump it is. The UI device 803 may also include a motion sensor (eg, the vibration sensors 840 ) for detecting vibrations. For example, a plant part may have an expected vibration level during operation. A user can use the UI device 803 place on or near the equipment. The UI device 803 can use the data detected by the motion sensor to identify the current vibration level of the equipment. If the vibrations exceed the expected level, the user can use the UI device 803 Check the system part more thoroughly or request a work task for the part of the system. In some cases, a diagnostic routine will automatically start when the UI device 803 is placed on or near the equipment to determine the vibration level of the equipment.

In some embodiments, the UI device may 803 a peripheral interface (not shown) to connect to other devices. The peripheral interface may be a serial interface, e.g. B. a USB interface (Universal Serial Bus) act. In other embodiments, as in some embodiments of the network interface, the peripheral interface may be a wireless interface for establishing a wireless connection with another device. For example, in some embodiments, the peripheral interface may be a wireless interface for short links, e.g. B. with the standard for Bluetooth (in the frequency band 2400-2480 MHz) or Nahfeldkommunikation (with the frequency 13.56 MHz) is compliant. The peripheral interface may be used to transmit status information to an external device or to receive status information from an external device, as described below. In certain embodiments, the peripheral interface may also be used for interacting with external devices that are for the UI device 803 Provide contextual awareness. For example, a context ID device can be recognized via the peripheral interface, as also described below. In some embodiments, a user may have status or process information displayed on the UI device 803 available via the peripheral interface on an external device.

During general operation of the UI device 803 can the processor 810 on the memory 815 access the UI routine 882 perform. If the processor 810 the UI routine 882 performs, causes the processor 810 the provision of expenses on display 820 where the output is information about units (eg, equipment, equipment, network nodes, process data, control data, etc.) in the process plant 10 represents. The output can be stored in memory 815 (eg graphic data, historical data or any previously received and stored Data) or based on data sent over the network interface 825 received (eg, received data from the control unit 11 or the database 151 ). If also inputs to the input interface 830 can be received, the input interface 830 generate the input data. The inputs can be made via the system bus 835 to the processor 810 be transferred, and the processor 810 executes one or more instructions or routines according to the received input. Often, the input data can represent a user interaction with the graphical output that appears on the display 820 provided. For example, the input data may represent the movement of a mouse. The processor moves 810 one on the display 820 displayed cursor corresponding to the mouse movement. The input data may also represent a selected UI element on the display 820 displayed, such as a window (eg, a browser window), a device graphic (eg, a container, a pump, a valve, a meter, etc.) or an operating system item. In addition, the input data may represent the control input. For example, the user can enter a setpoint for a process device using a keyboard, mouse, or touchscreen. If the input data represents a control input, the processor may 810 the input data via the system bus 835 to the network interface 825 transfer. The network interface 825 then transmits the input data to the process control network 100 where they are on another node (eg on the control unit 11 or the server 150 , in the 1A are shown) can be received. The processor 810 may also cause any other types of input data to the process control network 100 be transmitted.

Status awareness, transmission and cooperation

When performing, configuring, and maintaining process control with mobile devices, employees may need to move from device to device, and employees may want to be able to switch devices without seeing the ads they've viewed on a second device and / or recreate the processes they were involved in on the first device (and / or navigate back to the screens / processes). As illustrated in the above examples, an operator might want to remotely check the status of the process plant on her mobile phone on the way to work so that she is properly prepared on arrival at the factory. When she arrives at the factory, she goes to her office and works there first at a workstation. Afterwards, she uses a tablet to go to the equipment hall to check areas of the facility or carry out various tasks. In general, employees involved in the operation and maintenance of the process plant would like the equipment they use to have a certain degree of status sensitivity and transmit status information between devices to facilitate mobility and / or collaboration.

In one embodiment of the present disclosure, status information is seamlessly transferred from a first UI device to a second UI device to allow a user to continue a session from the first UI device on the second UI device or the session from the first UI without interrupting the workflow Device to the second UI device. The status transfer may also allow a first user of a first UI device to collaborate with a second user of a second UI device so that the two users can work together on tasks or work items. In another embodiment, a UI device may provide outputs according to the context of its execution. For example, the UI device may consider the location of the UI device and equipment, the type of UI device, or other aspects when determining which information to provide or how to provide information on the display of the UI device. The UI device and the mobile switching center disclosed herein offer the advantage of making operators and users of UI devices independent of physical control centers. A user of such a UI device can move freely throughout the plant without interrupting the workflow or restricting functions and capabilities to monitor and control the process.

9 illustrates an aspect of an exemplary mobile control center 900A , The mobile control center 900a includes a UI device 912a , a UI device 912b and a UI device 912c all from one user 901 and / or a user 902 can be used.

The mobile control center 900a allows the user 901 Synchronizing the UI devices 912a and 912b by transmitting the status of the UI device 912a on the UI device 912b , The transmission of the UI status can cause that on the UI device 912b similar information as on the UI device 912a are displayed. The status transfer can also cause the UI device 912b similar routines or applications as the UI device 912a performs. Also, the routines or applications can be on the UI device 912b containing the routines or applications on the UI device 92a at the same time as they are running. By transmitting the UI status from the UI device 912a on the UI device 912b can the user 901 the use of the UI device 912a quit and use the UI device 912b begin without interrupting the workflow.

Accordingly, the control center 900a to set up a secure collaboration session between at least two UI devices. In one embodiment, the secure collaboration session is automatically established when the two devices 912 approach and recognize the other device. After the session has been established, data synchronization between the UI devices can occur during a collaboration session. More precisely, the user can 901 with the user 902 work together, using the UI device 912b Status information on the UI device 912c transfers. By transmitting status information from UI device 912b on UI device 912c identifies the UI device 912c the operational status of the UI device 912b , For example, the UI device 912c the same or similar information as the one on the UI device 912c represent displayed information. The UI devices 912b and 912c You can also start communication routines for users 901 and 902 exchanging information (eg text, video and Voice over IP) using the UI devices 912b and 912c enable. For example, the UI devices 912b and 912c Share information about work items or tasks, so that users 901 and 902 Coordinated to a work task or task can work, even if for the user 901 and 902 not the same ads on the UI device 912b respectively. 912c being represented. In one example, users can test a device through the UI devices so that the other user knows that the device is being edited.

In some embodiments, the UI devices may 912a - 912c Transfer status information directly between these devices. The UI devices 912a - 912c may be used to transmit status information for short distance wireless technology, e.g. B. near field communication ( Standard ISO / IEC 14443 and ISO / IEC 1809 ) or Bluetooth ( Standard IEEE 802.11 ), to use. In other embodiments, the UI devices may 912a - 912c over the backbone 105 Status information about a node, e.g. B. the in 1A shown server 150 , transfer. In certain embodiments, the UI devices may 912a - 912c Be thin clients. This is what the UI devices render 912a - 912c Graphics, the bulk of the processing for the UI devices 912a - 912c however, it occurs on a node (eg, the one in 1A represented server 150 ) in the process control network 100 , In such embodiments, the status transfer may be between the UI devices 912a - 912c Transmitting status information between UIs running on the node.

In 9B become UI devices 112 in an exemplary mobile control center 900c illustrated. The mobile control center 900c Allows the transmission of a task status between the UI devices 112a - 112k and thus the synchronization of the UI devices as well as the cooperation between the users of the devices. The mobile control center 900c includes the server 150 , the process control network 100 , the user 901 and the UI devices 112a - 112k , The server 150 can be a database 151 which may include display data, parameter data, history data, context data, UI status information or other process engineering data. Database 151 may be in a store on the server 150 located or disconnected from the server 150 or stored on different devices distributed in the process plant. Each of the UI devices 112a - 112k can be from any type of process control UI device 112 which provides information about elements associated with a process or process and accepts user input through elements associated with a process or process. Each of the UI devices 112a - 112k can execute a corresponding UI. In alternative embodiments, the UI may be completely or partially on the server 150 be executed and on the UI devices 112a - 112k be provided, for. B. via a website. Each of the UI devices 112a - 112k can over the backbone 105 of the process control network 100 with the server 150 communicate. In the in 9B illustrated embodiment, the user 901 via a display 920 and an input interface 930 with the UI device 112 interact (the user 901 However, it can work with any of the UI devices 112a - 112k to interact). In this embodiment, the UI device is 112a a fixed workstation, with the input interface 930 a keyboard and the display 920 a monitor is. The UI device 112b is a mobile device (such as a cell phone or a PDA). The UI device 112c is a tablet that can receive touch input through a user's hand or through a pen. The UI device 112d is a portable device (in this case a watch with a touch screen). The UI device 112e is a laptop. The UI device 112f is a portable device (in this case, a headset with a head-up display.) The UI device 112g is a TV with which an input interface (not shown), e.g. For example, a keyboard, a mouse, a touch screen (eg, a capacitive touch screen), a motion sensor, or any other type of device that accepts user input may be linked. The UI device 112h is a device for the Display and user input (eg a touch screen) in a process plant (eg mounted on a wall, mounted on or near a process unit, etc.). The UI device 112j is a mobile device (eg a smartphone) with integrated projector, the UI on a surface 112k (eg a wall in the process plant). The on the surface 112k Projected UI may include a user input method (eg, tracking user movement via the UI device 112j or an external device (not shown)). Of course, in various embodiments, any combination of the UI devices 112a - 112k be used. In addition, the mobile control center 900c additional similar UI devices as the UI devices 112a - 112k include. In this description are each of the devices 112a - 112k however, in various embodiments, each of the devices may be associated with certain types of inputs 112 Accept inputs from multiple input sources, based at least on the usage type for the UI device 112 , For example, it is envisaged that UI devices 112 Accept inputs by pins or touch-sensitive devices that are not capacitive (eg resistive touchscreen, Surface Acoustic Wave (SAW) touchscreen, or other touch screen technology), for example: B. to allow input from a user wearing protective gloves. For each of the UI devices 112 Speech input can also be used, especially in environments where there is no external noise.

In the mobile control center 900c can any of the UI devices 112a - 112k the user 901 allow the monitoring and / or control of a process or elements through the process control network 100 are linked to a process. In one embodiment, each of the UI devices 112a - 112k Implement web clients or thin clients. In such an embodiment, the server may 150 the UI and all other routines for operating one or more UI devices 112a - 112k To run. The UI devices 112a - 112k can provide user input data to the server 150 submit, and it responds to user input. The server 150 can display data on the UI devices 112a - 112k transfer. As in this embodiment, most of the processing for the execution of the UI devices 112a - 112k through the server 150 This can be the operating status of the individual UI devices 112a - 112k track it by running the routines on the server 150 as well as between each UI device 112a - 112k monitored data monitored.

In other embodiments, the UI devices function 112a - 112k possibly just as data clients. For example, in embodiments, each UI device includes 112 a web browser and a routine for automatically generating HTML (or other code) for displaying information on the UI device 112 , The routine and / or the dynamic web page generated by the routine retrieve data from the server 150 and display the retrieved data (and other data, such as user input data) on the display. The routine and / or the dynamic web page may also accept user input and data back to the server 150 send. In such embodiments, much of the processing is done on the UI device 112 while over the network only data to the server 150 and be transmitted by this.

In another embodiment, statements (eg, JavaScript statements) that are based on the UI device generate 112 Dynamic code (such as HTML5 code) that is rendered in a suitable viewer application (for example, an HMTL5 viewer or a web browser). For example, the JavaScript code may open a WebSocket connection to use the WASP (WebSocket Application Messaging Protocol) message between messages on the UI device 112 running JavaScript and the server 150 to send.

The server 150 can periodically save UI status information (for example, in the database) or in response to a triggering event 151 ). The UI status information can show the status of the UI device at capture time. The UI status information may include information about the user or operator interacting with the UI device; to the applications, programs, routines or modules that are executed with respect to the UI device; to the graphics or sounds that are output on the UI device; to the section (s) of the installation to which the displayed data relates; or any other information related to the operation of the UI device. If the server 150 Receives a status transfer request, it can access locally stored UI status information in the database 151 access and submit them to the appropriate UI running on the server 150 is performed. The UI can transfer the corresponding display data to the corresponding UI device. For example, the UI device 112b Status information from the UI device 112a request (for example, where the user 901 from the UI device 112a to the UI device 112b switch without interrupting the workflow). In some embodiments, the UI devices 112a and 112b UI on that on the server 150 is performed. The server 150 can on in the database 151 access locally stored UI status information and send it to the UI for the UI device 112b to transfer. The UI on the UI device 112b determined based on the stored UI status information, what is on the UI device 112b is displayed and transmits the display data to the UI device 112b ,

In some embodiments, each of the UI devices may 112a - 112k Capture UI status information and in the database 151 save when a user interacts with the respective UI device. The UI device can be over the network 100 the UI status information on the server 150 transfer. The server 150 transmits the UI status information of a UI device 112a - 112k so that z. When receiving a request from a particular UI device of the UI devices 112a - 112k this UI device is executed according to the received UI status information.

Example: The user 901 starts using the UI device 112a (However, the following example also works with any of the UI devices 112b - 112k be executed). If the user 901 with the UI device 112a interacts, it periodically captures and stores UI status information. The UI status information can affect the user 901 relate, the z. B. represents a user ID or a user title / role. The UI status information may also refer to the user's session, including information about the user on the UI device 112a executed programs or routines, the time of acquisition, the duration of the session, the configuration of the display 920 of the UI device 112a graphics displayed on the UI device 112a monitored or controlled units (ie the process areas, devices, equipment or data) and / or the type of UI device used (in this case, a fixed workstation). After collecting and saving the UI status information, the UI device transmits 112a the UI status information about the process control network 100 on the server 150 so the server 150 the UI status information in the database 151 can save.

The user 901 decides to use a mobile UI device, eg. B. one of the UI devices 112b - 112f or 112i - 112k , In one embodiment, the user may 901 the UI device 112b use that to the user 901 recognizes. The UI device 112b communicates with the server 150 to get the latest UI status information available to the user 901 (in this case, the UI status information that was last on the UI device 112a were recorded). In some embodiments, the communication may include additional detection of status information regarding the UI device 112a on the UI device 112a trigger. The UI device 112b generates a GUI configuration based on the received UI status information, so that the display of the UI device 112b at least partially on the display of the UI device 112a responded to status information at the time of last capture. In other words, causes the mobile control center 900c a status transfer or status synchronization between the UI device 112a and the UI device 112b (in 10 an example of the appearance of the displays when synchronizing or transmitting the UI status is shown). The status transfer causes the interruption of the workflow to the user 901 is minimal.

In some embodiments, the detection of the UI status information may be automatic. For example, the UI device 112a Collect status information at regular, predefined intervals (for example, every 5, 10, or 30 minutes). The UI device 112a can also capture status information in response to a triggering event or triggering activity. The triggering event may include user input (eg, collecting status information each time a user input is received, or a schedule correlated to receipt of user input) or those on the UI device 112a provided information (eg the collection of status information on each alarm or each time a specified threshold for a measurement or value is reached). Alternatively, or in addition, the UI device 112a Manually acquire UI status information based on user input representing a command to capture or transmit the UI status information. For example, on the display 920 a graph will be displayed with which the user 901 interacts, the interaction causing the capture. The input interface 930 may include a mechanism (eg, a button, button, or trackpad) that is useful to the user 901 enabling the initiation of a capture. In some cases, a request may also be made by another UI device (such as one of the UI devices 112b - 112k ) the capture on the UI device 112a trigger. In another example, status information is provided by the UI devices 112a - 112k detected and transmitted (eg via near-field communication) when two UI devices touch (or are brought close together, eg 5 cm, 2 cm, 1 cm, etc.).

In other embodiments, the UI device recognizes 112b the user 901 automatically. For example, the user has 901 about a unique tag (for example, in a badge or on a card with an RFID chip) that identifies it. In other embodiments, the tag may be any tag or device that provides identification information, e.g. For example, an NFC device, a barcode, a Bluetooth device, or any other wireless access point. The UI device 112b can have a tag scanner or reader (such as an RFID scanner) that recognizes the unique tag. The UI device 112b can access a database at the one associated with the unique tag Identify users, so the UI device 112b the user 901 recognizes. The database can be located on the UI device 112b In other embodiments, however, the database is ordering 151 on the server 150 Users tags too, and the UI device 112 communicates with the server 150 to the user 901 to identify. In other embodiments, each UI device may be assigned to a particular user so that only a single user interacts with the UI device. In such an embodiment, the UI device may 112b the user 901 be assigned so that the UI device 112b It can be assumed that every user interacting with it is the user 901 is. Alternatively, the UI device 112b force that the user 201 enters a user ID and password to log in to the UI device 112b to register. This allows the UI device 112b , the user 901 to recognize.

In alternative embodiments, the user may 901 instead of the UI device 112b another UI device, eg. B. one of the UI devices 112c - 112k to use. This causes status synchronization or status transfer from the UI device 112a to one of the UI devices 112c - 112k , For example, the user may 901 a tablet, z. For example, the UI device 112c , with the last recorded status information of the UI device 112a synchronize. In other cases, the user can 901 a clock like the UI device 112d , a laptop like the UI device 112e , a headset like the UI device 112f or a TV like the UI device 112g with the last recorded status information of the UI device 112a synchronize.

In addition, the status information of the UI device 112a on the UI device 112a be transmitted. The user 901 can then have a session on the UI device 112a save and later on the session on this UI device 112a continue. The UI device 112a can return to an earlier UI state by accessing the state information on the UI device 112a or on the server 150 are stored. This differs from prior art systems where continuing a session at a later time, even on the same device, can be difficult because multiple users interact with the same console.

In further alternative embodiments, the user may 901 instead of the UI device 112a one of the UI devices 112b - 112k to use. That by the user 901 The UI device used can collect status information about this UI device. The captured status information can be sent to the server 150 where they are in the database 151 stored and accessible for access by the same or another UI device.

In some cases, the server can 150 a similar UI device as one of the UI devices 112a - 112k (ie, the server has a display and an input interface and can be used as a UI device). In such a scenario may be on the server 150 stored status information is accessed to the server 150 UI information to provide a user with the server 150 as a UI device can use. Accordingly, in some embodiments, each of the UI devices may 112a - 112k as a server 150 act.

In another embodiment, the UI devices 112a - 112k over the network 100 or another network or communication link, e.g. As a PAN (Personal Area Network) (eg., A Bluetooth network) or near field communication, status information with each other. In some embodiments, the receiving UI device may initiate the transmission of UI status information, while in other embodiments, the transmission is initiated by the transmitting UI device. In another embodiment, the status transfer may be accomplished by placing the UI status information in a memory (eg, a USB memory stick) and accessing the memory to retrieve the UI status information on a second UI device.

In certain embodiments, status transfers may be automatic and for the users of the UI devices 112a - 112k transparent. For example, a status transfer can be initiated automatically when a UI device is brought into the vicinity of another UI device. The UI devices may be circuits, e.g. As an NFC circuit, which allow the devices to recognize each other. The proximity of a device can also be detected on the basis of position data, which may be, for. From a GPS receiver, which may be included in one or more UI devices. The UI devices can send location information to the server 150 which uses this data to determine the proximity of UI devices and initiate a status transfer. In some embodiments, one or more UI devices may display an indicator graphic indicating that the respective UI device is currently receiving or transmitting status information. The indicator graphic may also indicate that a UI device is working with another UI device.

In 10 become sample device displays for UI synchronization between the UI devices 803a and 803b illustrates that z. B. before or during a status transfer can take place. In 10 can the UI device 803a a fixed workstation and the UI device 803b one Mobile device (eg a tablet). The UI device 803 contains a display 820a and an input interface 830a , the display 820a can be a GUI configuration 1010a displaying a container graphic 1015a , a level indicator graphic 1016a , a pump graphic 1020a , a valve graphic 1025a , a valve graphic 1030a , a chart 1035a , a chart 1040a and a graph 1045A contains. The UI device 803 contains a display 820b and an input interface 830b , the display 820b can be a GUI configuration 1010b displaying a container graphic 1015b , a level indicator graphic 1016b , a pump graphic 1020b , a valve graphic 1030b and a graph 1040b contains.

The UI device 803a can the UI status information 896 capture and on the server 150 or to another UI device, e.g. For example, the UI device 803b , transfer. The UI device 803a can when collecting the UI status information 896 determine which elements relate to the output on the display 820a exhibit. For example, the UI device 803 the the graphics 1016a - 1045A (a container, a pump, two valves and the devices that show the graphs 1035a - 1045A assigned) units and identify the units as status information 896 to save. In addition to identifying the above units, the UI device may 803a the coordinate positions for those on the display 820a identify displayed graphics. Thus, the UI status information 896 z. B. represent that the container graphic is in the center of the screen. The UI device 803a can also identify the locations of various windows or fields for currently running applications. In addition, the UI device can 803a identify the programs or routines running on the UI device 803a be executed, and store information about each program status. For example, a browser can be running and the UI device 803a Identifies a resource (such as a webpage, image, video, or other content) that the browser accesses or uses.

The UI device 803b can the UI status information 896 from the UI device 803a (or in other embodiments server 150 ) received. The output of the UI device 803b based on the received UI status information 896 , In particular, the UI device 803b on the UI display 830b display visual representations or graphics based on the received UI status information 896 based. Because the UI device 803b from a different device type with a different screen size than the UI device 112a can be, represents the UI device 112b possibly a different GUI configuration than the UI device 112a ready. In particular, the UI device 112b based on the UI status information 96 Identify units and programs with the highest priority and the GUI configuration 1010b generate accordingly. In particular, the UI device 803b the the graphics 1015b . 1016b . 1020b . 1030b and 1040b identify assigned units as high priority units. The UI device 803b Due to the limited screen size, it does not generate any graphics on the display 820a of the UI device 803a displayed graphics 1025a . 1035a or 1045A correspond. The UI device 803b can also display graphics at positions in the GUI configuration 1010b generate the relative positions of the corresponding graphics in the GUI configuration 1010a assigned.

Due to the different type of input interface (ie, touch-screen based and keyboard-based), the UI device may 803b also generate graphics whose size and shape are different from those on the UI device 803a distinguish generated graphics. For example, the UI device 803b Generate larger graphics that are easier to interact with by touch.

In some embodiments, the GUI configuration may be 1010b of the UI device 803b with the GUI configuration 1010a of the UI device 803a be identical, especially in embodiments in which the UI device 803a and the UI device 803b of the same device type. In other embodiments, there may be little correlation between the GUI configuration 1010b and the GUI configuration 1010a , For example, in some cases, the output on the display 830b of the UI device 803b partially or completely text-based. Even in such embodiments, the UI device may 803b nevertheless, based on the UI status information 896 determine the process units through which the UI device 803b To provide information. If z. For example, the UI device 803b none of the tank artwork 1015a of the UI device 803a corresponding graphic, the UI device can 803b nevertheless, determine that the container is a high priority entity and information about the text (eg, a textual value of the container level, the level indicator 1016a corresponds).

11 is a flowchart that is an example method 1100 to synchronize UI devices 112 represents. Other exemplary methods are described below, and the method 1100 should not be construed as a limitation. As described above, synchronizing the UI devices 112 Allow a user to continue a previous session on the same or a different device, and allow two or more users to collaborate by sharing information. method 1100 can be fully or partially implemented with one or more devices and systems, e.g. B. with the in the 1 - 10 shown devices and systems. method 1100 can be implemented as a set of statements, routines, programs, or modules that reside in memory 815 of the UI device 112 located and through the processor 810 in 8th be executed.

In the process 1100 receives the UI device 112 a request for the UI status information 896 (Block 1101 ). The UI device 112 Identifies a UI state of the first UI device 112 (Block 1105 ). Identifying the UI status may include identifying the on a display of the first UI device 112 displayed output. Identifying the output displayed on the display may include identifying the visual representations and graphics on the display of the first UI device 112 and identifying the entities associated with these visual representations and graphics. Identifying the output on the display may further include identifying the process parameters displayed on the display, identifying the GUI configuration on the display, and identifying the UI or device type of the UI device 112 ,

The first UI device 112 can identify process units associated with the output on the display. The process units may include process parameter data, process plant areas, field devices, executed applications, or application status. For example, the first UI device 112 identify a container graphic displayed on the display. The first UI device 112 uses this identification to identify container level readings, the area of the process plant for the vessel (eg, the boiler area), field devices associated with the vessel (eg, vessel inlet valves, vessel discharge pumps, vessel material temperature sensors, etc.), on the first UI device 112 executed applications (eg, a browser, a historian, an alarm management application, etc.) and / or the status of running applications (e.g., the resources the browser accesses or uses, the parameters specified by the Historian used or displayed, or the alarms displayed by the alarm management application).

After the first UI device 112 a UI state of the first UI device 112 It can determine data on a second UI device 112 that represent the identified UI status (block 1110 ). In particular, the first UI device 112 Data on the second UI device 112 which represent the identified units. In alternative embodiments, the first UI device 112 the unit data on the server 150 and then transfers the device data to the second UI device 112 ,

After on the second UI device 112 the UI status information 896 can receive the second UI device 112 Provide outputs according to the received UI status, and in particular according to the received unit data. The second UI device 112 For example, the determined process parameter data (ie, the one on the first UI device 112 provided process parameter data) on a display. The second UI device 112 can also provide an overview of the identified asset area (s) (ie, the areas that correspond to the identified issue on the first UI device 112 are assigned) on a display. In addition or alternatively, the second UI device 112 graphical representations of one or more identified field devices (ie the devices that are the output on the first UI device 112 are assigned) on a display. The second UI device 112 can also launch applications that match the identified applications (that is, the one on the first UI device 112 executed applications). Finally, the second UI device 112 cause one or more applications to be in an identified state (ie one or more on the first UI device 112 identified application status).

As another example and still referring to 11 can the UI device 803 the UI status information 896 and to the process control network 100 transfer. The UI status information 896 can change the status of the UI device 112 at the time of capture. The processor 810 can the UI status information 896 capture by causing the data representing the UI state to be in memory 815 be filed. The processor 810 can the UI status information 896 from the store 815 and over the network interface 825 to the process control network 100 transfer. The UI status information 896 may ultimately come from a node in the process control network 100 , z. From the server 150 to be received. In alternative embodiments, the UI status information 896 via the peripheral interface (eg a USB interface, the WiFi interface, the Bluetooth interface or the NFC interface), the peripheral interface providing the UI status information 896 to another UI device 803 transfers.

As above regarding 1A and below with respect to 12A and 12B described, the UI status information 896 z. B. Profile data of the user or operator included with the UI device 803 interacts. At the input interface 830 or the network interface 825 All or some of the profile data can be received. The processor 810 can cause that the input interface 830 or the network interface 825 the profile data via the system bus 825 in the store 815 transfers. In certain embodiments, the processor 810 the profile data in response to received data from the input interface 830 or the network interface 825 or in response to the data to the user of the UI device 803 or a similar UI device 803 to generate. In other embodiments, the profile data may already be in memory 815 available. The processor attacks 810 on the profile data or it stores the profile data in a different data structure (eg, the processor 810 on during the execution of the operating system 880 or another application on the UI device 803 access captured profile data and cause the profile data to be stored in a particular database used to transmit the UI status).

The UI status information 896 Also, the profile data may include session data, such as the output (eg, graphics or sounds) on the UI device 803 and the one on the UI device 803 running applications and the status of these applications. In other words, the processor can 810 in the illustrated embodiment, the session data based on the output on the display 825 and generate data based on the data generated or used while the other processor processes the application 810 be executed. The UI status information 896 In addition, the user profile data and session data may contain additional data about the operation or status of the UI device 803 include.

In another embodiment of the UI device 803 can this UI status information 896 from the process control network 100 receive and the UI device 803 into a status that reflects the UI status information 896 equivalent. In such an embodiment, the UI status information may be 896 a previously detected operational status of another UI device ("previous UI device") (ie the UI device 803b ) or the UI device 803 represent. In such an embodiment of the UI device 803 can the UI status information 896 via the process control network 100 at the network interface 825 be received. The network interface 825 can the UI status information 896 for storage in the memory 815 transfer. The processor 810 can be on all or some of the UI status information 896 In the storage room 815 access to the UI device 803 to put in a state of some or all UI status information 896 equivalent. The UI status information 896 can specify a UI state in which the previous UI device provides information about specific units in the process or in the process control network 100 has provided. The processor 810 may cause the display 820 Displays information that corresponds to these particular units. the display 820 can display the information in the same or similar GUI configuration as the previous UI device 803b However, under certain circumstances (for example, if the UI device 803 from a different device type than the previous UI device 803b is) use a different GUI configuration. In some embodiments, the processor 810 based on the UI status information 896 identify relevant points (eg relevant units) and cause that on the display 820 Information about the identified relevant points will be displayed.

The UI status information 896 Alternatively or in addition, to specify process units, they may indicate the status of one or more applications running on the previous UI device 803b were executed. The processor 810 may cause these one or more applications to start and run in the specified state. For example, the UI status information 896 indicate that a browser window was open and that a particular web page was displayed in it. In this example, the processor 810 cause a browser application to launch and the same web page open. In another example, the UI status information 896 indicate that a Viewer tool has been run to view the process history, that certain process values have been accessed by that tool, or that certain process values have been viewed by this tool. In this example, the processor 810 cause a viewer tool to start and access or display the same process values.

In 12A provides a block diagram of exemplary data for UI devices 112 in a mobile control center 1200a dar. The mobile control center 1200a allows a status transfer to one or more UI devices 112 so that the user of the respective UI device 112 Continue the workflow with a previously saved state or with users of other UI devices 112 can work together. The mobile control center 1200a includes the server 150 , the process control network 100 and the UI devices 112 , In some embodiments, the server may 150 also as a UI device 112 act. The server contains this 150 the display 820 to display a GUI configuration and to provide process information to an operator or user. In such an embodiment, the server may 150 also the input interface 830 for receiving user input.

The server 150 includes a processor 1201 , a network interface 1202 and a memory 1203 , In the storage room 1203 become the UI status information 1240 saved, the profile data 1245 and / or session data 1265 may include. The UI status information 1240 can in the in 9B represented database 151 get saved. The server 150 can connect via a wired or wireless communication channel through the process control network 100 communicate. Accordingly, each of the UI devices 112 using a wired or wireless communication channel through the process control network 100 communicate and each of the UI devices 112 can with the server 150 communicate.

The memory 1203 of the server 150 can include dynamic and / or persistent storage, and can be removable storage or fixed storage. For example, the memory 1203 Computer storage medium in the form of RAM (Random Access Memory), ROM (Read-Only Memory), EEPROM, FLASH memory or other storage technology, CD-ROM, DVD (Digital Versatile Disk) or other optical disk storage, magnetic cassettes, magnetic tape, magnetic disk storage or others Magnetic storage devices or any other medium that may be used to store the desired information. The processor 1201 is configured to retrieve and execute statements stored in memory 1203 are stored. In the storage room 1203 can z. B. operating system data or program data are stored. The network interface 1202 may include one or more antennas for wireless communication, one or more wired connections, or both. In some embodiments, the network interface 1202 include one or more GPS receivers, Bluetooth transceivers, NFC transceivers, RFID transceivers, and / or local network transceivers. The network interface 1202 can through the process control network 100 with the UI devices 112 communicate.

Each UI device 112 can contain data that has a user ID 1205 , a session ID 1210 , a client device ID 1215 and / or a UI type 1220 represent. The user ID 1205 can correspond to a single user or operator and it acts as a unique ID. Likewise, the session ID 1210 as a unique ID of a specific user session on the UI device 112 act. A user session is generally considered to be a period of use by a particular user without lengthy breaks. If a user is using the UI device 112a for a longer period of time and later the use of the UI device 112 the subsequent use generally marks the beginning of a new session (unless the session continues as described below). The client device ID 1215 can be used as a unique identifier of the UI device 112a act. Finally, the UI type 1220a the type of on the UI device 112a implemented GUI. The UI type is often the same as the device type of the UI device. In the preferred embodiment, there are two general UI types: a normal UI and a mobile UI. Desktops, laptops, and other large-screen UI devices typically implement a normal UI. Mobile devices, for. Mobile phones, PDAs and tablets often implement a mobile UI that offers larger graphics and larger text (relative to screen size). In many embodiments, due to the limited size of many mobile device screens, the mobile UI may provide a different GUI configuration and graphics. In other embodiments, other UI types, e.g. As a mobile phone UI, a tablet UI or a headset UI, be present.

The profile data 1245 can the user profiles 1250a - 1250d contain. Each of the user profiles 1250 - 1250d can correspond to a unique user or operator. The user profile 1250a can contain data that has a user ID 1252 , a user role 1254 and user history data 1256 represent. The user profiles 1250 - 1250d may contain similar elements. The user ID 1250a can represent a unique ID for a specific user and the user ID 1205a on the client device 112a correspond. The user role 1254 may represent the jurisdiction, title or role of a particular user in the process plant. For example, the user role 1254 restrict the areas of the plant that the user is allowed to control. The user role 1254 It may also limit the amount of control that can be implemented by the user or the types of programs the user has access to. In some embodiments, the user role 1254 also restrict the user's permissions to access and control units in the process plant based on a schedule. For example, it is possible for the user role 1254 only has the authority to implement control functions during the user's working time (eg 8-17). Finally, the user history data 1256 Trends, habits and preferences of the user represent the user profile 1250a assigned. The user history data 1256 can z. For example, specify a particular area in the process plant, certain devices or equipment, or specific process parameters to which the user preferably directs his attention.

The session data 1265 can the sessions 1270a - 1270d include. The session 1270a may contain data that has a session ID 1272 , a user ID 1274 , a client device ID 1276 , a UI type 1278 , Application state data 1280 and session time data 1282 represent. Each of the sessions 1270b - 1270d may include data representing similar entities. The session ID 1272 serves as a unique ID for a specific session. The user ID 1274 can represent a unique user and the user ID 1252 of the user profile 1250a and the user ID 1205a of the UI device 112a correspond. The client device ID 1276 can uniquely identify a specific UI device and the UI device ID 1215a correspond. Similarly, the UI type 1278 the UI type 1220a on the UI device 112a correspond. The data about the application state 1280 can represent programs running on a UI device as the UI status information 1240 they can also represent the state of the particular application at the time of capture. The session time data 1282 can represent temporal data, such as the start time of the session, its end time, its length, etc.

In operation, the UI device 112a the UI status information 1240 (including the profile data 1250a and the session data 1270a ) to capture. When a user session ends, the UI device may 112a the UI status information 1240 to save to the server 150 transfer. The network interface 1202 can the UI status information 1240 from the process control network 100 receive. The processor 1201 can work that UI status information 1240 to save to the memory 1203 be transmitted. In alternative embodiments, the UI device may 112a some or all of the UI status information 1240 on a periodic basis to the server 150 transmitted, or in response to a triggering event. The server 150 can then do some or all of the UI status information 896 transferred to a UI device, eg. B. to UI device 112b ,

Similar to 12A shows 12B a block diagram with exemplary data with UI devices 112 in a mobile control center 1200b are connected. The mobile control center 1200b may be a state transition from a first UI device 112a to one or more other UI devices 112b . 112c enable. As in the mobile control center 1200a allows the mobile control center 1200b a user of the UI device 112a , a workflow on the UI device 112b resume and / or resume, or he may communicate with another user through the UI device 112b work together. The mobile control center 1200b contains the server 150 , the process control network 100 and the UI devices 112a c. In some embodiments, the server may 150 also as a UI device 112 serve, the server 150 the display 820 which displays a GUI configuration and provides process information to an operator or user. In such an embodiment, the server may 150 also the input interface 830 for receiving user input.

The mobile control center 1200b differs in at least one respect from the mobile control center 1200a , In particular, in the mobile control center 1200b transmit the status and / or session data to the direct example of the UI device 112a to the UI device 112b , and not over the server 150 , Each of the UI devices 112 stores the UI status information 1240 which the session data 1265 can contain. The session data 1265 by any of the UI devices 112 can be stored, the user ID 1205 , the session ID 1210 , the UI device ID 1215 , the UI device type 1220 , the data on the application state 1280 and the session time data 1282 contain.

The user profile data 1245 described with reference to 12A , can in the server 150 and / or in memory of each UI device 112 get saved. In this way, every user can use one of the UI devices 112 and the profile of the user (including his settings, roles, archive data, etc.) will be used by the UI device 112 be available. In some embodiments, the UI device may 112 the user profile data 1245 from the server 150 download or otherwise access it when a particular user joins the UI device 112 logs. In other embodiments, the profiles of all users or of users who previously own a particular UI device 112 used in the memory of the UI device 112 be resident.

During operation, any UI device can 112 In the storage room 815 have stored one or more applications, for example, display applications for displaying information about the process plant. The UI device 112 can determine the state of the application (s) in the application state data 1280 to save regularly and / or the state of this application (s) on request to another UI device 112 transfer. For example, a user may access data from process plants using a viewing application on the UI device 112a Show. The viewing application may be on the UI device 112a located and data from the server 150 retrieve and / or receive (eg process data). In certain embodiments, the UI device receives 112a both process data and visualization data from the server 150 , For example, the UI device 112a from the server 150 Receive trend data that refer to a specific process parameter, and use these trend data to obtain additional rendering instructions indicating the manner in which the data is to be displayed (eg, 3D plot data, tabular data, axis data, etc.). The rendering data may be sent as a separate entity so that the same data is sent with different rendering information (e.g., formatting) corresponding to the target device. In any case, the UI device preserves 112a certain information about the state of the application (s) on the UI device 112a including information about which data is displayed, which areas or devices of process plants are displayed, what tasks are performed, and the like.

The user may want to use the UI device 112a to the UI device 112b For example, to go from a workstation UI device to a tablet UI device. To do this, the user can enter a state transition from the UI device 112a to the UI device 112b initiate. In a first embodiment, the user brings the UI device 112b near the UI device 112a so that the NFC devices in each UI device 112 communicate with each other and connect. For example, the NFC devices can work together to connect via Bluetooth or Wi-Fi, so that the session data 1265a from the UI device 112a to the UI device 112b can be passed to the UI device 112b can resume the session in a similar or similar state as the one on the UI device 112a was in operation. In a second embodiment, the user may have one or more menus on the UI device 112b activate to select a session number, for example on the display 820 of the UI device 112a , Other state transfer embodiments that may be used under these or other circumstances are presented in this specification. The devices can then over the network 100 (and possibly the server 150 ) or communicate directly with each other via Bluetooth or Wi-Fi to the session data 1265a from the UI device 112a to the UI device 112b transferred to. Once the UI device 112b the session data 1265a received and as session data 1265b has saved the UI device 112b Resume the session previously on the UI device 112a was in operation.

In certain embodiments, the state transfer is from a first UI device 112 to a second UI device 112 also transfer any control element that works with the UI device 112 connected is. For example, in some cases, a controller or other process device may receive inputs from only one source at a time. In such cases, it is important that the source of the submissions is definitely determined and that any potential for conflict is removed. When a user from a first UI device 112 to a second UI device 112 changes, such inputs after state transfer to this device must definitely be with the second UI device 112 be linked. In such cases, the server can 150 Keep tracking data (for example, the UI device ID 1276 that a specific session 1265 and it can reassign the UI Device ID during transmission to the second UI device. The server 150 may eventually find that a transfer has occurred, even if the transfer is directly between the first and second UI device 112 he follows; this depends on the last request of process control data. For example, the server 150 determine that the UI device 112b as last requested data, and therefore notice that the UI device 112b now in control of the session. Alternatively, the UI device 112a abandon the session or disallow it once the session has been broadcast. This will be a message to the server 150 sent to the content that has the UI device 112a no longer connected to the session leading to the UI device 112b was transferred. Or the UI device 112b can send a similar message to the server 150 send, which indicates positively that the UI device 112b now assigned to the session, and the server 150 informed that the UI device 112a no longer linked to the session. In yet another embodiment, a session token may be associated with each session that is stored in the UI device and transmitted from device to device. If the device does not have the session token for a particular session, the device does not send commands (or at least send a subset of commands) from that device, even if the device is otherwise in control of the session. This allows data associated with a particular session to remain on the UI device 112a even after the state transfer has taken place and the session token to the UI device 112b was passed on. The session token can take any form, including, for example, a secure file, a hash code, a specific code or string, and so on.

Some of the methods related to the concepts described in the preceding paragraphs will now be described with reference to the corresponding figures.

13 is a flowchart for an exemplary method 1300 to provide session data for a UI device 112 , Providing session data can facilitate UI state transfers or synchronization, allowing for continuous workflow or collaboration. method 1300 can, whole or partially implemented in one or more devices or systems, for example at the server 150 in the 1 . 9 and 12 will be shown. The method may be stored as a set of instructions, routines, programs or modules in memory 1203 stored and by the processor 1201 be executed.

method 1300 starts when the server 150 a session request from the UI device 112 (Block 1305 ) receives. The server 150 can determine if the UI device 112 a user ID (block 1310 ) and may request a user ID if none has been provided (Block 1315 ). Once the user ID has been deployed, the server can 150 identify the data associated with the user ID (block 1320 ) are connected. For example, it may include one or more user profiles, sessions, or UI devices 112 which are assigned to the user ID. In alternative embodiments, the server may 150 receive a UI device ID and identify data associated with the UI device ID (not the user ID).

After identifying data associated with the provided user ID, the server may 150 determine if the UI device 112 requests the workflow from an earlier session (block 1325 ) to resume. If there is no such requirement, the server can 150 identify a default session (that is, data representing a new session or default session) as a "target session" that the UI device (Block 1330 ) to provide. The standard session data may include data such as standard GUI configuration data, standard process parameter data, or standard display data. For example, for new sessions that do not continue an earlier workflow, the default GUI configuration may include an active window with an overview of the attachment. The server 150 can send the default session data to the UI device 112 (Block 1350 ) transfer.

If the server 150 The server may receive a request to resume the previous workflow 150 Determine if a particular session through the UI device 112 (Block 1335 ) was identified. If no special session has been identified, the server may 150 the last saved session associated with the user ID (or, in alternative embodiments, the UI device ID) will identify the "target session" to the UI device 112 (Block 1340 ) provided. The server 150 may be the most recent session data to the UI device 112 (Block 1350 ) transfer. If the server 150 Receives a special session associated with the request for resume workflow, the server 150 The stored session data for that session (in the memory of the 1203 in 12A shown server 150 stored, for example) as identifying data for the "target session" sent to the UI device 112 (Block 1345 ) to provide. The server 150 can send the respective session data to the UI device 112 (Block 1350 ) transfer.

In alternative embodiments, the server may 150 a second UI device 112 , where the second UI device 112 receives the session request from a first UI device 112 and places the session data with the first UI device 112 be.

14 is a flowchart for an exemplary method 1400 to generate a GUI configuration on a UI device 112 , method 1400 It may be the UI device 112 to provide its output in accordance with the information received in a UI status transfer and in accordance with the context of the environment and use of the UI device 112 , method 1400 may be implemented, in whole or in part, in one or more devices or systems, for example in one of the UI devices 112 or 112a -G ( 1 - 10 and 12 ). method 1400 can be stored as a set of statements, routines, programs or modules in memory 815 stored and by the processor 8310 be executed.

method 1400 starts when the UI device 112 Context data (block 1405 ) identified. The UI device 112 can also identify units associated with the context data. The context data can be any context information or elements. In one embodiment, the context data may represent all elements included in the context sensitivity data 1540 or the work task data 1550 are included and in relation to 15 to be discribed. The connected entities may be any entities, equipment, devices, or parameters associated with the context.

method 1400 may be receiving UI status information 896 include, for example, the in 12 (Block 14 ) UI status information shown 896 , The UI device 112 can the UI status information 896 received from a device or system that has the in 13 shown method 1300 implemented. After receiving the UI status information 896 can the UI device 112 Units based on received UI status information 896 (Block 1420 ). A unit can be any area, device, system or parameter in the process. In general, the units are with the UI status information 896 are also connected to the information attached to the last UI device 112 were provided to the UI status information 896 were recorded.

The UI device 112 can the units (block 1430 ) prioritize. A unit may have a higher or lower priority, depending on factors such as the importance of the unit for stable operation of the process, for the time sensitivity (eg, a stack becomes corrupted if a unit is not addressed quickly) the location (for example, if the UI device 112 is close to a location connected to a unit) for the status (eg, if a unit malfunctions or is associated with a malfunction) for the alarm condition (eg, if the unit is connected to a unit) Parameter value is linked outside the normal operating range), for the schedule (eg, if a unit is associated with an off-line device), or for the relevance of the work task (eg, if the unit is related to a work item, the with the user or the UI device 112 connected is).

The UI device 112 can generate a GUI configuration based on the prioritized units (block 1435 ). A prioritization of the units may be necessary if the UI device 112 can not display all relevant information relevant to the units identified in the context data and the session received. For example, in some embodiments, the previous UI device may 112 be a workstation with a normal UI type while the UI device 112 containing the UI status information 896 receives, is a tablet with a mobile UI type. Because mobile UI devices are configured for smaller screens, they often provide less information. Therefore, the UI device would 112 even if the UI device 112 has avoided identifying units associated with context data, yet prioritizing particular units to determine which units the UI device is for 112 Should provide information.

In alternative embodiments, the system or device may provide the UI status information 896 provides the type of UI device or device type of the UI device 112 identify the UI status information 896 receives. In such embodiments, the providing system may provide the UI status information 896 customize the UI device 112 to be provided. In other words, the providing system can provide more or less information, depending on the UI type or device type. The providing system may also provide display data formatted for the UI type or device type.

15 is a flowchart of a procedure 1500 for the direct transmission of status information between two UI devices 112 in the process plant 10 , method 1500 may be implemented, in whole or in part, in one or more devices or systems, for example in one of the UI devices 112 , method 1500 can be stored as a set of statements, routines, programs or modules in memory 815 stored and by the processor 810 be executed.

method 1500 starts with a first UI device 112 having one or more first routines for performing a function (block 1505 ). The function may be a control function, operation function, configuration function, maintenance function, data analysis function, management function, quality control function or a safety function. The first UI device 112 can be connected to a uniform logical data storage area via a network, e.g. For example, the big data system 102 , The unified logical data storage area can be configured to store, using a common format, process data corresponding to the process plant. The process data may include multiple types of process data, including configuration data, continuous data, batch data, measurement data, and event data.

The first UI device 112 can provide status information about a second UI device 112 (Block 1510 ) to transfer. The status information may indicate one or more first routines that are on the first UI device 112 are in operation. In some embodiments, the status information may be transmitted over an Internet connection. In other embodiments, the status information may be passed through an intermediate network. In still other embodiments, the status information may be transmitted over a point-to-point wireless connection from the first UI device 112 to the second UI device 112 be handed over. In some cases, the status information may be forwarded via wireless communication in accordance with a protocol such as the Bluetooth protocol or the NFC protocol. In other cases, the status information can be sent via a device (the server 150 can be) from the first UI device 112 to the second UI device 112 be transmitted. In certain cases, the first UI device 112 the status information to the second UI device 112 transferred when the UI devices 112 recognize each other and the same user is logged on both devices. In some embodiments, the status information may be based on an instruction to pass the status information provided on the first UI device 112 will be handed over. In certain embodiments, the passing of status information simplifies one or more of the following: Collaboration of the two UI devices 112 with different users; Mobility of a single user over the two UI devices 112 ; Device sensitivity of the user location within the process plant or device sensitivity near the User to a particular process equipment.

The second UI device 112 can receive the status information and one or more second routines (block 1515 ) To run. The display of the second UI device 112 may be according to the stored status and according to the device type of the UI type of the second UI device 112 be configured. The second routines may correspond to one or more of the first routines that reside on the first UI device 112 are in operation. In some embodiments, the second UI device may 112 receive a signal from a component for location awareness, and it may modify the execution of one or more second routines according to the received signal. In certain cases, the site awareness component may receive a signal from the second UI device 112 receive. The signal may cause the second UI device 112 modifies the execution of the one or more routines according to the received signal over the network. Modifying the execution of one or more routines may include one or more of the following: highlighting a portion of the process plant in which the second UI device is located 112 is; View information about a specific device within a specified distance from the second UI device 112 ; Display an alarm relevant to a device in the area of the process plant in which the second UI device is located 112 is; or displaying a work item that belongs to a device in the area of the process plant in which the second UI device belongs 112 located.

In some embodiments, the second UI device may 112 receive a signal from a device awareness device and may modify the execution of one or more second routines according to the received signal. In certain embodiments, the device awareness component may include a transmitter that provides a wireless signal to the second UI device 112 transfers. The wireless signal may identify the device to which the transmitter is linked.

In some embodiments, one or both of the first UI devices may 112 and the second UI device 112 Be mobile devices. In other embodiments, one or both of the first and second UI devices may be 112 Be workstations. In some embodiments, a UI device may 112 a mobile device and the other can be a workstation. In one embodiment, the second UI device 112 configure an ad based on the status information provided by the first UI device 112 received, and device type or UI type associated with the second UI device 112 is linked.

16 is a flowchart of an exemplary method 1600 for the transmission of status information between two UI devices 112 that with the server 150 in the process plant 10 are connected. method 1600 may be implemented, in whole or in part, in one or more devices or systems, for example, the process control network 100 , In particular, methods can 1600 , in whole or in part, may be implemented on one or more devices or systems, for example the server 150 , or one or more devices or systems such as the UI devices 112 , method 1600 can be stored as a set of statements, routines, programs or modules in memory 815 or in memory 1203 stored and by the processor 810 or the processor 1201 be executed.

method 1600 starts with a first UI device 112 comprising one or more first routines for performing a function in a process plant (Block 1605 ). The first UI device 112 can track the status of the one or more first routines that are on the first UI device 112 (Block 1610 ). In some embodiments, the server may 150 track the status of the one or more first routines attached to a first UI device 112 be executed. The first UI device 112 , or the server 150 , may store the tracked states of the one or more first routines (block 1615 ).

The first UI device 112 , or the server 150 , The stored status of the one or more first routines to a second UI device 112 (Block 1620 ) transfer. In some embodiments, the status information may be transmitted over an Internet connection. In other embodiments, the status information may be transmitted over a point-to-point wireless connection from the first UI device 112 or the server 150 to the second UI device 112 be handed over. The status information can also be from the first UI device 112 or from the server 150 via an intermediate device to the second UI device 112 be transmitted. In some cases, the status information may be forwarded via wireless communication in accordance with a protocol such as the Bluetooth protocol or the Near Field Communication protocol. In certain embodiments, the condition may be to the second UI device 112 be transferred when the first UI device 112 from the second UI device 112 is detected, or if the second UI device 112 from the first UI device 112 is recognized. Transferring the saved status to the second UI device 112 can transfer the stored status to the first UI device 112 include when on the first UI device 112 the instruction was received that the first UI device 112 the saved status to the second UI device 112 should transfer.

The second UI device 112 may execute one or more second routines, wherein the second routines correspond to the one or more first routines that reside on the first UI device 112 (Block 1625 ). In some embodiments, the second UI device may 112 receive a signal. The signal may be near the second UI device 112 to a device or location. After receiving the signal, the second UI device 112 modify the execution of the one or more second routines according to the received signal. In some embodiments, the second UI device may 112 transmit to a component for location sensitivity a signal indicating the proximity of the second UI device 112 indicating to the device or location. In such an embodiment, the second UI device 112 from a server 150 receive specific information about the device or location.

In some embodiments, the second UI device may 112 Take one or more of the following actions when near the device or location: Highlight a section of the process plant that contains the second UI device 112 is; View information about a specific device within a specified distance from the second UI device 112 ; Display an alarm relevant to a device in the area of the process plant in which the second UI device is located 112 Viewing a work item that belongs to a device in the area of the process plant in which the second UI device is located 112 is; Highlighting on display equipment of a process plant associated with the received signal; View information about a particular device associated with the signal on the second UI device 112 ; Displaying an alarm on the device associated with the received signal or displaying a work item associated with the device associated with the received signal.

In some embodiments, one or both of the first UI devices may 112 and the second UI device 112 Be mobile devices. In other embodiments, one or both of the first and second UI devices may be 112 Be workstations. In some embodiments, a UI device may 112 a mobile device and the other can be a workstation. In one embodiment, the second UI device 112 configure an ad based on the status information provided by the first UI device 112 received, and device type or UI type associated with the second UI device 112 is linked.

17 is a flowchart of another method 1700 for the transmission of status information between two UI devices 112 in the process plant 10 , method 1700 may be implemented, in whole or in part, on one or more devices or systems, for example the server 150 , or one or more devices or systems such as the UI devices 112 , method 1700 can be stored as a set of statements, routines, programs or modules in memory 815 or in memory 1203 stored and by the processor 810 or the processor 1201 out 12 be executed.

method 7500 starts with the server 150 containing one or more functions related to process data (block 1705 ). In some embodiments, the process data may be stored in a unified, logical data storage area and stored in a common format. The process data may include multiple types of process data, including configuration data, continuous data, batch data, measurement data, and event data.

The server 150 It may be a first UI device 112 allow over the server 150 to access the process data. The server 150 It may be the first UI device 112 also allow status information on the server 150 (Block 1710 ) to keep. The status information can be an indication of the state of the UI that is on the first UI device 112 is performed.

The server 150 It may be a second UI device 112 allow over the server 150 to the process data and status information (block 1710 ). The second UI device 112 can execute a UI in accordance with the status information.

In some embodiments, one or both of the first UI devices may 112 and the second UI device 112 Be mobile devices. In other embodiments, one or both of the first and second UI devices may be 112 Be workstations. In some embodiments, a UI device may 112 a mobile device and the other can be a workstation.

18 is a flowchart of an exemplary method 1800 which is the operation of the process plant 10 represents using UI devices 112 connected to the mobile control center. method 1800 may, in whole or in part, on one or more devices or Systems are implemented, for example the server 150 , or one or more devices or systems such as the UI devices 112 , method 1800 can be stored as a set of statements, routines, programs or modules in memory 815 or in memory 1203 stored and by the processor 810 or the processor 1201 be executed.

method 1800 starts with a first UI device 112 that on the server 150 (Block 1805 ) can access. The server 150 can be connected to a database that stores process data. The first UI device 112 can be assigned to a first user profile. The first UI device 112 can a function in the process plant (block 1810 ) To run.

A second UI device 112 can access the server 150 (Block 1812 ) apply. The second UI device 112 can be assigned to the first user profile. The server 150 can store status information that shows the status information with the status of the first UI device 112 (Block 1815 ) are linked.

The server 150 can access the second UI device 112 provide access in accordance with the stored status information (Block 1820 ) can stand. The second UI device 112 can a function in the process plant (block 1825 ) To run.

In some embodiments, one or both of the first UI devices may 112 and the second UI device 112 Be mobile devices. In other embodiments, one or both of the first and second UI devices may be 112 Be workstations. In some embodiments, a UI device may 112 a mobile device and the other can be a workstation.

19 is a flowchart of an exemplary method 1900 , executed on a server, which controls the mobile control of the process plant 10 simplified. method 1900 may be implemented, in whole or in part, in one or more devices or systems, for example, the process control network 100 , In particular, methods can 1900 , in whole or in part, may be implemented on one or more devices or systems, for example the server 150 , or one or more devices or systems such as the UI devices 112 , method 1900 can be stored as a set of statements, routines, programs or modules in memory 815 or in memory 1203 stored and by the processor 810 or the processor 1201 be executed.

method 1900 starts with the server 150 , the process data for display on a first UI device 112 (Block 1905 ) can format. In some cases, the formatted process data may be displayed on a web browser running on the first UI device 112 is executed. The server 150 can process data according to a device type or a UI type of the first UI device 112 format.

The server 150 can be sent to the first UI device 112 the formatted process data (block 1910 ) transfer. In particular, the server can 150 to the first UI device 112 Transfer process data that can be viewed in a multipurpose process control application running on the first UI device 112 is performed.

The server 150 can save the status information associated with displaying the process data on the first UI device 112 (Block 1915 ) are linked. Saving the status information may include storing one or more of the following: a display configuration of the first UI device 112 ; a section of the process plant attached to the first UI device 112 is shown; Data of a device of the process plant, that of the first UI device 112 are displayed; a feature that works on the first UI device 112 is executed and includes one or more of the following functions: control function, operation function, configuration function, maintenance function, data analysis function, quality control function or a safety function; and a user profile on the first UI device 112 is active.

The server 150 can display the process data for display on a second UI device 112 according to the stored status information (Block 1920 ) format. The server 150 can to the second UI device 112 the process data (block 1925 ) transfer. In particular, the server can 150 the process data according to a device type or a UI type of the second UI device 112 format. In some cases, the device type of the second UI device may be 112 depends on the device type of the first UI device 112 differ. For example, the first UI device 112 be a workstation and the second UI device 112 can be a mobile device. Alternatively, the first UI device 112 a mobile device and the second UI device 112 can be a workstation. In some embodiments, the server may 150 the process data for an ad on the second UI device 112 format, leaving an operating state of the first UI device 112 on the second UI device 112 is duplicated.

In some embodiments, the server may 150 a request from the second UI device 112 received to the second UI device 112 to provide a user interface according to the stored status information. The server 150 can with the second UI device 112 and in response to the request to provide a user interface, a secure communication channel between the server 150 and the second UI device 112 set up.

20 is a flowchart of an exemplary method 2000 for transmitting the status of the first UI device 112 to the second UI device 112 , method 2000 may be implemented, in whole or in part, in one or more devices or systems, for example, the process control network 100 , In particular, methods can 2000 , in whole or in part, may be implemented on one or more devices or systems, for example the server 150 , or one or more devices or systems such as the UI devices 112 , method 2000 can be stored as a set of statements, routines, programs or modules in memory 815 or in memory 1203 stored and by the processor 810 or the processor 1201 be executed.

method 2000 starts with a first UI device 112 or the server 150 that's on a display of the first UI device 112 (Block 2005 ) can identify.

The first UI device 112 or the server 150 can identify process unit data associated with the graphics displayed on the first UI device 112 (Block 2010 ) to be provided. The identification of the process unit data may include one or more of the following: process parameter data associated with the graphics on the display of the first UI device 112 linked; a process plant area that matches the graphics on the display of the first UI device 112 linked; a field device that matches the graphics on the display of the first UI device 112 linked; an application running on the first UI device 112 is performed; or the status of an application running on the first UI device 112 is performed. The first UI device 112 or the server 150 can transfer the identified data of the process unit to a second UI device 112 (Block 2020 ) transfer. The first UI device 112 or the server 150 can identify the identified graphics for the second UI device 112 (Block 2020 ) provide.

21 is a flowchart of a procedure 2100 to initiate a UI session on a first UI device 112 , method 2100 may be implemented, in whole or in part, in one or more devices or systems, for example, the process control network 100 , In particular, methods can 2100 , in whole or in part, may be implemented on one or more devices or systems, for example the server 150 , or one or more devices or systems such as the UI devices 112 , method 2100 can be stored as a set of statements, routines, programs or modules in memory 815 or in memory 1203 stored and by the processor 810 or the processor 1201 be executed.

method 2100 starts with the server 150 from a first UI device 112 a session request (block 2105 ).

The server 150 can identify a user profile associated with the session request (block 2110 ) is linked. Identifying a user profile associated with the session request may include that of the first UI device 112 receive a user ID associated with the user profile. The user ID is currently on the first UI device 112 to be registered. Identifying a user profile may also include that of the first UI device 112 receiving a user ID associated with the user profile, wherein the user ID is currently on a second UI device 112 can be logged in.

The server 150 can determine if a previous session exists (block 2115 ). The finding can z. B. include that from the first UI device 112 a session ID is requested that is associated with the previous session. In some embodiments, the determination may include that of the first UI device 112 and receiving a session ID in response to the request for a session ID. In some embodiments, the determination may include identifying the session ID received with the session request.

The server 150 can instantiate a new session that corresponds to the previous session if there is a previous session (block 2115 ). Alternatively, the server 150 instantiate a new session if there is no previous session, where the new session can be instantiated using a default session configuration. Instantiating a new session according to a previous session may include determining whether a session ID has been received with the session request. If a session ID was received with the session request, the server may 150 instantiate a session associated with the session ID. If no session ID was received with the session request, the server can 150 Instantiate a session associated with a current session, such as a session. For example, with the most recent session of a user ID associated with the first UI device 112 is linked.

In some embodiments, the method 2100 also the server 150 include the second UI device 112 sends a request, on the first UI device 112 instantiate a session that corresponds to the session running on the second UI device 112 is in operation. method 2100 can also include that server 150 receives a confirmation from the second client device.

22 is a flowchart of a second method 2200 to initiate a UI session on a first UI device 112 , method 2200 may be implemented, in whole or in part, in one or more devices or systems, for example, the process control network 100 , In particular, methods can 2200 , in whole or in part, may be implemented on one or more devices or systems, for example the server 150 , or one or more devices or systems such as the UI devices 112 , method 2200 can be stored as a set of statements, routines, programs or modules in memory 815 or in memory 1203 stored and by the processor 810 or the processor 1201 be executed.

method 2200 starts with the server 150 from a first UI device 112 a session request (block 2205 ). Receiving the session request may include receiving a destination session ID and a device type.

The server 150 can identify a device type that matches the session request (block 2210 ) is linked. The server 150 can identify the configuration of a graphical user interface that corresponds to the device type (block 2215 ) corresponds. The server 150 can identify a target session that matches the session request (block 2220 ) is linked.

The server 150 Can a new session for the first UI device 112 that corresponds to the identified configuration of the graphical user interface and the identified target session. The server 150 can be sent to the first UI device 112 transfer the data associated with the new session (block 2225 ). Configuring the new session may include identifying session data as one or more process areas, a device resource, or a series of process data that is being monitored or controlled in the target session. Configuring the new session may also include configuring the new session according to the restrictions associated with the identified configuration of the graphical user interface. Configuring the new session may further include identifying context data associated with the session request.

Identifying context data may include: identifying a location of the first UI device 112 in the process plant; Identifying a user type or user ID associated with the session request; Identify a user type or user ID that matches the first UI device 112 linked; Identifying one or more process control devices at a predetermined distance from the first UI device 112 ; Identify a feature on a second UI device 112 that is associated with the target session; or identifying a user ID associated with a second UI device associated with the target session.

context sensitivity

23 illustrates a second aspect of an exemplary mobile control center 2300 - context sensitivity. The mobile control center 2300 includes a UI device 112 and a process unit 199 , The process unit 199 can be a current task, a user, a process area, a device, a piece of equipment, or another UI device. The mobile control center 2300 can respond to one or more contexts in combination, and it can respond to the one or more contexts in several ways, as described below. In general, the UI device calls 112 Information about which data is displayed and the format in which the data should be displayed, and retrieves or displays the data according to the context.

In some embodiments, the information indicating the types and format of the data to be displayed is included in an extended device description language (DDL). A DDL is a human-readable language that provides a protocol for: describing the data from a smart device; The meaning of the data associated with and retrieved from the smart device; the methods available for implementing the smart device; the format for communicating with the smart device to obtain data, device user interface information (eg, editing of displays and menus), and data necessary for handling or interpreting other information related to the smart device, to obtain. An advanced DDL may include, among other things: what information should be displayed for different types of users; how should the information displayed to different types of users be formatted; which information should be displayed on different types of displays; how to format the information displayed on different types of displays; what information should be displayed in the light of an objective function (ie what information should be displayed, when a user performs a particular task); how to format the information displayed to a user performing a specific task; and how to combine statements that correspond to different profiles that are made up of different users, objective functions, and display types.

The UI device 112 can use the DDL or advanced DDL for a particular device from the server 150 download when the UI device 112 located near a particular process control device, and / or when the user requests the display of the information related to the process control device. In some embodiments, the UI device may 112 cache the DDL or extended DDL (collectively referred to herein as "DDL") for later use after it has been used. By caching the DLL for a device, the UI device can 112 provide the display information faster when a particular context or ad is activated / requested. The UI device 112 can update the DDL data in the background if the DDL has changed. The DDL may change due to the following: user settings; Standards for the process plant; Findings of the expert system about what information is useful in a particular context (eg, when the expert system determines that a particular parameter or value is important in the event of an alarm, etc.), and the like.

In a particular embodiment, the mobile control center 2300 and in particular, the UI device carried by a user 112 Display user information (eg, status, process variables and / or parameters, etc.) related to a particular process control device that is in proximity to the user. The UI device 112 may change the location of the UI device as described below 112 notice and / or notice that the UI device is 112 located near the process control device. After it was determined that the UI device 112 located near the process control device, the UI device can 112 retrieve or access a DDL indicating device-specific data (eg, process parameters, status, maintenance information, etc.) to be displayed, and then download and display the device-specific data corresponding to the DDL. In some embodiments, the data displayed for a particular process control device may relate to data related to other process control devices, such as data about the operation or status of neighboring devices, data about the operation of the method (eg, state of a batch process). Recipe) etc.

In another embodiment, the UI device may 112 View information that is not just the location of the device and / or its proximity correspond to the device to a particular process control device, but also those that correspond to the user and in particular the control area of the user. In process control, the control area refers to the role of the user and to the tasks and equipment for which the user is responsible. The control scope of a user may affect various aspects of the process, e.g. For example, the process parameters that the user can view; the process parameters that the user can change; the times at which the user can change process parameters; the areas and / or devices of the process plant that the user can view / change; the alarms / warnings that the user can confirm; the maintenance tasks that the user can perform; the decisions that the user should or can make, etc. Therefore, the UI device may 112 in such embodiments of a user profile for the user (on the UI device 112 or on the server 150 stored) retrieve information about the user's role and / or control area and display the specific data for that role and / or that control area of the user. For example, the displayed data may be useful in making the user's control decisions at a particular state of the plant, as long as the user is an operator. Also, those through the UI device 112 information formatted according to the role or control area of the user. For example, if the UI device 112 Located near a mixing container, the UI device used by an operator may 112 indicate the operating status of the tank, its capacity, its level, the temperature of the material in the tank, the pressure in the tank, the status of all the inlet / outlet valves that discharge or discharge material into the tank, the alarms or warnings related to the container as well as the status of a currently running batch recipe. If the same UI device 112 Used by a service technician near the same mixing vessel, the UI device can 112 show the status of the mixing vessel and the calibration data of sensors in the mixing vessel, the day the tank was last serviced and / or cleaned, a list of planned maintenance tasks for (or in relation to) the mixing vessel, all alarms required for maintenance the material in the container, all the barriers when the container is out of service, the presence of residues of vapors, etc.

In yet another embodiment, the UI device may 112 Display information that not only matches the location of the device and / or the proximity of the device to a particular process control device, but also those that correspond to an objective function. For example, a work task may be assigned to a user (eg, by the monitoring module 106 ). The UI device 112 may be aware (eg, due to the time the work task is scheduled to complete, due to the input of a user, etc.) that the user will perform a task related to the work task. When the user comes to or near a process control device that is related to the work item (ie, target device and target location), the UI device may 112 View information related to the specific task. Referring again to the example of the mixing container, a service technician performing a task related to cleaning or maintaining the container may call the UI device 112 the operating status of the container may be displayed and it may receive instructions or commands to deactivate the container, disable it, lock it or use other procedures necessary to commence the cleaning or maintenance function associated with the work task are linked. The UI device 112 can also get information from the monitoring module 104 extract, from the server 150 , from the big data system 102 or by one or more controllers to implement and / or support the maintenance functions and safe operation. As described in the above examples (eg in Example 4), the UI device 112 Extract information / data to increase security during a maintenance task. The implementation of these concepts is described in the following paragraphs.

In operation, it can be the mobile control center 2300 the UI device 112 provide information about the environment and the way the UI device is used 112 to recieve. For example, the UI device 112 its own location in a process plant by receiving position data from a stationary location device 118 identify, for example, from a GPS device or from a node to the in 1A shown process control network 100 , For example, the UI device 112 perform a context awareness routine and / or a location awareness routine that can track a user's location, schedule, qualifications, and / or progress on the work task. In other embodiments, the in 1A shown server 150 perform the context awareness and / or location awareness routine when the context awareness and / or site awareness routine with the UI device 112 communicated. Based on the tracking, the routine for context sensitivity and / or location awareness may allow the UI device 112 allow you to automatically identify and display equipment maps, photos or videos of the equipment, GPS coordinates and other information that matches a worker's location, or to assist mobile operators with navigation and equipment identification. Because a user may have certain qualifications, the routine can be for context awareness or the UI device 112 the appearance of the GUI configuration also or alternatively automatically to the qualifications and / or location of the UI device 112 to adjust. In another scenario, the context awareness routine may, for example, inform the user in real time about a newly opened work item or alarm associated with some of the equipment in its vicinity and for which the mobile worker is qualified, to take care of it. In yet another scenario, the context awareness routine may cause one or more applications that are specific to the user's location and / or qualifications to automatically be on the UI device 112 to be started.

The UI device 112 may identify a particular process entity, such as a field device or a portion of the equipment in its vicinity. The process units can join the UI device 112 automatically identify itself, for example by using a wireless communication protocol such as a IEEE 802.11 compliant wireless local area network protocol, mobile communication protocol such as WiMAX, LTE or other ITU-R compatible protocol, short wavelength radio communication protocol such as near field communication (NFC) or Bluetooth, wireless process control protocol such as Wireless HART or any other suitable wireless communication protocol. In some embodiments, the UI device may 112 Get plans or work items that are relevant to the identified location, equipment, or field device. In a particular embodiment, identifying a process entity may cause the UI device 112 automatically start one or more applications concerning the identified process unit, e.g. For example, a work order, a diagnosis, an analysis, or another application.

In some embodiments, the UI device may 112 during operation, the process unit 199 via an image sensor on the UI device 112 identify. In some cases, the user of a UI device 112 a picture of the process unit 199 make and the UI device 112 can the process unit 199 based on the captured image. In some embodiments, the process unit 199 a context ID device 198 include, or are close to, a unique ID or ID (eg a barcode). The UI device 112 can capture the unique ID, leaving the UI device 112 the process unit 199 or the context ID device 198 can identify. The UI device 112 can provide information (for example, via a display) that is relevant to the process unit 199 or for the context ID device 198 are relevant. In some embodiments, the UI device may 112 the location of the UI device 112 determine by the location of the identified process unit 199 or the context ID device 198 is detected. Once the location of the UI device 112 was determined, the UI device can 112 Provide contextual information (for example via a display) that is relevant to the position determined. For example, the context information may relate to other process entities in the field, schedules, or work items. In some embodiments, the context ID device may 198 the context information to the UI device 112 transfer. In other embodiments, the UI device may 112 the context information from the server 150 in response to the transfer of his location to the server 150 receive.

In some implementations, the UI device may 112 the process unit 199 determine via a motion sensor or an audio sensor. For example, the audio sensor can be used to capture audio data that the process unit 199 are assigned (eg via a sound detection routine). The sound may occur during normal operation of the process unit by the process unit 199 be generated. In other implementations, the sound may be generated by the speaker of an audio device connected to the process unit 199 is linked. In any case, the captured audio data can be used to control the process unit 199 to identify. The UI device 112 can also detect vibrations via a motion sensor to the process unit 199 to identify. For example, a plant part may have an expected vibration level during operation. A user can use the UI device 112 place on or near the equipment. The UI device 112 can use the data detected by the motion sensor to identify the current vibration level of the equipment. The UI device 112 can correlate the current vibration level with a characteristic vibration associated with the process unit 199 connected, so the UI device 112 the process unit 199 can identify. In some cases, a motion sensor and / or an audio sensor may be used along with another identified image / sound / vibration / location to identify a unique ID. For example, the UI device 112 based on the detected vibration level associated with a plant part and the location of the UI device 112 to identify a specific day with the process unit 199 linked to the UI device 112 , the process unit 199 can identify.

In further operation, the UI device 112 its own location by receiving position data from one or more GPS satellites 2303 identify. After identifying his location, the UI device can 112 communicate with a database or server to identify process units with locations that are near the location of the UI device 112 are located. The UI device 112 can its location to the server 150 transfer. The server 150 can return context information back to the UI device 112 transfer. The context information may refer to one or more process areas, devices, or equipments near the UI device 112 Respectively. The context information may also refer to schedules or work items that are related to the location of the UI device 112 are relevant.

The 24 - 27 , which are described below, provide a more detailed explanation of the operation of the context awareness routine in various embodiments of the present disclosure.

24 Figure 12 is a block diagram of an exemplary context sensitive UI device 112 in a mobile control center 2400 , The context-sensitive mobile control center 2400 It may be the UI device 112 to generate expenses in response to its environment and the nature of its use. The context-sensitive mobile control center 2400 can a device for context identification ("context ID device") 2402 , the UI device 112 and the server 150 contain. The UI device 112 can with the context ID device 2402 interact to identify context data or context elements. In certain embodiments, the context ID device may 2402 via Wi-Fi or LAN channels with the UI device 112 communicate. In certain embodiments, the context ID device may 2402 Process parameter data and / or display data to the UI device 112 transfer. The context ID device 2402 can use an image identification technology (such as bar code or QR code), an audio identification technology (sending a unique sound signature) or a wireless radio frequency technology such as RFID, NFC, Bluetooth or Wi-Fi ( IEEE 802.11 standard ) use. The UI device 112 can be over a network like the process control network 100 with the server 150 communicate. In other embodiments, the context ID device may 2402 in the UI device 112 and a device (such as a PLC device) can receive a signal from the context ID device 2402 receive and the location of the UI device 112 to the server 150 Report.

In any case, the server can 150 context data 2410 to save. The context data can The following include: User profile data 1245 (in terms of user / operator in the attachment), profile data of the UI device 2414 (in relation to the UI devices registered in the installation), field device profile data 2416 (in relation to the devices installed in the system), profile data of the equipment 2418 (in relation to the equipment installed in the plant), planning data 2420 (in terms of users and equipment / equipment plans) as well as work item data 2422 (in terms of tasks or work in the system). In some embodiments, the field device profile data 2416 in the profile data of the equipment 2418 be included. The user profile data 1245 may include data on qualifications that indicate a skill level or level of responsibility associated with a particular user. Task data 2422 can data such. For example, a task ID (identification of a particular task), a qualification threshold (indicating a minimum qualification or role / responsibility necessary to perform the task), target equipment (the equipment associated with the task) and progress in the task ( Determining how close the task is to complete). Each of the context elements 1245 and 2414 - 2422 may include location or area information (associated, for example, with a user, device, equipment, schedule, or work item), status, related processing units, unique IDs / tags, and / or authorization information.

During operation of the context ID device 2402 can be the context ID device 2402 include a unique ID or tag that is read, scanned, or otherwise on the UI device 112 can be received when the UI device 112 into the area of the context ID device 2402 arrives. The scope of the context ID device 2402 is of the specific embodiment of the context ID device 2402 dependent, but can be as small as a few inches or less, or up to a mile or more in size, or have any value in between. In some embodiments, the context ID device may 2402 the unique ID to the UI device 112 transfer. In other cases, the context ID device may 2402 View or otherwise provide the unique ID so that it is from the UI device 112 can be received and / or retrieved.

In any case, the UI device can 112 receive the unique ID and identify a context item, such as an area (ie, a location, geographic area, or region), equipment, devices, work items, or available schedules in the environment of the UI device 112 by correlating the unique ID with the context element. For example, the UI device 112 Access a database, table or data structure that pairs unique IDs with specific context elements. Such a database or table can be on the UI device 112 , on the context ID device 2402 or on the server 150 to be available. If the database or table on the server 150 is present, the UI device can 112 the unique ID to the server 150 transfer. The server 150 can access a database, table, or other data structure to identify the context element with the unique ID. The server 150 can transfer data to the UI device 112 opposite the context element.

Once the UI device 112 has identified a context item, the UI device may 112 generate an output that is relevant to the identified context item. For example, the context item may indicate particular areas, devices, equipment, or alarms associated with an area. The UI device 112 may generate visual representations, sound or other outputs associated with the particular devices, equipment or alarms to inform the user of the process conditions in the process area. Likewise, there may be a number of devices or alarms associated with an identified device. The UI device 112 can provide information about the devices or alarms associated with a device (from the field device profile data 2416 ). Similarly, the context item may cause the UI device 112 Provides information related to equipment (from the profile data of the equipment 2418 ), or with schedules (from the schedule data 2420 ) or with work tasks (from the work task data 2422 ).

In certain embodiments, one or more process controllers in the process plant may include context ID devices 2402 be. In other embodiments, the one or more process control devices may include context ID devices 2402 contain or context ID devices 2402 be assigned nearby. For example, one or more of the in 1A shown field devices 15 - 22 and or 40 - 58 Context ID devices 2402 These may include or be positioned in the vicinity thereof (eg, the context ID device 2402 attached to or near each of the field devices, or the field devices may have an internal circuit for the field devices to function as Context ID devices). Also control 11 , Gateway 35 , UI device 112 , I / O card 26 and 28 and the in 1A shown router 58 can be a context ID device 2402 be, include or are in the vicinity thereof. In such embodiments, the UI device may 112 receive the unique ID associated with each of the context ID devices 2402 is assigned, so the UI device 112 a context item (such as location or equipment ID) associated with one of the process control devices.

In alternative embodiments of the context sensitive mobile control center 2400 can the UI device 112 be or provide a unique ID. For example, the UI device 112 have on the device a clearly scannable image or a chip that transmits the unique identification data. In another example, the user of the UI device may 112 carry a company badge, card or other accessory with a corresponding image or chip. In such embodiments, the context ID device may 2402 read, scan or otherwise receive the unique ID. The context ID device 2402 can work so that it has the unique ID with a specific user or UI device 112 combines. The context ID device 2402 can map the unique ID to a specific user or UI device by pointing it to a context ID device 2402 stored data structure accesses. Alternatively, the context ID device 2402 the unique ID to the server 150 transfer, with the server 150 the unique ID maps a specific user or UI device.

In any case, once the context ID device 2402 the UI device 112 or has identified the user, the context ID device 2402 relevant context elements to the UI device 112 transfer. Alternatively, the context ID device 2402 communicate with one or more nodes in a network, e.g. The process control network 100 to notify the node or nodes that the user or the UI device 112 into the area of the context ID device 2402 has arrived. The node (s) may include one or more context elements, UI data (eg, display data, process parameter data), or other data to the UI device 112 transfer. The UI device 112 can work on the basis of the received data or provide expenditures. For example, the UI device 112 in certain embodiments, in response to receiving the unique ID, context element, UI data, or other context ID device data 2402 or from the server 150 start a target application. The target application may be, for example, an application intended to provide process graphics and information to the user. The target application may be, for example, a mobile application running on mobile phones or tablet devices. In other embodiments, the target application may be the browser routine 888 be. In certain cases, the browser routine 888 directed to a particular resource or group of resources associated with the received unique ID, context item, UI data, or other data.

In some embodiments, the context ID devices may 2402 Be part of an authorization system. For example, privileges associated with a process entity may be near a UI device 112 depend on the process unit. In some embodiments, a UI device may 112 get the permission or permission to change a parameter associated with a process unit when the user or the UI device 112 are near the process unit. The UI device 112 may also refuse the permission to participate in a work item or to change a parameter if the user's qualification level is below the specified qualification threshold associated with the task or parameter.

25 is a block diagram of another embodiment of a mobile control center 2500 in a process plant 10 , The context-sensitive mobile control center 2500 It may be the UI device 112 to generate expenses in response to its environment and the nature of its use. The mobile control center 2500 can the UI device 112 include that with the process control network 100 connected, including the areas 2505 - 2515 and a container 2520 , The UI device 112 is with the process control network 100 connected. The area 2505 includes a context ID device 2402a ; the area 2510 contains a context ID device 2402b , the process area 2515 includes a context ID device 2402C , and the container 2520 includes a context ID device 2402D ,

In one embodiment, the context ID device is 2402a an NFC device or includes such. The UI device 112 and the context ID device 2402a generally work at 13.56 MHz and can be compliant with NFC standards such as ISO / IEC 14443 . ISO / IEC 1809 , NFCIP-1, NFCIP-2 and JIS: X6319-f. NFC technology enables wireless transactions and data exchange between the UI device 112 and the context ID device 2402a , NFC technology can also be used to perform automatic bootstraps from other communication links. In such an embodiment, the context ID device may 2402a Instructions to the UI device 112 transfer. The UI device 112 can receive and execute the instructions, which causes the UI device 112 connects to another network. In some embodiments, the other network may be a larger network, e.g. The process control network 100 that includes other nodes. In certain embodiments, the other network may connect between the UI device 112 and the context ID device 2402a be. For example, the other network may be an ad hoc wireless network or a personal area network (eg, Bluetooth, IEEE 802.15.1 standards ) be. In In any case, the context ID device can 2402a in addition to the instructions of the network connection, the authentication information to the UI device 112 transferred, leaving the UI device 112 can connect to a network without the user of the UI device 112 manually set up the network and enter the authentication information.

Further operation of the context ID device 2402a can be the NFC tag or the device on the context ID device 2402a also save other statements on the UI device 112 can be executed. For example, the instructions may result in one or more applications being started or executed in a particular manner. In the illustrated embodiment, the instructions may cause the UI device 112 a unique ID (like the UI routine 882 out 8th ) or a browser (like the browser routine 888 out 8th ) or that the unique ID or browser is put into a specific state. The instructions can cause the UI device 112 Provides a GUI configuration with information related to the devices and equipment in the area 2505 belong. For example, the GUI configuration may be a window with a graphical overview of the process area 2505 contain.

In the further operation of context ID device 2402a can the UI device 112 from the context ID device 2402a via an NFC communication or over a network that the UI device uses 112 after receiving authentication information via an NFC communication, receive a unique ID. The unique ID generally represents the area 2505 However, in certain embodiments, it may also represent other contextual elements. The UI device 112 can use the unique ID to identify the context item (for example, area 2505 ) and to work according to the identified context item or to provide outputs (eg providing a graphical overview of the area 2505 ). Alternatively, the context ID device 2402a a unique ID from the UI device 112 receive and the UI device 112 (or its user), identifying the context ID device 2402a or another node in the process control network 100 Data, such as For example, context data or UI data, to the UI device 112 may transfer. The UI device 112 can work on the basis of the received data or provide expenditures.

In one embodiment of the context ID device 2402b is the context ID device 2402b an RFID tag or includes such. In such an embodiment, the UI device includes 112 an RFID scanner, and it uses the RFID scanner to get a unique ID. The unique ID generally represents the area 2510 However, in certain embodiments, it may also represent other contextual elements (eg, certain devices, equipment, locations, etc.). The UI device 112 may use the unique ID to identify the context item in accordance with the methods described with respect to FIG 24 were discussed. In an alternative embodiment, the context ID device may 2402b be an RFID scanner, and the UI device 112 can contain an RFID tag. In such an embodiment, the context ID device identifies 2402b the UI device 112 if the UI device 112 in the scope of Context ID device 2402b (for example, when the user enters the area 2510 enters). After identification of UI device 112 can be the context ID device 2402b with the UI device 112 communicate (eg with the process control network 100 , with another network, such as a personal area network, or via a display) and the unique ID to the UI device 112 or to the server 150 which can use the unique ID to provide contextual information for the UI device 112 provide. The UI device 112 can the area 2510 Identify in accordance with the procedures with regard to 24 have been discussed, and it can be based on the identified area 2510 provide work or spend. In another embodiment, the context ID device may 2402b the context element (rather than the unique ID) to the UI device 112 transmitted (for example via a wireless local area network communication such as Bluetooth). In yet another embodiment, the user may instead of or in addition to the RFID tag of the UI device 112 have an RFID tag. In either of these embodiments, both the RFID scanner and the RFID tag may be active or passive. The UI device 112 can work on the basis of the received data or provide expenditures.

In operation of an embodiment of the context ID device 2402C can be the context ID device 2402C a wi-fi access point with an area that defines the process area 2515 covers. If the UI device 112 in the process area 2515 can get the context ID device 2402C the communication with the UI device 112 produce. The context ID device 2402C can give a unique ID to the UI device 112 transferred, z. For example, a MAC address or a device tag. The unique ID generally represents the area 2515 However, in certain embodiments, it may also represent other contextual elements. The UI device 112 can use the unique id to name the context element (for example, data that represents the area 2515 represent) with the procedures to be identified with regard to 24 it can work according to the context item or provide outputs (e.g. B. a visual representation of the area 2515 ). For example, a database that pairs MAC addresses or device tags with particular areas may be on the UI device 112 save on it can from the UI device 112 or it can be stored on a node connected to the UI device 112 communicated. Alternatively, the UI device 112 a unique ID to the context ID device 2402C transmit, for example, a MAC address of the UI device 112 , Upon receipt of the unique ID, the context ID device may 2402C be operated so that it determines if the UI device 112 is assigned to the unique ID. The UI device 112 can work on the basis of the received data or provide expenditures.

In one embodiment of the context ID device 2402D can be the context ID device 2402D include a barcode. The barcode may be a matrix barcode (eg a QR code) or a linear barcode (eg a UPC barcode). The UI device 112 may include an image sensor, which may be a camera or a specific barcode scanner, or communicate with it. In operation, the UI device 112 Use the image sensor to get the barcode on the context ID device 2402D capture. The UI device 112 can decode the barcode encoded data ("barcode data"). The barcode data generally contains a unique ID identifying the container 2520 (or any other process control device or equipment attached thereto); however, in certain embodiments, the unique ID may also represent other contextual elements. The UI device 112 can use the unique ID to identify the context item (for example, data representing the container 2520 represent) with the procedures to be identified with regard to 24 it may work according to the context item or provide outputs (eg, a visual representation of the container 2520 ). In alternative embodiments, the barcode may include data or instructions that cause the UI device 112 takes certain measures, eg. For example, launching a browser or UI so that the browser or UI provides certain information. The particular information may refer to any number of processing units, e.g. On process parameter data, graphics of certain elements (eg tank 2520 ) or alarm data for a specific device. In other embodiments, the UI device may 112 or the user of the UI device 112 alternatively, or also include a barcode provided by the context ID device 2402D captured the context ID device 2402D the UI device 112 or identify the user. A barcode on the UI device 112 can also provide instructions to the context ID device 2402D be executed. For example, the barcode may cause the context ID device 2402D relevant information for the user or the UI device 112 provides.

In some embodiments, the UI device may 112 Identify the unique ID with other methods. For example, the UI device 112 use an audio sensor to identify a unique ID if the unique ID is a sound signature (as related to 24 mentioned), which is assigned to a plant area / plant part. The sound signature can be assigned to the sounds of a specific plant area / plant part that are generated during operation. Alternatively, the sound signature may be an audio signal generated by an audio output device connected to the equipment part. The UI device 112 can also use a motion sensor to identify the unique ID. The unique ID may be a certain level of vibration associated with a piece of equipment. For example, a user may use the UI device 112 place on a piece of equipment, leaving the UI device 112 recognizes the vibrations. In some cases, a motion sensor may be used in conjunction with another identified image / sound / location to identify a unique ID. For example, the UI device 112 based on the detected vibration level associated with a plant part and the location of the UI device 112 to identify a specific tag associated with the piece of equipment.

In some embodiments, the UI device may 112 identify its position by receiving position data. The position data can be received over a network, e.g. Via the process control network 100 , Alternatively, the position data may be transmitted via a GPS receiver to the network interface of the UI device 112 be received. The UI device 112 can compare its location with that of other process units to process units near UI device 112 to identify. The UI device 112 can move its location to a node in the process network 100 transferred, for example, to the server 150 , In some embodiments, the node may communicate by transferring context information to the UI device 112 react. In other embodiments, the UI device may 112 the location data to a context ID device 2402 transfer. The context ID device 2402 can display context data according to the received position data to the UI device 112 transfer.

The UI device 112 may in certain embodiments interfere with the context ID device (s) 2402 cooperate to get real-time position data of the UI device 112 provide. If a mobile operator is a mobile UI device 112 through an environment, the UI device can 112 the Location information provided by (or as a result of) context ID devices 2402 was obtained, use the current location of the UI device 112 in the process plant, and it can display a current map of the location of the mobile operator in the area. The map may display the location of the mobile operator from a top view or in a three-dimensional perspective. Of course, a desired or expected route can also be done on the mobile UI device 112 are displayed. Alternatively, the UI device 112 Use one or more accelerometers to determine the orientation and position of the device within the environment, and it can work with an image sensor on the UI device 112 work together to display an augmented reality view of the environment. For example, the mobile operator can direct the image sensor to an area of the process plant, and the UI device 112 can display a diagram of the equipment throughout the image, it can display a route to a desired device (eg, equipment that belongs to a current work task), it can display parameters or other process data related to the area of the process plant are connected, and the like.

26 is a diagram of an exemplary mobile control center 2600 , The mobile control center 2600 can be a first UI device 2602a , a second UI device 2602b , Equipment 2610 and equipment 2620 include. The first UI device 2602a can be an ad with a graphic 2615 include the equipment 2610 or other data showing with the equipment 2610 related (eg current operating parameters, setpoints, alarms, faults, scheduled maintenance, calibration data, etc.). The branch UI device 2602b can be an ad with a graphic 2625 include the equipment 2620 or other data showing with the equipment 2620 related (eg current operating parameters, setpoints, alarms, faults, scheduled maintenance, calibration data, etc.). Equipment 2610 can be a first context ID device 2604a include, and the equipment 2620 can be a second context ID device 2604b include.

In operation, an operator can use the UI device 2602a carries an area around the context ID device 2604a to enter. The UI device 2602a can with the context ID device 2604a communicate or scan it to allow the UI device 2602a Data from the context ID device 2604a can receive. The UI device 2602a can work in response to received data or provide expenses. In the illustrated embodiment, the UI device 2602a the graphic 2615 provide the equipment 2610 represents. In some embodiments, the UI device may 2602a provide alternative or additional expenses, e.g. Other graphics, process parameter values or alarms. The operator of the UI device 2602b can carry the scope of the context ID device 2604b enter, which causes the UI device 2602b the graphic 2625 which provides the equipment 2620 represents.

27 is a flowchart of an exemplary method 2700 to generate a graphical user interface. method 2700 may be implemented, in whole or in part, in one or more devices or systems, for example in one of the UI devices 112 , method 2700 can be stored as a set of statements, routines, programs or modules in memory 815 stored and by the processor 810 be executed.

method 2700 starts when the UI device 112 an external device or an ID / tag (block 2705 ) identified. The ID can be a picture, sound, or barcode. The ID may alternatively be a unique tag associated with transmission through an NFC system or RFID system. In some embodiments, the ID may be associated with a process entity, e.g. B. with a process area, a device, a piece of equipment or another UI device 112 ,

The UI device 112 can receive context information based on the identified external device or ID (Block 2710 ). In some embodiments, the UI device may 112 receive context information from the identified external device or ID. In other embodiments, the UI device may 112 the context information from the server 150 in response to the transmission of data received to the server 150 opposite the ID represent. The context information may represent contextual elements such as location, equipment, schedules, work items, etc.

The UI device 112 can display information for the UI device 112 (Block 2715 ) provide. The information may be provided according to the received context information. For example, the UI device 112 Generate information relevant to a received location, identified equipment or devices, received schedules, or work items.

With reference to 28 a flowchart illustrates an exemplary method 2800 that on a UI device 112 for controlling the process plant 10 using the UI device 112 is performed. method 2800 may be implemented, in whole or in part, in one or more devices or systems, for example, the process control network 100 , In particular, methods can 2800 , completely or partially, implemented on one or more devices or systems, for example the server 150 , or one or more devices or systems such as the UI devices 112 , method 2800 can be stored as a set of statements, routines, programs or modules in memory 815 or in memory 1203 stored and by the processor 810 or the processor 1201 be executed.

The procedure starts with a UI device 112 that to the server 150 over a network, a first request of first data from a first data storage area (Block 2805 ) can transmit. The data storage area may be a unified, logical data storage area containing one or more devices configured to store, using a common format, process data corresponding to the process plant. The process data may include several types of process data, e.g. Configuration data, continuous data, batch data, measurement data and event data.

The UI device 112 can, from the server 150 and in response to the first request, the first data from the storage area (Block 2810 ) received. The UI device 112 can be the first from the server 150 (Block 2815 ) received data.

The UI device 112 may get an indication that the UI device is down 112 close to an external device (block 2820 ) is located. The UI device 112 may include a communication circuit that functions to detect the proximity of external devices. The communication circuit may include a Near Field Communication NFC) circuit, a Radio Frequency Identification (RFID) circuit, a Bluetooth circuit, a circuit following the IEEE 802.11 Protocol, or a circuit that works according to the wireless HART protocol. In some cases, the UI device may 112 received an indication that the UI device 112 close to an additional UI device 112 located.

The UI device 112 may, depending on the received hints, make a second request for second data to the server 150 transferred (block 2825 ). In some embodiments, transmitting the second request includes transmitting a request for status information about the additional UI device 112 to the server 150 ,

The UI device 112 can, from the server 150 and in response to the second request, the second data (Block 2830 ) received. In some embodiments, the second data may include the requested status information of the additional UI device 112 represent. In such embodiments, the UI device may 112 in accordance with the received status information, also display process control data from the storage area. Viewing the process control data may duplicate the display of the additional UI device 112 , on the display of the UI device 112 include. Viewing the process control data may involve arranging the data stored on the additional UI device 112 displayed on the UI device display 112 include.

In other embodiments, receiving the proximity indication (block 1720 ) receiving a notice that the UI device 112 is near a process control device. The transmission of the second request (block 2825 ) can transmit a note to the server 150 include that the UI device 112 located near the process control device. In such embodiments, receiving the second data may include receiving process control data related to the process control device (block 2830 ). Receiving process control data related to the process control device may include receiving and displaying data from one or more of the following: an alarm associated with the process control device; from a maintenance task associated with the process control device; of a schematic representation of the area of the process plant, which is assigned to the process control device; or a status of an area of the process plant associated with the process control device.

In some embodiments, receiving the proximity indication (block 2820 ) include receiving an indication that the mobile device is in a particular area of the process plant. In such embodiments, transmitting the second request (block 2825 ) can transmit a note to the server 150 include that the UI device 112 located in the specific area of the process plant. In addition, receiving the second data (block 2830 ) comprise receiving second process control data related to the particular area of the process equipment. Receiving process control data related to the particular area of the process plants may include receiving and displaying data from one or more of the following: an alarm associated with the particular area of the process plant; from a maintenance task associated with the particular area of the process plant; from a schematic representation of the specific area of the process plant; or a status of one or more Process control devices associated with the particular area.

In certain embodiments, the UI device may 112 not with the server 150 but it can communicate with the equipment in a particular area. For example, the UI device may 112 can be located in the area of the process plant in the vicinity of a certain part of the process equipment, and it can, with or without an intermediary device (eg, via a router or other access point that is part of a wireless network) several devices (not the server 150 are) communicate in the area of the process plant. This can be the case, for example, if the server 150 is not available or if the area of the process plant is physically or logically off the server 150 is disconnected. In any case, the UI device can 112 Send data or requests directly and / or receive data directly from devices in the area of the process plant. For example, the UI device 112 a request for data over a network directly to another device (rather than to the server 150 ), it can receive data from the device in response to the request, it can display the received data, it can receive an indication that the UI device is receiving 112 located near an external device, etc.

A flowchart of a procedure 2900 to simplify the mobile control of a process plant, shows 29 , method 2900 includes the implementation of a mobile UI device (block 2905 and providing a location awareness component in the mobile UI device that is configured to generate information related to the location of the mobile device (Block 2910 ) belong. method 2900 also includes the provision of a database in the layout information of the process plant (block 2915 ) and the implementation of a first routine on the mobile UI device (Block 2920 ). The first routine may be arranged to interpret information generated by the location awareness component in accordance with the information stored in the database to establish a relationship between the location of the mobile UI device and the location of the process plant , The mobile UI device may also implement a second routine that operates to produce a graphics for display on the display that matches the established relationship between the location of the mobile device and the layout of the process plant (Block 2925 ). In certain embodiments, providing a database that stores layout information may include providing the database that stores bird's-eye view layout information, or may include providing the database that stores layout information in an eye-level perspective. The layout information may include, for each process device, a device tag, a device visualization (eg, one or more visualizations, each corresponding to a type of mobile UI device or a display type of a mobile UI device), a device location, and connection information from Devices include. The location awareness component may be, for example, a GPS receiver, an RFID reader, an RFID tag and a communication channel between the mobile UI device and a server providing data for the mobile UI device, multiple sensors (e.g. Accelerometers and gyroscopes) which serve to detect the movement and position of the mobile UI device, etc., relative to an anchor point. Implementing the second routine includes, in some embodiments, implementing a routine to generate a real-time graphical representation of the location of the mobile UI device within the process plant as the UI device moves within the process plant. Generating a real-time view of the location of the mobile UI device may include displaying the location of the mobile UI device on a bird's-eye view, or displaying the location of the mobile UI device on a display in three dimensions in one perspective at eye level.

It should now be clear that the UI devices 112 and, in some embodiments, the control network 100 , Be aware of various contextual information, including especially the location of one or more of the UI devices 112 in the process plant 10 , Various methods have been described, such as the control network 100 (including the server 150 ) or the UI devices 112 determine the location of a device. For example, the UI device 112 with context ID devices 2402 and / or the server 150 work together to locate a UI device 112 to determine. The UI devices 112 can also use the GPS receiver 832 include through which the UI devices 112 determine their location by receiving signals from GPS satellites, as is well understood. However, in some embodiments, one or more of the UI devices may 112 also the inertial positioning system (IPS) 834 for inertial positioning. The IPS 834 may take the form of discrete components or an integrated circuit. In at least one embodiment, the IPS is 834 an integrated circuit having a high precision clock circuit, three accelerometers (one each on the x, y, and z axes), and three gyroscopes (one each on the x, y, and z axes). In some Embodiments include the IPS 834 also a compass or magnetometer.

In any case, the IPS 834 be operated so that it controls the movement and orientation of the UI device 112 where it exists, recognizes and that it provides information about the distance and the direction in which the device has moved or moved. By combining information about the detected motion and orientation of the UI device 112 with another source of information that has an initial location (an "anchor point") of the UI device 112 indicates the UI device 112 determine its location independently of any permanent source of information. For example, a UI device 112 , which is carried by an operator, have a GPS receiver, and can determine the location of the UI device 112 track when the operator is moving through an outdoor area towards an indoor area. As the operator crosses the boundary between the exterior and interior, the UI device becomes 112 and especially the GPS receiver 832 probably lose the GPS signal. The UI device 112 can be the last known location of the UI device 112 using the GPS receiver 832 was determined to use as anchor point. From the anchor point, the UI device can 112 determine the route and the direction in which the UI device 112 moved in the interior. With the help of this information, the UI device can 112 , Routines running on the UI device 112 are in operation, and possibly other devices (such as the server 150 , the monitoring module 106 , etc.), continue to locate the UI device 112 follow. The UI device 112 may further provide the operator with a representation of the operator's location in the interior, may provide the operator with navigation instructions to a particular piece of equipment (eg, to a particular piece of equipment), or take action based on the location of the operator in the equipment recommend, and so on.

It is noted that the GPS receiver 832 Not the only source of information that is an anchor point for use in combination with the IPS 834 can represent. Each of the context ID devices 2402 can also work with the UI device 112 work together to determine an anchor point. For example, if the operator crosses the border between the exterior and interior, a context ID device may 2402 at the border (eg an NFC device on a doorframe) with the UI device 112 communicate to determine the location of the UI device 112 and to provide an anchor point. As another example, the operator may use the UI device 112 for scanning or otherwise interacting with a context ID device 2402 use (eg, with an RFID tag, an NFC chip, a barcode, etc.) at any known, fixed position in the process plant (eg, on a process device, near a particular location) Plant area, etc.) to create an anchor point.

The UI device 112 can be the anchor point and information provided by the IPS 834 be deployed, use on the display of the UI device 112 the location of the UI device 112 in the process plant or another environment. In certain embodiments, this includes the representation of the site on a floor plan of the process plant, the representation of the location on a 3D map of the process plant, the representation of the site on a schematic representation of the process plant, etc. Alternatively or in addition, the UI device 112 Provide navigation information to direct the operator to a desired location in the process plant (eg, to a job with an associated work item, to a selected location, to a device with a fault or alarm, etc.). In some embodiments, the UI device may 112 Provide navigation or position information to guide an operator to other people in the plant environment. This can be useful, for example, when trying to find injured employees or people who have requested help for a task.

Each UI device 112 that has positional data, be it GPS data, IPS data, or collaboration with Context ID devices 2402 provided, can be the location of the UI device 112 for the control system, especially for the server 150 and / or the monitoring module 106 , In some embodiments, the presence of the UI device may 112 in a certain area cause the server 150 , the monitoring module 106 or the UI device 112 one or more features of the UI device 112 disabled. For example, the microphone 842 and / or the camera 844 be disabled when the UI device 112 located in an area where operator privacy may be important (eg in a laundry room) or where safety considerations require it.

Likewise, in some embodiments, various control aspects of the process plant may be altered by the presence of persons in an area. For example, certain security systems may have a first threshold when there are no people in the area and a second, more conservative threshold when there are people in the area. In this way, the safety of persons can be improved.

30 is a flowchart of a procedure 3000 for determining the position of a mobile device in a process control environment. method 3000 includes the detection of an anchor position within a process plant (block 3005 ) and determining the anchor position according to the acquired data (Block 3010 ). The method also includes receiving data from the mobile device circuitry indicative of the acceleration and orientation of the mobile device (block 3015 ), and determining a position of the mobile device based on the received data and the anchor position (Block 3020 ). In certain embodiments, acquiring data indicative of an anchor position comprises determining a location of the mobile device using a global satellite navigation system, e.g. GPS, GLONASS or any other satellite navigation system. Acquiring data indicating an anchor position, in some embodiments, includes capturing an image (eg, an image of a barcode, an image of a portion of the process plant, etc.). For example, where an image of a portion of the process plant is captured, the captured image may be compared to a database of geologically located images (ie, images associated with a corresponding physical location). The data indicating the anchor position could also include data from one or more wireless signals, e.g. B. signals that with a IEEE 802.11 Specifications that capture data from an RFID device, establish a Bluetooth connection, or set up a near field communication session. Collecting data indicative of the anchor position could also include determining a process control device near the mobile device and receiving or retrieving information from the memory (or from a remote database) associated with the location of the process control device connected is.

Receiving data indicative of acceleration and orientation of the mobile device includes receiving data from one or more accelerometers and one or more gyroscopes receiving data from a magnetometer. Various embodiments include receiving data from an inertial measurement unit and / or receiving data from a device that includes three accelerometers and three gyroscopes. In some embodiments, the method also includes starting an application of the mobile device based, at least in part, on the determined location of the mobile device, the application operating to modify the operation of the process plant.

Referring to 31 , a flowchart shows a method 3100 for the contextual operation of a mobile device in a process control environment. The method includes acquiring information on the mobile device to identify a process entity in the process control environment (Block 3105 ). The process unit may be any process unit in the process plant including, but not limited to, an area of the process plant, a process control device, a controller, and the like. The method also includes identifying the work item data associated with the process unit on the mobile device (Block 3110 ). The work item data includes information about a target function associated with the process unit. In response to the received information and the identified work item data, an event is automatically triggered on the mobile device to facilitate the implementation of the objective function associated with the process unit (Block 3115 ). The objective function can be a scheduled task assigned to the process entity. In certain embodiments, triggering an event on the mobile device includes at least one of the following elements: the mobile device provides instructions relevant to the execution of the scheduled task; the mobile device displays safety information (eg, the materials in a process control device, whether the process control device has been disabled and / or disabled, whether any residual material is detectable, etc.); the mobile device launches an application to perform the scheduled task; or the mobile device provides an interface for performing the scheduled task. The objective function, in some embodiments, may be a permission validation function associated with the process entity. The automatically triggered event may be identifying a user ID associated with the user operating the mobile device; identifying a permission token associated with the process entity; determining a privilege level based on the user ID and the privilege token; and providing an interface for modifying parameters associated with the process entity to the extent specified by the privilege level. The privilege level may specify the extent to which the user is allowed to change parameters associated with the process control device. The target function associated with the process unit could also be an alarm control function, and the triggering of an event may include identifying the alarm and providing an indication of the alarm. The objective function could be a location determination function, and the automatically triggered event could be the determination of a location associated with the process control device and providing a graphical map showing a location of the process entity within the process control environment. In certain embodiments, gathering information to identify a process entity comprises capturing one or more data variables from one or more corresponding identification devices having a fixed spatial relationship with a corresponding process entity in the process control environment and a unique ID. In certain embodiments, the context identification device is a bar code, and capturing the tag data includes capturing an image of the bar code and bar code analysis to identify the tag data. The context identification device may be a radio transmitter, and detecting the tag data may include detecting a radio frequency signal output from the radio transmitter carrying the tag data. The radio transmitter may be an NFC device, an RFID device or a personal network device that transmits short-wave radio transmissions. Acquiring information to identify a process entity in the process control environment includes, in certain embodiments, capturing an image that is uniquely associated with the process entity. Acquiring information may also be detecting an audio signal and determining that the audio signal correlates with the process unit. Likewise, acquiring information may include detecting a motion pattern associated with a process entity.

Analysis of physical phenomena

The UI devices 112 can, in certain embodiments, with the expert system 104 and the big data system 102 work together to analyze data related to physical phenomena. The physical phenomena that can be analyzed include, without limitation, phenomena related to light in the visible and invisible spectrum (eg, flame colors in visible and IR spectra), and phenomena relating to vibrations in the audible range and below and above the hearing threshold (eg sound and other vibrations). Staff, which is a UI device 112 worn with a camera, accelerometers, microphone or other equipment can be used to capture and / or record data related to the physical phenomenon. For example, a camera may capture and record an image in the visible region, or, in certain embodiments, in the infrared or other spectra. A microphone may sense and / or record audible vibrations and vibrations above and / or below the threshold of hearing transmitted through the air. Accelerometers can capture and / or record vibrations when the UI device 112 is placed on a piece of equipment. The individual and / or all of these types of data may be from the UI device 112 to the expert system 104 be sent to analyze the data and / or with the big data system 102 to compare.

32 shows a method 3200 for analyzing physical phenomena in a process plant. method 3200 includes detecting a physical phenomenon in the process plant in a mobile device (Block 3205 ). Detecting the physical phenomenon may, in various embodiments, include detecting a visual scene, a sound, and / or a vibration. By way of example, and not limitation, in various embodiments, detecting the physical phenomenon may include detecting a visual scene, including a flame, a sound associated with a combustion chamber, a sound associated with movement of a liquid , an image or video from the top of a stack and / or a vibration associated with a rotating element.

method 3200 Also includes the conversion of the detected physical phenomenon into digital data representing the physical phenomenon on the mobile device (Block 3210 ). That is, the physical phenomenon (the visual scene, the noise, the vibration, etc.) is used and converted into digital data, for example, in the form of a digital image, a digital video, a digital audio file, or a digital representation of the captured Vibration. Further includes method 3200 transmitting the digital data to an expert system (block 3215 ) and analyzing the digital data in the expert system to determine the status of one or more process elements (block 3220 ). For example, if the detected physical phenomenon is the visual scene of a flame, the analysis of the data may include the analysis of the colors associated with one or more portions of the flame, or it may be the shape of the flame and / or the movement of the flame to be analyzed; if the detected physical phenomenon is a sound or vibration associated with the movement of a liquid, the analysis of the data may be the detection of cavitation associated with fluid movement; If the sensed physical phenomenon is a visual scene from the top of a stack, the analyzed data may include an analysis of the color or amount of smoke evolution.

method 3200 may also, in various embodiments, have an abnormal condition associated with one or more process elements to determine from the digital data a cause of the abnormal state; to automatically initiate a change to one or more process control parameters to correct the abnormal condition; to automatically generate a work task that causes the personnel to take action to correct the abnormal condition; to advise an operator of a corrective action to be taken to end the abnormal condition; and / or to determine a fuel composition associated with a flame or combustion chamber.

The following additional considerations apply to the discussion above. Throughout this description, actions refer to the server 150 , the UI device 112 or any other device or routines, generally actions and processes of a processor that manipulates or transforms data in accordance with machine-readable instructions. The machine-readable instructions may be stored on and retrieved from a storage device connected to the processor. That is, the methods described herein may be embodied by a set of machine-executable instructions stored on a computer-readable medium (ie, on a storage device). The instructions, when executed by one or more processors of a corresponding device (eg, a server, a mobile device, etc.), cause the processor to perform the procedure. Whenever the terms "stored" or "stored on a computer-readable storage" or "stored on a computer-readable storage medium" are used herein for instructions, routines, modules, processes, services, programs and / or applications, the terms "stored" and " secured "so that they exclude transitory signals.

User interface devices are referred to interchangeably herein as "UI devices" and "mobile UI devices". While these devices are commonly referred to simply as "UI devices" in most instances, the term "mobile" is added in certain descriptions to indicate that, in a particular example usage, the UI device may be a mobile UI device , The use or absence of the term "mobile" should not be construed as limiting, as the concepts described herein are applicable to all UI devices that may be used in the environment of a process plant. Although many of the examples described herein relate to browsers that display information, each of the examples provides for the use of native applications that communicate with a server to provide information. The native applications can be developed for any mobile platform, any workstation operating system, or any combination of mobile platforms and / or workstation operating systems and / or web browsers. For example, a mobile UI device may run on the Android ^™ platform while a cooperating stationary UI device (eg, a workstation) is running on the ^Windows® 7 platform.

 Further, while the terms "operator", "personnel", "person", "user", "technician" and other terms are used to describe persons who use the systems, devices and methods described herein in the environment of the process plant or interact with them, these terms are not intended to be limiting. As can be seen from the above description, the systems, devices, and methods described herein may result in relieving the plant personnel to some extent of the traditional limitations offered by process control systems. That is, the operators may perform some activities traditionally performed by technicians, and technicians may participate in activities traditionally reserved for the operators, and the like. When used in the description a particular term is used, in part, because of the traditional activities involved in plant personnel, but it is not intended to limit employees who might be involved in the activity.

In addition, in this description, instances used in the plural may translate components, operations, or structures that are described as instances in the singular. Although individual operations are represented and described as separate operations by one or more methods, one or more of the individual operations may be performed concurrently, and nothing requires the operations to be performed in the order shown. Structures and functions that are included as separate components in example configurations may be implemented as combined structures or components. Similarly, structures and functions represented as a single component may be implemented as separate components. These and other variations, modifications, additions and improvements are within the scope of this topic.

Unless otherwise stated, discussions here may use terms such as "processing", "computing", "computation", "Determining", "identifying", "presenting", "displaying" or the like, refers to actions or processes of a machine (e.g., a computer) manipulating or transforming data that is considered physical (e.g. magnetic or optical) quantities in one or more memories (eg volatile memory, non-volatile memory or a combination thereof), in registers or other machine components that receive, store, transmit or display information.

When implemented in the software, any of the applications, services, and modules described herein may reside in any tangible, non-transitory computer-readable storage such as a magnetic disk, a laser disk, a solid state storage device, a molecular storage device, or other storage medium. stored in the RAM or ROM of a computer or processor, etc. While the exemplary systems disclosed herein are also to be construed to include, among other components, software, and / or firmware embodied on hardware, it should be understood that such systems should be considered illustrative rather than limiting. For example, it is conceivable that some or all of these hardware, software, and firmware components may be embodied solely in hardware, solely in software, or in a combination of hardware and software. Accordingly, one of ordinary skill in the art will readily recognize that the examples provided are not the only way to implement such systems.

Therefore, while the present invention has been described with reference to specific examples, which are to be considered illustrative and not restrictive, it will be understood by those of ordinary skill in the art that changes, additions or removals to the disclosed embodiments may be made without departing from the spirit and scope of the invention.

aspects

• 1. Ein Verfahren zum Bestimmen einer Position eines mobilen Geräts innerhalb einer Prozesssteuerungsumgebung, wobei das Verfahren folgende Schritte umfasst: Erfassen von Daten, die eine Ankerposition innerhalb einer Prozessanlage angeben; Bestimmen der Ankerposition gemäß den erfassten Daten; Empfangen von Daten aus den Schaltungen des mobilen Geräts, welche eine Beschleunigung und Orientierung des mobilen Geräts angeben; und Bestimmen einer Position des mobilen Geräts gemäß den empfangenen Daten und der Ankerposition.
• 2. Ein Verfahren nach Aspekt 1, wobei das Erfassen von Daten, die eine Ankerposition angeben, das Bestimmen einer Position des mobilen Geräts unter Verwendung eines globalen satellitengestützten Positionsbestimmungssystems umfasst.
• 3. Ein Verfahren entweder nach Aspekt 1 oder Aspekt 2, wobei das Erfassen von Daten, die eine Ankerposition angeben, das Erfassen eines Bildes umfasst.
• 4. Ein Verfahren nach einem der Aspekte 1 bis 3, wobei das Erfassen eines Bildes das Erfassen eines Bildes eines Strichcodes umfasst.
• 5. Ein Verfahren nach einem der Aspekte 1 bis 4, wobei das Erfassen eines Bildes das Erfassen eines Bildes eines Teils der Prozessanlage umfasst, und wobei das Bestimmen aus dem Bild einer Position des mobilen Geräts das Vergleichen des Bildes des Teils der Prozessanlage mit einer Datenbank von Bildern umfasst, die mit Stellen in der Prozessanlage verknüpft sind, um die Position des mobilen Geräts zu bestimmen.
• 6. Ein Verfahren nach einem der Aspekte 1 bis 5, wobei das Erfassen von Daten, die eine Ankerposition angeben, das Erfassen von Daten von einem oder mehreren drahtlosen Signalen umfasst.
• 7. Ein Verfahren nach einem der Aspekte 1 bis 6, wobei das Erfassen von Daten von einem oder mehreren drahtlosen Signalen das Erfassen von Daten von einem oder mehreren drahtlosen Signalen umfasst, die einer Spezifikation IEEE 802.11 entsprechen.
• 8. Ein Verfahren nach einem der Aspekte 1 bis 7, wobei das Erfassen von Daten von einem oder mehreren drahtlosen Signalen das Herstellen einer Kommunikationssitzung über Bluetooth oder Nahfeldkommunikation (NFC) umfasst.
• 9. Ein Verfahren nach einem der Aspekte 1 bis 8, wobei das Erfassen von Daten von einem oder mehreren drahtlosen Signalen das Erfassen von Daten von einer RFID-Vorrichtung umfasst.
• 10. Ein Verfahren nach einem der Aspekte 1 bis 9, wobei das Erfassen von Daten, die eine Ankerposition angeben, das Feststellen eines Prozesssteuerungsgeräts in der Nähe des mobilen Geräts und das Empfangen oder Abrufen aus einer Speicherposition von Informationen, die mit der Position des Prozesssteuerungsgeräts verknüpft sind, umfasst.
• 11. Ein Verfahren nach einem der Aspekte 1 bis 10, wobei das Empfangen von Daten, die eine Beschleunigung und Orientierung des mobilen Geräts angeben, das Empfangen von Daten aus einem oder mehreren Beschleunigungsmessern und aus einem oder mehreren Gyroskopen umfasst.
• 12. Ein Verfahren nach einem der Aspekte 1 bis 11, wobei das Empfangen von Daten, die eine Beschleunigung und Orientierung des mobilen Geräts angeben, das Empfangen von Daten aus einem Magnetometer umfasst.
• 13. Ein Verfahren nach einem der Aspekte 1 bis 12, wobei das Empfangen von Daten, die eine Beschleunigung und Orientierung des mobilen Geräts angeben, das Empfangen von Daten aus einer Trägheitsmesseinheit umfasst.
• 14. Ein Verfahren nach einem der Aspekte 1 bis 13, wobei das Empfangen von Daten, die eine Beschleunigung und Orientierung des mobilen Geräts angeben, das Empfangen von Daten aus einem integrierten Gerät umfasst, das drei Beschleunigungsmesser und drei Gyroskope umfasst.
• 15. Ein Verfahren nach einem der Aspekte 1 bis 14, ferner umfassend das Starten einer Anwendung des mobilen Geräts mindestens teilweise basierend auf der bestimmten Position des mobilen Geräts, wobei die Anwendung betriebsfähig ist, um den Betrieb der Prozessanlage zu ändern.
• 16. Ein computerlesbares Medium, das Anweisungen speichert, die, wenn sie auf einem oder mehreren Prozessoren eines mobilen Geräts ausgeführt werden, den einen oder die mehreren Prozessoren veranlassen zum: Erfassen von Daten, die eine Ankerposition innerhalb einer Prozessanlage angeben; Bestimmen der Ankerposition gemäß den erfassten Daten; Empfangen an dem mobilen Gerät von Daten, die eine Beschleunigung und Orientierung des mobilen Geräts angeben; und Bestimmen einer Position des mobilen Geräts gemäß der empfangenen Daten und der Ankerposition.
• 17. Ein computerlesbares Medium nach Aspekt 16, wobei die Anweisungen, die betriebsfähig sind, um den einen oder die mehreren Prozessoren dazu zu veranlassen, Daten zu erfassen, die eine Ankerposition innerhalb einer Prozessanlage angeben, Anweisungen umfassen, die betriebsfähig sind, um den einen oder die mehreren Prozessoren dazu zu veranlassen, eine Position des mobilen Geräts unter Verwendung eines globalen satellitengestützten Positionsbestimmungssystems zu bestimmen.
• 18. Ein computerlesbares Medium entweder nach Aspekt 16 oder nach Aspekt 17, wobei die Anweisungen, die betriebsfähig sind, um den einen oder die mehreren Prozessoren dazu zu veranlassen, Daten zu erfassen, die eine Ankerposition innerhalb einer Prozessanlage anzugeben, Anweisungen umfassen, die betriebsfähig sind, um den einen oder die mehreren Prozessoren dazu zu veranlassen, ein Bild zu erfassen.
• 19. Ein computerlesbares Medium nach einem der Aspekte 16 bis 18, wobei die Anweisungen, die betriebsfähig sind, um den einen oder die mehreren Prozessoren dazu zu veranlassen, ein Bild zu erfassen, Anweisungen umfassen, die betriebsfähig sind, um den einen oder die mehreren Prozessoren dazu zu veranlassen, ein Bild eines Strichcodes zu erfassen.
• 20. Ein computerlesbares Medium nach einem der Aspekte 16 bis 19, wobei die Anweisungen, die betriebsfähig sind, um den einen oder die mehreren Prozessoren dazu zu veranlassen, ein Bild zu erfassen, Anweisungen umfassen, die betriebsfähig sind, um den einen oder die mehreren Prozessoren dazu zu veranlassen, ein Bild eines Teils der Prozessanlage zu erfassen, und wobei die Anweisungen, die betriebsfähig sind, um den einen oder die mehreren Prozessoren dazu zu veranlassen, eine Position des mobilen Geräts zu bestimmen, Anweisungen umfassen, die betriebsfähig sind, um den einen oder die mehreren Prozessoren dazu zu veranlassen, das Bild des Teils der Prozessanlage mit einer Datenbank von Bildern zu vergleichen, die mit Stellen in der Prozessanlage verknüpft sind, um die Position des mobilen Geräts zu bestimmen.
• 21. Ein computerlesbares Medium nach einem der Aspekte 16 bis 20, wobei die Anweisungen, die betriebsfähig sind, um den einen oder die mehreren Prozessoren dazu zu veranlassen, Daten zu erfassen, die eine Ankerposition innerhalb einer Prozessanlage zu erfassen, Anweisungen umfassen, die betriebsfähig sind, um den einen oder die mehreren Prozessoren dazu zu veranlassen, Daten von einem oder mehreren drahtlosen Signalen zu erfassen.
• 22. Ein computerlesbares Medium nach einem der Aspekte 16 bis 21, wobei die Anweisungen, die betriebsfähig sind, um den einen oder die mehreren Prozessoren dazu zu veranlassen, Daten zu erfassen, die eine Ankerposition angeben, Anweisungen umfassen, die betriebsfähig sind, um den einen oder die mehreren Prozessoren dazu zu veranlassen, ein Prozesssteuerungsgerät in der Nähe des mobilen Geräts festzustellen und aus einem Speicherplatz Informationen zu empfangen oder abzurufen, die mit der Position des Prozesssteuerungsgeräts verknüpft sind.
• 23. Ein computerlesbares Medium nach einem der Aspekte 16 bis 22, wobei die Anweisungen, die betriebsfähig sind, um den einen oder die mehreren Prozessoren dazu zu veranlassen, Daten zu empfangen, die eine Beschleunigung und Orientierung des mobilen Geräts angeben, Anweisungen umfassen, die betriebsfähig sind, um den einen oder die mehreren Prozessoren dazu zu veranlassen, Daten von einem oder mehreren Beschleunigungsmessern und von einem oder mehreren Gyroskopen zu empfangen.
• 24. Ein computerlesbares Medium nach einem der Aspekte 16 bis 23, wobei die Anweisungen, die betriebsfähig sind, um den einen oder die mehreren Prozessoren dazu zu veranlassen, Daten zu empfangen, die eine Beschleunigung und Orientierung des mobilen Geräts angeben, Anweisungen umfassen, die betriebsfähig sind, um den einen oder die mehreren Prozessoren dazu zu veranlassen, Daten aus einem Magnetometer zu empfangen.
• 25. Ein computerlesbares Medium nach einem der Aspekte 16 bis 24, wobei die Anweisungen, die betriebsfähig sind, um den einen oder die mehreren Prozessoren dazu zu veranlassen, Daten zu empfangen, die eine Beschleunigung und Orientierung des mobilen Geräts angeben, Anweisungen umfassen, die betriebsfähig sind, um den einen oder die mehreren Prozessoren dazu zu veranlassen, Daten aus einer Trägheitsmesseinheit zu empfangen.
• 26. Ein computerlesbares Medium nach einem der Aspekte 16 bis 25, wobei die Anweisungen, die betriebsfähig sind, um den einen oder die mehreren Prozessoren dazu zu veranlassen, Daten zu empfangen, die eine Beschleunigung und Orientierung des mobilen Geräts angeben, Anweisungen umfassen, die betriebsfähig sind, um den einen oder die mehreren Prozessoren dazu zu veranlassen, Daten aus einem integrierten Gerät zu empfangen, das drei Beschleunigungsmesser und drei Gyroskope umfasst.
• 27. Ein computerlesbares Medium nach einem der Aspekte 16 bis 26, ferner umfassend Anweisungen, die betriebsfähig sind, um den einen oder die mehreren Prozessoren dazu zu veranlassen, eine Anwendung des mobilen Geräts mindestens teilweise basierend auf der bestimmten Position des mobilen Geräts zu starten, wobei die Anwendung betriebsfähig ist, um den Betrieb der Prozessanlage zu ändern.
• 28. Ein mobiles Gerät zum Ausführen von Steuerungsvorgängen in einer Prozesssteuerungsumgebung, wobei das mobile Gerät Folgendes umfasst: eine erste Schaltung zum Erfassen erster Daten, die eine Ankerposition innerhalb einer Prozessanlage angeben; eine zweite Schaltung zum Ermitteln einer Beschleunigung und Orientierung des mobilen Geräts, wobei die zweite Schaltung zweite Daten generiert, welche die Beschleunigung und die Orientierung angeben; und einen oder mehrere Prozessoren, die mindestens einen Prozessor, der kommunikationsmäßig an die erste Schaltung angeschlossen ist, und mindestens einen Prozessor, der kommunikationsmäßig an die zweite Schaltung angeschlossen ist, umfassen, die betriebsfähig sind zum: (i) Bestimmen der Ankerposition basierend auf den ersten Daten; und (ii) Bestimmen einer Position des mobilen Geräts gemäß den zweiten Daten und der Ankerposition.
• 29. Ein mobiles Gerät nach Aspekt 28, wobei die erste Schaltung eine Bildaufnahmeschaltung umfasst, um ein Bild aufzunehmen, das die ersten Daten umfasst.
• 30. Ein mobiles Gerät entweder nach Aspekt 28 oder Aspekt 29, wobei die erste Schaltung eine Antenne zum Empfangen eines Hochfrequenzsignals umfasst, das die ersten Daten führt.
• 31. Ein mobiles Gerät nach einem der Aspekte 28 bis 30, wobei die zweite Schaltung einen Beschleunigungsmesser und ein Gyroskop umfasst.
• 32. Ein mobiles Gerät nach einem der Aspekte 28 bis 31, wobei die zweite Schaltung ein Magnetometer umfasst.
• 33. Ein mobiles Gerät nach einem der Aspekte 28 bis 32, wobei die zweite Schaltung eine Trägheitsmesseinheit umfasst.
• 34. Ein mobiles Gerät nach einem der Aspekte 28 bis 33, wobei die zweite Schaltung eine integrierte Schaltung umfasst, die drei Beschleunigungsmesser und drei Gyroskope umfasst.
• 35. Ein mobiles Gerät nach einem der Aspekte 28 bis 34, wobei der eine oder die mehreren Prozessoren die Ankerposition bestimmen, indem sie einen Suchvorgang gemäß den erfassten ersten Daten ausführen.
• 36. Ein mobiles Gerät nach einem der Aspekte 28 bis 35, wobei der eine oder die mehreren Prozessoren die Ankerposition bestimmen, indem sie Informationen von einem Server gemäß den erfassten ersten Daten anfragen.
• 37. Ein mobiles Gerät nach einem der Aspekte 28 bis 36, wobei die erste Schaltung ein RFID-Lesegerät umfasst.
• 38. Ein mobiles Gerät nach einem der Aspekte 28 bis 37, wobei die erste Schaltung einen Nahfeldkommunikations-Transceiver umfasst.
• 39. Ein mobiles Gerät nach einem der Aspekte 28 bis 38, wobei die erste Schaltung einen Empfänger umfasst, der konfiguriert ist, um Signale von einer Vielzahl von Satelliten eines Positionsbestimmungssystems zu empfangen.
• 40. Ein mobiles Gerät nach einem der Aspekte 28 bis 39, wobei der eine oder die mehreren Prozessoren ferner betriebsfähig ist bzw. sind, um eine Funktion des mobilen Geräts gemäß der Position des mobilen Geräts auszulösen.
• 41. Ein mobiles Gerät nach einem der Aspekte 28 bis 40, wobei der eine oder die mehreren Prozessoren ferner betriebsfähig ist bzw. sind, um eine Anzeige gemäß der Position des mobilen Geräts bereitzustellen.
• 42. Ein mobiles Gerät nach einem der Aspekte 28 bis 41, wobei der eine oder die mehreren Prozessoren ferner betriebsfähig ist bzw. sind, um eine Anwendung mindestens teilweise gemäß der Position des mobilen Geräts zu starten.
• 43. Ein mobiles Gerät nach einem der Aspekte 28 bis 42, wobei der eine oder die mehreren Prozessoren ferner betriebsfähig ist bzw. sind, um eine Kommunikation mit einem anderen mobilen Gerät oder einer Prozesssteuerungsentität mindestens teilweise gemäß der Position des mobilen Geräts herzustellen.

The following aspects of the disclosure are merely exemplary in nature and are not intended to limit the scope of the disclosure.

• A method for determining a location of a mobile device within a process control environment, the method comprising the steps of: collecting data indicating an anchor position within a process plant; Determining the anchor position according to the acquired data; Receiving data from the circuits of the mobile device indicating acceleration and orientation of the mobile device; and determining a position of the mobile device according to the received data and the anchor position.
• 2. A method according to aspect 1, wherein acquiring data indicative of an anchor position comprises determining a position of the mobile device using a global satellite positioning system.
• 3. A method according to either aspect 1 or aspect 2, wherein acquiring data indicative of an anchor position comprises capturing an image.
• 4. A method according to any one of aspects 1 to 3, wherein capturing an image comprises capturing an image of a bar code.
• 5. A method according to any one of aspects 1 to 4, wherein capturing an image comprises capturing an image of a portion of the process plant, and wherein determining from the image a location of the mobile device comprises comparing the image of the portion of the process plant with a database of images associated with locations in the process plant to determine the location of the mobile device.
• 6. A method according to any one of aspects 1 to 5, wherein acquiring data indicative of an anchor position comprises acquiring data from one or more wireless signals.
• 7. A method according to any one of aspects 1 to 6, wherein acquiring data from one or more wireless signals comprises acquiring data from one or more wireless signals that conform to a specification IEEE 802.11 correspond.
• 8. A method according to any one of aspects 1 to 7, wherein acquiring data from one or more wireless signals comprises establishing a communication session via Bluetooth or near field communication (NFC).
• 9. A method according to any one of aspects 1 to 8, wherein acquiring data from one or more wireless signals comprises acquiring data from an RFID device.
• 10. A method according to any one of aspects 1 to 9, wherein acquiring data indicative of an anchor position comprises detecting a process control device proximate to the mobile device and receiving or retrieving from a memory location information associated with the location of the process control device are linked.
• 11. A method according to any one of aspects 1 to 10, wherein receiving data indicative of acceleration and orientation of the mobile device comprises receiving data from one or more accelerometers and from one or more gyroscopes.
• 12. A method according to any one of aspects 1 to 11, wherein receiving data indicative of acceleration and orientation of the mobile device comprises receiving data from a magnetometer.
• 13. A method according to any of aspects 1 to 12, wherein receiving data indicative of acceleration and orientation of the mobile device comprises receiving data from an inertial measurement unit.
• 14. A method according to any one of aspects 1 to 13, wherein receiving data indicative of acceleration and orientation of the mobile device comprises receiving data from an integrated device comprising three accelerometers and three gyroscopes.
• 15. A method according to any one of aspects 1 to 14, further comprising starting an application of the mobile device based at least in part on the determined location of the mobile device, the application being operable to change the operation of the process plant.
• 16. A computer readable medium storing instructions that, when executed on one or more processors of a mobile device, cause the one or more processors to: collect data indicating an anchor position within a process plant; Determining the anchor position according to the acquired data; Receiving at the mobile device data indicating an acceleration and orientation of the mobile device; and determining a position of the mobile device according to the received data and the anchor position.
• 17. A computer-readable medium according to aspect 16, wherein the instructions operable to cause the one or more processors to acquire data indicative of an anchor position within a process plant include instructions operable to communicate with the one or more processors or cause the plurality of processors to determine a location of the mobile device using a global satellite positioning system.
• 18. A computer-readable medium according to either aspect 16 or aspect 17, wherein the instructions operable to cause the one or more processors to acquire data indicative of anchor position within a process plant include instructions that are operable are to cause the one or more processors to capture an image.
• 19. A computer-readable medium according to any one of aspects 16 to 18, wherein the instructions operable to cause the one or more processors to capture an image include instructions that are operable to contain the one or more To cause processors to capture an image of a bar code.
• 20. A computer-readable medium according to any of aspects 16 to 19, wherein the instructions operable to cause the one or more processors to capture an image include instructions operable to control the one or more To cause processors to capture an image of a portion of the process plant, and wherein the instructions operable to cause the one or more processors to determine a location of the mobile device include instructions that are operable to causing the one or more processors to compare the image of the portion of the process plant with a database of images associated with locations in the process plant to determine the location of the mobile device.
• 21. A computer-readable medium according to any one of aspects 16 to 20, wherein the instructions operable to cause the one or more processors to acquire data that capture an anchor position within a process plant include instructions that are operable are to cause the one or more processors to capture data from one or more wireless signals.
• 22. A computer-readable medium according to any of aspects 16 to 21, wherein the instructions operable to cause the one or more processors to acquire data indicative of an anchor position include instructions operable to cause the one or more processors causing one or more processors to detect a process control device proximate to the mobile device and to receive or retrieve information from a memory location associated with the location of the process control device.
• 23. A computer-readable medium according to any one of aspects 16 to 22, wherein the instructions operable to cause the one or more processors to receive data indicative of acceleration and deceleration Indicate orientation of the mobile device, include instructions that are operable to cause the one or more processors to receive data from one or more accelerometers and one or more gyroscopes.
• 24. A computer-readable medium according to any of aspects 16 to 23, wherein the instructions operable to cause the one or more processors to receive data indicative of acceleration and orientation of the mobile device include instructions that are operable to cause the one or more processors to receive data from a magnetometer.
• 25. A computer-readable medium according to any one of aspects 16 to 24, wherein the instructions operable to cause the one or more processors to receive data indicative of acceleration and orientation of the mobile device include instructions that are operable to cause the one or more processors to receive data from an inertial measurement unit.
• 26. A computer-readable medium according to any of aspects 16 to 25, wherein the instructions operable to cause the one or more processors to receive data indicative of acceleration and orientation of the mobile device include instructions that are operable to cause the one or more processors to receive data from an integrated device comprising three accelerometers and three gyroscopes.
• 27. A computer-readable medium according to any of aspects 16 to 26, further comprising instructions operable to cause the one or more processors to launch an application of the mobile device based at least in part on the determined location of the mobile device; the application being operable to change the operation of the process plant.
• 28. A mobile device for performing control operations in a process control environment, the mobile device comprising: a first circuit for acquiring first data indicating an anchor position within a process plant; a second circuit for determining an acceleration and orientation of the mobile device, wherein the second circuit generates second data indicating the acceleration and the orientation; and one or more processors including at least one processor communicatively coupled to the first circuit and at least one processor communicatively coupled to the second circuit operable to: (i) determine the armature position based on first dates; and (ii) determining a position of the mobile device according to the second data and the anchor position.
• 29. A mobile device according to aspect 28, wherein the first circuit comprises an image capture circuit to capture an image comprising the first data.
• A mobile device according to either aspect 28 or aspect 29, wherein the first circuit comprises an antenna for receiving a radio frequency signal carrying the first data.
• 31. A mobile device according to any of aspects 28 to 30, wherein the second circuit comprises an accelerometer and a gyroscope.
• 32. A mobile device according to any one of aspects 28 to 31, wherein the second circuit comprises a magnetometer.
• 33. A mobile device according to any of aspects 28 to 32, wherein the second circuit comprises an inertial measurement unit.
• 34. A mobile device according to any of aspects 28 to 33, wherein the second circuit comprises an integrated circuit comprising three accelerometers and three gyroscopes.
• 35. A mobile device according to any of aspects 28 to 34, wherein the one or more processors determine the anchor position by performing a seek according to the acquired first data.
• 36. A mobile device according to any one of aspects 28 to 35, wherein the one or more processors determine the anchor position by requesting information from a server according to the acquired first data.
• 37. A mobile device according to any one of aspects 28 to 36, wherein the first circuit comprises an RFID reader.
• 38. A mobile device according to any one of aspects 28 to 37, wherein the first circuit comprises a near field communication transceiver.
• 39. A mobile device according to any one of aspects 28 to 38, wherein the first circuit comprises a receiver configured to receive signals from a plurality of satellites of a positioning system.
• 40. A mobile device according to any one of aspects 28 to 39, wherein the one or more processors is further operable to trigger a function of the mobile device according to the location of the mobile device.
• 41. A mobile device according to any one of aspects 28 to 40, wherein the one or more processors is further operable to provide an indication according to the location of the mobile device.
• 42. A mobile device according to any of aspects 28 to 41, wherein the one or more processors is further operable to launch an application at least in part according to the location of the mobile device.
• 43. A mobile device according to any one of aspects 28 to 42, wherein the one or more processors is further operable to establish communication with another mobile device or process control entity at least in part according to the location of the mobile device.

QUOTES INCLUDE IN THE DESCRIPTION

This list of the documents listed by the applicant has been generated automatically and is included solely for the better information of the reader. The list is not part of the German patent or utility model application. The DPMA assumes no liability for any errors or omissions.

Cited non-patent literature

• IEEE 802.11 [0069]
• IEEE 802.11 [0120]
• Standard ISO / IEC 14443 [0136]
• ISO / IEC 1809 [0136]
• Standard IEEE 802.11 [0136]
• IEEE 802.11 [0242]
• IEEE 802.11 standards [0247]
• ISO / IEC 14443 [0257]
• ISO / IEC 1809 [0257]
• IEEE 802.15.1 standards [0257]
• IEEE 802.11 [0275]
• IEEE 802.11 [0288]
• IEEE 802.11 [0302]

Claims (27)

 A method of determining a location of a mobile device within a process control environment, the method comprising the steps of: Collect data indicating an anchor position within a process plant; Determining the anchor position according to the acquired data; Receiving data from the circuits of the mobile device indicating acceleration and orientation of the mobile device; and Determining a position of the mobile device according to the received data and the anchor position.  The method of claim 1, wherein acquiring data indicative of an anchor position comprises determining a location of the mobile device using a global satellite positioning system.  The method of claim 1 or 2, wherein acquiring data indicating an anchor position comprises capturing an image. wherein capturing an image preferably comprises capturing an image of a bar code, or a portion of the process plant, and wherein determining from the image of a location of the mobile device comprises comparing the image of the portion of the process plant with a database of images associated with locations in the process plant to determine the location of the mobile device ,  The method of any one of the preceding claims, wherein acquiring data indicative of an anchor position comprises acquiring data from one or more wireless signals.  Method according to one of the preceding claims, in particular claim 4, wherein the acquisition of data from one or more wireless signals comprises: (a) collecting data from one or more wireless signals conforming to an IEEE 802.11 specification; and or (b) establishing a communication session via Bluetooth or near field communication (NFC); and or (c) acquiring data from an RFID device.  The method of claim 1, wherein acquiring data indicating an anchor position comprises detecting a process control device in the vicinity of the mobile device and receiving or retrieving from a storage position information associated with the position of the process control device.  The method of any one of the preceding claims, wherein receiving data indicative of acceleration and orientation of the mobile device comprises receiving data from one or more accelerometers and one or more gyroscopes.  The method of any one of the preceding claims, wherein receiving data indicative of acceleration and orientation of the mobile device comprises receiving data from a magnetometer.  The method of any one of the preceding claims, wherein receiving data indicative of acceleration and orientation of the mobile device comprises receiving data from an inertial measurement unit.  The method of any one of the preceding claims, wherein receiving data indicative of acceleration and orientation of the mobile device comprises receiving data from an integrated device comprising three accelerometers and three gyroscopes.  The method of claim 1, further comprising starting an application of the mobile device based at least in part on the determined location of the mobile device, wherein the application is operable to change the operation of the process plant.  A mobile device for performing control operations in a process control environment, the mobile device comprising: a first circuit for acquiring first data indicating an anchor position within a process plant; a second circuit for determining an acceleration and orientation of the mobile device, wherein the second circuit generates second data indicating the acceleration and the orientation; and one or more processors comprising at least one processor communicatively coupled to the first circuit and at least one processor communicatively coupled to the second circuit operable to: (i) determining the anchor position based on the first data; and (ii) determining a position of the mobile device according to the second data and the anchor position. The mobile device according to claim 12, wherein the first circuit comprises an image pickup circuit to capture an image comprising the first data.  A mobile device according to any one of claims 12 or 13, wherein the first circuit comprises an antenna for receiving a high-frequency signal carrying the first data.  Mobile device according to one of claims 12 to 14, wherein the second circuit comprises an accelerometer and a gyroscope.  Mobile device according to one of claims 12 to 15, wherein the second circuit comprises a magnetometer.  Mobile device according to one of claims 12 to 16, wherein the second circuit comprises an inertial measuring unit.  The mobile device of any one of claims 12 to 17, wherein the second circuit comprises an integrated circuit comprising three accelerometers and three gyroscopes.  The mobile device of any one of claims 12 to 18, wherein the one or more processors determine the anchor position by performing a seek according to the acquired first data.  The mobile device of one of claims 12 to 19, wherein the one or more processors determine the anchor position by requesting information from a server according to the acquired first data.  Mobile device according to one of claims 12 to 20, wherein the first circuit comprises an RFID reader.  The mobile device of any one of claims 12 to 21, wherein the first circuit comprises a near field communication transceiver.  The mobile device of any one of claims 12 to 22, wherein the first circuit comprises a receiver configured to receive signals from a plurality of satellites of a positioning system.  The mobile device of any one of claims 12 to 23, wherein the one or more processors are further operable to trigger a function of the mobile device according to the location of the mobile device.  The mobile device of any one of claims 12 to 24, wherein the one or more processors are further operable to provide an indication according to the location of the mobile device.  The mobile device of any one of claims 12 to 25, wherein the one or more processors are further operable to launch an application at least in part according to the location of the mobile device.  The mobile device of claim 12, wherein the one or more processors is further operable to establish communication with another mobile device or process control entity at least in part according to the location of the mobile device.

Images