A verification plan (sometimes also referred to as a test plan, control plan or commissioning plan) is a plan that explains how you will organize the verification process to demonstrate compliance with the defined requirements.
A good verification plan answers the following questions:
- When will requirements be verified?
- How will they be verified?
- By whom will they be verified?
To develop a verification plan in BriefBuilder, you first have to define the overall set-up (the phases, methods, roles & outcome categories). Basically, you are defining the columns for your verification table (sometimes also referred to as compliance matrix).
After that, you can fill in the plan for all requirements.
Both steps will be explained in this article.
Setting up the verification plan begins with defining the relevant options for the earlier mentioned when, how and by whom questions. Furthermore, you may already want to define the possible outcome categories for verifications (compliant, non-compliant etc.).
When? (verification phases)
To define when a verification should take place, you can create verification phases in BriefBuilder.
To define verification phases, you have head to Settings and then click on Verification Phases.
Once you have defined the relevant phases, these will show up in the verification table in the column Phases.
How? (verification methods)
Next to when a verification will take place, you will also want to define how a verification should be performed. What should be done to demonstrate compliance?
Examples of verification methods are document review, calculation, inspection, simulation, performance test and functional test.
To define verification methods, you have to head over to:
Settings > Verification > Standard Properties
And then select Verification Plan.
You will get to see a default property called Method. Click on the Picklist Value field to be able to add or edit new methods.
Once you have defined the relevant methods, these will show up in the verification table as a drop-down menu in the column Method.
If the Method property doesn’t exist yet, you can create it by clicking on Add standard property and then set the input type to Picklist.
Who? (users, organisations, roles)
For reasons of accountability, it is important that there is a particular person or actor that is responsible for a verification. In BriefBuilder, this responsibility can be assigned on different levels. You can link verifications to:
- Users (specific people)
- Organisations (e.g. Architecture firm A or Contractor B).
- Roles (e.g. architect, engineer, indoor climate consultant)
Assigning verifications to users and organizations is easy in the sense that it does not require any adjustment of the verification settings. Both are readily available in your model when people have user accounts. The only thing you have to do is to make sure that these accounts are linked to the right verification roles and permissions.
But it is also possible that users and organisations are not yet known. In that case, you can choose to assign verifications to functional roles (e.g. architect, supplier, contractor etc.). These roles can be added via the roles menu:
Settings > Project model > Roles
Again, you have to ensure that these roles have the right permissions. Read more about that here.
The different outcome possibilities for verification results can also be part of setting up your verification plan. By default, BriefBuilder provides the following outcome options for verifications:
- Partially compliant
You can easily edit these categories via the Settings menu. You may, for example, want to add an outcome option called Not yet verifiable. Or perhaps you want to add an extra field called Approval if your verification procedure follows a ‘four eyes’ set-up.
To define and edit verification result properties, you have to go back to Settings again and click on Standard Properties below Verifications.
Then select Verification Result (not plan!).
If you want to change the outcome categories, click on the Picklist values field for the property Outcome.
If you want to add a new property, click on Add standard property. Set the input type to Picklist if you want to have a drop-down menu.
Making the actual plan
Once you have defined the overall set-up, you can start creating the actual verification plan.
To make the verification plan, go to the Verification table under Verifications in the main menu.
In this table, you will find all the defined requirements. For each individual requirement you can define how, when, and by whom they should be verified.
Typically, you do this in batches: you select groups of requirements that have to be verified in the same way. For example: you select all requirements concerning floor sizes and then define that all these should be verified during the concept design phase, by means of a calculation, with Architect Firm X as responsible.
You can make these selections by means of the table’s selections and filters.
The selections are shown before you get to see the actual table.
Selections for verifications
- Phase: relevant when wanting to define verifications for a particular phase
- Verification plan: relevant for finding requirements that don’t have a verification plan
- Responsible: relevant for finding verifications that haven’t been assigned to a responsible yet
- Outcome: only relevant when the verification process has taken off
Selections for requirements
- Tree: the tree or tree part that your set of requirements is part of (e.g. Spaces & Locations)
- Object type: relevant when interested in a particular object type (e.g. only spaces)
- Labels: relevant when looking for requirements that related to objects with a particular label (e.g. “office space” or “meeting space”)
- Requirement subject: relevant when looking for a particular type of requirement
For the verification plan, you will typically start with selecting a phase and then finding a particular set of requirements by selecting a tree (or tree part) and a requirement subject.
Once you have made you selections, click on Show, and you will get to see the set of requirements for which you want to define your verification plan details.
In the table itself, you can narrow your selection further down by using the column filters (the little filter icon ( above each column).
Especially the filter in the column Requirement type will be relevant as it allows you to make a very specific selection of requirements.
Adding verification plan details
Once you have selected the set of requirements that you had in mind, you can start filling in the verification plan details for these requirements.
You can define who is Responsible.
You can add a verification Method.
And there may be other verification properties to be filled in, if you have defined those earlier in the settings menu.
Duplicating verification plans
While working with your verifications, you might want to re-use the verification plan of one phase for a new, different phase. This can easily be done by cloning a verification phase in the verification settings.
To do that, you first have to navigate to the verification phases in the settings menu (Menu > Settings > Verification > Verification phases).
There, you will see the verification phases that you have defined.
By clicking on the clone button (), you will get a copy of that phase plus the related verification data.
When making the clone, you get the option to include or exclude the verification results. The default settings is that verification results are not included, but there are use cases in which this can be relevant (see next topic, ‘Planning re-verifications’).
It is also possible that you want to (or have to) re-do a number of verifications for a particular phase – typically those verifications that have a non-compliant result and/or those where the results were not approved by the client (if that is part of your set-up).
In that case, we recommend that you make a clone of verification phase in question (and put something like ‘re-verification’ in the newly created phase’s name), and then remove the ‘non-compliant’ results from that phase so that these can be verified again (without losing the earlier results).
In addition, you may choose to remove all the verifications that were already compliant, so that the phase only contains those verifications that need to be re-done.
For this, do the following:
- Go to Settings > Verification > Verification phases.
- Make a clone of the verification phase in question and include the verification results (!). Put something like ‘re-verification’ in the name.
- Go to Verifications > Verification table.
- Select the re-verification phase that you have just created, and select non-compliant for result.
- When clicking on Show, you will see all the verifications of which the outcome was ‘non-compliant’.
- To delete these results (!), click on the bulk action button ().
- In the bulk action, select clear values for all verification result (!) properties.
When you have done this, you have a copy of your original verification plan, but you emptied the ‘non-compliant’ results so that these verifications can be re-done.
Additionally, you may want to remove all the verifications that were already compliant. In that case, you need to do so some additional actions:
- Stay in the verification table, but go back to the selection screen (click on Selection, at the top of the table).
- Select the same (re-verification) phase, but this time select those verifications were the result was ‘compliant‘. This will give you all the verifications that will need no further attention.
- Click on show and go the bulk action button.
- In the bulk action menu, select Clear values for the property Verify?
When having done all that, all compliant verifications have been removed. And that means that your re-verification phase only contains those verifications that really need to be redone.
Doing the actual verifications
Once your verification plan is set up, it is time to do the actual verification and fill in the results. How to do so is explained in a separate article.