# data[].attributes.body
Setting FOC to 60-75
Walk Speed - 10-15
Run the appearance profiler and update home veiew point

# data[].attributes.body
Set issues to Reviewed and then Compact to remove resolved issues

# data[].attributes.body
1. Check for sectioning of each viewpoint in Saved viewpoints
2. Before reporting out make sure Auto load mode is on.
3. Check for Appearance profiler before reporting out for ease of understanding the trades
4. Auto Reveal mode should be unchecked
5. If we want to see typical issues at once, we can use 'preserve result highlighting' mode.
6. Use assign to feature for reporting out Level/Trade wise for respective Homeviewpoint
7. Make sure we use hide/override appearances for only Homeviewpoint in order to load the viewpoints faster.

# data[].attributes.body
Always check the coordinates in Revit by Turning on the Project Base Point and Survey Point from VV

# data[].attributes.body
Always preper importing clashes batches and search sets from previous projects while setting up new project, helps save time and setup quickly

Always select search sets when creating clash batches and not the file

# data[].attributes.body
Processing & Filtering of Issues, Viewpoint Creation

# data[].attributes.headline
Using Flypaper & BIM Track for Grouping Clashes

# data[].attributes.subject
Using Flypaper & BIM Track for Grouping Clashes

# data[].attributes.body
Separate Out Typical Clashes
Explode and then group remaining clashes

BIM Track Clash Grouper
For Grouping Large no. of clashes - 5k-10k clashes

# data[].attributes.body
Append Models, Creating Search Sets, Clash Batches, Setting up Appearance Profile

# data[].attributes.body
Check the model content wrt to drawings
Should be done during Project Setup
Ensure Proper Levels are assigned to the Model
The Grids should always align with Design Models
Coordinate systems should match with the Design Files

# data[].attributes.body
1. Updating the viewpoint for existing Issues on BIM Track while working parallelly on clashes
2. Check if we are using correct attributes and the Template(Confirm with POC about what attributes should vC fill and which template is being used).
3. Before pushing Issues to BT, confirm Issues/Non Issues with POCs.
4. Check for proper settings in BIM Track Settings
5. Before clash run, we can quickly check how many issues from previous update have resolved with the help of BIM track/Power BI dashboard.
6. Generating reports wrt status of Issues on BIM Track to get better picture for which are Issues and Non Issues.
7. Mark non issues as approved in clash detection in order to get clear idea about non issues for the next run.
8. Do not use refresh function after clash detection and before pushing the issues to BIM track since the updated models may make issues either resolved or the osition of viewpoints may change
9. Keeping the FOV upto 65-75 for the Home viewpoint.
10. Check file options

# data[].attributes.body
Appending models in a Stream line - Starting with Arch, STR models and so on.

Save as for Setting up Multiple Models
May become heavy if there are lot of Versions for Models

Set Current view as Home view

# data[].attributes.body
Revit Federated Model and Design Exports

# data[].attributes.body
check the revit file coordinates with Respect to Control point

Arch and STR if misaligned could be aligned by using common elements like Columns

Ask Trade Partners to export the Grids along with the model

# data[].attributes.body
Topic : Project Setup & Issue Grouping

# data[].attributes.body
Issue Reporting / Managing Issues on BIM Track