Revit views are essential for organizing, documenting, and coordinating BIM projects. As projects grow in scale, creating and configuring a large number of views consistently can become increasingly repetitive, especially when each company follows its own standards and workflows. While existing Revit features and automation tools can handle many common tasks, more complex requirements often call for a more tailored approach.

Creating Revit views may involve a series of repetitive steps, from selecting the appropriate level and view type to configuring the view for documentation or coordination. Users may need to create the view, rename it, apply the required template, set the scale, configure visibility settings, and apply filters. When the number of required views increases, these tasks can consume significant time and effort.
Manual configuration can also lead to inconsistencies between views, particularly when multiple users are working on the same project. Even when creating the same type of view, users may apply different templates, scales, filters, visibility settings, or naming conventions. Over time, these small differences can make it more difficult to maintain a consistent project standard.
Company-specific view standards are not always limited to a single setting. A particular view may need to follow different configurations depending on its level, discipline, zone, or other project conditions.
For example, an architectural floor plan on Level 03 may require Template A, a 1:100 scale, Filter Set A, and a specific naming pattern, while the same type of view in Zone B may require a different template and filter configuration. Applying these rules manually requires users to remember and correctly interpret multiple conditions for each view.
As the number of views grows into the hundreds, maintaining consistent standards becomes increasingly difficult. BIM managers may need to spend considerable time reviewing views, identifying inconsistencies, and correcting configurations. Furthermore, when company standards change, existing views may need to be updated individually, adding another layer of manual work to the project workflow.
Revit already provides several built-in features that can help users create and manage views more efficiently. View Templates can standardize view settings, while Duplicate Views, Filters, Browser Organization, and Project Templates can reduce repetitive configuration and help maintain consistency across a project.
For more advanced workflows, Dynamo and Revit automation can extend these capabilities by automating tasks such as creating views, modifying view properties, applying templates and filters, and processing multiple views at once. In addition, various third-party Revit add-ins provide tools for batch view creation and view management.
These capabilities can significantly reduce manual work for common scenarios. However, the challenge becomes more complex when automation needs to follow a company's specific combination of rules, conditions, and view configuration standards.

Existing Revit automation can effectively handle straightforward tasks, such as creating floor plan views for selected levels and applying a predefined view template. This type of automation is useful when the same process and configuration can be applied consistently across a project.
In practice, however, companies may have their own standards for how Revit views should be created and configured. The required setup may depend on multiple factors, including view type, level, discipline, zone, project phase, and company-specific standards.
These conditions can determine not only whether a view should be created, but also how it should be configured. For example, the automation may need to determine the appropriate view name, template, scale, filters, visibility settings, and other view properties based on the combination of project conditions.
This means the challenge is no longer simply about automating the creation of a Revit view. The real challenge is making sure the automation understands which view to create and how that view should be configured according to the company's rules.
Harmony AT is a BIM service and development provider specializing in BIM modeling, BIM consulting, software development, and workflow automation for the AEC industry. With experience in developing customized BIM solutions, Harmony AT helps companies improve their design and documentation processes through technology tailored to their existing workflows and standards.
As part of its BIM automation services, Harmony AT provides Revit View Automation to streamline the creation and configuration of Revit views based on company-specific requirements. The solution can be customized to automate different aspects of the view workflow, including:
In a large Revit project, users may need to create the same types of views repeatedly across multiple levels, buildings, or project areas. Harmony AT can develop custom automation that reads relevant information from the Revit model and uses predefined company rules to determine which views need to be created.
For example, if a project contains multiple building levels, the automation can identify the required levels and generate the corresponding floor plan views. The same approach can be applied to ceiling plans, sections, elevations, or 3D views when these are part of the company's workflow.
Instead of manually repeating the creation process for each level, the workflow can follow a predefined logic:
Project Data → Company Rules → Required Views → Revit Views
This allows the automation to create only the views required by the project and apply the company's defined logic consistently.
Creating a view is only the beginning. The new view may also need a specific template depending on its purpose and project context.
For example, an architectural floor plan may require an Architectural Floor Plan Template, while a structural plan or MEP coordination view may require a completely different configuration. In a larger project, selecting the correct template for every view manually can become another repetitive task.
Harmony AT can incorporate these requirements into the automation logic. Based on predefined conditions, the automation can determine which template should be applied to each view as it is created.
This means the workflow can move directly from view creation to view configuration, without requiring users to manually select and apply the appropriate template for every new view.
Company standards often require different settings for different types of views. A view's configuration may depend on its level, discipline, zone, view type, or project phase.
For example, an architectural floor plan on a standard building level may require Scale 1:100, Template A, and Filter Set A, while a view belonging to a specific zone may require a different template and filter configuration.
Harmony AT can translate these conditions into automation rules so that the appropriate settings are applied to each view. Depending on the project requirements, this can include scale, detail level, discipline, view range, visibility settings, filters, and view templates.
The key is that the automation does not simply apply one configuration to every view. It can use the defined conditions to determine which configuration belongs to which view.
View naming is another area where repetitive manual work can create inconsistencies. A company may have a naming structure based on information such as discipline, level, view type, building, or zone.
For example:
A – L03 – Floor Plan – Zone A
A – L04 – Floor Plan – Zone A
A – L05 – Floor Plan – Zone B
Rather than requiring users to enter each name manually, Harmony AT can incorporate the company's naming logic into the automation. The required information can be taken from the project and combined according to predefined naming rules.
This helps ensure that newly created views follow the same naming structure while reducing errors caused by manual entry.
The same Revit model may need multiple views of the same area for different purposes. For example, Level 03 could require an Architectural Documentation View, a Coordination View, and an MEP View. Although they represent the same part of the model, each view may require different templates, filters, visibility settings, and disciplines.
Harmony AT can develop automation logic that distinguishes between these requirements and applies the corresponding configuration to each view.
Instead of manually creating and configuring every version, the workflow can generate the required views from the same project data while maintaining the settings defined for each purpose.
The benefits become more significant as the number of views increases. Consider a project with 20 levels, 3 disciplines, 2 zones, and multiple view types. Manually creating and configuring every required combination can involve a large number of repetitive operations.
A custom automation workflow can process these combinations according to predefined rules and generate the required views in a structured way.
The workflow changes from:
Create → Configure → Rename → Check → Repeat
to:
Define Rules → Run Automation → Generate Standardized Views
This approach allows the BIM team to spend less time performing repetitive view setup and more time on the project work that requires human judgment.
Looking to automate Revit view creation around your company’s standards? Talk to Harmony AT about a custom Revit View Automation solution.
Danh mục