CROSS-REFERENCE TO RELATED APPLICATIONS AND PRIORITY CLAIM

[0001] This application claims priority under 35 U.S.C. § 119(e) to the following U.S. provisional patent applications:

U.S. Provisional Patent Application No. 62/16.1 ,536 filed on May 14, 2015 and entitled "APPARATUS AND METHOD FOR TRANSLATING INDUSTRIAL PROCESS CONTROL AND AUTOMATION SYSTEM EVENTS INTO MOBILE NOTIFICATIONS";

U.S. Provisional Patent Application No. 62/161,542 filed on May 14, 2015 and entitled "APPARATUS AND METHOD FOR USING CONFIGURABLE RULES LINKING TRIGGERS WITH ACTIONS TO SUPPORT NOTIFICATIONS ASSOCIATED WITH INDUSTRIAL PROCESS CONTROL AND AUTOMATION SYSTEM";

U.S. Provisional Patent Application No. 62/161,548 filed on May 14, 2015 and entitled "APPARATUS AND METHOD FOR AUTOMATED EVENT NOTIFICATION READ RECEIP TO SUPPORT NON-REPUDIATED AUDITING IN INDUSTRIAL PROCESS CONTROL AND AUTOMATION SYSTEM";

U.S. Provisional Patent Application No, 62/161 ,558 filed on May 14, 2015 and entitled "APPARATUS AND METHOD FOR EVENT DETECTION TO SUPPORT MOBILE NOTIFICATIONS RELATED TO INDUSTRIAL PROCESS CONTROL AND AUTOMATION SYSTEM";

U.S. Provisional Patent Application No. 62/161,622 filed on May 14, 2015 and entitled "APPARATUS AND METHOD FOR PROTECTING PROPRIETARY INFORMATION OVER PUBLIC NOTIFICATION INFRASTRUCTURE";

U.S. Provisional Patent Application No, 62/161 ,644 filed on May 14, 2015 and entitled "APPARATUS AND METHOD FOR PROVIDING EVENT CONTEXT WITH NOTIFICATIONS RELATED TO INDUSTRIAL PROCESS CONTROL AND AUTOMATION SYSTEM"; and

U.S. Provisional Patent Application No. 62/161,657 filed on May 14, 2015 and entitled "APPARATUS AND METHOD FOR UNIVERSAL ANNOTATION IN INDUSTRIAL PROCESS CONTROL AND AUTOMATION SYSTEM".

[0002] All of these provisional patent applications are hereby incorporated by reference in their entirety.

TECHNICAL FIELD

[0003] This disclosure relates generally to industrial process control and automation systems. More specifically, this disclosure relates to an apparatus and method for universal annotation in an industrial process control and automation system.

BACKGROUND

[0004] Industrial process control and automation systems are often used to automate large and complex industrial processes. These types of systems routinely include sensors, actuators, and controllers. The controllers are often arranged hierarchically in a control and automation system. For example, lower-level controllers are often used to receive measurements from the sensors and perform process control operations to generate control signals for the actuators. Higher-level controllers are often used to perform higher-level functions, such as planning, scheduling, and optimization operations. Human operators routinely interact with controllers and other devices in a control and automation system, such as to review warnings, alarms, or other notifications and make adjustments to control or other operations. SUMMARY

[00Θ5] This disclosure provides an apparatus and method for universal annotation in an industrial process control and automation system.

[0006] In a first embodiment, a method includes obtaining multiple annotations associated with multiple data items in an industrial process control and automation system. The method also includes, for each of the data items, obtaining a unique identifier for the data item. The method further includes storing, in a database, each of the annotations in association with one or more of the unique identifiers that correspond to one or more of the data items associated with the annotation.

[0007] In a second embodiment, an apparatus includes at least one memory and at least one processing device. The at least one processing device is configured to obtain multiple annotations associated with multiple data items in an industrial process control and automation system and, for each of the data items, obtain a unique identifier for the data item. The at least one processing device is also configured to store, in the at least one memory, each of the annotations in association with one or more of the unique identifiers that correspond to one or more of the data items associated with the annotation.

[0008] In a third embodiment, a non-transitory computer readable medium contains computer readable program code that, when executed, causes at least one processing device to obtain multiple annotations associated with multiple data items in an industrial process control and automation system and, for each of the data items, obtain a unique identifier for the data item. The medium also contains computer readable program code that, when executed, causes the at least one processing device to store, in a database, each of the annotations in association with one or more of the unique identifiers that correspond to one or more of the data items associated with the annotation.

[0009] Other technical features may be readily apparent to one skilled in the art from the following figures, descriptions, and claims. BRIEF DESCRIPTION OF THE DRAWINGS

[0010] For a more complete understanding of this disclosure and its features, reference is now made to the following description, taken in conjunction with the accompanying drawings, in which:

[0011] FIGURE 1 illustrates an example industrial process control and automation system according to this disclosure;

[0012] FIGURE 2 illustrates an example device supporting universal annotation in an industrial process control and automation system according to this disclosure;

[0013] FIGURE 3 illustrates an example context model for supporting universal annotation in an industrial process control and automation system according to this disclosure;

[0014] FIGURE 4 illustrates an example system model for supporting universal annotation in an industrial process control and automation system according to this disclosure;

[0015] FIGURES 5 through 7 illustrate example notifications related to an industrial process control and automation system according to this disclosure; and

[0016] FIGURES 8 and 9 illustrate example methods for supporting universal annotation in an industrial process control and automation system according to this disclosure.

DETAILED DESCRIPTION

[0017] FIGURES 1 through 9, discussed below, and the various embodiments used to describe the principles of the present invention in this patent document are by way of illustration only and should not be construed in any way to limit the scope of the invention. Those skilled in the art will understand that the principles of the invention may be implemented in any type of suitably arranged device or system.

[0018] FIGURE 1 illustrates an example industrial process control and automation system 100 according to this disclosure. As shown in FIGURE I, the system 100 includes various components that facilitate production or processing of at least one product or other material. For instance, the system 100 is used here to facilitate control over components in one or multiple plants lOla-lOln. Each plant lOla-lOln represents one or more processing facilities (or one or more portions thereof), such as one or more manufacturing facilities for producing at least one product or other material. In general, each plant l Ola-lOln may implement one or more processes and can individually or collectively be referred to as a process system. A process system generally represents any system or portion thereof configured to process one or more products or other materials in some manner.

[0019] In FIGURE I, the system 100 is implemented using the Purdue model of process control. In the Purdue model, "Level 0" may include one or more sensors 102a and one or more actuators 102b. The sensors 102a and actuators 102b represent components in a process system that may perform any of a wide variety of functions. For example, the sensors 102a could measure a wide variety of characteristics in the process system, such as temperature, pressure, or flow rate. Also, the actuators 102b could alter a wide variety of characteristics in the process system. The sensors 102a and actuators 102b could represent any other or additional components in any suitable process system. Each of the sensors 102a includes any suitable structure for measuring one or more characteristics in a process system. Each of the actuators 102b includes any suitable structure for operating on or affecting one or more conditions in a process system.

[0020] At least one network 104 is coupled to the sensors 102a and actuators

102b. The network 104 facilitates interaction with the sensors 102a and actuators 102b. For example, the network 104 could transport measurement data from the sensors 102a and provide control signals to the actuators 102b. The network 104 could represent any suitable network or combination of networks. As particular examples, the network 104 could represent an Ethernet network, an electrical signal network (such as a HART or FOUNDATION FIELDBUS network), a pneumatic control signal network, or any other or additional type(s) of network(s).

[0021] In the Purdue model, "Level 1." may include one or more controllers 106, which are coupled to the network 104. Among other things, each controller 106 may use the measurements from one or more sensors 102a to control the operation of one or more actuators 102b. For example, a controller 106 could receive measurement data from one or more sensors 102a and use the measurement data to generate control signals for one or more actuators 102b. Each controller 106 includes any suitable structure for interacting with one or more sensors 102a and controlling one or more actuators 102b. Each controller 106 could, for example, represent a proportional- integral-derivative (PID) controller or a multivariable controller, such as a Robust Multivariable Predictive Control Technology (RJVIPCT) controller or other type of controller implementing model predictive control (MPC) or other advanced predictive control (APC). As a particular example, each controller 106 could represent a computing device running a real-time operating system.

[00221 Two networks 108 are coupled to the controllers 106. The networks 108 facilitate interaction with the controllers 106, such as by transporting data to and from the controllers 106. The networks 108 could represent any suitable networks or combination of networks. As a particular example, the networks 108 could represent a redundant pair of Ethernet networks, such as a FAULT TOLERANT ETHERNET (FTE) network from HONEYWELL INTERNATION AL INC.

[0023| At least one switch/firewall 110 couples the networks 108 to two networks 112. The switch/firewall 110 may transport traffic from one network to another. The switch/firewall 110 may also block traffic on one network from reaching another network. The switch/firewall 110 includes any suitable structure for providing communication between networks, such as a HONEYWELL CONTROL FIREWALL (CF9) device. The networks 112 could represent any suitable networks, such as an FTE network.

[0024| In the Purdue model, "Level 2" may include one or more machine- level controllers 1 14 coupled to the networks 112. The machine-level controllers 114 perform various functions to support the operation and control of the controllers 106, sensors 102a, and actuators 102b, which could be associated with a particular piece of industrial equipment (such as a boiler or other machine). For example, the machine- level controllers 1 14 could log information collected or generated by the controllers 106, such as measurement data from the sensors 102a or control signals for the actuators 102b. The machine-level controllers 1 14 could also execute applications that control the operation of the controllers 106, thereby controlling the operation of the actuators 102b. In addition, the machine-level controllers 114 could provide secure access to the controllers 106. Each of the machine-level controllers 1 14 includes any suitable structure for providing access to, control of, or operations related to a machine or other individual piece of equipment. Each of the machine-level controllers 114 could, for example, represent a server computing device running a MICROSOFT WINDOWS operating system. Although not shown, different machine-level controllers 114 could be used to control different pieces of equipment in a process system (where each piece of equipment is associated with one or more controllers 106, sensors 102a, and actuators 102b).

[0025] One or more operator stations 116 are coupled to the networks 112. The operator stations 116 represent computing or communication devices providing user access to the machine-level controllers 114, which could then provide user access to the controllers 106 (and possibly the sensors 102a and actuators 102b). As particular examples, the operator stations 116 could allow users to review the operational history of the sensors 102a and actuators 102b using information collected by the controllers 106 and/or the machine-level controllers 114. The operator stations 116 could also allow the users to adjust the operation of the sensors 102a, actuators 102b, controllers 106, or machine-level controllers 114. In addition, the operator stations 1 16 could receive and display warnings, alerts, or other messages or displays generated by the controllers 106 or the machine-level controllers 114. Each of the operator stations 116 includes any suitable structure for supporting user access and control of one or more components in the system 100. Each of the operator stations .1 16 could, for example, represent a computing device running a MICROSOFT WINDOWS operating system. [0026] At least one router/firewall 118 couples the networks 1 12 to two networks 120. The router/firewall 1 18 includes any suitable structure for providing communication between networks, such as a secure router or combination router/firewall. The networks 120 could represent any suitable networks, such as an FTE network.

[0027] In the Purdue model, "Level 3" may include one or more unit-level controllers 122 coupled to the networks 120. Each unit-level controller 122 is typically associated with a unit in a process system, which represents a collection of different machines operating together to implement at least part of a process. The unit-level controllers 122 perform various functions to support the operation and control of components in the lower levels. For example, the unit-level controllers 122 could log information collected or generated by the components in the lower levels, execute applications that control the components in the lower levels, and provide secure access to the components in the lower levels. Each of the unit-level controllers 122 includes any suitable structure for providing access to, control of, or operations related to one or more machines or other pieces of equipment in a process unit. Each of the unit-level controllers 122 could, for example, represent a server computing device running a MICROSOFT WINDOWS operating system. Although not shown, different unit-level controllers 122 could be used to control different units in a process system (where each unit is associated with one or more machine-level controllers 114, controllers 106, sensors 102a, and actuators 102b).

[0028] Access to the unit-level controllers 122 may be provided by one or more operator stations 124. Each of the operator stations 124 includes any suitable structure for supporting user access and control of one or more components in the system 100. Each of the operator stations 124 could, for example, represent a computing device running a MICROSOFT WINDOWS operating system.

[0029] At least one router/firewall 126 couples the networks 120 to two networks 128. The router/firewall 126 includes any suitable structure for providing communication between networks, such as a secure router or combination router/firewall. The networks 128 could represent any suitable networks, such as an FTE network.

[0030] In the Purdue model, "Level 4" may include one or more plant-level controllers 130 coupled to the networks 128. Each plant-level controller 130 is typically associated with one of the plants lOla-lOln, which may include one or more process units that implement the same, similar, or different processes. The plant-level controllers 130 perform various functions to support the operation and control of components in the lower levels. As particular examples, the plant-level controller 130 could execute one or more manufacturing execution system (MES) applications, scheduling applications, or other or additional plant or process control applications. Each of the plant-level controllers 130 includes any suitable structure for providing access to, control of, or operations related to one or more process units in a process plant. Each of the plant-level controllers 130 could, for example, represent a server computing device running a MICROSOFT WINDOWS operating system.

[0031] Access to the plant-level controllers 130 may be provided by one or more operator stations 132. Each of the operator stations 132 includes any suitable structure for supporting user access and control of one or more components in the system 100. Each of the operator stations 132 could, for example, represent a computing device running a MICROSOFT WINDOWS operating system.

[0032] At least one router/firewall 134 couples the networks 128 to one or more networks 136. The router/firewall 134 includes any suitable structure for providing communication between networks, such as a secure router or combination router/firewall. The network 136 could represent any suitable network, such as an enterprise-wide Ethernet or other network or all or a portion of a larger network (such as the Internet).

[0033] In the Purdue model, "Level 5" may include one or more enterprise- level controllers 138 coupled to the network 136. Each enterprise-level controller 138 is typically able to perform planning operations for multiple plants lOla-lOln and to control various aspects of the plants lOla-l Oln. The enterprise-level controllers 138 can also perform various functions to support the operation and control of components in the plants l Ol a-lOln. As particular examples, the enterprise-level controller 138 could execute one or more order processing applications, enterprise resource planning (ERP) applications, advanced planning and scheduling (APS) applications, or any other or additional enterprise control applications. Each of the enterprise-level controllers 138 includes any suitable structure for providing access to, control of, or operations related to the control of one or more plants. Each of the enterprise-level controllers 138 could, for example, represent a server computing device running a MICROSOFT WINDOWS operating system. In this document, the term "enterprise" refers to an organization having one or more plants or other processing facilities to be managed. Note that if a single plant 101 a is to be managed, the functionality of the enterprise-level controller 138 could be incorporated into the plant-level controller 130.

[0034] Various plant applications 139 could also be executed in the system 100. In this example, the plant applications 139 are shown as residing on Level 5 of the system 100, although plant applications 139 could reside on other or additional levels of the system 100. The plant applications 139 could represent any suitable applications that are executed by server computers or other computing devices.

[0035] Access to the enterprise-level controllers 138 and plant applications 139 may be provided by one or more enterprise desktops (also referred to as operator stations) 140. Each of the enterprise desktops 140 includes any suitable structure for supporting user access and control of one or more components in the system 100. Each of the enterprise desktops 140 could, for example, represent a computing device running a MICROSOFT WINDOWS operating system.

[0036] Various levels of the Purdue model can include other components, such as one or more databases. The database(s) associated with each level could store any suitable information associated with that level or one or more other levels of the system 100. For example, a historian 142 can be coupled to the network 136. The historian 142 could represent a component that stores various information about the system 100. The historian 142 could, for instance, store information used during production scheduling and optimization. The historian 142 represents any suitable structure for storing and facilitating retrieval of information. Although shown as a single centralized component coupled to the network 136, the historian 142 could be located elsewhere in the system 100, or multiple historians could be distributed in different locations in the system 100.

[0037] In particular embodiments, the various controllers and operator stations in FIGURE 1 may represent computing devices. For example, each of the controllers 106, 114, 122, 130, 138 and each of the operator stations 116, 124, 132, 140 could include one or more processing devices and one or more memories for storing instructions and data used, generated, or coliected by the processing device(s). Each of the controllers 106, 114, 122, 130, 138 and each of the operator stations 1 16, 124, 132, 140 could also include at least one network interface, such as one or more Ethernet interfaces or wireless transceivers, facilitating communication over one or more networks or communication paths,

[0038] Engineers and other personnel in industrial facilities often need to troubleshoot problems and investigate improvement opportunities. In the course of these or other activities, the personnel routinely find and review significant amounts of information. As this occurs, the personnel gain knowledge about the industrial facilities and the data that describes those facilities. Often times, this knowledge is transient and is either (i) not recorded or shared with others or (ii) entered in a particular application but not available outside that application. As a particular example, many conventional applications allow users to enter comments on data that are specific to that particular application, but those comments are private to the application. There is no ability to query all comments across all applications in an industrial process control and automation system. This makes collaboration difficult and future similar investigations less efficient.

[0039] In accordance with this disclosure, an annotation database 143 is provided that allows users to annotate a wide variety of data (possibly any piece of data) in the system. For example, a user might comment on an event with his or her understanding of the root cause, annotate a measurement value at a specific point in time to point out an anomaly, or tag an asset to categorize the asset. In some embodiments, each annotation stored in the annotation database 143 includes a reference to one or more associated data items, a time that the annotation was created, a point in time that the annotation is relevant to, a user who created the annotation, and text describing the annotation. This information can be stored in a common database for multiple (possibly all) data items in a system, providing a centralized storage for the annotations. The annotation database 143 could also be searched in various ways, such as by annotation content (like searching for all comments or other annotations containing certain terms or all data items with a specific tag) or by data item (like searching for ail annotations related to a specified asset in a specified time range). Using the annotation database 143, users can more easily capture knowledge about industrial facilities and related data, as well as more easily find relevant knowledge that has been previously provided by others. The annotation database 143 includes any suitable structure for storing and facilitating retrieval of annotations.

[0040] One example use of the annotation database 143 is in conjunction with notifications provided to users' mobile devices, where users can use the mobile devices to provide comments associated with events or other data items. The widespread use of mobile "smart" devices (such as APPLE IPHOMEs and IPADs and ANDROID devices) allows users to remain connected and to interact with remote computing devices from virtually anywhere each user travels. Among other things, this could allow personnel associated with an industrial process control and automation system to receive warnings, alerts, or other notifications associated with events and other information and trigger actions associated with the control and automation system, regardless of whether the personnel are physically located at an industrial site. For example, events that are generated in a process control and automation system are often presented to operators currently on shift in one or more control rooms. There may also typically be a need or desire to inform users outside of control rooms, outside of an industrial plant, or while off network of events that are happening in the control and automation system. These events can come from a variety of applications, such as from a distributed control system (DCS) itself, advanced process control applications, operations applications, or business applications. Deliver}' of notifications describing these events to a user's handheld mobile device enables the user to receive notifications virtually anywhere and at any time.

[0041] To support this functionality, the system 100 includes a notification server 144, which receives data from other component(s) of the system 100 and generates notifications for users. For example, the notification server 144 could receive information identifying different events that occur with the system 100. The events could be associated with any suitable activities or conditions in the system 100, such as the generation of warnings or alerts by other components in the system 100. The notification server 144 could receive this information in any suitable manner and from any suitable source(s), such as from a historian, controller, or plant application. The notification server 144 uses this information to generate notifications (such as push notifications) and other messages to be sent to appropriate users. The notification server 144 could also provide additional information to appropriate users in response to user interactions with those notifications or other messages.

[0042] The notification server 144 communicates over a third-party network

146 with a third-party server 148. The third-part ' network 146 generally represents any suitable communication network(s) outside the system 100 (and therefore out of the control of the owners/operators of the system 100). The third-part}' network 146 could, for example, represent the Internet, a cellular communication network, or other network or combination of networks. The third-party server 148 represents a server used to provide notifications to end-user devices 150. For example, the third-party server 148 could push notifications to the end-user devices 150, allow retrieval of notifications by the end-user devices 150 at specified intervals or when requested, or provide notifications in any other suitable manner. The end-user devices 150 can then connect to the notification server 144 over the network 146 to receive details about notifications and events or to query for any notifications. As a particular example, the third-party server 148 could be used by companies like APPLE, SAMSUNG, or GOOGLE to provide push notifications or other notifications to mobile devices.

[0043] The end-user devices 150 denote any suitable user devices that can receive and present notifications to users. Examples of end-user devices 150 include smartphones, tablet computers, or other communication/computing devices. Specific examples could include APPLE IPHONEs, APPLE IPADs, and ANDROID devices.

[0044] As part of the use of notifications, users using the end-user devices 150 could submit comments about events or other data items associated with the control and automation system 100. The notification server 144 supports the storage of these comments as annotations in the annotation database 143. The annotations could then be searched later to support any number of functions.

[0045] In some embodiments, annotations are stored in the database 143 and linked with identifiers of associated data items. Each identifier can be unique in the system, and any user or system that queries for data can further request associated annotations (which could be located, for example, using one or more suitable data identifiers). Any suitable unique identifiers could be used here. In particular embodiments, any data item that can be identified using a uniform resource identifier (URI) could be annotated. Various URIs could also be "normalized" to a known or standard format since multiple URIs are possible for the same item. For instance, a client could pass a full URI to the annotation database 143, and an annotation layer or application 143a can normalize the URI before adding or querying entities in the database 143. If there is an extensible mechanism 143b to register "annotation sources" and include a normalization expression, many other items ca be annotated. The annotation layer or application 143a includes any structure (such as logic executed by one or more processing devices) for normalizing URIs or other data item identifiers. The extensible mechanism 143b includes any structure (such as logic executed by one or more processing devices) for registering sources of annotations and collecting information about how to normalize URIs or other data item identifiers from those sources.

[0046] As a particular example of this functionality, personnel using operator consoles in control rooms often have access to a "logbook" application, which allows the personnel to (among other things) provide and share comments related to the personnel 's tasks. Ordinarily, these comments can only be shared with other users of the same logbook application. Through the use of the annotation database 143, comments in the logbook application could be associated with annotations from the end-user devices 150, such as by linking the annotations with URIs of comments in the logbook application.

[0047] Among other things, this allows one application to query the annotation database 143 and retrieve information associated with multiple applications. For example, when users search the comments in the logbook application, the URIs of identified comments could also be used to retrieve related annotations from the annotation database 143. Similarly, when users search the annotations in the annotation database 143, the URIs of the identified annotations could also be used to retrieve related comments from the logbook application.

[0048] Moreover, an annotation in the annotation database 143 could be linked to any number of data items in any number of applications. For example, a single annotation could be linked to a data item describing an event, a data item defining a notification sent in response to the event, any user comments associated with the notification, and logbook comments related to the event. This allows annotations to be linked to various data items, including data items from different applications executed in the control and automation system.

[0049] One potential issue with storing annotations in a centralized database 143 is "orphaning," where an original data item is deleted but annotations for that data item remain in the database 143. This could be handled in any suitable manner, such as by using a cleanup mechanism that initiates a "call back" to an annotation source to check for the existence of a data item. If a data item cannot be found, any annotations for that data item could be deleted, archived, or processed in any other manner.

[0050] In this way, knowledge associated with an industrial process control and automation system can be collected from users, stored in a central repositoiy, and searched or used in any other suitable manner. This allows personnel to more easily retrieve information that might be relevant to the personnel's current tasks and to preserve more facility-relevant knowledge over time. This also allows capture of comments or other information provided by users' mobile devices.

[0051] Although FIGURE 1 illustrates one example of an industrial process control and automation system 100, various changes may be made to FIGURE 1. For example, a control and automation system could include any number of sensors, actuators, controllers, operator stations, networks, databases, servers, end-user devices, and other components. Also, the makeup and arrangement of the system 100 in FIGURE 1 is for illustration only. Components could be added, omitted, combined, further subdivided, or placed in any other suitable configuration according to particular needs. Further, particular functions have been described as being performed by particular components of the system 100. This is for illustration only. In general, control and automation systems are highly configurable and can be configured in any suitable manner according to particular needs. In addition, FIGURE 1 illustrates an example environment in which annotations related to an industrial process control and automation system can be collected and stored. This functionality can be used in any- other suitable system.

[0052] FIGURE 2 illustrates an example device 200 supporting universal annotation in an industrial process control and automation system according to this disclosure. The device 200 could, for example, represent the annotation database 143, notification server 144, or end-user device 150 in the system 100 of FIGURE 1. However, the annotation database 143, notification server 144, or end-user device 150 could be implemented using any other suitable device or system, and the device 200 could be used in any other suitable system.

[00531 As shown in FIGURE 2, the device 200 includes a bus system 202, which supports communication between at least one processing device 204, at least one storage device 206, at least one communications unit 208, and at least one input/output (I/O) unit 210. The processing device 204 executes instructions that may be loaded into a memory 212. The processing device 204 may include any suitable number(s) and type(s) of processors or other devices in any suitable arrangement. Example types of processing devices 204 include microprocessors, microcontrollers, digital signal processors, field programmable gate arrays, application specific integrated circuits, and discrete circuitry.

[0054] The memory 212 and a persistent storage 214 are examples of storage devices 206, which represent any structure(s) capable of storing and facilitating retrieval of information (such as data, program code, and/or other suitable information on a temporary or permanent basis). The memory 212 may represent a random access memory or any other suitable volatile or non-volatile storage device(s). The persistent storage 214 may contain one or more components or devices supporting longer-term storage of data, such as a read only memory, hard drive. Flash memory, or optical disc.

[0055] The communications unit 208 supports communications with other systems or devices. For example, the communications unit 208 could include a network interface that facilitates communications over at least one Ethemet, HART, FOUNDATION FIELDBUS, or other network. The communications unit 208 could also include a wireless transceiver facilitating communications over at least one wireless network. The communications unit 208 may support communications through any suitable physical or wireless communication link(s).

[0056] The I/O unit 210 allows for input and output of data. For example, the I/O unit 210 may provide a connection for user input through a keyboard, mouse, keypad, touchscreen, or other suitable input device. The I/O unit 210 may also send output to a display, printer, or other suitable output device. [0057] When implementing the annotation database 143, the device 200 could execute instructions used to perform any of the functions associated with the annotation database 143. For example, the device 200 could execute instructions that receive annotations associated with data items, information about those annotations, and identifiers of the data items. The device 200 could also execute instructions that normalize the identifiers (such as URIs) or that perform other pre-storage operations on the data. The device 200 could further execute instructions that store annotations and the associated data and identifiers in the database 143. In addition, the device 200 could execute instructions that facilitate querying of stored annotations, management of the stored annotations, or other suitable functions.

[0058] When implementing the notification server 144, the device 200 could execute instructions used to perform any of the functions associated with the notification server 144. For example, the device 200 could execute instructions that detect events associated with an industrial control and automation system and that generate and transmit notifications to end-user devices. The device 200 could also execute instructions that receive comments or other annotations associated with the notifications or other comments or other annotations from the end-user devices. The device 200 could further execute instructions that provide the comments or other annotations to the database 143 for storage.

[0059] When implementing the end-user device 150, the device 200 could execute instructions used to perform any of the functions associated with the end-user device 150. For example, the device 200 could execute instructions that process notifications, present information to users, and receive comments or other annotations from users. The device 200 could also execute instructions that provide the comments or other annotations to the notification server 144 or the annotation database 143 for storage in the database 143.

[0060] Although FIGURE 2 illustrates one example of a device 200 supporting universal annotation in an industrial process control and automation system, various changes may be made to FIGURE 2. For example, components could be added, omitted, combined, further subdivided, or placed in any other suitable configuration according to particular needs. Also, computing devices can come in a wide variety of configurations, and FIGURE 2 does not limit this disclosure to any particular configuration of computing device.

[0061] FIGURE 3 illustrates an example context model 300 for supporting universal annotation in an industrial process control and automation system according to this disclosure. For ease of explanation, the context model 300 is described as being supported by the industrial process control and automation system 100 of FIGURE 1. However, the context model 300 could be supported by any other suitable system.

[0062] As shown in FIGURE 3, the context model 300 includes a mobile solution 302, which generally denotes at least part of the functionality of the notification server 144 and the application executed by the end-user devices 150. The mobile solution 302 interacts with three types of users 304-308 in this example, namely mobile users 304, product administrators 306, and system administrators 308. The mobile users 304 generally denote end users who use the end-user devices 150 to receive notifications and optionally act on those notifications. For example, the mobile users 304 could use the end-user devices 150 to review notifications regarding events in the industrial process control and automation system 100, provide comments or other annotations related to the events, and interact with other users to resolve undesirable or problematic situations in the system 100. Note, however, that the notifications could be used in any other suitable manner. The mobile users 304 could also have the ability to configure or control the notifications that are sent to those mobile users 304, such as by defining different rules used to generate the notifications.

[0063] The product administrators 306 represent users who configure the functionality of the mobile solution 302. For example, the product administrators 306 could define rules or other logic that control the generation of the notifications. As a particular example, the product administrators 306 could create rules that define the notifications sent in response to various events, the users who receive those notifications, and the contents of those notifications. In some embodiments, rules can be defined for different roles, and associations of users to those roles can be used to identify the mobile users 304 who receive notifications for those roles. As noted above, end users can also create their own rules for notifications, and the product administrators 306 could have the ability to review, modify, or delete the end user- created rules. [0064] The system administrators 308 represent users who are responsible for allowing the mobile application executed by the end-user devices 150 to be authorized in their environment. For example, the system administrators 308 could grant permissions for end-user devices 150 to access the mobile solution 302 and register the end-user devices 150 with the mobile solution 302.

[0065] The application executed by the end-user devices 150 could be provided via an electronic store or marketplace, such as a corporate store 310 or a third-party store 312. Each electronic store 310-312 generally represents a computing system hosting one or more applications or "apps" that can be downloaded to the end- user devices 150. As the names imply, the corporate store 310 denotes a computing system operated by a corporation or other entity associated with the industrial process control and automation system 100 or other system. The third-party store 312 denotes a computing system operated by a third party unrelated to the industrial process control and automation system 100 or other system, such as APPLE or GOOGLE. End users can use their end-user devices 150 to access one or more of the electronic stores 310-3 12 and download an app that supports the use of notifications related to industrial process control and automation.

[0066] Once configured and placed into operation, the mobile solution 302 receives information about events from various sources, such as one or more process control systems or applications 314. Each process control system or application 314 could represent any component within the industrial process control and automation system 100 that can generate events or data indicative of events. In some instances, a process control system or application 314 can be designed to specifically integrate with the mobile solution 302, and the process control system or application 314 ca itself provide events with or without tags (event-related information) to the mobile solution 302, In other instances, a process control system or application 314 may be unable to provide this information to the mobile solution 302 itself, and a plug-in or other mechanism can be used with the process control system or application 314 to identify events and transmit information to the mobile solution 302.

[0067] However the events are detected, the mobile solution 302 receives information about the events and uses rules or other logic to generate notifications for mobile users 304. The mobile solution 302 also sends the notifications to the end-user devices 150 of the mobile users 304. In some embodiments, the notifications are sent to the mobile users 304 directly via a third-party notification service 316, which could denote a service provided by the third-party server 148. The third-party notification service 316 could include an APPLE or ANDROID push notification service, although other push or non-push notification services could be used. The third-party notification service 316 provides the notifications to the end-user devices 150 used by the mobile users 304. Alternatively, the mobile solution 302 can generate obfuscated messages (such as unique alphanumeric codes, brief summaries, or other obfuscations) for the generated notifications, and the obfuscated messages can be sent to the third-party notification service 316 for delivery to the mobile users 304 as obfuscated notifications. The obfuscated notifications can be used by the end-user devices 150 to securely interact with the mobile solution 302 in order to obtain and present non-obfuscated notifications to the mobile users 304.

[0068] In whatever manner the notifications are provided to the end-user devices 150, the end-user devices 150 can present the notifications to the mobile users 304. For example, an end-user device 150 can receive and present a listing of notifications for a particular mobile user 304, where the listing identifies the notification messages, their associated identifiers, and some (or possibly all) of the fields of the notification messages. Annotations or other text-based communications associated with those notifications can also be provided to or received from the end- user device 50. Annotations could include communications such as comments from users or read receipts, forwarding indicators, or other system-generated annotations. In addition, context (such as detailed historical data for one or more process variables) can be provided to the end-user device 150. Note, however, that notifications can be used in any other suitable manner and that any other suitable data associated with the notifications can be sent to or received from the end-user devices 150.

[0069] Annotations received from the end-user devices 150 can be provided from the mobile solution 302 to the annotation database 143 for storage. The mobile solution 302 can also provide additional information to the annotation database 143 for use in storing the annotations in association with related data items. For example, the mobile solution 302 could provide identifiers for notifications that are associated with annotations, and the annotation database 143 could store the annotations in association with the notification identifiers. The mobile solution 302 could also or alternatively provide identifiers for events or assets that are associated with annotations, and the annotation database 143 could store the annotations in association with the event or asset identifiers. In general, a wide variety of associations can be made between annotations from mobile devices and data items within an industrial process control and automation system.

[0070] Although FIGURE 3 illustrates one example of a context model 300 for supporting universal annotation in an industrial process control and automation system, various changes may be made to FIGURE: 3. For example, additional types of users could be associated with the mobile solution 302, or functions of multiple user types could be combined. Also, while specific entities such as APPLE and ANDROID are described above, other stores or notification services could be used. In addition, various components could be added, omitted, combined, further subdivided, or placed in any other suitable configuration according to particular needs.

[0071] FIGURE 4 illustrates an example system model 400 for supporting universal annotation in an industrial process control and automation system according to this disclosure. For ease of explanation, the system model 400 is described as being supported by the industrial process control and automation system 100 of FIGURE 1. However, the system model 400 could be supported by any other suitable system. Also, in the following discussion, it is assumed that obfuscated notifications are sent to the end-user devices 150 via the third-party notification service 316 and that the end-user devices 150 request non-obfuscated notifications securely from the notification server 144. However, other mechanisms for providing notifications to the end-user devices 150 could be used, such as direct delivery of non-obfuscated notifications via the third-party notification service 316.

[0072] As shown in FIGURE 4, the system model 400 includes an event detection unit 402, a mobile notification unit 404, and a mobile services unit 406. These units 402-406 could, for example, denote different functional units of the mobile solution 302. Each of the units 402-406 could be implemented using any suitable hardware or a combination of hardware and software/firmware instructions. For instance, each of the units 402-406 could be implemented using one or more software routines executed by the processing device(s) 204 of the notification server 144.

[0073] The event detection unit 402 receives information associated with events, such as from one or more process control systems or applications 314. The information associated with the events could include information such as a time of an event, a source of the event, a condition associated with the event, a category (such as minor, major, or critical) of the event, and a description of the event. The event detection unit 402 can obtain the information about the events in any suitable manner. For example, the event detection unit 402 could poll the process control systems or applications 314 at specified intervals, in response to triggering events, or at other times. The event detection unit 402 could also receive the information from plug-ins or other data collection components in or associated with the process control systems or applications 314 at specified intervals, in response to triggering events, or at other times. The events here could represent all events generated by the process control systems or applications 314 or only a subset of events generated by the process control systems or applications 314 (such as only certain types of events). The event detection unit 402 processes the information and outputs information identifying the events, such as in a standard format, to the mobile notification unit 404.

[0074] The mobile notification unit 404 receives the information identifying the events from the event detection unit 402 and generates obfuscated notifications for end-user devices 1 50. For example, the mobile notification unit 404 can generate non- obfuscated notifications containing suitable information about the events, generate unique identifiers for the non-obfuscated notifications, and generate obfuscated notifications that include the unique identifiers. The obfuscated notifications (referred to in FIGURE 4 as notification summaries) are sent to the third-party notification service 316 for delivery to mobile applications 408. The mobile applications 408 represent an application executed by one or more end-user devices 150. The mobile notification unit 404 also provides various information, such as lists of notifications and the notifications themselves, to the mobile services unit 406.

[0075] The mobile services unit 406 interacts with each mobile application 408 securely, such as by using Virtual Private Network (VPN) or other secure communication protocol . The mobile services unit 406 performs various functions related to notifications. For example, the mobile services unit 406 could receive unique identifiers or other obfuscations from the mobile applications 408, retrieve non-obfuscated notifications associated with those obfuscations, and provide the non- obfuscated notifications to the mobile applications 408, The mobile services unit 406 can also manage lists of notifications that particular users have received, manage read-receipts for notifications that are read or viewed on the users' end-user devices 150, and allow rules to be configured by the end-user devices 1 50. The mobile services unit 406 can further provide user-generated or system-generated annotations to the end-user devices 150 and receive user annotations from end-user devices 150 for delivery to other end-user devices 150 or storage in the annotation database 143. In addition, the mobile services unit 406 ca receive invocations of various commands from the end-user devices 150, such as commands for obtaining historical data, user comments, or other contextual information about a specific notification.

[0076] Although FIGURE 4 illustrates one example of a system model 400 for supporting universal annotation in an industrial process control and automation system, various changes may be made to FIGURE 4. For example, various components could be added, omitted, combined, further subdivided, or placed in any other suitable configuration according to particular needs. Also, various components in FIGURE 4 (such as components 402-406) could be implemented using a common device, or at least some of those components could be implemented using different devices.

[0077] FIGURES 5 through 7 illustrate example notifications related to an industrial process control and automation system according to this disclosure. As shown in FIGURE 5, a graphical user interface 500 can be presented by the mobile application 408 on the display screen of an end-user device 150. The graphical user interface 500 here includes a listing of notifications 502. Each notification 502 includes various details about an event, such as a name and severity of the event, a time of the notification, and comments about the event. As shown in this example, the notifications 502 are grouped into different categories, although other categories or arrangements could be used. The graphical user interface 500 also includes various controls 504, such as controls for viewing all notifications, flagged notifications, or closed notifications and controls for changing the viewing arrangement.

[0078] Selection of a specific notification 502 in the graphical user interface 500 could cause the mobile application 408 to present a graphical user interface 600 as shown in FIGURE 6. The graphical user interface 600 includes information 602 identifying a particular event and a trend diagram 604 showing historical values of one or more process variables associated with the particular event. The graphical user interface 600 also includes specific process variable values 606 associated with the event and an identification of the rule(s) 608 that triggered the notification or that are related to the notification. Moreover, the graphical user interface 600 includes controls 610 that allow a user to close a notification, escalate the notification to one or more specific users, own the notification (meaning the user will be responsible for resolving the event), flag the notification (so it appears as a flagged notification in FIGURE 5), or share the notification with other users.

[0079] In addition, the graphical user interface 600 includes tabs 612 that can be used to select whether detailed information or historical information associated with the selected notification is being presented to the user. In FIGURE 6, the ' ^" Detail" tab has been selected. Selection of the "History" tab can present content in a graphical user interface 700 as shown in FIGURE 7. The graphical user interface 700 here includes the controls 610 and the tabs 612. The graphical user interface 700 also identifies any user comments 702 associated with the selected notification, along with a text entry box 704 that allows entry of a comment related to the selected notification. Any comment entered through the text entry box 704 can be sent from the end-user device 150 to the notification server 144 for delivery to other users who receive the notification. Comments entered through the text entry box 704 can also be sent from the notification server 144 to the annotation database 143 for storage.

[0080] The graphical user interface 700 further includes a read receipt summary 706, which identifies the number of users who have viewed/read the selected notification. The read receipt summary 706 can represent a link, which can be selected by the user to view an identification of users who have opened, viewed, or read the notification.

[0081] Although FIGURES 5 through 7 illustrate examples of notifications related to an industrial process control and automation system, various changes may be made to FIGURES 5 through 7. For example, the content and arrangement of each graphical interface are for illustration only. Also, while shown as being used with an APPLE IPHONE, the notifications could be used with any other suitable devices.

[0082] FIGURES 8 and 9 illustrate example methods 800 and 900 for supporting universal annotation in an industrial process control and automation system according to this disclosure. In particular, the method 800 could be performed by the annotation database 143, and the method 900 could be performed by the notification server 144 or other device(s) supporting other application(s) within an industrial control and automation system. However, each method could be performed using any other suitable device or system.

[0083] As shown in FIGURE 8, an annotation related to one or more data items is received at step 802, and one or more identifiers identifying the one or more data items are received at step 804. This could include, for example, the annotation database 143 receiving a user comment or other annotation from the notification server 144 along with one or more URIs or other identifiers identifying one or more related data items. The related data items could include one or more notifications, equipment or other asset parameters, or any other suitable data item(s) in an industrial control and automation system.

[0084] The one or more identifiers are normalized at step 806. This could include, for example, the annotation layer or application 143a translating each data item URI or other identifier into a standard format. Tins could also include the annotation layer or application 143a using normalization expressions obtained by the extensible mechanism 143b to determine how URIs or other identifiers can be translated into the standard format. The annotation and the normalized identifier(s) are stored at step 808. This could include, for example, the annotation database 143 storing the annotation in association with the normalized identifier(s) in relational tables or other database structures.

[0085] At this point, the stored annotation and normalized identifier(s) can be used in any suitable manner. For example, a query for searching through the contents of annotations can be received at step 810, and the annotation database can return, an identification of any annotations satisfying the query and any related identifiers at step 812. This could include, for example, the annotation database 143 searching the stored annotations to locate any annotations containing text that matches one or more search parameters. This could also include the annotation database 143 returning a listing of any annotations that satisfy the search parameters and any data item identifiers associated with those annotations.

[0086] As another example, a query for searching through the identifiers can be received at step 814, and the annotation database can return an identification of any identifiers satisfying the query and any related annotations at step 816. This could include, for example, the annotation database 143 searching the stored identifiers to locate any identifiers that partially or completely match one or more search parameters. This could also include the annotation database 143 returning a listing of any data item identifiers that satisfy the search parameters and any annotations associated with those identifiers.

[0087] A cleanup operation occurs to identify any stored annotations whose related data items have been deleted at step 818. This could include, for example, the annotation database 143 attempting to access each data item using the URI or other identifier for that data item. If a data item cannot be accessed, the annotation database 143 could perform one or more actions with respect to any annotations associated with that data item, such as by deleting the annotations or archiving the annotations.

[0088] As shown in FIGURE 9, an annotation related to one or more data items is obtained at step 902, and one or more identifiers identifying the one or more data items are obtained at step 904. This could include, for example, the notification server 144 obtaining a user comment associated with a notification and obtaining one or more URIs or other identifiers identifying the notification, an asset parameter associated with the event, or other data item(s). The annotation and the identifier(s) are transmitted to an annotation database for storage at step 906. This could include, for example, the notification server 144 transmitting the annotation and the identifier(s) to the annotation database 143. This could be done when the annotation and identifier(s) are obtained, at a scheduled interval, or at any other suitable time.

[0089] At this point, the stored annotation and identifier(s) can be used in any- suitable manner. For example, a query for searching through the contents of annotations can be transmitted at step 908, and an identification of any annotations satisfying the query and any related identifiers can be received at step 910. This could include, for example, the notification server 144 receiving from the annotation database 143 a listing of any annotations that satisfy ⁷ one or more search parameters and any data item identifiers associated with those annotations.

[009Θ] As another example, a query for searching through the identifiers can be transmitted at step 912, and an identification of any identifiers satisfying the query and any related annotations can be received at step 914. This could include, for example, the notification server 144 receiving from the annotation database 143 a listing of any data item identifiers that satisfy one or more search parameters and any annotations associated with those identifiers.

[0091] Note that the application providing annotations and identifiers to the annotation database 143 need not be the same application querying the annotation database 143. Also, the annotations and identifiers received by an application from the annotation database 143 need not be the same annotations and identifiers provided by- thai application. As noted above, for example, a logbook or other application could query the annotation database 143 for annotations, including those provided by the notification server 144 related to notifications. In general, any suitable source can provide annotations to the annotation database 143, and any suitable destination can query the annotation database 143.

[0092] Also note that while shown as returning the data item identifiers as part of a query, the annotation database 143 could instead use each data item identifier to access and retrieve the associated data item. The annotation database 143 could then return the retrieved data items in response to a query, rather than or in addition to returning the URIs or other identifiers for those data items.

[0093] Although FIGURES 8 and 9 illustrate examples of methods 800 and 900 for supporting universal annotation in an industrial process control and automation system, various changes may be made to FIGURES 8 and 9. For example, while each figure shows a series of steps, various steps in each figure could overlap, occur in parallel, occur in a different order, or occur any number of times. Also, each method could include any number of annotations, data items, and data item identifiers.

[0094] Note that while the above description often describes the universal annotation functionality in conjunction with annotations sent to or from mobile devices, the universal annotation functionality is not limited by that particular use. The universal annotation functionality can find use in a large number of industrial environments and may or may not be used to store annotations sent to or from mobile devices.

[0095] In some embodiments, various functions described in this patent document are implemented or supported by a computer program that is formed from computer readable program code and that is embodied in a computer readable medium. The phrase "computer readable program code" includes any type of computer code, including source code, object code, and executable code. The phrase ' ^" computer readable medium' ^* includes any type of medium capable of being accessed by a computer, such as read only memory (ROM), random access memory (RAM), a hard disk drive, a compact disc (CD), a digital video disc (DVD), or any other type of memory. A "non-transitory' ^* computer readable medium excludes wired, wireless, optical, or other communication links that transport transitory electrical or other signals. A non-transitory computer readable medium includes media where data can be permanently stored and media where data can be stored and later overwritten, such as a rewritable optical disc or an erasable memory device.

[0096] It may be advantageous to set forth definitions of certain words and phrases used throughout this patent document. The terms "application" and "program" refer to one or more computer programs, software components, sets of instructions, procedures, functions, objects, classes, instances, related data, or a portion thereof adapted for implementation in a suitable computer code (including source code, object code, or executable code). The term "communicate," as well as derivatives thereof, encompasses both direct and indirect communication. The terms "include" and "comprise," as well as derivatives thereof, mean inclusion without limitation. The term "or" is inclusive, meaning and/or. The phrase "associated with," as well as derivatives thereof, may mean to include, be included within, interconnect with, contain, be contained within, connect to or with, couple to or with, be communicable with, cooperate with, interleave, juxtapose, be proximate to, be bound to or with, have, have a property of, have a relationship to or with, or the like. The phrase "at least one of," when used with a list of items, means that different combinations of one or more of the listed items may be used, and only one item in the list may be needed. For example, "at least one of: A, B, and C" includes any of the following combinations: A, B, C, A and B, A and C, B and C, and A and B and C. [0097] The description in this patent document should not be read as implying that any particular element, step, or function is an essential or critical element that must be included in the cl aim scope. Also, none of the claims is intended to invoke 35 U.S.C. § 112(f) with respect to any of the appended claims or claim elements unless the exact words "means for" or "step for" are explicitly used in the particular claim, foilovved by a participle phrase identifying a function. Use of terms such as (but not limited to) "mechanism," "module," "device," "unit," "component," "element," "member," "apparatus," "machine," "system," "processor," "processing device," or "controller" within a claim is understood and intended to refer to structures known to those skilled in the relevant art, as further modifi ed or enhanced by the features of the claims themselves, and is not intended to invoke 35 U.S.C. § 112(f).

[0098] While this disclosure has described certain embodiments and generally associated methods, alterations and permutations of these embodiments and methods will be apparent to those skilled in the art. Accordingly, the above description of example embodiments does not define or constrain this disclosure. Other changes, substitutions, and alterations are also possible without departing from the spirit and scope of this disclosure, as defined by the following claims.