Project controls glossary

The approved scope, schedule and budget against which progress and performance are measured. A baseline only changes through formal change control; if it is re-set informally, variances lose their meaning and the program loses the ability to show what a change cost.

See: Planning and Scheduling · Scope, Strategy & Change

The process that captures a proposed change, assesses its impact on schedule, cost, risk, constructability, approvals and resourcing, approves or rejects it, and tracks its implementation and benefits. On infrastructure contracts the same process handles variations claimed under the contract.

See: Scope, Strategy & Change · Cost Management

Time or money held to cover risks that are identified but uncertain in outcome. Well-run programs size contingency from a quantitative risk analysis (for example the difference between the P50 and P80 or P90 outcome) and draw it down against specific risks, so the reserve is defensible rather than a flat percentage.

See: Risk & Contingency Management · Safran Risk

The hierarchy used to collect and report cost: budgets, commitments, actuals and forecasts roll up through it. Aligning the CBS with the work breakdown structure and the schedule's coding lets cost and time be read together, which is the basis of earned value and integrated project controls.

See: Cost Management · Oracle Unifier

Establishing the budget, tracking commitments and actuals against it, forecasting the estimate at completion and controlling change so the program stays within its funding. On capital projects it also covers contract administration, payment claims and cash-flow forecasting.

See: Cost Management · Oracle Unifier

The longest chain of logically linked activities through the schedule, which sets the earliest finish date. Activities on it have zero (or the least) total float, so any delay to them delays completion unless it is recovered. Near-critical paths, with only a few days of float, matter almost as much.

See: Planning and Scheduling · Primavera P6 EPPM

The scheduling technique behind Primavera P6, Oracle Primavera Cloud and most enterprise planning tools: activities with durations are linked by logic (finish-to-start, start-to-start and so on), forward and backward passes calculate early and late dates, and the difference is float. A schedule is only as good as its logic and its calendars.

See: Planning and Scheduling · Primavera P6 EPPM · Oracle Primavera Cloud

Establishing what delayed a project, by how much and who is responsible, from the schedule records. Common methods include as-planned versus as-built, time impact analysis and windows analysis; the choice depends on the records available, the contract and whether the analysis is prospective or retrospective.

See: Forensic Delay Analysis

A method that measures progress in the same units as the budget. Planned value, earned value and actual cost are compared to give schedule and cost variances and performance indices (SPI, CPI), and to forecast the estimate at completion. It requires an integrated baseline where scope, schedule and cost share a common structure.

See: Integrated Project Controls · Cost Management

Managing many projects as a portfolio on one platform, with shared standards for structures, codes, calendars and resources. Primavera P6 EPPM is the best-known example; the enterprise setup (EPS, OBS, codes, calendars) is what allows portfolio-level reporting and comparison across projects.

See: Primavera P6 EPPM · P6 vs Oracle Primavera Cloud

The forecast total cost of the project when it finishes: actual cost to date plus the estimate to complete. It should be revised as risks materialise or retire and as productivity trends emerge, rather than defaulting to the budget until the money runs out.

See: Cost Management

The amount of time an activity can slip without delaying the project (total float) or the next activity (free float). Float ownership is a frequent contractual argument; a schedule health check looks at how float is distributed and whether constraints or long lags are hiding it.

See: Planning and Scheduling

The familiar bar-chart view of a schedule: activities as horizontal bars against a time axis, with logic links drawn between them. It shows when work happens but not where, which is why linear projects also use a time–location diagram.

See: Planning and Scheduling · TILOS vs Primavera P6

A single schedule that integrates the scope, logic and resources of every party and discipline on a program, from design and approvals through construction and commissioning. It is built to standards (WBS, code sets, calendars, quality gates) so that it can be baselined, updated, risk-analysed and reported from one source.

See: Planning and Scheduling · Pi Academy

Running planning, cost, risk, change and reporting as one connected system rather than as separate disciplines with separate data. Integration means the schedule, cost plan and risk model share structures and update together, so a forecast in one is reflected in the others and leadership sees one version of the truth.

See: Integrated Project Controls · Pi System

A collaborative production-planning method from lean construction in which the people who will do the work (the last planners) commit to weekly work plans drawn from a lookahead, and percent plan complete is tracked to improve reliability. It complements, rather than replaces, the CPM master schedule.

See: Pi Academy · Planning and Scheduling

A formal decision point between lifecycle phases (strategic assessment, business case, design, delivery, close-out) at which the program must demonstrate defined maturity before funding or approval is released. Governance frameworks tie scope maturity, estimate class and schedule confidence to each gate.

See: PMC Governance · Scope, Strategy & Change

A short-horizon plan, typically three to six weeks, taken from the master schedule and made ready for execution by clearing constraints such as design, access, materials and approvals. It is the bridge between the CPM schedule and what crews actually do each week.

See: Planning and Scheduling

A plot of cumulative earthworks volume (cut positive, fill negative) along the alignment of a road, rail or pipeline. Its shape shows where material is in surplus or deficit, how far it must be hauled and where borrow pits or spoil sites are needed, which drives earthworks cost, plant selection and staging.

See: Mass Haul Viz · TILOS

A technique that runs a schedule or cost model thousands of times, each time sampling durations, costs and risk events from their probability distributions, to produce a distribution of possible outcomes rather than one deterministic date or cost. It underpins quantitative schedule and cost risk analysis.

See: Safran Risk · Risk & Contingency Management · Safran Risk vs OPC risk analysis

Points on the outcome distribution from a Monte Carlo analysis. P50 is the value with a 50% chance of not being exceeded, a realistic central estimate; P80 and P90 are the values with an 80% or 90% chance, used to set contingency or a committed date. Funding bodies in Australia and New Zealand commonly ask for P50 and P90 figures.

See: Risk & Contingency Management · Safran Risk

Turning schedule, cost, risk and progress data into insight that leadership can act on: trends, early-warning indicators and forecasts presented in a form that supports a decision, rather than status reports that describe the past. Pioticon's PiViz product is built for this.

See: Performance Intelligence & Communication · Pi System

Pioticon's enablement model that embeds the Pi System in a live project environment as an operating control platform. Governance, project controls, performance intelligence and reporting are delivered through one integrated environment, giving shared accountability and real-time visibility across the lifecycle.

See: Pi System · PMC Services

Pioticon's enablement model for workforce capability: aligning people, roles and behaviours with the delivery systems through continuous feedback, applied coaching and capability reinforcement. It is delivered through Pi Academy's coaching and development programs.

See: Pi System · Pi Academy

Pioticon's digital enablement model, in which project platforms such as Primavera P6, Oracle Primavera Cloud, Unifier, Safran Risk and TILOS are configured to deliver understanding rather than just connectivity, so decisions rest on verified data instead of assumption.

See: Pi System · Digital Solutions

Pioticon's proprietary performance intelligence system. It integrates governance, planning, cost, risk and performance reporting into a single control environment built on one source of truth, so control is foresight-driven rather than reactive. It is deployed through three enablement models: Pi CaaS, Pi DiS and Pi Coach.

See: Pi System

Pioticon's integrated model that combines project management with integrated project controls (governance, planning, cost, risk, scope and change, performance reporting and forensic analysis) so a program runs on one set of connected data. Not to be confused with the generic contract role of Project Management Consultant.

See: PMC Services · Pi System

The function that sets and operates the standards, systems and reporting rhythm a portfolio, program or project runs on: governance forums, controls processes, tools and assurance. Pioticon establishes and runs PMOs for infrastructure owners and delivery authorities.

See: PMC Governance · PMC Services

The three levels at which delivery is governed. A project delivers a defined output; a program coordinates related projects to realise a benefit; a portfolio is the whole set of programs and projects an organisation funds. Controls must be designed for the level at which decisions are actually made.

See: PMC Governance

Establishing how much work has actually been done, using rules agreed in advance (quantities installed, milestones achieved, weighted steps) rather than opinion. Reliable progress is the input to earned value, forecasting and any credible delay analysis.

See: Planning and Scheduling · Integrated Project Controls

Modelling uncertainty and risk events numerically to forecast a range of completion dates (QSRA) or costs (QCRA), typically by Monte Carlo simulation on the schedule or cost model. Outputs include P-values, risk-driver rankings and the contingency needed to reach a target confidence.

See: Risk & Contingency Management · Safran Risk · Safran Risk vs OPC risk analysis

Assigning labour, plant, materials or cost to schedule activities so the plan shows demand over time. A resource-loaded schedule can be levelled, cash-flowed and used for earned value; an unloaded one can only show dates.

See: Planning and Scheduling · Primavera P6 EPPM

The controlled list of identified risks with their causes, consequences, probability, impact, owner and treatment. It feeds the quantitative model (risk events mapped to activities and cost items) and is the record behind contingency drawdown.

See: Risk & Contingency Management

A structured review of a CPM schedule's mechanics: missing logic, leads and lags, constraints, high float, negative float, long durations, invalid dates, resource loading and critical path integrity. The DCMA 14-point assessment is the most widely used checklist; the point is to know whether the schedule can be trusted before it is used to make decisions.

See: Planning and Scheduling · Forensic Delay Analysis

How completely scope, requirements, assumptions and interfaces are defined at a given lifecycle stage. Immature scope at commitment is the most common root cause of later variations and disputes, which is why governance frameworks tie scope maturity to each stage gate.

See: Scope, Strategy & Change · PMC Governance

A schedule view for linear projects (roads, rail, pipelines, tunnels) with location or chainage on one axis and time on the other. Each activity is a line whose slope is its production rate, so crews working the same corridor and the clashes between them are visible in a way a Gantt chart cannot show.

See: TILOS · TILOS vs Primavera P6

The hierarchical decomposition of the project's scope into deliverables and work packages. It is the common language that planning, cost, risk, change and reporting share; when the schedule, cost plan and contracts use different structures, integration fails at the first report.

See: Scope, Strategy & Change · Planning and Scheduling