Description
Principaux enseignements
- Learn about the basics of Autodesk Construction Cloud.
- Come to terms with the difference between a design object and the corresponding commissioning asset.
- Learn about the model-based workflow within Autodesk Construction Cloud.
- Learn how Dynamo can help in setting up the assets database.
Intervenants
- Ives VeelaertAfter obtaining his master's degree in engineering, Ives Veelaert was a data management consultant within the architecture, engineering, and construction (AEC) space for several years. He has helped set up the data management structure for many companies, including for the renovation of the European Community building in Brussels. He joined Autodesk, Inc., 15 years ago and is now helping AEC customers understand the Autodesk EDM (engineering data management) offering. Within ACS (Autodesk Construction Solutions), Ives focuses on the workflows, present within the "Autodesk Construction Cloud" (ACC) portfolio.
- KPKristina PoluyanovaKristina embarked on her career with Autodesk six years ago as a Construction Customer Success Manager for BIM 360 in Barcelona, Spain. 3 years later she relocated to London, UK, where she continued expanding Autodesk Construction Cloud reach across the UK, Ireland and the Middle East helping main contractors and owners adopt construction technology on their projects. In the past 2,5 years, Kristina has utilized her construction expertise as Senior Product Marketing Manager for EMEA, steering the go-to-market strategy for Autodesk Construction Solutions in the region, which includes overseeing market trends, industry regulations, competitive landscape & defining product-market fit in each region.
KRISTINA POLUYANOVA: Hello, everyone. And thank you for joining our Autodesk University class on assets, behind the scenes. We have a lot to cover today. So let's begin. But before we do so, please bear in mind that we may be making forward-looking statements. And we encourage you not to use this as the reference for your business decisions, as future developments may change. Please use your best judgment.
Today, on the call, we have-- today on the call, we have myself. I am Kristina Poluyanova. And I'm currently working as the senior product marketing manager for [INAUDIBLE] focused on representing our EMEA perspective and requirements when it comes to go-to-market efforts related to product positioning.
I've been with Autodesk for six years. Prior to joining the go-to-market team, I have been working as the customer success manager with the customers in the Middle East, UK, and Ireland, helping them to deploy digital solutions like BIM 360 or Autodesk Construction Cloud in its early days.
On a personal note, I was born in Russia, moved abroad 13 years ago, lived 10 years under the Mediterranean sun in Barcelona in Madrid in Spain, and then relocated to London where I am currently based three years ago. I also have my brilliant colleague, Ives, on the line here today giving this presentation to you. Ives, feel free to introduce yourself. Over to you.
IVES VEELAERT: Thanks, Kristina. Yes, so my name is Ives Veelaert. I'm a technical sales engineer, work in the EMEA region, Europe, Middle East, Africa. I'm based out of Belgium. I've been working for Autodesk for 16 years. I've been touching upon most of the software, such as, well, back in the day, AutoCAD of course, but then Revit Civil 3D Navisworks.
Did a lot of work in data management. And so it was kind of a natural progression for me to venture more into our cloud solutions, which is obviously the Autodesk Construction Cloud, and everything that goes with it. I live in Belgium. And that's-- yeah, more or less what there is to know about me. So back to Kristina.
KRISTINA POLUYANOVA: Thank you for the introduction, Ives. So here is the agenda we have prepared for you today. We will start with the introduction to assets and how we got there. Then, we will talk about asset-based workflows, the value proposition for assets, and we'll wrap it up with the future vision for assets, and the sneak peek into our roadmap. So let's begin.
First, let's identify what the problem in the market is. So if we look at construction project today, we know as a matter of fact that they create a massive amount of data. And data creation is just the beginning. Asset information is originating during the design phase. The model is a great source of truth for all the equipment and system components that need to be installed.
However, all this information is not easily transferred to construction teams during the actual building phase. Teams need to manually extract asset information from the model to then import it to any assets and equipment tracking tools. So we uncover that, that teams are not having visual representation of assets. As the result, they are suffering from data loss, as they don't know what has changed.
It is difficult to get asset information from the model into the assets tool. So teams need to manually enter this information. And teams cannot trust the information because it's not updated with the right results, and results in incomplete information, which means that having a strong and connected foundation for your asset management is critical for improving your asset life cycle.
With that, let's have a look at what can be done to address these pains in the market. Asset tracking is the answer. But what do we mean when we say asset tracking? So asset tracking is actually the process that allows tracking construction components throughout the life cycle, meaning that we start with design and manufacturing. We move all the way to construction and handover.
Now, let's have a look at what the critical components of asset tracking are. Eventually, we can break them down into three critical buckets. Connecting BIM to construction would be the first bucket. Being able to track any types of files, from PDFs to 2D CAD files, to 3D models. And last but not the least, allowing for a component-centric approach to installation, quality, and commissioning.
Assets are really the future that will bring you to the ultimate competitive edge. According to the Building Regulations Advisory Committee in the UK, the golden thread is the information that allows you to understand the building and the steps that need-- needs to be kept in order in order to make sure that the building is safe now and in the future.
So what we want to say here is that assets can, and should, be situated in the middle of the golden thread that can connect your 3D models, your 2D views, your PDF sheets, to all of your construction workflows. Now, let's have a look at what we actually mean with that, with all construction workflows. If you break down these workflows and look at them from a connected workflow perspective, we will see that assets actually impact all stakeholders in the construction lifecycle regardless of whether you are the owner, the architect, the subcontractor, or the general contractor.
For instance, for owners, defining asset tracking process, and which asset fields are required and handover to influencing what tools need to be used by the contractor, and overseeing the input of data would be one of the critical components of the work performed. For an architectural design team, participating in design reviews for contractors, from overseeing quality project installations, to identifying the right handover tools. As you can see, the workflow, and all the stakeholders within the workflow, are really connected.
Moreover, digital twins provide an opportunity to really transform the build and asset lifecycle. We can affect the transformation by tracking a digital thread of information that links all organizations and data with the end-to-end digital process that spans capital planning, architecture, engineering, construction, and asset management.
So transformation starts by understanding, what are the desired outcomes of the owner? What are the data requirements? And beginning to track the digital information, those necessities through planning, design, and construction lifecycle, via a digital replica of as-built asset. By extending the digital thread into operations, we can create a single pane of glass for correlating operational data and use rich data for predictive insights.
And finally, the knowledge collected by the twin can inform the capital planning portion of the lifecycle, giving owners additional insight. For example, is my facility achieving sustainability goals that I've set and I will fall in the right direction? Which systems or equipments and materials perform better than other across my portfolio? Or what's the future planning and design decision do I need to take in order to maximize my ROI and ensure I hit the goals for my portfolio?
So now, let's have a look at what Autodesk has done to help the industry uncover these workflows and address these needs. So if we look at the next slide, we will see that our journey with assets does not simply start now with Autodesk build and assets in Autodesk Construction Cloud. It actually goes back to the times of our legacy product, known to many of you as BIM 360 Classic, and BIM 360 Build, or Next Generation.
We started our journey with the equipment story back in 2013 with equipment in BIM 360 Field with the introduction of Field mobile app and equipment connection to models through BIM 360 Glue. We then introduced assets module in the summer of 2020 in BIM 360 Build with the intent to track an asset from its specification to acceptance through the use of customized status steps, and a more connected experience with the rest of BIM 360 portfolio within a common data platform in BIM 360 Docs.
Then with assets in Autodesk Build, post acquisitions, we provided our customer the ability to track asset status, installation, identify defects, complete inspections, pull asset information into construction-based workflows, leveraging the best of our elevated Autodesk Construction Cloud portfolio. All of this is amazing. However, there were still critical features missing.
The model has-- since the model has the most accurate information, by manually taking that asset info into assets tool, teams were losing a lot of data that cannot guarantee that all asset information is actually accurate. And second of all, the attributes, and terminology, and models may not align with the owner requirements. And the amount of information that needs to be conditioned and changed for the field teams is really overwhelming.
So now, with model-based workflows in assets, which is really the last pillar here, teams can get easy transfer of model information into assets tool that is visible, actionable, and accessible to field teams as well as connect their mobile data to powerful asset workflows. Model-based workflows in assets gives team-- give teams the ability to improve progress tracking by connecting teams, and elements, and properties from a model to assets and asset fields.
So in total, what we achieve here is we managed to connect design workflows to construction to help ensure data integrity, better decision making, we're saving time, and we're improving schedule control. Now, with our ultimate solution, which is Autodesk Construction Cloud, that spans across the entire building life cycle. We help teams around the world to address rapidly-expanding building and infrastructure needs, while making construction more predictable, safe, and sustainable to ensure you're able to make better decisions every day.
And if we look at the next slide, we will see that if we leverage the depth and connections of the Autodesk Construction Cloud platform, and BIM Solutions, you will actually be able to extract assets from models and connect them to the other parts of our portfolio such as submittals, such as forms, schedule, that will automatically help you to prevent error and eliminate manual processes to be able to deliver, track, verify, commission, and handover with data collected throughout the project.
As a result, what assets help us to achieve in Autodesk Build are the three core outcomes. And these are around decision making, so with teams having more visual representation of asset installation, save time by [? instantly ?] pulling asset information directly from models into the assets tool, and better schedule control by allowing a more accurate and complete asset tracking information.
Now, with this, I will hand it over to Ives, who will guide you through all available workflows and cover what's hidden and unhidden in products, and what you can use in your job every day. Ives, the floor is yours.
IVES VEELAERT: Thanks, Kristina. Yes, so let's have a look at some of those workflows. And this is perfectly in line with what Kristina was telling. I mean, we've talked about ACC, Autodesk Construction Cloud, as the single source of truth. I do believe that it's not just about a communication platform where you have documents, and forms, and what have you. I think the core of the whole construction cloud and what owners in the end are interested in is maintenance of their assets.
And so assets are indeed critical. And the beauty is that we can set up for success. We can talk about workflows from early design into maintenance, actually, and always have that single source of truth in front of us. So it means that we're going to be talking-- in the next couple of slides, we're going to be talking about, how do we actually set up an ACC project with assets in mind? So there's a couple of things that we're going to do. I'm not going to go through the whole list here. You're going to see that in action.
All of these are topics we're going to be discussing. So you can consider the ACC project setup as indeed setup and indeed the design aspect of ACC. We're then going to move into-- we've set up for success. We do have our asset tracking from the design. We're now actually going to deploy them. We're actually going to commission them. We're going to install them. And a lot of aspects around assets or any element that should be installed on a construction site, it has to do with completing forms, a commissioning form that needs to be filled in, et cetera, et cetera.
So you're going to see a couple of interesting workflows here where we tie forms automatically to assets based on status, et cetera. So that's the second thing. So we're moving from design into construction. Construction is finished. So therefore, if you consider having those assets installed and the whole building ready, then we can talk about handing over and maintenance.
So we're going to talk about Tandem, which is our digital twin solution. Now, of course, Tandem, if you look at it, it's as I mentioned, a maintenance tool. It comes after a handover. So you can imagine that not all the information that went on, and all the information and the workflows that went on during construction, are relevant to maintenance.
So you're going to see that Tandem actually pulls the design files from ACC. But what we can also do is we can pull asset information from ACC. So who installed it? When did it get installed? When's the new review of the element? When do we have to have maintenance on the element, et cetera, et cetera? Put dates in, et cetera.
We can all pull that in from our assets in ACC, and push them into Tandem, and do some relative analysis within that tool, within the digital twin maintenance tool. So what is Tandem, assets to Tandem, and then finally, a bit of what we can do once those assets have been entered, or the data I should say, on those assets, have been-- has been entered into Tandem. What can we do with Tandem? So that's essentially what we're going to be seeing here.
OK, so first of all, project setup. So we're really going to start with basics, with the basics. We're going to be looking at defining, in this case, a project template. You see that at the top, which is called factory template which has settings. So that's the first thing. We're going to set up a project as a template. And I want to draw your attention to the fact that these days, we now can define different categories of assets within the template, within the ACC template.
Now, what does that mean? It means that we have entire flexibility on setup of projects if we need, let's say, a hospital-based project, or a nuclear-based project, or whatever. We can have templates around that. We can specify our different assets right at the start, actually. So what is an asset from an ACC point of view? Essentially, it's an element that we want to track during construction. So we have the design information, we'll talk about that a bit later, but we also have construction information. Who installed it? When did it get installed? Et cetera.
So it's relevant that, of course, not all assets have the same construction information. So we need to define categories. So that's the first step. And the second step is actually, well, which categories get which kind of properties attached to it? So you're going to see, I've kept it really simple for this presentation. We've got three parameters, three fields, if you will, design ID installed by and serial number that we're using. And then indeed, not every asset has the same type of installations. That is that-- what do we mean by that?
Well, it goes through a whole cycle of different installation statuses such as, as you can see here, specified, ordered, delivered, installed. Again, I've kept it simple here. But you can imagine if you were going to install a door, that door might have a different set of statuses attached to it compared to a pump, or an electrical machine, or whatever. So I don't think a door will have a pre startup, a startup, a pre-functional performance test, and a functional performance test. That might be something for an electrical device, an electrical machine, whatever.
So what I'm trying to say is those assets are going to define the flexibility and the followup and maintenance of our building afterwards. And again, we're setting up for success here. So we're specifying this right out of the gates, right inside of the factory, template in this case. Into the templates. So of course, once that's done, all we need to do is based on that template, as you can see here, we're going to create our project. And that's effectively when we go into the presentation in a second, we're already past the initial design.
So we do have a building. We do have some structural information inside, we have equipment inside, et cetera, et cetera. So this is going to be a digital factory in which we're going to be maintaining all of those assets right from the start of conception down into delivery and maintenance. So just to give you an idea what are we looking at, well, we're looking at a data set with-- which has, just a screenshot here, which has as an architectural model, this building.
Inside, we're going to see some MEP services, HVAC, electrical, sanitary, et cetera. So all of this is defined within the MEP part. And of course, as I mentioned, this is a factory. So we'll need equipment. We're going to have conveyor belts. We're going to have, for instance, robot controllers. We're going to have plates on which those robot controllers can move, robot risers that we're going to have inside, et cetera, et cetera. So that's what we're going to do here.
OK, now I do want to stress this is a single source of truth. So essentially, it means that I want to transfer data from design into Autodesk Construction Cloud into, later on, Tandem. And so there's two things that I'm going to already define right from the start-- right from the start inside of my design files, which is two parameters called the asset URL, we'll talk about that later on, and the design ID, which is the unique identifier in this case of Revit.
And by the way, the workflow you're going to see is based on Revit. But we can also manipulate certain aspects and make sure this is aligned with, I don't know, 3DDWGs, maybe Civil 3D data. We can align it with IFC files through Navisworks, et cetera. So it's not just tied to Revit but I do think this is a nice example. So we're sticking to Revit for this presentation.
One of the critical aspects in our asset definition, and this is something I'm going to do right from the start, is the asset classification. And we're going to be using uniformat. For instance, in this case could be any type of format. I know different countries have different types of classifications. It doesn't really matter what type of classification we use. But I would strongly suggest to use classification because that is also how we can differentiate our different assets right from the start, right from the design aspect.
One of the other aspects inside of ACC is obviously a location breakdown structure, or LBS. Now, one of the things that, again, we can do is, well, first of all, we need to define our location breakdown structure. What I want to do is I want to use my rooms, or indeed, spaces, in this case, it's rooms, but could be spaces. I want to use my rooms from Revit to create effectively my location breakdown structure, which therefore is going to be tied to that whole-- that whole building, if you will.
OK, so let's have a look. You're going to see a video here. So we're inside of ACC. And just as I wanted to illustrate, so if we go into Settings, you're going to see that we have something called locations. And again, as you can see, that digital factory is empty. So we're going to use a template, which we can download. That's what you see here. And effectively, all we need to do is define the different stages, the different levels, of our location, or I should say, of our locations.
So of course, in Revit, I can pull a schedule on my different levels on my different rooms, the names, the numbers, et cetera. And we can export that. This is just an export to Excel. So I can get all of that information. And of course, the next step would be to say, OK, I want to transform this into something that looks like a location breakdown structure. And all we need to do is update this upload-- sorry, upload this into ACC. And you're going to see that effectively, it's going to have that hierarchy of the project name, the level on which we're sitting, et cetera.
So that's kind of the first thing. So out of Revit, I'm generating a location breakdown structure. So OK, let's rewind for a second. I've got my project template. We've got the asset structure in place. I know where potentially my assets are going to sit. That's the location breakdown structure. But obviously, the next step is now to actually create those assets. And so that's where the model-based workflow comes in.
So essentially, what we're going to do is we're going to leverage the power of ACC. We're going to leverage the power of Autodesk Docs. And we're actually going to say, look. Have a look at this Revit file, for instance. There's a couple of formats that we support amongst other things in IFC. So we could actually say, look, we're going to have this file here, which is, in this case, again, a Revit file. And I'm going to specify that remember those categories?
With their properties, with their approval, or installation status set, I can actually define that based on any type of parameter, any combination of parameters, I can say, look. This category, or this subcategory, or this sub subcategory, corresponds to this type of element. And that's effectively what we're doing here. So I'm actually looking for a certain family, a certain type, and I'm going to pull this information from my Revit file and into an asset database, if you will.
Now there's another thing that we're going to do here. Remember that I set that design ID? So we can use, for instance, Dynamo to pull the design ID from the element and push it into a parameter. What we're also going to do is not by mapping to a certain category, but by mapping one parameter from the design into the construction parameters, if you will, we can make sure that the design ID is pulled through into our assets. And that means that if I do the mapping for just about all of these elements, you're going to see that, indeed, I have a design ID, which you can see.
But I can also click on my model link, which you see here. And effectively, I'm pulling all of those assets in an automated way from my Revit files. If something happens to the Revit file, this system is going to warn me, and it's going to tell me there's modifications you need to review. That's effectively what is happening here. OK, so we've got our categories. We've got the location, breakdown structure. We've finally got our assets from the Revit files.
What we're going to do now, and this can apply to the location breakdown structure, but this could be applied to any type of information even from an external database. But what we're going to do is we're going to update our assets with the location breakdown structure. So I've got 318 assets here. What I'm going to do is I'm going to export all of those assets, kind of a report. Think of it as an Excel report. And on the other hand, again, I have my Revit file with my families, my types, my design ID. See? My unique identifier is pulled back here.
And so what I can do is I can say, OK, based on that design ID, I want to have my location breakdown structure, which is effectively the element-- the room that the element is sitting in, which I can report on in Revit, and say, OK, this is going to sit in, I don't know, room one, or room B, or a meeting room, or staircase, or whatever. And all I need to do is based on design ID, just pull this into that export from my assets. And guess what we're going to do then? We're going to import that new spreadsheet file.
And because it knows where these assets are sitting, it's going to actually update my assets. It's not going to recreate new assets. It's going to update my assets. And that's effectively what you're going to see here. The location is being pulled from the Revit file. So that's what we see here. And the beauty is then, of course, that we can start filtering. Show me everything that is in a certain storage I, or storage B, or whatever. And again, that tie to the actual 3D design file.
Cool. So we have our assets. So as you see, we moved through the whole thing. We've set up the project, we've got the location breakdown structure, we set up categories, we pulled the assets. We now have the assets all updated with location breakdown structure and everything. So what I want to do now is, as I mentioned, I want to get the single source of truth. In Revit, I need to understand where my asset is. In my asset, I need to understand where my element is that you've already seen.
We're going to see in a second if I'm in Tandem, where does this sit in ACC? You're going to see all of this in a second. OK, so what I want to do now is I want to do a bidirectional link. So as I mentioned, we have the elements in, or as an asset I should say. We can push this into-- or we can show this into the 3D model. But what we can do here is now say, OK. And that's that second parameter. Remember that I mentioned that in the beginning?
You've also seen me just export, again, the list of assets. All we need to do now is say, OK, I'm going to take that asset list. And essentially, to cut a long story short, I'm going to pull up the design ID from the assets, from ACC, I'm going to find this element in Revit, and I'm going to say, right. Get me the URL that this thing is pointing to inside of ACC. So all of these assets have unique URLs that are also being reported on through the spreadsheet.
So all I need to do, then, is say, OK, update that parameter, which means that we now have a bidirectional link. I can go to my model, it zooms to the equipment, I can select my equipment, and if you then actually look at the properties, then it's going to push back into my assets, if you will. You're going to see that later on.
OK, so time to bring in a VR. OK, so we've got our model. We've got everything in place. But, of course, there are a lot of stakeholders. And we need to convince those stakeholders of, in this case, our digital factory. So what TwinMotion is really good at is effectively running a presentation and understanding what is happening. So this is something you can give to a stakeholder, I don't know, some government institute that needs to give its approval on my building.
And TwinMotion is very easy to deploy extra cherries on the cake, I would say. So for instance, I can put a truck in. By the way, notice the truck. Something's going to happen to it. That guy in there, he's-- it's truly a 3D character that we can look at. And he's kind of interacting with us. See the gate that opened automatically as I moved forward? And as I move into the construction, or the production, sorry, production unit, you're obviously going to hear noises of that production. You can see the conveyor belt working.
All of this is still that single source of truth. I'm just leveraging [INAUDIBLE]. OK, so let's go back here. So we're going to be venturing more and more into this. And by the way, you're going to see I'm specifically focusing and gearing TwinMotion towards presentation because you can actually put that extra feeling inside. You'll notice the TV screen where we can do some quite intelligent stuff. Just notice how it kind of interacts with me.
So that's what we can do here. So again, TwinMotion, very much around presentation. Why do I focus on this because you're going to see the acquisition of The Wild company within Autodesk. And they've also gotten, or developed for years now, VR environments. And so you're going to see that VR part pass by as well. And I clearly want to differentiate the two. You're going to see that this is visualization, and convincing people to understand what is happening.
Whereas with The Wild, that's an integral part of our decision cycle. You're going to see that it's a collaborative VR environment in a second. And the reason I'm explaining it here is because you're going to hear some sounds within the-- come on, The Wild environment. So that's why I want to position it here.
But as I mentioned, The Wild is really around collaborative VR environments in which we can review whatever is happening inside of our design files, and during construction. You're going to see that in a second, we're going to be-- there's going to be two of us. Notice that the truck is gone by now. So we're going to-- there's going to be two people, myself and a colleague of mine, who's going to be interacting and who are going to be reviewing the design as it is happening.
And that's the beauty of The Wild, of course, that you don't actually have to go on a construction site. Imagine that you have all those construction trucks and those different machines, those cranes, et cetera obstructing what you want to do, and the verifications you want to do. So in that respect, The Wild is a very safe way of doing a review of a building. So that's the difference between the two.
Again, TwinMotion, really presentation, a presentation environment in which we want to convey our design intent, whereas The Wild is really a collaborative VR environment, which helps us in safety, actually, because we don't necessarily have to go to the construction site to see what is happening.
More about The Wild in a second. OK, so we've done the design and we've convinced our stakeholders we're now into construction. And so the first thing is that I want to follow up on my assets. So the first thing is that I want to decide on what assets do we have, when do they need to get installed, et cetera. A lot of times, I heard about people saying, it would be good if you guys would have forms rather than assets on which we do the checking. Because people work with forms in the field. And that's effectively what you're going to see here.
So you noticed in the title ACC Connect. So I'm going to leverage a recipe on ACC Connect that will tell me that whenever an asset is in a certain state, I'm going to generate an installation, or a commissioning form. Notice also, jumping back a second here, notice also that the elements that we have, the different assets as you see here, they can be tied to a 3D model. But they can, at the same time, be tied to a 2D sheet, which is relevant to all those construction workers who are very much interested more in the 2D sheet rather than the 3D file.
So what we can do here is have the best of both worlds, combine the 3D model and the 2D sheets. Notice the color coding. Remember that color coding. It's going to come back. Everything that's specified is going to be black. Everything that's ordered is going to be orange. Everything that's delivered is going to be kind of this purple color. This will come back in a second.
Notice also right now that we have this one PDF attached to it, which is the manual. One of the benefits, as Kristina mentioned in the beginning, assets should be the source of everything that is ACC and construction. We can tie PDFs to it, et cetera.
Now, the thing is that as far as forms are concerned, we don't really have any forms. That's why you just saw my forms tab is empty. So what we're going to do is we're going to say, OK, get me the assets within ACC through ACC Connect, which is the scripting, the very easy scripting language, visual scripting language. Think of kind of Dynamo for Revit. But this time, it's leveraging the ACC Cloud. It's going to help us in automating certain processes. And the automation I have in place here is once an asset hits the delivered state, you should really get a form attached to it.
We can base this, we can have different forms based on different types of assets. Hence, the categories again. But what you're going to notice is that I now have, on my assets, I'm going to have for my specific elements, my furniture for instance. You're going to see there's my TV screen and my sofa. Those are going to be installed. They're in the delivered state right now. So I have my reference to my commissioning forms, et cetera.
OK, cool. Now, before we do that, let's have an idea as to what my colleague is going to think of this. Now, the beauty is that, again, all of this is tied to ACC. So you're going to see The Wild in action in a second. And what I really want to do is invite my colleague through ACC through the scheduling tool, or through the meetings tool I should say, excuse me, through the meetings tool. I'm going to send him a URL through The Wild environment.
And this is not The Wild just yet. I just want to illustrate that the file that we're going to be using is this one. And you're going to notice that certain of these elements are black, which corresponds to the specified status. Some of these are kind of orange, which is the audit status. And then the kind of purple ones are the delivered status. So what we're going to do is I'm going to link into the wild here, which is an environment that does tie into ACC.
So all I need to do is we're going to go into this environment. And it's going to pull information from ACC.
[VIDEO PLAYBACK]
- Hey, [? Johann. ?] Good morning. How are you?
- Good morning.
- You can see the collaborative-- Good. I'm good. Thanks for coming into our VR environment here. You've seen obviously the invite in Autodesk construction [? count. ?] Yeah.
- Thanks a lot for inviting me. I'm really happy to be here, and to inspect the model you wanted to show with me. And it looks like the weather's quite nice at your place.
- Yeah, right. No. This-- well, I'm in Belgium right now. And it's kind of September, end of summer. It's a bit cloudy. But well, it's kind of raining. But it's, well, it's OK. I'm not complaining. Where are you these days?
- I'm in Munich. And it's not raining, at least. So it's not like we can see outside here in the workshop. But it is really-- it's sunny. We have 26 degrees. And that's fine. So this is really what you like in autumn, right?
- Yeah, yeah, yeah, absolutely. All right. So let's have a look at this digital factory that we've been constructing. And you can just give your thoughts as to what we're installing. I do think it's a little bit small. So let me just try and grab that and make it a little bit bigger. There we go. I think that looks pretty nice.
- That looks pretty nice. Oh, come on. Come on. Let's make it really big enough.
- Yeah.
- So this is how we can see it. [INAUDIBLE]
- That's true. That's true. That's better. That's better, Johann.
- There we go.
- So yeah, as you can see, this is obviously a factory. There's all kinds of equipment inside. So we're about to install. And that's just what I wanted to get your thoughts on.
- Can we-- can I just hide the architectural file so that we can see inside? So because I do see the model now. And that's fine. But let's go to the model. Just a second.
- Yeah, sure.
- I will just go to the model browser. And that's great. I can look at the whole model and the whole views that I'm used to in the Construction Cloud.
- No, absolutely. Absolutely.
- And let me just--
- All communication.
- Let me just hide the architecture model.
- Yeah, exactly.
- This is much better.
- That's what we're looking for. Yeah, absolutely. That's what I wanted to get your thoughts on. Actually, it's kind of on the first floor that we're going to go into in a second. So maybe-- actually, let me go in and maybe-- or are you going to activate the walls again?
- Yes. I just did so.
- OK. OK. Then I'm just going to walk out here again. There we go. OK, cool, so let's go inside. I'll just go inside and I'll just ask you to follow me if that's OK. So I'm gone now.
- [? Here we go ?] now.
- Let's just-- I'm going to gather you. There we go.
- Whoops.
- And you should-- and you should be somewhere around--
- Oh yeah. Let me just walk a little bit away.
- There you are.
- Look here.
- OK. Hello, there. So yeah. We're inside now. So as you can see, what I've done to help us, if you will, is that some of this equipment that we really need to install, they go through a couple of statuses, as we know, from Autodesk Construction Cloud. So everything that's just specified where we still need to decide on who gets to deliver, et cetera, I've put that in black. So the air terminals, for instance, at the top, that's-- those are black. So that's still not decided on, if you will. We know there is an HVAC system that's going to go in.
But we haven't decided on it yet.
Actually, we're going to start with the first floor. So I'm just going to move up to the first floor. And I'll see you there. I'm going to gather you again. OK? So just bear with me for a second.
- I can follow.
- And you can follow. That's also fine. You're going to follow. And ah, there we go. Yeah. Let me just-- like this. OK, so let's just go into the hallway here. Shall we? So again, what you're going to see is that we're at the end of the building. There we go. So again, if you look for you straight ahead, for me to the left, there's a couple of those elements in black. They're still in a specified status. If you look right back at you in the other room that we just came from, there's the furniture [INAUDIBLE] ordering. So that's going to be installed in the near future.
And then if you look the other way--
- [INAUDIBLE]
- Yeah, if you look the other way, there's the TV and the sofa that's in kind of this purple kind of color, which is kind of aligned with the coloring in ACC again. But this is actually delivered. It sits on the construction site. And we really don't want to go into the construction site right now. It's a mess with all the installations. So that's why this VR environment is also pretty cool, and a safe way to inspect things. But so essentially, what we're going to install as a first step, I think, it's tomorrow actually, is the sofa and the TV screen. So people can--
- It's delivered, but it's not installed.
- No, it's not installed yet. No, no, no. Exactly. And I think this is kind of a good location, I think. So yeah.
- It looks like-- but you know what? What I was just looking at, there's a big hole in here.
- Yeah, that's true.
- This is for the stairs, right?
- That's the staircase. Yeah, that's the staircase. They're still missing. Yeah, absolutely. Don't fall in.
- And so I have a feeling if this is more like a noisy area because everybody's running up and down. So I'm not sure if the TV installation and the sofa installation would be the best here. So there should be a more quiet room somewhere more cozy.
- OK. Well, obviously, we have the browser. We could look through it in the ACC environment. But I know for a fact that as it happens, let's just-- I'm just going to go to the other side here. There we go.
- I'm going to follow you. Wow, you're fast. You're fast.
- Yeah, I'm fast, man. I'm fast. Cool. So if we look inside here, then I think what you're saying is that this actually might be the better location to install this, right?
- Exactly. This is much more quiet and much more cozy.
- That's true. OK, so let's go with that. OK, excellent. Good stuff. [INAUDIBLE] Well, that's actually all I had for you. And you never know who's looking over our shoulder. So they're going to be bored after a while. Right? So let's just call it a day. Thanks a lot for giving me this feedback. And if I have any more news, I'll send another invite in ACC.
- Yes.
- Thank you.
- [INAUDIBLE] It was great to follow you in this workshop.
- Cheers. Bye, man.
- See you soon. Bye-bye.
[END PLAYBACK]
IVES VEELAERT: There we go. So hopefully, that gives you an idea of the difference between TwinMotion and The Wild. One is a presentation environment, the other one is a communication platform, which helps us in a safer and better way to manage construction sites and have a conversation around what should be installed, et cetera. OK, so you've noticed that we kind of described in that video, I mean, it's just a basic example, right? But we decided to move the sofa and the TV to another room.
So of course, we now need to install this. We're actually going to go live into that construction environment. And we're going to leverage the mobile device of Autodesk Construction Cloud. So of course, all of that relevant information that sits within ACC is still there. We do have our sheets, we do have our files, we do have our forms, et cetera. Everything that's in the cloud, we can leverage.
What you've just seen here is that I went to my assets, and I actually went to my locations. I can scan my location code and see again just as I did on the browser, I can see what elements, what forms, what assets, et cetera, sit in this room. And so what you're going to see is that, OK, so I [INAUDIBLE] this screen to be installed. Remember that it's delivered, but we now need to install it. It's still in the same place. We haven't touched that. But remember that we negotiated that it should really move to another environment.
And we could use issues. We could actually even create an issue inside of The Wild and specify that the element should be moved or whatever. What we're going to do here now is say, OK, so we've got our TV screen. It's installed. Let's assume it's installed in the other room. You'll see what happens in a second. And I just scan, for instance, a QR code, which is going to be the serial number. And all we need to do then is specify-- the only thing that's different for now is that we need to modify the location.
Remember, we did get that message. We did receive the TV. And we did move it to another location. So that's effectively what we're going to do here. We're going to say, look. Rather than that staircase, I'm going to push it into one of those rooms, the storage room. All we need to do now is sign off on this, submit it, sign off on it. And that's going to be a readily-completed form inside of ACC.
OK, so we've got a bit of a problem now because my form tells me that that TV screen has effectively moved. So what I want to do now is I want to trigger an automation that will get me to move that asset to the correct room within Revit. So as I mentioned, single source of truth, we always want to connect everything. So here, you're going to see this installed. I've picked a sofa one just as an example. I could have picked a TV. But in this case, also automatically generated form, we filled it in. It's installed, sits in another room.
So what you're going to see is that we're pushing from the forums. We're linking into the assets. And you're going to see the asset is now in status delivered and that we don't really have that link from the form just yet. Right? It's still in the delivered state. The other aspect is that I do have a design issue from ages ago, which has got nothing to do with the story here. So what I'm going to do now is automate the fact that if a form comes in, it should really update the installation status. It should really fill in who installed it, which is the one signing off on the form.
And actually, if the location has changed, I want to raise automatically an issue that tells the designer they need to move that sofa, or TV, or whatever. So that's what you see here. If the two do not equal each other, basically create an issue, and attach it to the asset. So that's what you're going to see here. So I'm going to run this script.
By the way, I'm using the test recipe here because we can trigger on certain events. We can say, OK, we want to do this every five minutes or so. So we would have been waiting here for quite a while. So that's why I do a test recipe, which is immediately. But you get the hang of it. You understand what is happening. We're actually automating the fact that I want to have an issue. As you can see here, please move sofa, et cetera, et cetera.
You're also going to see that it says description generated by system. We're going to come back to that in a second. But the fact is that issue was generated automatically, points to the asset. And so therefore, I now know, OK, so I need to-- I need to look at that asset from a Revit point of view. Notice also the status has changed to installed. So it's pulling that information from the phone. OK, so we've got the issue, we've got the original form tied to the asset. Again, everything asset related. Single source of truth assets are critical for a digital twin with a correct handover process at the end with all the information attached.
OK, so next step. We've got the form, which tells me that that sofa moved to another room. We raised an issue. So essentially, what I can do is, well, I'm going to automate the process of moving this TV and this sofa. Now, of course, obviously, I don't know exactly where we've put this. So you're going to see how I've done that in a second.
The first thing to do, obviously, is filter my issues on those specific ones that I need to modify. And so again, I'm going to leverage that report of those specific issues as a spreadsheet. I'm going to move-- I'm going to import that or I'm going to get that as input into my Revit file. We're going to read that Excel file, we're basically going to read that description field. Remember that I mentioned that description field, which essentially specifies the new location, and has, guess what, the design of the Revit element inside.
So with those two bits of information, I can basically pull any of those elements and push it to any other location. Second aspect is that at the top, you might have seen that there's some color coding going on. So not only will I move this element, but I'm also going to color code where the element is sitting. And you'll notice that those elements by default sit on the centroid of that room. I obviously need to move that again. But that's what you're going to see here.
And that's how we do this. We then save that file back into the cloud. And essentially, you're going to have an update. And just as a bonus here, this is not between just-- or in one floor. Just as an example, I just modified the spreadsheet myself, but you're going to see that I have this furniture element in a certain location. And what I can do now is I can say, OK, I'm going to push that furniture into another location on another floor just as an example that you'll see that the Dynamo script is also working.
You're going to see it's a storage A there. That's where we want to get that element to. So I'm just going to run with that spreadsheet, which is modified. It pulled the furniture from ground floor, or level zero, moved it into level one, again, at the centroid. So we still need to move that obviously. But it's quite flexible to use that-- to use that as an automated workflow. OK, so very quickly, so we've got everything installed, everything is up to date. What can we actually do with our assets, because they are now living things, if you will, they've got all the data.
They are installed, or they're in the process of being installed. Just as a quick overview of ACC, if you will, we've got schedules, we've got costs, we can predict cost, et cetera. That's essentially what you're going to see in this quick video. So essentially, you're going to be looking at, for instance, or we're going to be looking at the schedule. Schedule can be tied to assets, which needs-- which asset needs to be installed at what point in time. And the beauty is that I can also attach my tasks with the elements to be installed to my cost, which means I can start forecasting when this guy that delivers the HVAC system, when does he get paid, do we have enough budget, et cetera, et cetera.
Again, as you can see, I'm pulling my HVAC, my air terminal. I'm showing it in 3D. And as I mentioned, that's what I mentioned in the beginning. We can also do that bi-directional link and have that URL point back to the asset. So that's what we're going to see here. Notice also a couple of things here. That's the next step we're going to do.
Notice that we have our planning. So what I can do is I can take my planning from ACC, effectively through desktop connector, which you see at the top, and I can pull this in. Automatically, and that's a Navisworks functionality, I can pull in my different tasks also in Navisworks. And if I then decide to have my elements defined or sorted, if you will, as selections with the same name, with the same name, I can actually tie my objects to my timing and run an animation across time. So what you're seeing here is I've pulled that database,
I've actually specified that all of these elements need to be constructed. We can also demolish-- or we can have temporary elements. In this case, it's all construct. And effectively, you're going to see plumbing fixtures, lighting fixtures, sprinklers, ducts if you look at the MS project file. Then it's effectively the same task.
So what I'm trying to say is that we can automate the process of my timeline and following through on how my construction sequence is going based on ACC. And remember, those tasks, again, without going into too much detail, but just about anything can have feedback from the construction side. So it means that if somebody says, that schedule, well, I'm going to put a suggestion in because there's a modification to the planning. Then, we can totally do that. So that's what you're going to see here.
OK, so all of this is being constructed based on my MS project file. Notice that indeed, there's like a sequence in certain of those tasks. Obviously, because it's a planning tool. So what we're going to do here is very quickly, I'm going to say, look. One of those tasks, we can't complete it because it's delayed due to some reason. So we're going to move this to another start date, another end date, et cetera. And that means that my project-- my MS project is going to update.
And so that means that hopefully, I can get my Navisworks file and my animation to follow that. So very quickly, what we have here is a full process that allows us to automate and to approve suggestions from the field. We're going to update the Microsoft Project file. We're going to update the schedule. And that means through Desktop Connector, all I need to do in Navisworks is update my schedule. And everything will follow.
So that's what you're going to see here. So in this workflow, as the project planner, I'm looking at this, I'm analyzing of it's critical path, if there's cost involved. But let's assume all of this is good. So I'm going to approve that change. I'm going to modify my Microsoft planning accordingly. So my forklift, which I moved, I'm actually going to do this now as the planning supervisor. I'm going to push this in, update the schedule. And effectively, what you're going to see is that if I move to Navisworks, then that's going to follow.
For instance, here, version three. If I compare it to version one, for instance, or version two for that matter, you're going to see the changes that have happened. OK, there we go. So I'm just going to actually quickly move on. I just want to show you that, indeed, if I refresh this, I can synchronize my Microsoft Project. My tasks, they're going to be updated. And all I need to do is simulate this again. And you're going to see that at the end, the sequence in which these things are constructed has been reversed now due to the fact of a change on the construction field.
Last thing, reporting. So again, all of the information that we have on assets can be used and can be leveraged to analyze in time across cost, but also in, for instance, just a basic report. What's installed at what point in time? And how much percentage do I have installed, et cetera, et cetera? So that's kind of what we can do here.
Very quickly, you've seen that in The Wild, I have my different elements color coded. So again, what we can do here is I can base myself on the assets from ACC. They all have a status. And again, in Navisworks, I can link that database with my assets in here. And I can say, look. Get me as an extra property the status and potentially the URL. So that's all we need to do. The only thing that's left now is to actually do an appearance profile on those different elements.
So we're going to be, first of all, looking at the different assets. That's what we're having here. That's a selection set again. We can then say, OK, everything that's not an asset, make it transparent, for instance, or hide it, or whatever. And the beauty is now if I look at it, I'm just going to move forward for a second here. If I look at those different elements, I can actually color code them based on the installation steps. And that's what you saw in The Wild actually.
I saved this file into ACC, as The Wild is communicating directly with ACC, I can see those different color codes. In this case, it's green for installed, et cetera, et cetera. But that's effectively what you're going to see here. So I'm just going to move forward here. We're just going to color code a little bit more. We can walk through. This is in Navisworks. But the same thing is happening in real life, with for instance, [INAUDIBLE].
OK, so that's kind of it when it comes to what we can do with assets from a construction point of view. So we went from design, we went into construction, you've seen that all the data is indeed connected. Again, even from Navisworks, we can link into ACC, et cetera. But the thing is that we finally want to move to maintenance. And maintenance is really around digital twins.
So what do we do with digital twins? We simulate, we predict, we inform essentially. And that means that once we're in installation, once we're inside of maintenance, it means there's a lot more potential for our assets. Because if you think of a building, 10% of its lifetime is construction. The rest of it is maintenance. And so there's quite a few things that we want to understand when it comes to maintaining assets. So performance monitoring assets and portfolio analysis, et cetera, et cetera.
So quite a few things that are relevant from a maintenance point of view. Actually, I would say the most important thing is those assets because as you can see here, 95% of all that data goes unused from the design point of view. What I'm showing you here is that we can bring this information along. And another aspect is owners want to be more integrated into this whole construction process and actually have their hand on what is being delivered to them.
And when we say that, well, traditionally, owners get maps of data. And really, what they want is a digital twin that helps them analyze information. And when it comes to analyzing information, we're really talking about assets, systems, spaces, et cetera.
OK, so Tandem is our digital twin tool. We can pull information in from ACC, just the files. What I'm going to show you here is that we can also sync asset information to Tandem. So again, we're looking at ACC, we're looking at the different files-- sorry, the different assets. I can filter for audit installed specified as 35, 37. Two of them are indeed installed now. Remember that television and our sofa? It's sitting in the correct place, et cetera.
Again, we can report on that. That's the report I showed earlier on. So we can see how many have been installed. There's two of them ordered, specified. Again, same story as before. So what we can do now is without going into too much detail, we can easily pull the files themselves, the Revit files, from ACC into Tandem. The problem is the data that sits with the assets. So you're going to see installation status is empty, installed by is empty.
What I really want to get at the get go in Tandem is to at least start with the construction information that came from the construction side and from the construction workflows. So again, I've developed an-- or there's an ACC script that a recipe, if you will, that we've built, which essentially, without going through all the details, but it's listing all the assets in Tandem, it's running through the assets in ACC. It's comparing both. If a parameter is different, empty, or differently filled out, it's going to update those assets in Tandem.
And it's as easy as running that script, and you're going to see there's no tricking here. This is basically just pulling that information, assigning it to the different elements, and that's what you're going to see here, installed audit specified. With the asset URL, remember that I said that I will also be able to point back to ACC. And so effectively, that if you think of it, this makes ACC kind of the communication platform also for Tandem. It means that we can have forms in there that will update information in Tandem, et cetera, et cetera.
So that's what we see here. Again, all those different elements, I can, again, sort by any of those properties. I can look at that furniture, look at the properties. That's what we're doing here. And as I mentioned, we've got the asset URL is also updated through the script. So I bring that back into ACC. I can look at the placement in 2D. And all of this data does correspond. It's all based on the single source of truth with all the information attached through the different stakeholders, et cetera.
And finally, there's also a report that we can get out, which is automatically sent to us as and when data gets updated in Tandem. OK, so that's it. I'm going to skip the Tandem overview for now. I think this is something that is well documented. You can go to tandem.autodesk.com or intandem.autodesk.com, to get information on Tandem and what the value that is that Tandem can bring. But essentially, Tandem is our digital twin, which allows us to report on certain aspects that allows us to understand how elements are working in real life, et cetera.
So I'm just going to move forward. And I'm going to hand it over to Kristina here. So Kristina, if you can take us through the last slides. Thank you very much.
KRISTINA POLUYANOVA: Thank you for the presentation of workflows, Ives. So now, let's summarize the values of workflows demonstrated before to you. So if we look at the next slide, we'll see that if we combine all the workflows we've just seen, we can basically break them down into three core buckets. First, design and coordination, meaning that we're able to achieve better outcomes, improve communication, and facilitate 2D and 3D exchanges.
Second, planning and field, meaning that we are able to improve field collaboration, have better cost control, and easy handover. And last but not the least, operation and maintenance, meaning that we are able to provide easy access to digital twins, and streamline operational readiness of facilities. Now with that, let's have a look at what the future is holding for us.
What is our vision for assets? So for the next year, what we are planning to do is to continue delivering on our vision of asset-centric construction by providing more functionality for project teams to track any item for the building. Whether it's for a sheet, model, file, or a spreadsheet, the information is connected and centralized on objects through the power of the Autodesk Construction Cloud platform, allowing anyone on the team to stay focused on building, not searching for the information and wasting your time.
So let's have a look at it in more detail. How are we planning to get there? We are planning from an R&D perspective to focus or to set the goal for assets around three core themes. First is around streamlined workflows. What we mean by this is that our team is focused on making sure your asset data is captured by the right people at the right time and for the right group of assets.
Second, optimization, meaning that you will notice improvements, significant improvements, in performance and deeper connections to the rest of the Autodesk Construction Cloud portfolio, as well as quality of life updates that makes finding, grouping, and tracking your assets easier. And the last one here is models for the field, meaning that we are committed to providing even more functionality to utilize model information combined with field information to collect and track information for the digital handover.
And with that, we're going to thank you for your attention today. And we are looking forward to seeing you here next year. Enjoy the rest of AU. Thank you.
IVES VEELAERT: Thanks, guys. Bye, everyone.