A Hitchhiker’s Guide to ArcGIS GeoBIM and the Construction Cloud

STEPHEN BROCKWELL: Good day, and welcome to Autodesk University. This is a Hitchhiker's Guide to ArcGIS GeoBIM and the Autodesk Construction Cloud. I'm Stephen Brockwell. I'm the senior product owner for ArcGIS GeoBIM at Esri and with me today is Anthony Renteria, who is the product manager for ArcGIS GeoBIM.

The session that we're going to do is going to first give you an overview of the business problem ArcGIS GeoBIM is designed to solve by integrating your geospatial services of Esri with the BIM360 or Autodesk Construction Cloud projects that you have. Anthony will give that context, and then he'll go into a user-centric demo of what the result is, how end users will experience the product.

I'm going to go into details about how to build a GeoBIM project, including talking about how to make sure your DWG in Revit files are well georeferenced, how to convert them and use them in ArcGIS itself for both 2D and 3D maps and scenes, and then how to build a project from start to finish with our ArcGIS GeoBIM project manager. Throughout, we'll give you help links and other resources that will make it easier for you to better understand how to go about this, and hopefully be self-sufficient.

We'd like to give you a little bit of a vision of the future that we see for GeoBIM. It's a big and growing kind of really enterprise. It's an association in Europe as many of us know. And also, there's going to be a live Q&A at the end where you'll be able to ask questions of us, and we'll be able to get your feedback on what your priorities are for the future. So with that, I'd like to invite Anthony Renteria to come along and give the project delivery galaxy a look.

ANTHONY RENTERIA: Thanks, Stephen. Hi, everyone. My name is Anthony Renteria and I'm the product manager for ArcGIS GeoBIM. Now before we go into the content, I just wanted to drop our safe harbor statement. We just want to make sure people are aware that we might mention some roadmap, or schedule information, or even some scope about our product that we'll include release and timing on, and just to be aware that items can change without notice. We're just advising teams to just be aware of those before moving forward and to our content.

So let's move into the galaxy of ArcGIS GeoBIM and how it connects to multiple systems. And so when we talk about ArcGIS GeoBIM, it is about delivering an innovative and easy to use web based experience for project teams, so that way they're able to explore and collaborate on BIM projects that may contain issues, and use that data from these multiple systems, but within geospatial context.

And we see this very applicable to both AEC firms and owner/operators that just simply want to work with their data from across these multiple systems, and build out these web experience to simplify the communication, and ultimately, collaboration between teams, and then even with external stakeholders.

And so at the premise of ArcGIS GeoBIM is it does sit in ArcGIS online services for this first release, and eventually will be in ArcGIS enterprise in the future. And it makes connections between our ArcGIS services, to documents, models, and files stored within the Autodesk Construction Cloud and BIM360.

And so when you start to look at the reasonings behind this product and for what's going on within this ecosystem today, or this galaxy really, it's these two worlds, right? BIM and GIS that are constantly being developed for projects, for assets, for facilities. And so what we've seen over the past couple of years with the Autodesk and Esri partnership is starting to bring these two worlds closer and closer together.

And so what we're seeing are desktop application users able to use web services from the other side of this system, and bring that directly into their workflows, in the case of InfraWorks, and Civil 3D using the Autodesk connectors for ArcGIS. And at the same time within ArcGIS, our ArcGIS pro users are able to access ACC and BIM360 content directly into our desktop application, and bring that directly into their workflows. So bringing Revit, DWG files and enabling, and creating new maps and scene services from that information.

And of course, we also have site scan for ArcGIS that has connections into the ACC and BIM360 services as well, for drone capture workflows that are very important to capturing realistic representations of the built world. And so what we've seen is these two large silos of information that our customers are burdened by multiple desktop and web applications just to view simple view of their project and portfolio data sets. And so they're trying to develop in-house systems that really are too costly to create and maintain for multiple project types, or even assets across their portfolio.

And so when we see this struggle with developing secure connections and effectively trying to link across systems it's just not something that's easy to scale across an organization. And so at the end of the day, while a lot of that's on more of the tech side of this, it's just being able to not be able to share an easy process view of what's going on within in the GIS worlds with your stakeholders, who just really need to understand insights into what's the process, what's going on, and be able to inform and provide better feedback into this process for project delivery and operations.

And so that's where ArcGIS GeoBIM comes in. It is about connecting these two worlds, and providing a simple point of access for project teams, and owner/operators. And so that way all teams are available to have easy, immediate access to project information across systems, while reducing the amount of data conversion in that process. But then also improving team collaboration by really just simply putting your projects on the map, and making that experience enabled for your teams to find the data they need.

But then at the end of the day also, is increasing stakeholder transparency. A lot of times building projects, and infrastructure, it's a complex process. And so this is to help communicate, and help our teams really understand what's going on across their projects, and ultimately extending into their portfolios of projects. And so what I wanted to share with you today is there are two new item types that we use to manage within GeoBIM. It's the GeoBIM project, and the GeoBIM apps.

And so one thing I wanted to share with you is when you create a GeoBIM project, it doesn't necessarily mean you're making only a single GeoBIM app. You may have multiple GeoBIM apps within a single project. And so what I want to showcase for you today is just what one of those app experiences could be like in this world, and then what I wanted to share in this app experience view of GeoBIM is all the different levels of connection. Not just across a single project, but a portfolio of projects.

So let's start with this end user app experience within GeoBIM. Now, what you're seeing is that job application. We're zooming into this map experience where we've automatically already created some polygon features that have been generated from model files stored on ACC or BIM360. And so as you can see, as I select a polygon in the map view, there are links associated that open up on the right side within Autodesk Forge.

And so these are those views into roadways designs, or progress of the documentation. But being able to see the location of these documents and files as they're being generated, and see the live, up to date information on right. Now, we're automatically generating these links to these polygons for users, but also doing it for issues, too.

So we're mapping out issues as points that connect back to the information stored within BIM360 and ACC. But also, how this ability to flip to a 3D version of the scene. So you can use both a map and a scene in this experience, and be able to move around, and see your projects within context, and then dive into the details of each.

So in this case, I can also link to a shell or a representation of what the conceptual element is going to be for this facility or building, in this case, a hospital. And then open up the associated Revit model for that building and see the up to date progress, because we're making links that are dynamic, and will show the most recent version within that linkable selection.

And so I'm not limited to just one building. I've now moved into another building where we've actually created what we call in GIS, a building scene layer, which is element for element GIS features for the building systems. And in this case, if I select a feature in that GIS view it automatically opens up the highly detailed model and takes me to that digital model's element in the same place so I can verify documentation.

And we could do that with IFCs, like in this case of the parking structure example, or we can make that same connection with utilities. So bringing in Civil 3D DWG pipe networks into, and creating GIS symbols for 3D representations, we can also begin to make these links and connections.

And so that way yes, you have this representation and this realistic context that also takes you into the highly detailed modeling information, whether it's documentation, or the features themselves have been built into geometries. And of course this extends to transportation, but also we can then move to another location altogether. So moving into another project development in our portfolio.

I was previously in the Denver area, and now I'm in Southern California. I haven't left my single app experience, but I'm now moving into this place where we're bringing in rich mesh data that's been generated from drone capture, and site scan for ArcGIS, and then overlaying that with a polygon of a new development, and then being able to also incorporate some of that structural information, and piping systems that are going to be intended to be built over time.

But we can also connect that information to progress photos as the construction is being progressed through the schedule. And then ultimately, even add in as another aspect, reality capture meshes that bring in a mix of both our mesh data captured from drones, but then also overlay some of the systems directly in GIS that take you back to that rich BIM documentation that's been generated through that process.

And so what I'm trying to provide for you is this really quick example of many of the ways that you can begin to quickly link and make connections between your data, and then start to extend this information out to anyone that has a web browser. Now, the other aspect to take into account here is the ability to create dashboards. In the early part of this the past application I showed how you can map out, or we can automatically map out, issues into points and bring that into these experiences.

Well, those points are also very useful for issues because then we can connect that into our dashboard experience automatically, so we can extend this user interface out to your project managers, to executives that just need to understand what's the progress of the issue coordination within your teams, and understand what's still open, and what needs to be resolved.

So with that, I wanted to give you that quick rundown of what's possible. And so now that I've given you an idea of what you can do in GeoBIM with this end user experience in the applications, I'm going to hand it back to Stephen so he can give you an idea of how do you build this now.

STEPHEN BROCKWELL: Thanks very much, Anthony. So let's get started on how to make that application that Anthony was showing you, and the sort of fundamentals. I'm not going to create something as extensive as Anthony did. He was really trying to show you a really good view of how the product actually works. I'm going to give you a much more simple demo to help you get through an understanding of how it actually is constructed.

So there's a few parts to that. The first is some concepts that are important for you to understand. That includes the sort of services we create and use to manage it, how it's constructed, the elements. How to georeference your data, and how that works, and how we like to see it. There are other ways of course, but there are a couple of ways we really recommend.

Give you an overview of how to use ArcGIS Pro to pull in the data and create web maps and web scenes that you can then share through GeoBIM for your users. And then finally, the steps of creating GeoBIM projects and the apps that result from them.

So conceptually, let's walk through a few user scenarios to better understand what the intent of GeoBIM is. So let's look at a mid-sized AEC firm that's trying to do some kind of interesting GIS applications that have a project focused approach. So an account, which is a sort of first element of a GeoBIM project really, it's the thing that connects you between the Esri system, and the Autodesk system.

The first thing you need to know is that with that account you can identify one or more projects, and in this scenario, a small firm is really defining a GeoBIM project that's going to talk to an airport design project, and a city water construction project. Those are the two they're working on, and they've got two GeoBIM projects for that use web maps and web scenes, mesh, and other imagery files, and so on. Utility networks and whatnot. And these are the two GeoBIM projects they're going to define.

A larger firm might want to have different projects with different views based on who is of interest, particularly if they've got multiple customer projects going on in their accounts. They're probably going to want to have those separated so that information is not easily visible across organizations. So they might want to give isolation to that. They do that by having a GeoBIM project that points to one for one customer, or three, or any number of projects for a different customer, and so on.

So it's possible to set GeoBIM up in this way to create one project per project, but also one GeoBIM project for many Autodesk Construction Cloud projects. You know, GeoBIM is not intended to be used only in the AEC firms. It's also very useful for infrastructure owners, these airports being one of them.

This model is actually from an airport that we've worked with extensively for a number of years that has what we call, or they call, an asset information model, which is essentially the as constructed documentation for their site. And then of course, they've got many projects, up to 100 at a time that are in different stages. Design, pre-construction, and so on.

And what they might want to set up is a single GeoBIM asset management GeoBIM project that is only talking to the asset and information model. But they might also want to have an overview project of all of the in-flight projects that actually has the ability to do comparisons with the current asset information model.

So this GeoBIM project here would talk to all of these projects, and additionally the asset information model. So GeoBIM is flexible in that way. It allows you to have one or more GeoBIM projects-- I mean BIM360 or ACC projects.

So just an overview of some of the technicalities that are actually important. When you create a GeoBIM project, you're creating a number of different services and items from an ArcGIS perspective, and I think it's important that you understand just some basics about how it works.

So when you create a GeoBIM project, you have a GeoBIM service. In there we store points for all of the issues that are in your BIM360, or Autodesk Construction Cloud, document boundaries that are calculated from your Revit and DWG files, and then BIM project boundaries that are actually created from the aggregate of all of the documents for a particular project.

We also have metadata for links, jobs where we do reporting, and accounts as I said, that link your system to the Autodesk Construction Cloud. Now, one GeoBIM project will have many apps. And those apps actually start to bring in other ArcGIS artifacts that may or may not have GeoBIM specific data in them. So I could have a map of utilities, or a map of something else, or a web seen with meshes of ground cover, or scans of a project at a certain stage, and to that we add our feature services.

So you get a complete map, and you'll see how this takes shape in a moment. So it's important that you make your referencing as good as possible to make sure that these make sense, and that you keep track and take care with the custodial sort of relationships of all of these different items.

All right. So now let's discuss how to go about georeferencing your data to make sure that it works with ArcGIS GeoBIM. OK. So given those conceptual underpinnings and understanding how at least basically we store information, the key thing is we store document locations as little polygons, and we store issues as points that are calculated based on their location within those document boundaries.

So to do that, we have to have referenced CAD and Revit files, and for the next few minutes, I'm going to describe how to go about doing that in a way that works as much as possible with both GeoBIM and ArcGIS probe so you can get the best of both worlds.

Let's start by talking about how to georeference Civil 3D files. The first step is really to use a standard well-known ID for a coordinate system. The vast majority of Civil 3D users will use a well-known ID for a coordinate system. It may not be one that is shared with Esri.

So you want to make sure that you have a coordinate system to find, which we've done here. This is California State plane. And then we didn't know from the properties in Civil what the coordinate system well-known ID is, but we can find that out from the map, map CSS assigned command. So that's 2229 and we find that, yes, that's an Esri coordinate system that we can use.

So that is going to be fine. If we do that GeoBIM at least will go through and find those locations and calculate the document boundaries based on that, and you'll be good from a GeoBIM perspective. Now, if you want to have the same coordinate system sort of set up for both GeoBIM, and ArcGIS Pro, and perhaps you have a custom coordinate system that you want to use, what you do is you create a PRJ file.

I'm not going to go into the details of that here. That's really well described in the documentation, which is available here. And you go to that Esri CAD PRJ file, which simply defines the well known text essentially of the coordinate system you're going to use. And then across the board pretty much, as you'll see in a moment with ArcGIS Pro, everything will read it. We will read it, pro will read it, and everything is good. So that's actually the recommended approach for CAD files.

Now when it comes to Revit files there are really two approaches we use. One, is to use the actual project address on a map. And that's what you're seeing here, that's a very simple way to do it. Different geographies use this more or less. It does require, in general terms, that your survey point and project based point are located within a reasonable distance of the model so that that geolocation is anchored at the correct spot.

It's used also for weather services and those kinds of things to do certain kind of environmental calculations, and those kinds of things. So if you're using that, we can in GeoBIM actually locate the model that way. It's not the most efficient or accurate mechanism we can use, though.

So a more comprehensive approach really is to use the shared coordinates workflow with a PRJ file. As we described in the PRJ file, if you are using shared coordinates, can be one PRJ file that applies to all of them. Essentially, you define your real world coordinates in Civil 3D. You correlate those with the Revit model, and there's a workflow to do that, and I'll show you that in a moment.

And then you define an Esri PRJ file that has those, you push that into your BIM connection, you know, so that pro and we can use it. And it also again works for custom coordinate systems. Again, it's really important that you keep the survey point and project base point close to the model for this to work effectively. So let's take a look at some of the details of how that happens. So these are files on the GeoBIM's side that have been located nicely.

So this one, the hospital had an interesting sort of orientation. So the true North was kind of oriented to a certain angle, and then the other files have other coordinates. Now in Pro if you don't have a PRJ file these are going to end up in the ocean somewhere, where they're really-- it's kind of meaningless location for them. So what we have to do is to make sure that we have something consistent, and this is where that PRJ file comes in, and that shared coordinates workflow.

So for shared coordinates, and I'm giving a very simplified view of this, but I basically define a correlated point between Civil 3D and Revit. So here I've defined a coordinate in Civil 3D, tracked its coordinates, made sure I have them. I've got my survey and project based point here. I'm going to unclip so that I can actually make sure that the survey point moves with me when I do the movement of the point, and that's really important.

There are some practices where that might not be desirable, but this is the way GeoBIM does it at the moment. So then given that, I define the shared point at a location using the shared coordinates workflow, essentially. And that is the same point that is in the Civil 3D space. I basically get those coordinates in there, and I say OK, and then we're all ready to go. So now because my survey point is unclipped it moves with the model, and everything will be nicely oriented.

Excellent. So now we've done the work to get our DWG and Revit files properly georeferenced so that both GeoBIM and ArcGIS Pro can use them. So let's walk through the process of how you get, particularly web scenes we're going to focus on, but the process for web maps is very similar. Get CAD data files into ArcGIS pro, and publish them to ArcGIS online where we can consume them in ArcGIS GeoBIM.

So one of the first things to know about is the relatively new BIM connection, BIM cloud connection inside ArcGIS Pro, which is an extension to just the catalog tool inside ArcGIS Pro so. I can create a new BIM connection, give it a name, and authenticate, of course. I have to give ArcGIS Pro explicit permission to use the data in either BIM360 or the Autodesk Construction Cloud.

I get a seamless view of all of that data in this list here. So that's a list of all my projects. Then I go into the projects and I navigate to the files. Now, what we support in this plug-in here is of course IFC, Native read now, Civil 3D and other DWG files plus Revit files. So those can be downloaded into the project directory, or they can be downloaded and added to new scenes, completely up to you. I'm just downloading them for now.

We did this we actually also had the PRJ files as I mentioned earlier, in those project directories so that the coordinate systems come in correctly. Without the PRJ file you're going to have the situation we showed you earlier, where the file will go into somewhere in the ocean, or some relatively unpredictable place. Whereas with this case, just literally by dragging and dropping the models, they come in right on in this particular web map.

And I've given you an indication as to where to go in the docs to get more details on this. Now, once I've sort of downloaded and started to create web maps or web scenes with those CAD and Revit files, I can actually use two particular workflows to convert them into useful tools within my web map, and web scene, that can then be published easily to ArcGIS online.

For Revit files you use BIM file to database and this will take the input file, and create a feature data set inside a geo database, that you can then use to publish other byproducts, which we'll go into in a minute. If you brought the data in from the BIM cloud connection your coordinate system will be automatically detected, because you defined the PRJ file, and you stuffed it up there with your other files in your project.

Essentially, the same process, but a slightly different workflow. CAD to geo-database does the same work for CAD files, including extracting some more features out of the Civil 3D files now. And that includes some pipe networking, and also some survey point information that's being extracted in native form now, rather than just as CAD entities. Again, for the DWG files, that same PRJ file that you use at the project level will also define where those go.

So now that we have downloaded the files, we've added them to ArcGIS Pro, we converted them to geodatabases that can then be used and treated as information, in particular for the building scene layer, which is something new. It's recommended that you do for a Revit file that has particularly building information in it. It gives you a lot of information that in the web, we can use to do some navigation. Anthony would have shown you the building explorer, where you would be able to navigate floors, and these kinds of things.

So to do that, you use the building scene layer package, and then once you've created the building scene layer package, you upload it. So I just create new content. I go search for the building scene layer package. I upload it. And this workflow, in the last couple of releases of ArcGIS online has improved incredibly.

It's as simple as you see here. I just go get the building scene layer package, and I add it to my content. And after a period of time, it takes a couple of minutes depending on the size of it, you can see it creating a service. I've accelerated this, but it works really, really well and the results look excellent.

So that's how basically to use pro to define and build your data sets that you're going to use, and now we're going to look at the GeoBIM project manager to see how to use those maps, and the data in BIM360 to create GeoBIM apps that your users can view.

OK. So we've sort of got an introduction to how GeoBIM works from an end user perspective, we've kind of gone over some of the key concepts, the item types we create, the feature services we create to support the data we create from your links, and so on. And we've figured out how to use pro to create content using Revit and DWG files.

So now let's use the GeoBIM project manager to create the apps that Anthony was showing you earlier. So just as a starting point, you can access GeoBIM from the app launcher in your ArcGIS home page when you have a license assigned.

So it's assigned via a user type extension. GIS professional standard and advanced users get it automatically, and other users like creator roles and so on are assigned it by their administrator according to what their enterprise license agreement establishes. Anthony will go into more of that later if you have questions about it.

So we press on that, and then we go to GeoBIM where we do our work. And this is the GeoBIM landing page, which gives you a list of all the different projects you've been using. You can tell we're doing a lot of testing here, but you know, I can filter on the ones that I own.

I can go back to all, I can look at the ones that are shared with me, and so on. And what I'm going to do is create a new one. All right. And I'm going to give it a nice image, because it deals with the wide range of space. It's actually a project that's going to be in the Denver area and Southern California.

And now I'm creating that project. I'm creating the services we use for it. And I get my first page, the accounts page. And this is where, as I mentioned earlier, you create that link between GeoBIM and its GeoBIM project, and the information in your BIM360 system. I have to log in of course, and authenticate. And it allows me to access different data. And I'm going to choose the projects that I want.

Now this is where if you remember, I said we could use all projects. That's something we can do. So if I'm an owner operator and I have 20, 30 projects going on, I want to do a comparative study, a portfolio kind of view of things, I can do that by saying all projects.

Or I can actually choose the two that I'm interested in for specific customer, a galactic customer, and there we go. So now that's how simple that is. I've got an account set up, so that I'm linked to two specific ACC projects.

Now I go to the Tools page, and this is where the magic of the georeferencing happens. So what I'm going to do is I'm going to just give you a very quick overview of the different options, but the first step is always to locate engineering documents. And here are some settings that we have. As I mentioned earlier, if I knew the well-known ID and it was a single well-known ID, in this case it is not, but if I didn't want to go and edit all my DWG files to make sure I was using it, I could actually enter it here. That's a possibility.

The other thing I can do is I can force synchronization. What that means is when you run the tools page, when you run the script that goes on in the background for this, it actually does a synchronization. It might be that you made a mistake in the well-known ID, but that nothing on the BIM360 side has changed. If that were the case, you would say force synchronization, because you want to overwrite all of the files you've got now, because there was a mistake made in it.

We perform a degree of outlier analysis to try to identify some documents which are clearly not in the correct location, so they're georeferencing is wrong. I'm not going to go into that for the purposes of this demonstration. When we locate issues we do some similar things. We use the boundaries that are generated from the locate engineering documents step to locate issues. Now, in some ACC. And BIM360 projects you don't have to have a document you can have project level issues.

Those can be georeferenced using the project address if it's been entered, and the force synchronization also applies. So now the other thing we can do at the end of that process, once we got our documents and our issues, is to create BIM project boundary. So what that means is we create the aggregate boundary of all of the documents georeferenced in that project, and we create what we call a project boundary that you can use after that.

And that is different options for this. I won't go into the details again here, but I like merged document boundaries. They tend to look best to my taste. And they're we're ready to go. So now we're going to run this tool. It runs in the background, and it can take some time. It can take five minutes, 10 minutes, or longer if it's a very large project, or a very large number of projects.

Now we can start to see some results coming in here. So given that, we're going to leave this, and going to find some links. OK. So as I mentioned when I was sort of introducing the concepts, links are made ultimately between features, and the BIM360 or Autodesk Construction Cloud documents.

So let's pick a map here to make this relatively easy, conceptually, and go about defining some links. So first off, I can define links pretty much with any feature, and to any BIM360 document, or ACC document. So if I have PDF files, if I have images, anything that is stored in BIM360 can be linked to a feature. So let's pick a pretty obvious feature, here. This one. And let's create a link for it.

All right, we have a bunch of PDFs. I can grab that, I can grab a DWG, I can grab another one. I can grab all my PDFs for example, that are maybe they related to that building, or it doesn't really matter for the purposes of this demo. But I define those links, and there we go. And of course I can preview them just to see what the content is, and that goes for Revit files as well.

So that is how easy it is to define a link. And that link is static, so in other words, it's not tied to the attributes of a feature. It's saying, OK, this file, this PDF file or whatever, is linked to this specific feature. There's also link rules, which is somewhat different.

And in that case, I can take anything that is in my model and as long as it has a URL available in the attribute table that links to the BIM360 side. And in this case when you use ArcGIS Pro to pull data in, you do, you have the shared view that actually provides the URL to the document that was the source of this information.

And I can go and link that like that for my pipes layer. I can grab other features and grab them as well, multi patches, any feature that has come from that source of information can be linked. Let's see here. And there we go.

So this happens, and you'll see here this is an interesting feature of this. So not only have I linked this particular little building to some PDF files now, but by rules I've actually linked it to its source document. Not only that, but I've linked it because that link is from the data, it links directly to the actual instance geometry.

So I can actually zoom in and correlate my selections here. This is very useful, and Anthony I think has shown it in the user side of the app. So that's links. That's how to go about those, and it works essentially the same way in a web scene.

Now, when it comes to this part, I mean I guess I don't really need to create new apps, new links to have apps that use web scenes and web maps for now. So creating an app is super simple. There's two types.

There's a dashboard app, and just a viewer app. I'm going to create a viewer app first. We get a template here, which is just schematic. It's not really meant to be interactive. I can choose different themes for look and feel of the application if I want to. I like the dark theme. And then I select my map, and that's the one I was looking at here.

And I add my project layers to an image in that very beginning. When you take a map that you've created from CAD files, and utility models, and everything like that, you actually end up-- we add our services to it. So let's just save that to a copy that we can reuse. That's what I meant about renaming them. You want to be able to reuse your maps in other applications.

Now let's grab a scene as well. And this is a sort of joint scene that I've developed. Cool. And the same operation takes place. So in 3D web scenes as well, you can actually have your scene have its layers from GeoBIM, the documents and issues layers.

OK. So I've defined both the web map and web scene, and I am able to navigate around and those kinds of things. And you'll see what the result looks like in a moment. I have a number of tools that I can turn on and off here, and some of them are very specific to and just standard for Experience Builder.

Others are specific to our application and we allow you to have 3D widgets, which we'll explain in a moment. Time slider, which we're not going to get into today, but it allows you to define and visualize projects over time. And the ability to create new issues, as well.

So I saved my project. And then I run it. And there you have it. This is how a GeoBIM project is transformed into an app. It's meant to be very simple.

It really works in concert with ArcGIS Pro and with just the ArcGIS online platform, web maps, and web scenes. I can toggle between them. It's really easy to do that. And then my navigation. This is one of the referenced files that we have established. So this is really quite easy to do.

Thank you, everyone, for joining us for a Hitchhiker's Guide to ArcGIS GeoBIM and the Autodesk Construction Cloud. I'd like to thank Anthony Renteria for helping us get this content created, and also Aaron Cheuvront, the product engineer on ArcGIS GeoBIM for particularly the work on the Revit and Autodesk georeferencing preliminaries. Have a great Autodesk University, and we'll talk to you soon.