Batch Historian database security

The Windows user group 'DVBHisAdmin' controls which users have write-access to the Batch Historian database required for configuring and managing the database. Configuring and managing the database is accomplished through the Batch Historian Administrator's Tool. Any function not covered in the Batch Historian Administrator's Tool application (adding comments, for example) requires additional keys be assigned to the individual user or to the 'DVBHisAdmin' group. The 'DVBHisAdmins' group must also have full access to any auto-archive folder.

The Windows User Group 'DVBHisUsers' controls which users have read-access to the Batch Historian database required for running Batch Historian client applications (such as Batch History View) which need access to the database. Write-access is permitted only for marking a reference batch and adding comments. Write functions require the appropriate security keys be assigned to the individual user or to the 'DVBHisUsers' group.

Refer to the Batch Functions Security topic for information about the specific DeltaV batch locks and keys.

Both the DVBHisAdmin and DVBHisUsers groups are local groups on the Batch Historian Server node if DeltaV software is installed in a workgroup environment; or, are domain groups if DeltaV software is installed in a domain environment. All DeltaV accounts that will access the Batch Historian must be added to the DVBHisUser group; and, users requiring write-access must be added to the DVHisAdmins group (added by using DeltaV User Manager). To add non-DeltaV accounts as members into these Windows groups, you must log in to Windows as Administrator, select the group, and add the desired users.

The following table outlines the main functions available through the Batch Historian Administrator's Tool and the minimum security needed to perform those functions.