Verify your event frame data

To verify your resulting event frame data:

1. Confirm that PI batch interfaces, version 4.0, or later, have automatically switched to event frames.

   The interfaces log file PIPC.Log will include messages about migration and cutover:

   • When the interface fails to write to the PI Batch Database, because batch to event frame migration is occurring:

     PI Batch Database to event frames migration is in progress.

   • When migration is complete:

     PI Batch Database is read-only because it has been migrated to event frames. Interface will create event frames in the PI Asset database: AFserver\\AFdatabase

     Where AFserver is the name of the PI AF server, and AFdatabase is the name of the AF database, to which Data Archive is migrating batches.

2. Confirm that the PI Batch Database is read-only.

   The AF Link tool shows you if the Batch Database is read-only. Also, if you attempt to edit batch data the edit will be rejected.

3. Enable or start up any PI EFGen (PI Event Frames Generator) or non-Batch Framework interfaces that create PI Event Frames data.

4. Confirm that event frames were properly migrated by looking at the Batch database status field in the AF Link tool and by checking the Migration errors report.

   You might also want to perform a random check of a few event frames in PI System Explorer. To look at an individual event frame, right-click it and choose Properties, you can verify that the start time and end time make sense and use the Attributes tab to check values such as Batch ID, Procedure, and Product. You might also want to look at the overall event frame hierarchy in PI System Explorer to check it looks as expected.

   Note: You can click Extended Properties to see information such as the original object name before any truncation or character replacement took place during migration.

5. In any reporting tools you use, confirm that batch data is being presented properly in event frame format to your end users.