Monthly Register — February 2025

Two weeks of Riyadh, and the part worth carrying home fits on a single line of a bid.

Big 5 Construct Saudi ran across 15 to 18 February and again 24 to 27 February, its 13th edition, at the Riyadh Front Exhibition & Conference Center at ROSHN Front. Week one sat with heavy construction, concrete, HVAC and technology. Week two sat with façades, urban design, hospital fit-out and facilities management. The second week closed yesterday, and by now the hall plan has stopped being interesting while the conversations have not.

Attendance figures, Vision 2030 pipelines and the organiser's claim that a two-week construction show is a first in the region belong to the trade press, which covers them perfectly well. The commercial fact the halls made harder to dodge is narrower: on a Saudi gigaproject, the information requirement is no longer a late appendix. It is a priced line, and buyers and the supply chain spent two weeks in the same building discovering what each side thought that price covered.

What moved

A slogan requirement cannot be priced. “Comply with ISO 19650”, “LOD 300 throughout”, “a common data environment shall be provided”, “COBie at handover” — those sentences travel beautifully in a BIM execution plan, and they tell a task team nothing about which container, in which state, with which fields, against which pass-fail test, will be accepted. So the supply chain prices what it can see: a login, a clash-report ritual, an export. The appointing party believes it has bought an information-management system. What it has bought is a cover sheet.

What is being priced, in the open, is easy to name without a transcript. A hosted repository. Named licences. A BIM execution plan that restates the employer's language back at him. A federation at a named milestone. A permit-stage model file, because last year's Gulf conversation made the portal slot ordinary. A handover model parked beside a crate of operations-and-maintenance PDFs. None of that is nothing, and none of it is the issued set either.

What typically is not priced is the trail that makes those objects usable after the person who uploaded them has left the programme.

Put the question to a live package and watch the room. Can the current construction information be named — these sheets, this model state, this specification revision, released to these companies, for this purpose, in this information state — and then reconstructed a year later without ringing somebody who has since moved firms? If the joint venture novates, if the next package names a different common data environment, if the subscription lapses, does the export carry revision, suitability and transmittal history, or only a bag of natives and PDFs? Gulf programmes that publish information requirements tend to be precise about deliverable formats and quiet about who owns that trail when three environments are federated. A show the size of Big 5 Saudi is the month's weather because that silence is now sitting across a table from a rate.

The question worth keeping is therefore a good deal narrower than “are we doing BIM on the giga?” It is whether the price includes the audit trail. If the answer comes back as a platform name, the row has not been priced. If it comes back as a reconstructable published state — container, revision, suitability, transmittal, named recipients — the row can fail, and a requirement that can fail is the only kind worth writing down.

None of this belongs to a single software house, and nobody should read it as a recommendation to change one. It applies to any common data environment, any model platform, and any portal sitting between a package and a delivery authority. The halls made the conversation public. They did not invent it, and in my experience they rarely settle it either.

What changed in the standards

No new ISO 19650 part was published in February. The part that landed at the end of January — ISO 19650-6:2025, on health and safety information, the ISO text dated 13 January and the BS EN ISO text dated 31 January — is now the working document on sale. It was not January's lead here and it is not February's. Trade coverage has a public launch at the BSI built environment summit on 26 March, so until then the accurate scale is a new part in circulation rather than a rewritten appointment. It is a communication standard for health and safety information across the life of the asset. It is not a Saudi gigaproject exchange information requirement, and it does not tell a document controller which container carries the issued set.

The UK BIM Framework did not issue a replacement text this month. The Information Management Initiative launched in November remains a sector invitation to write a mandate — not a statutory instrument, and not a new part of the series, whatever it gets called on a slide.

Saudi municipal permit texts were not rewritten in the halls either. Last month's anniversary already named the shape of that duty as information managers actually live it: a gate that often asks for a model, and a stamp that still sits on a drawing pack. A first year of live submissions is not a new clause. It is the weather in which this month's priced rows will be tested.

One thing to watch

Watch the priced row. If it cannot fail — no named container, no state, no field list, no rejection rule — it is a slogan with a currency symbol in front of it. If three environments are federated and nobody priced the trail between them, the first package handover will show you the gap, usually on a Thursday afternoon. If the permit model and the construction issued set are still two objects, the price did not buy one project.

Watch Part 6 the same way. On a slide, offered as proof that the series is now complete, it will change nothing on a live job. Written into named health-and-safety exchanges, with owners and a state attached, it will start showing up in how requirements get drafted — in Britain, and on any appointment that already cites the series.

Two weeks from now, when the stands are back in their crates, the honest test is whether document controllers on gigaproject packages are still arguing about what the rate bought: a login and a BIM execution plan, or a published state with a trail that survives novation. That argument is a great deal cheaper before award than after it. If you sit on the buying side, put one question to every bidder — which line of your price covers the transmittal history, and what happens to it the day the subscription ends. The answers separate quickly, and they cost you nothing but the asking.