KonnectxD
DEFINITIVE GUIDE

The Definitive Guide to Schedule Intelligence for EPC

Konnect xD Engineering·25 min read

Introduction

Project planning is the backbone of every successful EPC (Engineering, Procurement, and Construction) project. Yet the tools and standards used across the industry — Primavera P6, XER files, CPM scheduling — remain opaque to many stakeholders who depend on them daily.

This guide demystifies the fundamentals. Whether you're a project director reviewing a contractor's schedule, an asset owner evaluating project health, or a digital architect building planning analytics, you'll find practical knowledge distilled from real-world EPC experience.


What is Project Planning?

Project Planning is the systematic process of defining project scope, objectives, and the steps required to achieve them within constraints of time, cost, and resources.

Think of it like GPS navigation for your project: you define where you are, where you need to go, and the system calculates the best route while continuously adjusting for real-world conditions.

The Core Components

| Component | What It Defines | Why It Matters |

|-----------|----------------|---------------|

| **Scope** | What work needs to be done | Prevents scope creep |

| **Schedule** | When each activity happens | Drives resource allocation |

| **Budget** | What each activity costs | Controls expenditure |

| **Resources** | Who does each activity | Ensures capacity exists |

| **Risk** | What could go wrong | Enables proactive mitigation |

EPC Project Scale

| Project Type | Typical Activities | Duration |

|-------------|-------------------|----------|

| Small Modification | 500-1,000 | 6 months |

| Plant Turnaround | 2,000-5,000 | 3-6 months |

| Medium EPC | 5,000-15,000 | 1-3 years |

| Mega Project | 20,000-100,000+ | 3-7 years |


What is Primavera P6?

Oracle Primavera P6 is the industry-standard software for planning and managing complex projects, especially in construction, engineering, oil & gas, and infrastructure sectors.

Think of it as the "SAP of project scheduling" — what SAP is to finance, P6 is to planning.

Why P6 Dominates EPC

1. Enterprise-grade — handles 100,000+ activities across multiple projects

2. CPM engine — built-in Critical Path Method calculations

3. Resource management — supply-demand analysis and levelling

4. Multi-user — concurrent access via Oracle database backend

5. Industry standard — contractually required by most EPC clients

Key P6 Concepts

Enterprise Project Structure (EPS) — hierarchical organisation of projects
Work Breakdown Structure (WBS) — deliverable-based decomposition of scope
Activities — the atomic unit of work with duration, dates, and assignments
Relationships — logical dependencies between activities (FS, SS, FF, SF)
Calendars — working/non-working time definitions
Resources — labour, equipment, and material assignments

What is an XER File?

An XER (eXport/Exchange Report) file is Primavera P6's native data export format. It's a simple text file containing all your schedule data in a structured format.

XER File Structure

ERMHDR 12.0 ...

%T PROJECT

%F proj_id proj_short_name ...

%R 1234 "FPSO Module Installation" ...

%T TASK

%F task_id task_code task_name ...

%R 5001 "A1010" "Mobilise Construction Team" ...

%T TASKPRED

%F task_pred_id task_id pred_task_id pred_type ...

%R 8001 5001 5002 "PR_FS" ...

Critical XER Tables

| XER Table | Konnect xD Entity | What It Contains |

|-----------|-------------------|-----------------|

| **PROJECT** | Project | Project header (dates, IDs, settings) |

| **TASK** | Activity | Individual tasks with status, duration, dates |

| **RSRC** | Resource | Labour, equipment, material definitions |

| **TASKRSRC** | Assignment | Links between activities and resources |

| **TASKPRED** | Relationship | PDM logic links (FS, SS, FF, SF) |

| **CALENDAR** | Calendar | Working/non-working time patterns |


PMP Standards & Terminology

The Project Management Professional (PMP) framework from PMI provides standardised terminology used globally.

Key Terms Glossary

| Term | Definition |

|------|-----------|

| **CPM** | Critical Path Method — calculates the longest path through the network |

| **WBS** | Work Breakdown Structure — hierarchical decomposition of project scope |

| **EV** | Earned Value — budgeted cost of work actually performed |

| **PV** | Planned Value — budgeted cost of work scheduled |

| **SPI** | Schedule Performance Index — EV ÷ PV (1.0 = on schedule) |

| **CPI** | Cost Performance Index — EV ÷ AC (1.0 = on budget) |

| **Float** | Time an activity can slip without delaying the project |

| **Baseline** | The approved schedule snapshot used for comparison |

| **Data Date** | The "as-of" date dividing actuals from forecasts |


EPC Project Stories

Story 1: The Missing Link

A contractor submitted a 15,000-activity schedule for an offshore platform. Everything looked reasonable — activities had durations, resources were assigned, milestones were set.

But when Konnect xD's DCMA 14-Point Analysis ran:

Logic Density: FAIL — only 0.8 relationships per activity (healthy is 1.5-2.0x)
Missing Predecessors: 3,200 activities with no incoming logic
Missing Successors: 2,800 activities with no outgoing logic

The schedule was essentially a list of tasks with dates, not a network. Any delay would have been undetectable because the CPM engine had no dependency chain to calculate through.

Result: The contractor was required to add 8,000+ relationships before the schedule was accepted.

Story 2: The Phantom Critical Path

A mega-project team was confused — their schedule showed a 4.5-year duration, but the real-world progress suggested 6+ years. The CPM critical path was being driven by a procurement activity with an artificially short duration.

Konnect xD's AI Risk Scoring flagged this:

• The procurement activity's 3-month duration was in the bottom 5th percentile of similar activities across 200+ historical projects
• The model predicted an 85% probability of 6+ month delay on this specific activity type

Result: The team adjusted the procurement duration and added contingency, realigning the schedule with realistic expectations.


How Konnect xD Addresses These Challenges

Automated Quality Assurance

DCMA 14-Point Compliance — instant schedule health check against the gold standard
Quality Scoring — every schedule version gets a quality score (0-100)
Trend Tracking — see how schedule quality evolves over time

AI-Driven Intelligence

Predictive Finish Dates — ML models trained on 500+ historical schedules
Risk Scoring — activity-level risk assessment based on historical patterns
Optimisation Recommendations — actionable suggestions for schedule improvement

Connected Data

Knowledge Graph — schedule data connected to 3D models, cost data, and procurement
Version Management — full audit trail of every schedule snapshot
Cross-Project Analysis — benchmark performance across your project portfolio

Further Reading

PMI PMBOK Guide — Project Management Body of Knowledge
AACE Recommended Practices — Cost Engineering standards
Oracle P6 Documentation — Technical reference
DCMA 14-Point Assessment — Schedule health metric standard