A project schedule is not just a list of activities with start and finish dates. In engineering, construction, mining, energy, infrastructure, or major maintenance projects, the schedule is a logical representation of how the work is expected to be executed, what conditions must be met, what constraints exist, and what sequence allows the committed milestones to be achieved.
The Value of a Well-Structured Schedule Read More »
Not every schedule that works for project control is also suitable for forensic analysis. This distinction is important. A schedule may be useful for coordinating activities, issuing weekly reports, or tracking general progress, while still being weak as technical evidence in a claim, audit, contractual dispute, or expert review.
RSQI: How to Tell If Your Schedule Is Suitable for Forensic Analysis Read More »
Schedule quality analysis does not depend only on reviewing logic relationships, constraints, float, or resource assignments. Before reviewing those specific findings, it is also important to observe general elements that help determine whether the schedule is clear, organized, and easy to interpret.
General Schedule Observations Read More »
A schedule may have a reasonable start date, an apparently achievable finish date, and an acceptable logic network, while still hiding an important issue: a resource distribution that may be difficult to execute in practice. xerPlanner’s resource distribution curve analysis reviews how labor hours are distributed over time, considering both work already performed and work remaining to be executed.
Resource Distribution Curve Analysis Read More »
One of the key elements of a reliable schedule is ensuring that its activities are integrated into a coherent logic network. In general terms, an activity without predecessors is an activity that does not have a prior logical relationship controlling its start or finish.
Activities without predecessors Read More »
A well-structured project schedule should ensure that its activities are integrated into a coherent logic network. In general terms, an activity without successors is an activity that does not have a following relationship allowing the logical flow of the schedule to continue toward other activities or toward project completion.
Activities without successors Read More »
Maintaining coherent logic relationships between activities is essential to ensure a reliable workflow within the schedule. However, there are cases where an activity may have predecessors and still have an open start. In practical terms, an activity with an open start is not necessarily an activity without predecessors.
Activities with open starts Read More »
Maintaining coherent logic relationships between activities is essential to ensure that the schedule correctly represents the project execution sequence. However, there are cases where an activity may have successors and still have an open finish.
Activities with open ends Read More »
In a schedule developed with Primavera P6, activity dates should mainly result from logic relationships, calendars, durations, and the natural behavior of the CPM model. The more the schedule depends on properly built logic relationships, the more useful it becomes for planning, control, and impact analysis.
Activities with absolute constraints Read More »
In a schedule developed with Primavera P6, activity dates should mainly result from logic relationships, calendars, and durations. However, there are constraints that allow certain time limits to be established for the start or finish of an activity.
Activities with window constraints Read More »
An updated schedule should reflect not only how much progress has been achieved, but also whether the work was executed according to the planned logic. When an activity progresses in the field before the logical condition defined by its predecessor has been met, an out-of-sequence condition may occur.
Out-of-sequence update Read More »
Clarity in activity names is a basic element for a schedule to be properly understood, reviewed, and used. Although Primavera P6 identifies each activity through a unique Activity ID, the activity name remains a key reference for users, reviewers, contractors, control teams, and execution stakeholders.
Activities with duplicate names within the same WBS Read More »
In Primavera P6, an activity can have resource assignments to represent labor hours, equipment, materials, or other components required to perform the work. These assignments support the calculation of units, costs, resource curves, and time-phased resource requirements.
Activities with duplicate resource assignments Read More »
In Primavera P6, activities can store labor hours related to planned, remaining, or actual work. These hours are important for analyzing schedule workload, building labor hour curves, and evaluating how the required effort is distributed over time.
Activities with labor hours without a labor resource assigned Read More »
In Primavera P6, activities can store non-labor units related to equipment, machinery, or other resources that do not represent direct labor. These units are important for analyzing equipment usage, building resource load curves, reviewing operational needs, and evaluating how non-labor resources are distributed over time.
Activities with non-labor hours without a non-labor resource assigned Read More »
In Primavera P6, the Data Date represents the time boundary up to which actual progress has been updated. Everything that happened before that date may be part of the actual record of the schedule; everything from that date onward belongs to the planned future.
Activities with actual dates later than the data date Read More »
In Primavera P6, total float indicates how much an activity can be delayed without affecting a key schedule date, such as the project finish, a contractual milestone, or an imposed constraint. When an activity has negative total float, it means the schedule no longer has enough margin to meet one of those dates under the current conditions.
Activities with negative total float Read More »
In Primavera P6, total float represents the amount of time an activity can be delayed without affecting a key schedule date, such as the project finish, a contractual milestone, or a relevant constraint. A certain amount of float is normal and desirable, as it allows the schedule to absorb variations, uncertainty, and execution adjustments.
Activities with excessive total float Read More »
In Primavera P6, the Finish to Start relationship is one of the most commonly used dependencies to represent the logical sequence between activities. In this type of relationship, the successor activity can only start after the predecessor activity has finished.
Finish to Start links with positive lags Read More »
In Primavera P6, positive lags allow a time interval to be introduced between two related activities. In certain cases, they may represent legitimate planned waiting periods, such as curing, drying, approval, area release, mobilization, or any other period that must pass before the successor activity can proceed according to the defined relationship.
Links between activities with excessively long positive lags Read More »
In Primavera P6, positive lags allow a time interval to be added between two related activities. In simple conditions, this lag may be easy to interpret. However, when the predecessor activity and the successor activity use different calendars, the same lag can produce different effects on the calculated schedule dates.
Links between activities with different calendars and positive lags Read More »
In Primavera P6, activity relationships represent the logical sequence of work. These relationships define how one activity depends on another and support the calculation of dates, critical path, float, and the overall schedule flow.
Negative Lags (Leads) in Activity Relationships Read More »
In Primavera P6, logic relationships between activities represent the project execution sequence. The most common relationship types are Finish to Start, Start to Start, and Finish to Finish, because they usually reflect more naturally how work is performed in the field.
Start to Finish Activity Relationships Read More »
In Primavera P6, it is possible to create logic relationships between activities that belong to different projects within the same database. These relationships, known as external relationships, can be useful for coordinating interdependent schedules, integrating work fronts, or controlling interfaces between related projects.
External Activity Relationships Read More »
