The Seamless and Bi-Directional Integration of InfoDrainage with Civil 3D

SAMER MUHANDES: Good morning, good afternoon, and good evening, everyone, wherever you are. And welcome to Autodesk University online. I'm going to be presenting this session live. And it's going to be the same session that you're going to see, but probably I might be wearing a different shirt. Let's see.

Today's topic is on the seamless and bidirectional integration of InfoDrainage with Civil 3D. My name is Samer Muhandes. I am the Drainage design product manager. I'm the product manager of InfoDrainage. I've been with Autodesk for two years, and I spent most of my career on the last 10 years in consultancy designing drainage systems and green infrastructure. And parallel to me working in consultancies, I have been doing a PhD part time at Imperial College London on the topic of sustainable drainage systems and green infrastructure.

So before I make a start, as an employee of Autodesk I have to present this slide to you, which is the safe harbor statement. As a product manager, I may slip tongue and talk about the future and basically make future statements. If I do that, and I know I will, please do not base your procurement or investment decisions based on what I'm going to say if it's something to do with the future. I will describe where the software is at and what is currently in the software, but I will be talking about the future direction of the software as well.

So we got this out of the way. The legal people can sleep at night. And yeah, let's talk about the agenda.

So we're going to start with an introduction. We're going to talk about climate change and green infrastructure and why we need that and why we need to change the way we do drainage systems. Then we will talk about the offsite flow analysis. I'm not going to talk about it. I'm going to jump to the software and do it.

So basically, we will be working on InfoDrainage. And we will set up a model. And it's going to be a story, similar to how a drainage designer in a consultancy office would be starting a project, from the moment they get their hands on the land, it's a green field, and they want to develop a business park or a residential development, all the way to the moment that they are getting their deliverables together and to send them to the local authorities.

And I'm going to be emulating the back and forth with the local authorities, the clash detection, the back and forth with the Civil 3D people. And then we will talk about the future direction of where we're going. So you're going to see some back and forth.

On purpose, it's designed to basically run into some sort of a blocker and come back and iterate the design. And so we make it more fun. And we're going to be playing in the software together. We're going to make mistakes now, and then we will validate.

We will find out where these mistakes are, something we forgot to enter. And then we'll get back to that value and then enter it. And it's going to be an hour of fun using the software. Then we have half an hour for you to ask questions.

OK, so climate change is happening. And we have the data to back this up. Basically, in the UK in 2020, just before COVID, we had areas in the UK that were subject to 400% the average 30-year rainfall. And people said that, oh, this is a rare event. It doesn't happen every year. Well, actually, the next year, in 2021 in May, we had areas in the UK that were subject to 200% the average 30-year rainfall.

And in the same year in July in Belgium and Germany, we lost lives to flooding because some areas in these countries were subject to 600% the average 30-year rainfall. So yeah, it is happening. And apparently, the traditional way of doing drainage systems has failed us. We cannot keep getting our pipes bigger, and we cannot keep getting our flood walls higher. So we need to find an alternative way of doing drainage.

Our intelligence as human beings made us come up with amazing ideas to make that water disappear. As soon as it rains, our objective is to just take that water, make it disappear, send it into the river really quickly, and make sure that we have dry paved surfaces.

But at the same time, our lack of intelligence made us do this whilst messing up with the hydrological cycle. Before we developed these areas, it used to rain. Water used to infiltrate in the ground. It used to evaporate. It used to be intercepted by the leaves of the trees.

And then via evapotranspiration, it would be sent back to the atmosphere. And we lost all of this. Now we have a lot of water being sent to rivers really, really quickly, which treating now the water as a waste product. And that process failed us. It was efficient to keep dry paved surfaces. But it failed us, and it messed up the hydrological cycle.

So we need to think about modern ways to deal with stormwater. And this is called green infrastructure, as our US colleagues would call it, or maybe as the UK colleagues would call it, SuDS. So this is basically-- we're not saying that you need to stop building roads and highways and parking lots and buildings. We're saying that you need to incorporate methods and structures within these developments to ensure that you're restoring the hydrological cycle, you're not messing up the hydrological cycle, and you're not creating a rapid response from your developed catchment.

So if, let's say, I'm building a road. I can put these measures next to the road or I'll incorporate them within maybe the central reservation. I can put a swale by this new development or some sort of an infiltration trench so water can slow down. And maybe we can encourage infiltration. Maybe we're going to improve the water quality. Or maybe also, we will enhance the amenity of the area and encourage biodiversity and attract butterflies and birds and whatnot.

So these measures are called green infrastructure. And they're being used widely. And this is the future for drainage. And this is the way we're going to be able to tackle the impact of climate change and urban creep and population rise and all that.

So why InfoDrainage? We've been doing drainage design for maybe 100 years since Bazalgette. And we're happy with our spreadsheets and our traditional software that we use to do linear drainage and this great pipe tank solution. Why would I want to look at a new software technology?

First of all, because of the way we're changing and the way we're changing our approach to drainage, now we want to tackle drainage by incorporating these features, which have been incorporated in the traditional software, but as an afterthought. So we had a software that deals with linear drainage, pipe, manhole, pipe, manhole, pipe, manhole, tank. And then we said, OK, let's find a way to replicate a pond. Let's find a way to replicate an infiltration trench.

And it didn't work. It wasn't accurate. With InfoDrainage, we had this green infrastructure as the foundation of the software. So basically, this is the basis that we built the software around it. It wasn't an afterthought.

And as benchmarking or as the impact of having these solutions at the heart of InfoDrainage, so people have done flow monitoring for a pond in Scotland. It's called Claylands Pond. We compared the monitored data against-- or the observed data against the simulated data from InfoDrainage and another software that follows the traditional approach. And you could see here that InfoDrainage demonstrated a better agreement with the observed data.

So observed data is in red. And InfoDrainage, using the modern approach to simulate green infrastructure, is in orange. And another software using the traditional approach is in gray. And blue is the inflow. And you could see how InfoDrainage was demonstrating a better agreement.

So let's jump to the software and play with it and see how the story would go from the moment you start the project all the way to submission. So within InfoDrainage, let's say you start a project, and you can load an image, a background image, which is georeferenced. And let's say that you have a green field site. Ignore these buildings for a moment.

And they tell you that OK, we have maybe a project, a residential project or a business park. And we're going to build offices or houses. And we want to go through planning application.

So the first thing when you talk to planning officers or the lead local flood authorities, they would tell you, OK, I need you to check the pre-development rate. And then that would be the basis for the flow restriction. I'm not going to allow you to build your site, create a crazy flow rate, and discharge into rivers or the public sewers-- depends where you're discharging.

So the first step would be to create a subcatchment in the model and say, OK, that is my green field site, which I'm going to convert into roads and buildings and whatever. And I'm going to use a method called SCS with a curve number of 30, because that is a good curve number to describe a permeable response.

And then we're going to go ahead and set up an SCS rainfall. So I've already done that. And I can show you this is the SCS rainfall. And probably, we're going to check the five-year event for now. And now I'm going to analyze.

So once you analyze, you can plot the results. And you can see the response that, OK, you're generating 26 liters per second for a five-year event.

So let's assume that you're limited now to 10 liters per second. So they're going to tell you, OK, probably, for a one-year event, you will generate 10 liters per second. And that would be your allowable discharge rate.

If we go ahead and duplicate that phase, and we call that post-development, and now I'm going to play with the parameters. So that now is a brownfield site. And it's now an urban area. And let's treat it as a parking, paved parking.

So now if I run an analysis and compare the results, we can actually go ahead in here and plot the results, so before and after. And I can select the storm.

And you could see that before development, this was the catchment response. And when I developed the catchment and made it urban, we lost the infiltration, the evaporation, the evapotranspiration, the interception. We lost all of these hydrological processes that used to reduce the volume of runoff and the peak, and it used to delay the runoff. So you could see that delay. We lost all of these benefits. And now we're generating a really rapid response and a peak here response.

So if I go to the local authority, and I say, hey, I'm developing this area, and I'm going to discharge 250 liters per second. Is that OK? They're going to chase me out of the room. And they're going to say no, no, no, no. This is your allowable discharge rate. You're not allowed to send 250 to our rivers or to our public sewers. It depends where you're discharging.

So the solution would be to find a way to create some storage in your site so you're limiting that discharge to the allowable discharge rate. We're going to come up now with an allowable discharge rate, and we're going to iterate until we make it work, iterate the storage.

So I'm going to duplicate that phase. And I'm going to call it storage design. And before I go ahead and put some storage here or there or in a corner, et cetera, let's run a 2D analysis called Deluge. Based on the terrain that we have for the site, I'm going to run that Deluge.

And it will tell me if I drop a bucket of water on the site, where that water will go. So we're applying a depth of water, and we're going to see where that water is going to go. And maybe I can-- 5 meters squared for the element area, and we're dropping 50 millimeters on the site. So that would be the starting depth.

So if I go ahead. And now let's view the results. So you could see here that if I drop that bucket of water on the site, you can see from the arrows that water will be channeled this way, and it will make its way all the way to the corner. So this is an area where water will be accumulating.

So it's a good choice if we want to have storage structure. But you could see also the channeling of water towards that area mainly is in this area here, this road. So that is a road that you would need to avoid if you're designing an evacuation route. If there is an important school here or a hospital or whatever, and you're trying to design an evacuation route in case of extreme flooding, so you know that you're not allowed to take the kids and put them subject to flood risk and have a big hazard.

So yeah, this is a quick assessment that is very, very useful for us to know what roads to avoid during an evacuation and where are the locations where I should be considering as a storage location. So yeah, I can see this is a good location now based on the analysis. Ignore the images. I mean, we figured that already in the image. And you could see from the development that we're going to have a pond here.

But yeah, this is a good place to go and digitize a pond. So you could easily say, OK, I'm going to digitize that pond in here. And you can have it. And then you can connect your development to it. So I'm going to go ahead and import a polygon. I'm not going to digitize the pond.

So I'm going to go to some of the controls. And I will go to Import from GIS. And I will import a polygon, now GIS 5.

And now this shapefile has the polygon boundary. I can bring it in, and I can say this is a pond. For some reason, my mouse is playing up. And I can load some sort of a mapping-- the mapping for me.

And I can import it. And now I have an object here, which is at the pond. And the subcatchment was automatically connected to the pond.

So what I'm going to do now, I'm going to double-click on the pond. And I'm going to delete that row. And I'm going to design that pond. So it's 1.5 meters deep. And I know the top area, but I don't know the base area.

So what I can do, I can go and say, do the side slopes based on 1 in 4, because I asked the landscape architect, and they said that they would like people to be sitting on the banks of the pond to have their lunch break if it's a business park, or maybe kids will be playing around it. So they need a gentle slope. And I want to maintain the top area. I know that the top area, this is the area that we purchased, so this is the land take. And I'm going to maintain it and then go down.

You can do the opposite. You can maintain the base area and then go up. But then you're going to end up with more land. So let's do top area, and then we go down. And then we got this pond in here.

So now this catchment, the developed one, will go to that pond. And now I need to say the outlet of the pond is not going to be free discharge. It's going to be restricted and based on a discussion with the local authority. They gave me 10 liters per second as a allowable discharge limit. And the depth is 1.5, the depth of the pond or the depth that orifice will be subject to.

And, of course, sometimes people talk about freeboard, so they need 150 meter freeboard for the pond. So that's OK. We can have that. And the pond would look like this.

And if I say OK to that. Now, before I go and analyze, I need to check if I forgot anything. So I can go and validate, and I can say, oh, and I can see that everything is OK. And now I'm ready to analyze. So I can analyze that.

And I can go to results. And I can compare. So let's compare three phases-- pre-development, post-development, and storage design. You could see now, pre-development is blue. And now post-development is red-- now, post-development, where the pond is green. So we have this long response because we have it. And we have now a storage structure, and we have an orifice.

If you notice, the storage structure in InfoDrainage is polygonized, which means that the time of concentration for water that comes in and gets out from the other end has been taken into account. You see that we can here specify a center line, so you can say from here to here. So that's the direction of water. And this is going to be our storage design.

But actually, water will not be pointed at the pond. Water will get to the pond using a network of pipes and manholes. So if I go to my Civil 3D design, I can now see that maybe someone else digitized the pipes and manholes. But let's do them in InfoDrainage first and see how we can bring a GIS layer of manholes and then how we can connect them together and then how we can design the pipes and then take them to 3D.

So I'm going to start the journey by bringing the nodes. So if I go to the GIS files, and I go to the nodes, and these are my nodes, and this is the mapping, I can load maybe a mapping file. And I can import them.

So all the nodes are here. Something is always useful when you bring note is to lock them, because if you bring connections, the levels of the connections might override the levels-- they might snap to each other, and they might override each other. So locking them is a useful tip.

And then you can go to connections and import connections. Or you can digitize. So let's try and digitize. It's really easy. So you can go here and say, I'm going to have a pipe. And then you can say this to this and then this to this, all the way to the end.

So I'm going to delete these pipes. And I'm going to import them from GIS. So I'm going to have links. So these are the links and their pipes. And you can load a mapping file that you saved previously.

I don't think I have one in here. But you can drag the-- so you can say incoming is from and outgoing is to. And upstream cover level is here, and base level is here, downstream cover level is here. Downstream invert level is here, entry, entry loss is here. Exit loss is here. And then manning is here. And the diameter of the pipe is here.

You can bring more data-- for example, number of barrels. But I think that would be enough for now. And now you brought the network, and it goes all the way to the pond.

And I can respecify the destination in here. I can say, OK, this is where my head wall will be. And now I don't have that subcatchment that goes to the pond right away. It's going to be basically properly distributed across this catchment.

So I'm going to bring a layer. And basically, this layer is this subcatchment, so subs. And I'm going to import. So now all the subcatchments have been brought in, and they are connected.

So I can now check the design of the pipe. So I have these pipes. Now, they haven't been snapped to the edge of the manhole because of locking, because we locked the manholes. So I'm going to go and unlock the manholes. And that will help us with the design.

So in here, basically, you could see that I have a design criteria. This is where I decide what sort of pipes I have in for my project. This is where I decide whether I want to minimize the excavation or minimize pipe diameter, because they're both two conflicting objectives.

This is to say, I want the pipes to meet soffit to soffit. I want to have a minimum cover depth. And I want minimum slope to be 1 in 20, maximum slope 1 in 500. Whether we want to allow backdrops or not, so you can do all of these. And then you can-- once you hit Finish.

And now you have a system that has been designed properly. And it's taking the water all the way upstream to downstream. Similarly, we can design the other sections as well. So if I design, you can check connectivity as well. When you create flow path, it will help you to check the connectivity and see that everything is connected.

So I'm going to check the profile. And it looks OK to me. But of course, once we run a simulation, we will know for sure. So we can do that here as well. And that looks OK as well.

So now let's go ahead and run a simulation. So I'm going to analyze. First of all, let's validate and see if we forgot anything or if we have any errors that will prevent us from simulating. So one error, which is the unused inlet should be disconnected. When you import and export, it creates inlets, and you would need to delete these unused inlets.

But it's something in the ponds or in the manholes. When we change the connectivity, you would need to remove the inlet. And when we talk about inlets, we talk about this part, which is in here. So if you have unused inlets that basically you had a gully connected or a curved drain, then you deleted the object, you would need to just remove that. And the software has removed it already with the validation.

And now it's saying that we have two subcatchments that haven't been connected, number 19 and number 12. So I can easily go in here and say, OK, let's connect that one to this manhole here. And let's connect that one to this manhole.

And now let's analyze again or validate. And now the software is happy. So I can run an analysis.

Once you run an analysis, you could see now that the pond is happy. It's 84% available because we're running a five-year event. But let's check the hydraulic grade line and energy grade line in the system. So I can zoom in here, and I can see AGL, AGL. And I can basically play some animation and see the water going up and down. And I can check that, OK, there is no bottleneck.

But now let's stress test the system with a bigger storm. So now if I go and say maybe I'm going to run a 100-year event, and I want a 40-year return period, and I'm going to hit Analyze. So now I have 48% available within the pond. The pond is quite big. It's 2,000 cubic meters.

So that tells me that if I go and reduce the size of my pond, that I will be OK. So there is no need to spend all that money on 2,000. So this is a good time to look at the storage calculator. So we can say, I want to use the software storage calculation in here.

So I can say I have almost two hectares in the model. And let's say the volumetric coefficient is 1. And the authorities gave me 10 liters per second as a discharge rate. And I'm going to use the SCS storm. And I want to calculate.

And I've been told that now the range is 1,200 to 1,600 or to 1,700. That would be what I would need. And I had 2,000-something. And by the way, the range is not guessing. It's because the software at this moment doesn't know whether you're going to use a pump to control your discharge or an orifice or a weir. So based on your discharge efficiency, the storage will be dictated.

So maybe let's go with the maximum. Maybe 1,700 is a good estimate. And that would reduce the size of the pond. If I say, OK, it's always true to site. You would see that that has been now reduced, the size of the pond. And I can rerun the analysis.

And now it's 26% available. So yeah, we're optimizing now. We have detailed drainage design taking the water all the way to the pond.

Now it's a good time to think about other sustainable drainage systems. So probably, this supermarket over there, or this-- maybe it's not a supermarket. It's a school. Maybe we ask them to be sustainable and look at sustainable methods to discharge into our systems.

So what they did, they told us, you know what? I am going to have some sort of maybe porous paving in that car park. So they agreed to do that, which is great. So that porous paving, they can put it like this. And now we can connect the inflow to the porous paving.

And from the porous paving, we can connect to the pond. And that with a pipe maybe, or it's connected with no delay. If you want just a volumetric exchange, you can have a no-delay connection, which is a notional connection. Doesn't have physical aspects.

So we're now sending water to the porous paving, from the porous paving to the pond. And this is the USB of InfoDrainage. It allows you to get all these elements interconnected together. And you're not worried about getting around the limitation of the software or trying to represent a structure with a dummy node and the depth-area relationship.

And we've been always some sort of-- we've been struggling with the way to model interconnected structures. And we always assume things. And we say, OK, let's put that pond on a node, and let's drop that swale on the other link, et cetera. And we always made these really, really big assumptions that affected and impacted the hydraulic results.

But now we're describing the physical reality of the structure. We say, OK, this is a porous paving. How deep it is? It's 1 meter. The paving layers is 80 millimeters. The percolation is 1,000. Porosity is 30%, assuming it's gravel.

And let's say it's flat, 1 in 500. And then the inlet is coming from the subcatchment. The outlet is going via an orifice. Maybe it's here, or maybe not via an orifice. Maybe I'm going to have an underdrain.

So an under drain, which means maybe 150-millimeter pipe, perforated pipe. And I have two of them underneath the car park. And here, I have 0.9 meters as a release height. And I can say OK to that.

And before I say, OK, I need to say that control the discharge using the underdrain. That is the outlet. And now I can say specify the outlet. And now the outlet, let's say this is where the perforated pipe is, for example.

And now I'm describing exactly the physical reality of what's going on. Everything is interconnected. I don't need to basically make assumptions. And all the lengths are true lengths. Everything is true to size. So I'm not trying to get around the limitation of the software.

So if I validate, maybe I forgot something. So in here, the underdrain, we should have this as maybe 0.5. And the hydraulic conductivity, which describes how fast the water would be moving horizontally in the structure. So maybe if I put some infiltration as well, so I'll say OK to that.

And let's delete the unconnected inlet. So if I analyze now, everything is good. And I can run the analysis.

In the past, I worked on a project when every plot was sending water to a porous car park, and from the porous car park to the drainage system, from the drainage system to some sort of a soakaway, and then from the soakaway to a tank, and then to the ground. So lots of interconnected structures, and we didn't have InfoDrainage at the time, and we struggled big time with the fact that we were trying just to manipulate things and put parameters and account for this and account for that. And yeah, it was a big mess.

And in here, we could see that the porous paving is not enough. And basically, we are flooding from the porous paving. I can run it through the analysis and see how water is leaving the porous paving or leaving the structure, a certain structure, and coming out from certain manholes or certain structures. And I can visualize where that water is going.

And probably, it's worth doing maybe a quick one. So let's put a crazy storm in here. So let's go maybe 100 millimeters. And let's put maybe 60% climate change. And I am going now to say OK to that.

And instead of running 1D analysis, I'm going to run 2D analysis. But it's not a deluge this time. It's an analysis that water will flow through the pipe system. And then when it floods, it will leave the manhole, and it will run on the surface. And if it finds another manhole, it will go back in, and so on.

So if I go to 1D or 2D analysis, I can choose that crazy storm. And I can say Run. It might take some time, so a minute or two. And basically, it's running 1D, 2D integrated analysis. So water is going into the 1D system and then popping out of manholes and structures.

In the meantime, I will be opening a model in immersive 3D, which is technically the same one. OK, I have flooding, as I hoped I would have. And now let's visualize that flooding.

So you can see here that water did leave a certain manhole. So if I play it, and I can just go step by step in here. Yeah, so you could see that water is leaving a certain manhole, and then it's running on the surface, making its way somewhere. And at the same time, water is leaving the porous paving, making its way to the pond. And all these ponds and porous paving will be considered in the simulation. So they're interacting with the water.

And then we have a sanitary water system as well. So we want-- we call it foul in the UK, and they call it sanitary in the US. So we want to create some sort of a sanitary system to take the foul water, or the sanitary water, from the properties, or the offices, or the properties.

So if I go to Data, and I drop a surface in here, just so we can pick up the cover levels, I'm going to draw a very random pipe. I'm not going to put the image for now. But I will just go and add a network. And I will say OK.

That's my network. And I'm going to add some sort of an inflow. So you can add a base flow if you know that there is maybe some sort of groundwater ingress. Or you can add a hydrograph if you want to simulate sometimes what will happen if you have a fire hydrant being used in the area, the hydrograph or water main burst, et cetera.

So we're connecting now that subcatchment-- the sanitary subcatchment or the foul subcatchment is different because this is when you have the number of appliances. You can put two basins, two toilets, two showers, two washing machines, et cetera. And then it will calculate. It will sum up all the units. And you put a frequency factor, and then you have a flow rate.

Frequency factor will account for the fact that people in a tower, for example, will not be flushing toilets at the same time. They will not coordinate taking showers and flushing toilets and using washing machines all at the same time. So if you have one, then yes, maybe it's a public toilet, and people might be using it at the same time. But if you're in a residential tower, then there is a frequency factor, the intermittent use factor. So yeah, let's say 1 for now.

And now I want to design that pipe. So currently, it's set at level 0. And I will just go and design it based on full-bore velocity. And if I say OK to that, now I have a sanitary system designed properly.

And now I need to go back to my stormwater design. And I will just switch off this 2D analysis. And now I'm worried, and I couldn't sleep at night after that design because I'm worried that I might have some sort of clashes in the intersection points.

So we have a clash detection analysis that will allow you to say, can you check that phase with the foul phase or the sanitary phase, run clash detection, and show me where the-- if I'm clashing or not. Basically, if there is more than 300 millimeter spacing between them, vertical separation, then happy days. I'm not overly concerned because the trench is almost like maybe 300 millimeters from each side or 150 from each side, et cetera.

But if it's less, then yes, it means the pipe went into the other pipe. So in here, it's negative, which is concerning. And I know that I need to change something.

Now, within InfoDrainage, I think it's the only software that has clash detection between the pipes and the stormwater control. So you can do clash detection with-- if I do this, for example, and I run an analysis again, classification analysis, it will show me clashes between manholes and stormwater controls, pipes and stormwater controls, and then pipes and manholes, and pipes and pipes. So you see here, it will say this pipe is clashing with the stormwater control, and another pipe is clashing again. And you can increase and decrease the tolerance to account for various things.

OK, so I have the network in Civil 3D. So sometimes, people have it in Civil 3D. They digitize it in Civil 3D. And they want to take it to InfoDrainage to be analyzed. So can we do that?

And then the other story is, I've just done this, and I'm really happy with it. Let's go back, because I messed it up. So I'm really happy with this. And I take this to Civil 3D and basically get that design to play and live with the rest of the site design, where the utilities and the gas main and the utility corridors are. Yes, for sure.

So now once it's validated, we can go to Civil 3D. And we can go to Innovyze and import from InfoDrainage. So I can save it and import from InfoDrainage.

So before we go to Civil 3D, let's check the part family and make sure that we assigned part family to the pipes. So I used purposely part family concrete pipe design. Which matches the Civil 3D part family and the PVC pipe SI. And I used this name as well, the cylindrical junction structure, which matches a part in Civil 3D.

So I'm going to check my pipes and see that-- or my nodes. And they all have the part family assigned. Similarly with the structure, so happy days. All what we need to do is to validate, and maybe we just need to connect-- delete this inlet, which is OK. And then I can validate again.

And the model is happy. I can save it. And now I'm going to go to Civil 3D. So the first scenario is that I finished a design that I'm happy with, and I'm going to import it from InfoDrainage to Civil 3D.

So in here, it will present me with the mapper. And I can say, give me that on a pre-development. It was post. And now I want to say, don't bring these scenarios. We were just experimenting and discussing.

So this is not to be brought. So only this one. And Civil 3D-- notice that I'm using the name that matches a part in Civil 3D. So the part in InfoDrainage, this is an InfoDrainage part family. It's called Concrete Pipe SI.

It found one in my library in Civil 3D. So it mapped them together. And then it looked at InfoDrainage pipe diameter, and it found the same size in Civil 3D. So it mapped them together.

So if I go to junction, it did the same thing. It found the same junction name in Civil 3D or as a part, structure part in Civil 3D. So it mapped them together. And then it looked at the diameters, and it found the same diameter, 1.2. Happy days, so I can just hit Finish. And I will get my model in here.

Now, the thing is, every element of this model is a smart object. So if I click on this manhole, it's not a circle. It's an actual manhole. And if I go to Settings, I can go to the extended data. I can see InfoDrainage data, and I can see if it's sealed or not. I can check the design data, and I can look at the levels, the cover level, the invert level. And I can create also a long section.

So if I go to View, and I-- let's make it horizontal or vertical to vertical. And in here, let's go and do an alignment from network parts, so from here all the way there.

And I can say, OK. And I'm going to use that surface, create, and then create profile view. And let's put it over there. So this is the profile view. We can see the network that we designed. And in here, this is the plan view.

So let me try to click on one subcatchment. Is it a polygon? No, it's an actual catchment. And you can see all the data, and you can see extended data set from InfoDrainage, which tells you what is the runoff method, and what is what, and what is the volumetric runoff coefficient.

Even the structure in here, that one, came as a surface. And if I click on that surface in here, for example, it has data with it, which describes everything to do with the depth, the manning, the perimeter, the safety factor, all the InfoDrainage data that we put, the infiltration rate, the, of course, cover level and exceedance level, so all of these, and because Civil 3D, for now, recognized that as a surface that consumes the same space. OK, so that's one aspect of the journey, so a journey from InfoDrainage all the way to Civil 3D.

Now, what if we are doing the opposite? If we are designing a highway, and someone was looking at this, and let's say someone decided to digitize the pipes and manholes. Let me digitize the pipes and manholes. And they looked at this, and they said, OK, probably that manhole should be here, and that manhole should be there.

And before we proceed with that change, we would need to check the hydraulics. So we would need to send that model to InfoDrainage to be checked again. And then we send it back.

So first of all, let's make more changes. So that person went to the subcatchment and said, OK, probably, we shouldn't consider it to be 100% for the 100% volumetric runoff coefficient or percentage of impervious. Let's make it 90%. Let's put 20% urban creep.

So you can manipulate some of the InfoDrainage data in here. And let's make more changes to the pond. So if I make that surface in here, and I maybe play with the infiltration rate or with manning, someone said maybe I'm going to put more vegetation, which means manning should be 0.04. So now I can export that model and go to Innovyze and go to Export.

And I'm going to say Export from Civil 3D. And I go Next. And then-- so it found all these parts. I can easily write them here, or I can maybe open some mapping file. Or probably, I can do that, and then I can bring them all here. And I can do the same here, or I can type it right away.

And now it's creating the InfoDrainage file. So if I go to InfoDrainage, and I open that file, export from Civil 3D, you will see that these manholes that we moved, you'll see them here. You will see that the pond because we changed manning to 0.04. So that changes here.

Now, do you think that we lost the rainfall? No. We still have the rainfall there. So the rainfall has been preserved. And you can see, we have the rainfall data. So you wouldn't lose any data from your model when you go back and forth from between InfoDrainage and Civil 3D. So we went from InfoDrainage to Civil 3D. We had everything, and then we came back from Civil 3D to InfoDrainage. And we still have everything related to the model.

Now, one thing you might ask yourself, how about results? Can I send hydraulic results to Civil 3D? Now, up to this moment, when I recorded this video, so no, people couldn't migrate results. But from next week, you'll be able to do that. So this is why I'm not able to show it in the software. I will be showing it live in Las Vegas.

But I'm going to show you a video on my machine that shows you how to do this and show you a demo, basically, a technical preview of this. So in here, this is when we import a model. In this scenario, we will ask you what sort of storm or what sort of rainfall do you want to use for your results. So you say, I'm going to use that storm. And you can choose which duration, which temporal pattern.

And as soon as you bring it in, you can put the profile view in. And then you will see that all the pipes and the structures, they have hydraulic grade line, energy grade line populated from InfoDrainage. So you can click on the structure as well. And you can see the hydraulic grade line, energy grade line. And you can see them on the long section as well. It's there in green and pink.

So that is something that is going to be in the software from next week. But I'll be presenting this live in Las Vegas.

OK, so so far, you've seen how we design drainage systems with green infrastructure. And you've seen how we migrate data from InfoDrainage to Civil 3D and from Civil 3D to InfoDrainage, how we use the material awareness in InfoDrainage to map elements to Civil 3D, and how we use Civil 3D enhanced hydraulics. Now we have it's recognizing the connectivity, the hydraulics, the infiltration rate, the pond, et cetera. So all of these elements are being recognized.