Negative Float in Retained Logic and Progress Override

Introduction

In project management, scheduling software like Primavera P6 plays an important role in planning, executing, and monitoring project activities. One of the critical aspects of effective scheduling is ensuring that activity relationships are logical and accurately represent the project’s workflow. An illogical or inaccurate relationship setup can lead to misleading schedule outputs, such as negative total float values, which can cause confusion, delay, and misleading project timelines.

This article dives into how logical relationships in Primavera P6 affect total float calculations, particularly when using the “Retained Logic” and “Progress Override” settings. We’ll explore why a schedule might display a negative total float of like -20 days with retained logic and how changing the setting to progress override can adjust total float values and address out-of-sequence activities.

Understanding Activity Relationships in Primavera P6

Activity relationships define the dependencies between tasks in a project schedule. The four primary relationship types in Primavera P6 are:

1. Finish-to-Start (FS): The successor activity cannot start until the predecessor activity finishes.
2. Start-to-Start (SS): The successor activity cannot start until the predecessor activity starts.
3. Finish-to-Finish (FF): The successor activity cannot finish until the predecessor activity finishes.
4. Start-to-Finish (SF): The successor activity cannot finish until the predecessor activity starts.

Logical relationships are critical for an accurate schedule because they dictate the sequence of activities and the flow of the project timeline. Illogical relationships or improper sequencing can result in out-of-sequence progress, negative float, delay, and inaccurate critical paths.

Retained Logic vs. Progress Override

When updating a schedule with actual progress, you might encounter out-of-sequence activities—situations, where work on a successor activity, begins before its predecessor is complete, contrary to the planned logic. Primavera P6 offers two primary methods to handle out-of-sequence progress during scheduled calculations:

1. Retained Logic

• Definition: Retained logic respects the original planned relationships and logic, even if actual progress deviates from it.
• Impact: If an activity starts out-of-sequence, retained logic will delay the remaining duration of the out-of-sequence activity until its predecessors are complete.
• Result: This can lead to negative total float values because the software anticipates that the remaining work cannot logically proceed until predecessors finish, creating a scheduling conflict.

2. Progress Override

• Definition: Progress override ignores the logic of the relationships when actual progress doesn’t follow the planned sequence.
• Impact: The software allows activities to continue without considering the original dependencies, effectively overriding the planned logic.
• Result: This can eliminate negative float and out-of-sequence progress by adjusting the schedule to reflect actual progress, but it may compromise the logical integrity of the schedule.

Negative Total Float with Retained Logic

A negative total float indicates a delay in the schedule that affects the project’s finish date or a constraint that cannot be met based on the current plan. When using retained logic:

FREE COURSE

Primavera Online Basic Course -English

Online Primavera P6 Course for Engineers & Construction Managers Learn how to use Oracle Primavera P6 to plan, schedule, monitor, and control…

• 5,405 students
• WhatsApp support group
• Certificate

Start free

• Out-of-sequence Progress: If an activity starts before its predecessor finishes, retained logic schedules the successor’s remaining work after the predecessor’s completion, causing delays.
• Negative Float Generation: The delayed remaining durations can push out the project’s finish date or violate constraints, resulting in negative total float values like -20 days.

Example Scenario

• Activity A (Predecessor): Original duration of 5 days.
• Activity B (Successor): Finish-to-Start relationship with Activity A, original duration of 5 days.
• Actual Progress: Activity B starts on Day 3, before Activity A finishes.

With Retained Logic:

• The remaining duration of Activity B is scheduled to resume after Activity A finishes, causing a delay.
• If this delay impacts the project completion date, a negative total float appears.

Impact of Switching to Progress Override

When you switch the scheduling option to progress override:

• Out-of-Sequence Progress Handling: The software disregards the logical relationships for out-of-sequence activities, allowing them to continue based on actual progress.
• Total Float Adjustment: The schedule recalculates without the delays imposed by retained logic, often eliminating negative total float.
• Logical Integrity: While it resolves negative float and removes out-of-sequence progress, it may lead to an illogical schedule that doesn’t accurately represent the project’s dependencies.

Ensuring Accurate and Logical Relationships

To maintain a reliable schedule where total float remains consistent regardless of the scheduling option:

1. Validate Relationships:
   • Regularly review and confirm that all activity relationships are logical and accurately represent the project’s workflow.
   • Avoid unnecessary or illogical dependencies that could cause conflicts.
2. Manage Out-of-Sequence Progress:
   • When out-of-sequence progress occurs, assess whether the original logic needs adjustment.
   • Update relationships if the actual workflow deviates from the plan, ensuring the schedule reflects reality.
3. Choose Appropriate Scheduling Options:
   • Use retained logic when it’s important to maintain the original plan and relationships.
   • Select progress override cautiously, understanding that it may compromise the schedule’s logic.
4. Analyze Negative Float:
   • Investigate the root causes of a negative total float rather than only adjusting scheduling options.
   • Address issues such as unrealistic constraints, inaccurate durations, or illogical relationships.

Conclusion

Logical relationships are the backbone of an effective project schedule in Primavera P6. Negative total float values under retained logic often highlight underlying issues with activity sequencing or unexpected progress deviations. Switching to progress override can temporarily resolve negative float and out-of-sequence progress, but it may mask deeper problems and result in an illogical schedule.

By ensuring that relationships are accurate and logical, you can maintain consistent total float values regardless of the scheduling method. This approach leads to a more reliable schedule that truly reflects the project’s dynamics, enabling better decision-making and successful project delivery.

By prioritizing logical relationships and understanding the implications of scheduling options, project managers can leverage Primavera P6 effectively to deliver projects on time and within scope.

If you are struggling with your project schedule relationships, We can help you with one of the following:

1.       Intermediate Planning course

2.       We provide project management services where we can do the job for you. Simply send your request to: [email protected] and we will contact you shortly

Download the Resources of this Article 

---

Keep in Touch

Join our Email Newsletters and receive FREE weekly useful content!

Your Name

Email

---

Related posts:

The Earned Value Cost does not equal the Actual Cost. How does the planning department balance the management triangle How to get connected to Planning Engineer Website Heads Up WHAT’S THE FIRST WORD YOU SEE? Why Project management and project management plan