Abstract: User interface sessions in a user interface device are initiated or resumed according to stored state data. A session request is received from a first client device. A user profile associated with the session request is identified and a determination made as to whether a previous session exists. If no previous session exists, a new session is instantiated using a default session configuration. If a previous session exists, a new session is instantiated according to the previous session.

Abstract: User interface sessions in a user interface device are initiated or resumed according to a device type and a target session. A session request is received from a first client device. A device type associated with the session request is determined, and a graphical user interface configuration is identified according to the device type. A target session associated with the session request is identified and a new session is configured for the first client device according to the identified graphical user interface configuration and the identified target session. Data associated with the new session are transmitted to the first client device.

Abstract: Techniques for securing a device for use in or with a process plant include provisioning the device with a key generated at least in part from data indicative of necessary conditions and/or attributes that must be met before the device is allowed access to a network of the process plant. Upon initialization, the device determines, based on the key, whether or not the necessary conditions are met, and the device isolates itself or accesses the process control network accordingly. Keys and the necessary conditions/attributes indicated therein may be based on, for example, location, time, context, customer, supplier, particular plant, manufacturer, user, data type, device type, and/or other criteria. Additionally, sub-keys associated with a key may be generated from another set of necessary conditions/attributes. Sub-keys may be provided by a different entity than the key provider entity.

Abstract: Techniques for securing a device for use in or with a process plant include provisioning the device with a key generated at least in part from data indicative of necessary conditions and/or attributes that must be met before the device is allowed access to a network of the process plant. Upon initialization, the device determines, based on the key, whether or not the necessary conditions are met, and the device isolates itself or accesses the process control network accordingly. Keys and the necessary conditions/attributes indicated therein may be based on, for example, location, time, context, customer, supplier, particular plant, manufacturer, user, data type, device type, and/or other criteria. Additionally, sub-keys associated with a key may be generated from another set of necessary conditions/attributes. Sub-keys may be provided by a different entity than the key provider entity.

Abstract: Techniques for securing a device for use in or with a process plant include provisioning the device with a key generated at least in part from data indicative of necessary conditions and/or attributes that must be met before the device is allowed access to a network of the process plant. Upon initialization, the device determines, based on the key, whether or not the necessary conditions are met, and the device isolates itself or accesses the process control network accordingly. Keys and the necessary conditions/attributes indicated therein may be based on, for example, location, time, context, customer, supplier, particular plant, manufacturer, user, data type, device type, and/or other criteria. Additionally, sub-keys associated with a key may be generated from another set of necessary conditions/attributes. Sub-keys may be provided by a different entity than the key provider entity.

Abstract: Techniques for securing a device for use in or with a process plant include provisioning the device with a key generated at least in part from data indicative of necessary conditions and/or attributes that must be met before the device is allowed access to a network of the process plant. Upon initialization, the device determines, based on the key, whether or not the necessary conditions are met, and the device isolates itself or accesses the process control network accordingly. Keys and the necessary conditions/attributes indicated therein may be based on, for example, location, time, context, customer, supplier, particular plant, manufacturer, user, data type, device type, and/or other criteria. Additionally, sub-keys associated with a key may be generated from another set of necessary conditions/attributes. Sub-keys may be provided by a different entity than the key provider entity.

Abstract: User interface sessions in a user interface device are initiated or resumed according to a device type and a target session. A session request is received from a first client device. A device type associated with the session request is determined, and a graphical user interface configuration is identified according to the device type. A target session associated with the session request is identified and a new session is configured for the first client device according to the identified graphical user interface configuration and the identified target session. Data associated with the new session are transmitted to the first client device.

Abstract: User interface sessions in a user interface device are initiated or resumed according to stored state data. A session request is received from a first client device. A user profile associated with the session request is identified and a determination made as to whether a previous session exists. If no previous session exists, a new session is instantiated using a default session configuration. If a previous session exists, a new session is instantiated according to the previous session.

Abstract: Systems and methods for providing an integrated HMI application for monitoring and interacting with both batch and non-batch processes in a process plant are disclosed. A plurality of independent stand-alone software objects defining various batch process interface views are embedded within a non-batch process control interface application. A blackboard service is provided for storing batch control data used by the various stand alone software objects. The blackboard service may be adapted to communicate with a batch control server to receive batch control data for populating the various batch interface views with data relating to various batch processes being carried out in the process plant and to send instructions for controlling the various batches input by users via the various batch interface views.

Abstract: A process control system capable of executing a function after initiation thereof by a user includes a computer having a memory and a processing unit. A security module stored in the memory of the computer and adapted to be executed on the processing unit of the computer analyzes security information to determine whether the function should be executed. The security information is collected contemporaneously with the initiation of the function and in association therewith.

Abstract: Improved method and apparatus for controlling thermal stress on component parts of a steam turbine while providing maximum loading and unloading rates during startup, shutdown, and other periods of load change. From monitored and derived quantities, a loading rate is calculated for each of a plurality of preselected turbine component parts and the lowest rate is selected for control. Simultaneously, and in concert with load change calculation and execution, the steam admission mode of the turbine is automatically directed to either the partial arc mode or the full arc mode as necessary to reduce stress as compared with a preselected and adaptive stress reference value.