Delivery – Q6: When & Where do information deliverables need to occur in relation to each other?
We have so far defined what needs to be delivered and by whom. Now we need to ensure that it is understood, when each of those information packages need to be delivered and where they need to be delivered to.
To do this, the Information management team map out the key milestones for each package, making sure they are clearly defined, and the interdependencies are complete. This timeline should also include when that information is collected, verified, authorised, shared and then published, making sure that its purpose is made clear, using the BS 1192/ ISO 19650 coding.
It is also important to state where this Information will be placed and who needs to be notified of its state of readiness.
When planning, in my experience, it’s always best to start with the desired date/time and work backwards. Using the synch matrix that has already been developed in general, work towards making it more detailed.
Most organisations involved in the handover of assets are good at specifying and carrying out commissioning on physical assets. This needs to be replicated on the digital asset and resources assigned to ensure it is done correctly. The digital asset, if it is incorrect and faulty will damage property, people and reputation just as much as a physical one.
The physical interface between various packages of works should have been identified by now and this information should be used to start to understand the digital interfaces that will need to be coordinated across all delivery partners and existing asset owners.
This will allow the Information Manager to complete the required information deliverables timeline in detail and further update the Digital Construction Expectations document.
The Digital Construction Expectations document
In the 7 questions methodology we talk about a “Digital Construction Expectations” document, this is a live document owned by the client, that defines the current level of digital delivery expected of its employees and deliver partners. As each project is launched the document is reviewed and if necessary updated to show any new standards, methods or processes that all future projects ought to use.
This document is then combined with the Project Information Requirements and any project specific expectations to generate the Exchange Information Requirements document.
This is not a widely used document but is a good piece of advice from one of the UK’s major Infrastructure owners.
Exchange (Employers) Information Requirements
The EIR which until recently stood for Employers Information Requirements and now uses the word Exchange instead, is the client’s chance to define their requirements for procuring the digital asset. They will need to be very careful what they ask for, too prescriptive and you are preventing innovation and progress, too loose and you will probably receive something that you didn’t even expect!
Don’t just demand BIM or a Digital Twin and also don’t just say it must comply with standard ISO 19650, BS 1192 or Level 2! You will need to explain:
How you want the information delivered?
When you want it delivered and what it dependent or depends on it?
Where it is to be created, worked on and delivered?
What the information is and what specific part of a standard or library, coordinate system, classification table and format is needed?
Who is responsible for authoring, authorising, approving and coordinating?
Why the above is required?
Note that the EIR will tell the delivery partner how they will deliver the information and how to guarantee consistency, value and quality, not how to generate the information itself, as this method is an important commercial advantage to both parties and would stifle innovation and competition. The delivery partner must feel free enough to do what they do best but understand they need to deliver the end result to the client’s specification.
Several of the more digitally advanced client organisations have a live document running all the time called the Digital Construction Expectations document (DCE). This presents an up to date set of paragraphs and statements that suit the entire business and will be combined with the Project Information Requirements to be presented to the delivery partners for their response.
The EIR should set out three areas for the delivery partners to respond to:
Taking everything into consideration whilst writing this document and aligning it with the rest of the contractual package is important and is assisted by using the 7 Questions for Capable Clients methodology.