Kelly Doyle, COO, ProjectReady
Tom Noctor, Senior Strategic Product Consultant, Procore
Paul Doherty, President & CEO, The Digit Group
The team effort involved in projects in the Architecture, Engineering, Construction and Owner space is something that cannot be overlooked. From the financial groups to project managers to the build and design teams to the workers on the ground, the vastness of individuals involved on a single project cannot be overstated. With not only different teams but different individuals using particular software for their particular needs, how do the various stakeholders, teams and individuals communicate through the lifecycle to ensure the smooth completion of a project?
In a recent Panel discussion sponsored by the UK & Europe Digital Construction Online, entitled “Connecting Design & Build Teams Across Multiple Software Solutions in a Project’s Digital Lifecycle” just that topic was taken up and discussed by Kelly Doyle of ProjectReady, Tom Noctor of Procore, and Paul Doherty of The Digit Group.
Design/Build Information Management Challenges
Focusing on the Design and Build Teams of an AEC/O project, the Design teams author in one set of tools but the Build teams compile and distribute in another. This creates a disconnected process for approvals and tracking with no end- to-end audit trail. Tom Noctor of Procore says that having worked in construction for 14 years, he has seen first hand what happens when the team on the ground gets the wrong information.
The Current Flow of Information
Our industry today is gaining much more control over projects than ever before. There are large platforms that are Design focused, others are Build focused. Design teams and Build teams both require different types of software applications, due to the nature of what they do. The information on these applications however become siloed and disconnected. Disconnected information can lead to risk. Paul Dohery of The Digit Group says he gets requests for 3rd party tools all the time, but how can all the tools be integrated?
The State of the Possible
The Integrated Data Environment (IDE) allows cloud based integration of apps, systems, data and workflows for both Design and Build Teams. As a single user experience, sharing and syncing content creates “one version of the truth.” The IDE allows for security, tracking, auditing, governance, communication and collaboration and the mitigation of risk. Dohery says that Procore was revolutionizing as it brings other softwares into place and ProjectReady connects the dots to the standard of care and flexibility no matter what team is in place in the project.
From a global perspective, ISO 19650 is not just a standard but a “Standard of Care” that explains the need to have control of all project information regardless of the platform or team. When discussing ISO 19650, both Paul and Tom agree that a standard is open to interpretation. Kelly Doyle, of ProjetReady adds that information is the key and that all systems must be in place and connected. Beyond a Common Data Environment (CDE) there is a need for a “system of systems.” Tom adds that when we look at the assets at the utilization phase or the build phase or the contraction phase, how do we maintain the assets throughout the life cycle. It’s the need for structured data to truly understand what the project details are.
There is an amazing future for the AEC/O. Paul Doherty says that it’s not just about building the building anymore. We are in the pioneering stage of the digital realm. We have infinite space and we have the tools. With the use of IDE, Digital Twins, and the interconnection of data, and data that is trustworthy and accurate, decision making s easier and going forward more viable. Kelly Doyle sums up that we now have richer knowledge of where we need to go and the state of the possible.