Start the Batch Historian after the Application Station has been downloaded with the setup information for the Historian. The Batch Historian runs as a service and is started using the Batch Historian Administration client.
Open the Batch Historian Administration client by choosing DeltaV | Batch | Historian Administration Tool from the Start menu on a DeltaV machine or Start | Programs | FRSI | Batch Historian Clients | Batch Historian Administration on a non-DeltaV machine. Connect to the local Batch Historian and select Start/Stop Historian from the Server menu on the Batch Historian Administration toolbar. This command is also available from the context menu when a server is selected. The status of the connected Batch Historian is shown in the status bar at the bottom of the Batch Historian Administration window.
Once the Batch Historian is running, it will begin reading data generated by the Batch Executive and Event Chronicle defined as inputs during the setup step. This could include data that the Batch Executive generated prior to the Batch Historian being started. If Campaign Manager is running, campaign data will be collected as well.
Note If the configured Event Chronicle is deleted and recreated, you must stop and restart the Batch Historian to synchronize the record numbers.
With the Batch Historian running, select Start/Stop Historian from the Server menu on the Batch Historian Administration toolbar to stop the Batch Historian. This command is also available from the context menu when a server is selected.
Note You must be a member of the Windows Administrator's group or the local DVBHisAdmin group to run the Batch Historian.
If the time zone is changed on the Batch Historian machine, you must start and stop the Batch Historian to re-synch to the new time zone. It may be necessary to restart the Batch Historian machine, if new time stamps are not recording correctly. Also, archives will be in a different time zone and cannot be changed.