Understanding Verification Template
The image below illustrates how Verification Template is configured in RiskView.
As shown in the image, contents of the Verification derive from the contents specified in Verification Template, so it is important to have the Verification Template set up properly before rolling out the Control Assurance in your system.
Before creating the Verification Template, it is important that the following components are populated in RiskView as they are the core elements in the Control Assurance workflow:
- Created Performance Standards with valid Performance Criteria
- Assigned Verification Manager in Risk Register Manager
- Created Base Controls and linked up to appropriate Risk Controls in Bowties (this is a requirement for Critical Risk Control Verification)
- Optional: Created Major Accident Events and linked up to appropriate Bowties
Once the aforementioned components are present in your system, you can start creating your own Verification Template. To do that, click on Browse and navigate to Risk Studies -> Verification Templates. Once you are in that view, click on the “+” button from the toolbar just like how you create bowties.
Once you’ve clicked on the “+” button, the new item’s properties panel will pop up.
The table below shows the purpose of each editable field in the Verification Template:
|Code||This field is normally populated automatically when you create a new item. It is used as a unique identifier.|
|Name||This is where you specify the name of the Template.|
|Type||This is where you can specify a Performance Standard Type for the Template. This information will be attached to the Verification Activities created and it is used as filter information for the following dashlets:|
|Description/Purpose||Specify the description/purpose of the Template to give some context to the person who will be completing the Verification.|
|Introduction||The contents of this field will appear on the first page of the Verification. This field supports HTML text formatting (such as font size, colour, tables).|
|Steps to be Performed||Specify the steps to take to complete the Verification.|
|Items to be Verified||Specify which entity will be included in the Verification. The different options will be further discussed in the next section.|
|Register Scope||Specify where the Verification is going to be created.|
|Content Scope||Specify the content scope of the Verification. More on this will be further discussed in the next section.|
|Recurring||Select the recurrence period for the Verification.|
|Due Date||Specify the due date for the Verification (this option is only available if no recurrence period is specified).|
|Time to Complete||Specify the time to complete Verification (this option will appear when recurrence period is specified).|
|Status||Specify the status of the Verification Template.|
Capabilities of the Introduction field
The Introduction field supports HTML text formatting, and the contents in the section will be displayed on the first page of the Verification.
Some features of this field include:
- Font formatting (emphasis, colour, size)
- Insert images from web
- Create tables
Different Type of Items to be Verified
At the time of this article is written, there are 6 types of Verifications user can choose from, namely:
- Critical Risk Control Verification
- Bowties Review
- Risk Scenarios (via Major Accident Events)
- Major Accident Event (directly)
- Performance Standards (directly)
- Base Controls (Design Verification)
- As Defined in Verification Template
Critical Risk Control Verification:
When this option is selected, a Verification will be created if matching criteria is found. This option requires the following to generate the Verification:
- Critical Base Control
- Performance Standard
- Optional: Major Accident Event
For example, a Critical Base Control called “High Level Alarm” is used in a bowtie and it is selected in the Verification Template. The Template will then create 1 Verification. If a Major Accident Event is specified in the Template as the additional filter, the Verification will be created depending on the bowtie which “High Level Alarm” is attached to (no Verification if the attached Major Accident Event does not meet the one from Template or bowtie does not have Major Accident Event attached).
When this option is selected, a Verification will be created for every bowtie that exceeds the risk rating score specified in the Template. This option will use the Critical Risk Controls in the related bowtie as the criteria for the Verification.
For example, the bowtie “Falling from Height” has 3 Critical Risk Controls (e.g. fall arrest, emergency response, training) and it has a risk rating of “Medium (16)”. A Verification will be created if the risk rating threshold specified in the Template is less than that, and the Verification will use those 3 Critical Risk Controls as the criteria.
Risk Scenarios (via Major Accident Events):
When this option is selected, a Verification will be created if matching criteria is found. Similar to the Critical Risk Control Verification, this option requires the following to generate the Verification:
- Major Accident Event
- Performance Standard
For example, a Major Accident Event called “Explosion” is attached to a bowtie and it is selected in the Verification Template, the Template will then create 1 Verification. If no bowtie matching the Major Accident Event is found, no Verification will be created.
As Defined in Verification Template:
When this option is selected, user does not need to specify the entity to be verified. The Template will create the Verification in the specified Register (depending on the Register Scope).
User has the option to specify certain aspects related to the Verification (such as MAE or Base Control). Additionally, user also has the option to update those related items upon completion of the Verification.
For example, an “Explosion” MAE and “Emergency Response” Base Control are linked to the Verification. Upon completion of the Verification, if the user specified to update those items from the Verification Template, the Verification result will be stored in those items.
For the other Types:
The Template will create 1 Verification for every entity selected (e.g. if 2 Major Accident Events are specified in the Template, 2 Verifications will be created).
The Register Scope option will be available for all Verification Types
This option allows the user to specify which Register the Verifications will be created, either:
- This register only
- This register and all registers below
- Or specifying the register from the register list
As mentioned in the beginning of this article, the contents of the Verification derive from the contents specified in the Verification Template, the Performance Standards to be specific.
The Performance Criteria in the Performance Standard will be used as the questions for the Verification. User also has the option to apply filter on the questions by using the Criteria checkbox.
For the example in the screenshot, as “In-Field” and “Out-Field” are selected, the contents of the Verifications will only include Performance Criteria that will match the selected options.
* This will not be applicable for the Bowties Review option, as the criteria will be based on the Critical Risk Controls of the related bowties.
Creating Verifications from Verification Template
Once all the necessary fields are populated in the Verification Template, you can create the Verification from the Status section.
Depending on the settings you have chosen, you can:
- Create an Adhoc Verification
- Create a Planned Verification
- Activate Schedule
Option 2 and 3 will appear when the recurring period is set.
The generation process should be instantaneous and should take no more than 30 seconds.