How to Find and Fix Missing Logic (Open Ends) in P6

What Is Missing Logic (Open Ends) in P6?

In Primavera P6, 'missing logic' – also called open ends – refers to activities that lack a predecessor, a successor, or both. A proper schedule should have every activity tied into the network except the very first and very last. When activities dangle without logical connections, the schedule loses integrity and fails basic DCMA 14-point checks.

Open ends are classified into two types:

• Open start (missing predecessor): The activity has no predecessor, meaning it can start at any time without being constrained by earlier work.
• Open end (missing successor): The activity has no successor, meaning its completion does not drive any subsequent work.

Both types create floating activities that undermine the critical path and make the schedule unreliable for planning and control.

Why Dangling Activities Break a Schedule

Missing logic is one of the most common DCMA 14-point failures. The DCMA metric for missing logic requires that no more than 5% of activities have open ends (excluding the project start and finish milestones). If your schedule exceeds this threshold, it will fail the logic check. Beyond the metric, open ends cause several problems:

• False float: Dangling activities often show excessive total float, masking the true critical path.
• Inaccurate critical path: Without proper links, the critical path may skip key activities, leading to wrong completion date predictions.
• Poor schedule credibility: Stakeholders lose trust when activities appear disconnected from the project workflow.
• Ineffective resource levelling: Resources assigned to open-ended activities may not be levelled correctly, causing overallocation or gaps.

For forensic delay analysis, missing logic makes it impossible to determine the true cause of delays because the network does not represent the planned sequence of work.

Finding Open Ends Quickly in P6

P6 provides several ways to locate missing logic. Here are the most efficient methods:

1. Use the DCMA 14-Point Check (Schedule Checker)

In P6 Professional, go to Tools > Schedule Checker and select the DCMA 14-point check. The report will list all activities with missing predecessors or successors. You can export this list to Excel for further analysis.

2. Run a Tabular Report

Create a report that filters on Total Float or Activity ID and includes columns for Predecessors and Successors. Then sort or filter to find activities with blank predecessor/successor fields. You can also use the Activity Details view to scan for activities with no links.

3. Use the Activity Network View

Switch to the Activity Network view and look for activities that are not connected to the main flow. Isolated nodes or chains that do not connect to the project start/finish are easy to spot visually.

4. Use the Trace Logic Feature

Select an activity and use Trace Logic (right-click or toolbar) to see its predecessors and successors. If the trace stops unexpectedly, you have found an open end.

For a free, browser-based alternative that performs these checks instantly, you can use Project Assure. It parses your XER file locally and runs DCMA 14-point checks, including missing logic analysis, without uploading any data.

Fixing Open Ends Correctly (Not with Constraints)

Once you have identified open ends, the correct fix is to add logical relationships – not constraints. Many schedulers mistakenly use constraints like 'Start On' or 'Finish On' to anchor dangling activities, but constraints do not replace logic and often introduce new problems.

Step-by-Step Fix:

1. Identify the intended sequence: For each open-ended activity, ask: 'What work must happen before this activity can start?' and 'What work must happen after this activity finishes?' Consult the project team if needed.
2. Add predecessor relationships: Use Finish-to-Start (FS) relationships by default. For example, if a concrete pour must follow rebar installation, link the rebar activity as a predecessor to the pour.
3. Add successor relationships: Ensure every activity (except the final milestone) has at least one successor. If an activity is the last in its path, link it to the project finish milestone.
4. Use milestones for start and finish: Add a 'Project Start' milestone with no predecessor and a 'Project Finish' milestone with no successor. Then link all initial activities to the start milestone and all final activities to the finish milestone.
5. Avoid constraints: Only use constraints when absolutely necessary (e.g., mandatory dates from contracts). For routine logic fixes, relationships are always preferred.

Common Mistakes to Avoid:

• Adding constraints instead of logic: A 'Finish On' constraint on a dangling activity does not connect it to the network; it only fixes its date. The activity still lacks logic and will not drive successors.
• Overusing 'Start to Start' or 'Finish to Finish': While these have their place, FS is the most common and should be used unless there is a clear reason otherwise.
• Leaving activities with only a predecessor or only a successor: Both ends must be connected for the activity to be fully integrated.

Verifying the Fix

After adding relationships, re-run the DCMA 14-point check to confirm that the percentage of open ends is below 5%. Also, recalculate the schedule and review the critical path. If the critical path now flows through all key activities, your fix is successful. You can also use Project Assure to re-analyse the XER and see the updated metrics instantly.

Remember, missing logic is not just a DCMA metric – it is a fundamental flaw that undermines the entire schedule. Fixing it properly ensures your schedule is reliable, defensible, and useful for project control.