Fatal Errors in Workset Management in Revit ⚠️ and Best Practices to Avoid File Bloat, Slow Synchronization, and Data Conflicts 🚀 Fatal Errors in Workset Management in Revit ⚠️ and Best Practices to Avoid File Bloat, Slow Synchronization, and Data Conflicts 🚀 Effective Workset Management to Improve Revit Project Performance Worksets in Revit are the cornerstone of effective collaboration in complex multidisciplinary projects. Their proper management is not just an option, but an absolute necessity to ensure smooth workflow, model stability, data accuracy, and fast synchronization in a shared work environment. This guide aims to analyze common mistakes made by engineers and designers when dealing with Worksets, how these errors negatively impact the project, and to provide best practices and approved solutions in accordance with international standards such as ISO 19650.Comprehensive Overview and Importance of Effective Workset Management in Revit ❌ Common Mistake: Many teams fall into two main errors: either over-creating Worksets unnecessarily or under-creating them and leaving most elements on the default "Workset1" or "Shared Levels and Grids" Workset. Common mistakes also include not logically assigning Worksets to elements (e.g., placing structural elements on an architectural Workset or vice versa), or not creating dedicated Worksets for Linked Models, Detail Groups, or Shared Components loaded from libraries such as those available in "Library For Revit 2022 En Rvtcpenu". This leads to utter chaos in the model. 💥 Negative Impact on the Project: Performance Degradation and Slow Synchronization: The model becomes very heavy, and opening, saving, and synchronizing with the Central Model take a very long time, significantly hindering team productivity. Difficulty Controlling Visibility: Isolating elements or hiding specific disciplines in different Views becomes an impossible task, leading to visual clutter and difficulty in producing sheets. Coordination and Clash Detection Issues: When exporting the model to Navisworks or Autodesk Construction Cloud (ACC) platforms for Clash Detection, the data is disorganized, making it difficult or impossible to filter clashes by discipline or element type, leading to inaccurate results. IFC Export Failure: Poor organization affects the quality of IFC file export, as "IfcExportAs" or "IfcExportType" cannot be effectively assigned, leading to loss of structural data essential for OpenBIM and subsequent analysis. Difficulty in Quantity Take-Off (QTO): Extracting accurate quantities becomes extremely difficult, as elements cannot be easily filtered by Workset ownership, impacting cost estimates and schedules. 🔍 Root Cause Analysis: This error stems from a lack of deep understanding of how Worksets function as a tool for element management, visibility control, and performance in a shared work environment. Some users believe they are merely a way to divide work, without realizing their fundamental role in organizing the model's database. The absence of a clear BIM Execution Plan (BEP) that defines Workset structure, naming conventions, and responsibilities is often the main reason, or a failure to adhere to such a plan if it exists. Inconsistent naming (e.g., "Workset1", "My Workset") exacerbates the problem. ✅ Best Practice and Approved Solution: Workset Planning in BEP: Workset structure and naming conventions must be clearly defined in the BIM Execution Plan (ISO 19650 Information Standardisation). Naming should be descriptive and standardized, such as: 00_Shared_Elements: For Levels and Grids, Scope Boxes, and elements shared across disciplines. ARCH_Walls: For architectural walls. ARCH_Floors_Ceilings: For architectural floors and ceilings. STR_Concrete_Elements: For structural concrete elements. STR_Steel_Elements: For structural steel elements. MEP_HVAC_Ducts: For HVAC ducts. MEP_Piping: For plumbing pipes. LINK_ARCH: For linked architectural files. LINK_STR: For linked structural files. LINK_MEP: For linked MEP files. 00_MEGABIM_Details: For detailed components or shared detail groups. Create Worksets at Project Start: All main Worksets should be created at the start of the central project, and not left to individual users' discretion. Accurate Element Assignment: When modeling any element, ensure it is assigned to the correct Workset. The Workset for any element can be changed in the Properties Palette under "Identity Data". Periodic Verification: The BIM Manager or Coordinator conducts periodic model Audits to verify the distribution of elements to the correct Worksets using Schedules or Filters. Worksets for Shared Libraries: When using standard components from libraries such as "Library For Revit 2022 En Rvtcpenu", ensure these components are added to the appropriate Workset when inserted into the project, or that a dedicated Workset is assigned to them if they are shared components of a special nature. 1. Failure to Create and Organize Worksets Structurally and Accurately ❌ Common Mistake: Many users believe they must "own" (Make Elements Editable) an entire Workset to work on some elements within it, or they forget to Relinquish All Mine after completing modifications. Some also modify elements they do not directly own, leading to frequent warning messages or synchronization blocking. 💥 Negative Impact on the Project: Synchronization and Collaboration Blocking: When a user owns a Workset or an element, no other user can modify that Workset or the elements owned by the first user. This leads to mutual waiting and workflow disruption, especially in large projects with multiple teams. Loss of Changes: A user may be forced to undo or discard their changes if there is an ownership conflict, leading to hours of lost work. Increased Local File Size: Unnecessarily retaining ownership of many elements increases the size of Local Files and slows down their performance. Inability to Perform Management Tasks: The BIM Manager may face difficulty performing maintenance or auditing tasks on the central model if many users own important Worksets or elements. 🔍 Root Cause Analysis: The root cause is a lack of clear understanding of the difference between "Borrow Elements" and "Make Elements Editable". "Borrow" allows temporary modification of an element or group of elements, with automatic relinquishment upon synchronization or file closure. "Make Elements Editable" grants full ownership of a Workset or a group of elements, and must be relinquished manually. New users tend to opt for the latter believing it offers greater control, without realizing its implications for the shared work environment. ✅ Best Practice and Approved Solution: Always Borrow Elements: The golden rule is to use the "Borrow Elements" option as much as possible. When you modify an element you don't own, Revit will automatically prompt you to "Borrow" that element. This is the correct behavior. Relinquish Ownership Regularly (Relinquish All Mine): All team members should synchronize regularly (Sync with Central) and use the "Relinquish All Mine" option upon completing a task, before taking a long break, or at the end of the day. This ensures elements are available to others. "Make Elements Editable" for Exceptional Cases Only: Use "Make Elements Editable" only when you need to make extensive modifications to a large number of elements within a specific Workset, or when managing the Workset settings themselves. This should be done with prior team coordination. Monitor Ownership (Worksharing Monitor): The BIM Manager can use tools like "Worksharing Monitor" (available as part of Revit) to monitor who owns which Workset or element, and intervene to resolve conflicts. Training and Awareness: All team members should be trained on the correct understanding of ownership management and the importance of relinquishing elements after completion. 2. Poor Management of Workset and Element Ownership (Borrow vs. Make Elements Editable)

Common Mistakes and Golden Practices: BIM Model Quality Checking and Clash Avoidance with Solibri 🛠️✅ Solibri is a critical tool in Building Information Modeling (BIM) for ensuring model quality and avoiding clashes. This article aims to review common mistakes engineers make when preparing models or using Solibri, and to provide best practices for writing custom Rule Sets that ensure design compliance with code requirements and engineering standards before execution begins. Model checking in Solibri is an essential step to ensure the quality of engineering projects. Here, we review common mistakes engineers may make and how to avoid them.Solibri Model Checking: Common Mistakes and Golden Practices ❌ Common Mistake: Architectural and structural engineers model elements at different, inconsistent levels of detail, which do not align with project phases or specified information requirements. For example, structural columns might be modeled as simple elements while rebar detailing is expected at a later stage without clear definition. This discrepancy leads to inconsistencies in the information available for checking. 💥 Negative Impact on the Project: Solibri checks fail because expected properties or geometries are missing. False Positives arise, or real clashes (False Negatives) are overlooked in clash detection. This issue leads to inaccurate Quantity Take-Offs (QTO), delays in information exchange, and non-compliance with Information Delivery Plan (IDP) requirements according to ISO 19650-3, significantly hindering project progress. 🔍 Root Cause Analysis: The main reason is the absence of a clear and shared Information Delivery Plan (IDP) (according to ISO 19650-3) from the project's inception. Misunderstanding of Level of Development (LOD) definitions, for example, confusing LOD 300 with LOD 350. Teams work in isolation without clear coordination in BIM Execution Plans (BEP). As a result, Solibri rules cannot find the required information or check inconsistent information. ✅ Best Practice and Approved Solution: To ensure effective model checking in Solibri, you must: Establish a robust Information Delivery Plan (IDP) and BIM Execution Plan (BEP): Specific LOD requirements for each discipline and project phase must be precisely defined. This ensures compliance with ISO 19650-3 and forms a solid foundation for consistent modeling. Write custom Solibri checking rules for LOD compliance: Classify Elements: Create Classification Rules in Solibri to classify elements based on their intended Level of Development (LOD) (e.g., "Structural Columns - LOD 300"). Verify Properties: Write custom Rule Sets using tools like "Component has Property" and "Property Value Check" to ensure that elements at a specific LOD contain the required parameters (e.g., "Fire Rating" for walls at LOD 300, or "Rebar Diameter" for structural elements at LOD 400). Use Information Takeoff (ITO): Utilize the "Information Takeoff" feature to extract information and verify its completeness against the Information Delivery Plan (IDP). Space and Clearance Rules: Implement Rules based on Spaces or Clearance rules, especially for Mechanical, Electrical, and Plumbing (MEP) disciplines, which rely on the accuracy of Geometric LOD. Continuous Auditing: Regularly audit models in Solibri to ensure compliance with specified Levels of Development. Common Mistake #1: Inconsistent Level of Development (LOD) between Architectural and Structural Models ❌ Common Mistake: Architectural and structural models are linked together but use different grid systems, or shared coordinates are not properly established and maintained, or local origins are used haphazardly. This leads to a loss of spatial alignment between models. 💥 Negative Impact on the Project: This results in misaligned elements in Solibri, widespread false clashes, and the inability to perform meaningful clash detection or spatial coordination checks. Errors appear in quantity take-offs, and significant time is wasted on manual adjustments. It can also lead to corrupted IFC exports due to coordinate transformation issues. 🔍 Root Cause Analysis: The root cause stems from inadequate BIM coordination planning and a lack of understanding of shared coordinates in modeling software (such as Project Base Point, Survey Point, and Internal Origin in Revit). Failure to follow a federated model approach with a common coordinate system leads to this problem. (For more on setting up projects in a BIM environment, refer to this article: ALLPLAN, and this article on model coordination: Revit Structure 2019). ✅ Best Practice and Approved Solution: To ensure proper model alignment: Define a project-wide shared coordinate system: A common Survey Point and Project Base Point must be defined early in the project. Use "Acquire Coordinates" or "Publish Coordinates" functions in software like Revit. Write custom Solibri checking rules for coordinate verification: Import Models: Import architectural and structural models into Solibri. Visual Inspection: Use the "Comparison" feature for visual alignment inspection. Relative Position Verification Rules: Create custom rules to verify the relative position of key elements (such as columns and core walls) from different disciplines. For example, a "Components are within Tolerance" rule can check if structural columns are within a small tolerance (e.g., 5mm) of their architectural counterparts. Identify Unlocated Components: Use "Rules for Unlocated Components" to identify elements that may have shifted or been misplaced. Link Models with Shared Coordinates: Ensure that all linked models in authoring software are placed using the "Place by Shared Coordinates" option. Common Mistake #2: Lack of Grid System Coordination and Shared Origin Points (Coordinate Corruption)

Common Mistakes and Golden Practices: BIM Model Quality Checking and Clash Avoidance with Solibri 🛠️✅ Solibri is a critical tool in Building Information Modeling (BIM) for ensuring model quality and avoiding clashes. This article aims to review common mistakes engineers make when preparing models or using Solibri, and to provide best practices for writing custom Rule Sets that ensure design compliance with code requirements and engineering standards before execution begins. Model checking in Solibri is an essential step to ensure the quality of engineering projects. Here, we review common mistakes engineers may make and how to avoid them.Solibri Model Checking: Common Mistakes and Golden Practices ❌ Common Mistake: Architectural and structural engineers model elements at different, inconsistent levels of detail, which do not align with project phases or specified information requirements. For example, structural columns might be modeled as simple elements while rebar detailing is expected at a later stage without clear definition. This discrepancy leads to inconsistencies in the information available for checking. 💥 Negative Impact on the Project: Solibri checks fail because expected properties or geometries are missing. False Positives arise, or real clashes (False Negatives) are overlooked in clash detection. This issue leads to inaccurate Quantity Take-Offs (QTO), delays in information exchange, and non-compliance with Information Delivery Plan (IDP) requirements according to ISO 19650-3, significantly hindering project progress. 🔍 Root Cause Analysis: The main reason is the absence of a clear and shared Information Delivery Plan (IDP) (according to ISO 19650-3) from the project's inception. Misunderstanding of Level of Development (LOD) definitions, for example, confusing LOD 300 with LOD 350. Teams work in isolation without clear coordination in BIM Execution Plans (BEP). As a result, Solibri rules cannot find the required information or check inconsistent information. ✅ Best Practice and Approved Solution: To ensure effective model checking in Solibri, you must: Establish a robust Information Delivery Plan (IDP) and BIM Execution Plan (BEP): Specific LOD requirements for each discipline and project phase must be precisely defined. This ensures compliance with ISO 19650-3 and forms a solid foundation for consistent modeling. Write custom Solibri checking rules for LOD compliance: Classify Elements: Create Classification Rules in Solibri to classify elements based on their intended Level of Development (LOD) (e.g., "Structural Columns - LOD 300"). Verify Properties: Write custom Rule Sets using tools like "Component has Property" and "Property Value Check" to ensure that elements at a specific LOD contain the required parameters (e.g., "Fire Rating" for walls at LOD 300, or "Rebar Diameter" for structural elements at LOD 400). Use Information Takeoff (ITO): Utilize the "Information Takeoff" feature to extract information and verify its completeness against the Information Delivery Plan (IDP). Space and Clearance Rules: Implement Rules based on Spaces or Clearance rules, especially for Mechanical, Electrical, and Plumbing (MEP) disciplines, which rely on the accuracy of Geometric LOD. Continuous Auditing: Regularly audit models in Solibri to ensure compliance with specified Levels of Development.Common Mistake #1: Inconsistent Level of Development (LOD) between Architectural and Structural Models ❌ Common Mistake: Architectural and structural models are linked together but use different grid systems, or shared coordinates are not properly established and maintained, or local origins are used haphazardly. This leads to a loss of spatial alignment between models. 💥 Negative Impact on the Project: This results in misaligned elements in Solibri, widespread false clashes, and the inability to perform meaningful clash detection or spatial coordination checks. Errors appear in quantity take-offs, and significant time is wasted on manual adjustments. It can also lead to corrupted IFC exports due to coordinate transformation issues. 🔍 Root Cause Analysis: The root cause stems from inadequate BIM coordination planning and a lack of understanding of shared coordinates in modeling software (such as Project Base Point, Survey Point, and Internal Origin in Revit). Failure to follow a federated model approach with a common coordinate system leads to this problem. (For more on setting up projects in a BIM environment, refer to this article: ALLPLAN, and this article on model coordination: Revit Structure 2019). ✅ Best Practice and Approved Solution: To ensure proper model alignment: Define a project-wide shared coordinate system: A common Survey Point and Project Base Point must be defined early in the project. Use "Acquire Coordinates" or "Publish Coordinates" functions in software like Revit. Write custom Solibri checking rules for coordinate verification: Import Models: Import architectural and structural models into Solibri. Visual Inspection: Use the "Comparison" feature for visual alignment inspection. Relative Position Verification Rules: Create custom rules to verify the relative position of key elements (such as columns and core walls) from different disciplines. For example, a "Components are within Tolerance" rule can check if structural columns are within a small tolerance (e.g., 5mm) of their architectural counterparts. Identify Unlocated Components: Use "Rules for Unlocated Components" to identify elements that may have shifted or been misplaced. Link Models with Shared Coordinates: Ensure that all linked models in authoring software are placed using the "Place by Shared Coordinates" option.Common Mistake #2: Lack of Grid System Coordination and Shared Origin Points (Coordinate Corruption)