Simplify Construction Model Coordination and Navisworks

good everyone really good to have you in this recorded session my name is Craig Howie I'm the technical director of digital uh for acon based in South Africa I run a digital project delivery team here in South Africa that works on projects both locally and internationally and we're currently busy on projects in a couple of different locations obviously in South Africa in Canada in the Middle East and also in the United Kingdom the team that I manage is made up of a couple of Bim coordinators boo

m managers and information managers and we use Autodesk boom 360 and ACC fairly regularly also we we use a lot of navisworks uh the team that I work with is very passionate about building 360 and ACC as well as navisworks so really looking forward to presenting this topic to you to you today just going to hand over quickly to the mid for him to introduce himself thank you click and hi all uh nice to have you all here my name is namit ranjin and I am a senior implementation consultant with Autode

sk I'm based out of Bangalore India I'm a civil engineer by academics but by Professor profession and practice I've always been into Bim uh I specialize in Automation and computational Design this is my fourth year at Autodesk and I serve as a subject matter expert for building related products together with the automation Spectrum containing products like Dynamo generative design and Forge thank you and over to you shashat thank you named hello everyone it's pleasure meeting you virtually my na

me is senior implementation consultant based out of Bangalore India I'm also civil engineer by degree like namit and started my career as a structural engineer in the power plant design sector and worked on many detailed design and construction project I joined Autodesk four years ago and currently helping Autodesk Enterprise customers by innovating their design and construction workflows with the aec products and Autodesk Construction Solutions I will now hand over to Craig uh to start with the

EU class over to you Craig thank you great thanks uh great so we've got Autodesk on the cool with me um so as is tradition uh save Harbor statement applies um all right so jumping straight into the agenda obviously the topic is solving the clash between model coordination and navisworks and we're going to run through a couple of different sections the first one is looking at model coordination the tool versus navisworks and I'm going to give you some key insights as to how Acom is making a deci

sion between using either one of those tools or both then we're going to talk a little bit about Clash avoidance obviously you can't talk about the topic of clash detection with our Clash avoidance and so we can talk through that then moving on to giving you some key insights Around Clash standards and processes that we're applying at acon and then ending off uh namit are going to talk us through some reporting and dashboarding and how a common is using some of the dashboarding features so jumpi

ng into the presentation uh model coordination in navasfix so this has been quite a big question that we've been asking ourselves at Acom over the last few months the two tools model coordination and navisworks obviously have a couple of features that overlap and sometimes it's not all that easy to decide which tool to use so just to run through some of the features that overlap um obviously both of the tools um do model Federation and so very alike with that um they are both model viewers uh ob

viously the one is online the other one is desktop based tool they both have an issue management tool of sorts um obviously model coordination is fully integrated with building 360 or ACC issues and then you now have navasfix obviously traditionally you would have used something like viewpoints as sort of a pseudo way of working with issues but now you've got the issues tool in namasteworks which integrates across both authoring tools navisworks and in obviously into boom 360 and ACC and then th

e last feature over that is Clash detection and Reporting so both model coordination has a clash tool it does automated Clash detection so as long as you drop models in a certain location it federates clashes those models against one another and then you've got sort of the navistrix approach to class detection we've got the class detective you go in you set your rules you set your clashes you run those clashes the following week if you need to run clashes again you go in and run those clashes um

over and over again sort of manually one would say then reporting um both tools do a level of reporting there's certain reporting features within model coordination itself it's fairly basic You've Got The Clash Matrix view that you can look at and there aren't really too many other sort of reporting dashboarding features around clashes themselves within model coordination obviously you can do reporting around issues and that sort of thing but there's fairly limited tools within the application

for for reporting on on clashes and then you've got navisworks where where you're doing possibly very detailed Clash detection and you can output reports from class detection oh sorry from The Clash Detective and um from The Clash detective you obviously can also export various file formats that can get integrated into different dashboarding applications so just to talk through the combinations of the tools um so you have model coordination Standalone which you potentially can use just by itself

you then have navisworks which also you can use Standalone sort of AKA old school nervous works and we've been using navaswix in the aec industry and other Industries for many years now and then the sort of new approach is obviously taking model coordination and combining it with navistrix and um yeah obviously that's one of the the newer approaches to working um and we're seeing a lot of uh positive movements in that space at the moment so how do we decide on what tools to use and what combina

tion of tools to use so I'd say that there's probably four factors that we're looking at when we choose which tool to use and the first one is size and complexity of models and of the overall project when we we talk about complexity that's got to do with uh sizes and models it's got to do with file formats it's got to do with quantity of models and then also the factor is how many different stakeholders there are and how many models they're providing that's quite a critical one on which route we

go is a model coordination or navisworks or a combination of the two the next one is reporting and dashboarding requirements and so if you have very basic reporting requirements then a certain tool may be better if you've got more advanced reporting requirements and dashboarding requirements which obviously some projects have and certain clients have and you're going to sort of lean towards um one of the other products then there's a level of customizability so something like model coordination

is very easy to use it's very simple but it's not highly customizable and some teams do want that and sometimes that's really a good thing to have stuff that's quite simple uh navasfix on the other hand lots of granularity you can customize it a lot you can um exclude things you can really get into customizing it quite a lot and then obviously that customization remains within the file that you're working in where's one of the the challenges maybe with something like model coordination is doesn

't necessarily keep your settings that you you using like a filter or something like that next time you open it up potentially you have to go and reset things um so that's one key thing the next one is team setup um roles and responsibilities on a project obviously plays quite a big part around what tools you're using and then in particular Around Clash detection how you deal with Clash detection if you have a Bim manager on a project that is given the role of doing class detection and given a l

ot of time to do Clash detection and potentially you're going to use a certain set of tools if you are making pushing class detection and coordination activities back to project teams a lot more which which differently we we're doing in the industry at the moment then you're going to possibly use different tools for that that are maybe a bit more suitable then as far as skills go um you know do you have a team that's uh looking for a sort of basic tool to work with is it are you working with a t

eam that's looking for a more advanced um Advanced tool what are these skills do you have people that never worked with navistrix and maybe putting them on something like model coordination is a very easy win maybe you've got a team that's actually worked extensively with navistrix in the past and you want to keep that experience and and use it and then the last one is licensing so obviously there are licensing considerations when choosing which tool and I think different um companies are going

to deal with this quite differently and I think also different markets are going to deal with this quite differently if I look at a market like South Africa and Africa I think licensing will pay quite a big part in which tools get used and maybe that's not going to be exactly the same everywhere else but differently in a market like South Africa you're going to see people wanting to use certain combinations um very much so driven off of initial outlay of Licensing costs great so if we look at th

e projects that we're using model coordination and navistriction we have a combination of projects we have schools we have museums we have shopping centers um even some sort of more civil infrastructure projects out of my group like Pump Station treatment plants mixed use projects and some data centers and those projects are located in in different regions so there's a combination of South Africa Middle East Canada um that we're using the software and those projects are based in those locations

so what we generally do is we look at our project we look at what sort of complexity is this project based off of the four factors that I shared on the previous slide and we rate them as either a low complexity for using model coordination and navisworks or a higher complexity for using model coordination or navisworks to out of all the projects that we've run so far we generally feel that for basic projects um projects that maybe there's not too many different file formats that models are relat

ively simple um where uh Team structure is not overly complicated model coordination is really powerful for those types of projects and we're seeing really good traction on some of our more basic sort of mid-range projects with model coordination the nice thing with model coordination is you can sort of set it up and then the team can use the platform and it requires minimal uh sort of ongoing maintenance and that sort of thing from Urban manager which is really nice on our more complicated proj

ects we're definitely leaning in more towards using a combination of model coordination and navisworks and you know having the models sitting in the cloud really helps with dispersed teams and bringing in the power of navis weeks on top of that really is is great I've put an asterisk there on the navistrict Standalone um so that's sort of like old school novice Works um you know federating models that are sitting off you on your computer or on a server we still do believe that there is most prob

ably a place for that where projects are very very complicated where there's many many file formats coming in from different different sources and maybe where the project team is working in a different CDE to and maybe not using the 360 ways you see as their primary CDE so there is still a place for that okay so once you've decided on what tool you want to use you want to obviously start talking about um you know prevention of of clashes um so Clash of woodings obviously always quite a Hot Topic

um and and that's really where we should focus a lot of our time and then the class detection part is obviously a lot simpler so what we did is we went back and looked at what are the causes of a clash and I must say there was pretty um there was a lot of alignment on on what the the team stored around what was causing clashes there weren't too many uh completely out there ideas everyone sort of knows what causes clashes we believe that to be um most probably front and center is just poor plann

ing poor project planning is really plays a big part in clashes a level of lack of standardization either in your corporate standards um and how they're set up or alternatively at a project level maybe not having the standardization or at least the um the uh Clarity on what those standards are bad communication a lot of clashes are caused by teams not communicating well well with one another either within a team or even certain teams communicating with other teams so that those three are really

the big ticket ones that we felt then you've got scope misalignment so we we definitely believe that uh projects are still not maybe being scoped with the model first approach um so it's a scope differently there is scope misalignment and projects and you know this is not a thing that's unique to a company like Acom this is um you know really common across uh across a lot of companies and then model experience is one that comes into play when when you're seeing a lot of clashes in particular mod

el experience around having four thoughts and what you're doing so having awareness around what you're doing when you're modeling and then understanding that okay I'm about to put a system into this area but I've I've designed and I've modeled five projects like this already so I know that there's going to be another service going into this location or a unit yeah or a wall here or whatever so model experiences differently a factor then the last three and most probably the least uh sort of the t

he last three maybe not the most critical but definitely uh players is lazy modeling definitely some of the clashes we see is just modelers being lazy in the way that they work uh the other one which is quite a big one is lack of collaborative mindset so we'll have teams that sometimes are very much so working in a siled approach to how they they model or design and they're only focused on getting their their particular package out the door and like we'll switch off models and just model their s

tuff and not really take into consideration sort of collaborative mindset to doing things and the last one is limits of Technology we do believe that technology could still play uh more of the active part in how we do Clash avoidance and I'll allude to some of those a bit later so talking about modeler techniques for clash avoidance um we've got four specific techniques that we're trying to push with with our teams the first one is for MEP teams so service zoning and service planning is really i

mportant if you don't do it you are going to land up having a lot of clashes no surprise there one of the approaches we are trying is we're trying to do some sort of more schematic 3D massing of large services um initially on projects um very easy to to move that that sort of main run around quickly and get a very good idea of three-dimensional Services um zoning we then take that once we we've got that nursing sort of thought out and then documents it in a 2d process just for for future referen

ce um we're finding that quite effective on some of our projects at the moment where the team is actively and consciously applying that process the next one is the use of the dynamic use of section box tool within Revit we feel that that really can help you with spatial awareness make you more effective in your modeling you've also got good add-ins on the market like the Queen's section box tool one thing that's most probably still missing in Revit is a first person option for navigating through

models we'd really like to see some improvements of uh how we've used stuff in revits in a more Dynamic way we sort of fly through the model like we would with other industry applications possibly that will never come into Revit itself but it would be nice to have a live connection to a tool that's quite good at viewing models and and driving sort of spatial awareness so section box office you can get quite cumbersome when models are quite big and moving the section box around can be a bit uh s

low um so having that live connection would be really good then on the MEP side one of the techniques we're trying um to to use more is within a Pim 360 with ACC environment we instead of teams MEP based teams sharing their models once a week through design collaboration and then each and every individual MEP team consuming that model once a week we sometimes during certain periods of projects Live Links the MEP so our mechanical electrical plumbing and fire if we do have it separated we'll have

the other models live linked we find that that provides a lot more of a dynamic environment now we don't do that with architecture structures we're happy just seeing their updates maybe once a week but within a sort of active MEP team we're finding that that live linking does help then we are slowly trying to change our approach to how we segregate models we we've got ourselves in these very large projects into a habit of breaking up every single discipline into a different Revit model and we'r

e actively working on our MEP models to try and combine those into instead of having five or six MEP models per Zone we're trying to compact those and see where those synergies between different disciplines uh even trying to get modelers to model more than one type of service does help and then the last one is screen setup uh we we did a an interesting exercise which I'm about to show you to drive improved spatial awareness when people are modeling and I think this uh this area is definitely som

ething that uh can help with with Clash avoidance so what we did is uh we did a bit of a fun exercise with the team recently um we we asked him to do a screen selfie of what their screen real estate looks like so not really the hardware I'm not too concerned about that just want to see how people are laying stuff out on these screens and are they laying their stuff out on their screens an effective way to be productive in the production that they're doing but also do they have a coordination typ

e mindset or a an approach that is allowing for them to have a better spatial awareness as they're working they've got very good spatial awareness of what's happening around them in the model and so one of the the key themes that we picked up with this is a lot of uh you know a lot of the guys had more than one screen obviously um Everybody sent either two screens or three screen options uh felt a little bit jealous uh I've I've most probably got a bit of a lack of a good screen setup at the mom

ent looking at some of the teams combinations um but we one of the main teams that we saw was a in a three screen process as an example which is on the screen now is teams grouping a theme on each screen so in this example the person had reference material on the far left unfortunately it's a PDF I think so maybe that's not always the best example in the middle he was very clear on his approach to his modeling space it's his primary modeling space the the teams were very clear that they like to

use the river tabs and have a couple of river tabs available to you to jump between SO gas and a good 3D view they were quite vocal about not liking child views and saying that it just gets messy and it's not really that helpful which is quite interesting feedback and then the last screen is tools and files so you can see they're really extended out there uh their tools panels to see information see data and then they're obviously also looking at a couple of files the next Trend that we saw and

this is what I was hoping to see is a combination of authoring tools and a combination of viewing and coordination tools so yeah yeah you can see the users got his his tools for for authoring and modeling opening on open on the left and he's got a viewer and a coordination tool on the far right so it's revered on the left and another switch on the right that that was really what I was wanting to see and I think we generally saw that as a bit of a trend the last option that one of the users came

up with was quite Advanced at least to me um so you didn't only you didn't have one screen option you had three screen options and what he does is he uses the Windows task view to customize desktop so it comes in every day and he customizes desktop it's very organized about how he's dealing and and toggling between different desktop options so you had a three three screen setup for communication for modeling and drawing and then coordination and modeling so quite in a more detailed look at how s

creen layout works but I definitely felt that this user had very good spatial awareness around how he was working and I believe that would lead to having less clashes or at least him causing less clashes all right and jumping into Clash standards and processes um so before I get into Clash standards themselves um I think with Bim 360 and ACC information flows is really important the tools are quite simple uh you have sort of carte blanche in some ways of how you can set folders up so you have to

have quite a a strict work at least a quite a good understanding of how you want information to flow within Bim 360 and ACC and that relates to eventually to how you do coordination or design review or or class detection so in this setup you'll see that I've got uh all the different modules listed on the left we've got document management design collaboration model coordination and then we have our dashboarding which is obviously external at this stage for us um through Power bi and then we've

got a very distinct approach to how we deal with Revit models and how we deal with say navistrix models within the work of progress State shared published and archived in ISO 19650 terminology so the the takeout here is just understand what you want your information flow to to do for you understand how the different modules can allow you to move information in different files from one work state to another workstate so for example with the work in progress we will use design collaboration to mov

e information into the shared area when we move information from the shared area to the published area we'll use the review work we'll we'll review workflows to move that information across also key to this is understanding where you want to do things so where do you want to do class detection do you want to do class detection and work in progress information do you maybe want to do some class detection reporting unshared information and in in your published area is that an area that you want to

actively work with your clients and users their issue management area of replacing pins and models and deliverables so you really need to give that some detailed thought um then diving into our actual Clash detection standards we've actually overhauled them a little bit recently because features are changing quite rapidly around us and tools are advancing and we we've had to go back and refresh our approach so looking at that approach we we looked at six different key things around class detect

ion the first one was how do we access Federated models we obviously now got the option with monocle Nation to have the models located on the cloud and we can point navisworks at those models on the cloud that's a huge advancement to how we used to work with navasfix with class detection um tests we'd sort of gone down a route where we had themed Clash detection tests and we had lots of class statistics class detection tests actually over 300 different tests that we would use as a standard and w

e sort of felt that we were starting to trip up over that standard as we try to scale it out um class grouping you've now got a class grouping tool within navasfix definitely you had third-party add-ins that did that previously but that kind of changes the landscape a bit around how detailed your Clash tests need to be because you can now use cash grouping to really get some granularity in your patch tests the next one is team engagement uh you know keep it simple type approach you know roles an

d responsibilities is always a thing when it comes to coordination and class detection you know it's not the manager's role to do class detection or at least to solve clashes it's the design team's responsibility yet we often see the clan the the bid manager um doing and doing some of those tasks so at least getting a little bit more involved in than what they should the next one is class resolution and we've separated class resolution and clash and Reporting um we found that we maybe sometimes

are too hyper focused on reporting on clashes and weren't thinking enough about how uh how we effectively give Clash information to teams or how effectively um teams can access class information themselves even um to effectively update those clashes and resolve them versus having a very much so mindset around a class detection to produce a report obviously reporting is important so so that was a factor in in some of our updated standards so then we took those key Focus areas and embedded some of

the new features and some of the new Concepts that we wanted to apply so for example for accessing Federated models you know master nwfs and work in progress in wfs on on Bim 360 or in model coordination really new nice new advancements um you know flash grouping We Got The Clash tool so we went and embedded those different features onto this loud I won't go through all of them now um but that that was kind of the way that we we processed the information to to work it out okay so this is what o

ur current cash detection process looks like um you know looking at it you might say well we haven't exactly kept it simple Craig the reality is we work on big projects and there are complexities to working on big projects and we work with big teams in these complexities so this is what our Clash detection approach looks like for large complicated projects and we've taken the approach where we we've mapped it out and really looked at what does role each role do so what does a Bim manager do what

does a design manager or the designer do what does a discipline design lead do what are these what are the different roles or different stakeholders and what tasks do they do so we've mapped that out in different swim Lanes I mean being very specific about who does what and then we've also tried to start Shifting the approach a little bit so we're bringing the design discipline design lead into the process with what we had found in the past that you know class detection and model coordination o

ften will seem to be a modular thing or a bin thing and designers were you know divorced from it so we've gone away we've remapped it we've looked at the process in four steps so obviously the boom managers in in the sort of cyan color the managers involved in some of the setup as quickly as possible he gets nwf files files out to the team the team then use those NWA files for the the full duration of the project they use that to run their own uh internal meetings uh once they've done some of th

eir own internal meetings that goes and moves out to a shared area where there is more sort of weekly coordination done at a high level we bring the design manager friends and Center into that process to support that and we run those two um discipline and interdiscipline or uh work in progress and shared approach and next to one another over weekly cycles and then obviously at an issue at a point of issue a milestone you then get to to issuing that information out so we've been quiet um quite sp

ecific in our approach you'll see that it uses model coordination and it uses navisworks for different things we use nwf files for work in progress we use nwf files for uh shared and we we output obviously nwd files because often that is a requirement from the client side one of the the pain points in this process still is how to update statuses in navisworks you know something like model coordination has the not an issue feature which is quite nice but navig is still a little bit awkward as to

how somebody can go into model look at clashes and then update the status of that Clash especially when it comes to trying to do that in a user multi-user environment so the lessons that we've learned so far with model coordination and navisworks um published times can take a while um we've had a few challenges with with published times so just allow for that in your workflow um and in your process uh you know somebody publishes a big model it's not going to be available instantaneously so you n

eed to to have a process that's flexible to to work with that the next one is do not publish Sheets if not completely essential now that might be a bit controversial to some you know the fully integrated approach should be publish your Revit mobile model publish your sheets your Revit sheets do review on that model and on those Revit sheets uh I think for small to medium-sized projects that is suitable I think for very very big projects or or maybe even projects that still have very complicated

model setups we find that the time to process sheets slows things down and it becomes a little bit counterproductive so if you don't absolutely need it turn your sheets off and your published time is going to be faster the internal clashes and model coordination um so model coordination I obviously have the feature to be able to turn this feature off if you're doing Clash detection and noviceworks turn them the model coordination clashes off it'll help with processing time into model coordinatio

n so that's another key thing that we've found there great so I'm going to hand over to shashwat and namit and they're going to talk us through some of the reporting and dashboarding that we've been involved with with them and some sort of Industry insights thanks guys thank you Greg reporting and dashboarding to make the Clash proc process much more productive there is no better way than dashboarding to aggregate all of your important project metrics in one place reporting and dashboarding help

you identify Trends and patterns and enable you to make the informed decisions it is also perhaps one of the Prime attraction on LinkedIn to have fancy visual visualizations however in order to make your project decisions data driven it is important to utilize the correct data in the correct way not all dashboards create equal value in this section we will talk about our efforts and learning lessons around reporting and dashboarding to make the class process much more productive as we all know

data export is the first place to start this process so let's look at the data export option in our context there are multiple ways by which we can extract the data to capture the actionable information from the Bim models or from cloud projects from the Autodesk construction cloud in product reporting features we can extract the issue reports directly from the web application we can export issue summary report issue details report containing the issue list its status type title description and

root causes and due date this is simple export and does not require any customization of the tool now if you need to customize the data reporting and would like to create your own bi dashboards then you can extract the account level data of the ACC project with the help of data connector data connector offers you the flexibility to analyze the data using your own business intelligence tools with low level of code integration furthermore from the inside Tools in construction Cloud platform you ca

n connect the data from partner application to your insights dashboards this means you don't have to switch between application as you can view all the relevant project data in single area to provide a holistic view of the project performance there are chances that the Data Insights from the in-product features are not providing you the required information and hence with the help of foods based apis you can access the design and Engineering data and customize it based on your project requiremen

t this requires High code involvement moreover directly from the navysbox application you can export Clash reports view Viewpoint X reports Etc and we will discuss this in our coming slides how Acom has created dashboards to capture the trend of clashes to provide the Insight on coordination now before we go to the data connector we would like to highlight the current issue management features differences between Bim 360 and ACC projects there are some substantial features that are now added in

ACC issue management as compared to Bim 360. in Bim 360 there is no option to import the issues in bulk however using ACC we can bulk import the issues using Excel sheets the referencing option also are limited in Bim 360 currently and we can only uh link or refer the rfis assets files as a references but in Autodesk construction Cloud platform you can add additional references to the issues such as sheets photos project schedule and more this would allow users to better communicate the informat

ion during the issue management process it is not possible to publish or unpublish the issues in Bim 360 however in ECC you can create private issues and after filling all the relevant information you can then publish the issues if you had received a lot of requests from the customer who want to delete the issues in Bim 360. the good news is now in Autodesk construction Cloud projects if by mistake you have created any issue you can delete them permanently last but not the least in Autodesk cons

truction Cloud platform we can customize the company logo in the issue reports but Bim 360 currently don't have this functionality in place with that let's discuss the in-product reporting from data connector if you need to customize the information and create your own business intelligence dashboards then you can also extract the account level or project level data from the ECC project with the help of data connector data connector offers you the flexibility to analyze the data using your own b

i tools with low level of code integration and currently there are two ways by which you can extract the ACC data using data data connector you can either download the CSP report in your local system and capture the insights or directly in my Microsoft power bi with the help of certified Autodesk construction Cloud connector you can get that data and create your own bi dashboards once you have integrated the data connector in power bi then you do not have to worry about the data sync as it will

automatically sync the data based on the sync frequency that you have set in your Autodesk construction Cloud project and if you need further customization in data connector then we with the help of the data connector force base API you can do it now this is one of the dashboard samples that we developed as a proof of concept with Ecom to showcase the integration of the account level inside with the help of ECC data connector in power bi this data this dashboard is capturing the account level in

formation of the total number of issues created at account level you can then filter this information uh created the issues created by company by type by status and this also uh showing the timeline of the creation of date with the status from the dashboard the custom attribute information such as priority and discipline what what we have what Ecom has added in the issues template that can be added in the issue details and this can also be captured via this dashboard this is the live data integr

ation and we can filter the issues created by project type company and other with other attributes hence by incorporating the data and analytics in your project workflows you can streamline operations and optimize the project delivery with that I will hand over to namith and namith will tell us and provide us give some insights on forge-based data attraction over to you name it well thank you shashwat uh let's talk a little about Autodesk Forge as the next data export option Forge is autodesk's

cloud development platform the first platform is a set of web services apis which can be used to build Innovative Cloud powered applications now since we've been talking about ACC and Bin 360 it would be interesting to add that both ACC and Bin 360 are based on top of Forge and that means your files your issues clashes and pretty much everything on Bim 360 and ACC is accessible and controllable via Forge you can automate stuff think about getting a WhatsApp notification when somebody uploads a f

ile on Docs from automating these little tasks to design Automation and much Beyond you can use Forge to create digital twins visualize and analyze data integrate AR and VR and a lot more now coming back to visualization some of the relevant apis for us in the context of reporting and visualizing clashes were account admin model coordination and issues the model coordination apis provides information around coordination spaces models Vos and clashes so we developed a proof of concept to bring in

this data using four model coordination apis into Power bi which could then be used to provide an overview of clashes in the selected project the POC also offered visualization for clash progress distribution categories and resolved clashes versus total the timeline of clashes with status was intended to provide a trend line and relevant filters to select you know project type company and roles allowed to narrow on on the on the data and get precise information um also we were not able to utili

ze this dashboard into the main project this was intended for because we decided not to use model coordination Standalone in this project because of the project requirements which sort of takes us back to our initial slides where we talked about factors that govern what to use uh but in the projects where model coordination Standalone is a reasonable option Acom might want to convert this proof of concept into production in the future now creating something like this does require bit of programm

ing database and power bi skills but in the long term the gains would you know the gains could be sort of worth it you know if you have many projects using Standalone model coordination now let's take a look at the final and the most conventional way to utilize data export and import this is once again a class dashboard but this takes in data from navisworks it provides a trend line of clashes to provide insights on coordination uh details slash information by package and discipline and also cla

shes are distributed by status and priority level this is something that requires human inputs and is a manual process let's get on to the next slide to have a look at the secret recipe to build this well not a secret anymore so basically we call it source files like nwcs into NWS and get xmls from the respective nwfs the xmls contain class details priority levels disciplines and other attributes coming from navisworks the next step is to drop these xmls from different teams into a defined locat

ion over SharePoint as seen in the diagram the data from XML gets Federated into an Excel spreadsheet and that spreadsheet becomes the data source for our power bi report with that I'll pass it over to Craig great thanks Amit so dashboarding we we've definitely been learning some some lessons around the importance of of different dashboards for for different features within the different tools um one thing we we have found and and that people should be aware of is the danger of chasing clashes a

nd as a sort of a number or a kpi and losing sight on just good quality design coordination we have some had some instances where team have been too hyper focused on the numbers and and haven't been focused on on quality coordination the other one is just having a plan around uh what you want a dashboard so set your boom 360 in your ACC up in a way that is suitable for Downstream dashboarding of information so if you're going to dashboard issues make sure that you've organized your the way that

you use issues make sure that you have organized the way that you maybe set up custom attributes for issues so that you can dashboard or have effective dashboards um further further down the down the line on the project some of the really positive things that we're getting out of dashboards um you know project insights with minimal human efforts um you know we're working on fairly large projects it's not always possible to to check everything uh manually and all the time so we really get really

great um insights with minimal human effort which is great um we can really use those in science to make key decisions on projects then transparency is a big one you know you cannot hide when all the data is just pushing into into a dashboard so you can very quickly see which teams are engaged which teams are behind on things um you know potentially where there's problems um so it's really great uh to to have that sort of level of transparency and then the last thing is um you know driving posit

ive team engagement I think dashboards are one of those special things that pull different team members together um you know historically often you've had designers you know separated away from from modeling and it's one of those things that now pull modeling teams and design teams together and also pulls in some of the other key stakeholders and projects uh lead designers designers project managers that sort of thing so we're really seeing great uh Team engagement and um you know that's really

helping us move move things forward thanks uh let's move to the next one okay so the next section is a couple of suggestions from our site um you know we work with the tools a lot um we you know we sometimes give all of this a bit of a hard time they're putting out a lot of a lot of features all the time for us into tools and we always want more um but this was probably a few things that we would still like to see um one of the first things is a truly multi-user environment especially around how

you you update Clash statuses so model coordination has it you can go in say something's not an issue but within the navistrix environment that's still very awkward how you can get that to work we've been trying a couple of different things we've been using Dynamo scripts to to help with with that um but have tripped up with a few things there recently the next one is the UI revamp so you know navisworks is is uh quite old now it's been around um around the block and we definitely feel that it

could do is an interface update um it's very technical in nature at the moment and that means probably some time strives the wrong stigma around it um and there's I think there's definitely other tools on the market that um you know the UI is really helping with the Positive stigma and breaking the stigma of it just being a technical Bim tool you know um the next one is uh you know we really feel that the Revit product team could do some more work around handling how published views work and pro

tecting teams against mistakes with published views so we often will have teams publish a view and then forget links on or or certain items and it's very easy for for team member to make that mistake and with a few tweaks here and there maybe just in Revit you could really protect against that um a bit as we like to see that and then the last one you can see that we're doing a lot of proof of Concepts around dashboards we will obviously also have a lot of dashboards active on our projects and a

lot of that effort has been done outside of the tools and tools like power bi and that sort of thing it would really be great to see some more advancement and out of the box uh dashboards within boom 360 and ACC and I'm fairly confident we will see that in the future in in ACC so that was just a sort of constructive feedback from our side on on features and improvements that we'd like to to see so I'd just like to um thank everybody for joining the session um and um yeah please do reach out on o

n socials to to either one of us um and we'll we'll answer any questions that you may have so thanks a lot thank you