说明
主要学习内容
- Learn about maximizing collaboration between different teams through the use of Autodesk Construction Cloud workflows for megainfrastucture projects.
- Learn how to implement a controlled sharing environment to boost design coordination.
- Discover a Civil 3D data shortcut strategy to minimize rework.
讲师
- JCJoao-Guilherme ALVES CORREAJoao is passionate about fostering innovation and efficiency in engineering practices. With over 15 years of experience as a Civil Engineer and BIM Manager, he has worked on major international road and rail infrastructure projects. In 2018, Joao joined the Egis Group as a BIM Manager, where he led the digital engineering strategy at Egis design offices in Brazil and Colombia, contributing to enhancing Egis' reputation as a leader in BIM for infrastructure projects in these regions. In 2021, Joao transitioned to Egis' Rail and Transportation business units in France, working on research and development initiatives in digital technology. He drove advancements in team productivity through the deployment of collaborative and integrated design methods to support the implementation of BIM in international projects. In 2024, Joao completed another cycle within the Egis Group, joining the Egis Intercity Service Line as a BIM Manager for strategic infrastructure projects in Europe and the Middle East.
- AMAlexis MERESSEI am in charge of linear infrastructures software for EGIS, a multi disciplinary worldwide engineering firm. I joined EGIS Road department in 2008 as a designer though apprenticeship. For 17 years, I had the opportunity to work on exciting highways projects in France (A88, A63, CSNE) and internationals (Qatar, Peru, Benin). Civil3D user since 2013, I gradually became EGIS, Civil 3D corporate champion developing BIM processes and specifications to implement Civil 3D for projects. I have overseen company standardization, developments related to the automation of time-consuming tasks, and I delivered design and deliverables trainings in Egis France office but also in Armenia, Indonesia and Ivory Coast offices. I have taken over the governance of software benchmarking, deployment and production methodologies development in road and rail infrastructure application.
JOAO GUILHERME ALVES CORREA: Hi, all. We are here today to present the session mastering collaboration in high-speed rail projects with Autodesk Construction Cloud and Design Cloud work-sharing tools. This session is organized in four chapters, an introduction, project and process description, and the results we achieved so far. So let's start with some quick introductions.
My name is Joao. I'm really glad to be here with you. I'm a civil engineer and BIM manager, working for Egis since 2018. In my background, I have 15 years of experience working in major roads and railway projects. Currently, I'm working mostly with infrastructure projects in the Middle East region. In my day to day tasks, I usually work with Autodesk tools, especially Civil 3D, Navisworks, and ACC.
ALEXIS MERESSE: And I'm Alexis. Also, I joined the Egis road department, 16 years ago, and I had the opportunity to work on an exciting project in France and across the globe. I started as a Civil 3D user in 2015, then gradually became a Civil 3D corporate expert, developing BIM processes and specification to implement in projects. I have overseen company standardization and development related to automations.
Additionally, I deliver design and deliverables trainings in our international offices, and since April last year, I have taken over the management of software in road and rail infrastructure application. It's my second time at AU, because I presented a class on standardized data tool last year.
JOAO GUILHERME ALVES CORREA: So we're speaking about Egis. Egis is an ambitious engineering company ranked first in France and 16th worldwide, with around 20,000 employees globally and growing, we cover all disciplines from design to operations. Our turnover exceeds $2 billion thanks to the major projects we developed all around the world, and we are committed to driving innovation and sustainability in all of them.
So in Egis, we believe that digital transformation is no longer a choice. It's a necessity. We believe digital tools and processes should serve a clear purpose, delivering more efficient and sustainable projects. To achieve this, we combine our strong technical expertise with cutting edge digital processes. We continually refine this through ongoing training and innovations developed in-house at our digital and data factory.
By doing this, we ensure that we deliver projects that are not only efficient, but also truly sustainable. It's all about work for a better future. In Egis' business line transportation, our teams are responsible of major infrastructure projects, like railways, roadways, metro, and tramway lines. To support teams in these complex missions, we have a digital engineering team dedicated to develop tools and processes to improve their performance.
This team is basically composed of people with a mix of technical and digital skills from different regions and disciplines, encouraging innovation and disseminating best practices in all Egis sites. So now that introductions were made, let's move to the subject of this presentation. You know, this year, San Diego is hosting AU, but this city is also known for hosting another giant conference for the comedy world. Yeah, you got it. It's Comic-Con.
So why not combine AU and the comics world to tell you the history of one of our most challenging projects? This is the start of the Masters of The High-Speed Rail comic book, and yes, maybe you saw some similarities with the original Masters of The Universe. Of course, we love them. Here, we'll talk about how to use ACC and Civil 3D in a clever way to achieve a top class collaboration in high-speed rail project. But even if this presentation is about high-speed rail, at the end, you will see that heroes from roads, ports, airports, and other infrastructure segments can also take inspiration in this process, because it's fully scalable and adaptable for any major project requirement.
Let's start with the chapter one, the project. And sorry for that, but for some confidential reasons, we cannot give you the full context of the project. You know, this is part of the contract, but anyways, it's in a higher level. We are talking about the design of a new high-speed railway line in the Middle East. It's quite complex project, because, first, it's a high speed train.
So there are a lot of requirements that must be taken into account not only inside the stations, but also all along the railway line. And second, it's a very short contract, 12 months only. What is interesting in this project, it's that digital plays a key role since the concept design as client wants to gather information for the sequence of the project.
Well, the project was organized in three milestones, where milestone two and three are the most critical ones. We have three modes in each one to produce 100% of the deliverables, and remember, we are talking about a complete railway line. It's a lot of information to produce and to manage. This brings us to the second problem. I mean, if you want to produce all this information in such time, I really need a big group of superheroes. And yes, of course, we have it, 182 superheroes from 90 different companies and cultures, speaking multiple languages and working from different time zones. They are joining their force to deliver this full project in only 12 months.
Basically, the project headquarters, also know as DeCastro, is in one country of the Middle East, but its exact location remains a mystery. And we also have heroes from France, England, and India to help them to deliver magic models and plans. And, finally, well, I think that you know how it works. There is no superhero history without bad guys.
In our history, here, we have three of them, time, budget, and design changes. So this project is quite strategic for the country, so we need to protect it at all costs against the damage those three evil guys can do. I can give you a simple example of their powers. Middle East countries are known of their first development in these latest years.
There are new constructions emerging from the ground all the time. So almost every week, we had to do changes in the alignment to consider new constructions that were being planned in the railway corridor. And you know, if you change the alignment, you need to change everything. So you lose a lot of time, and of course, all that have impact in the projects budget. You see, it's not easy. So in these situations, you need a plan. You need a real process.
Now, we'll tell you how we prepared our heroes, giving them some mighty weapons to deliver this project. Well, everything starts with ACC. So how ACC can help us in the fight against these super villains? Let's consider changes first. Client requirements were, basically, Autodesk software.
So selecting deploy ACC was an easy choice. Things, like the possibility to sync both project and client project spaces and the integration, a new feature proposed by ACC when working with Autodesk softwares, are great. But we need something special, and ACC reviews feature gave us that. We'll talk more about that later.
Then you need to take into account the time you spent to deploy a solution like that. So it's a web app. You don't need to turn on the IT signal to call the cavaliers of the dark IT to help you with the installations. Then you don't need to be a master in the obscure arts of the common data environment to set up the project space as it's very intuitive.
And, finally, even if you have heroes who never use it, ACC, they can learn it fast. There is no secret. And, well, what about budget? So two powers caught our attention, the possibility to use existing licenses in each company, but also a special one, desktop connector, which allows our heroes to work in the day to day production for free, yes, you know, if heroes need to pay attention to their bank account.
Now, OK, serious part, how did we set ACC to receive a project of this size? First thing is that you need to be compliant with ISO 19650 standards. This group of standards will make your life pretty easier, even if at the beginning, it could seems to be a bit complicated.
So here, you have an overview of the main folders we set. Basically, we have one main folder to host all project management information, one to stock important communication with client and other stakeholders, a specific one for all inputs we received to start the project, and another one where we share training and support content. All these four folders are visible to everyone in the project, and then we have a final and magic one, the production or collaborative area.
So inside production folder, we have four specific subfolders. Work in Progress, which hosts the daily production to share the areas for, one, use it for internal collaboration. And the other, use it to share draft and preliminary content with the client. And finally, we have a published folder that hosts validated and approved files. In the end, it's the project's final repository. All that, of course, based on ISO 19650 recommendations.
Each of these areas have the same subfolder structure. Workstreams, Discipline, and Milestones. The difference is that our superheroes could organize their WIP folder the way they were used to, while in both shared and published areas, we have a rigid structure containing three specific subfolders-- Deliverables, Models, and Others. This will help us a lot later. You will see it.
So, OK, next step. You need to give powers to your superheroes. To set the proper permissions, we used ACC features, defining user rights according to their company, the workstream or discipline they are working, and their role in the project. Then, as spider was told, with great powers comes great responsibility. So in WIP folders, we restricted the access to the discipline level. It means if you are part of that discipline, you can see the folder and modify its content.
For all others, it's magically invisible, protecting all production files. In the other hand, for shared and published folders, we gave the visibility power to our heroes. So with that, they could use the models produced by other teams to complete their own ones. You see, this is what we call collaboration.
And yes, I know all this setup stuff is becoming a bit boring. So time to move to the interesting part. Let's talk about the collaboration. Keep in mind the objective of our mighty heroes here-- to win the battle against the bad guys. So they need to be able to produce the project, respecting the deadlines, be able to track and incorporate all design changes, and at the same time, save money and reduce rework. So to reach these objectives, we had to think a lot in ways to use ACC to facilitate the hero's task.
Think in the context again. We have different companies from different countries with different design cultures. For most of the heroes, it was the first time they were using ACC to deliver a project. So even with all superpowers, things had to be as simple as possible. In this case, why not use ACC DOCs Reviews as some sort of collaborative tool?
The objective of review is to be a quality control to-- but there is an interesting part there. It has a feature that allows our warriors to assign destination folders to validated files. And then ACC magically transfers a copy of those files to the preset destination folder. It covers exactly our needs. And I know you are probably waiting to ask me, but why don't you simply use design collaboration for Civil 3D and Revit?
The answer is simple. You always need to remember the three bad guys. With this new approach, we can have a single validation process for all kinds of files. No matter if we are talking about a DWG, a Revit, or in limits of C1. It's easier for all to understand that everything must follow this review workflow prior to a publication. Then when we use Review, we are adding a validation stage into the sharing process. People pay much more attention when they are signing a document, and that's exactly what happens here.
And finally, design collaboration costs a bit more than using the simple Review feature. So we have 180 people in this project using this tool every day. That can quickly impact the budget.
So, at the end, how this process works in a few words. In fact, WIP files will be always under WIP folder, and they can be updated whenever needed, day after day. We never change the name of these files because vertical control is managed automatically by ACC. Then collaboration happens every Wednesday. If there were changes or updates in WIP files, teams are requested to share them in the shared internal area.
So these changes are accessible by everyone, enabling early coordination and reducing rework. This process is repeated week after week. And every two weeks, we also share a copy of the draft shared of the draft models with the client so he can follow the project progress, and of course, make comments earlier, also reducing rework and the production costs.
And as teams are only allowed to reference files saved in the shared folder, it's simple to sync them with the production files. Let's use the example of the coordination model. We only need to define a link between the Navisworks file and the discipline NWC model in a single time. Then in the next week, if someone does an update in those discipline files, we just need to open our NWF coordination model to synchronize the changes. You see?
We also publish the coordination model once a week using a NWD format. This is the model we use for clash detection, model coordination, and issues management. And there, the magic powers appears again. Any changes in the NWC files can be quickly synced with the NWC one, and then we can easily check if problems and issues we identified before were revised or not.
OK, all that seems to be pretty easy and good, but you still need to consider some efforts to deploy this approach. First thing you need to consider is training people. But it seems that superheroes don't like long online training sessions. Yeah, that didn't work at all in our case. So we decided to change the approach and to provide quick training sessions two times per week where we had 50 minutes of training for a specific subject, and then 50 minutes of Q&R.
With that, we saw some good changes in the behavior of the teams, like a massive drop in non-compliant actions on ACC. At the end, we are able to train 164 people total, which is really good, taking into account the amount of heroes working in this project. And of course, to compliment the training sessions and let the heroes more autonomous, more detailed documentation was produced, including step by step guides and videos.
And to be sure that teams could always find someone available to help, we deployed a new support network with at least one champion in each region. With that, communication was facilitated, as our heroes could speak in their native language. But also, we covered 100% of the project working hours as there were teams working from Sunday to Thursday and others from Monday to Friday. You see, even heroes need some time to rest.
So serious time again. Feedback time. We decided to use the end of milestone 1 to evaluate the performance of the project, and it was not good enough. We started the project with a common group of three review workflows that were used by all teams. The problem is that when a hero creates a workflow, he was obliged to set three different things-- the destination folder, the technical validator, and the quality checker. But we saw that many of them were picking wrong options, so the result was not perfect and things were getting messy. You see, it was like a rusty sword. It does the job, but you still suffer.
Then for milestone 2, we decided to create some twin review workflows for each discipline, already setting the name of the validator, the quality checker, and the destination folder. That was a game changer, as the process became simpler to all. Like a super mighty, brand new sword. And at that point, we had a standard process to share information that was working pretty well. But to meet all project goals, we had to work even better. We need more power. And that was the start of a quest to find the best weapons to improve design production using Civil 3D and model coordination with Navisworks and ACC.
Let's start with the Civil part. And you may know that when we talk about collaboration in Civil 3D, we must talk about data shortcuts. I think that you may know what they are, right? In other words, it's a feature that allows us to share Civil design information like alignment, corridor, or pipe networks, referencing them in a dynamic way with other files. I mean, it's capable to identify, alert, and synchronize design changes when they happen.
And in a project of that size, we cannot simply let the heroes create data shortcuts the way they are used to. In fact, we had to define some rules, especially to avoid the bypass of information, but also to be sure that all changes were taken into account. Deadlines are too short to assume these risks. Let me try to explain the trick.
Well, let's go back to the Discipline WIP folder. Each team has to define a data shortcut inside its own WIP folder. They can link their own files with that data shortcut because they are the masters of that information. But to get information from other teams, they are obliged to sync their data shortcuts with file shared in other disciplines' internal shared folder.
Copy a file from other internal shared folder to your own WIP folder is forbidden because this breaks the synchronization loop. With that, there is no way of missing any design changes because your data shortcut will always make reference to the most up to date file. To let it clear, look at this example. Here we have four disciplines-- Alignment, Tunnels, Track, and System.
When Alignment does a change, it is published in their internal shared area, and then teams can read the information there. Then Tunnels and Tracks produces their own models, and it works the same ways. When published, systems can read the shared information. So let's assume that in the week after, there is a big change in the Alignment. As everything is linked, the review process is way faster. You see it.
With that, our mighty heroes were able to be much more efficient producing their models. But again, we always need more power or some sort of magic to help us with the design documentation, as it's one of the more time-consuming tasks in the project. So time for you, Alexis. Please show us some tricks to forge an even might hammer for our heroes.
ALEXIS MERESSE: OK. Thank you, Joao. So, yeah, I have things that could interest you, I'm sure. So as I said, I joined logistics 10 years ago. I was a draftsman, civil road designer, corporate B2B trainer. So I'm familiar with the problem faced by the 800 Civil user attaches. And when I joined the DB Department, I saw that we able to respond effectively to project problems through automation, but that we are never really looked at common problems.
I also realized that through BIM project are reinventing work processes, traditional deliverables-- I mean plain view, longitudinal profile view, section view. Yeah, they are still necessary elements in the life of project. And in this chapter, I'm going to tell you about the solution we've put in place to automate them.
So this is the initial findings. These tasks are time consuming and repetitive, require a certain number of clicks, parameters to be filling, and navigating between several windows. Project changes on this type of document leads to the risk of errors and a lack of uniformity sometimes. And finally, this task are often with low value added, and our users are more interested in spending time on design than in plan editing.
So we are faced with a common finding. I mean, regardless of the type of the project, we clearly need to improve the efficiency and make the user experience more comfortable. And what is great about Autodesk products and with Civil 3D in particular is their openness to different forms of development.
You can use Script, LISP, Dynamo, but we choose the .Net programming to ensure maximum user experience, and we opted to develop a plugin with Autodesk Consulting team in France. And we did it. I am so pleased to present our deliverable automation plugins.
So it currently automates three types of deliverables. The first one is the creation of longitudinal profile view, which simplifies and optimize the process of creating them, then the same tool but for the section view with a special feature for plotting, and finally an advanced management tool for xref and layouts. To explain how these tools revolutionize the way we deliver, let's take a closer look on the section view tool.
But just before a quick reminder of what section view is. So this is a cut of corridor which displays infrastructure information like surface, pavement structure, 3D solid blocks. And this element, so in the upper section, represented by styles or can be labeled.
In the lower part called the data band, set, it's present elevation and distance values. This information is retrieved from the surfaces. Here, information on natural ground terrain project of subgrade.
The number of sections used depends on the frequency with which sample lines are applied. For an example, with a frequency of 20 meters for 50 kilometer long project, 2,500 section views will be generated. So it's a lot.
Well, so how are these elements generated? We need to define all this information, select input or output for the style, surface association, and so on. And you have to repeat this for each sample line groups and elements in your file.
This can be very time consuming if your project contains multiple alignments, 10 changes, or roundabouts. So we decide to group all these together in a single window applicable to all alignments in a single drawing. And here it is.
So it's divided into three parts. The upper part, so in green, contains information taken from the traditional method but reduced to a minimum. So the user should not need anything more.
You choose the template, scale, paper size, and few styles but nothing more. The rest of the information is now integrated into a parameter file, as they are often identical between projects. Then the element selection at the bottom in yellow, which enables us to create drawings for simple lines group included in the file but with a single click, and last but not but not least, the section display setting, which allows us to automate the association of surfaces with data bound sets.
Let's take a closer look to this one. Because one of the most causes of error and wasted time when creating section view, it's association with the wrong surface to a data bound set. This information is crucial for obtaining the right information, such elevation values.
How to automate this association? By simply searching for a matching word. If the name of the surface contains top, then it will be associated with the data bound set style that contains the word project.
And we can also manage the label and super styles. That will be represented in the section views. We can do that for natural ground surface, data surface, and many other surfaces you may need. Sure, this configuration file will be applied to all sections in the drawing at the time of creation, regardless of the number.
OK, so that's a lot of information and better than explanation. Here a video of it works. So this is the default process.
You can see there is a lot of information to be filled in and a lot of selection to be made by the user. Here, just the styles. And that's what I mean by surface association. You really have to be careful. Otherwise, the information will be wrong.
The process is now almost finished but just for one sample group. Then you have to do it for the other one. Now let's do it on several alignments in less time it takes for one with the edges deliverables plugin. So, this new process, you just have to manage different styles, select the paper size, select choose all elements you want, and click on OK.
I just wait. It's very fast. Yeah, I think it's done.
And this new process is remarkably effective in combating our super bad guy. And I want to feel it. Watching the smile on the face of our superhero is wonderful.
And let's continue with section views. We have just seen how to automate creation, but what about PDF plotting? So you need to know that you want to generate one section view per sheet.
This can represent hundreds or thousands of PDFs. But what is the problem? In fact, if you want to generate using layout tabs, we are limited to 2,051. This severely restricts us because we have to split our design into several files.
For 40 kilometer long project, so we need to create 10 files, and this method is not really adapted for us. We optimize this process by generating our section view in the model space, exporting to AutoCAD, and using a list to plot this in PDF. But however, the more section view the files contain, the more IEC element it contains and so the longer it takes to export to AutoCAD. And yeah, the user is blocked during this time.
All he has to do, in fact, it's just to wait until the end of process. And finally, how does need to be redone if the design has changes? We are fully automate this step in background.
The user can now continue his work, close this, file and open other. He will be notified when the PDF are available. And nothing better than a new video to understand the power of this feature.
All you have to do is launch a new command. Select the section to be plotted and wait for the PDF to become available. You are free to move on. Just the message will alert you as soon as the process is complete.
Yeah, and so we also apply this philosophy to the production of longitudinal profile view. But I'm going to pass this one because it works almost identically. And I'd rather talk about another important subject, which is harmonization of rendering.
As Joao explained very well in the previous slides, our team are present around the globe. This means that in addition to templates, we have to provide to our user a tool helping them to homogenize the rendering. The aim is to avoid this type of rendering, teams working on the same disciplines with the same sources but applying different references, display orders, or applying different layer filters.
And clearly, better management of our xref requires robust standardization. And at edges, this is evolving day by day. This year, we introduce new elements that link protection folders, files, and layers.
This is a classification code, and it's used for all projects regardless of the design, software use, or disciplines, if you are working on rail, road, or inbound projects. And this one is a key element in our automation process. We use this one to automatically order the references in a file. In other words, if I integrate 100 references, delete some, add new ones, which it was we usually do on a project, the tool will always order the references in the order defined by our standardization.
So display order is defined in the configuration file and deployed on our user workstation. It recognizes the classification code, presents the reference name, and places it correctly among the other references. We have also created a plugin for layer filter. If you need to share a particular display or modifying color, line styles for particular rendering, it's now so easy to do.
Once again, there is nothing better than a video to illustrate this. So you can see that my file contains 85 references. So just run the command. It recognizes the classification code using the name and automatically positions them to a simple click.
That file displayed too much information for my type of rendering. I therefore use a layer filter plugin to hide what I don't need. I run the layer filter, select the right config file, and update, and that's all.
Of course, this configuration file are shared with the company or with the project. I forgot something about reference layer. When they are attached, they are associated with the current layer. Now this plugin solves this by assigning specific layer to each references.
Well, it's time for me to close this chapter. With the automation, I use edges, but I've selected the most emblematic ones which are open to all type of project and which drive me in my job. That is to improve the experience of our users by simplifying processes and making them more efficient by proposing solutions that limit risk and error and using as far as possible our standardization and by enabling our users to work on tasks that bring a better syllable rate. Until we come back to LI later, I will hand over to Joao because Joao, I think you have a one last trick to show us.
JOAO GUILHERME ALVES CORREA: Yeah. Of course I have, Alexis. We still need to talk about model coordination. And when you talk about model coordination in an Autodesk environment, we are basically talking about ACC and Navisworks.
In fact, there are some ways to access and view models using these tools. Sees the complete free one to a 100% web solution. We decided to stay more in the middle in our case, using features from ACC viewer and the combo between Navisworks Manager and Desktop Connector but of course sharing binding issues on ACC to assure that every single user in the project could have access to that information. With that, we had an online viewer available for all everywhere, but also a single tool to run most of the BIM uses.
We decided to don't activate clash detection, neither QTO in ACC, because it increases the synchronization time in the web server. And here, our objective was to have information shared and ready to be used as fast as we could. So if you want to be a wizard in model coordination, you need to define a good work breakdown structure. In this project, we have 150 different models between discipline, coordination, and federated one.
It's a lot. So usually in this type of long, linear, and complex project, we use a first level of coordination where we split the project by assets like stations, depot, or railway segment. For each of these assets, we define a coordination model linking all discipline models that are a part of them. And with that, we can have a first coordination check, verifying clashes and interfaces inside that asset.
Then we need to go to a second level of coordination. And to do that, we use the federated model. In this model, we create links with all coordination models so you have the full overview of the project.
Then in this level, we only check clashes and interfaces issues between the assets. And of course, you don't need to wait until the first level of coordination is completed to start the second one. I really like to use this process because you can assign different heroes for each coordination level. It's way easier to manage them.
So the tricky part-- on ACC, there is a magic workflow that maybe will help you to save a lot of time when doing model coordination. All you need to do is to activate the model coordination feature, then define a single coordination space for the whole project. In our case, we did that using the internal shared folder. So all its subfolders were automatically added as part of that coordination space.
Then you will create a dedicated view for each coordination or federated model, of course using the NWD file shared before. So with that, you have a one to many relationship between coordination space and views and one to one relationship between views and models. This trick regrets automated synchronization to your views when your model is updated.
Then, going back to issues, we use in Navisworks Manage and its coordination issues adding that allow us to sync issues between both tools. The advantage is that you can run clash detection directly in Navisworks and then transform clash issues in ACC issues. So they are visible to all, even for those who don't have Navisworks available in their computer.
You see, with that, you can even save some money just using this strategy. To create the issues in Navisworks, It's very simple. But instead of opening the NWD file, save it on ACC, you just need to load the view we created before. So as you said, whatever the NWD file is or whenever the NWD file is updated, your view will be updated, and you can check the results of the changes against the issues you created before.
We also deployed some Power BI dashboards to help us to check if shared files were validated but also to track the production progress week by week, identifying new, updated, unchanged, and missing models. Our dashboards can run this analysis per discipline and per segment of the project. So we can easily see when something is drifting. Report that to the Council of Heroes, and then actions can be taken to put the project back in the tracks again.
These dashboards are also used to feedback the MITP. So really, coordination tasks are way easier with this duo, ACC and Power BI. And now you know the full trick.
So, as time is running out, let's move to some results. First, let's start with some renders that we created from the project. Here, we used Autodesk cloud render to produce those images. First you see some models in the at grade segment. We used Civil and Revit to build these elements.
Then here, we have some bridges, and you see how amazing they are. And of course, a lot of coordination between Civil and Revit files were required to fix the interface between railtrack and the structure. And finally, a typical tunnel shaft in the section showing the interior of a station with its platform and the concourse area. This one, of course, were built using Revit.
And of course, you want to know more about the numbers. So this process helps us to save 80% of the weekly spent doing model coordination tasks. It means that from two days of work per week to check, share the models, sync changes in the coordination model, and update the MITP, we are able to reduce it to around three hours week, giving us more time to check clashes and control the models, increasing the overall quality of our deliverables.
And concerning rework hours in Civil, well, in general, for alignment, track worth, earthwork, and tunnels, the weekly controlled charrette process and the data shortcut strategy resulted in a reduction of 40% of the hours spent on sensing changes in Civil. With that, we reduced to almost zero the time spent searching new files, rebuilding xref and data shortcut links every week. A major win.
ALEXIS MERESSE: a word about how we'll save on our deliverables with automation-- so as you can see, these figures are significant. Now, 70% on section view, 50 on longitudinal profile view, 85% of the management of our xref layers. So yeah, sure, this may have to be set against the frequency of use, but all of our users benefit, whatever the project. And these figures illustrate an important step forward in automation and reinforce our determination to go even further.
JOAO GUILHERME ALVES CORREA: these were the weapons and tricks we use to defeat the bad guys. We hope you like it. And now it's time to major thanks to all ages and partners, superheroes who are working in this project. You know, we need to protect their identity at all so they can continue to save the world, but we'll make an exception for some few ones. First, my teammate Ana Gabriela, for putting his soul to transform the idea of linking Power BI and ACC into this powerful project management tool and reviewing the workflows for the milestone too.
ALEXIS MERESSE: I like to say a special thanks to Ajesh and Rob, who did a fantastic job on our automation plugins. They understood very well our needs perfectly. It was incredible.
JOAO GUILHERME ALVES CORREA: of course, Alexis, we cannot forget Damian, Arnold, and Lionel from Egis but of course Layla and Vincent from Autodesk. [NON-ENGLISH]. They gave us the full support to make this presentation happen.
ALEXIS MERESSE: you so much.
JOAO GUILHERME ALVES CORREA: we also need to thank you a lot for picking our presentation between all those nice options to start your AU classes. It was a pleasure for us to share our tricks. Our Egis heroes will be presenting more sessions in AU. You can find them here.
Also, if you want to hear more about this high speed rail project, I will be presenting a class at Autodesk Rail Summit in Copenhagen November this year, sharing more information about collaborative features involving Autodesk tools for model production. And of course, if you want to join our team of superheroes, don't forget to follow Egis in the social networks. We always have new opportunities for people who love to create, to innovate, and to design a better future. Thanks again, and see you soon.
ALEXIS MERESSE: you.