80,000 Cubic Meters of Concrete: Revit and Dynamo for Project Managers

ELISA BACCHI: OK, we will start with a short introduction to the company, and then the main speaker will be Bitetto, Fabio. I'm Elisa Bacchi of the Maire Tecnimont Group. I'm civil and architectural leader. And I'm leading the BIM system development in our company. And Fabio Bitetto is our main BIM coordinator specialist, in particular-- specializing in particular in underground design. But today, we'll show you one very good history about the concrete design applied to our main projects.

And-- OK now-- OK, just a brief introduction about our company. Maire Tecnimont Group is a multi-national company. We are operating in 40 countries and with 50 companies. We are about 80,000 people around the world, and we are specializing in industrial plant, our field are petrochemicals, fertilizer by power plant generation, and oil and gas.

Tecnimont is a company accompanied by sister company. And we are used to work in particular as main contractor following the entire cycle of our project, from feasibility up to basic and construction design, up mechanical erection, commissioning for giving to the client the [? plant ?] [INAUDIBLE]. And you can see just-- sorry. You can see in this picture the countries around the world that we are covering with our presence and projects.

In particular, our sector, the main sector, is on petrochemical plants and on fertilizer. And we are having very good result also in oil and gas. Now, we will show you one short video that is prepared for explaining you the big efforts that have been done from our company for implementing BIM system methodologies inside plant design, inside the 3D model plant design. That has a very old history in industrial plant.

The BIM system development has been done, in particular, for civil discipline. We've been engineering civil department, covering all the sub-disciplines of civil engineering. And when I speak-- when I speak about the civil [? submission system, ?] we are considering, for example, the underground sector, ground sector, foundation, elevation, concrete, the steel structure, and building design. You can see from this video that our plant has a very urban scale.

So this video-- OK, our [? renderized ?] video. But behind these 3D model objects, there is all the engineering that is valid for construction and implementing the BIM methodologies within our 3D model plant design, that is [? in ?] development. For example, using other important tool in oil and gas fields, such as intergraph, SP3D tool. I don't know if someone knows these tool, implementing the BIM system development, using, in particular, Revit.

We-- we are on the projects in the very early stage. And we are able to manage all the cycle of the project, from engineering of the procurement of the material and up to the construction. So we are thinking that now we are-- we have get a very good result for these implementation in our workflow.

Now, I would like to introduce Fabio Bitetto-- will explain you one [? history ?] of 80,000 cubic meter, about one of the most important projects that we are delivering now. The project is under construction, and it is located in Oman country. It is a petrochemical plant for producing polyethylene and propylene. And now Fabio will continue the presentation for you. Thank you.

FABIO BITETTO: Thanks, Elisa. Good morning, everyone. I am so happy to see all these people here today, also because it's the last day. Here you can see the learning objective of this class. So maybe you have already read all of these points. Today, we will see it, and we will understand how to plan, monitor, and determine the project progress and the construction work front, using Revit and Dynamo. We will learn how to use Revit in order to coordinate engineering and construction activities on a real mega project. We learn how to use a Dynamo to manage custom data, build inside your models, and in the end how to visually track your project growth.

Here instead, I summarize all these point, all the point that we will touch today. So I will start with a short introduction of the Orpic Project, our very big BIM challenge. Then, we will analyze the workflow of the civil department inside our company, regarding only the concrete part. So we will see families, main item model, and assembly model. Then we will switch to Navisworks, in order to see how use this tool for track your project growth. Then, the two that we will use in this class in order to monitor the project progress and how we can improve these workflow using Dynamo. So we will analyze, in depth, the Dynamo script that we have created, in order to monitor the project progress. In the end, we will see the relationship between the Excel file in which we have the S-curve and the Dynamo, and what could be for the development of this workflow.

OK, so let's start with the introduction of the BIM challenge inside our company, so the Orpic Project. Last year, we had the opportunity to take the challenge of the BIM introduction inside our company on one of the biggest project that our company ever made. So this is the Orpic Project. The Orpic is the client-- OK, oil and gas company in Middle East. The contract is the realization of our polyethylene plant and polypropylene plant. On an EPC basis, so it means that we have a contract-- we are contractor for engineering, procurement, and construction phases. In the end, the value of the contractor-- or contractor that is around $900 million. So as you can understand, it's a very big plant.

The project is located in Oman, in Sahara, near Muscat. And here, you can see the plot plan of the plant. So we have in the above part, the utilities and the off-site, regarding this part, in particular, for example, in the above part, we have substation dedicated to the process area. In the middle, in the real core of the plant, that is the process part, composed by a PP unit and a PE unit. And in the end, we have a very big logistic part, in which we have the product warehouse.

Just to understand, some data about the process area, composed by PE-- PP unit. The PE unit has two units designed to produce 880,000 tons by year, for HDPE and LLDPE-- an extrusion building, a blender product silos, auxiliaries, and the buildings and structures dedicated for this part. Also for the PP unit, we have extrusion building, [INAUDIBLE], an all building and structure dedicated for the production of HDPE.

Instead here, you can see p-charts, in order to understand what is the split of work and the engineering weights. As usual for our company, the main actor of the engineering process is the piping department. But the piping department is followed by us, so by civil. When we talk about civil inside our company, we are talking about civil, structure, building, and underground. Instead for the construction weights, we have the main character-- we have the main character, because we have civil works, site preparation, piling works, steel structures, and the-- OK, we are the main character for the construction weights.

Now I can't give to you the real number regarding this project for privacy for the client, but in order to understand the complexity of this plant, the plant is near 49 soccer fields. We are talking about more than 80,000 cubic meter of concrete and an elevation near to 3 Eiffel Tower.

Here instead, the split of work of the civil design and the main character of this changing is Revit, because as you can see, these are all the activities that now are already done in Revit, in our company. So site preparation, piling, reinforce and concrete, underground utilities, road and paving, and building. The only black sheep is the steel structure. That is made in [? Tecla. ?]

OK now, we will analyze the workflow regarding the civil design inside our company. When we are talking about civil design in our company, the split of work is in four civil sub-disciplines, so reinforced concrete, underground road and paving, building and steel. So as you can understand, the situation is really complex, also because we don't work on the same file, on a central file, but each sub-discipline as a [INAUDIBLE]. So also, we have divided the roads inside our company, because for us, the success of the BIM implementation relies on the people that actively involved into the project. So we have defined, properly, roles and responsibility, in order to have the full control of the 3D model and all the output related to the 3D model.

As you can see, we have a BIM engineers that our the main character of the civil model authoring activities. Then a BIM leader in engineer that coordinate all the activities of the BIM engineers. And in the end, the boss, the BIM coordinator that collect all the data coming from each sub-discipline and create the final output of our discipline, that is the civil master model. In our class, as I said to you, we will analyze only the concrete part, from the modeling to the management part.

Here are some numbers regarding the reinforced concrete structure of the Orpic Project. So we are talking about more than 200 Revit files. We have 20 people involved in the Revit model authoring. OK, so 20 people dedicated only to Revit model authoring. And most of these people are located in our sister company, in Mumbai. Then we have five assembly models, and we will see, later, which is these assembly models. And as I said to you, 80,000 cubic meter of concrete, more than 80,000 cubic meter of concrete.

OK, so about concrete part, this is the BIM workflow inside our company of the concrete part. You can think it like a chain, with these three cycles. The first one is families. Then, we have the main item model, so for each main item that populate our plant, we have one single file and one main item. In the end, we have the assembly model, in which we collect all the main items coming from each sub-discipline.

OK, the first cycle, so the families. For us, create your own families is very important, in order to have a BIM library and have the most used type already-- always ready for each project. The first step is the type of definition, so we defined the type name with a specific procedure made by Elisa this year. Then we have the material data. These are very important for us, because this data allow us to filter inside the assembly model, using the material. So if I want to understand-- if I want to monitor only elevation concrete or only foundation concrete, I can do it through this material data.

Then we have the geometric data, that simple define the shape of our object, and in the end, the target data. Also, the target data follow the same procedure of the type of definition. And these are very important, because in our big plant, we have a lot of objects. But each object has a unique item tag, in order to identify, in a very quickly way, all the information related to each single object inside the plant.

As you can see here, we have created several families for Tecnimont's project, regarding the concrete part. And you have to consider these, that we have a very big company. And for us, standardization is very important, because we-- the main and the aim of the company is to create and build the same type of plant all around the world. So for us, standardization is very important.

The second part is that these-- the main item model. What it means? That for each item inside our plant, we have one single file dedicated, in which we do model authoring activity, but not only, because we manage all the information regarding this main item. For example, in this picture, you can see the extrusion building of the PE process part of the Orpic Project.

OK, these here-- I summarized these four point, that are the main activity that we do with these file. So model authoring, deliverables, schedules, and in the end-- the most important for this class-- that is the project status. About model authoring, I can say to you that in this file, obviously, I've collected all the families that we have created. And in particular, we have created a lot of View Template, checking view, in order to make easier the use of Revit, because as I say to you, most of the people involved into the model authoring activities are located in Mumbai. So we have to be sure that each object is modeled in a proper way.

The second step is that of the deliverables, so each construction drawings is fully developed in Revit. For example, for the Orpic Project, we have produced more than 1,800 IFC drawing, fully developed in Revit. You can see here that in our drawings there are a section, isometric view, and shadows, and a lot of things.

So as you see, we have also schedules, schedules related not only to quantities. So for example, here you can see a schedule about reinforcement quantity. But we have also, for example, bar bending schedule or pile coordinates, that for us are very important because support the civil subcontractor inside the site.

In the end, the project status, so the main character of this class. Basically, we manage the information related to the project status on two levels. The first level is on the main item as it is, we can say. Because under the project information of each file, we have these parameters, the project issue date, the project status, the project name, the project status divided by foundation concrete, piles, and elevation concrete, and in the end the project description. About this division, I can say to you that for us, it's very important. Identify which is-- we track the stage of-- the status of the main item, in order to understand. If, for example, only piles are under construction, or are under construction also the foundation, et cetera.

The second step is that of parameters related to the instance. OK, so each instance inside these models, has attached these two parameters, that are project parameters. The first one is the engineering status, and then we have the issue date. So the issue date is really simple to understand, because when a modeler create a construction drawing, he simply select all the object in one drawing and input them manually the issue date. Instead for the engineering status in our company, we have three possibility.

The first one is IFB, that means issue for basic, so we are talking about a dummy model and our preliminary design. Then we have the IFR, that is in the middle. It means that the 3D model and all the output related to the 3D model are really for client review and comments. And in the end, we have the IFC status, that is maybe the most important, that means issue for construction. So the 3D model and also the deliverables are ready to be sent on site.

In the end, the last part of our workflow is the assembly model. That maybe is the most important, because the main activities that we do with this model is the data management. About this model, I can say to you that we link, so all the main item in one single file. Maybe sometimes, this file could be really EV, so you can split the plant in more than one assembly file. For example, in the Orpic Project, we have divided the plant with the five assembly file, in accordance with the division and the plant layout.

OK, the activities-- so data management-- but what data we are talking about? First of all, key quantities. The quantities that we monitor are piles, foundation concrete, elevation concrete, reinforcement, anchor bolts, embedded plate, lean concrete, grafting also, so a lot of key quantities. Here, you can see example of a schedule, in which we monitor these keep quantities. So you can see the project name-- the main of the main item, the project description, the material. So as you can see, the material inside the family is very important, because allow us to create more than one schedule. And then in the end, we have the total quantity and the project status. So this is the project status on the first level, the project status regarding the main item as it is.

Here we have created conditional formatting inside this schedule, in order to highlight, in green, the IFC status. We create inside these assembly model also 3D views with filter, in order to do a check and visually analysis. For example, here are four key quantities. We have created a 3D view with a filter that pick a particular parameter, in order to highlight, in yellow, the main item, with the concrete volume less than 20 cubic meter. In orange, the concrete volume between 20 cubic meter and 100 cubic meter. And in the end, in red, the biggest main item with red-- with the concrete volume more than 100 cubic meter.

AUDIENCE: [INAUDIBLE]

FABIO BITETTO: We have here, instead, the project monitoring. So what we can monitor with this assembly model, the 3D model activities, the engineering activities, and the issue of the document. Here instead, we have the two parameters related to each instance. So the engineering status and the issue date. And we have also the total quantity, obviously. This schedule is very important, because as we will see, we will use this data in order to create our curve and analyze the progress of our project.

Also for the project monitoring, we have created a 3D view with a filter, that in this case pick the engineering status, in order to highlight the IFC status in green and the red-- And the IFB status in red. Using the engineering status, we can create also views, 2D views and 3D views, for constructability. So in a very simple way and using only the default setting of Revit, we can use-- we can review the construction processes, using visual analysis and check. We can identify any obstacles before an item is actually built. And we can simplify the analysis and speed up the work at site.

These are some picture of the Orpic Project, so that is under construction. And you have to consider that all the deliverables regarding constructability are sent [? in field. ?] It's [? sent ?] directly to the civil subcontractor.

OK, how can use Navisworks in order to track this kind of information regarding the project status. So as you can see here, we have the same example of the Orpic Project, in which you can see, in red, the IFB status and in green-- in red, the IFB status, and in green, the IFC status. The tool that we use inside the Navisworks are sets. I don't know if one of you knows sets, but basically sets are groups that share common properties. It is very simple to create sets inside Navisworks, because you have simple to find the item, and then insert these situations.

So you have to select your parameters, that in our case is the engineering status. I remember you, the engineering status, so they're related to each instance modeled inside our models. The condition, that in our case is equal, and then the value, IFC for example. So using this tool, we have created two sets, the concrete IFC and concrete IFB, in order to visually track every time the situation of our project.

OK, now we see which is the tool that we will use in order to analyze the project-- the project status. The tool that in our company we use is the S-curve, because using this tool, we can track visually, every time, the project progress. We can quick identify the project growth, the slippage, and if there are potential problems. And we can create a historical record of what has happened-- sorry-- to a particular date.

Here are some basic information about the S-curve. So this tool is composed by three kind of curve. The first one in green, the base line that is built with preliminary information. So for example-- I don't know-- information coming from the offer. Then we have the actual curve, that maybe is the most important, because it's the curve created using the real information, so the real quantities of our project. And then the target curve in red, so the quantities that we have to achieve every time and every month during our project.

So basically using this tool, we can identify the growth of our project with a comparison between the baseline curve and the target S-curve. We can identify the slippage of our project, that is defined as the amount of time a task has been delayed from its original baseline schedule. And then in the end, the most important part of it is the project progress. So with a comparison between the target curve and the actual curve, we reveal the project-- the progress of the project over time.

Here instead you can see the S-curve that we use in our company, and that this curve is used also for the Orpic Project. On the right part here, you can see the cubic meter of concrete. Then on left, we have the accumulated progress. In the middle, there is this [INAUDIBLE], in order to understand this file. So we have these three histograms divided by planned monthly, which is planned every month, which quantities are planned every month. The construction progress. And instead-- at the end, the actual progress. Using this histograms and these quantities, we create these three curve at the top, the planned, the actual, and the construction.

In the bottom part, instead, there is a table divided by cutoff date, so divided by month, and then divided by planned, construction, and actual. So basically in this table, we input the quantities in order to create our progress.

Before BIM, in our company, we have a manual data collection and input. You can do analysis when you work with AutoCAD or any other tools that are not BIM, you can do analysis after-- only after documents issue. And in the end, we have no connections with the 3D model activities, so we don't know if the quantities that we input inside our Excel spreadsheet are real or not.

So how we can improve these workflow? We can improve the workflow using Dynamo. How many of you knows Dynamo and use Dynamo everyday? OK, maybe not enough, OK.

[LAUGHTER]

As you can see here, using Dynamo, you can make appear money from [? a hat, ?] so I suggest to you to use Dynamo everyday. Dynamo is a visual program extension of Revit, if you don't know it. And Dynamo is a very powerful tool, because it allows you to manipulate all the data inside the Revit model. With Dynamo, you can also create geometry, explore design options, and you can connect and create relationship between the elements inside your model.

This is the workflow of our Dynamo script that now we will analyze. So first of all, we have to extract data from the Revit schedules. Then, we have to manipulate this data. And in the end, we have the export, all the data in the S-curve Excel file, in order to create the progress of our project.

OK, this is the script. As you can see, it's very simple. The first step is this one. The node get the schedules. Within this node, we can extract all the schedules inside the Revit file. You can see here, there is a bar under this node, because this node is a custom node. What it means? Inside the Dynamo, there are two kinds of nodes, the default nodes-- OK, so when you install Dynamo on your laptop or your PC, you find a lot of collection, a lot of nodes. Instead, you can create on your own-- your nodes, using the Python script, the Python language, if you want. Or you can download package from internet and use other nodes.

For example, for these nodes, the Get Schedules, we have created a Python script, but there is a package, maybe, archi-lab, if you want, that has a lot of nodes in order to extract the views and schedules from the Revit file. Another thing is that when you work with Dynamo, there are the Revit categories. But if you use categories, and then you try to get all the views from the Revit file, so using the default nodes inside the Dynamo, you can extract, for example, sections, the floor plan, but you cannot extract schedules. So you have to use a custom node, not default node.

Then the second step is this one, manipulate the data. OK, let's start with this node, ELEMENT, dot, NAME. That means that we have to get the name of each schedules, in order to filter them. We will filter the schedules using these two nodes that are STRING CONTAINS and LIST FILTER by a Boole mask. What it means? We filter using Boolean values. And these Boolean values is coming from the node STRING CONTAINS. So basically, the output of the ELEMENT, dot, NAME is a string, so the name of our schedules.

Then we connect this string with the STRING CONTAINS. We create a simple code block with the name of our schedule, that is main item model status, in which if you don't remember, we have the main item name, all the total quantity of concrete, the engineering status, and the issue date. The output of [? these ?] STRING CONTAINS is a Boolean value. So it means if the schedule's name is equal to these code block, the Boolean would be yes or not.

In the end, we connect the list, that now is not visible, the list of our schedules with these node. And the [INAUDIBLE] you will have the schedules that satisfy these condition, so with name, main item model status. And this, instead, are all the other schedules inside your project.

In the end, we have to manipulate data. This because, as you can read here, the output will not be all the data collected into the schedules. But the output will be this object, ViewSchedule. What it means? That we have the schedules but not the data inside the schedules. So also, in this case, we have to use a custom node that is called TRANSACTION. And also, in this case, in the archi-lab [INAUDIBLE]. If I remember well, there is this kind of node, that, as you can see here, extract all the data coming from the Revit schedules.

Another important thing is setting inside the Dynamo that is called Lacing. When you work with Lacing inside the Dynamo, it's very important to consider this set, the Lacing, that basically is the algorithm that manages the data matching. What it means? We have three possibility for latching-- Lacing, sorry-- the shortest, the longest, and the cross-product.

Where we select the shortest means that Dynamo connect the input ban, one-by-one. So for example, if I have a list of four indexes and the list of six indexes, Dynamo associate, one-by-one, the first four indexes. But in the end, the last two indexes runs dry. Then we have the Longest List. That means that Dynamo keeps connecting inputs, re-using elements, until all streams run dry. And this is the setting of our TRANSACTION node. And in the end, the most complex is the Cross Product List, that makes possible all the connection between the elements inside the list.

For the step 2, so for manipulate data, you can use also another method. That is not filter using the schedule's name. [? But ?] to get the item directly from a list. And in this case, we use also the ELEMENT, dot, NAME in order to see and analyze all of the schedules inside our Revit project. But then we use this node, GET ITEM at index. And so for example, in our case, these schedules-- OK, main model status is at index number 2. I input this one in a code blocker. And in the end, I connect it. My schedules [INAUDIBLE] the output will be just one into the Transaction node. In this case, the Lacing of the Transaction node could be also shortest, OK? You don't need to select longest.

In the end, we have to extract all the data coming from Revit-- sorry, we have to export all the data coming from Revit, into our Excel file. So basically, we can use the [? fourth ?] node of Dynamo. It is called Excel, dot, [? RIGHT TO FILE. ?] And ER-- we will connect the file path of our Excel file. So as you can see, S-curve, dot, XLS. Then, we have to import manually the sheet name in which we want to extract all the data. And in our case, the name will be quantity from Revit. Then, select the starting row of the export, the starting column of the export, and the data. These data are the data extracted with the Transaction node.

OK, now, in the end, we analyze the relationship between the S-curve Excel file and the Dynamo, in order to see how we can determine the project's progress. OK, this is the quantity from Revit spreadsheet. So here, you can read that in a sheet name in Dynamo, we have insert this name, [? Quantity for Revit, ?] that is the same that we have in the Excel file. Here, the starting row of the export, that in our case is [? 13, ?] and the starting column, that is the column A. So this is the reason why I input here 0.

So basically, here, we have all the information regarding our project, because for each main item that is modeled into the main item file, and so the assembly file, I have IFC status, the issue date, and-- the most important things-- the quantities. What I can do here is summarize all of these quantities, in order to have the quantities divided by month, and in order to have the quantities only for the IFC status. I can do it using a simple function of Excel, that is called SUMIFS Function. Basically, with this function, we can add all the arguments that meet multiple criteria.

So just to understand, we have to define the sum range of all of the data that we want to add. And in this case, the data, obviously, are the total quantity, the cubic meter of concrete. Then we have to define the criteria and also the criteria range. In our case, the criteria number 1 is the engineering status. So as range, I take this column, in which I have all the status of the main item, because, for example, you can see here that in this schedule, we have not only the IFC status, but we have also the IFB status. And this is-- there are some reason, because of this.

Then the criteria number 1 is the issue date. So we create a list of issue date a month, and we select this column for the range. In the end, we connect this summary table that is coming from Revit with the table of the S-curve, in order to have the actual curve built directly from Revit. So OK, you can see here, all these quantities are coming from the summary table. Here, a short video, just to see that this is not fake, this node, but it works. So as you can see, the actual curve, so the red one, is built directly from the data coming from the assembly model.

OK, we're using this tool and this relationship, but we can reschedule items in IFB status, in order to get monthly progress. What it means? That we shared-- we export also the IFB status, because in the Excel file, you can read the total quantities of each main item. You can say which is the bigger main item, and you can reschedule it in order to see, and in order to get, the monthly progress. Then you can have all the data up-to-date and always available. You can easily find the mistakes in the schedule, because, for example, if you see that the actual curve is above the target curve, or maybe there is something that is wrong, and you can do analysis based on real-model quantities. So you are sure, 100%, that all your analysis are correct.

In the end, I want to just to give you one feedback about what could be a further development. So you have to consider that using this method, we built only the actual curve using Revit. But for example, we can create a preliminary assembly model with a conceptual masses and the total quantities attached to these masses. We can extract from these preliminary assembly. A main item list, a preliminary item list, and the schedule built directly in Revit, so [INAUDIBLE] with the Excel file. And in the end, we can build, also, the baseline curve and the target S-curve directly with the 3D model data.

Thank you for your attention.

[APPLAUSE]

If there are any questions. You.

AUDIENCE: In the beginning, you showed your [INAUDIBLE] drawings, and so there's a thousand pieces. Did you use any tools to create those [INAUDIBLE] drawings a little more automatically?

FABIO BITETTO: No, it's not automatically.

AUDIENCE: To create the sheets and the views or anything like that.

FABIO BITETTO: No. Yeah.

AUDIENCE: [INAUDIBLE] If I understood you correctly, you're updating status on [INAUDIBLE]?

FABIO BITETTO: No, when they are built, because we are talking about engineering status. So what it means? Our department issues-- so for example, when we have to issue the construction drawings, we input directly into Revit the status. So for example, we have to issue the particular drawings into a particular date. We were prepare them, the PDF file and the AutoCAD file, in order to send it to the client, and to site. And in the same time, we define the engineering status directly from Revit. So we are not talking about construction. We are talking about engineering status.

ELISA BACCHI: Yes.

FABIO BITETTO: But if you want, you can-- with the same procedure, we can create a project parameter called Construction Status, in which you input the data, the construction data, of a particular element, in order to have also the construction curve. It's the same [INAUDIBLE].

ELISA BACCHI: In our com-- sorry, in our company report, the reports that are really issued from project control department, there is the curve, the feasibility curve of progress, of engineering, and of progress of the construction. The construction progress is given by another department and is totally [? filled ?] manually and not created using BIM models yet.

It is our target to bring the model inside and having a BIM field operator inside. We have not introduced it yet, these rules, in the entire cycle, lifecycle, of the projects-- step-by-step. But it is necessary, of course. Thank you for your query.

FABIO BITETTO: OK.

AUDIENCE: Hi, do you have a process, a vetting process to be sure, positive [INAUDIBLE] a right one. I mean with calculations, you can have a [INAUDIBLE].

FABIO BITETTO: OK.

ELISA BACCHI: [INAUDIBLE]

AUDIENCE: [INAUDIBLE]

ELISA BACCHI: One moment.

[INTERPOSING VOICES]

AUDIENCE: Basically, we have standardized, as much as possible, all the elements of [INAUDIBLE] that we are using [INAUDIBLE]. So in the same way, we are sure that what is the [INAUDIBLE]. And because we are modeling the right way the object [INAUDIBLE].

ELISA BACCHI: Estimate.

AUDIENCE: [INAUDIBLE]

AUDIENCE: [INAUDIBLE]

ELISA BACCHI: Yes, they are. They are [INAUDIBLE] quantities. And we are exponing the right quantities related to the projects, also [INAUDIBLE] to the drawings extracted by the model. So we cannot give not right quantities, because it's [? the cause ?] of [? claim ?] from our subcontractors. So we have to pay attention, a lot, to these item, in particular for reinforced concrete, because in industrial plant, we have two main key quantities to manage the project. One is steel quantities, and another one is concrete. Managing these two quantities, we are creating the feasibility to civil subcontractor for one side and the feasibility to mechanical director and the procurement of material from another side. So it is essential to give this right quantity.

About steel, you are right. If you-- [? doesn't model. ?] For example, the joint detail-- OK, there is some mismatch, because you are not considering the steel joint's connection. So you have to estimate, or you have to decide in your company if you would like to design, also, the joint connection, to have the very real quantity over the projects. OK?

AUDIENCE: [INAUDIBLE]

ELISA BACCHI: Also finishing. So--

AUDIENCE: [INAUDIBLE]

ELISA BACCHI: Yes.

AUDIENCE: In the beginning, you were showing-- one of the slides was showing [INAUDIBLE]. And one of them was [INAUDIBLE]--

ELISA BACCHI: Tecla.

FABIO BITETTO: Yes.

AUDIENCE: Was there any reason why you didn't Autodesk?

FABIO BITETTO: Basically because there is a client requirement and a vendor requirement, so it's only this. There are no particular issue about what tools can do or something like this. It's only vendor and client requirements.

ELISA BACCHI: Client and also-- because we started initially using, for steel, Tecla tool, so it is very embedded in our procedure, and it is not so simple to change now. But we are starting any kind of a development also in this direction. In our opinion, we are thinking that you can proceed, obviously-- or considering, for example, [INAUDIBLE]. And also there, Revit, because Autodesk is improving a lot. And we know that these are very smart to be used.

AUDIENCE: [INAUDIBLE]

FABIO BITETTO: Yes, bec--

AUDIENCE: Basically, analysis [INAUDIBLE] assembly model. [INAUDIBLE] assembly model that collect [INAUDIBLE].

FABIO BITETTO: So it means that in the assembly, you have the total quantities on the project. So when--

ELISA BACCHI: The actual.

FABIO BITETTO: The actual total quantities of the project. So you extract the data from all the project, not only one particular [? item. ?]

AUDIENCE: [INAUDIBLE].

ELISA BACCHI: Yes, the assembly model is the federated model, but we have only this way to proceed, considering our IT infrastructure, and also the workflow of the entire project, because you have seen that we have a lot of structure to be managed from calculation, up to delivery for construction, so different team.

And then each of these models comes through in an interoperability process, from Revit in IFC format, up to inter publisher tools, that is an intergraph tools-- tool for reaching the model inside the model plant that is done in SP3D.

FABIO BITETTO: SP3D.

ELISA BACCHI: So practically-- and the design review are done considering the multidisciplinary of the project. Now, I'm speaking not only about concrete, because-- in Navisworks-- because we have to give demonstration in three important contractual step of the progress of the model in front of the client. And review of the entire model is done in Navisworks.

FABIO BITETTO: Other questions?

ELISA BACCHI: Other question?

FABIO BITETTO: OK.

ELISA BACCHI: OK.

FABIO BITETTO: Thank you to everyone.

ELISA BACCHI: Thank you.

FABIO BITETTO: Have a nice day.

[APPLAUSE]