Week 9 Lecture: ISO 9650 & BIM Execution Plan
Week 9 Lecture Notes
Introduction
Welcome to the week 9 lecture. Speaker is Mark Cohen, past president of Brisbee, a founding member of the Brisbane chapter.
Brisbee is the first city BIM in Australia, organizing quarterly industry events at QUT.
Today's topic: ISO 9650 and the BIM execution plan, aligned with assessment 2.
Speaker Introduction
Mark Cohen is here to discuss international standards and their relevance.
Briefly covering standards, ISO 19650, classification, and client information needs.
Mark has been involved in various BIM industry initiatives and started as an architectural technician in the UK.
IB has two core parts: digital advisory and digital delivery.
Digital delivery focuses on BIM creation, structuring, handover, exchange, and acceptance.
Digital advisory focuses on client requirements.
Client Maturity Levels
Clients, including asset-owning entities like Queensland Health and QUT, have different BIM maturity levels.
BIM implementation should be incremental, starting with basic requirements and gradually adding complexity.
Queensland Health's BIM requirements have evolved over the years, with updates in 2018 and 2022, and ongoing updates.
Initial Challenges
Upon returning from the UK to Australia, projects rarely went from early design through construction with model delivery to the client.
Good work was often done in conceptual and detailed design but would falter later.
Contractors sometimes didn't leverage BIM contracts, indicating a lack of standardization.
The Importance of Standards
Creating custom standards without basing them on existing frameworks can be problematic.
Using international standards like ISO 19650 or NATSPEC templates helps ensure familiarity and receptiveness.
Natspec had a BIM guide, but it wasn't prescriptive.
Some companies preferred UK standards like PAS 1192, while others followed US standards, leading to inconsistency.
This inconsistency hindered the development of BIM libraries and standardized BIM execution plans.
Standardization is crucial to avoid technical jargon and ensure that everyone uses the same language and terminology.
ISO 19650 Overview
ISO 19650 came along in 2018.
Title: Organisation and digitization of information about buildings and civil engineering works, including building information modelling, information management using building information modelling.
It's more about information management than BIM itself.
ISO 19650 Parts
There are six parts to ISO 19650:
Part 1: Overarching concepts of managing information flows.
Part 2: Delivery phase of the asset (design, construction, handover).
Part 3: Post-handover, operational phase.
Part 4: Information exchange.
Part 5: Security-minded approach, considering security implications for infrastructure projects.
Part 6: Health and safety, standardizing terminology and approach to BIM and health and safety interactions.
Historical Context
ISO 19650's development goes back to project reviews, such as the Heathrow tunnel collapse, where information management was lacking.
Evolved from Avanti, BS 1192 (drawing-focused), and PAS 1192 (BIM-focused).
International Standard Development
International standards require endorsement and creation by bodies like ISO or IEC.
Structured with technical committees and subcommittees dealing with specific topics.
Multiple countries are involved in the voting process.
In Australia, Standards Australia mirrors international committees.
Subcommittee members can vote on, approve, or edit standards.
The terminology must be suitable for an international market, and images should be easily translatable.
The entire process of drafts, reviews, and revisions takes years.
Focus on Information Management
ISO 19650 focuses more on information management than BIM.
Standards Overview
There are various standards related to BIM, some more important than others.
Level of Development (LOD) debate.
LOD is being superseded by Level of Information Need, broken down into five categories.
Clients should focus on outcomes and information about assets rather than geometric complexity.
Specifying LODs can lead to unnecessary detail, increased costs, and models that contractors don't use.
Example: LOD 400 for a block wall requires modeling each block and grout individually.
Finding the right balance is crucial.
Other relevant standards include the ISC data schema and classification systems.
ISO 19650 is not all-encompassing but gains traction due to government endorsement.
The standard has been decades in the making.
Relationship Between Standards
ISO 9001 is a quality standard.
Asset management and project management fall under quality standards.
Information management encompasses ISO 19650 concepts.
Delivery involves Project Information Model (PIM) and Asset Information Model (AIM).
PIM includes drawings, reports, and models relevant to project delivery.
AIM is the data needed to operate an asset, including operational needs and facilities management.
Digital Twins
Digital twins are spatial environments (3D model or GIS) with operational information connected to the physical asset.
Involves bi-directional connectivity between the physical and digital realms.
Organizations like the Digital Twin Consortium define digital twins.
Example: HVAC system data feeding into a digital twin for predictive maintenance.
Australian Guide to ISO 19650
An attempt to create an Australian guide to ISO 19650 faced copyright issues with ISO.
The UK BIM framework offers better guidance material due to buy-in from BSI.
They moved their material to Mortar, an information exchange platform, and principles for BIM implementation.
Recommendations from various bodies endorse ISO 19650, as well as classification systems like UniClass.
States align with ABAB recommendations for consistent processes across sectors.
Key Terminology
ISO 19650 introduces terminology like appointing party and lead appointed party.
The standard focuses on appointment workflows rather than project workflows.
Key Documents
Key documents include OIR, PIR, AIR, EIR, AIM, and PIM.
AIM is the asset information model, and PIM is the project information model.
Organizational Information Requirements (OIR)
OIR covers an organization's overall needs, such as QUT's requirements for delivering education.
Includes information on student numbers, buildings, courses, and safety.
Only a subset of OIR flows down to projects and BIM.
Asset Information Requirements (AIR)
AIR is more focused, specifying information needed to operate a particular asset.
Queensland Health has good guidance information based on ISO 19650, covering delivery and operational phases.
UK BIM framework offers examples and explanations, but the ANZ guide provides local context.
Standardized Terminology
Standardizing terminology is a key aspect of ISO 19650.
Parties: appointing party, lead appointed party, and appointed party.
Procurement model influences the appointment structure.
ISO 19650 is not looking at a project workflow, but at an appointment workflow.
Relationship Between Documents
OIR drives AIR and PIR, which in turn informs the EIR, PIM, and AIM.
OIR Details
Covers high-level organizational needs (e.g., QUT's education delivery, student numbers, building capacity).
AIR Details
Focus on information needed to operate a specific asset (e.g., a new building's requirements).
Based on guidance to ISO 19650, breaking down the delivery and operational phases.
UK BIM Framework
Provides guidance to 19,650, covering concepts, the delivery phase, and operational requirements, with pillars for each.
Supplements the ANZ guide with in-depth explanations and examples for 19,650.
PIR Details
Should be project-specific, but clients often create generic PIRs for similar projects.
Includes details from AIR and sets out specific project needs.
EIR Details
More granular: specifies file formats, exchange frequency, and specific required information.
Can be custom for each appointment but is often a standard copy-paste.
Informative information is sometimes included (explaining common data environments), which is technically incorrect.
Common 19,650 Concepts
Using appropriate technology.
Delivering in accordance with information requirements.
Exchanging information using a common data environment.
Making information accessible to the right parties for the life of the project and asset.
Accessibility of Information
Ensuring information is accessible beyond the project's lifespan is essential.
Using appropriate technology and delivering according to requirements are key concepts.
Using a common data environment is vital for information exchange and accessibility.
Accessibility example (projector warranty certificate):
Should be accessible beyond the design and construction phase, integrating with operational systems.
Common Data Environments (CDE)
CDEs are standardized processes for exchanging information as defined by ISO 19,650.
They involve information states (work in progress, shared, published, archived) with associated workflows.
Information States
Work in progress: Information is being developed.
Shared: Information is shared for coordination.
Published: Information is approved and released.
Archived: Information is replaced and stored.
CDE Workflow:
Iterative design process (design change, review, sharing, client approval).
Regular sharing (e.g., architects share models weekly with structural engineers).
Key milestones result in submissions to clients for acceptance (published stage).
Information Status
Crucial for determining the current status of a piece of information within a CDE.
UK national annex lists file naming and container naming conventions, and statuses (suitabilities).
Suitability/status codes indication what each item should be used for (e.g., only for coordination, not for construction).
Task/Master Information Delivery Plans (TIP/MIDP)
Assigns tasks to parties (architects, structural engineers).
Identifies what tasks need to be done, what information needs to be produced.
Similar to a drawing register done in advance during planning.
Workflows - Involve building up information, key project milestones (schematic design, design development, construction design), and key decision points.
Workflows
AIM to PIM Information Flow
Defines the link from PIM and AIM, with key decision points and information exchanges throughout the process.
ISO 9001 Alignment
Framework of different levels authorization and reviews.
*
Metadata Importance
Metadata, is important for workflows.
TIPs and MIDPs
Defined as the Task Information Delivery Plan and Master Information Delivery Plan.
Assigns tasks to parties (architects, structural engineers).
This assigns what tasks need to be done, what information needs to be produced.
Similar to a drawing register done in advance during planning.
Mobilization
Key Processes
Mobilization - involves testing all defined processes (model sharing, issue tracking) with real models.
*
Tender Response Process
Different Parties Involve
Agreements from designers, BIMM execution plans also involve from the parties.
This leads to a selection phase along with an assessment to identify which is best, and assess the clients execution plan.
Project Delivery and Sign-Offs
Importance of Acceptance Check
A lack of communication between involved parties during delivery and or sign-off might lead to errors.
Digital and Physical Alignment
Align the information, acceptance of handovers is only deemed once the digital aspect is satisfactory.
Implementation of Lessons Learned
Capture lessons learned from projects such as the dos and don'ts.
High-Level Learnings
Use of International Standards
Use execution plans for the standards or processes.
That state governments want them with standard alignment between one another.
However its understood that ISO 19,650 is commonly misunderstood in how it is actually implied.
ISO 19,650 Questions
Is it a Guideline or Requirement
They are provided to allow for common ways of working.
Modification or Revisions of ISO
It is meant to be modified and adapted to each users own personal needs.
*
Is it free
This ISO documentation is not free, it usually is a subscription provided document.
Classification Systems
Standardizing Terminology
Implementation to help standardize between different parties.
Helps with providing a definition what objects and such are called.
UniClass
A system stemming from the UK that helps standardize things from the UK.
Components Of UniClass
Downloadable tables
This includes the Elements, functions, systems, products.
*
Element and Functions
Is built straight into the tool, where is will or separates the specific function provided.
Complexities and Entities
Tables that Include
Complexities, entitles and locations that identify the use of location.
Quick Rundown
General Implementations
Implementations are for Transport and NSW with DMS SD 124.
That was very quick. Any questions on that one, and then I've got one last little section about tying it back to client need, which will take a couple of minutes, but we'll see how we go. We'll come back to classification questions at the end. It's a client need everything recording a bit. Yeah, sure. We've got, still got a few minutes, so we'll see how we go. Um, but client need, everything comes back to client need. Yeah, so all of the stuff we were talking about before, everything that you deliver or you design, what your design looks like, what it contains. Physical building, it's gotta be driven by the client, yeah, it's the same with the information as well, so some of it, yeah, maybe the contractor wants this bit of information or a subcontractor wants this bit of information. But in large part, it's gonna be driven by what the client wants. For whatever they're doing, so what is their use case for data? What are they actually gonna be doing with this building once it's handed over, what data would be relevant to them? What do they need, and that's really important that you have that in your mind at every step. Whether you Delivering a design, whether you're specifying information, whether you're writing a BEP. What do you actually need, because everything that you specify and include, That they don't actually want. Is more dollars. Yeah, they're gonna, someone's gonna pay for it. You might not see that, but if you put in, oh yeah, we want serial numbers for all of this type of asset, someone's physically got to go around on site during construction, read a serial number from a speaker, put it into, uh, probably some sort of app in the short term, go back to the office, transfer it from the app to the relevant bit of model geometry. And that's time. You do that by hundreds of items or thousands of items. Do they really need the serial number for that? Or do they just need to know, make and model so they can find a warranty certificate or something? Or how's it gonna work? Um, so really bringing it back to what the client needs is super important, because it's kind of like this, you probably have seen stuff like this before as well. There's just so much confusion out there. I've seen some really good examples held up this case study, oh yeah, this is going back 20 years, we did this awesome bem for this project. We, uh, handed it over to the client. There were 22 fields of information. And for all the stuff they're interested in and the client. Got up on stage and said, yeah, that was good, but out of the 22. We didn't want 14 of them, and we were missing 3 other really important ones. So we would have traded those 14 for these 3 other fields of information. So it's going back to what the client wants, super important. Um, so clear. Communication of information requirements and needs is vital, but then all that's also got to flow through floor, yeah, that's the the function that it's providing, it is a floor. So wall separation, whatever. So that's not used as regularly, but you'll be super familiar with it if you looked at it. It's all common things like walls, floors, ceilings, whatever. Systems and products are probably the more commonly used in BIM and um BIMM objects. Uh, systems don't get confused with MEP systems. It's talking about systems as a way of categorising things. So you have, um, road paving systems that make up of sub-base and, Subgrade and fill and whatever and then layers of tarmac and line marking and whatever, that's all a system that will give you a road. Yeah, so there's systems and then you go into products where you're talking about a light switch or a chair or a particular type of table or whatever. Um, And the way it works is it just assigns codes. So you can easily start talking about what that thing is. One of the examples they give here under the SS for systems. You can talk about things at a high level and roll it up, cos some clients only wanna know, uh I wanna know about, A lighting, how many, how many uh lighting, um. Elements have I got in my building? Like 783. Awesome, thanks. Whereas someone else has got to go down right down into the nitty gritty and go, Well, how many of these particular lights have I got in this room, or whatever. So that's, it's all about categorising and grouping things and so you're talking about them in the same way. Uh, example of what they do in Queensland Health, um, there, there is a skipped over the other tables just for simplicity, but there are things like complexities, uh, sorry, complexes, entities and spaces, locations as tables, which start talking about the use of space and how that rolls up. So we won't focus on that too much, but systems and products, again, is the key one, key one that they're doing. Um, Transport for New South Wales have got this publicly available document, if you do want to look at it, look for that number, DMS SD 124, um, and that's all about how they, Apply uni class within their super complex transport network. Uh, That was very quick. Any questions on that one, and then I've got one last little section about tying it back to client need, which will take a couple of minutes, but we'll see how we go. We'll come back to classification questions at the end. It's a client need everything recording a bit. Yeah, sure. We've got, still got a few minutes, so we'll see how we go. Um, but client need, everything comes back to client need. Yeah, so all of the stuff we were talking about before, everything that you deliver or you design, what your design looks like, what it contains. Physical building, it's gotta be driven by the client, yeah, it's the same with the information as well, so some of it, yeah, maybe the contractor wants this bit of information or a subcontractor wants this bit of information. But in large part, it's gonna be driven by what the client wants. For whatever they're doing, so what is their use case for data? What are they actually gonna be doing with this building once it's handed over, what data would be relevant to them? What do they need, and that's really important that you have that in your mind at every step. Whether you Delivering a design, whether you're specifying information, whether you're writing a BEP. What do you actually need, because everything that you specify and include, That they don't actually want. Is more dollars. Yeah, they're gonna, someone's gonna pay for it. You might not see that, but if you put in, oh yeah, we want serial numbers for all of this type of asset, someone's physically got to go around on site during construction, read a serial number from a speaker, put it into, uh, probably some sort of app in the short term, go back to the office, transfer it from the app to the relevant bit of model geometry. And that's time. You do that by hundreds of items or thousands of items. Do they really need the serial number for that? Or do they just need to know, make and model so they can find a warranty certificate or something? Or how's it gonna work? Um, so really bringing it back to what the client needs is super important, because it's kind of like this, you probably have seen stuff like this before as well. There's just so much confusion out there. I've seen some really good examples held up this case study, oh yeah, this is going back 20 years, we did this awesome bem for this project. We, uh, handed it over to the client. There were 22 fields of information. And for all the stuff they're interested in and the client. Got up on stage and said, yeah, that was good, but out of the 22. We didn't want 14 of them, and we were missing 3 other really important ones. So we would have traded those 14 for these 3 other fields of information. So it's going back to what the client wants, super important. Um, so clear. Communication of information requirements and needs is vital, but then all that's also got to flow through
Client Need
Implementing Need
Needs to be driven by constant communication with the clients in the physical world.
Use Cases for the Clients
After they receive the building and all of the data, what are they going to do with it?
Specifying Data Needs
Implementing the specifications need to follow the needs of the client, by communicating with the data, BIM or BEP, so what their values are.
Avoiding Dollars Wasters
Don't waster specifiers that clients wont like.
Communication Requirements
Implementing communication requirements helps benefit all parties that have been involved.
Clear line of communication between requirements.
Table Information
Identifying information
You must identify what information the floor provides.
*
Using Classification
Using Correct Code
All code should be categorized into the system.
Client Communication
Communication implementation
This can assist with weaving in values during data checks to help create a streamline delivery of information.
Review Points
Common Values
This will align with review to make the key things of clients as deliverable for each design.
Conclusion
Final Points
These are the deliverables for the project, such as PIM or client frameworks.
Client Needs and Data Specification
Data specification needs to come from a client based body, it needs to show the requirements of either operation or client body.
Templates
National implementation
The older and newer specifications implement the national needs. The implementation also combined with the bin management plan can assist with what is need.
That, that, that there, so it does get pretty complex pretty quickly. Um, so that's why it's always important to bring it back to what does the client wants. Um, So I think that this is a good. Example for you to look at where it's not a great document, it's not a great project information requirements document at all, but it's one that's publicly available and representative of where the client was in terms of their maturity at the time, and it's, it's, it's, yeah, freely available from their website. Um, so it does give you an idea around how they're specifying information, uh, and of course, you know, as we're looking earlier, it fits within, um, a much broader, Um, framework for them, where you're using a whole bunch of different things. Um, to I get to the outputs point at the various stages throughout a project of asset data, models, all sorts of stuff like that. Um, and most parts of that are freely available. There's a list there showing, uh, the capital infrastructure requirements. They're not really model-based at all, but they have a lot about, uh, the engineering, the architecture. At this stage, you should deliver these drawing types and stuff like that, and they refer to the PIR that does the heavy lifting in terms of information requirements. And then there's templates that are provided, rabbit templates, cause that was their, um, They deemed that their supply chain was using that tool more than any of the other tools, and they had a limited budget, so they created that in the first instance, um, equipment lists that are basically like asset lists that contain some data that needs to be ingested into the models, um. Execution plan templates for the supply chain to use, and then they're expecting those deliverables for which there's templates out the back as well. So if you were super motivated and wanted to have a look at a real world example, you could take some of that framework, uh, info. Um, and you could look at a different section and go through and go, OK, well, how would this apply to a real world project? And this, um, process here, which I've used with other groups, is going through and creating an example of free assets in something like, uh, Revver, um, ingesting that info, and, um, looking at how you then export that. Into a client template. So you're ultimately going from beginning to end and giving um. The clients, what they've specified, and so do you understand that, cos that's what this is about industry given these documents. So if you can read that and understand it, even if you don't do the process, being able to read through and follow along, understand what they're asking for, gives you a pretty good head start. That's it. So any questions? There was a lot of it was like drinking from the fire hose a bit, into the execution plans. So being able to connect it back to client values as well, so this applies whether you're writing specifications or whether you're doing something like a BEP being able to weave in, maybe not in a technical document, where you're getting super, um, Uh, into the weeds around model formats and whatever, but being able to pick bits out and go, oh yeah, they say they want a digital campus and that they like innovation, and integrity is really important, so you can weave that into these data checks are done to ensure the integrity of the data. At handover and so you can start, you know, tying it back to client values, um, which is probably more important when you're writing, um, information requirements, but you can still factor that in when you're writing a BIAM execution plan, for example. We want to do this stuff because it aligns with the client values that we've determined from this document or that document. Um, but the big thing that you're really looking for when you're applying something like 19,650 is that going from the PI to the aim, uh, that, that gap, making sure that you're specifying information that's gonna be of value to be able to deliver the project, um, but also be, um, really valuable for the client. And this, this is kind of like a simplified version of what we saw before. Starting the project here, project information delivers over time, it's being exchanged with your common data environment. But ultimately, it
The Client's Perspective on 19,650 Alignments
Specification Clarification
Client driven, innovation, and the integrity of the whole process and design. Ensure specifications are correct and that documents contain valuable information.
Making sure information is delivered from the requirements to be able to deliver the project.
Communication for Data Value
Need to make things valuable and streamlined the data so things can be completed on the correct project.
Common Data Implementation
Information exchange system
What system do you plan to use for the data exchange process?
Questions and Closing Remarks
Questions Answered
There were questions about ISO implementation, states in Australia and where things should be implemented.
Summary
Quick note
Overall there needs to be an effort into to 19,650 in some shape or fashion.
Gratitude to Mark
Mark was proudly recognized and thanked to his effort into drafting and provided input to the ISO standard.
Additional Comments
2/3 the marking of this data has been completed, 2/3.
Quality of the standard and its effort has been high.