Verification execution

Task:	Verification execution
Who receives it:	▪Team members responsible for the execution of the asset verification defined in the verification plan ▪Executor user, defined during verification programming.
When:	▪The verification programming is closed, if the verification activity does not have an approval step configured. ▪The programming is approved, if this step is configured in the verification activity.
Purpose:	To execute the verification of assets.

How to execute this task:

1.Select the desired verification from the list of pending records.

2.Click on the button to edit the verification data. See the Executing the verification section for details of how to enter the execution information.

3.After completing all information of the verification execution, click on the Execute button, located on the verification data screen, to send the verification to the next step. At this point, the system will ask whether you wish to send the record to the next step:

▪If it is not confirmed, the record will remain pending and this action may also be executed by clicking on the button on the toolbar.

▪If confirmed, the record may move on to one of the following steps:

ºExecution approval: The record will move on to this task if the standard activity associated with the verification plan is configured with the execution approval step

ºFinished: If the approval step is not configured in the activity, then the verification will be finished.

4.To execute activities in batches, that is, several activities at the same time, use the "More Finish" button located on the toolbar of the verification execution task screen. The button allows finishing activities in batches without the need to open the data screen.

Even if an activity is under the "To be started" status, the system will finish the activity, without going through the "Execution" status. The start and/or end date/time fields that are not filled out will be automatically completed by the system. The executor will also be filled out by the system with the user that is performing the batch execution. If there is approval, the system will send it to Execution approval and not to Finished.

For batch execution to be possible, the activities must not have fields with mandatory completion.