With Robert Martinko, Application Engineer, Augmenta
Most electrical BIM teams build a conduit run schedule at some point. The real question is when. The trend is changing, but on a lot of jobs it might come together near the end, as a handoff document. It still has value at that point, but most of the value it could have provided for teams has evaporated.
Robert Martinko is an Application Engineer at Augmenta and an electrical engineer by training. He has spent more than 10 years starting up BIM teams for electrical contractors, so he has seen run schedules built early, built late and not at all. We asked him what changes when the run schedule comes first. His answer was that almost every step after it gets easier, and that it all starts from a drawing every team already has.
Here are the five reasons he gave for building it before anyone routes a run.
Before a BIM manager can staff a job or give the PM a real number on modeling hours, they need to know what has to be modeled. The run schedule tells them. It lists every feeder, where it starts, where it ends and what size it is, so the team can see the size of the job before the first conduit goes in.
“How can you have a ballpark for how long something is going to take until you get what it is you need to model?”
It also gives you a baseline. When the schedule changes, you can compare versions and see what moved, instead of finding out in the model.
Good conduit modeling starts with a picture of the whole project. Without a schedule, a modeler might run a feeder from DP to LP3 and only later notice that RP2 sits right on the same path. That run could have gone in the same rack from the start.
With the schedule open, you can see every run the project needs, then plan each floor the way you would in the field. Rob described it this way:
“I’m going to take the central corridor, because I’m going to peel off both ways to hit those panels.”
The result is fewer one-off runs, cleaner racks and less conduit modeled twice.
People roll on and off projects all the time. When run IDs and source and destination information live in the schedule and in the model, the next person can compare the two and see exactly where things stand.
Without that, they are guessing. Say five of the DP conduits are modeled and the sixth isn’t. Rob asked the obvious question:
“Unless he visually checks every DP to see if there’s a conduit there, how is he going to know?”
On a big job, that’s hours of checking. Worse, it’s conduit that gets modeled twice.
Single lines change, sometimes late. If you have been modeling without a schedule, it is hard to tell what a revision actually touched. With a schedule, you update it first, and then you know which runs moved and which sizes changed. Rob’s example was a common one: a run that was one 4-inch conduit becomes two 3-inch. You fix those runs and leave the rest of the model alone.
Estimates are built early. When the run schedule only gets finished at the end of the job, the comparison between what was estimated and what was modeled comes too late to help anyone. Build the schedule early and you can sit down with estimating after the first floor and say, here’s what you carried and here’s what we’ve got. That lesson can shape the rest of the floors on the same job, and the next bid, instead of ending up in a closeout report.
None of this takes new software. A run schedule can live in a spreadsheet, built from a drawing you already have, before anyone has spent an hour routing. What changes is the order of the work. Rob summed it up this way:
“The more we can be smart and organized in our processes, the more we can make smart decisions.”
If your team already builds run schedules at closeout, try moving the work to the front of the next job and see what it saves.
Watch Rob walk through the five reasons that every electrical BIM team should create conduit run schedules earlier in the process.