Micropiling works underway at District Docklands
Micropiling works are now underway at District Docklands, strengthening an existing operational building through carefully planned foundation works.
Useful technology solves a real problem.
That was our focus at Urbanity-26, held from 22 to 24 July at The Star Gold Coast. As a Gold Partner, Kapitol joined developers, builders, consultants and other property professionals to discuss where technology and modern construction methods are making a practical difference. We also shared what we’ve learned from applying those ideas to live work.
Across two sessions, Andrew Morrison and Tim Trimble approached that question from different angles. Andrew joined a panel on AI and robotics in real estate and construction. Tim presented the modular delivery of NEXTDC D1 in Darwin as a project case study. Together, the sessions covered both the bigger industry conversation and the decisions needed to turn an idea into something that works on site.
Construction has been grappling with productivity challenges for decades. AI, robotics and automation won’t solve those challenges on their own, but they can form part of a practical response.
During the panel, Andrew’s focus was on where emerging technologies are creating value now, how they can improve productivity and project delivery, and what it takes to move beyond isolated trials. The discussion looked past technology as a headline and towards implementation: the workflow being improved, the waste being removed and the person being given clearer information.
That distinction matters. A new system doesn’t need to overturn an entire business to be worthwhile. It might help a team complete a repetitive task faster. It might make information easier to check. It might identify an issue before that issue reaches site. Small improvements, repeated across a project, can change how effectively people work.
This is how we think about innovation in construction industry practice at Kapitol. Technology needs to earn its place. The starting point is the problem, not the product.
The same principle guides our in-house Digital Engineering capability. Autodesk Construction Cloud, BIM coordination, PointCloud scanning, OpenSpace AI and PowerBI serve different purposes, but the test is consistent: do they create clearer information, support earlier decisions or reduce uncertainty for the team doing the work?
The benefits of digital engineering become tangible when digital information connects directly with design, fabrication and installation. That link was clear in the D1 case study presented the following day.
On Friday, Tim Trimble, Kapitol’s Critical Infrastructure Lead, presented the modular construction of NEXTDC D1 in Darwin. The project used nine front-of-house modules and eight data hall modules, contributing to a three-month programme saving. The front-of-house modules were installed over two days.
The case study showed that modular is a delivery method, rather than a standard product or a shipping container placed on site. At D1, the modular scope included front-of-house offices, a kitchen, meeting rooms and end-of-trip facilities, alongside data hall components. The project combined these elements with site-built substructure, civil works, landscaping and roofing.
The value of BIM in construction was most visible at the interfaces.
PointCloud surveys captured the as-built geometry of the prefabricated module bases. That information was incorporated into the BIM model and structural steel shop drawings, allowing the steelwork to be fabricated against the actual module geometry. The modules were manufactured in different states, with front-of-house modules made in Melbourne and data hall modules made in Sydney, before being transported to Darwin. By bringing the survey data into one coordinated model, the team checked alignment before shipping. The installation was completed over two days without connection issues.
This is where the benefits of digital engineering move beyond model presentation. The model becomes a practical coordination tool linking work produced in Melbourne, Sydney and Darwin. It gives the project team a chance to find a mismatch while there’s still time to resolve it, rather than discovering it while a module is being lifted into position.
D1 also showed why modular planning can’t stop at design. Regional delivery brought constraints around plant, equipment, materials and trade availability. Limited local fabrication capacity and long material lead times increased the importance of early procurement. Seasonal workforce changes meant resources needed to be secured early, with fly-in fly-out labour helping maintain project momentum during the wet season.
Logistics also changed during delivery. When the Stuart Highway temporarily closed to over-mass vehicles, the team developed an alternative plan to transport modules to Darwin by barge. It was a clear reminder that modular work still depends on construction fundamentals: planning the route, checking the interfaces and preparing for the conditions around the job.
These lessons are particularly relevant to data centre construction, where technical coordination, programme and commissioning need to remain aligned. The method can remove work from site and reduce pressure on constrained regional resources, but only when design, manufacture, transport and installation are planned as one delivery process.
The biggest takeaway from Urbanity-26 was simple.
The future of construction won’t be defined by a single technology.
It will be shaped by organisations that can combine people, processes and technology to solve practical problems.
Whether the discussion focused on AI in construction, digital engineering, robotics, modular construction or productivity improvement, the underlying objective remained consistent: delivering better outcomes.
Better coordination.
Better certainty.
Better quality.
Better use of the resources available to us.
Urbanity-26 demonstrated that many of these tools are no longer future concepts. They’re already being used across projects today. The challenge now is understanding where they create value, how they support project teams and how they can be implemented in ways that improve delivery rather than add complexity.
