Determining where to place your crews and how to manage them not only assists with project deliverables. It also helps your crews manage the work and flow of the job site, allowing them to be more productive and inclined to remain a part of your team. So, what can you focus on to make project teams successful while also elevating project success? Crew Logic. Let me Explain.
In our recent webinar with AACE International, we pointed out the importance of crew logic. Or, as I sometimes call it, “The Silent Killer of Construction Scheduling.” Sure enough, we got quite a few questions about what crew logic is. To us, this was not a surprise… What people are familiar with, though, is scheduling.
Construction scheduling is an essential part of every project of any size. Its success or failure largely depends on the proper allocation of resources. How these resources are allocated hinges on the logic within the project schedule. Therefore, the logic put into your project schedule needs to be consistent with what is feasible–not just with what is desirable. Read on to see what I mean.
Types of Logic Within a CPM Schedule
Before getting into the nitty-gritty details of crew logic, I should explain the importance of rational logic in CPM scheduling. Critical Path Method (CPM) Scheduling develops a comprehensive work plan that showcases how activities will get done within a construction project using network diagrams. The main benefit of using a CPM schedule is its ability to identify relationships and dependencies between all activities within the entire project network. CPM essentially creates a blueprint for project performance.
The relationships within this network are referred to as logic. Logic is the reason CPM scheduling programs can run calculations. It explains the order of the program, which is sometimes referred to as the project roadmap. This order is how the program calculates float values, start dates, finish dates, and so on.
It is critical for schedules to be built with quality in mind. High-quality construction schedules ensure that all the logic within them is accurate. However, the first schedule created often has incomplete logical information.
What does this mean?
Well, within CPM Scheduling, there are two kinds of logic: Hard Logic and Crew Logic.
All About Hard Logic
Typically, the initial project schedule contains precise “hard logic” information. Hard logic refers to the necessary sequence of tasks, dictated by what is physically feasible for the project workflow. It outlines an order of operations that cannot be rearranged or modified.
The hard logic in this CPM schedule is explaining that you cannot begin Mechanical, Engineering, and Plumbing (MEP) work on level one until you have completed the structure on level one. Similarly, you cannot start the structure of the second floor until you are done with the first floor’s structure because you cannot build in thin air. You need the structure below to do so.
The thing about hard logic is that it represents how project schedules are wired. But what happens when an activity gets delayed?
The schedule above depicts that the framing activity on the first floor was delayed. And, without crew logic present, the schedule is indicating that framing on the first and second floors will happen simultaneously. This is otherwise known as trade stacking. The issue here is, without an additional crew, the framing activities would be impossible to complete within their time parameters.
Furthermore, trade stacking on top of delays does not reflect a feasible reality, especially considering the overbearing amount of resource and crew restraints happening in the built environment. Additionally, when activities automatically stack on top of each other, float becomes consumed. And, when float is consumed, everything becomes compressed by design.
When everything is compressed, inefficiencies result–especially when you do not add people and are not sure if the area (or trade) is truly critical or not. This is where missing crew logic becomes “the silent killer” in construction. So, I’ll finally explain what crew logic means and why it is crucial for project success.
What is Crew Logic?
Crew logic is a form of “soft logic” that assigns relationships to activities that are reflective of where a crew is going to move next–based on means, methods, & crew constraints. For example, you might want your crew flowing from floor to floor or area to area.
Let’s take a look at the same original project schedule with the same hard logic, but this time with crew logic added to it:
Now, the schedule has crew logic (featured in blue) embedded within it. The crew logic notifies the scheduling program that, for example, you cannot start framing on level two until the framing is complete on level one.
Why is Crew Logic Important?
Crew Logic identifies crew constraints reflected in the plan, makes the schedule more reactive, and generates a more reliable & accurate critical path. You know, because the program is telling you that you cannot begin framing on the second floor until it is finished on the first floor.
Without it, when an activity gets delayed, it overlaps with other activities on different floors–meaning you will need additional crews to complete the stacked trades – which would otherwise get lost in the schedule file unless the PM and Super were paying very close attention.
Again, considering the skilled labor shortage, the multiple crews required to keep up with the plan may not be feasible. Basically, if you are not keeping a close eye on these things, your project will be delayed–not just by a week or two, either…
However, at the end of the day, delays happen–especially nowadays. They are essentially inevitable. That being said, it is how you handle delays that matters most.
Discussing Delay
This might seem contradictory to many people. After all, who wants to talk about delays when a whole lot of money is on the line?
I do, and so do many others to whom I have proved that discussing delay makes things a whole lot easier in the long run. Why is this?
Well, personally, I believe scrambling at the end of the job causes too much harm–mentally, emotionally, and physically. Not just for one person either, but for everyone involved.
I also do not believe in sending out a schedule that says I am going to achieve something that I cannot. Rather, I want the program that I am using to tell me exactly when a delay happens so I can have conversations with relevant stakeholders about it to figure out the plan for mitigation. Or better yet, use the schedule as a tool to show trade contractors the delays and the consequences of the delay.
On the other hand, if you do not discuss the delays and just keep moving down the line, your schedule becomes compressed and potentially unachievable. Schedule compression comes with a lot of risks, including but not limited to the following:
- Schedule quality & viability
- Inefficiencies in trades
- Further delays & overruns
- Claims & Disputes
- Impacts on quality & safety
Creating a Reactive Schedule
Without crew logic, impacts are not clear… Trades become stacked by design, critical paths shift, and float becomes consumed–all of which are a recipe for delays, inefficiencies, and future disputes.
Essentially, crew logic makes the schedule much more telling of when impacts are happening and the immediate effect of those impacts. This helps right the ship before it is too late. It also aligns with your crew’s own constraints.
Most importantly, your crews are not merely resources. They are people. They are not expendable, especially in today’s environment. If you take the time to know precisely what your crew teams can accomplish along with their plan to be successful and then implement that information into the schedule, your project will inevitably run smoother.
