Once the project opens, you will see a vertical bar with menu items. See below for an explanation of each of the menu items.
The project home is the first page you see when accessing a project. On this page you will find basic information about the project:
- Status (are you looking at an active project or one that is archived?)
- Version (is it the working version, in which you can edit, or a ‘frozen’ published version?)
- Project information (e.g. client name or type of tender, click here to see how you can edit this)
- Comments (the comments in the model that are addressed to you personally)
In addition, there is an ‘action button’ on the project home page that is quite crucial:
- the history button that shows the latest changes in the requirements (only visible in the working version) of your project model
Under this header, you will find access to all the ‘trees’ that can be used to formulate requirements concerning the project.
Here you can find the general requirements that apply to the project as a whole.
|Objectives & principles||What needs to be achieved? And what are the general ideas and design principles that underpin the project?|
|What are the general standards (e.g. building codes) that apply to the project?|
Here is a set of requirements that relates directly to the design and function of the project that has to be build (and/or maintained).
|Who will be the users/occupants of the building?|
|What are the (user) activities that need to be facilitated?|
|Spaces||What kind of spaces and areas have to be realized?|
|Systems & elements||What are the relevant technical systems and elements?|
|What kind of user equipment needs to be placed in the building?|
These are requirements concerning the services (e.g. maintenance) that have to be delivered once the project is completed (if relevant).
|What services are part of the contract scope?|
|How to deal with possible performance failures?|
|How can the quality of the delivered services be measured?|
These requirements concern the delivery process. The requirements do not concern what has to be delivered, but how it needs to be delivered.
|Processes & activities||What processes and/or activities need to be performed by the parties that are responsible for delivering the project?|
|Products||What are the products (e.g. documents, samples) that need to be delivered to the client during the realization of the project?|
Under this header, you can find access to a table in which you analyze the set of requirements, or see the results of the analysis (depending on your role).
Under this header, you can find the verification table (also often referred to as verification matrix or compliance matrix) that shows all the requirements and the verification data that are related to it.
Furthermore, there is a button called ‘demonstration documents’ that gives access to a tree/list of the documents that a contractor wants to use as proof/supporting material in the verification process.
Under this header, you find the links to a number of tabular overviews. These overviews can be very handy for getting an overview of the overall set of requirements. For editors, the overviews offer the possibility to work in a more ‘excel-like’ way.
The following overviews are available:
|Cross tables – requirements||This table can showcase a tree’s (1) properties, (2) relations or (3) both at the same time (e.g., spatial object’s sizes and quantities, as well as their relations to technical elements).|
|Area overview||Overview and calculation of the project’s size in terms of square meters and room quantities|
|Comments||Overview all the comments (and responses) that have been made|
In BriefBuilder we currently offer two kinds of diagrams, which are mostly relevant for building projects.
|Area diagram||Bubble diagram that depicts the project’s spatial decomposition in a visual way, with each object represented as a circle.|
|Adjacency diagram||Similar to above, but all spatial objects and their interrelations are shown individually.|
There four kinds of settings. These settings are only visible if your project role allows you to edit these settings.
Click on “standard properties” to be able to define the standard properties for requirement objects (spaces, systems etc.)
Click on “standard properties” to be able to define the columns/properties that you want to use for your requirement analysis.
Click on “standard properties” to be able to define the columns/properties that you want to use for your requirements verification and to define the phases in which the verifications have to take place.
Under Admin settings you can define the general set-up of your project model by selecting different kinds of modules.