Never Miss a Beat: Track Everything with Assets and Equipment Management

ROBERT SMITH: Hi, everybody. Welcome to AU 2024. This class is about Tracking Everything with Assets and Equipment Management. Before we get started, we are going to show the Safe Harbor Statement. This presentation may contain forward-looking statements about our outlook, particularly around the product.

These forward-looking statements are being made as of today. If this presentation is being viewed afterwards, we have no obligation to update or revise them. So any statements we make regarding future development is not intended to be a promise or guarantee. They just reflect our plans of what we have today.

So about me. My name is Robert Smith. I'm a Senior Product Manager here at Autodesk. I've been with Autodesk for about seven years now in a variety of roles, but with the ACC Assets team for about three. My previous experience, I've always worked in construction and construction tech, so for about 12 years and been in a variety of roles.

In construction, I worked as a project engineer as you can see on site. I had the opportunity to be on projects from start to finish. So only on a few projects, but on those projects for a long time, particularly aviation and education.

In construction tech, I've had a variety of roles from support, QA, customer success, consulting, and now product in both enterprise and the startup space. And I'm based in Portland, Oregon. As you can tell, I'm a big Dodger fan. The new son, we both watch [INAUDIBLE] 50/50 celebration. So we're quite excited-- or you can tell I am.

And then that's me quite some time ago, eager and bright eyed, probably second day on the job site. So there were a lot of if-only-you-knew-what-came-next. And I'm a first time AU speaker, so this is my first time doing a presentation. Been at AU several times in the past, but this is my first time giving a presentation. So I'm excited to share with you.

All right, our agenda today. So we're going to start with one of the harder questions that we have to answer, which is what is an asset? It's a question that's if you ask 10 different people, you'll get 10 different answers. So aligning on a standard definition for us before we continue too far in the presentation is going to really give us a framework of how these things all follow after.

Next, we're going to talk about Asset Tracking in Construction. So why is tracking assets important? What type of value do they provide? And what are the problems that it's solving? After that, we're going to talk about our product assets within the build and our vision and strategy.

So how do we recognize these problems, and what is our plan to tackle them? We'll talk about where assets is today, where we've been-- where we are so far along that journey, and then we'll jump into a live demo of the product itself. So let's break it down. What is an asset?

And whenever I talk to one of you, one of the first questions I always start with is, what are you tracking? What are you using assets for? What is your primary purpose? And it's always a little different. It always kind of amazes me to see the different use cases we see for assets, and we have asset capabilities in several of our Autodesk products.

So across the different teams, we all came together to just align on a standard definition. And the standard definition we came up with is very similar to the ISO standard, actually. But it is, "An asset is any physical or digital component within a built environment that has potential or actual value tracked and managed throughout its life cycle from conception, design, and construction to operation and maintenance." That's a long sentence with a lot of details very carefully crafted. So let's break it down very simply.

Let's take a look at that statement again, and let's just look at it from a noun and verb perspective. So when we look at what an asset is in this statement, it comes down to any physical or digital component that has potential or actual value. If we break this down into two words, the way I would summarize it is, it's important objects. It's objects that you care about because they have some type of value to you. If we look at the verb of this statement and what you do with these assets, they're attract and managed.

And what that means is that they're status driven. So these assets, all you need to know the status of them throughout the project. And it has centralized data. As you're managing these assets, different data is coming in, and you need to be able to centralize that.

But I don't want to dismiss those phrases. The prepositional phrases provide important context. So if we look at those to give some details to this, we look at within a built environment. All right. So these assets are a part of a built environment, meaning they do belong to a project, or are a project themselves, in some cases.

In the next phrase for Attract and Manage, throughout its life cycle conception to maintenance. And when we think of that, we think of the centralized data and everybody interacting with it. There's a variety of roles and responsibilities and different hands that are interacting with assets at different times. There's different sources of data. So whether it's coming from submittals or specifications, whether it's field team information, there's information in different people interacting with this asset data throughout its lifecycle.

So ACC assets and asset tracking, we look at some phrases in here and we take, again, the noun and the verb. An asset is tracked and managed. So we take that, we can summarize it into asset tracking as a feature and functionality. And what asset tracking does is, it can be a variety of different objects. For us in ACC assets, in particular, we see objects like movable equipment, forklifts, those are lifts.

We see system components, fan coils, air handlers, pumps, items that really make up a building. We see building components more and more, which is concrete, pieces of steel, doors. It could be any part of the building that you're installing, or even project areas, lighting zones different phases of the building that need to be turned over. All of these are being tracked as assets.

And they're being tracked throughout the project. So they're starting from requirements. Even before design starts, they could know what type of assets they need and they need to start tracking it before design, before the first model is drawn, before the first sheet is out. All the way to handover. And if you noticed on the phrase in our definition, the asset definition at Autodesk is two operation and maintenance.

So it actually goes even a little further. But for asset tracking in that information being gathered throughout the project, that's our big focus on ACC assets is this space here requirements to handover. We do provide some functionality for operation and maintenance, but it's minimal, and that's not our target area. Our target area is released from the very conception of this asset, providing it to handover over to the owner.

So asset tracking. So regardless of how it's being done, traditionally, today it's being done, and it is being done in a variety of different places. So you may have inspections about a fan coil. You may have issues on a fan coil. You may have RFIs on a submittal or a fan coil may have submittals.

You may have cost items. You may have schedule. There's all sorts of information about this one fan coil, and it's stored all over the place. It's stored in one drives and emails and spreadsheets, in other systems, other softwares. If someone wants to know what is the status of this fan coil and what is the information about it, they could find it, but they would have to go to so many different places that it becomes very, very difficult.

And it's very difficult to just know where is this item today. Now, this causes a lot of problems. And some of the industry problems that we've seen based on research lately is that 87% of owners report that their projects are coming under greater scrutiny. And so when things come under greater scrutiny, you need to have access to the data quicker.

When your data is fragmented, and it's in several different places, getting that data to show what is the status of this item and what is the information associated to it, becomes very difficult, which leads to the next problem, which is that over half of general contractors reported problems getting off the job in at least a quarter of their projects, which means that at the end of the job, this data is so fragmented, they need to go back and then they need to reorganize it. They need to audit what's missing and what's not. They need to go back and do a lot of work that could have been done throughout the job.

And, lastly, 72% of firms take projects have taken longer than expected, in part, to this problem where all of the data is fragmented, and we need to find ways to get it together. Now, I'm not saying asset tracking in this problem is the cause of all of these different things. But it certainly is a subset and can contribute to bringing some of these numbers down.

So what if we, instead of having this giant bucket of-- or no buckets, instead of having many, many different buckets of information in several different places with no clear status, what if we provided a container of this information? A single place where you could go to that fan coil. You could see the submittals about it. You could see the RFIs about it. You could see the forms, issues.

Everything is centered on this one object, regardless of who's interacting with it. And we gave you the status of this. So you know exactly when this item was specified. You know when it's on site, when you need to send people to go install it.

You know what objects need to be commissioned that day. You have everything you need about an asset in one single place. And that is the product of ACC assets in build.

So now let's jump into the Vision and Strategy. So with assets, we provide that centralized place. And we're in the Autodesk Build Platform, which is great because the platform provides all of the other information that we need to centralize. So it provides the forms for the field collaboration workflows. It provides the inspections for installation, quality commissioning, the reports, the schedule connections, the RFI submittals.

All of the data about this asset is living in our platform. And assets is the place you can aggregate all that data. You can take your data from model files and put it into the asset. You can take this asset and draw it on a 2D sheet. At the end of the job, all of your information is centered on this object, and we provide you with the status of this object, so you know exactly where this object is, what phase of the project it's in, and what's its life cycle, and you have all of that data readily available to you.

And the ACC vision, our vision is pretty straightforward, and you'll notice a lot of the definition that we talked about baked in here, but our vision is to deliver an industry-leading asset tracking solution that enables project teams to track, visualize, and act on centralized data on any construction components. And you'll notice track and centralized data are very similar to the asset definition, but we added in two other verbs, Visualize and Act, that really make up our vision and kind of separate it a little bit from the definition. And what we mean by "visualize" is our solution at ACC Assets focuses on tracking. And when you start tracking hundreds, thousands, hundreds of thousands, potentially millions of objects, you need a way to visualize those statuses. You need a way to know which information is where.

And so our tool, also our Vision is to be able to easily see the status of objects anywhere you need to see them. And not only that, but you need to act on the data. So you're putting all of this information into assets. You're putting all the information into our platform, and you're able to view it. But as you get data, you need to know what to do next.

And that's really part of the vision is providing you that answer to the question before you have to ask the question. And you'll see that reflect a little bit in our strategy. So our vision doesn't really change year to year. Our strategy, we do revisit from time to time. It hasn't changed too much, but I'll give you some insight of what we have.

The first one has never changed, and it's not going to change any time soon. The first thing that we strategize to really execute on this vision is to create and manage source agnostic containers to capture, connect, and centralize information. And source agnostic container, a little bit of a confusing term, what we mean by that is we don't want to be reliant on any one source of information for this asset. We need a container that's separate from these other sources that you can connect to and that can connect to any other type of information.

For example, if you have a model file, that model file may contain important information about that asset. It may be a subset of information. It may be quite a bit of information. And that information should live with the asset. But that asset shouldn't be reliant on the model object.

That asset also needs information coming from field. So it needs to have install dates. It needs to have any other type of information that comes in, field serial numbers, model numbers, any type of verification that goes on out there. It also needs to have information that's put in manually from other places.

It also needs to have information coming in from RFIs, submittals. So the container really provides a way for us to take in information and send that information to provide that connection point between the model, the sheets, and the other information in the project. And we're going to continue to have that as our strategy because this is such an important part of taking an asset and the object and connecting it to the rest of the Autodesk platform.

Next part of our strategy is connecting assets to the field-based workflows for streamlined processes. And what we mean by field-based workflows is-- one of the most important parts actually is making sure that the asset information and the asset workflows you need to do are available offline in the field. Because the office side usually all has internet access, and they can input this information, they can view the information, act on it in the office. But in the field, one, the building isn't built. It may be underground.

The assets you're acting on, we can't rely on a stable connection to really act on these things. So we need to focus on making sure the field teams are enabled to do what they need to do. And we need to make sure that our product is easy to use for field users. We don't want to make a product that field teams that come on and off the projects that are constantly switching hands are having to be trained or find cumbersome to use. We want to make sure that they have that information readily accessible, so that they can do their inspections, they can log their issues, all within the app itself.

And, lastly, the next part of our strategy that we're executing this vision on is reporting actionable and persona-based information. And this goes back to not only giving you information about your assets, because when you have analytics, that's amazing. You get these analytics. You get all of this data going on in your project. But once you have the data, you need to know what to do with it.

So we want to be able to not just give you that data, but to also say, you have this data. Here's what you need to do to move this asset from the status it's currently in to the next all the way over to handing it over. So these are the three strategies that we focus on as we develop this platform and we build up the strategy and product that we're really focusing on executing near term.

So I want to jump into where we are today. So, today, we do have that centralized information. We have created that source agnostic container that contains all of the information for everybody to access. We have provided connections to both Sheets and Model files, so you are able to visualize the status of your assets in both sheets and model files.

And we are providing progress and reporting. So we do have a variety of different ways to access progress and reports from Power BI, PDF reports, Excel, as well as some in-app reporting as well. And so if we take a look at where we are today, we have this connected and unified data. We have an object, and if you select an asset, you can view all of the data that came in from it.

Whether it's from a model file, whether it's from Excel. You have all the information readily available as well as any of the information associated to it from the platform, like forms, issues, submittals, RFIs. And you also are able to see who has changed information. So we're keeping an audit trail to make sure that your information is accurate, and you have everything you need to know about it.

The next thing that we do provide today is that connection to Sheets and Models. So you can see, if you have an object, you can draw it on a 2D sheet so that you're getting a visualization of all the objects that you care about in your project. And you have the same access to the same information whether this information came from Model Excel.

And the same thing with the Model file. So you can actually open this asset in its model file and view it in its status in context with everything else as well as have information about it, including its references. And in the model file, these are also available in 2D.

We know that's the primary way field teams like to operate is on 2D sheets. It provides a lot more installation and a lot more context. So having that information available on 2D views within the model is really important.

Our newest feature, Systems. So Systems enables you to track items in a group. So this lets you, not only group assets, but understand the relationships between them. So we have, in this example, a heating system. And you can see the heat recovery units in there, and you're able to view any active issues on them.

And this is also available on mobile. So any systems that you need to act on are also available. And you're able to change the status. You're able to view the components within that system and view any open issues that need to be addressed.

So here we're just looking at a system, and we're looking at all the components that make up a bit and all the issues that are there. And you're also able to perform your own inspections of it.

We support field workflows. So we support QR code scanning, for example. This lets teams easily go to the asset they care about, find the object they're looking for, all the associated information about that asset, and perform the object-- the tasks that they need to do. So if you're looking at a panel board and you need to create an inspection form, that's available for you to do directly in the app through a QR code.

And you don't have to search through different modules to get that information. It's all available to you looking at the system it's associated to, the items it's connected to, all of it's available today on the app. And I'm excited to share something that's coming extremely soon and going into early access.

We are finally enabling 3D tracking on mobile. So assets are going to be available on the new model viewer that we have established. You're going to be able to access your assets. You're going to be able to perform the same workflows that you can on the web directly within your application.

So you can search for your objects. You can go directly to what you're looking for in the model file. And you're going to be able to perform your inspections, change the status directly in the model file itself.

So you have access to the details. You have access to the photos. And you can actually perform your inspections directly within the model file.

This is a really important milestone for us because, traditionally, we found models being used in the field being used very reactively, in a sense, when we talk to you. We find that when a clash comes up and they need to review what was the status of it, they look at it in that context. They'll pull up the model and look at it.

What this really enables is a proactive approach to the Model files. Field teams don't need to be model experts. They don't need to navigate the Model file in ways through different views or filtering in the model browser. Instead, they can just search for the objects that they care about, filter it down, interact with these assets, and perform their field workflows directly on the model. Rather than looking at a model and going somewhere else, everything is contained exactly in one place for them connected to the model.

But we do know that Models-- a lot of contractors and a lot of teams, Model files aren't reliable or they may not be available to you on the project. Objects need to be tracked before Model files are available. And for that reason, we do provide the ability to draw the assets on 2D sheets. This lets you view the same information on your 2D sheets and access the same field information that you need to access.

And lastly, we have the Progress and Reporting available. So we do have a variety of reports, including the Power BI and Asset Detail Report, as well as a lesser-known feature that's extremely valuable, and it's called Asset Progress. It's available in the app. And it will give you the asset categories and the status of all the assets as well as if you want to do percent, you can also look at percentages in there, as well as any open issues that need to be addressed as part of that status.

So we'll take a look at that in the demo. But it's a very, I wouldn't say hidden, it's a lesser-known feature that is a lot of value.

OK. So with that, let's jump into the demo. Before we get started on the demo, just to give some context on this project, if you're familiar with Revit, you're probably familiar with this project as Snowden Towers. It is a mixed-use building. For all intents and purposes, we'll kind of consider it design build where they had early access to the model.

And we're going to dive into three, maybe four or two, different scenarios depending on our time. We're going to talk about structural insulation, heating system tracking, door insulation, and probably also lighting installation, lighting and handover, too. So let's jump into the demo.

OK. So here I have my project as Snowden Towers in ACC build. And over on the left, I have assets. And if I select that, I have my asset categories over here on the left. And so these asset categories are the categories of objects that are valuable to you.

So, in this case, the objects are architectural objects, curtain walls, doors, windows, mechanical. We have heat recovery units. And we have some structural elements, concrete, and steel as well. So these are just a subset of objects that are on a project, but these are the ones that we're going to be focusing on and that we're considering the important objects here.

So the first use case that I wanted to jump into was structural tracking. And we have both concrete and steel. And in this case, these came from a Model file. So you can see, if I scroll over, they are associated to a Model file. And the way they came from the Model file was from a project admin coming in here to the Models file, and adding the structural model to assets.

And once that model file is added, you can map properties in the model to the asset categories. So you can see we have the categories, those objects that are important. I'm just going to take concrete as an example. and we'll look at slab. So 27 assets.

So what we do is we ask for a model property. And in this case, since it's a structural model and all the floors are slabs, we knew that we could say Revit category equals floors. And what that does is it combs through the Model file. Any object that matches that property condition, so any object that has a Revit category of floors, is going to be considered an asset.

So it went through and it automatically grabbed 27 assets, and it's going to create 27 different assets for us. Now, that's pretty nice for concrete, but when it comes to something like steel, it's, by far, the fastest way to do it. Because we're going to be importing 394 and 40 assets all at once, rather than going through a schedule or a spreadsheet import, this is going to let you grab all of those and create them all as assets at once.

Now, this is a Revit file. A lot of times structural models we know come in as IFCs and UFCs from other applications, like Tekla. And these support that as well. So you can use your IFC and NWC model files to extract assets from.

The next step on the model workflow is Properties. And this is important because a lot of times Properties and Model files don't align with the way field teams call their Properties. So, for example, if we look in here, the name of the slab, for example, the name of the slab is going to be a different property in Revit. And so the model property in Revit may be level.

So in assets they may want to see the name of this asset as the level property. In the description, so what field teams would expect to be a description, would actually be a type name. So what we're doing is we're, basically, providing a translation between model file names and field teams, what they kind of expect to consume out there. It's also important because we can take certain fields, like area, and map them to asset fields like square footage.

We find a lot of times only a very small subset of model fields actually make their way into assets. There's so much important valuable information in the model. And when they start getting to it in the field, only a subset of that information starts to be valuable for those field teams. So we're providing a way to really extract the valuable information to those field teams and put it in terms that they understand here.

After that, we'll come here to Importing Assets. Then, what happens is we're reviewing all the assets to import. In one assets version, for example, what we want to do is make sure you understand what's happening with your assets. So to understand if assets have been added or modified or removed, we want to give that overview.

So here I can see there's been one update to the level 3 slab square footage. Change, very, very small increment there. So I'm not going to import it, but that's what you would do. You'd click Import, and it would create all those assets for you.

So when we come to this lab here, we can come and we can see how that level 3 that we just looked at that was in [INAUDIBLE]. And it's in progress, right. So we see that it has a concrete core checklist. And if I click that and click the Model file, we'll be able to see that asset with its status assigned to it.

So there we are. So now you're getting an overview of all of the structural elements in that file. So, traditionally, when I was in industry, we did self-perform concrete. And, as it be, one of my responsibilities was printing out the 36 by 42. And any time there was a four, I'd go ahead and put stickies or color code and, basically, match these color codes up to show the status of the floors.

And then we'd staple them on top of each other. I'm sure you all know the drill. But this replaces that. It allows you to change the status out in the field or in the office, and it automatically color codes you. So you don't have to go and you don't have to mark things up.

You don't to change colors. Everything is done out there. And there's great communication between what's happening in the office here and happening out in the field. So if we take a look at this slab that's in progress, let's say, that we need to do the Concrete Report Checklist.

What we can do is we can take this, and we can sync it over to the app. And we can have the field team take a look at it. So I'm going to go ahead and do that. And give you a look at the application.

So here I'm in the ACC app. I'm going to go ahead and tap More. And you can see I'm in the assets module here. And all of the assets that I have are available here. Now, since we're in the Model file, I'm going to actually go to the Model file and take a look at it and give you a sneak peek here.

OK. And you can see I'm in our new beta product, the new model viewer. Everything looks nice and smooth. And you'll see we have a new tab here called Assets. Rotate the landscape so you can see. But as soon as we do that, you see the same color coding that you did on web available here directly in the model. And when I select that asset, the same details show up here that show up in the web and any other place.

So we have that square footage, have the status, and I have that Pre-Pour checklist. And so I can open that checklist, and I can start filling it out and make sure all the inspections here are done by the different teams. And I could submit this back to the office. So here I'm filling out my form and I'm submitting it back out to the office. That would sink back on the web.

All right. So the field team could input the information. It could go and review over to the office. The office team can review it. They can send it back and say, submitted. Once that's done, the team can just come back here, change the status to Complete, ready to pour, post-pour, complete. Having that kind of color coding, providing that information here directly from the Model file back to the office. So with that, that's providing the overall structural installation workflow.

Now let's jump into another use case. So we can demo here. Let's talk about our 2D workflows. So what I want to show is something that may necessarily not come from a Model file or you may or may not have gotten it, but it may not be reliable. But you're tracking doors, and you need to track all of the door install. You need to have that door hardware submittal associated to it. And you need to know it out in the field.

In that case, you can take your door schedule, whether you're exporting it from somewhere, whether you receive it, whether you're creating it yourself, you can import it from a spreadsheet. If you do have the Model file, you can import it there, too, as well. Make it a little bit easier. But what you can do is you can draw them on the sheet. So you can see here, I have two sheets that's relevant to this piece of equipment or the store, one on A101 or level one floor plan, as well as a 601, which is our door schedule.

So I'm going to open A101 just to give you an overview here. You can see that visual reporting directly here available on the sheet. So I go right to that door, A101, I know exactly where it is, all that same asset information is available here on the 2D sheet. And so if I'm going out on the field, I'm doing an install on the app, I can view the same submittal information available on the web out in the field to make sure that what I'm installing matches.

OK. I want to jump in and do a little bit, too, of a different use case, or of like a commissioning-equipment-type of workflow equipment tracking workflow, let's call it. Not be heat recovery units. So in this project, the project is being heated by individual heat recovery units, and we need to be able to track the status of the heating system as a whole. So we're not only tracking the objects individually, but we're also tracking them as a system.

So we have the individual heat recovery units here. I did import these ones from Model file with the barcode, but you can see that most of them are in pre-startup. So we're going through commissioning almost on this piece of equipment. We're getting ready to kind of start that process. What we could do is we could start here in the heating system.

So we have our new tab systems. And going into that, you can see the system has its own individual status. So we know that the heating system is now in pre-start. Now, what we've heard is the system itself could be in pre-startup, but there could be active issues and other things going on where the statuses within it don't exactly match. So you can see heat recovery unit, or HRU 202, is a pre-startup. The HRU109A is still installed.

And so you get that information, but here's where you need the actionable information. We're gathering this data for you. You're seeing that the status is installed. Why is it not in pre-startup like everything else?

So here you have the active issue. So hovering over it, we see this-- HRU is not functional. We need to return it. So they've gone out there. They've done the inspection on this unit. They found that it's not functional and it needs to be returned. So looking at the system as a whole, you can see, OK, this system is starting to be restarted up. There's still some issues going on that we need to address, but we're on the right path.

And not only that, but we can also not just look at the heat recovery units, but we can look at the panel boards here associated to it. Now, I didn't go through, and I didn't establish the whole electrical one line of DC recovery units. But you could.

So you could see, OK, the panel board is not energized, but the transformer, the electrical meter, everything else is on. So you can actually go back, and you can track, where is this being held up, and what do we need to do to bring this to the next step? Systems allows you to provide that relationship and understand what you need to do.

It also lets you do your inspections directly on the system itself, so we're talking about heat recovery units here. You may have a heating system that relies on in air handling units and pumps and several other pieces of equipment to make that heating happen. We know that when that gets into the later stages of commissioning, a lot of times the inspections need to happen on the whole thing. So you're turning on the whole heating system with all of these different components, and you need to be able to test on that one system.

So here, you could grab your form inspection, and instead of making one form and attaching it to every single piece of equipment, you're performing that inspection on the actual system itself. So systems are not just groups of objects necessarily. They're providing the relationships and the information that you need to perform critical workflows for you.

All right, then one more. We have one more to show. So the last one that I want to show you is electrical, and I want to show you light fixtures because I think this is an interesting example of one thing you can do here. So electrical fixtures-- you can see we have 588 of them, and that's a lot of electrical fixtures. So it was very easy to import these from a model.

I think the property mapping was Revit category equals light fixture or something like that, mapped the name. And now I have all of my light fixtures associated with that. I have all the model data associated to it, and I have the fed by, so I know which panel this light fixture is being associated to.

So let's say that some of these are being ordered, but let's say that some of them are-- we're getting in the later stages. Some of these panels are starting to get energized, and what that would look like from a field perspective-- so what I'm going to do is I'm actually going to share my app again.

And once-- we don't really need to look at the model file here on the mobile device because these objects have been installed. We know the lighting zone that we're going to. But we know that the panel board, for example, has a QR code on it. So we're going out, and we're looking at a particular panel board to see what's going on with the lighting zone, this particular lighting zone.

So let me see if I can-- I guess I can't. Let me go back here, and I'm going to come to Microsoft Word. And I have a QR code here, and I'm going to scan it on my app really fast. And we'll come back to mirroring here so you can see what happens.

So you can see after scanning that on the app it brought up all of the items that I've scanned, and since I've set up that relationship between the panel board and these light fixtures, it's showing me all the objects that are associated with this panel board. So in this case, I want to look at the panel board itself, so I'm just going to select the panel board.

It looks like it didn't pull up there, but that's OK. So now I'm looking at the asset name. I'm looking at the category and looking at the objects itself. And I'm looking at the lighting zone, so P303. So I can go in there, and I can see the system statuses, everything for this panel board. It is on site, and we have 20 assets that are part of it. And there's one open issue here.

So if I go into this object, I can see, OK, we've only installed some of these light fixtures. Several of them are on site, so they're waiting to be installed. There's no issues there. They're just on site. We haven't installed them yet.

But some of them are ordered. Some of them aren't even on site. But we can see there's issues, so if we open that, we can see the asset name. We can see the zone. And if we go to References, we can see these light fixtures are back-ordered.

So now we know, OK, this lighting zone, this panel boards are to be installed or this panel board is installed. It's pretty much ready to energize. But certain light fixtures here are back-ordered, so there's not going to be a-- we're not going to be able to fully hand over this lighting zone just yet.

And actually, if I go back to that panel board, one thing I can also do is-- let me go back to Assets, go back to that panel board really fast. Oops, P303. The other thing I can do with that panel board is I'll scan the QR code, and I can perform the panel board inspection here directly from the asset itself.

So here's an electrical panel inspection. I can add it. I can go through all of the inspections I need to so that even though I'm not turning it on yet, I can still get my inspection done on it, make sure everything's good to go. And then when those light fixtures come on board, I can just go ahead and scan them in. I can change their status, and then we're good to go.

So here we're providing an overview of just how everything works together in a lighting zone, and for those back in the office, one of the nice things that we do have with the model is that they're getting that visual reporting piece in the model file itself. So if I come into the model file, I don't have to be on site to go look what is and what isn't installed, what open issues are there. Instead, I can just come here, and I can filter by that system. So I can say, this lighting system, P303-- what is going on with it.

And let me switch to actually to a better view here to see an overall thing. So I can say system is P303. Oops. And I can see exactly what's going on with this system from the model file in the office, so I can see, OK, these light fixtures are good, they're installed, these ones are on site, and these ones here are ordered. Why are these ordered? Well, the light fixtures are back-ordered.

So in the office, they're getting that same information. While you're out in the field, you're getting that same information. Everybody's on the same page of what's happening with this lighting zone. Whether they're looking at it from a model file or not, whether you're looking at a 2D sheet or not, all this information is available to the same people, regardless of where it came from.

So that covers a variety of different use cases with assets and the different features within it. Very briefly, I do want to give you what you can expect to see in 2025 from us. Like we talked about, the container-- we talked about that source agnostic container. We call it our container strategy.

You're going to see a continued focus on that container strategy and being able to take sources to that asset from different sources-- from and to those different sources and providing that one place where you can continue to aggregate data. You're going to find more ways to access and act on your data. So we're still looking into ways and still producing ways to access all this data that you're giving us and providing you more information to act on these data.