I have been having some issues using Create Cut Fill Volumes to properly calculate Subsoil Excavation. I have my proposed model, existing ground terrain, existing features model, and subsoil excavation model. For the subsoil, I just created a template to run along a corridor for the limits defined by my geotech. I have several different types of templates but essentially, they go down a defined depth and back up to existing ground at 1:2. The volume option for my SubSoil Feature is set to Unsuitable.
When I run Cut/File Volumes I get a section that looks like this in my subsoil area.
As you can see, it is NOT computing the additional fill area needed between the existing ground and bottom of proposed. The smaller area below existing ground in the middle of the section is the existing roadway. This gets removed with a different pay item, but then must have embankment placed in the area voided by the existing pavement. It seems to only be calculating the area above existing ground that is not also above subsoil excavation. It should be doing something like this:
The yellow would be quantified as Subsoil Excavation AND Embankment. The blue would be embankment. But the software is not calculating the additional embankment required above the subsoil excavation.
I have previously tried a different approach where I only calculate subsoil excavation in one file, and then standard cut/fill in another file (without attaching the subsoil model). This works in most cases except for situations like this:
In this image, I ran the subsoil earthwork in another file, and then attached it to my standard earthwork file to see if there were any issues. You can see here that we have a red shape for the excavation below existing in order to construct the proposed elements. The issue is that this should NOT be calculating excavation because subsoil excavation would already remove this material. Furthermore, the embankment for the subsoil is going to fill back up to existing when it should only be filling to the bottom of the proposed elements.
So, in situations where the proposed surface is entirely above existing ground, my process of splitting the volume calculations into different files works just fine. It's only when the proposed elements are in cut that we have an issue where extra cut and fill will be calculated.
If anyone has any suggestions are to what I am doing wrong, please let me know. Or perhaps there is an issue with the way the volumes calculate that needs to be address by Bentley.
Thank you
When using Create Cut Fill Volumes the additional fill will be identified if "Compute Unsuitable" is turned on as shown in the example below
I have that checked and that is not happening.
Zachary Billings, P.E.
Senior Roadway Engineer (Licensed in FL and MI)
CONSOR Engineers, LLC
System Info:
Windows 11 | Intel Core i7-13700k | Nvidia RTX 3080 FTW3 Ultra | 32 GB of RAM | 2 TB Western Digital Black SN850x NVME
Power GEOPAK V8i Select Series 10 Version 08.11.09.918 | FDOT SS10 Version 01.04.01
ORD Version 10.11.00.115 | FDOT Connect Version 10.11.00.02
YouTube Page for ORD: https://www.youtube.com/channel/UC3S-94f7_yUJ-GMhMYPhInA
I see you have "Split" set to true, but no other "Remove" options... Double check that those are there to better define the area. It seems to require an additional feature definition or two that can better isolate the area.
Bentley Accredited Road Designer | Bentley Accredited Road Modeler
colliersengineering.com
I have had a feeling this was the problem. You can see from my first image that when I choose split, I do not get those additional options to show up. I have seen those options in other videos, but was thinking that perhaps they were removed in the latest version of ORD.
I am using the latest version of ORD: 10.10.21.04.
Are you using this version? Or could this possibly be an issue with the FDOT workspace that I am using?
Thanks
Check your FDOT files. I haven't updated to 10.10.21.04 (Currently on 10.10.01.03). I'm using FDOT 10.10.00.01 and see those options available. Maybe a missing or broken dll in the newer version ??