How Autodesk Construction Cloud Facilitated Design Collaboration for Paper, Energy, Mining, and FMCG Conglomerates

YASH VYAS: Hi, everyone. Welcome to our AU session. Today, I know the title is a bit long, but today, we're going to talk about how ACC facilitated design collaboration and construction processes for paper engineering, mining, and FMCG industries. The title's a bit long, as I mentioned, and why these industries, we'll get to know in a while.

But my name is Yash Vyas, and I have my dear friend Mani, who's joining me for today's session. But before we move ahead, I'd like to make a thing clear that we may be making forward-looking statements. And we encourage you to not use this as a reference for your business decisions. We'll say that the future development may change, and please use your best judgment moving forward.

With that, my name is Yash Vyas. I'm a technical solutions executive. I work with Autodesk. I look after the ACS tech sales for the Indian market. I have over eight years of experience in the industry. My experience includes BIM automation, computational design, and digital transformation for the organizations.

Outside of work, I'm an everything-at-once kind of a person. I'd like to do anything and everything that takes over my mind. I'm also a professional motocross racer, so that's what I do in my spare time. And as you can see, I have my headphones on. I'm a big-time music buff, and I can listen to music all day through. So that's a bit about me. Over to you, Mani. Thank you.

MANIKANDESWAR AMARANATHAN: Thank you, Yash. Hi, this is Manikandeswar. I am a senior implementation consultant based in Bangalore, India, with a background in automotive and mechanical engineering. I bring over 11-plus years of experience in the engineering industry. I specialize in helping manufacturing and plant engineering customers implement and integrate tools, processes, and workflows to achieve their business goals.

My expertise includes Vault, Fusion Manage, ACC Docs for PDM and PLM, and AutoCAD, Inventor, Inventor Factory Design Utilities, Fusion 360 for product and factory design. Thank you.

YASH VYAS: Thank you, Mani. So we'll have a look at today's agenda and what are the items that we're going to talk about. So firstly, we'll talk about the struggle that is real. We'll talk about the problem that we are solving. Next, we'll talk about how we are getting the things done in terms of solving that problem. And then we'll have a look at the secret sauce-- what makes this a game changer? And at the last, the payoff-- why all of this is worth the effort.

But before we start, I have something to check with all of you guys. We have four must-haves for everyday living. I'll go-- the things one by one. First is a toilet paper and a currency note. We can't live without it. If we talk about electricity, we can't even imagine our lives without the same.

If we talk about minerals, anything and everything-- a laptop, batteries, mobile phones, electronics, cars-- you can see, almost everything around you has some element of silicon or some material. And all of that is possible because of the mining industry. And at the last, our favorite and delicious snacks-- you can't imagine your lives and birthday parties without it.

If I would say, these are not the things that we panic-buy during a crisis. These are generally the everyday products that we use. But today, we'll explore how ACC is helping transforming these industries and making them accessible for the masses as we move forward.

But there is a fun fact as well. Paper industry produces enough paper to wrap the Earth 50 times. A single wind turbine can power up to 1,500 homes. There are the deepest mines in this world that can stack up 10 Empire State buildings. And FMCG company hardly takes less than 24 hours these days to get a product from their assembly line to shelf.

But the thing is, what is common between all the industries, and why the title? Despite the different nature of these industries, at the very core of it, they function quite similar. They are very capital-intensive and infra-intensive industries, and they have to interface a lot with the AC industry when they set up factories or into their day-to-day operations.

And that's where the real challenge lies because of the nature of the industry. It involves multiple disciplines. Every discipline was working on their own set of applications in their own environment. And that's created a real challenge. And there was a lot of collaboration issues in there.

So what's the problem we are solving? As we move ahead, everyone is talking about data, the big giants, the MVPs of the world. Everyone is emphasizing a lot on data. And it can be emphasized more that data is the new oil, digital transformation is now. If we lose out on a common data environment or if we lose out on this opportunity to digitalize the entire industry and workflows, I think that will be too late to move forward.

But if we talk about the real challenge in terms of the things that we face at the ground level, so manufacturing customers are planning their facilities with the best possible and technological way that they can. But still, these are unconnected and consecutive. And the workflows are also broken.

So how it will look like in a factory is most of the projects, they miss a combined approach with the great tools. So a factory planner would be having a very good tool to plan the factories, but they'll go up to a point. And then they give it to an architect. And the architect will take it again from 0.

Now, the architect, he or she, will use their applications, their set of things. They'll give the things to the production planner. And then the production planning team would again start the things on a new set of product. There is a lack of continuity as we are moving forward. And that's the real challenge because there is no common thread that is tying all the things that every persona, or individual, or group is working in general.

And that's why we have disconnected workflows. And the execution-- that can be optimized with the tools we have. And we generally don't get it. But with that, as I'm from the AC industry, I have my own bias why my tools are better. But I have my friend Mani, who comes from the design and manufacturing background. I'll ask him. Mani, what do you think about this?

MANIKANDESWAR AMARANATHAN: Hey, I agree. So the statement what you made-- it's 100% right. At the same time, the issue extends beyond just that. In the design world, once the manufacturer receives the 3D data, they often have to recreate the manufacturing drawing from the scratch.

And this process disrupts the data continuity and leads to disconnected workflow between teams in various stages of the product life cycle. And according to industry studies, this fragmentation can significantly impact the overall product life cycle. It limits the ability to analyze new product design efficiently. And consider crucial factors, such as manufacturability, supply chain concern, material selection, production cost, and quality-- so all this or beyond this. Over to you, Yash.

YASH VYAS: No, totally concur with you, Mani. Thanks for aligning with me like this-- one of the times when you aligned with me. But the thing is, see, everything is causing us either rework or loss of time. And everything, if it goes in rework or time-- that is cost.

So cost is the biggest thing, but it doesn't stop here. If you look at this slide, most of the companies are working, as we mentioned earlier, in functional silos, like department head setup is the way that they have to work, and that's it. Very little attention is paid to the things like how the data will flow across the company and how individual employees would be entangled in the entire scheme of things. And the image is self-explanatory. Procurement are using their own set of things, manufacturing quality. But there's nothing that's common between all of them.

But if we move ahead, on an average, we use around 45 apps in a single day. But all of those data that we are using in these apps are siloed. We have a piece of software for every business challenge. And every different tool, as I mentioned, is serving to a different department.

But what's the cost? It is costing us time and money. And there are stats which say that people spend around 12 hours of their day time in just digging the data. And 30% of the time that people spend on their work is just looking for the right data. If we somehow solve this problem, we can tap onto this part of the lost time for our efficiencies.

So the challenge, if we try and sum it up, the obstacle in cross-industry collaborations are we have to manage multiple file formats because design and manufacturing set of people-- they have their own applications. [? Fair point-- ?] serves best to them.

The folks on the AC and the construction industry people on the site-- they would be having their own applications and software that they use. So the project coordination also becomes complex. And as we have a lot of tools, as I've mentioned into the scheme of things, data integration, data interoperability also becomes a challenge.

With that, we have a solution for this. We are at Autodesk. And we make anything, so why not this? So we'll talk about how we get the things done. But before we do the things, let's have our project stakeholders defined. These are the project stakeholders we'll be having a look at in our product demo as well.

So the first persona would be production planning. At a higher level, this is the discipline that will focus on the factory related elements. Then there would be a persona who will be working on the service-related or who's responsible for the MEP services, building services-related things. And then there is a persona who will be working on the building design-- maybe the architectural and structural element of the building.

So the approach going forward today is integrated factory model with our own flavor to it. And what the integrated factory model solves-- you have a single integrated model with data hosted on a common platform. You can keep the iterations iterative. And it is a continuous and interactive implementation. And as I mentioned, as we are going through a common thread, the cycle is continuous all along.

But with a smart factory, with Autodesk tools, we always encourage customers that you don't just plan into Autodesk. You build the things in Autodesk. And we have enough capability to support you to operate your things in Autodesk. So from start, from inception, to the end of life of any project or process, we are there to support you.

But today, we'll focus our discussion around planning and building side of things. So we'll have a look at a few of the things and how we have a connected workflow in here. Apart from that, if we just have a look at the product collections that we're going to talk about, so these can be categorized in into two segments.

One is product design and manufacturing collection. Maybe we'll talk about how we're using FDU Inventor and maybe the possibilities that we can have with AutoCAD and Navisworks. And the AC collection, for sure, will be leveraging onto Docs, Build Module of Autodesk Construction Cloud, and obviously, Revit.

With that, this wouldn't have been possible without the slide that you're seeing on the screen because the real challenge in the construction industry, when they interface with people coming from design and manufacturing backgrounds, is a variety of applications. And there is no better person than Mani who can talk more about this. Over to you, Mani.

MANIKANDESWAR AMARANATHAN: Thank you, Yash. So when we speak about AnyCAD, I'll split its benefits into five major categories and talk about it. One, interoperability-- AnyCAD enables seamless integration of different CAD formats, allowing designers to incorporate components and assemblies from various sources. And this is crucial in factory level design, where equipment and missionaries from different vendors may be used. And it overcomes the difficulty in integrating different CAD formats, preventing isolated workflows and promoting efficient process.

Second, data continuity-- as we mentioned earlier, by maintaining the integrity of the original data, AnyCAD ensures that the updates to the original files are automatically reflected in the assembly. This helps in avoiding costly errors and reworks caused by the data inconsistency. It addresses the challenge of maintaining the data integrity across the different stages of the design process, reducing errors and the need for rework.

The third is about collaboration. Any CAD facility collaboration between different teams and the stakeholder who might be using different CAD systems-- this is essential in an multidisciplinary environment like factory layout design, where mechanical, electrical, And Civil engineering teams needs to work together. And it breaks down the barrier to effective collaboration caused by different CAD systems again.

And the fourth is time efficiency. Eliminating the need for data translations, reduce the time spent on converting files and fixing the errors due to the conversion issues, and the data losses-- this accelerated the design process and allows for quicker iterations. It's solves the problems of time-consuming data translations and error correction process, speeding up the design workflow.

And finally, cost savings-- when we talk more about cost, that's one of the benefits what we get from AnyCAD. By reducing the need for multiple software license, minimizing errors, and rework, AnyCAD can lead to a significant cost saving. This is a key consideration for any project looking to stay within the budget. It addresses the high cost associated with managing multiple software licenses and dealing with the errors and reworks, ultimately leading to reduced project cost. Now, let's hear from Yash on how AnyCAD plays a significant role in enhancing the connected workflows. Over to you, Yash.

YASH VYAS: Thank you, Mani. So the real challenge with the design and manufacturing folks, when they used to interface with the AC, was multiple file formats. But I think Mani has this thing sorted for us. So with that, let's talk about the real workflow of what we're going to look today.

So the workflow we are talking about is-- I've kept this slide as quite simple. The name depicting is self-explanatory. We'll talk about connected workflow. Just to give you how this workflow would work, so we'll start with AnyCAD data. This would be your inputs, but we understand that there has to be some sanity checks in review before we start and use consuming the models.

So we'll have a look at the review workflow of how we're going to do that. Then from review workflow, we'll have a set of approved files. These approved files would be used to maybe create packages. Mani will show you how he's doing the model processing, and that's making my life easy to take the things on Autodesk Construction Cloud.

The approved file set will again go on to design collaboration, will do certain things with ACC. We'll speak as we'll be going through the demo. And there is this interesting QR code. We'll be using this during the demo. And it is there. It is linking with the asset system. So we'll be using this during the demo, but more to see about this once we are into the demo.

But before we move to the action, this is the ACC integration that we're going to talk about. So you can see that there is a building element coming in from Revit. We had a building. We have a MEP services model in here as well. The only piece missing here is the factory model.

And that's how we're going to solve it. We'll talk about how FDU in Inventor can cater to your factory model workflows. We'll move it to Revit. Everything is managed in Vault. So people who are using Inventor-- they are very familiar using Vault. For fair reasons, that component life cycles and version management for a DNN setup is seamless in Vault. We are not disturbing them, but at the same time, we are using ACC to take the things ahead for our AC folks.

And once all of it is done, you can see that everything's published to AC, and will achieve our IFM model at the end of it. So we've talked enough. We have all the slides. We have talked about a lot of numbers, but nothing makes sense if we don't have a look at the things in action. So let's just jump to the product and see how we're doing it here.

So as I mentioned, we started with our input files coming in from AnyCAD. And we'll talk about those input files. So for the input files, we are leveraging onto the ACC Docs module. If you see, I have a folder structure in here. And if I go to this folder, you can see I've created this folder called Building Incoming. This is the place where we would be having all the files coming in.

And if you see, if I show you, I've already created a review order trigger on this. There is a review called Factory Model Incoming. If I go to the reviews, and if I show you to the settings, we have already created a workflow that calls this factory model incoming. Again, this has a workflow, which is a one-step approval workflow that we're going to talk about.

And we are using this workflow to review the files once they are hitting our system. We are also copying these files into the system once they are there. So we are making sure that there is no human intervention to create a review. So let's just try and put the things onto the platform.

So if I go to my work-in-progress files, if we go to the folder, the moment anyone uploads any file to this particular folder, a review is created. And that's how they work on that. Yeah. So say if I upload files from a computer, it'll open up a few things. Download this file.

And if I open this, it will upload this file into the folder. It's a small file, should not take a lot of time. Once it is done, you can see that it's processing in here. It will change the version of the file, but more importantly, rather than changing the version of this file, what you will see in here is it will trigger-- so you can see that the file is uploaded, and a review is created.

You don't have to do the review and do the things manually. All of it is taken care of by the review order trigger process. Now, the review that was created was review 3. And this is the review that is just created. And the files, as we were going through the reviews-- we talked about-- that would go into a certain location.

So this is the place where the files would go into the published model. And this is the place where we'll be having all the files. We can see that we are having V1, V2. You can also have multiple reviews for the same version of files. And you will have a version management consistent and managed in here.

So once we approve the file, it should be V3. And it will create a new version of files. So let's jump back to the review. I'll open this review. I'll start the review now. So I've started it. This is a one-step review workflow, but as we are on to ACC now, we can leverage onto all the capabilities that we have in terms of review workflows.

We can have up to six-step approvals and four-step approvals. So it's limitless, in a way, how much you can do with ACC. So I've opened this file. So I'll have a look around. I can see. And I check that everything's all right. So the files is here. The model should load. OK, perfect.

So we have this control panel equipment thing in here. I've checked that things are looking fine. The geometry is as per the things. The appearance and the properties are in there. OK. It should be approved. I see that it's all good in there. I've approved this file from here. You can see that the review status is approved in here. I'll just submit this review.

I'll add a note that it all looks good. And I'll submit this. So there would be a persona, a design reviewer, or a design manager who will review the files at the start of this cycle so that the team that's working on it don't spend a lot of time closing and reviewing things.

You can see that there was a notification which said that review was closed. You can have all your reviews consolidated in here with certain things. You also have a timeline of sorts in here that gives you a real-time progress of where the review stands, how much of it is completed, how many files are there, and a few more things-- next action, due date, all of things.

So we are in ACC, so we assume that all the things that are related to ACC are taken care of when we are talking about this. So as I mentioned the things would go into the building approve file. The version 2 has now become the version 3. And this is where I'll ask my friend Mani to take it over. Over to you, Mani.

MANIKANDESWAR AMARANATHAN: Thank you, Yash, for walking us through the entire workflow on the review process from the ACC side. And you are able to see I've opened the ACC Docs here. And we are able to see the files which got approved recently. But at the same time, I want to show that that can be seen in Vault.

And you will be wondering how that is possible. Now, I'm just going to walk you through how to set up ACC and Vault integrations. So to start with, we have to just go with Tools and go to Administrations, Vault Settings. And you are able to see the screens here. So Collaborate. And you are able to click the Configure under the Project Sync management.

So all we need to do is we need to map our folders here. And that is about this cloud drive mapping. Just create a new, and you are able to define-- OK, let it be IFM project here. And you are able to see certain options here-- whether you want to enable this cloud drive mapping, and do you want to have a manual sync here, or do you want to only upload the related files based on the release by us, or include this in documentation files.

And not only that, the initial thing what we have to do it is-- we just need to go to Vault Folder Selections. So this is where your root folder will get selected, where you want to do the sync between the Vault folder, as well as the project folder for ACC. So I can go here and choose the ACC locations and click on the project files.

And what are the folders you want to sync here? So you can click on the scheduled folder sync. You can click on the folders. So within that root folder, if you want to sync any folders specifically-- for example, here we were talking about the published equipments, right? So I'm just going to show the published one from ACC. So I'm creating that particular folder.

And there are always these three particular options. I'll give a quick brief about it. When I say upload to cloud drive, there is about only from Vault to ACC. It acts as one way. The files from Vault will go to ACC. And this is about download from cloud drive that is nothing but from ACC to Vault. It's, again, one way from ACC to Vault.

And the final thing would be bidirectional sync. It's about Vault to ACC and ACC to Vault. It will always go to and fro. And you can make sure you can apply that action to the subfolders also. And you can even sync data and files here. OK.

And not just that. Here whenever we say this, so we have an option called Schedule. And this is about the automated way of getting your sync done. So if I start my day at 9:00 AM, I want my files to be at 8:00 AM. Then all I need to do is just change this time to 8:00. And then every day at 8:00 AM, you will get the sync done before your start of day.

Or else, you can choose every eight hours. That's a minimum. And you can still go up to any limit. You can go to 12 hours or 14 hours. Depends on our needs. And if you feel like you don't want a Project Sync to be done with the scheduled one, you can always prefer none. That means you will end up having a manual sync, but I'll explain what benefit that has.

And the final thing about the filter-- it is not necessary that you need to download or upload every files in that particular folder, right? So you can always go and filter it out. With respect to file extensions, you can save that DWG file alone. Then only these extensions which matches this criteria will upload the files or to and fro works.

OK? And this is all about how do we sync here, but at the same time, if there is any manual push which we require-- because we don't want to wait until the schedule happens because it's every eight hours or it's the time-based one. So I don't want to wait until that. The next one would be if I want to download anything from the cloud drive, that is nothing but our ACC environment.

I just want to do only one thing. Just click on this. Download from cloud drive. So this is the immediate update because we do have an email notification between ACC and Vault, which helps us understand, OK, the file is ready. If you want to proceed now, you can do that sync right away. So that's the one which I'm doing. And I'm clicking on the Publish Equipment.

And then when I click Next, so that shows all the files related to that particular folder. And I just need to click, and then download. So when I click on this, you are able to see that in the job queue, that means the job browser will schedule all these things. And it runs via job processor, and syncs happens. OK?

And this is how the sync between ACC and Vault works. It's just not limited to only download from cloud drive. I can even send this file-- for example, if I want to send my manufacturing drawings once I complete that, I can click on that particular drawing and then upload to cloud drive for the immediate sync, like how we did for the download from cloud drive. OK?

Now, what I'm going to do with this-- I'm just going to open this particular file in my way. And you are able to see that when we say manufacturing way of working, the Vault will have the lifecycle states, and the revision managed, and everything over here. And based on these life cycles, we are able to process everything when it comes to [? WAP ?] review, release, or archive any manners.

Now, I'm just going to do Open. When I open it, when I check out it, that goes to the Inventor applications. And over there we are able to just modify things. Or in order to just retain it, what I can do with this-- we don't need to modify anything. I just need to create a manufacturing drawing out of it.

So there are more things to do in Inventor. I'm just going to restrict myself and show very limited things which we can do right away. So you can actually right-click and go for Create Drawing View, where you are able to have a templates or automate this entire process with logics.

So when I say templates, you are able to see that there are templates where I just need to click on this. And these views are created automatically. And not just that, I'll also show you this. Whenever we do that, OK, we are able to do all the dimensions and mappings, and all the fabrication details, and the BIM list for that, everything.

So once we are done with this, all I need to do is check back to Vault. So once we check back to Vault, you are able to see that in our Vault environment. And that is the site EW. So you are able to see that here. And you can even view that over here. And if you want to do any mock-ups who doesn't have Inventor, they can do everything here.

At the same time, as I mentioned before, you can upload to cloud drive, or you can wait for the manufacturing-- or we can wait for the scheduled sync. Yeah. OK. And now, I'm just going to show-- so once the schedule is open, you are able to see that sync here. And you are able to view that same file in ACC also.

And this helps us, the site engineer or BIM engineer, to know what is happening in the manufacturing world, how the manufacturing goes, whether the fabrication drawing is released or not. All this connectivity would be here. And once the file is released, that will also send a notification to the people.

So after this file gets published in ACC, it is not just limited to the fabrication drawing here. We are talking about the factory design utilities a lot, right? So when we say factory design utility a lot, I just want to show a workflow which includes the factory layouts.

So before getting into that, I'll just give a glimpse about what exactly these factory design utilities are and why that is special. The factory design utilities in Autodesk Inventor offer a significant benefit for manufacturing and factory design, including streamlined layout designs, access to the comprehensive asset library-- so when I say asset library, you are able to see there are plenty of asset libraries with respect to automotives, or with respect to any paper industries, or with respect to any process, equipment, or conveyors.

So you have inbuilt libraries which you can directly use and then click and place it here. So that's one thing. And this is not just limited to the asset. It has interoperability with AutoCAD. So you can first start your design with 2D layout. And when you move this design to Inventor, it will have the 3D views. And it creates as a 3D layout. And you are able to enhance the visualization and analyze and integration with the factory design queue. And these tools collectively enhance efficiency, accuracy, and collaboration in the factories in object.

OK. Now, I'm just moving back here. So this is the factory layout which we have created in the FDU. So once I'm done with this particular factory layout from the production planning side, what I actually need to do with this-- I can either send it to the Navisworks, or I can even do the Export to Revit.

So when I say export to the Revit, that actually maintains not just exporting the data. It maintains the relationship till the end. So when I say relationship till the end, if I do any modification further to this particular factory layout, it still maintains that particular connections. So when I update here, that syncs with our Revit file, which stays in ACC.

So again, the sync happens with the Desktop Connector. So whenever we say Vault and ACC, there is a bridge which connects with Desktop Connector, so Vault files go to the Desktop Connector. And Desktop Connector syncs the file to ACC. That's one bit. I just want to make it clear here.

And once I click here, you are able to see the Revit file got export. And we are able to see all these things getting seen here. So whenever we do such activities, it makes sure the file is checked out from Vault. And then it creates the exports. So that is what is happening in the background right now before that export happens.

So once this has been done, I'll just quickly show you how the link is maintained. Then we'll see the action in the ACC. So this export is done. Then I am able to show the link. And this will store-- for example, I'll also move to the ACC and show where exactly that shows. And then I think--

YASH VYAS: But doesn't this get interesting, Mani, that I'm getting to see all the things in ACC, and I don't have to learn how Vault and Inventor works? I'm quite sorted in here.

MANIKANDESWAR AMARANATHAN: Sure, Yash. So that's the way of working with collaborative way. Right? So that's really cool. And yes, I believe I will hand it over to you to take upon how you utilize that Revit file in ACC and then do it. One final check. I'll just check-- OK, that's still happening. I'll just make sure. OK.

OK. Let the sync happen-- so once the sync has happened, it is always maintained the link. So that is how we explained it earlier. And that is how that works. So now, I'll give it to Yash to walk you through on the next side of Vault, not only about the collaboration, right? So now, the site engineer and the BIM engineer-- to collaborate that and enhance their coordination process. Now, Yash will explain how that works in the ACC environment. Over to you, Yash.

YASH VYAS: So thank you, Mani. I don't now have to bang my head into how to make things work in Inventor, how to make things work in Vault. I have all my Revit models in here. And that's it. I can take it, head for the ACC lifecycle as usual. And that's what we're aiming for.

So this was the factory layout that Mani did create. I'll quickly open it on ACC Docs Viewer. One good thing while using ACC Docs Viewer is we have support of over 70 file formats. So even though we are not using this as a common data repo to and store the things, this is much beyond that. You get all the functionality in terms of creating issues, going to the model properties, creating sections, and whatnot.

So we're getting the best of every world in that way. So this is the factory layout that Mani just created and pushed through Revit. And the Revit model is collaborated on ACC. It can be a cloud model, cloud worksheet models. You name the usual AC workflow. And this supports it.

So this was the factory model that we had in here. Apart from the factory model that Mani just pushed from Inventor, we have architecture model as well. So you can see this folder structure. We have a factory equipment model. We had a building model in here. And we had a combined services model as well.

So we will link all these models coming in from various disciplines onto ACC using design collaboration. But before I move to that, we'll talk a bit about what Mani created. There was a drawing there, which he created out of a control panel. And that's the game-changing thing that we're going to do today.

Mani utilized all the good things that were existing in Inventor and Vault, and took the things onto the ACC. And for someone like me, who is not an expert on, say, Inventor or Vault-related workflows, I still have these files. And I can use them for my perusal. What I did was I created a package from these files.

So I created a control system packages. For my friends who are familiar with BIM 360, so there was this thing called Sets in BIM 360. So we have created these packages. We can link these packages to certain items in a later stage in the workflow, but we'll talk about it. So I'll come to that.

So once I have the files, once I have the reviews, I can create issues. I can do the things usually I'll do in a typical Docs environment. With that, I'll move to the next piece into the story, which is design collaboration. Now, I have my models coming in from various disciplines at ACC, be it, say, factory or be it MEP services.

I don't have to think or ponder too much about the file formats and everything because we are working in a connected environment. And every change that is even happening in, say, Inventor is reflecting into Revit, and can be reflected into ACC in real-time. How cool is that?

So if we have a look at the project timeline, you can see building services and factory equipment things in here. And you can see there are certain packages shared by the teams. This was a challenge previously when people were working in silos because there was no common platform to share and collaborate on data.

But now, we have a trackable interface, where we can not just share the data. We can collaborate all the things coming in from various domains together. And we also have a timeline to keep track of things when they came, and everyone is on the latest and greatest revision of the data. So no more searching through the email mailboxes and downloading the attachments. Everything is coming in seamless starting from your Inventor, Vault, or things move to ACC. And we'll talk about the design collaboration.

So what design collaboration does is apart from your usual document consuming and sharing workflows, we also have these things where we can create consolidated project models in here. You can have a look at few things you can define. And you can also turn on this color. And you can see what thing is belonging to what discipline.

So you can see I have all my services. Model is colored as green, but rest of my vector elements are colored in magenta. Isn't that cool? Apart from that, you can have and work on faces, levels, content, browser. I won't go into the details of ACC module, but the idea is to show you how you can take the things right from the design stage to a collaboration stage onto ACC.

And it just doesn't stop here. You can do all your document consumption and design collaboration workflows in here. You can use the rest of the modules that ACC offers, but the idea was to take you through a connected thread across the workflow. Once we are done with our collaboration, the next usual step is we'll move to the model coordination.

I have this thing already open in my place so that we don't take a lot of time and things getting loaded. So this is the place where you can do live clash checks when the things are consumed and you you've gone through the design collaboration workflow. As the natural progression says, you will do a coordination in terms of clashes.

Previously, if this was to be done, there were multiple files that has to be collected in some applications, like, say, Navisworks. And then you were doing all your clash checks. With ACC, you have your clashes real-time. Any given update in any model at any point in time, you have your clashes.

So you will get this clash matrix in here. And if I open any of the clashes from in here, I get all the capabilities that model coordination module that brings to my table. And that's it. It will load the model. I can review the clashes of various disciplines right onto the cloud. I don't have to jump to a different application. I need not to be an expert of any other app or file format, for that matter.

I can review the clashes. I can group them the way I might be doing in Navisworks. And I can resolve the clashes back in Revit or Navisworks. Maybe using Revit and Navisworks issues [INAUDIBLE] resolve this, but again, the intent is to show you the possibilities. And we can always get into details at a later stage on how to do that if that supports [INAUDIBLE].

So we can visualize the changes, clashes in here. And maybe we can create an issue like a usual workflow, a clash issues, and things like that. And that's how we'll coordinate our model. So apart from that, once you have your clashes, you have your things back resolved in Revit Navisworks.

And this iterative cycle would go until we reach a stage where we have the coordinated model. Now, we are at a stage when our models are coordinated. And that's when we'll be jumping to the field. So for this, we'll be using the Build module. Again, you can see everything in ACC is coming through a connected workflow.

And Build is the place where we'll be using the assets. So all the assets that Mani created in Inventor are getting carried over in ACC using Build. And even to assets, we can create certain systems. So I've created a controller system. I've created a conveyor system.

So right from the place where Mani was talking about that control panel and he did export a drawing out of it, I have those assets classified into an asset system. You can see that. So if I open this thing, I can see the asset that will get loaded into the model, but in the meantime, I've added that reference in here.

So even if I create a package of any particular asset drawing, I can link that package so that we are in a connected flow and things are not getting lost just in your mailboxes. So if I click in here, it will take me to the package, which I created for the assets. And those packages would be having all the drawings regarding these assets we're talking about.

In the meantime, while our file is getting loaded, I'll jump back to assets and talk a bit more about how we can leverage onto the assets functionality. So we have talked about how the asset system works. We've also created the settings because we have created certain custom status set.

And as you can see in here, we have this factory equipment status set created. You can see the status here are not the regular tracking way. Every industry has their own way of working. And factory equipments have their own way to track the commissioning side of things.

So you can see we are doing robotic movement checks, equipment checks, sequence checks, and whatnot. So once we have created the status sets, we'll use this to track the things onto our assets. With that, I'll again jump back to assets. I have kept these assets open so that we don't have to reopen them again.

So if I open any of these status, you can [AUDIO OUT]. Once I click on that model, you can see I have all the things in here. And to add to your surprise, I can track everything based on the status color that we've just seen in the status setting. I can collaborate on issues right into it if I want to isolate the asset with the rest of the model is what I can do.