File overview

Contents

The file overview is a table that shows all the files that are captured in the model. Practical for if you want to find out what files have been uploaded in the model.

Just like the other overviews, the file overview can be accessed via the main menu, under header Overviews.

Good to know: in BriefBuilder, there are various places where you can upload files:

– Project documentation on the project home (e.g. a site plan)
– Supporting files for properties/object descriptions (e.g. a reference image)
– Uploads for objects (e.g. a product sheet for an object)
– Demonstration documents for verification results (e.g. a test report)
– IFC files for the IFC comparison (i.e. a design proposal)

In the files overview, all these files come together in one list.

Overview layout

The file overview features four columns:

File: the name of the file.
Object: the name of the object(s) to which a file is linked. This can be a requirement object (e.g. a space or system), but also a demonstration document or the project home.
Type: the name of the specific property or attribute for which the file has been uploaded.
ID: The relevant requirement ID (only in case a file been added as an upload or supporting file for a requirement property or object).

See below for some examples.

Example 1: files linked to requirements

In this first example (see screenshot below), you can see that there is a file called Diagram bicycle path, which has been linked to the Descriptions of two spatial segments called Bicycle lane, which have REQ-920 and REQ-903 as requirement IDs.

The fact that this diagram is linked to two segments means, in this case, that these two segments have to be designed according to one and the same diagram.

Example 2: files linked to the project home

In this second example (see again screenshot below), you see a file named Site plan, which is linked to the Project home (which is essentially the model’s introduction page).

Note that in this case the last column doesn’t feature a requirement ID because the upload option on the the project home is intended for background information and not for requirements information.

Example 3: files linked to demonstration documents

In this example, two files have been linked to two demonstration documents. Demonstration documents are being used in verification processes to demonstrate that the design team is compliant with a particular requirement (e.g. test reports or product declarations).

Note again that there are no requirement IDs in the last column because demonstration documents are not requirements. Also note that the third column says Uploads, which refers to the relevant table on the demonstration document’s detail view.