Purpose
1. Automate clash detection in design and engineering models to ensure early conflict identification between architectural, structural, and MEP models.
2. Provide real-time, automated clash detection notifications to involved teams, automating documentation of clashes for streamlined resolution.
3. Automates the consolidation and archiving of clash data, supports regulatory compliance, and accelerates the overall design workflow by automating communication and reporting tasks.
Trigger Conditions
1. Automated trigger upon completion or update of model merging in BIM software.
2. Automates with scheduled clash detection scans (hourly, daily, per change).
3. Triggered by manual request or automatedly when a model with new geometry is uploaded.
Platform Variants
1. Autodesk Navisworks
• Setting: Use 'FindClash' and 'OnClashFound' event listeners.
2. Revit
• Setting: Automate event triggers on model saves.
3. BIM 360
• Setting: API call to /issues endpoint post-detection.
4. Procore
• Setting: Webhook for new coordination issue.
5. Bluebeam Revu
• Setting: Automate batch Studio Push by clash-detection script.
6. Slack
• Setting: Dynamically populate #clash-detections channel.
7. Microsoft Teams
• Setting: Automator bot posts detailed clash summary cards.
8. Jira
• Setting: Automate with /issue POST endpoint.
9. Asana
• Setting: POST /tasks for each clash detected.
10. Trello
• Setting: Automate POST to /cards.
11. Monday.com
• Setting: POST /items for clash reporting.
12. Google Sheets
• Setting: Append automatedly on clash detection event.
13. SharePoint
• Setting: Automate POST to /_api/web/lists for reporting.
14. Dropbox
• Setting: Automate file push to project folder.
15. DocuSign
• Setting: Create envelope using DocuSign API post-detection.
16. Adobe Sign
• Setting: REST API POST agreement creation upon closure of clash.
17. Gmail
• Setting: POST to /gmail/v1/users/me/messages/send after detection.
18. Outlook
• Setting: Automated email event upon detection/reporting.
19. Zapier
• Setting: Automated triggers on new clash event.
20. Twilio SMS
• Setting: POST to /Messages with clash details.
21. AWS S3
• Setting: Use AWS SDK to PutObject after each report is generated.
22. OneDrive
• Setting: Graph API to automate file save upon clash detection.
Benefits
1. Automates detection, notification, and documentation for faster issue resolution.
2. Reduces manual overhead, automating communications and recordkeeping.
3. Centralizes clash data, automating reporting and compliance tasks.
4. Minimizes risk of oversight via automated, consistent notifications.
5. Saves cost and time by automating repetitive workflow steps in the design process.