What is verification?
In BriefBuilder, there is a dedicated feature for requirements verification. Verification is the process of checking whether a design solution or service meets the formulated requirements.
The actual verification (e.g. by means of tests, calculations, simulations, inspections) does not take place in BriefBuilder, but you can use BriefBuilder to define for each requirements how it should/will be verified (the verification plan) and to capture the outcomes of the verification.
By taking a systematic approach to verification, you can avoid that requirements are overlooked or ignored during the design process and ensure that the outcome of the project will be compliant with what the client asked for.
Typically, it is the design and engineering team that is responsible for verification. In some projects, they even have a formal obligation to demonstrate that all requirements have been met.
The verification process can be organized in different ways. It can be a simple compliance check list, but it can also be a more comprehensive set-up, in which requirements are linked to verification methods, verification phases and demonstration documents. Both are possible.
Verification plan and verification outcome
In BriefBuilder, we make a distinction between the verification plan and the verification outcome.
|Verification plan||A description of when and how the verification will take places, and who will be responsible for it.|
|Verification outcome||The result of the verification, with a concrete outcome (e.g. pass/fail) and optionally also an approval of the outcome and a link to a demonstration document.|
The verification plan can be made by either the construction client or the contract party (contractor/design/engineering team). In the latter case, the verification plan typically has to be approved by the client before it is executed.
Detail view and verification table
In BriefBuilder, there are two places where you can work with verification:
(1) on the detail view of objects
(2) in the verification table (also referred to as ‘compliance matrix’)
Both will be discussed briefly below.
Verification on the detail view
BriefBuilder’s verification feature can be found on the detail view of each object, by clicking on the icon in the upper right corner of the BriefBuilder screen, and the select verification.
Once, you have selected ‘verification’ as a view option, you will see that a couple of verification buttons/columns have added to you screen, which you can edit via the verification settings menu.
The number of columns is dependent on the number of verification phases that have defined (which you can do via the verification settings). For each phase, there are two icons/buttons available:
Verification plan: here you can define/see whether the requirement has to be verified in that phase.
Verification outcome: here you can add the verification outcome and related info like a note or a link to a demonstration document.
Verification table (aka ‘compliance matrix’)
The same verification information can also be found in the verification table, which can be found under the button Verification in the navigation menu.
The verification table is a great tool if you want select all requirements of the same kind at once. For example, all the requirements concerning room sizes, or all requirements concerning acoustics.
See for short explanation below. A more extensive explanation can be found here.
- Use the Selection part to select a part of the model you want analyze (e.g. the spaces tree);
- Use filters within the analysis table to narrow your search down on specific requirements (e.g. usable floor area);
- Enter the verification data in the Verification columns of the table (e.g. a verification method or outcome).