It is an example of a test activity (a ‘soak test’) that is part of a commissioning process. In this example, the description and properties are used to specify what the client expects from the design team in relation to user involvement.Ī more technical example can be seen below. See below for a simple example of what kind of requirements a client may have formulated concerning the activity Workshops with end users. Is there a particular approval process or approval period? Is there a particular protocol or method that needs be applied?Īre there requirements that apply to the people that will perform the activity (e.g. Is there a particular time frame for the activity?Īre there specific norms or regulations that have to be complied with? How often does an activity need to be executed? Typical examples of such properties are: Frequency This can be done by creating properties on the detail view of a process/activity (just click on Add property button), or by defining standard properties (via the requirements settings menu). Process requirementsįor each process and activity, you can define requirements concerning how or when they need to be executed. maintenance, operation, cleaning, security). Services are the activities/task that a party has to deliver once the built structure is in use (e.g. Processes are the activities/tasks that have to be done to realize and complete the project (e.g. Please note: processes are sometimes mixed up with we call services in BriefBuilder. You can use BriefBuilder’s label feature to indicate whether activities are optional. Example of how a ‘process tree’ can be used to define what kind of activities are expected in relation to interior design. This can be done by using the folders ( ). In the tree, processes and activities can be structured according phasing or discipline or a combination of both. requesting permits or doing a particular test). landscape design or interior design).Ĭan be subdivided into sub-processes or activities.Ī specific activity or task that has to be executed by the contractor/design team, typically with a distinct deliverable (e.g. It consists of two types of objects:Ī general process that has to be taken care of by the contractor/design team (e.g. In the process tree, you can define what processes and activities have to be done by the contract party. The process and deliverable decompositions can be found under requirements / process, in the navigation menuīoth will be discussed below. a deliverables tree (what has to be delivered?).In BriefBuilder, there are two ‘trees’ (decompositions) available for capturing such requirements: BIM models, certificates, warranties, test reports).īoth are important as they help to create a shared understanding of what needs to be done and delivered in each phase of the project. In addition, there are likely to be requirements concerning the deliverables that need to be produced during the project (e.g. particular design tasks or engineering activities). In large construction projects, requirements will not only concern the built object itself, but also the processes that need to be performed by the contractor/design team to realise it (e.g. Important: to be able to define process requirements, you must activate the process module in the modules menu.