What is verification?
In BriefBuilder, there is a dedicated feature for requirements verification. Verification is the process of checking whether a design solution, process 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 (the verification result).
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 in BriefBuilder.
Plans, results, documents
In BriefBuilder, we make a distinction between the verification plan and the verification result. Furthermore, we have the concept of demonstration documents, which are the ‘proof’ for the verification results. See below for a brief discussion of all three concepts.
A verification plan is a description of when and how you will verify compliance with a particular requirement. Such a plan usually consists of the following attributes:
- The phase in which verifications will take place (e.g. design phase, construction phase, …)
- The verification method that will be used (e.g. calculation, inspection, …)
- The person or party that is responsible for executing the verification (e.g. architect, electrical engineer, …).
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 usually has to be approved by the client before it is executed.
The verification result encompasses information about the actual verification. Typical attributes are:
- The outcome of the verification (e.g. compliant, non-compliant, requires attention).
- Notes concerning the outcome (e.g. “non-compliant because of ….”)
- A link to a demonstration document (e.g. calculation or test report)
- Possible approval of the outcome (e.g. from the project’s quality manager or the client)
- Possible follow-up actions (e.g. design modification, requirement modification, …)
The verification results are usually added by the design and/or delivery team that is working on the project. At the end of each verification round, there is usually a discussion with client about non-compliance issues, which may result in changes to either the requirements or the design solution.
Verification results can be linked to demonstration documents: documents or files that can be used in the verification process to demonstrate that (designed/built) solutions are compliant with the client’s requirements.
Examples of demonstration documents are test and inspection reports, floor plans, calculations, specification sheets, and compliance certificates.
Demonstration documents can be manually uploaded in the BriefBuilder model or they can be fetched from a document management system (DMS).
Working with verifications in BriefBuilder
There are several specialist articles about working with verification in BriefBuilder in this knowledge base. In general, however, it is important to know that there are two places in BriefBuilder 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 detail view
BriefBuilder’s verification feature can be found on the detail view of each object by clicking on third button of the view options in the upper right corner of the BriefBuilder screen. This view button is represented by a check mark.
Once you toggle this button on, 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 Selections to focus on a particular part of the model (e.g. the spaces) and click on Show;
- Use filters in the 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).
There’s also the possibility to get a quick visual overview of the verification process so far. You can do so by navigating to the verification dashboard.
Incidentally, clicking on any part of the diagrams on the dashboard will instantly take you to that particular set of requirements in the verification table. It’s an easy way to access certain verifications without needing to set up a filter or selection yourself.
Check out the other articles concerning verification in this section.