AC1 Lecture 8 Oct 21, 2026
From Individual Modelling to Collaborative BIM Practice
This session of Advanced Computing 1 explored how architectural and construction projects are organised and delivered through collaborative digital workflows. Building on the measured survey assignment, the lecture introduced students to professional approaches to information management, file naming, project documentation, and team coordination.
The central message was that BIM is not simply about creating a three-dimensional model; it is about managing information consistently across people, disciplines, and project stages.
Through examples from previous professional projects, including the Colchester Northern Gateway and British Museum Western Ranges, students were introduced to the standards and workflows used to coordinate complex architectural projects.
1. Understanding the Common Data Environment (CDE)
A Common Data Environment (CDE) is a shared digital environment in which project information can be stored, organised, accessed, and exchanged by members of a project team.
Although a CDE may initially seem similar to cloud storage services such as Google Drive or Dropbox, its role in BIM extends beyond simply sharing files. It provides a structured approach to managing information so that team members can identify the correct documents, understand their purpose, and work from coordinated project data.
For Assignment 2, the CDE will support collaboration between group members working on the measured survey and its associated BIM documentation.
Students should become familiar with:
Accessing the project through Autodesk's collaborative environment.
Organising files according to the agreed project structure.
Managing Revit models and linked information.
Using consistent file names and identifiers.
Sharing information in a way that supports coordination and review.
Students must complete the Model Information Asset Tracker using the supplied link or QR code, providing the appropriate university and Autodesk account details. This information will be used to arrange access to the project environment.
2. Applying ISO 19650 Naming Conventions
One of the main topics was the use of naming conventions based on ISO 19650, the international standard for managing information over the life cycle of built assets using BIM.
Consistent file naming allows project teams to identify information quickly and reduces ambiguity when multiple consultants and disciplines are working on the same project.
A structured file name may include fields identifying:
The project.
The originator or organisation responsible for the information.
The volume or system.
The level or location.
The type of information.
The discipline.
A unique document or model identifier.
The exact fields and their order depend on the project's agreed information standard. Students should therefore use the naming convention cheat sheet provided for the course rather than inventing their own format.
These conventions serve a similar purpose to referencing and formatting standards in academic work: they establish a predictable system that allows information to be understood and checked consistently.
3. Learning from Professional BIM Projects
The lecture used examples from large-scale professional projects to demonstrate how naming conventions and information management operate in practice.
Colchester Northern Gateway
The Colchester Northern Gateway project illustrated how multiple building models can be linked into a coordinated Revit environment. The example demonstrated the importance of organising models, separating information into appropriate volumes or packages, and maintaining consistent positioning across the project.
The discussion also highlighted the role of shared coordinates in ensuring that individual models align correctly within the wider site.
British Museum Western Ranges
The British Museum Western Ranges project provided another example of a complex architectural environment involving multiple linked Revit models, CAD files, drawings, and existing-building survey information.
The project demonstrated how different information sources can be brought together to support the development and coordination of a building model. It also highlighted the importance of organising files by purpose and responsibility, particularly when multiple consultants contribute to the same project.
These examples are significantly larger than the projects students are undertaking. Nevertheless, the underlying principles remain relevant: clear file structures, consistent naming, reliable coordinates, and carefully managed links are essential at every scale.
4. Coordinating Models, Drawings and Survey Information
Professional BIM projects frequently combine information from different sources. These may include Revit models, AutoCAD drawings, survey data, point-cloud or LiDAR information, and existing-building records.
The lecture demonstrated how these different resources contribute to a coordinated model and why their relationships must be managed carefully.
Students should understand that linking files is not simply a technical exercise. Each linked resource must be identifiable, correctly positioned, and appropriately maintained.
Common coordination considerations include:
Checking that linked models and drawings use the intended coordinates.
Confirming that files are correctly named and stored.
Avoiding broken, duplicated, or incorrectly referenced links.
Keeping the project folder structure understandable to other team members.
Ensuring that the information presented in drawings corresponds with the underlying model.
The quality of a coordinated model depends not only on the accuracy of its geometry but also on the reliability of the information and relationships that support it.
5. Organising the Common Data Environment
The CDE must be structured so that students, tutors, and other team members can locate and review project information efficiently.
A clear folder structure helps distinguish between different types of information and makes it easier to understand the status and purpose of individual files. Consistent naming conventions reinforce this structure by ensuring that files can be identified without opening each one.
Students should apply the course's agreed approach to organising their survey information, Revit models, supporting documents, and drawings.
The lecture also highlighted the importance of checking file links and folder organisation. Incorrectly named or poorly referenced files can create confusion and make collaboration more difficult, even when the underlying model is technically sound.
6. Preparing Professional Project Documentation
BIM work involves more than the model itself. Architectural teams also produce documents that explain the project, define responsibilities, record decisions, identify risks, and establish how information will be managed.
The lecture introduced examples of professional documentation, including BIM Execution Plans and project information documents.
Students should begin to recognise the purpose of several important project-management tools:
BIM Execution Plan (BEP)
Defines how BIM will be implemented on a project, including agreed processes, responsibilities, information exchanges, and coordination requirements.
Responsibility Matrix
Identifies who is responsible for particular tasks, deliverables, or information packages. This is especially useful when work is divided between several team members.
Risk Register
Records potential problems that could affect the project, along with their likelihood, consequences, and proposed responses.
Project Execution Plan
Sets out how the project will be organised and delivered, including the workflow, responsibilities, programme, and coordination approach.
For the major group project, students should develop a practical workflow in Miro and prepare a project execution plan supported by a responsibility matrix and risk register.
These documents should reflect the group's actual working process rather than simply reproducing professional templates without considering how they apply to the assignment.
7. Using Appropriate Tools for Final Documentation
The session emphasised the importance of selecting software appropriate to the type of document being produced.
Microsoft Word and Google Docs are useful for text-based documents, but complex architectural submissions often require more control over page layout, drawing placement, image quality, and graphic consistency.
Tools such as Adobe InDesign and Affinity Publisher can support the assembly of drawings, photographs, diagrams, schedules, and written material into a coherent presentation package.
Students should aim for a consistent visual language across their submissions, with clear hierarchy, readable text, appropriately scaled drawings, and good-quality images.
File size should also be considered when preparing submissions. Students should keep files manageable and follow the specified submission limits without unnecessarily compressing drawings or images to the point that their quality is compromised.
8. Collaboration and Professional Responsibilities
The lecture reinforced that successful group work depends on clear communication, agreed responsibilities, and active participation.
Students should establish a shared understanding of who is doing what, how information will be exchanged, and how the group will check its work before submission.
For the measured survey component, students were reminded to submit their field notes as a single, compiled PDF document. The notes form an important record of the information collected on site and provide the basis for subsequent modelling and documentation.
Students should also ensure that their contributions are accurately represented in shared submissions and communicate with their group members when responsibilities or submission arrangements need clarification.
Access to the CDE and participation in the collaborative workflow are important parts of the assignment. Students should address outstanding access or submission issues promptly and follow the instructions provided through the course.
9. Preparing for the Next Stage
Before the next class, students should:
Complete the Model Information Asset Tracker using the supplied link or QR code.
Ensure that the correct university and Autodesk account details have been provided.
Submit the measured survey field notes as one compiled PDF.
Apply the supplied naming convention cheat sheet to project files and drawings.
Establish a group workflow in Miro.
Prepare a project execution plan, responsibility matrix, and risk register.
Organise the group's digital files in preparation for collaborative work.
Consider how the final documentation package will be assembled and presented.
These activities will help establish a more organised foundation for the major project and prepare students to work within a structured BIM environment.
Central Theme
Professional BIM practice depends on effective information management as much as it depends on modelling skills. By applying consistent naming conventions, using a Common Data Environment, coordinating linked models, and planning their work collaboratively, students begin to develop the standards and habits required for architectural practice.
