William Baker-Jones works in digital construction at Kier. He was Deputy Head of BIM and Digital Engineering at Babcock International Group in 2024. His work covered information management, BIM and data for the major infrastructure programme at Devonport. He studied architecture at the University of Plymouth before working in architectural practice and construction.
In his Morta interview, William explains how information requirements and delivery dates connect to procurement, design and site activities. He also discusses information security and the importance of explaining risks and benefits in language that project managers and senior leaders recognise.
His separate data-assurance presentation describes using Python, IfcOpenShell and Morta's APIs to check model data against information requirements. He explains how the checks account for different projects and the information needed at each stage, using demonstration data to illustrate the approach. Across the two contributions, he connects the purpose of information with practical ways to specify and validate it.
We've got to think of information as an asset and something that we need to value.
Episode #2 Moving from reactive to proactive information management
People understand information. It's [...] getting them to understand the value of that information and what it can do for them.
Episode #2 Moving from reactive to proactive information management
Don't do too much at one time.
Episode #2 Moving from reactive to proactive information management
Babcock InternationalWilliam Baker-Jones
William Baker-Jones explains proactive information management by linking requirements and delivery dates to the activities they enable. His Babcock examples show why information value, access and security form part of the same business conversation.
Babcock InternationalWilliam Baker-Jones
Babcock connected requirements held in Morta to Python and IfcOpenShell for repeated IFC checks. William Baker-Jones's comparison reduced processing for 404 model files from 128 hours to 13.4 hours, with some reporting steps still in development.
Get started