PI Audit database top-level records

Column Name

Description

Example

Category

The category to which the database affected by the audited action belongs. See PI database categories.

TimeSeriesDB, ConfigurationDB, SecurityDB, SystemDB

PI Database

The name of the PI Database that was affected by the audited action. See PI database categories.

PIPoints, PI Modules, PIBatch

DB RecordName and DB RecordID

All PI Audit Database records have a DB RecordName and DB RecordID determined by the particular AVEVA™ PI System™ database in which they originate.

In the PI Point database, the default PI point CDT158 has a DB RecordName=CDT158 and DBRecordID=3. In this example, DBRecord ID is only unique for a particular Data Archive server or collective.

Effective Date

The effective date and time of the audited action. The effective date and time of the module for the audited action.

31-Dec-69 16:00:01

Audit Action

The type of audit action.

• Add: Create a new PI point.

• Remove: Permanently delete a PI point.

• Edit: Edit the attributes of a PI point, or edit a value in the PI Archive. For State Sets databases, adding a Digital State to a State Set is recorded as an Edit of the State Set in the State Set database.

Action Time

The date and time when the audited action occurred.

2009-10-05 16:39:31

PI UserName and PI UserID

These attributes identify the user who is responsible for an audited action: For users authenticated through Microsoft Windows, the PI UserName is the name of the user's Windows account. For users authenticated through a PI Trust or through user password authentication (explicit login), the PI UserName is the name of the PI Identity. For more information on authentication and PI Identities, see Authentication management with Windows security.

The Windows user jsmith mapped to the PI Identity piadmins: PI UserName=jsmith and PI UserID=10.

The Windows user jsmith explicitly logging on as piadmin authenticated through explicit login: PI UserName=piadmin and PI UserID=1