PI Manual Logger audits

PI Manual Logger contains several auditing features that enable you to validate changes that users have made.

Audits of PI Data Archive

Security on the PC application is integrated with PI trusts or PI mapping. When users log in to a PC workstation and start PI Manual Logger, they are authenticated against the established PI trust or PI mapping on the currently connected PI Data Archive. After they are authenticated, they can access data in PI Data Archive. Furthermore, if they enter data into PI Data Archive, the changes made to tag values are audited in the PI audit database.

Audits on changes to the user database

Administrators can audit changes in the user database, such as user password changes and user group relationship changes. You select Tools > Global Options and then select the Message Logging tab. The following options are available:

• Log user logon/off activities

• Log user group membership changes

• Log tour permission group changes

• Log user password change events

• Log Admin user group changes

Audits of tour definition deletion and creation events

You can audit tour definition creation and deletion events. You select Tools > Global Options and then select the Message Logging tab. The following options are available:

• Log tour definition creation events

• Log tour definition deletion events

Audits on data transfer

All successful data transfers from PI Manual Logger to PI Data Archive are audited and logged into the PI Manual Logger database. To view these logs, use the Message Log Viewer. The following option is available:

• Log send to PI events

Audits on Manual data must be submitted for approval tour option

If the tour option Manual data must be submitted for approval is set to True, submit and approve events can be logged to the Message Log if the following options are enabled:

• Log tour run data approval events

• Log tour run data submit events

Audits on data changes in PI Manual Logger

If a user makes changes to an existing tag value, its timestamp, or its comment, the action is audited and saved in the tour run audit trail. You can view the audit trail in the tour run audit log.

Audits on duration of tour runs

The duration of a tour run is recorded and saved in the dbo.tblTourRunAuditLog table in the AuditLog field. The format for this information is as follows:

Total Duration: 00:00:29
Session 1: Duration: 00:00:04 Start Time: 2017-06-30T17:05:46.789Z End Time: 2017-06-30T17:05:51.245Z
Duration Between Sessions: 00:00:14
Session 2: Duration: 00:00:24 Start Time: 2017-06-30T17:06:05.518Z End Time: 2017-06-30T17:06:29.909Z