Abstract: An event historian system receives event data from a client system via a network connection and stores the event data in a block data storage system. An event data block in which to store the received event data is selected based on the time range of the occurrence of the received event data. The received event data is stored in a snapshot within the event data block. Event property data is extracted from the received event data and used to build a plurality of event property index files.

Abstract: Annotating content, comprising data values of one or more tags corresponding to a process device within a continuous process, with content descriptors in a historian system. Content descriptors enable indexing and saving content within a search service database for later retrieval by search strings that match the content descriptors. Content having one or more common content descriptors are retrieved and transmitted to a client computing device via a communications network for displaying in a dashboard on the client computing device.

Abstract: Operational historian system retrieving summary data values and source data values based on alignment between a summarization cycle duration and a query cycle duration. A retrieval service process executing on a historian device utilizes a summarization cycle duration, including start and/or end times thereof, and a query cycle duration, including start and/or end times thereof, to determine whether to retrieve, via a communications network, source tag data and/or summary tag data from memory storage devices.

Abstract: A server system can operate to function as an automatic association of tags defining a system within a process. The operations include accessing tags and associated signals including a plurality of data values over time indicative of a physical property, behavior or measurement of a component of the process. For each signal, calculating a time-weighted average over a specific time period, selecting a specific number of different day periods sampled from the tags and signals, and for each tag, calculating a slope and intercept by calculating a linear regression of plurality of signals over the specific time period. Further, calculating a residual value of each data value of the signals over the specific time period, and calculating a normalized value of each residual value, and then calculating the absolute value of the dot product of the normalized residual value and the residual value of a subsequent number of tags.

Abstract: Processing raw data stored in an historian device for determining an amount of products passed through a process element in a process control environment is described. A count value is incremented by a counter at a rate at which products pass through the process element. The count value rolls over to zero when the count value reaches a rollover value R. An historian device periodically receives count value data points from the counter. A deadband value D is set in the historian device for distinguishing between rollovers, resets, and reversals. A client device queries the historian device for an amount of products passed through the process element for a timeframe. The historian device selects a set of count value data points from within the queried timeframe. The historian device determines, based on the selected data points and their quality, an amount of products passed through the process element.

Abstract: Disclosed are systems, servers and methods for a multi-tenant framework that manages and controls operations of software as a service (SaaS) applications and services, and the data and metadata (e.g., files) created, updated and interacted with therefrom. The disclosed framework provides a centralized approach to managing the entitlement and provisioning of SaaS applications on client devices across a variety of channels on a network. The disclosed SaaS framework is configured for management, control, deployment and synchronization between devices, applications, systems and platforms both on-premises (on-prem or local devices/storage) and/or hosted on a network (e.g., a cloud platform, service or platform).

Abstract: Some embodiments of the invention provide systems and methods for securing configuration information for cloud-based services. Some embodiments include a system comprising a data store and data sets including plant process information and configuration information. A memory device stores computer-executable instructions executable by a processor coupled to the cloud service. When executed, the instructions receive configuration information, store it in a data file, apply a generated certificate to the file, and deploy the resulting protected configuration data file to the cloud-based service. In addition, the protected configuration data file is made available by obtaining the file from the cloud-based service.

Abstract: Disclosed are systems, servers and methods for a multi-tenant framework that manages and controls operations of software as a service (SaaS) applications and services, and the data and metadata (e.g., files) created, updated and interacted with therefrom. The disclosed framework provides a centralized approach to managing the entitlement and provisioning of SaaS applications on client devices across a variety of channels on a network. The disclosed SaaS framework is configured for management, control, deployment and synchronization between devices, applications, systems and platforms both on-premises (on-prem or local devices/storage) and/or hosted on a network (e.g., a cloud platform, service or platform).

Abstract: A server system can operate to function as an automatic association of tags defining a system within a process. The operations include accessing tags and associated signals including a plurality of data values over time indicative of a physical property, behavior or measurement of a component of the process. For each signal, calculating a time-weighted average over a specific time period, selecting a specific number of different day periods sampled from the tags and signals, and for each tag, calculating a slope and intercept by calculating a linear regression of plurality of signals over the specific time period. Further, calculating a residual value of each data value of the signals over the specific time period, and calculating a normalized value of each residual value, and then calculating the absolute value of the dot product of the normalized residual value and the residual value of a subsequent number of tags.

Abstract: Systems and methods for securing configuration information for cloud-based services. A system comprises a data store and data sets including plant process information and configuration information. A memory device stores computer-executable instructions. When executed by a processor coupled to the cloud service, the instructions receive configuration information, store it in a data file, apply a generated certificate to the file, and deploy the resulting protected configuration data file to the cloud-based service. In addition, the protected configuration data file is made available by obtaining the file from the cloud-based service.

Abstract: Operational historian system retrieving summary data values and source data values based on alignment between a summarization cycle duration and a query cycle duration. A retrieval service process executing on a historian device utilizes a summarization cycle duration, including start and/or end times thereof, and a query cycle duration, including start and/or end times thereof, to determine whether to retrieve, via a communications network, source tag data and/or summary tag data from memory storage devices.

Abstract: A historian system stores data values and associated metadata. The system has a historian data server, a metadata server, and one or more data collector devices. The data collector devices collect data values from a set of one or more connected hardware devices and send the collected data values to the historian data server. The data collector devices also create tag metadata associated with the collected data values and send the created tag metadata to the metadata server. The historian data server receives the collected data values and stores the collected data values in a memory storage device. The metadata server receives the tag metadata and stores the tag metadata in a memory storage device.

Abstract: Automated recovery of execution roles in a distributed historian system in accordance with actions and rules customized to each execution role. A monitoring service monitors the health status of execution roles and automatically performs a corrective action in response to the health state of an execution role triggering a predetermined rule.

Abstract: Embodiments of the invention provide a management console enabling monitoring of distributed components of a process control application. The management console includes a management console window that can be customized according to one or more user-defined software code modules that interface to data sources to populate views supported by the console window. The invention further includes a language and method of composing blocks of executable code within the management console that provide the capability to run many analyses simultaneously. The console window includes a set of view templates including controls for manipulating graphically displayed representations of data rendered by the distributed components, and an interface for exchanging requests and data with an extensible set of software modules that provide data links to one or more distributed data-linked components. The set of software modules also define the customizable portions of the view rendered by the console window.

Abstract: A system for historizing process control data. A configurator module registers a data source device with a historian server and indicates to the historian server to generate data source registration information for identifying the registered data source device. The historian server generates and stores the data source registration information. The historian server also generates a connection token comprising the data source registration information. The configurator module forwards the connection token to the data source device, which stores the token and sends it to the historian server with data. The historian server compares the connection token received from the data source device to the connection token stored by the historian server, wherein if they match, the historian server stores the data from data source device.

Abstract: Automated correlation of process attribute value changes with events related to the changes. A managed historian utilizes a namespace property to correlate process tag values with corresponding events. The managed historian generates and provides to remote user devices a graphical user interface that includes a plot of data values of the process tag and a visual icon representing the event overlaid atop the plot of data values.

Abstract: Operational historian system retrieving summary data values and source data values based on alignment between a summarization cycle duration and a query cycle duration. A retrieval service process executing on a historian device utilizes a summarization cycle duration, including start and/or end times thereof, and a query cycle duration, including start and/or end times thereof, to determine whether to retrieve, via a communications network, source tag data and/or summary tag data from memory storage devices.

Abstract: Processing raw data stored in an historian device for determining an amount of products passed through a process element in a process control environment is described. A count value is incremented by a counter at a rate at which products pass through the process element. The count value rolls over to zero when the count value reaches a rollover value R. An historian device periodically receives count value data points from the counter. A deadband value D is set in the historian device for distinguishing between rollovers, resets, and reversals. A client device queries the historian device for an amount of products passed through the process element for a timeframe. The historian device selects a set of count value data points from within the queried timeframe. The historian device determines, based on the selected data points and their quality, an amount of products passed through the process element.

Abstract: Targeted distributing of reports containing historical process control information to particular user devices via a communications network. A curating service permits assigning a score to each report based on an interest level value of the historical process control information to a user associated with each user device and/or an urgency value of the historical process control information. Routing reports to user devices based on the score raises visibility of the historical process control information without overburdening the communications network.

Abstract: Associating comments with tags in a managed historian system in accordance with a flexible, platform-independent data structure. A worker role instance automatically associates received comments with a process tag at a particular time in response to receiving the comments. The worker role instance stores the comments in the flexible, platform-independent data structure such that the comment is provided in association with the tag at the particular time in response to a display or search request for the tag.