Recently in Sydney, Transport for NSW (TfNSW) hosted a Digital Engineering Framework industry brief, sharing their vision and the standards they’re setting for digital engineering in the transport industry.
Simon Vaux (Director) and Adam Griffiths (Program Lead) each spoke of the need for collaborative processes and a common data environment to meet the evolving needs of TfNSW and their customers.
A priority for TfNSW was to develop processes and standards that all consultants and contractors will need to follow when working with TfNSW infrastructure. The standards have been published on their website to inform potential consultants and contractors who may seek to work with TfNSW and if you’re interested in digital engineering, I highly recommend downloading them and having a look. The documents include:
- Digital Engineering Standard explaining the concepts of digital engineering and defines TfNSW’s requirements for selecting contractors to deliver on digital engineering projects
- Digital Engineering Execution Plan Template for how contractors can explain to clients how they will meet TfNSW’s requirements
TfNSW has a adopted classification schema and coding system (different to the usual COBie standard). This will be based on the UK UniClass system (PAS 1192 standards) combined with area and discipline coding. The aim is to create a common data environment that flows through from design to construction into asset management. This will enable the industry to gain more efficiencies in design, cost control and asset management.
“By ‘building our assets twice’ first virtually and then physically, digital engineering has the power to provide valuable insights, create efficiencies and deliver cost savings to every decision we make.” Transport for NSW
All data requirements will be decided at the beginning of a project and will be available (and updated as required) throughout the project and supplied with all digital engineering documentation at handover. There is a ‘step-change’ whereby the constructor (along with the designer) will have to satisfy digital engineering requirements for TfNSW so that digital engineering data is not lost at the end of a project.
There is a clear opportunity in the early phases of an asset’s lifecycle for asset owners to prepare for the asset management phase that often lasts decades longer than the design and construction phase. It’s great to see asset owners like TfNSW gaining better control and visibility by setting digital engineering standards early that will ease them through handover to asset management.
Another digital engineering leader in Australia to watch is Snowy Hydro. With an asset lifecycle that lasts centuries, they’ve recognised the value in introducing digital engineering standards while the asset is being designed and constructed. If you’d like to find out more about how RedEye is working with organisations to draft their own digital engineering standards, feel free to reach out to me on LinkedIn or via email.