Collaboration in a Single Model
One thing that makes Revit stand out from the crowd in the AEC world is that Revit comes as three
discipline specific products: Revit Architecture, Revit Structure, and Revit MEP. These three products
succeed where others in the past have failed because all three disciplines can be fully integrated
with ease. In this article I will offer an alternative solution to the integration of all three disciplines
using Revit as the main design / documentation tool. Multidiscipline Collaboration on a Single
Central File is a different workflow to the traditional linked file and copy / monitor method. It
requires multiple disciplines within a design team to utilize one central file, split into worksets to
produce a Revit model and construction documents. This methodology is suited to multidiscipline
consultancies large and small. The image in Figure 1 is just one example of a project that we’ve used
this approach with successfully.
Insert Figure 1 – Jowett Figure 01.jpg (Caption: Structural framing and services for a new
build Tea Factory in New Zealand)
Why use a multidiscipline central file?
From a collaboration point of view, a multidiscipline central file will mean nothing is modelled twice,
and everything is fully coordinated. Currently we find the majority of Architects will model structural
slabs, structural walls, columns and beams. The Revit Structure user will come in and model the
structural slabs, structural walls, columns and beams all to the correct size as per the design. This
information doesn’t always make it back into the Architects model, resulting in the Architect
showing the incorrect structural steel sizes and referring back to the Structural Engineers drawings.
Isn’t this asking for trouble?
In addition, the Revit Structure user will copy / monitor any timber framing from the Architects
model that may need to be shown in certain sections and details. By this stage we have two of every
major component in the project. Next it is the Revit MEP users turn; they start by modelling a ceiling
(because Revit doesn’t allow copy / monitor of ceilings) and also copy / monitor most of the walls in
a project. Once all three disciplines are involved, we have two to three copies of every major
component in a project.
One single central file means we only do things once, and everyone owns and only models what
belongs to them. This means the model will be coordinated as it is constructed, as opposed to
coordination reviews taking place at set stages during the design and documentation stages. This
can only result in increased productivity, and improved documentation.
The workflow needs to change
For a multidiscipline single central file to work effectively, the timing of each disciplines input into
the Revit model needs to be thought about carefully. Ideally the basic footprint of the building, grids,
and floor levels need to be set before any Structural and Services input into the Revit model. The
Architects may have to put in more work up front, to the point that Architectural developed design
is almost complete when the structural developed design starts to make its way into the Revit
model. I appreciate there are always time constraints on projects, tight deadlines, 50% and 75%
design reviews, but if the Structural model can start to take shape as late as possible, you will have a
much more successful project, and larger profit margin, in comparison to starting the model early
and updating the model as the design changes.
Communication is the key to success
Communication within the design team always has and always will be critical to the coordination
process and the workflow of a project. Revit does have collaboration tools that can improve
communication between disciplines, but this should not replace a much more traditional approach
i.e. a phone call, or even an email to discuss design changes that could have an impact on the other
disciplines. In my experience with Revit, I am seeing less and less communication between the
“drafting teams.” If anything Revit requires much more communication than the old AutoCAD days,
to make sure this happens the Revit team (the lead Revit Architecture, Revit Structure and Revit MEP
modellers) should hold Revit meetings, similar to the design team meetings held by Engineers and
Architects, to discuss any Revit related issues in the project.
The Revit team should hold a Revit meeting before the project starts, this first meeting should be
used to identify when each discipline should start to model, outline who will set up the central file,
where the central file will reside, who will model what, and who will own what. The Revit team
should then hold Revit meetings on a regular basis throughout the duration of a project.
If all three disciplines are working under one roof, set up a project team. Sit the Revit Technicians
from each discipline in the same area, this will only improve communication and coordination, and
can only lead to increased productivity. On large scale projects, a Revit Manager should be
appointed to project manage the Revit model and the Revit team.
Produce accurate models
We rely on each other’s work, so all Revit Technicians should take the time to go that extra mile to
get things right. Don’t model something that “looks right” on a drawing at a scale of 1:100, and
produce the 1:10 detail using a drafting view and detail lines. Make sure it is accurate within the
Revit model.
If we construct an inaccurate model, what chance do we have of producing accurate construction
documents? Guidelines should be set up that detail the best practice methods for constructing a
Revit model. All Revit users should follow these guidelines, keeping the construction of Revit models
consistent throughout the company. This will ensure any Revit user can step in and work on any
project at any time, with minimal complications.
Setting up a multi-discipline central file
A multi-discipline central file should be set up and managed by a single user. This user could be a
nominated person from the Revit team on a small scale project, or the Revit Manager on a large
scale project. Close attention should be paid to the following stages of the file set up.

Central file location - If the project is going to span across offices or regions the central file
should be set up on a server that has a good connection speed for all remote users. If the project

is ‘in house’ (all disciplines under one roof) the central file should be set up on a local server that
can be accessed by all disciplines.
Worksets - Worksets within a multidiscipline central file should be set up for at least each
individual discipline I.e. Architecture, Structure, Mechanical, Electrical, and Plumbing. It may be
necessary to set up more than one workset for each discipline, or break the building up into
worksets. This should be discussed in a Revit team meeting, before the central file is set up.
Consider owning the worksets you are using, this will make sure no other discipline can interfere
with your elements – easier said than done, but worth a thought on smaller scale projects.
Phantom users could be created to lock down certain worksets i.e. Levels and Grids. The phantom
user could be the Revit manager, who would set up the levels and grids at the start of the project,
and take ownership of the workset.
Considerations





It will be necessary to set up a Revit project template that is suitable for use across multiple
disciplines, keep this simple, and don’t overload it with too many families. Line weights and line
styles will need a lot of thought, and view templates for each discipline are a must.
The project browser should be set up to list Type/Discipline; this will break down the views
specific to each Revit flavour. Careful management of the project browser is essential; control is
required for naming conventions, browser organisation, etc.
A naming convention for usernames can be a great help when working on a multidiscipline
central file, an example would be the name of the user + their extension number i.e. Glenn
Jowett – Ext. 8144. Remember communication is critical.
If each discipline uses the same title sheet, it is important to add discipline specific parameters
to the title sheet family, i.e. Structural Drawing Number, Architectural Drawing Number, etc.
Everyone must use the same release and build of Revit.
Insert Image 2 – Jowett Figure 02.jpg (Caption: Exterior view of a new build Tea Factory
in New Zealand)
The future
This article only scratches the surface of multidiscipline collaboration on a single central file, but I
think the key to successful multidiscipline collaboration is to set boundaries and guidelines from the
start of a project, pay special attention to the timing of each disciplines input into the model, and
open up the lines of communication between disciplines. If you can stick to these three basic
principles you will soon see the benefits of single central file collaboration.