This article sets out the key similarities and differences between masters in the platform, office standards in NBS Building & Landscape and office masters in NBS Create.
| NBS Building & Landscape office standards | Masters |
Similarities
|
- You can have separate office standards for different purposes, each controlled by permissions.
- You can have whole preliminary and work section specifications as office standards.
- You can copy the whole office standard, or just selected sections into a new job.
- The decisions you take in the office standard (e.g. excluding clauses, inserting clauses, clause edits and so on) are copied into the job specification.
| - You can organise your masters into folders. A masters folder is like a project. It can contain as many preliminary and work section specifications as you like.
- You can insert a folder description to set out the scope of the master folder and the nature of the projects it should be used for.
- You can set the permissions on the master folder, and individual documents inside it - just like projects.
- You can write whole preliminary and work section specifications as masters.
- You can copy the whole, or selected sections, from the master into a project.
- The decisions you took in the master (parking rows, articles and clauses, inserting your own information) and your edits are copied into the job specification.
|
Differences
|
- You must to be connected to to the office standard files to use them. They may have been saved on a network drive. Each installation of Building and Landscape needs to be correctly configured to read the office standards location.
| - Just like projects, masters are in the cloud. This means masters information is available to your teams (depending in permission settings) no matter where they are based or which compatible device they are using.
|
| NBS Create office masters | Masters |
Similarities
|
- Office masters are in the cloud.
- You can control who in the organisation can add, edit, and delete the office masters and the rest of the users can reuse them.
| - Masters are in the cloud but there is no software to install to use them in the platform.
- You have a finer level of permissions control.
- You can set the permissions to master folders and the master preliminary and work section specifications they contain.
- You can set who will build and maintain them by making them administrators and contributors.
- You can set who can see and reuse the master by making them readers.
- For sensitive or private masters you can hide them from everyone except the users who need to see them.
|
Differences
|
- There is only one collection of office master clauses.
- Two or more types of the same clause are differentiated by a tag.
- You cannot park rows in your office masters, these are decisions reserved for editing the clause in the job.
- You add individual systems and clauses to job specifications one at a time rather than in bulk.
- Systems cannot be linked to other systems within your office master.
| - You can organise your masters into folders. Separate folders may be used for different regional operations, separate teams or disciplines, clients or sectors. The specification content in each folder is separate and can be managed as discrete sets of information.
- There are no tags in the platform. When you have two or more types of the same thing you differentiate them with the prefix and the suffix.
- You can park unwanted information in your master and this will remain parked when you copy it into a project.
- In addition to adding systems and sections, you can write whole preliminary or work section specifications for the purpose of being copied and reused 'wholesale'.
- You can also copy a selection of systems or sections and add them to projects in bulk.
|
