Insights

What is PDRI®?

PDRI® (Project Definition Rating Index) is a structured tool used during front end planning to assess the completeness of project scope definition. It helps teams identify gaps and project risk factors before detailed design and construction.

The index was developed by the Construction Industry Institute in the USA and The University of Texas at Austin. Individual PDRI® publications relate to various sectors – mining, civil engineering, industrial construction and infrastructure.

The traditional PDRI® for industrial projects uses a 0–1000 point scale. The lower the score, the better defined the project.

How to Interpret a PDRI® Score

As practical indicative ranges:

Important: these are practical interpretive ranges, not universal CII thresholds for every PDRI® application. The score should always be interpreted in relation to project type, project phase and the specific PDRI® version being used.

For CII small industrial projects, the typical early-review range is 400–800, while the final review typically falls within 150–400, with a target of 300 or below.

For large and complex industrial projects, 200 points is a particularly important benchmark. CII research found that projects scoring below 200 generally performed better in terms of cost, schedule and change performance.

How to Assess Project Readiness

Project readiness should cover more than the completeness of engineering documentation. It should also consider:

• project scope and boundaries,
• technical and process requirements,
• project input data,
• site conditions,
• technical concept,
• legal and permitting requirements,
• procurement and execution strategy,
• schedule and budget,
• project organization,
• risks and project assumptions.

PDRI® converts this assessment into a structured and measurable process, identifying gaps that need to be addressed before moving to the next project phase.

PDRI® and Project Readiness for Execution

PDRI® is a key tool for assessing Project Readiness, but the score should not be the sole basis for an execution decision. As a practical interpretation:

• PDRI® ≤200 – the project is well defined and may be considered ready for progression, subject to closing critical actions.
• PDRI® 200–300 – the project is generally well prepared, but remaining gaps and their risk impact should be reviewed.
• PDRI® 300–400 – additional work is required to strengthen project definition and close key gaps.
• PDRI® >400 – caution is recommended before committing to major execution activities; critical definition gaps should be addressed first.

PDRI® does not simply answer “Can we start the project?” It answers “How well is the project defined, and where are its weaknesses?”

Causes of EPC Project Delays

EPC project delays rarely have a single cause. They are usually the result of problems accumulating from the early stages of the project.

Typical causes include:

• incomplete project definition,
• scope and client requirement changes,
• engineering and document approval delays,
• design errors and inconsistencies,
• long-lead procurement problems,
• supplier and subcontractor delays,
• poor multidisciplinary coordination,
• slow decision-making,
• ineffective information flow,
• inadequate planning and control.

Delays often develop as a chain reaction: Decision → Engineering → Procurement → Construction. Effective delay management therefore requires identifying the root cause, rather than simply monitoring the resulting delay.

Project Recovery Plans

A Project Recovery Plan is a structured set of actions designed to restore control over scope, schedule, cost and resources.

A good recovery plan should answer:

• What went wrong? – identify causes and impacts.
• Where are we now? – assess the current project status.
• What needs to change? – define corrective actions, priorities and resources.
• How will we recover the schedule? – establish a realistic recovery programme and focus on the critical path.

A recovery plan should not simply be a revised schedule. It should define how the project will be managed differently.

Risk Management

Risk management is more than maintaining a Risk Register. Its purpose is to reduce both the probability and impact of events that could negatively affect project objectives.

The process includes:

• risk identification,
• probability and impact assessment,
• risk ownership,
• preventive and mitigation actions,
• trend monitoring,
• contingency planning,
• regular risk profile updates.

Mature risk management means moving from “What are our risks?” to “What are we doing to prevent the risk from becoming a problem?”

Project Control Indicators

Project Controls provide the information needed to determine whether the project is progressing towards its objectives.

Key areas include:

• Schedule – programme and progress,
• Cost – budget and cost forecast,
• Engineering – documentation and approvals,
• Procurement – orders and deliveries,
• Construction – physical progress,
• Changes – scope changes,
• Risks – risk levels and trends,
• Cash Flow – actual and forecast cash inflows and outflows.

Good KPIs should not only show what has happened, but also indicate what is likely to happen next.

How to Evaluate an Equipment Supplier

Supplier evaluation should go beyond price. Key criteria include:

• experience and references,
• technical competence,
• manufacturing capacity,
• quality management,
• inspection and testing capabilities,
• personnel qualifications,
• financial stability,
• availability of materials and components,
• international delivery experience,
• ability to meet the required schedule.

The best supplier is not necessarily the cheapest supplier. It is the supplier capable of reliably meeting technical, quality and schedule requirements.

Technical Bid Evaluation

Technical Bid Evaluation (TBE) is used to compare supplier offers against project requirements.

The assessment should cover:

• datasheet and specification compliance,
• materials,
• technical parameters,
• applicable standards,
• scope of supply,
• certificates and documentation,
• inspection and testing,
• technical warranties,
• deviations,
• installation and commissioning requirements.

A good TBE should identify not only technical compliance, but also the risks associated with selecting each supplier.

Supplier Evaluation

Supplier evaluation should be performed before selection, during execution and after delivery.

Before placing an order, the evaluation should cover the supplier’s experience, quality performance, technical capability, manufacturing capacity and financial stability.

During execution, key areas include:

• manufacturing progress,
• documentation,
• quality,
• inspections,
• schedule,
• material procurement,
• corrective actions,
• readiness for shipment.

After delivery, performance can be assessed against: Quality – Delivery – Cost – Technical Performance – Documentation.

Sourcing of Specialized Equipment

The sourcing process should include:

• defining requirements,
• identifying technologies and manufacturers,
• developing a long list,
• verifying capabilities,
• developing a short list,
• issuing RFQs,
• technical and commercial evaluation,
• supplier audit or inspection,
• negotiations,
• supplier recommendation.

For custom-made, long-lead or technically high-risk equipment, sourcing should start as early as possible.

The objective is not to find the cheapest manufacturer, but the supplier capable of delivering the right technology, quality and schedule at an acceptable level of risk.

FEED vs. Basic Design

FEED (Front-End Engineering Design) establishes the main technical solutions, project scope, process parameters, major equipment requirements and key cost and schedule assumptions.

Basic Design further develops these assumptions to support detailed engineering, procurement and construction.

Key elements include:

• project scope and boundaries,
• design basis,
• material and energy balances,
• process parameters,
• process concept,
• major equipment requirements,
• infrastructure,
• applicable codes and standards,
• cost and schedule assumptions.

A well-developed FEED reduces uncertainty and provides a sound basis for investment decisions.

Constructability / Feasibility Assessment

A Constructability / Feasibility Assessment determines whether the proposed design can actually be executed under the assumed project conditions.

It may cover:

• equipment transportation,
• site access,
• cranes and lifting equipment,
• installation of heavy equipment,
• existing infrastructure,
• site conditions,
• construction sequence,
• work within operating facilities,
• safety,
• availability of contractors and materials,
• site constraints,
• required execution schedule.

A technically correct design is not necessarily a design that can be constructed efficiently and economically.

Technical Assessments

A Technical Assessment is an independent review of a technical solution, equipment item or engineering package against project requirements.

It may include:

• verification of design assumptions,
• process solution assessment,
• documentation review,
• materials assessment,
• code and standard compliance,
• equipment and supplier evaluation,
• identification of errors and inconsistencies,
• interface review,
• technical risk assessment,
• optimization recommendations.

The purpose is not simply to identify errors, but to confirm that the proposed solution is technically appropriate, feasible, safe and fit for purpose.