Breaking Through the Cloud: Vanderlande's Baggage Handling Revolution at LAX

KEITH PHOENIX: Hello. Welcome, everybody, to Breaking Through the Cloud, Vanderlande's Baggage Handling Revolution at LAX. Today, we are going to present to you a case study for Autodesk Construction Cloud on the LAX baggage optimization program. We are the prime contractor on this project, in charge of managing BIM for ourselves and all of the other trades involved. Which presents some unique challenges, but also some unique opportunities.

Our agenda today. We'll go through introductions. We'll discuss the challenge that we faced, the critical success factors, we identified. The solution we came up with. How to set up and execute that solution. And then we will recap some lessons learned. My name is Keith Phoenix. I'm an engineering project manager at Vanderlande. I have seven plus years of experience in layout package creation, 3D modeling of systems, BIM coordination, process standardization, and continuous improvement. With me here today is Daniel Guevara.

DANIEL GUEVARA: Thanks, Keith. Good morning, everyone. My name is Daniel. I'm a senior mechanical project engineer with Vanderlande. My background and experience is in mechanical engineering and design, field engineering, structural design, and BIM management.

KEITH PHOENIX: And we're here today representing Vanderlande. Vanderlande is a market leading global partner for future-proof logistic process automation in the warehousing, airports, and parcel sectors. The project that we're here to discuss is the Los Angeles International Airport Baggage Optimization Program Phase 2. This project is a large-scale, multiphase brownfield project where our task is to replace an existing baggage handling system to enable a new in-carrier system.

This presents some unique challenges because as a multiphase project, our goal is to replace the baggage handling system while maintaining operations for the airport. Which means that we need a very detailed, phased approach to demolition and installation. And it also presents unique challenges because there are a lot of existing brownfield conditions here that we need to account for.

The challenge that we're facing is that the industry is quickly moving towards a fully cloud-based BIM coordination environment using programs like Autodesk Construction Cloud and Revit. The issue for us is, Revit does not include baggage handling systems or conveyors by default in their program. There aren't families associated with those mechanical objects that we need to be able to coordinate with. So while we are moving towards a Revit-based solution, we need a cloud-based BIM solution for our AutoCAD and Navis workflows.

Our need, again, is to manage BIM for this large-scale, multiphase, brownfield project. Develop a way of working for our current workflow that also accommodates our external partner workflows. And take advantage of cloud-based BIM practices, the latest and greatest technology available. In the past, we've used programs like BIM 360, Revizto, and BIM Track to create our BIM software. We've used tracking and programs like Excel and Smartsheet. Development has crossed from CAD to Revit and Tekla, or whatever our subcontractors are using to provide their models to us. And sharing has been done through one drive box, SharePoint, et cetera.

So we pick and choose various pieces of software to create our BIM program for each individual project. The problems with that is, sometimes there are unclear or non-existent model acceptance requirements. We encounter multiple, sometimes incompatible file formats in our BIM environment. Models can be out of date or incomplete. We have unclear coordination hierarchy. That means who's moving what, where, when, and why? Poor clash management in general. And mismatch coordination and construction schedules. This one's my favorite. There's nothing better than coordinating something in 3D that is already installed on site.

Before integrating any type of BIM software on the LAX baggage optimization program, we took the time to determine what critical success factors did we need to make this pilot a success. For model coordination, we knew we needed high-quality models with acceptance requirements, review and approval processes, and integration processes. We knew we needed quality clash detection processes and tooling, clash logging and categorization ability, and filtering and prioritization. Communication tools for clash management assignment and reporting. And response resolution and closeout processes that could be prioritized by our construction dates.

For information exchange critical success factors, we knew we needed a common data environment that would act as a single source of truth for all of our BIM processes. We needed to define and track model and deliverable upload frequency. We needed the ability to update, identify and track model changes, escalations. And report on those changes. And define acceptable model formats and model information requirements.

As a result, Vanderlande has accelerated our BIM capabilities. Since we're no longer just participating as coordinators in BIM, but leading and managing, we decided to partner with our clients at the Los Angeles World Airport Authority, and our general contractor at Swinerton, who were already using Autodesk Construction Cloud. This is a great step forward for us in adapting towards industry trends and improving our BIM processes and capabilities.

In order to integrate ACC into our projects, we needed a new software integration process. We're using AutoCAD for our system modeling and layout. We're using Navisworks for model navigation, conversion, clash detection, and issue creation. We're using ACC for our model upload, review, approval, and issue assignment tracking, reporting, and resolution. And we're using Revit Downstream for conversions for those clients who need Revit-based deliverables.

The next step was to determine which Autodesk Construction Cloud modules did we want to incorporate onto this project. By default, we have Docs, which allows us to store and manage files and data. We need the Model Coordination module to detect and review clashes. And we need the Design Collaboration module to capture and manage design data. The next thing that we wanted to do was determine a common file format. We picked the NWC file format because it works with our AutoCAD and our Revit workflows. And it's already a part of our Navisworks workflow.

The other benefit that we see from using the NWC file format is that it integrates live with Autodesk Construction Cloud. It supports live model viewing. And we can also live link to the Navis environment using the Issues add-in order to create issues live in our Navisworks environment that will populate in the ACC environment. With our tooling and processes defined, Daniel will now walk us through setting up our ACC model environment and our model workflows.

DANIEL GUEVARA: Thanks, Keith. So I'm going to start talking about setting up ACC, and introducing the application of ACC. But before I do so, I want to introduce the participants on our project. So starting at the top of this pyramid here, we have Vanderlande. We install the BHS system. We have our subcontractor Swinerton. Their scope of work is relocating and demoing existing utilities, since this is a brownfield project. And assisting them in doing so is a team of utility specialists.

Reading these names from left to right, we have Murray Company who is in charge of HVAC and plumbing. We have COSCO Fire Protection, Rivers and Christian Architecture, G2 Electrical, and Aztecs for data and fiber. So these are all of the participants on our project. And now on the next slide, I'm going to show you how we set them up in our ACC environment. So first up, you're going to want to do is create your project space in ACC.

Once you go to the ACC home page, you'll see all of the projects that are active and that you are a part of. So you'll click on your project. And in the Docs module, you'll go over to Members. And adding members here is pretty easy to follow and straight forward. Once you're on this page, you'll click on Add Members. This will navigate you to a screen where you're asked to put in the members information. Their first name, last name. They'll need an email so they can receive the link.

And then you can add some custom fields to them, too. You can assign to what company they work for. And then you can assign them their job title. There's a variety of choices there, from architect to project manager, engineer, so on and so forth. And then lastly, you can choose to set them either as a project member or a project admin. So once you have your members set up in ACC, you need to define a folder structure. So this folder structure is going to determine how your participants upload and share collaborative files.

Here's an example of how we did our folder structure. We broke it down by trade. So we have a BHS folder. This is the folder Vanderlande is most active in. This is where we upload any files pertaining to the conveyor system. We have an NEP folder for Swinerton. This is where they put in any files that pertain to the demo or relocation of utilities. And so on and so forth for the architectural and structural aspects of the building.

Once you have your folder structure set up, the last thing you need to do is to grab folder permission and access settings. So clicking the sidebar menu on any one of the folders you set up, you can scroll down to Permission Settings. And it'll navigate you to this screen here. And this here allows you to grant access to your team members. So you type in the team member's name once they're set up in your ACC. And you can give them this minimal access to just view files. Or you can give them full administrative controls over such folders.

So we went over how to set up our ACC by adding our team members and uploading-- and setting up our folder structure. Now we're ready to begin populating models into these folders. So in this example, I'm going to navigate over to our BHS folder here. Now, you can see here there's a lot of files in this folder. It's very congested. Over 40 plus files in this folder. The reason for that is because for our system being so large and complex and in a brownfield setting, it requires a team of several design engineers working simultaneously.

So we take our large system, we break it into smaller subsystems. And we append each file one by one, the system comes together as a whole. So when you're working in a manner such as this with multiple engineers working at the same time, it's very important that you have really good revision and document control. ACC has a good document and revision control embedded into the Documents module. It is very easy to follow. It's as simple as picking a naming convention for a file, uploading another version of that file with the same naming convention. And the version number will automatically update for you.

So if you see here, we have a range of different versions with a range of different upload dates. And all this is automatically kept for you. And uploading files is as simple as just dragging and dropping them into this folder. So the next thing we're going to go over is an example of uploading one of these files here. I'm going to navigate over to my [INAUDIBLE] TC19 file, which is my structural support steel for my TC19 conveyor.

You see here we're on version 8. I'm going to drag and drop a new version of this file here, making sure the naming convention is still the same. And you'll see this file now went from version 8 to version 9. The upload date has been updated. So this is a good way to communicate to your other BIM participants who maybe aren't in your company for them to navigate over to your folder and being able to filter by the latest version or the last upload date. This makes sure that everyone is aware and up to date with the latest and greatest files.

So we've gone over how to populate models into our folders. To maintain a well-kept environment, it's important to have some review process. So in our project, we want to make sure everything funnels through the BIM manager. This ensures a few things for us. It makes sure that only quality and well-reviewed models are making it into the federated workspace. So in this section, I'm going to go over how to initiate the model reviews.

If you click on one of the files in one of your folders, on the sidebar menu, there is an option to Submit for Review. So you'll go ahead and click that. And that'll bring up this window here. The BIM Manager and BIM Admin will set up a series of workflows custom to your projects. So you'll have that option to select one of those from that dropdown menu there. You'll give your review a name, and then you'll click Submit. Then you'll be prompted to this final screen where you have the option to notify what reviewer you are sending this to.

And you can also CC in other members to notify them that this model has been sent for review. And then you want to give the reviewer a brief message on what has changed in this model update that you're sending for review. So some examples that I get is maybe I have Murray send me a new model. And they're telling me that they adjusted a certain duct in a certain section of the building. So this gives me clear and concise information on what exactly to look for when I'm conducting a model review.

So this is how you initiate the model review. And now, we're going to go over how to manage the model review as a project admin. So under the Docs module again, you will want to go over to Reviews. And when you click on Reviews, it'll take you to this screen here. And what you'll see is all of the reviews that have been sent to you populate here. We created a demo for this presentation. So we'll go ahead and click on that, that ACC Test there. And that'll take me to this review screen.

The first thing I want to do is click Start Review-- Initiate Review at the top right of the screen. This will send an email back to the initiator that their model has been received, and it's officially under review. From there, I would then download the initiators model. Review it against the comments that they sent. Once I've conducted my review, there's three options that I can do here. I can approve the model. And this will send the email to the initiator that the model has been reviewed and approved, and is now part of the Federated model.

I can reject the model. Or I can reject the comments. If I reject the comments, I find that's much more efficient to use as opposed to just rejecting the model. If I click on Add Comments, and I add any commentary as to why the model was rejected or what needs to be changed, and then I click Reject with Comments, this sends an email back to the initiator. And allows them to see what they need to change in their model so they can do a resubmittal.

KEITH PHOENIX: Thanks, Daniel. We have ACC fully set up. Let's talk about some of the tools that we're using to enable the BIM execution workflow. The first tool that we're using is the Coordination Issues add-in for Navisworks. It allows us to live link our Navisworks environment to Autodesk Construction Cloud. Allows us to view the latest Autodesk Construction Cloud uploaded models from that environment in our Navisworks environment, and automatically update those models. It also allows us to perform issue creation in our Navisworks environments that are populated into ACC. So the Coordination Issues add-in is a key add-in for this workflow.

The other tool that we're using is local NWF files. These local NWF files are also linked to the Autodesk Construction Cloud environment. They allow us to append in our local design files. So the latest versions of whatever our designers are working on currently in the office that have not yet been uploaded into ACC. So they can use it during their design process to make sure that they are designing in the coordination environment. It also allows us to do things like save viewpoints, save clash tests, and overall, just avoid data loss and inefficiencies.

With our tools defined, Daniel will walk us through how he is managing the BIM coordination process for the LAX Baggage Optimization program.

DANIEL GUEVARA: Thanks, Keith. In this section, I'm going to do a video demonstration on how we create a Navisworks coordination environment. So let's recap what we've done so far. We've set up our project in ACC. We've invited our team members. We've set up our folder structure. And set up an approval process. Now we're ready to start collaborating with each other in Nav itself. As Keith mentioned before, we're using Navisworks and the coordination plugin for Navis on this project. So you're going to want to make sure you download both of those, software and the plugin.

And then open Navis, head over to Coordination, Open. And then you'll be asked to fill out these three fields on this screen, Account, Project, and Coordination Space. I already have them filled out on the screen here. Once I select those three selections, it now pulls in all of the files available that have been uploaded to my ACC. So the files that we were just reviewing the previous section with all of the version numbers, who contributed the file, the last time the file was updated is all available to navigate here in Navisworks.

So now we have this, there's a variety of things we can do. We can set up a system with all of these files. Or perhaps you're only interested in a certain section of the building. So you can pick and choose what files you want to open. For this example, I want to open that TC19 structural support steel model that just updated. So I'm going to go and select that. And I want to see that with the conveyor that the structural steel is supporting. So I'll go ahead and select the BHS TC19 conveyor.

And I want to see what that looks like versus existing conditions, so I'm going to select these T100 models in the architectural model. Then I'll click Open. So what you see here on the screen now is my TC19 conveyor versus the architectural building shell, and the existing conditions that we scanned, which was those T100 models. Now that I have this environment populated, there's a variety of things I can do. I can start creating viewpoints and exporting XMLs. I can start taking my own notes, running clash detection, issue tracking.

And the best part of this is that I can save this as an NWF to my local PC. And so as long as I have internet connection, anytime I open up that NWF file, it's always going to pull in the latest versions from my ACC. OK, so we just set up our Navis environment. And now we're going to start going over clash detection. Before I go over the actual software execution portion of it, I want to go over a segment that is equally as, if not more important. And that is your plan and approach to running clash detection.

So what you see here is an overview of our entire system. Very large, very complex system in a brownfield setting. Lots of existing utilities in the way. At the beginning of this project, we knew we ran the risk of installation beginning when we are still coordinating. And that is true. That is something that is currently ongoing. We are still coordinating areas while we are beginning to install equipment. So we needed to make sure that our BIM schedule stayed ahead of our installation schedule.

So rather than running clash detection for the entire system at once, we broke our system down into sections that align with our installation schedule. So if you're running a large-scale project in a similar setting, this is something you want to consider before running into clash detection. So now that we have a plan in place, we're ready to start diving into the execution of clash detection. And in this slide, we're going to go over a video presentation on how to run clash detection.

So what we have on the screen here is our TC19 conveyor, the same environment we created earlier. And you see here on the screen, if I select this model, that is named BHS level 2 TC19. Now, you see there's a lot of obstruction-- clashing with this conveyor. A lot of interferences. If I click on that model, that is creating all of those clashes. A lot of existing conveyor. A lot of existing utilities. Existing ductwork, existing conduits. Some structural steel in the way as well.

If I select that model, that is the T105 scan model, which is we scan the building and we redrew all the components in Revit, and converted that into an NWC. So I want to see where these clashes occur, what these clashes are. And the frequency, the exact location, so on and so forth. And all this information I can obtain via clash detection. So that is what we're going to do next here in this section.

So what you're going to want to do is, within Navis, you're going to navigate over to your Home tab. And you're going to click Clash Detective. You're going to go to Add Test. And you're going to name this something unique in case you need to reference this later, it's easy to find. A naming convention I like to use A versus B. So in this case, I'm going to use TC19 BHS versus T105 scan. Once I named it, I'm going to go over to the Selection A window. And my Selection A is going to be that TC19 conveyor that I mentioned. So let me find it and select it here.

Then under my Selection B, I'm going to select that 105 scan file. Then I'm going to set a tolerance. I use 1 inch because that is our installation standard. And then I'm going to select Run Test. OK, once I run that test, you can see the Results window now has some data that I can filter through. So if I click on some of these clashes here, you'll see my screen will start to navigate me to where the clash exists. But it's a bit difficult to make out what I'm looking at.

So there is some isolation tools that help you get a better image of what it is that you're looking at here. If I use the Hide Other tool, it'll show everything that's clashing in it's highlighted geometry. The red being my conveyor, the green being the scan information. So you can see here, I have my curve clashing with an existing conveyor. I find it useful to toggle on and off between the Hide Other tool and using section views to get a better idea of what is actually going on here.

And if the Hide Other tool doesn't work, the Dim Other tool is also useful isolation tool, which will highlight the geometry, but it will show all of the other components surrounding in transparent polylines. So let's go back to referencing the clash detection approach that we mentioned. So here, we have area 11, small area of our building, of our project. I ran a clash detection tests of just the conveyors in that area versus the existing conditions. And that yielded 66 total clashes, which is not a long list. Very easy to navigate through.

Now, I ran a test of all of the system at once versus the entire existing condition files, and that yielded over 17,000 clashes. So 66 clashes is a lot easier to navigate through opposed to 17,000. Trying to filter through 17,000 clashes, very overwhelming. It's not efficient. It's very, very easy for important things to get missed. So before you run into clash detection, it's really important to have a strategic approach and ensuring everything is going to get captured.

So we went over clash detection, our clash detection approach. Now that we have some clash detection results to filter through, we're going to go over grouping clashes. So what we have here on the screen is some of the clashes from that large test that we did. The 17,000 plus. So I'm going to go to these results. When I'm grouping clashes, I'd like to filter by grid. Because I want to see these clashes listed by grid location.

So if I start clicking on some of these clashes here so we can get a better idea of what we're looking at, you can see here, the red item's a piece of my equipment. And the green item here looks to be the framing of an existing catwalk. So here, I can do one of two things. I can group by my equipment, which would be everything clashing with that one red item there. Or I can group by the catwalk. So I'll select the three dots there on the Selection A side. And now let's create a group. And that group shows everything that clashes with that one piece of red equipment.

Now, if I do the opposite, it shows me everything that green catwalk frame clashes with. So you can see here, it's creating an issue for me in several areas. It's clashing with my curve. It's clashing with another conveyor. It's clashing with an MCP panel. So now I'm going to give an example on when I would group by either my conveyor system, or B, my counterparts file. So let's start off with an example when would group by my conveyor system.

So what we see here on the screen in pink is our conveyor. This is approximately about a 10-foot section of conveyor belt. So it's not very long. And what you see here is a bunch of utilities going through this conveyor. I have an existing duct. I've got some plumbing issues, some conduits, some pipes, some sprinklers. Clearance issues with structural steel. All in a small section of conveyor. So in this instance, I would group by the conveyor to highlight everything that is happening in that one location.

The second option I would do is something like this. So what I'm going to do here is I'm going to fly over our system and show these two pipes that exist in the building. And they create issues for me in different areas. They block access to install structural support steel, create issues with conduits coming from NPCs. Clearance issues with catwalk and conveyor. It's just creating a bunch of issues throughout my system in different areas. So in this case, I would want to group by the utility so I can see everywhere that utility causes an issue for me.

And this is something we actually did run in our project. We did actually run clash detection and group everything by this utility. And we were able to use the results of that test to navigate a workable path for these two large pipes. So what we're looking at now in 2D is this coordination drawing that was driven by the results from that clash detection and grouping. So you see here is the existing demo path to the pipes we were just looking over. We highlighted the areas of concern.

And avoiding those areas of concern, we were able to find a new, feasible path of travel that worked for both parties. So in summary, grouping your clashes, it helps you consolidate all of your clashes to a smaller list and it'll help you lead to more feasible solutions by looking at items as a whole instead of every clash individual one by one. OK, so we've gone over clash detection. We've gone over how to execute clash detection. And now how to group our clashes. Once we have clashes groups, we're ready to consolidate and create an update issues with ACC.

So now that we have clashes grouped, let's create some issues. So we're going to go to our coordination inside of Navisworks. And we're going to click Manage Issues. What we have on the screen here is a seismic brace from our system going through a duct. And want to create an issue for this. So if I open up my Issues module here. And what I like to do is I like to draw or cloud where the clash occurs.

So I'm going to go to Review. And I'm going to draw a circle around this clash here. This is a structural brace versus an existing duct. I'm going to click Create Issue. I'm going to drop a pushpin here. So that pushpin is going to act like a little camera. And it's going to stay in my environment every time I click on this clash. Now, the title here, I want to name this something unique. All of our equipment on this project has a unique ID tag. So whether it be a conveyor, a catwalk, an NPC panel, a structural brace, structural support steel, everything has a tag.

So here, I'm going to name this E012. So this is structural brace E012. I'm going to make sure that the title of my issue has that name. So I'm going to name this seismic brace E012 versus duct. And this is really important because what depending on what name this, I can search for these clashes or these issues in my ACC with keywords that exist in the title. Which would make it very, very easy to start to find issues, pertaining to certain sections of equipment or certain areas of my project.

So carrying on, I'm going to go ahead and add a description to this. I want to ask Murray-- who is our HVAC subcontractor-- if we can relocate this duct, or if we can sleeve this brace through this duct. Just to initiate the issues conversation. Then I'm going to go to Assign. And I'm going to assign Swinerton. You can either assign companies or you can assign individuals. And then you can add watchers. So I'm going to assign Swinerton, but I also want to put in the team members from Murray, since this will be in their scope of work.

Then for location details, I like to use grid intersections that are extracted directly from Navis. Then you have the option to add in start dates and due dates in here. So I'm going to go ahead and put some dates assigned to this. And then down here, you have some custom fields, which we'll go over in a later section. But once I fill out all of my fields, I'll go ahead and hit Create. So what we have on the screen here now is a good list of some of the issues we created on our project.

And I'm going to demonstrate how you can use these issues to drive your BIM meetings. As I mentioned before, every time you create an issue, it drops a pushpin for you. So for example, if I click this clash here, this issue, it's going to navigate my Navis environment to where I drop that pushpin. And in here, you can see all of the information, the status, the type of issue, the title, the assignee. All the information that we previously filled out will get stored here.

And in our coordination meetings, we use these issues and we take screenshots and upload photos from our site as well to track progress on these issues. And everything gets saved and time stamped in here-- into the Issues module. And you can do this either in Navis or from the ACC from the website.

And my favorite feature here is the Comments Log. So we use this as a means of meeting minutes. So as we make progress on design efforts or site surveys, we communicate with one another here in the comments section. And it'll save who sent the comment, and when they sent it. And all of this information can be extracted and pulled into a PDF report, which we'll go over later in the presentation.

So spoke briefly on the use of custom fields and filters. ACC has a lot of stock options for you to filter all of the issues on your project. But it also gives you the option to add custom fields. Custom fields are very advantageous. They allow us to filter data by a project-specific parameter. They allow you to bring attention to specific data points. In our case, we wanted to bring the attention of everyone of what areas they should be focused on.

These are the custom fields that we use on LAX. So starting from top to bottom, we have priority as a filter, because we want to make sure the most critical items get seen first. We have has comments, which goes in hand-in-hand with the priority filter. Because we want to make sure that the most critical issues get seen, and the most critical issues that are waiting comments get responded to. We have phase, which represents the time or conveyor and catwalk will be installed. So this allows us to assign due dates by area for our project.

Then we have header steel phase, which is the structural steel timeline of when that structural steel will be installed on site. And then we have step. Which is inactive. Step, what we use-- we were originally going to have a step installation approach being uninstall this conveyor, install that one, then install this, so on and so forth. But we decided to approach the project in a installation by area approach, rather than a stepped approach. So the step filter is no longer in use on this project.

Now, you can leverage custom filters for coordination. So what I'm going to show you here is what are our coordination efforts look like before we begin to utilize custom filters. So you can imagine it's a brownfield setting, a lot of existing utilities, several different trades involved. A lot of work being done in the field. So as we found issues and they were getting resolved in the field, these dots here represent the locations these clashes were being resolved. Good that our team is doing the work. But the downside is that it's not collectively freeing up one space of installation.

So once we began to integrate the use of custom filters, this is what our issue management began to look like. So on the right side here, what I did, for example, I applied some filters I have. Clashes assigned to Swinerton with the due date of August 14 in header phase area one. This will show Swinerton, and this is everything they need to be looking at and prioritizing. So then all of our coordination effort began to look like this, where all of the clashes we were resolving, all were working towards freeing up the space of installation. So we don't accrue any scheduled delays.

So now we have a better idea of issues and utilizing custom filters, I'm going to give an example of the lifecycle of the issues for our project here at LAX. The first thing we do is we run clash detection. We group our clashes. And we create a new issue. We initiate the conversation of what needs to be done. Then we have coordination meetings, site surveys, design collaboration, so on and so forth until we arrive at a resolution. Now, if for whatever reason we get stalled, if we run into occurrences where we need approval from the city, we need approval from the customer, we need to conduct further testing or information, then we set the status of the issue to In Review.

Now, once we find a resolution that we know will work, it's been designed, it's been surveyed, it's been signed off on, we set the status to Pending. Once a week, we walk the jobsite to monitor and track progress. Then and only then do we close the issues. We make sure that the work that was done in the field was actually completed. And it was completed to the commitments that we have in the Issues module, and what is shown in our federated model. And that does a few things for us. It ensures that what we are seeing in 3D is actually happening in the jobsite. It keeps everyone proactive and accountable.

Many times on several projects, we go from steps 1, 3, and we skip steps 4 and 5. We don't do any follow ups. So having this lifecycle for our issues, makes sure that we're running an optimal BIM program. The last section I'm going to go over here is generating reports.

So we've had lots of technical discussion of the use of software and the use of ACC. But not everyone on our project may be from a technical trade or technical background. We may have project managers who want to see the status of their project. We may have construction managers and superintendents who want to see the status of open items on their job site.

So we can relay all that information to them with the reporting feature in ACC. So what we have shown the screen here is all of our issues within the Docs module. And in this example, I want to create a report of all of the issues in header phase one. So I'm going to clear my search. And then I'm going to apply some filters here. I'm going to scroll down to my custom fields. I'm going to type in header phase, I'm going to type in one. So now ACC has filtered through all of the issues in area one.

I'm going to select all of them. And then I'm going to go to Export. I'm going to click on Export Report. I'm going to name this Area One Issues. Hit Run Report. Going to download this report now. Once I've downloaded, I get this PDF here. So this PDF is very easy to follow, and it has a lot of good information. So you see, all of the titles are shown here in the table of contents with an issue number. All of the parameters that we filled out in the earlier slides are now shown in here. Everything ranging from model placement to who created this issue to the date this issue was created on.

All of the comment conversation history is also held here. Any screenshots or pictures that were taken for this issue, along with any images that were uploaded from your job site. And my favorite feature of this, too, is all of the comments get captured in here with the author and time and date as well. So all of your design efforts and everything that you've been doing to run your BIM program in ACC and in Navisworks can now be easily shared with others via the reporting.

So now I want to go over a weekly BIM meeting cadence. So we have all the tools that we need to run a good program. So how do we make sure that we take all of those tools and we actually end up at a good end result? So I'm going to give you a breakdown of what my week looks like to make sure my project stays on track. So on Monday, I have a coordination meeting that covers the future conveyor system that we intend to install versus the existing brownfield settings. And we use that environment that we build in there to drive the foundation for our Tuesday meeting.

In our Tuesday meeting, we have new utilities that we need to introduce into the building, but they do not have priority over the BHS that we are going to install. So we take the environment we created on Monday. And we introduce the new utilities on Tuesday, making sure that it doesn't create any more clashes of what we've done on Monday. So between the Monday and Tuesday meeting, we have a wide range of action items that we need to delegate to our site team. And then on Thursdays, we do a follow up site walk.

And on the site walk, we all speak in the language of ACC, where we all reference issues by their number. Everyone has their laptops open. For example, if someone wants to speak to me on clash number 1052, 562, so on and so forth, we'll walk over to where that clash is in the field. We'll make sure that the work was actually completed, and that it aligns with what coordinated in our model space. And if it does, then we close out those issues. So having a good cadence aligned with the good use of tools in ACC and Navis sets you up to run a very-- an optimal BIM program.

KEITH PHOENIX: Thank you, Daniel, for walking us through the BIM execution on the Baggage Optimization Program at LAX. I'm going to go ahead and talk about some of the lessons that we've learned throughout this process. in ACC it's important to establish a way of working up front, and also make sure that it's user friendly. We want people involved in this environment. Maybe not everybody is used to working in a cloud environment for BIM. So it's important to establish those ways of working and make sure that everybody has access. And that the way that you have your folder structure and your permissions set up is user friendly.

We want to maintain those file names, as Daniel mentioned a while back. If you upload a file and you replace it with a file with a different name, it's going to lose that link to that issues environment. We want to leverage comments. And when I say leverage comments, I don't mean just adding comments to issues, or using our comments filter. My favorite thing that Daniel mentioned about comments is that he actually uses the comments to maintain meeting minutes for each of the issues on the project.

So when he's in his BIM meetings talking about resolutions, or proposed solutions, or things that can or cannot be done with a particular issue, he's making comments as he goes in those meetings. And they are time stamped and they have the names of the people who have spoken on them and agreed to them. It's a very important thing that I think he is doing. Because in the past, when we're talking about change management for individual issues, sometimes you have to dig through emails, or you have to dig through somebody else's meeting minutes.

By leveraging those comments, you get to see everything associated with those issues in one single place. And it's available to everybody. We also want to leverage our custom fields and filters. By adding things like priority, comments, phase, header phase, we're able to prioritize the work. And we're also able to provide that for our other trades so that they can come into the ACC environment and see exactly what they need to be looking for any given date, and for any given priority. Which allows them to be more proactive.

So not just for our BIM management team, but for our subcontractors, and other trades that are in there. Everybody should be able to just go into ACC, filter through their issues and begin executing work. For BIM lessons learned, number one, BIM management is a full time job. Daniel is a mechanical project engineer for Vanderlande. Typically on a project like this, he has other tasks as well. But this is a full-time role to manage BIM for a project of this size. We want to define a BIM structure and cadence. Daniel talked about that quite a bit. Making sure that we have a good structure in place, a good backbone. But also a good cadence that is going to enable us to enable our construction workflows.