Earlier in 2016, we posted about the ongoing challenge that we see with clash detection. The building information modeling (BIM) community responded enthusiastically to our views that there are inherent limitations in how we perform clash detection on today’s projects. On LinkedIn alone, we had thousands of views and hundreds of likes, indicating to us that there needed to be a change to the clash detection workflow.
Today, we’re here to tell you how our product, ClashMEP, fits in to the practice of clash detection and how it can change today’s projects.
Clash detection is currently a separate process from the act of modeling. It requires a separate program to analyze clashes, additional training on another software platform, and additional time to work in a platform that isn’t your core modeling program. The analogy we use is that clash detection is often like turning in your homework to be graded by your teacher – you turn it in on a deadline, get it graded, and make corrections the following week. This separation of process is how we currently do clash detection.
Enter ClashMEP. ClashMEP adds clash detection directly within the Autodesk Revit platform. This means that modeling and clash detection are captured on one single platform, without the need for an export.
In addition to being on one platform, ClashMEP fundamentally changes the nature of clash detection. You don’t “run” a clash report. ClashMEP is constantly tracking what you’re modeling and does real-time, dynamic clash detection! As you model, clashes are immediately indicated, giving you instant feedback. This is a capability that modelers do not currently have on any other clash detection platform.
ClashMEP is designed to work within your current modeling workflow. It detects clashes with other Revit objects (including when they’re hidden in view), linked files, IFC files, and point clouds. Training takes under 15 minutes and there are no significant hardware performance issues as you do your work.
At BuildingSP, we believe in innovation that directly affects workflows that matter on projects. Here are three ways that ClashMEP is a valuable, innovative addition to any MEP modeling workflow:
1. Minimize Coordination Time
We were talking to a large university recently and they estimated that each MEP coordination meeting costs at least $20K. If you add up the project billing rates of all the participants in coordination, you can easily convince yourself this is true. ClashMEP minimizes coordination time by bringing clash detection directly to the modeling platform in real time. This changes the project workflow (and saves money) by lowering the reliance on coordination meetings.
2. Skip Modeling of Point Clouds
ClashMEP does clash detection against point clouds. When ClashMEP detects an object clashing with point cloud data, it increases the visibility of the object, and the point cloud doesn’t even need to be visible in the view. If you’re working with point cloud data, this means you can do MEP routing without first converting the point cloud into a model! This saves you time, money, and reduces risk on your projects with as-built conditions.
3. Leverage Collaboration for Revit (C4R)
Collaboration for Revit centralizes BIM information for project teams. It uses a cloud service to allow multi-user, concurrent co-authoring of BIM content within Revit. ClashMEP works in C4R environments, which means that more and more of your project will be on one platform and in real time. When used with C4R, ClashMEP may nearly eliminate the need for any separate clash detection processes.
Our work at BuildingSP is not yet done. We are continuing development of both ClashMEP and GenMEP. In a future post, we will describe how ClashMEP works so that you can understand how our technology is unique, different, and exciting. In the near future, we hope to announce new versions of ClashMEP for other modeling platforms, including AutoCAD.