Duct Banks in Civil 3D: How to Model Them in 3D and Automate Underground Electrical Design

A duct bank isn't one pipe: it's an assembly of several pieces, and each one matters for something different.

The conduit matrix. Rows and columns: 2x2, 2x3, 3x4. Each conduit with its size and position. That defines how many circuits fit.

Conduit spacing. Whatever the specification requires for heat dissipation and for the concrete to flow.

The concrete encasement. With its cover above and beside the conduits. It sets the bank's real width and height — and therefore what it clashes with.

Depth. Minimum cover from finished grade to the top of the encasement. It changes under roadway versus under sidewalk.

Manholes and handholes. At every sharp change of direction, at splices, and at a maximum spacing so cables can be pulled.

The trench. Excavation width and depth — what gets paid for and what gets scheduled in the field.

Civil 3D has no dedicated duct bank object. In practice there are three routes, and each one is good for something different.

1. A corridor with a duct bank typical section. You build the section (conduits plus encasement) as an assembly, usually with Subassembly Composer, Autodesk's tool for creating custom typical sections. The corridor repeats it along the alignment and profile. It's the most native route: the bank follows the layout, and you get sections plus excavation and concrete volumes.

2. A pipe network with parallel conduits. Each conduit is a pipe in a network, offset from the centerline. You can use Civil 3D's pipe network interference check and label each conduit. But keeping 6 or 12 parallel pipes in sync when the layout changes is tedious, and the concrete encasement doesn't exist as an object.

3. 3D solids by sweep. Sweep the duct bank section along a 3D polyline. It's quick, and it looks right in cross-discipline coordination. But it's a dead object: it doesn't update when the route changes and it can't be labeled.

One typical section per configuration. A real project has several banks: 2x2 low voltage, 3x3 medium voltage, variants under roadway and under sidewalk. Each one is a typical section someone has to build and maintain.

Transitions. Wherever the bank changes configuration, enters a manhole or crosses a road, the section changes. Every transition is a manual corridor edit.

The profile. The bank has to keep minimum cover while going over or under every utility it crosses. Setting that profile by hand, crossing by crossing, is slow and easy to get wrong.

Manholes. Placing them at every change of direction and meeting maximum spacing.

The takeoff. Linear feet of conduit by size, cubic yards of concrete and excavation, number of spacers and manholes. Usually from a spreadsheet that isn't connected to the model.

A custom plugin turns the duct bank into something you choose and generate, instead of draw.

What it does:

1. Takes the route. A polyline in plan or an existing alignment.
2. Takes the configuration. The bank type: matrix, sizes, spacing, cover. Ideally from a table of your utility's standard types.
3. Computes the profile. It follows the ground at minimum cover and, wherever it crosses another utility, drops or rises to keep the required separation. If no solution exists, it flags the crossing instead of forcing an elevation.
4. Builds the 3D model. Individual conduits, concrete encasement and trench.
5. Places manholes at changes of direction and wherever maximum spacing is exceeded.
6. Delivers the takeoff. Conduit by size, concrete, excavation, backfill, spacers and manholes.

If there's one reason to take the duct bank to 3D, it's this.

An electrical duct bank almost always crosses water, sanitary sewer and storm drainage. Every crossing has rules: minimum separation between power and water, which one goes on top, what protection is required. Those rules come from the applicable electrical and plumbing codes and from each utility's specifications.

In 2D, those crossings are two lines touching in plan. You can't tell if there's a conflict.

In 3D, with every utility modeled at its real elevation, each crossing can be checked:

• Civil 3D includes an interference check for pipe networks.
• To coordinate all utilities together — including a duct bank modeled as a corridor or solid — the usual route is Navisworks clash detection.
• A plugin can check minimum separations between the duct bank and each utility directly, which is what actually matters and what clash detection doesn't measure.

Week 1 · Standardize your duct banks. List the configurations your office or utility uses: matrix, sizes, spacing, cover, under roadway and under sidewalk. One table.

Week 2 · Write the crossing and manhole rules. Minimum separations with each utility type, maximum manhole spacing, minimum conduit bend radius.

Week 3 · Model one real duct bank. With a corridor and a typical section, or with a Dynamo routine. Compare the takeoff against the one you already delivered.

Week 4 · Check the crossings in 3D. Combine the bank with the same project's water and sewer networks and check separations. Whatever you find there is the case for automating it.