A DeltaV Batch Historian receives data from the DeltaV control system and saves that data to a SQL Server database. Several client applications make the data available to users. The figure below shows how information flows into and out of the Batch Historian
A Batch Executive is the source of recipe execution information. As a batch executes, batch events generated by the Batch Executive are passed to the Batch Historian and stored in the main database. The Campaign Manager is the source of campaign execution data. Like Batch Executive, Campaign Manager automatically feeds campaign-related events to the Batch Historian for storage. The Event Chronicle is the source of process-related alarms and events, including operator changes, system messages, and user-defined events. The Batch Historian copies this data into the main database so that process data can be included in batch reports and queries.
Up to four Batch Historians can be enabled in a DeltaV system. A single Batch Historian can receive events from multiple Batch Executives and Campaign Managers; however, Batch Executives and Campaign Managers can feed their events to only one Batch Historian.
Data stored in the Batch Historian database is viewed using Batch History View and other example Batch Historian client applications. The clients include Batch Historian Administration, Batch Report, Batch Equipment Report, Campaign Report, and Batch Query. (Batch History View and Batch Historian Administration are fully supported clients. The other clients are report/query applications that can be used as provided or customized using standard SQL queries and Visual Basic. The source code is included on the DeltaV installation disk.)
Information Flow in the Batch Historian
Data received and stored by the Batch Historian includes: