Abstract: The disclosure describes a system for the advanced delivery of information. In some embodiments, the system creates a display in response to an alarm. In some embodiments, the information on the display is a function of attribute mapping and/or analysis performed by the system. The system uses one or more of manual links, statistical analysis, correlations, maintence data, and/or historical data as tools during determination of what to display according to some embodiments. In some embodiments, the system uses one or more of these tools in conjunction with one or more of process simulators, artificial intelligence, machine learning, and/or real process feedback in the analysis to determine what to display to a user during an emergency and/or an anomalous event.

Abstract: The disclosure describes a system for the advanced delivery of information. In some embodiments, the system creates a display in response to an alarm. In some embodiments, the information on the display is a function of attribute mapping and/or analysis performed by the system. The system uses one or more of manual links, statistical analysis, correlations, maintenance data, and/or historical data as tools during determination of what to display according to some embodiments. In some embodiments, the system uses one or more of these tools in conjunction with one or more of process simulators, artificial intelligence, machine learning, and/or real process feedback in the analysis to determine what to display to a user during an emergency and/or an anomalous event.

Abstract: A multi-tiered replicated process database and corresponding method are disclosed for supporting replication between tiers. The multi-tiered replicated process database comprises a tier one (T1) database server computer including a process history database and a replication service. The replication service includes a set of accumulators. Each accumulator is adapted to render a summary T2 database tag data structure from a set of data values retrieved from the process history database for a specified T1 database tag. The replicated database system also includes a tier two (T2) database server computer comprising a consolidated database that includes process data replicated from a set of T1 database servers. At least a portion of the process data replicated from the set of T1 database servers is summary T2 database tag data rendered by the set of accumulators.

Abstract: A multi-tiered replicated process database and corresponding method are disclosed for supporting replication between tiers. The multi-tiered replicated process database comprises a tier one (T1) database server computer including a process history database and a replication service. The replication service includes a set of accumulators. Each accumulator is adapted to render a summary T2 database tag data structure from a set of data values retrieved from the process history database for a specified T1 database tag. The replicated database system also includes a tier two (T2) database server computer comprising a consolidated database that includes process data replicated from a set of T1 database servers. At least a portion of the process data replicated from the set of T1 database servers is summary T2 database tag data rendered by the set of accumulators.

Abstract: A database server for handling steams of time stamped data points for tagged variables is disclosed herein that supports a set of advanced data retrieval operations/queries invoked by clients of the database server. The advanced data retrieval operations are invoked by client queries to provide, on demand, secondary information by processing previously tabled data corresponding to received data streams rendered by a variety of data sources in a supervisory control/monitoring, process control and/or automated equipment environment. Calculations, on previously stored data, for rendering the secondary information are performed within the database server at the time the secondary information is requested by a client of the historian that maintains a database containing the previously stored data. Moreover, a filtering stage and enhanced time-in-state processing operations are supported.

Abstract: Disclosed are techniques for synchronizing software objects in one namespace with software objects in another namespace. When a change is detected in the first namespace (such as the addition, deletion, or movement of a software object), only as much information as is needed to characterize the change is sent to the second namespace. The second namespace then replicates the changed status of the first namespace. In one embodiment of the invention, an Archestra namespace is synchronized with an InSQL namespace by applying the public/private namespace capability of InSQL.