InfoDrainage for Transportation Projects: From Concept to Detailed Design

YOUSSEF AL FAHHAM: Hello, everyone. Thank you for joining our presentation, titled "InfoDrainage for transportation projects, from concept to detailed design." I'm Youssef Al Fahham, senior technical marketing manager at Autodesk. And with me are Ryan and Matt. They're both going to introduce themselves. So, Ryan, go ahead.

RYAN BROWN: Ryan Brown, the technical sales subject matter expert, here to talk about drainage and drainage and roads.

MATTHEW PIGGOTT: And I'm Matthew Piggott. I'm a tech sales SME as well. I look after the APAC region. I'm located in Australia.

YOUSSEF AL FAHHAM: Super. Thanks a lot, Matt. Thanks a lot, Ryan. That said, before we get into the agenda, we just wanted to display the safe harbor statement, which is simply highlighting that if we make any forward-looking statements, we do not want you to make any purchasing decisions based on those. So that aside, we'll get to the agenda.

So we're going to start by talking-- by providing a background and then introducing InfoDrainage and some of the capabilities within InfoDrainage. And then we're going to get to the technical portion, really the meat of this presentation, where we're going to touch on the Autodesk Construction Cloud. And then, we're going to cover workflows pertaining to roads and rail. Finally, we're going to provide some resources at the end before we wrap up our presentation.

So starting with the background, given that we're going to be talking about transportation, just thought we'd put a brief definition of what transportation is. It's simply the movement of people and goods from one place to another. So the transportation industry, it's of critical importance. And we're going to have some statistics and numbers that display that, but we're going to first take a look at it nationally, first pertaining to roads.

So roads, nationally, there are about 4.18 million miles of roads that are used to contribute 73% of-- to carry 73% of domestic trade. And they contribute more than $700 billion annually to the economy. And that's just nationally.

Now, rail is a similar story, but maybe a little bit on a slightly smaller scale. So there are 160,000 miles of tracks, where 40% of domestic long distance trade is transported through rail. And they contribute $274 billion annually to the economy. And the transportation industry and infrastructure in general gets some decent funding. For example, in the US there's almost $1.2 trillion for transportation and infrastructure spending that were signed into law in 2021.

Now, that is the National picture. But it applies globally as well. Irrespective of what region you're at, the story is quite similar. And that highlights the importance and the critical nature of transportation projects and transportation infrastructure.

Now, it's just worth level setting on one thing, that we're going to break down transportation for the sake of this presentation into four components. First being planes and airports, boats and seaports, trains and rail tracks, cars and roads. And we're going to highlight an overarching challenge that we find that any of these transportation infrastructure is prone to.

And that is during a rain event, any transportation infrastructure could be prone to flooding. And that is what we're going to try to tackle here is what drainage infrastructure you could incorporate into your projects to mitigate or reduce the risk of your infrastructure turning into a flood area. Before we progress, it is important noting or highlighting that our focus is going to be on rail and roads primarily. And everything in the coming slides pretty much towards the end of the presentation is going to focus on those two technical workflows-- rail and roads.

So that was a little bit of the challenge. When we think about what is the simplified outcome that we're after, without getting any technical or going into any level of detail, if we just think about it, the simple outcome that we're after is to keep water away from our transportation infrastructure through any storm, big or small, that can impact our infrastructure. So that is the simplified outcome that we're after.

Now, how we get there is obviously using a lot of things. We're going to tackle the technology component. And that is going to be InfoDrainage. So InfoDrainage, as we mentioned in the previous two slides, InfoDrainage for roads and rail is what we're going to be talking about.

However, there are so many other applications where you can use InfoDrainage. Some of them even extend outside of the transportation industry. But our focus for today is going to be the use of InfoDrainage for roads and rail projects.

If you're not familiar with InfoDrainage, it is an analysis, a stormwater analysis and design solution that is comprehensive and has a lot of capabilities that you would need for your project, starting with a Civil 3D integration to being able to bring in background data, perform 1D and 2D analysis, to some design automation capabilities, phase management, to host multiple scenarios in the same model, and flexible reporting to be able to extract that data out and share with your stakeholders through various customized reporting. And there are so many other features, but these are some of the features that we're going to touch on on the following slides just very briefly before I hand it over to Ryan and Matt to dive deep into the technical workflow.

So starting with the Civil 3D integration, what that means is pretty much you might have data in your Civil 3D model with a preliminary or conceptual design of your network and layout and sizing and all of that. You are able to bring that data into InfoDrainage to do your detailed design, to update the sizing, to design your stormwater controls, your ponds, your basins, et cetera. And then you're able to then also bring that data back into Civil 3D as your final design. So this is the integration or the streamlined integration that you have with Civil 3D and InfoDrainage.

Now, let's say you bring-- aside from Civil 3D data that you can exchange with InfoDrainage, there's also a lot of other data types that you can bring in, namely surface data, CAD data, GIS data, and images as well. And all of that you can bring into InfoDrainage for your projects.

Now, let's say that you bring in surface data. This is an example of a surface that was brought into InfoDrainage. You can use-- it's something we call the Deluge feature, which has a machine learning component, to be able to identify the channeling and ponding on your surface by simply applying an amount of rain on that surface. So you can go from a surface that looks like what we had shown earlier to a surface that looks like what you're seeing on the bottom right-hand side that's identifying some of the areas that are where ponding and channeling is going to happen. And that could allow you to determine what areas you can prioritize to build your stormwater controls.

And that's a pretty basic analysis that you can perform in InfoDrainage. But you can also perform maybe more sophisticated or more comprehensive analysis, such as a 1D, 2D analysis, where you're then looking at the interactions between your 1D network and your 2D surface. And that is also available to you in InfoDrainage.

And you can't talk about 1D and 2D analysis without really touching on the various rainfall and runoff types-- rainfall types and runoff methods that exist. So there are seven rainfall types, design storms, that exist in InfoDrainage, in addition to the ability to input user-defined and known rainfall, in addition to the various runoff methods that are built into InfoDrainage. And there are 14 of them shown on the screen here.

So that pretty much everything we've covered so far in the past few slides was talking about the analysis portion. Now, if we get to the design portion, there's a lot of features that can help you in your projects. One of them being design automation, where you can use the network design wizard to preliminary-- to automate the preliminary sizing of your pipes and manholes. Or you can also use the built-in design calculators to be able to just quickly adapt your design and quickly size stormwater controls based on your site requirements and based on certain parameters that you input.

You can also, with InfoDrainage, host all the scenarios of all the phases in the same model. So you don't need to have duplicate models with different phases that you're looking at. It can just be one model with the various phases that you're looking at. And that really streamlines the comparison process when you start looking at how each phase or how each scenario is performing and how it compares to the other scenario. And this is very helpful when it comes time to pretty much decide which direction you're going to proceed with when it comes to the implementation of your drainage design.

And last but not least, can't talk about InfoDrainage without really touching on flexible reporting, which in simple terms, this gives you the ability to decide what results you'd want to see in the software that is of value and of meaning to you. And you have that flexibility to say, OK, which results I want to see, but also we do recognize that in some cases, there are some regulatory requirements to be able to bring those results into some sort of a custom spreadsheet. And that is also very much streamlined when you talk about it in terms of flexible reporting, because that way you're only going to be interested in seeing the results that are of interest to your regulatory agency that you'll be submitting the project to. And so flexible reporting is very helpful to allow you to do that for your projects.

And that said, that was just very high-level introduction on some of the capabilities. And now we get to the workflow. And for the workflow, we're going to start by talking about the Construction Cloud. And this is going to be pretty simple. Pretty much our use for the Construction Cloud was to host all the data used for the project. And that is just highlighting or emphasizing the value of having this common data environment as you work across your projects with many different team members and stakeholders that might need access to the data. So for this project, using something like the Autodesk Construction Cloud would prove very valuable to host the data and for everyone to work off of that same data in the common data environment.

So that said, we're now going to segue to the technical workflow where Ryan is going to touch on the roads portion of this presentation. And I'll pass it on to Ryan.

RYAN BROWN: Yeah, thanks, Youssef. So, yeah, we're going to start off with roads and just talking about some of the workflows within InfoDrainage and Civil 3D for an optimized design. So workflow overview, first, starting out in Civil 3D, generally speaking, just laying out pipe networks and catchments and different things that we'll need for that drainage design. We're going to push that design out into InfoDrainage, where we're going to be sizing culverts, sizing the pipe network itself, looking at roadside ditches and including some of that, as well as including bypass links for the different inlets and some of the different configurations we have with having inlets in InfoDrainage and what that looks like.

Finally, looking at the simulation and results just to make sure that everything works as we expect it to. And then finally-- well, not finally guess-- flexible reporting in there to be able to adapt relatively quickly and easily as different formats come up using that flexible reporting in order to come up with a report that looks like what it needs to be for whatever regulatory agency, whatever DOT needs that. And then finally, looking at the final design in Civil 3D where we're going to import back from the InfoDrainage file into Civil 3D, take a look at some of the characteristics that followed over, take a look at some of the profiles that get updated and whatnot.

So, first of all, the site overview-- so going through this, just kind of looking at the design itself, we've got an existing road where we're adding an additional roadway to. So here, I'm just turning on some of the existing contours we have here to get a better idea of what exactly we're adding in here. I forgot exactly how long this is, but I think it's just a couple of miles where we're adding that second-- well, I guess two additional lanes up on the top there. And then it kind of flips over into where the existing road is on the north side there.

And then the proposed road is on the south side here. Again, turning off some of the proposed contours here just to take a look at some of the existing contours and really highlighting how that southern portion of the road is going to be a proposed surface where we're going to have to put in some culverts, of course, put in the drainage on the road, and whatnot.

So the preliminary design, laying out everything in Civil 3D, and pushing it over into InfoDrainage-- so again, we're just scrolling through the site, looking at what we have here. We've got the pipe networks in here. We've also got catchments in here as well, so all the properties that are associated with that, type of concentration, curve number, if that's applicable, C factor for the rational method, different things like that. And as you can see, all of the HGL and EGL, all of those are 0 for here. And a little bit earlier, showing that all the pipes in here are simply laid out as 15-inch pipes all across the network without really any kind of consideration for elevation or anything.

So first step is going through the ribbon toolbar up in Civil 3D. So once you install InfoDrainage, this ribbon toolbar shows up in Civil 3D, having that basically mapping to the file name, creating a new network, that screen previously showing that we would be exporting the pipe network, selecting that pipe network, also selecting the network for-- or the surface that would be associated with everything. Here, we're just mapping up things between what it is in Civil 3D to what it is in InfoDrainage. And these are templatable, so being able to open up that kind of configuration and being able to reuse that across all kinds of different projects.

We do then flip over into InfoDrainage, where you can see similar kind of outline for our network here. You can see, again here all the diameters in here. Those are all 15-inch pipes. Pulling up some of the attributes for the catchment areas, just doing some rational method analysis really for this. And then finally looking at one of these profiles, we can get an idea that the elevations weren't really considered at all. We were just plopping it in. And then we're relying on InfoDrainage to be able to size everything. So you can see it's just kind of a basic layout there.

Once we go through that, the next step is to design the pipes, networks that are along the road, as well as the culverts in there. So going ahead and playing this, everything up here, you probably saw it on the first video that you do need to create these flow paths. These flow paths are basically just telling you like what pipes I have in here. And once you go to size it, being able to reference that set of pipes.

But the first step in all of this is going to be sizing-- or creating a rain event. So here, I've got the Rainfall Manager pulled up. And I'm using the built-in Noah-- Noah Atlas 14 River Builder. So again, pulling up one of those profiles, like you can see there, the most downstream end was actually outside of the surface. And so it just brought it to 0, which is why that looked a little funky.

But this is the preliminary design wizard. So we're looking at this one network here that we just had pulled up. Stepping through here, I'm going too fast, stepping through here is basically setting up boundary conditions. So we've got a pipe library, pipe size libraries, manhole libraries.

And once we go through this routine of selecting the storm, selecting some of those boundary conditions, once we do get that information, it will go through an algorithm and size all those pipes for you, set new elevations for everything. And as we pull up the profile here, we see that outlet there has changed a good bit from what it was previously. And I think just simply because this is a fairly straightforward, simple process, we've got the profile looking pretty similar, except for that downstream end obviously.

So taking a look here with the roadside ditches, this video goes through that process of creating these simple junctions. Those are going to be the endpoints of our trapezoidal ditch in this case, so not a lot of information that needs to necessarily go in there. But you do have the option of including the parts family. So having that in there as that transitions back into Civil 3D, making sure that the right part gets populated. Excuse me.

But looking at the side of the road here, we've got an outfall for that culvert. So that's where that ditch is going to end up being. So taking a look at the trapezoidal channel connection link. And as we go up through here, just kind of following along the roadside up to that junction that was just created in order to have the trapezoidal channel.

With this trapezoidal channel, it's very similar process that you'd go through as the pipes to be able to have this being sized with that design wizard. And as we go through here, we can see that trapezoidal channel all cut out. And as we go through we can make adjustments if needed to those different vertices. I'm adding that as a new flow path. Again, that's because we need to define essentially what we're looking at in terms of the design goals.

And as this scrolls up, we've got the length of the-- or the-- what am I saying-- the profile that we're looking at. And pulling up that design wizard again, just stepping through the motions, essentially there's some inputs that need to be put in, so Manning's n. Do some kind of preliminary-- or looking at the shape and size of the trapezoidal channel, we don't have any of that information populated. But again, just going through that network design wizard and having it specify the height and width, bottom channel width, all that kind of stuff in the trapezoidal channel.

All right. So looking at the bypass links in here, we've got the area down here where we're going to be including that bypass link. And it's a pretty simple process, pretty important in transportation projects as well, as we can't get all the water in the inlets like we'd like to. With this, we do limit the amount of water getting into these inlets by using the HEC-22 equations. There's also some rating curves and that sort of thing that can be input.

But the idea here is to select some boundary conditions. We've got the amount of estimated runoff for the storm event that we want to size it for. And then inputting some of the parameters for the road, longitudinal slope, cross slopes, Manning's n, as well as the configuration for the inlet itself. If you're familiar with the HEC-22 equations, a lot of these inlet types and locations should look pretty familiar with that.

And again, just specifying some of those criteria so that eventually on the right side there, we'll get a nice graphic looking at the spread that's approaching, what's being captured, the spread afterward. Once we get that all in, we know that we are bypassing some flow. So where does that flow end up going?

I've got the custom cross-section already built out to here. And we'll take a look at what that cross-section looks like here in a minute. But as a representation of the curb inlet and some of the roadway connecting those two structures and including that as a bypass, we've got that information in there now. So you can see that shape where we've got the cross slope going down into the curb and the curb going up and then just kind of flat after that.

Once you do have all that in, we can certainly run the simulation. Of course, we need to validate models before we're able to run the full analysis with them. But what you'll see here in a second is the results from that run. And as we pull up the profile for the-- or I guess the results from the different storm events that we have in here, what kind of max flow we're getting in, the typical curb section that I have in there. So you can see there's a little bit of depth. And as we pull up some more graphical results, we can see the flow there as well that is going through that bypass link.

So we already went through the preliminary design wizard. So like I mentioned before, it's just using the rational method for that site. The real meat and potatoes of the whole simulation is to run a full analysis. So this is a fully dynamic routing, everything from through the hydrograph and all that. It's not just using a steady state type of approach. It is a full dynamic simulation, which gives us theoretically the best results tends to be a little bit conservative using the more standard steady state approach in there.

But we can see after that full analysis is run, we can also pull up profiles, play through the simulations, look and see if we've got any surcharging in any case. You can see on the profile there, the water, as we're playing through the simulation, that water filling up in the pipes. And if we did have any issues, we would start to see some warning icons on there, highlighting that we do have some issues in there.

We also have a handful of different kinds of reports. And a lot of these reports do look fairly similar. This auto report in particular, I like to call it a dummy check. If you have some regulations that you're trying to meet, whether it's a certain amount of cover over the area or velocities that need to be within a certain range, you can set these up in order to highlight where those issues are. So as you're submitting into flood agencies or DOTs or whatever else, you can be sure that the criteria that they're looking for is actually correct rather than submitting something and then having to redo it because you missed a check in there.

But, yeah, do have the audit reports in there as well as some other results in there being pulled up in graphical or tabular results, also comparison reports. And then finally, looking at the flexible reporting. So in this case, this is an example of basically a storm tab sheet.

You can see in Excel. I've got the report itself on the left side. All those values were 0 or N/A in that Excel spreadsheet. And then I've got some other tabs there where we're going to be pulling out some of the information.

These are templatable. So once you get things set up, you can reuse these across different projects and pull in and copy and paste that data into the Excel sheet that you have set up in order to produce that report in that particular style that's needed. So here, we're were exporting out this information into a CSV format. Once we get that named and everything, we are going to do the same thing for some of the other results. But the idea here is to take that information from the CSV and then simply copy and paste it into the appropriate tab.

Just a little bit of how this is set up. Once you do run the preliminary design wizard, you can get some of those rational method results out. If you do want some of the more dynamic results, you do have to rerun it through that full analysis, as we're doing here. Again, a template just built out to our needs essentially for how we have that Excel sheet set up and then exporting out to a CSV and doing the same thing, copying and pasting that data into the appropriate tab.

And as you'll see here, once we do get that populated, we'll flip back over to that report page and see that the values in here have now been populated. So again, kind a quick and easy way to be able to get those reports in the format that are needed. That was really the whole basis and reason behind the flexible reporting.

And final design, so bringing it back into Civil 3D here. So we've got the [? Unified ?] tab again here at the top there. And just like we're importing, we're now exporting-- or exporting to InfoDrainage. Just like we were exporting, we're going to now import from InfoDrainage, selecting that file that we're going to import and then also the different parameters that are associated with that. So we've got the network in there that we're going to, I guess, quote unquote, "copy over." And then also the different information associated with the parts family mapping here, again, where we're taking whatever we had in our InfoDrainage and then mapping it to what it's supposed to be in Civil 3D.

So you can see not only did our pipes update, which we'll take a deeper look in a second there, but also some of the grading has been incorporated here from those ditches that were included. So lots of stuff gets carried over. So you can see the new data in here showing that proposed contours and down here at the bottom where we've got some profiles set up.

And these profiles, this is the existing one, just to highlight that these things do change as well. So we can look at that profile. And then take a look at that same profile in the proposed phase, so scrolling back down to that and seeing that. Before they were kind of overlapping. Now those elevations have been modified and updated with those new inverts from the pipes. So if you do have these profiles already set up in Civil 3D, it maintains those connections and less rework, less redrawing that goes into play.

Finally, looking at some of the pipe attributes here, I'm pulling that out to be a little bit bigger. We can see now that the diameters over on the left side there, a lot of them stayed 15 inches. But there are a couple in there that updated to the 18 inch or larger.

And then also scrolling over to the right, the HGL and EGL information that was before 0, all that gets carried over as well for all the pipes in our network. Some other attributes that get carried over, there are flow data that-- max flow data that gets carried over in there. And then in the extended properties data set, things like velocity can come over as well. So again, makes it easy for putting in the-- if you have labels or something like that and you have that all kind of mapped up together, those labels should automatically update as you import the new model. And with that, I'm going to hand it over to Matthew Piggott to go over the rail portion.

MATTHEW PIGGOTT: Thank you, Ryan. I'll now take us through the rail component. So for this example, a prelim concept design has already been conducted. And we are now carrying out our detailed design phase. So this is where we can conform to our local project guidelines, confirm our standard drainage elements or add bespoke details while ensuring constructability. And we can begin to add value to the design, like designing for sustainability outcomes, cost savings, et cetera, and holistically designing with other project disciplines in mind. You can see a bit of a workflow overview here of what I'll be covering for the rail component. But some of the workflows that Ryan covered in roads are applicable as well.

So just a brief overview, the rail component is located to the west of the project. And it includes a track and overpass upgrade. And realignment highlighted here in the first image. And then also part of the scope includes a new station and car park facilities. So I'll highlight this in the video on the next slide.

So as a slight overview, we've got the rail scheme to the west, as I explained earlier. And there's the rail component-- sorry, the road component covering through the whole site. We've got the track here that needs to be upgraded and then the station. And you can see some of the other disciplines involved in that as well. And there's the car park, which is going to require some drainage design updated for that piece as well.

So we can see some of the proposed drainage layouts from before, which we're going to add more detail to in this phase of the design. So that's just the pipe network shown, or highlighted there. And we can open up a Table view to inspect some of the attributes for these pipe structures. We can view lengths, invert levels. And you'll see here that we don't yet have any hydraulic results tied to those, which we're going to do through the process.

We can view tables of information for our structures as well. So that run of pipes have shown here, I've got a profile set up. And as Ryan mentioned too, when we go through the process of adding detail or sizing any extra structures, this is going to update our profile views.

Another way we can view information is using the Project Explorer in Civil 3D. And this is really a great way or a simplified way to make changes to our drawings and plans. You can see here, we can view the profile view of this run of pipes. We can view the attributes to our pipes and structures here as well.

So like we did for the roads, I'm going to export this out into InfoDrainage. And I'm just stepping through the processes again. This whole process is designed to, I guess, go through round trips. So we can update our old models here. I'm going to take the surface with us again to help with the design.

And then from there, we'll go to the mapping portion. You can see if we're doing this process again with the round tripping, a lot of the information is going to be remembered. And then finalize the mapping and then I'll open up the InfoDrainage model.

So just flicking over to InfoDrainage, I'll open that project. Again, just highlighting that this is saved in the Autodesk Construction Cloud. And I can access that through my desktop connection. And I'll just highlight that same profile that we inspected in Civil 3D to show all that data coming across as well.

So looking at the interface of InfoDrainage, we can see at the top in the menu ribbon bar that it's been designed to help us step through typical drainage design workflows, from importing our data, bringing in rainfall, doing a preliminary sizing, and then conducting our full analysis and inspecting those results. In the Import tab, we can load in background layers, like the aerial images shown here. And then we can go through and set up our flow paths and inspect all that data that's come across from Civil 3D.

Like I suggested, this part of the workflow, we've already carried out a preliminary design, so a lot of these sizes are kind of in a good place. And we're just going to add detail. We can play around with our display settings and load in templates of displays that are really going to be suitable to us to help view our design.

That's the beauty of InfoDrainage. We can load templates in for many number of things. And one of the most important is these object templates, which essentially are libraries or of standard types of elements for drainage design or things that we might typically use in our projects, so from subcatchment land use setups, pits, typical pits and inlets, our stormwater controls, or our pipes. An example here is a slot drain or trench drain, which might be typical to a rail project that we can apply as we're doing our design.

So one of the first things we might carry out as well at this stage of the design is a deluge analysis. So we do have a machine learning component to basically spit these flood maps out instantaneously. And these have been trained on tens of thousands of simulations.

So what this is going to do is, I guess, take our surface model and apply a depth of water to it and basically highlight to us where flow is captured on the surface or channelized. And we can see if our initial design and the design surface are actually in conjunction to how we designed it earlier, making sure that the inlets are actually capturing the flow where they need to be.

Another useful part of this is we can actually validate our catchments or add any. So we can see the major flow direction being shown on the screen here. And basically highlighting that we've got this catchment draining to this inlet in the correct location.

OK, so this is where we can begin to add detail to our design. So one of the first things we might do is for this particular catchment here, we've got a track or trench drain or a ditch that's conveying flow to this sag inlet here. And the idea is that we need to take this flow away from the track. So it's important that the calculated depth here is not going to exceed any freeboard levels to, I guess, the [? SES ?] levels or the ballast.

So in the inlets, we can design this up. There are a number of different options. If you've got, say, capture curves from the inlet supplier, you can load them in here. This example is going to have a look at the HEC-22 to help size these inlets as well.

So we're going to add our rainfall designed for the particular return period. And then this is essentially the slope that's leading into the inlet location. So I'm just going to add some values here.

And then once we get through all that, we'll actually start having a look at sizing our inlet. This particular one is in a sag location. So we're going to keep it just as a grate opening. And then we can play around with, I guess, the opening grate lengths and widths, specify a type that we've got on the list here. And you can even add some blockage factors as well. Probably the most important value we're adding here is the depth value. So that's what we're checking for this location.

So that's for, I guess, along the track. Looking at the access road, similar to what Ryan showed in the road component, we can start to add detail to these inlets that are on grade. Checking with our part family, we can make sure that we're designing the same element within InfoDrainage to make sure that it's performing hydraulically And, then go through the same process. This time, we're going to use the HEC-22, but it's going to be on a grade location this time.

So in some of these cases, we're not going to be able to capture all the flow. And as Ryan showed before, we can add our bypass, making sure that gutter spread is not going to-- or is going to be within acceptable limits before it gets captured by the next downstream inlet.

So a lot of these examples are carried out where applicable on the site. And basically, we do this for the whole entire design. So you can see here, we're just doing some checks on the approach flows. We can check the schematics for depths and widths. And we can play around with whether just a grate opening is going to work or we need combination.

There might be typical standards requirements for the types of inlets that are being proposed for this type of project as well. So we try and keep them as standard as possible. Otherwise, we might need to add some bespoke details.

So I'll do some final checks. And once we're happy with them, we can adopt that. So from there, we can perform our detailed analysis.

So Ryan touched on this a little bit before. But the beauty of the analysis is that we're actually using the full dynamic 1D equations here. And this is going to be, I guess, more theoretically accurate in the types of results that we're getting spit out. And these things can account for channel storage, backwater effects. You can apply your entrance and exit losses, flow reversal and also pressurized flow as well.

So we can inspect some of the results here. In this case, it looks like in a few of these types of events, the type of design that we put forward is really handling all of this flow, even in some of these extreme rainfall events. So we can do a bit of optimization on some of these pipe networks and maybe decrease the size, saving some costs.

So for this particular one, just to show an example, we can see that it's handling these flows. And I'm just going to decrease the size of one of these pipes here. So we can do that in many ways. And one of the ways is through the profile, the table view. And then we can run the analysis again and check all those sizes work.

So from here, additionally, we could use other features, like the Clash Detection, to add detail to our design, or the 1D 2D analysis to check how it handle flows and extreme rainfall event. So we're going to add some stormwater controls here. So sustainable drainage design requirements are continuing to be required or even mandated on the projects. And not only can these stormwater controls prevent flooding by capturing and detaining the peak flows, but they can capture and store the water to be recycled, clean before reuse or discharge back into the receiving environment, as well as many amenable functions too.

So I've added a basin here, which is saved into my project template. You can manually draw these in. And going into the properties of it, we can begin to specify types of depths that are required.

And we can play around with freeboard. So design for that, we can add initial depth of water if we're designing a stilling basin. In this case, it's going to be dry.

And the beauty of these stormwater controls in InfoDrainage is the many sizing calculators that come along with it. So you can actually help design for the type of volume or area that's going to be required from the upstream catchment. In this case, we're going to have a look at designing the base level for a side slope. In this case, we're changing from a 1 in 10 and going to a 1 in 5 shape. And when I apply, you can see these changes are directly shown in the screen.

If our drainage goes away from a typical Lincoln node model-- so you can actually see in the plan view the type of space that the stilling basin is going to take up. For our outlets too, there are calculators we can use to get an idea of the type of diameter for an outflow pipe that might be required. I'm just going to manually specify one. And there are many other properties that we can add as well. I'll touch more on the pollution later.

Again, by being true to site, InfoDrainage lets you, I guess, specify the outflow location. So you're getting some real lengths and ideas of where these inlets and outlets are going to be in conjunction to these stormwater controls. So we can have a look at our stormwater controls in a profile view too, so just adding flow path here. I'll just rename it first. And we can see that upstream pipe network discharging into our stilling base in there.

So from here, we can then run our analysis again and start to, I guess, check the hydraulic results for the pipe network and what's leading into that basin. So for this particular rainfall event, we can see that it's a lot of the storage is available to capture more flow. And if we look at an extreme event, we can see that there's actually a flood risk happening.

So what this means is that the water level is actually breaching our freeboard requirements. But it's still being contained in the stilling basin for a 1 in 100 year event. And we can view these results in our profile view or our tables as well.

So from here, we can try and play around with the size and maybe optimize it a little bit to. Another option could be to increase the outlet capacity to drain that flow away more quickly. Or you can add multiple outlet configurations, like a riser or a weir, for example.

So we had a look at adding a base to our design. One of the beauties of InfoDrainage is we can do some optioneering. So have a look at a number of different options to help to add this sustainability element to our design, but also reduce the amount of flows or flooding that's being discharged to the receiving environment.

So in this case, we've got an option for adding some extra stormwater controls. Maybe we've got some space restrictions. So we can add an underground tank to the car park. And we can start to build in a purposeful swale next to the car park and the access road here to try and slow down those flows, but also capture it for a water quality piece.

So once we've analyzed our scenarios side by side, we can generate a phase comparison report. So this is going to be a useful way for us to actually compare the results of all these scenarios side by side. We can do this for multiple storm events and choose which results we're actually interested in inspecting.

And so once we kind of sorted out our table, we can generate a report and then view the results here. So what we're really interested in here is the type of outflows that are going from our design into the receiving environment. So we can see here that by doing nothing in the original, we've got a flow of 1,475 liters per second discharging out. And then these are reduced in our stormwater control options. We can see this is greatly reduced in the basin phase and slightly reduced with our tank and swale options.

So it might be-- because we've got the space, it might be more meaningful to go with the basic design. And then we can take this further by actually looking at water quality piece that goes with that. So we can model pollutants as wash-off in InfoDrainage. So we can add what types of pollutants we're trying to model. And then we can add these to our catchments as a type of concentration.