Monthly Register — October 2024

Here is the question to take out of a week like the one the industry has just had: if your subscription lapsed tomorrow, what could you actually walk out with?

Autodesk University ran from 15 to 17 October at the San Diego Convention Center, with a digital pass in parallel. It is the host's annual gathering for the design and make industries, construction included. The trade press that sat in the hall has the session-by-session account, and the host has the recordings.

What moved

What can be said without theatre is the shape of the week as it was publicly framed. The conversation on the floor, and in the coverage that followed, was not mainly about a new drawing tool. It was about where project data is supposed to live once authoring is finished: in a hosted repository, reached through the host's interfaces and partner connections, rather than by handing native files across a table. Industry clouds, application programming interfaces, and "the model as data" are the vocabulary. File exchange is the thing being quietly retired from the slide.

That is a commercial strategy, and there is nothing scandalous about a software company having one. It is also an information-management event, whether or not the conference billed it as one.

The distinction that gets lost in the applause is between legal ownership of an uploaded model and operational ownership of the project record. Most platform terms already say the customer keeps intellectual property in the files they put in, and that sentence is worth exactly what it says and no more. It does not answer any of the questions a document controller has to live with on a live job.

Can the current issued set be reconstructed if the subscription lapses, the joint venture ends, or the employer names a different common data environment at the next stage? Does an export include the metadata that made the file usable — revision, suitability, transmittal history — or only a bag of natives and PDFs? If the host's preferred path is an interface into its own cloud, what happens to a party that is not licensed for that cloud, which on most jobs is at least one specialist subcontractor and frequently the client's own facilities team? Who holds the audit trail showing who approved what, and on which date, once the project is in dispute and the pleasant collaboration language has stopped?

None of that is unique to one vendor. It applies to any hosted common data environment, any "industry cloud", and any hyperscaler folder dressed up as a project system. Autodesk University is the lead this month because it is the loudest public statement of the pattern, not because the pattern has a single owner.

It matters most on the jobs that already run forty systems and still cannot name the issued set. Moving the same files into a more elegant cloud does not, by itself, produce a single source of truth. It can make the opposite problem harder to see, which is the part worth being nervous about: the record looks unified because one login shows all of it, while the contract parties still cannot take a complete copy home. Tidiness reads as control right up to the point somebody needs a set and a licence has expired.

A rough rule for reading roadmap slides. If a slide constrains export, that is news. If it only promises connection, it is marketing.

What changed in the standards

On the last working day of the month, 31 October 2024, sections 114 to 116 of the Leasehold and Freehold Reform Act 2024 came into force in England, amending the Building Safety Act 2022. They extend remediation orders and remediation contribution orders so that they can cover "relevant steps" — interim measures such as a waking watch or a simultaneous evacuation alarm — as well as the cost of expert reports and certain related expenses, including alternative accommodation when residents are moved out on building-safety grounds, rather than only the permanent fix of a relevant defect.

That is a leaseholder-protection commencement. It is not a new part of ISO 19650, and it is not a new information-management mandate. The golden thread did not arrive this month. A specific set of First-tier Tribunal powers did, and the two get conflated within about a week of any building-safety commencement.

The information consequence is narrower than the headlines and still real. A wider set of safety actions can now be ordered, and those actions generate records: patrol logs, alarm strategies, survey reports, cost evidence. If those records live only in a managing agent's inbox, the building has the same problem a site has when the only complete drawing set is in one person's downloads folder. If they are treated as part of the building's safety information, they need somewhere to live that outlasts the consultant who produced them and the agent who commissioned them.

For the avoidance of doubt: no new ISO 19650 part was published in October 2024, the UK BIM Framework did not issue a replacement text, and the Gulf permit-stage BIM requirements that came into force earlier in the year were not rewritten this month.

One thing to watch

Two weeks after San Diego, whether anyone remembers the keynote will tell you nothing. Whether document controllers are still arguing about export, exit and who can reconstruct the issued set without the original host's login will tell you a good deal. If they are, the argument has legs and belongs alongside the systems-sprawl diagnosis rather than in a conference recap. Theatre dies inside a fortnight. Ownership arguments do not.

Watch the commencement the same way. If information managers leave "relevant steps" to the residential lawyers, the record of those steps gets assembled later, under pressure, out of mailboxes — and somebody will bill for that reconstruction.

So, at your next procurement: put export and exit in the acceptance tests, not in the appendix. Ask the vendor to hand you a full copy of a project, metadata included, while you watch and time it. Ask what that costs, because it may well cost something. And ask who signs to say the copy is complete.