Schedule recalculation engine

What it does

A built-in critical path engine. It walks the schedule's relationships forwards and backwards using each activity's work calendar (including shifts, lunch breaks and holidays), retained-logic progress handling and constraints, and produces early and late dates, total float and the critical path. It is what makes Time Impact Analysis and Collapsed As-Built possible, because both need a schedule recalculated under a hypothetical.

What it helps you achieve

• Answer 'what if' questions on a real schedule without opening P6.
• Get delay results that come from recalculation, not from guessing at knock-on effects.

How to run it

Where to find it: Runs behind Time Impact Analysis and Collapsed As-Built

1. There is nothing to configure: it runs automatically whenever you run a Time Impact Analysis or a Collapsed As-Built analysis.

What you get

• Dates and float that respect each activity's own calendar, shifts and holidays.
• Out-of-sequence progress handled the way P6's retained logic handles it.

Good to know

• It has been checked against real Primavera P6 exports: on the schedules used to validate it, its late dates and total float matched P6's own stored values on every comparable activity, and its early dates matched on all but a handful (well under one percent).

Frequently asked questions

Does it replace Primavera P6?

No. It reads P6 exports and recalculates them for analysis. You keep scheduling in P6.

Go deeper

• Critical path method: a worked example →
• What total float tells you about risk →

Terms used here

• Critical Path Method (CPM)
• Retained Logic
• Progress Override
• Total Float