AC1 Lecture 11 Nov 11, 2026
Developing Working Drawings in a Collaborative BIM Environment
This Advanced Computing 1 session focused on the practical development of architectural working drawings within a collaborative BIM environment, using Autodesk Revit and Autodesk Forma (ACC). The session introduced students to the importance of establishing a structured project environment, managing shared project files, and coordinating multiple building models within a common site context.
The practical demonstration explored how to establish a coordinated Revit workflow, from setting up project folders and linking external models to acquiring shared coordinates, managing project phases, and preparing individual building models for integration into a wider collaborative project.
1. Project Organisation and the Common Data Environment (CDE)
The session began with a discussion about student engagement with the collaborative project environment. Despite previous instructions, several groups had not yet populated their assigned project folders or established the necessary file structures within Autodesk Forma/ACC.
Students were reminded that effective BIM collaboration begins with good information management. A well-organised Common Data Environment (CDE) is essential for ensuring that project information is accessible, identifiable, and properly managed throughout the design process.
Examples of folder structures from previous academic years and professional projects were presented to demonstrate how project information should be organised. Students were encouraged to establish a logical folder hierarchy that accommodates different project stages, disciplines, models, drawings, and supporting documentation.
Particular attention was given to:
Establishing a clear and consistent folder structure.
Using the project folders provided within the CDE.
Applying appropriate file naming conventions.
Avoiding ambiguous file names such as Final, Final Version 2, or Final Updated.
Maintaining appropriate backups of project information.
Understanding the relationship between cloud-based collaboration and local project files.
Students were reminded that these practices are not simply administrative requirements but reflect the information-management standards expected within professional architectural and construction practices.
2. Establishing the Revit Project and Linking External Models
The session then moved into a practical demonstration of setting up a Revit project for collaborative working drawings.
An important part of this process involves establishing a base Revit file that can act as the reference environment for the individual building models being developed by each group.
Rather than recreating existing site information, students were shown how to link an appropriately coordinated site model into their project.
The distinction between linking and inserting external content was discussed. Linking is generally the preferred approach when working collaboratively because it maintains a relationship with the original source file. This allows the linked model to be updated independently without unnecessarily duplicating its contents within the host project.
The demonstration covered:
Creating and saving a new Revit project.
Applying the correct project naming conventions.
Linking an existing coordinated site model.
Using manual positioning to establish an initial relationship between models.
Understanding how linked files are managed through the Revit Project Browser.
Maintaining an organised project environment for subsequent collaboration.
Students were also encouraged to consider the implications of file paths and cloud-based file management when working with linked models.
3. Coordinating Building Models Within the Site Context
A significant portion of the session focused on the spatial coordination of individual building models within a shared site environment.
Where multiple groups are developing different buildings or components of a larger project, it is essential that each model maintains the correct position and orientation relative to the overall site.
The demonstration explored how to use the coordinated site model as a reference for positioning individual building models.
Model lines were introduced as a useful method of establishing reference positions and aligning geometry in three-dimensional space. Students were shown how to use these references alongside Revit's Move and Align tools to position building elements accurately.
The example included positioning a guardhouse model in relation to the coordinated site geometry.
An important point was that model coordination should not rely exclusively on plan views. Although plan views are useful for establishing horizontal positioning, three-dimensional coordination is necessary to account for elevation, orientation, and other spatial relationships.
Students were therefore encouraged to consider the full three-dimensional relationship between their building models and the site.
4. Geolocation and Acquiring Shared Coordinates
The next part of the demonstration explored Revit's geolocation and shared-coordinate workflows.
For a collaborative BIM project, establishing a consistent coordinate system is essential. Without this, individual building models may appear correctly positioned within their own files but become misaligned when linked into the overall site model.
The demonstration explained how to acquire shared coordinates from an existing geolocated base file.
The general workflow involved:
Linking the existing geolocated Revit file into the new project.
Establishing the appropriate relationship between the linked model and the host project.
Using the Acquire Coordinates tool to obtain the coordinate information from the linked file.
Verifying that the project has adopted the correct coordinate system.
Pinning the linked geometry once the coordinate relationship has been established.
An important distinction was made between physically moving geometry into position and acquiring coordinates. These are related but separate operations.
Students were reminded that the sequence of operations matters. Coordinates should be acquired before pinning the reference geometry, as pinning elements prematurely can interfere with subsequent positioning and coordination operations.
The discussion also addressed how to reset or re-establish coordinate relationships when elements have been moved incorrectly.
Ansel raised questions about whether the base file needed to be geolocated before it could be used as a reference. It was clarified that the demonstration file was already geolocated, allowing the other project files to acquire its coordinate information.
Groups 5, 6, and 7 were specifically encouraged to revisit the earlier class recordings from Weeks 6, 7, and 8, which covered the process of acquiring coordinates from scratch.
5. Managing Project Phases and Model Visibility
The session also introduced the importance of managing Revit phases when integrating multiple building models into a shared project environment.
Phasing allows different stages of a building's lifecycle or construction process to be represented and managed within the model.
The demonstration covered the relationship between the phase settings of linked models and their host projects, highlighting how inconsistent phase settings can result in elements appearing incorrectly or becoming invisible.
Students were shown how to manage phase settings to ensure that the linked building geometry displays appropriately within the overall site model.
The Revit Project Browser was also discussed, including the use of browser organisation settings to group views according to their associated project phases.
This is particularly useful when developing working drawings for projects involving existing buildings, proposed construction, and multiple stages of development.
Students were encouraged to consider how appropriate phase management contributes to a more structured and understandable model.
6. File Management, Backups and Cloud Collaboration
Towards the end of the session, the discussion returned to the importance of maintaining reliable project information.
Students were shown how to save and manage their Revit project files, including the importance of maintaining backup copies.
Although Autodesk Forma/ACC provides a cloud-based environment for collaboration and file management, students were encouraged not to rely exclusively on a single storage location.
Maintaining appropriate local and cloud-based backups provides an additional layer of protection against accidental changes, file corruption, or other technical problems.
The benefits of cloud-based collaboration were also highlighted, particularly the ability to maintain a record of project information, file access, and changes made by different team members.
These features support greater accountability and transparency when multiple people are contributing to the same project.
Key Learning Outcomes
By the end of this session, students should have a better understanding of how to establish and manage a collaborative Revit project environment.
In particular, students should be able to:
Establish a logical project folder structure within Autodesk Forma/ACC.
Apply consistent and professional file naming conventions.
Create a Revit base file for their group project.
Link external Revit models rather than unnecessarily inserting or duplicating their contents.
Position and coordinate building models within a shared site context.
Use model lines and other reference geometry to assist with three-dimensional alignment.
Acquire shared coordinates from an existing geolocated Revit model.
Understand the correct sequence for acquiring coordinates and pinning linked geometry.
Manage Revit phases and organise project views accordingly.
Maintain appropriate backup procedures when working with cloud-based project files.
Required Actions and Preparation for the Next Session
All groups should now begin implementing the workflows demonstrated during the session.
The following actions are required:
Project organisation: Populate your assigned Autodesk Forma/ACC project folders with the relevant project information and establish a clear folder structure.
File naming: Review your existing files and ensure that they follow the naming conventions discussed in previous lectures.
Revit base file: Each group should create and save at least one Revit base file within its assigned project folder by the end of this week's session.
Coordinate acquisition: Groups 5, 6, and 7 should revisit the recordings from Weeks 6, 7, and 8 to review the process of acquiring shared coordinates from scratch.
Practical application: Use the scheduled tutorial session to work on your individual group projects, resolve coordination issues, and implement the Revit workflows demonstrated.
Particular attention should be given to Group 3's work on the Bomber Primary School site, where the coordination of individual building models within the wider site context will be an important part of the next stage of development.
Moving Forward
The transition from individual modelling exercises to collaborative BIM-based working drawings requires a more disciplined approach to project organisation and information management.
Students should begin thinking beyond the production of individual Revit models and consider how their work contributes to a coordinated project environment. File structures, naming conventions, shared coordinates, linked models, and project phases are all fundamental components of this process.
The objective is not simply to produce a collection of architectural drawings, but to establish a coordinated and professionally managed digital project from which those drawings can be developed.
The next stage of Advanced Computing 1 will build on these principles as students continue developing their group projects and translating their coordinated BIM models into architectural working documentation.

