Home / Insights

Notes from practice

Short, practical notes on project controls, BIM and construction data: what tends to go wrong, and how to prevent it.

14 notes
Featured | Project management

Every new party adds more interfaces than you think

Interfaces between parties grow as n(n−1)/2. Two parties share one interface, five share ten, ten share 45 and twenty share 190.

2 parties15 parties1010 parties4515 parties10520 parties190
Interfaces between parties, n(n−1)/2.

Headcount grows in a straight line; coordination effort does not. A project with twenty subcontractors needs an interface register, a responsibility matrix and a common data environment with clear ownership, not only more meetings.

We start every engagement by listing the parties and the information that passes between them. It is the cheapest risk register a project will ever write.

BIM QA/QC

Model health is a deliverable

Check the model before every issue, not after a rejection.

Read the note

A model that opens slowly, carries thousands of warnings or misses its parameters fails at the worst moment: the night before a submission.

Treat model health like any other deliverable. Agree the checks in the BIM execution plan, run them before every issue, and send the report with the model.

Warnings, file size, unused families, naming, worksets, shared coordinates and parameter completeness cover most of what goes wrong.

BIM coordination

Clash counts are not progress

A falling clash count can hide a growing problem.

Read the note

A report of 4,000 clashes says more about the test settings than about the design. A count that falls to 400 may only mean the tolerance changed.

Group clashes by location and cause, set tolerances by system, and track the issues that need a decision. Ten resolved design issues are worth more than a thousand closed duplicates.

Data

A dashboard is only as honest as its coding

Three coding systems produce three different projects.

Read the note

When the schedule, the cost report and the model use different codes, the dashboard reports three different projects.

Agree one breakdown structure before the first baseline. Every later report then becomes a query rather than a reconciliation.

Dashboards

A KPI without an owner is decoration

Every number on a dashboard needs a person who acts on it.

Read the note

Dashboards fill up with measures nobody acts on. Each one costs attention and hides the few that matter.

For every KPI, write down who owns it, what threshold triggers action and what that action is. If nobody can answer, take it off the page.

Planning

Update the programme, or stop quoting it

A baseline nobody updates is a record of intentions.

Read the note

A baseline that has not been updated since award is a record of intentions, not a plan.

A useful update records actual dates, remaining durations and logic changes, with a short narrative of what moved and why. Without the narrative, the next update cannot be checked.

Project controls

Earned value needs honest progress

CPI and SPI are only as good as the progress measurement behind them.

Read the note

Earned value is simple arithmetic on top of a hard judgement: how much work is really done.

Agree measurement rules per activity type before work starts, such as milestones for formwork cycles and quantities for concrete. Then the indices mean something.

Claims

Records win claims

Time-bar arguments are settled by what was written down at the time.

Read the note

Many standard contracts, including FIDIC forms, set strict notice periods for claims. Missing one can cost the entitlement.

Daily reports, dated instructions, located photographs and a notice log checked every week decide most of these arguments.

BIM coordination

Federation is not aggregation

Each discipline should keep ownership of its own model.

Read the note

Linking every model into one file is aggregation. Federation means each discipline keeps ownership of its model, with agreed origins, levels and exchange dates.

Without that discipline, a clash report measures file problems, not design problems.

MEP

MEP coordination does not scale linearly

Ceiling voids, risers and plant rooms concentrate the conflicts.

Read the note

Doubling the floor area does not double the MEP coordination effort. Ceiling voids, risers and plant rooms concentrate the conflicts.

Budget coordination hours by zone complexity, not by area.

BIM standards

Level of information need replaces guesswork about LOD

Write down what each purpose needs, per deliverable.

Read the note

LOD describes how developed an element looks. Level of information need, from ISO 19650, says what geometry, data and documents each purpose requires.

Writing it down per deliverable ends most arguments about whether a model is finished.

Construction management

Your RFI count is a diagnostic

A rising count on one package usually points to a design gap.

Read the note

A rising RFI count on one package usually points to a design gap, not a difficult contractor.

Track RFIs by package, age and cause, and the pattern tells you where to send the designer.

Information management

Set up the CDE before the first drawing

After the hundredth drawing it is a filing exercise.

Read the note

A common data environment set up after the hundredth drawing is a filing exercise. Set up before the first, it is a control system.

Agree folders, naming, status codes and permissions at mobilisation, and enforce them in the platform.

Handover

Handover data is a construction deliverable

Collect asset data as equipment is installed.

Read the note

Asset data collected after completion is expensive and incomplete, because the people who knew the answers have left site.

Collect it as equipment is installed and check it monthly. COBie is the format; collecting on time is the method.

Get new notes on LinkedIn

We publish a new practitioner note every week. Follow the page to see them first.

Follow Ascendix on LinkedIn

Have one of these problems?

Send us a short description. We will tell you whether we can help and what it would take.