Skip to content
PodSubs
ShowsPeopleGuestsJobsNewsEvents
More
BlogPodCred
Menu
ShowsPeopleGuestsJobsNewsEventsBlogPodCredNetworksSign in
Join nowSign in
  • Shows
  • People
  • Jobs
  • News
  • More
    • Guests
    • Events
    • Blog
    • PodCred
    • Networks
    Join nowSign in

Reimagining AEC

Reimagining AEC artwork

Introduction to BIM: Reliable Information from Design to Operation

Nov 2, 202635 minAudio

In this episode of Reimagining AEC, his own independent podcast, Dr Sepehr Abrishami follows one services riser in a residential block to set out what building information modelling is and what it is for. The episode covers the ISO 19650 definition of BIM, the dimensions from 3D to 6D, the move from PAS 1192 to ISO 19650, the common data environment, level of information need, and the chain from exchange information requirements to delivery plans. It closes with the golden thread under the Building Safety Act 2022 and the place of digital twins in the same framework. Chapters 0:00 Opening: one riser, one question 3:08 The problem and the definition 7:14 One set of objects, four classes of information: 3D, 4D, 5D and 6D 12:47 From a UK maturity model to an international vocabulary 16:24 The common data environment 20:45 Asking for the right information: requirements and level of information need 24:38 The supply chain's answer: BEP, MIDP, TIDP and the delivery process 27:50 After handover: the golden thread and digital twins 31:47 Close After listening, you should be able to: Define BIM using the ISO 19650-1 definition and explain why BIM is a process rather than a software product. Explain what the BIM dimensions from 3D to 6D add, and how errors in 3D information carry into programme, cost and operation. Trace the transition from the Levels framework and the PAS 1192 suite to the BS EN ISO 19650 series and the 2021 Information Management Mandate. Apply the four states of a common data environment and the decisions that move information between them. Distinguish level of information need from the older level of development scale. Outline the hierarchy of information requirements and how the EIR drives the BEP, MIDP and TIDPs, and relate the golden thread and digital twins to ISO 19650 delivery. References Barton, T. (2020, May). Pressing pause to avoid error. Institution of Civil Engineers. https://www.ice.org.uk/news-and-insight/the-civil-engineer/may-2020/pressing-pause-to-avoid-error British Standards Institution. (2018). BS EN ISO 19650-1:2018 Organization and digitization of information about buildings and civil engineering works, including building information modelling (BIM). Information management using building information modelling. Part 1: Concepts and principles. BSI. British Standards Institution. (2018). BS EN ISO 19650-2:2018 Organization and digitization of information about buildings and civil engineering works, including building information modelling (BIM). Information management using building information modelling. Part 2: Delivery phase of the assets. BSI. British Standards Institution. (2020). BS EN ISO 19650-3:2020 Organization and digitization of information about buildings and civil engineering works, including building information modelling (BIM). Information management using building information modelling. Part 3: Operational phase of the assets. BSI. British Standards Institution. (2020). BS EN ISO 19650-5:2020 Organization and digitization of information about buildings and civil engineering works, including building information modelling (BIM). Information management using building information modelling. Part 5: Security-minded approach to information management. BSI. British Standards Institution. (2020). BS EN 17412-1:2020 Building information modelling. Level of information need. Part 1: Concepts and principles (Withdrawn). BSI. British Standards Institution. (2022). BS 8644-1:2022 Digital management of fire safety information. Part 1: Design, construction, handover, asset management and emergency response. Code of practice. BSI. British Standards Institution. (2024). BS EN ISO 7817-1:2024 Building information modelling. Level of information need. Part 1: Concepts and principles. BSI. Building Safety Act 2022, c. 30. https://www.legislation.gov.uk/ukpga/2022/30 Centre for Digital Built Britain. (2018). The Gemini principles. University of Cambridge. https://www.cdbb.cam.ac.uk/system/files/documents/TheGeminiPrinciples.pdf Construction Leadership Council. (2024). Delivering the golden thread: Guidance for dutyholders and accountable persons. Construction Leadership Council. Hackitt, J. (2018). Building a safer future: Independent review of building regulations and fire safety. Final report. HM Government. Hetherington, J., & West, M. (2020). The pathway towards an information management framework: A "commons" for Digital Built Britain. Centre for Digital Built Britain. Infrastructure and Projects Authority. (2021). Transforming infrastructure performance: Roadmap to 2030. HM Government. International Organization for Standardization. (2022). ISO 19650-4:2022 Organization and digitization of information about buildings and civil engineering works, including building information modelling (BIM). Information management using building information modelling. Part 4: Information exchange. ISO. International Organization for Standardization. (2025). ISO 19650-6:2025 Organization and digitization of information about buildings and civil engineering works, including building information modelling (BIM). Information management using building information modelling. Part 6: Health and safety information. ISO. Sacks, R., Eastman, C., Lee, G., & Teicholz, P. (2018). BIM handbook: A guide to building information modeling for owners, designers, engineers, contractors, and facility managers (3rd ed.). Wiley. UK BIM Framework. (2019). Information management according to BS EN ISO 19650. Guidance Part 1: Concepts (2nd ed.). UK BIM Framework. UK BIM Framework. (2020). Information management according to BS EN ISO 19650. Guidance Part C: Facilitating the common data environment (workflow and technical solutions) (1st ed.). UK BIM Framework. Reimagining AEC is Dr Sepehr Abrishami's own podcast. Related episodes take up the subjects introduced here one at a time, among them 4D BIM, cost management with BIM, information requirements under ISO 19650, the common data environment and the golden thread for higher-risk buildings, and each can be heard in any order.

Audio and video play straight from the show's own hosting. PodSubs stores and serves no media.

Transcript

From the show.

Segment 1: Opening

Every design team works from drawings that keep changing, and someone has to know which version is the one to build from. I am Dr Sepehr Abrishami, and managing a design team, as I did for part of my career in architectural practice, put that question in front of me again and again. Reimagining AEC is where I work through problems like that one, and this episode starts from the term underneath all of them, building information modelling, and what it should mean.

Let me start with a situation. It is illustrative rather than a real project, but anyone who has spent time on site will recognise it. A contractor is building a twelve-storey block of flats in England. On the fourth floor, a ventilation duct has to pass through a fire-rated wall in a services riser. Earlier in the month the mechanical engineer moved the duct and issued a revised drawing. The fire-stopping installer is still working from the previous revision, because that was the copy in the site folder. The penetration through the wall is sealed in the wrong place. Meanwhile, the new duct route runs straight into a steel beam, and nobody noticed, because the structural drawings and the mechanical drawings were never checked against each other. Much later, an inspection finds the problem. The wall is opened, the duct is rerouted around the beam, the fire-stopping is redone, and the programme slips.

Notice that nobody in that story did careless work. Every person acted on the information in front of them. The information was the problem. It was out of date, it disagreed with other information, and the correct version was not where the installer could reach it.

So the question for this episode is this. What does it take for information about a built asset to be reliable enough to base decisions on, from the first design meeting to the years the building is in use?

By the end, you will be able to define building information modelling, or BIM, in the terms of the international standard. You will be able to explain what the dimensions from 3D to 6D add, and why UK practice moved from the PAS 1192 documents to the ISO 19650 series. You will be able to apply the four states of a common data environment, tell level of information need apart from level of development, and trace how a client's information requirements lead to a BIM execution plan and to delivery plans. You will also be able to place two recent developments, the golden thread and digital twins, inside the same framework.

We will get there in six steps. First the problem and the definition. Then the dimensions of BIM. Then the change of standards that gave the industry a shared vocabulary. Then the common data environment, where information is managed. Then the way a client asks for information and the supply chain answers. And finally, what happens to information after handover. The duct in that fourth-floor riser will come with us through every step.

Segment 2: The problem and the definition

The riser story is small, but the pattern behind it is well documented. Traditional information management on construction projects rests on two-dimensional drawings, and drawings leave room for interpretation between disciplines. When the architect, the structural engineer and the mechanical engineer each draw their own version of the same space, the clashes between them are often found on site rather than during design. The cost of finding errors late is large. Writing for the Institution of Civil Engineers in 2020, Tom Barton of the Get It Right Initiative reports estimates that put the total cost of avoidable error at between ten and twenty-five per cent of project cost.

Procurement adds to the difficulty. Construction is usually procured in separate packages, so information does not pass cleanly from designers to constructors, and from constructors to the people who will operate the building. Late design changes then create quality defects and programme slippage. The effect compounds as projects grow more complex and supply chains grow longer, because every extra organisation is another place where information can be copied, altered or lost.

Behind all of these issues sits one common failing. Information is unreliable, inconsistent or inaccessible at the moment someone needs it. In the riser, all three happened at once. BIM, and the ISO 19650 series of standards that now governs it, were developed to address exactly that failing.

The definition that matters for professional and academic work comes from ISO 19650-1, published in 2018 by the International Organization for Standardization, ISO, and adopted in the UK as the British and European standard BS EN ISO 19650-1. It defines BIM as the use of a shared digital representation of a built asset to facilitate design, construction and operation processes to form a reliable basis for decisions.

Two parts of that definition deserve attention. The first is the word shared. BIM is a team working method. A model that sits on one designer's computer, however detailed, does not meet the definition. The second is the phrase reliable basis for decisions. The purpose of modelling is not the model itself. The purpose is the decisions the model supports: where the duct goes, when the wall is closed, what the change costs, which damper needs testing next year.

This leads to the most common misconception about BIM, that it is a piece of software. It is a process. Software supports the process, but software alone does not deliver BIM. The process runs through design coordination, cost planning, procurement, construction management and the operation of the asset, and it depends on standards, contracts and agreed protocols as much as on tools. Adoption reduces design errors, transaction costs and disputes when it is implemented against a defined information standard. Without that standard, the same software can produce the same confusion as the paper drawings in our riser.

One more point before we move on. You will often hear people talk about BIM dimensions, 3D, 4D, 5D and 6D, sometimes grouped as nD. This is a useful teaching frame, and I will use it in a moment. But nD is not a defined term in ISO 19650. It is shorthand for the classes of information carried by the model.

So the first part of the answer is already clear. Reliable information comes from a shared and managed process, set against a standard, and not from a particular tool.

Segment 3: One set of objects, four classes of information

Let us take the dimensions in turn, starting with 3D, because everything else draws on it.

3D BIM is the object-based, geometric and data-rich representation of a built asset. It differs from three-dimensional computer-aided design, or CAD, in one important respect. In a CAD file, a wall is a set of lines. In a BIM model, a wall is an object that knows it is a wall. It carries parameters such as its fire rating, classification data, and relationships to the floors and openings around it. That is what allows information to flow downstream into the later dimensions. Sacks and colleagues set out this distinction in the BIM Handbook, in its third edition of 2018.

On a real project, each discipline produces its own discipline model: architectural, structural, civil, and mechanical, electrical and plumbing, usually shortened to MEP. These discipline models are combined into a federated model, which is used for coordination, clash detection and design review. In our riser, the federated model is where the revised duct route would have been checked against the structural model, and where the beam would have been flagged as a clash long before anyone reached the fourth floor. Because the later dimensions all draw on this model, the quality of the 3D information directly shapes what 4D, 5D and 6D can deliver.

4D BIM links model elements to programme activities. It gives the project team a visual construction plan instead of a bar chart read in isolation. The way 4D works is a chain of four steps, and the order matters. You begin by extracting construction information from the federated model. You then examine the model elements for constructability, and that analysis identifies the activities needed to build them. Next, you link those activities through logical dependencies, so that one cannot start before another is complete. Only then can you plan site logistics, temporary works and the loading of labour and plant. Each step depends on the output of the one before, so a weak model at the start produces a weak programme at the end.

What 4D offers, in one principle, is the chance to rehearse construction before committing to it. You can watch the sequence before anyone is on site, test different buildability options for a difficult sequence, and catch sequencing errors in the simulation rather than on the ground, which is where they become expensive. In the riser, a 4D sequence would show whether the fire-stopping is scheduled before or after the final duct route is fixed. For a complex programme with thousands of activities, 4D is the most practical way of validating the logic before work starts.

5D BIM links model elements to cost data. Quantity take-off, cost planning and estimate control can then happen alongside design rather than after it. The workflow has a clear direction. The federated model is imported into a dedicated 5D platform, such as CostX. Quantities are generated from the model, grouped by element classification. Those quantities are exported to a Bill of Quantities. Productivity and pricing rules are then applied to build a cost plan that stays linked back to the model. The practical benefit is that the quantity surveyor can take part from concept design, comparing options against a live cost model rather than waiting for a set of tender drawings. Automating quantities reduces manual error and shortens the review cycle on complex and very large projects. Because the cost plan is coupled to the model, the cost of rerouting our duct appears in the cost picture quickly, instead of surfacing months later as a claim.

6D BIM concerns operational information. Facilities management has historically relied on handover documents produced at the end of a project, often disconnected from the design information that came before them. The result is duplication, gaps and errors when the building goes into use. ISO 19650-3, published in 2020, governs information management in the operational phase. In the UK, the structured format used to deliver asset data from project to operation is COBie, which stands for Construction Operations Building information exchange. A well-delivered 6D handover gives the operator a single source of current asset information. It shortens the time needed to populate computer-aided facility management systems, and it provides the foundation for a digital twin of the asset in use, which we will return to at the end. For the riser, 6D means the fire damper in that duct is handed over as a recorded asset, with its identity and location, rather than as a page in a binder.

So the dimensions are not separate products. They are the same objects carrying further classes of information: geometry, then time, then cost, then operation. That is why an error in the 3D information does not stay in 3D. It travels into the programme, the cost plan and the operator's records.

Segment 4: From a UK maturity model to an international vocabulary

If reliable information depends on a standard, the next question is which standard. The answer has changed, and you will meet both the old and new vocabulary in the literature, so the history is worth understanding.

In 2016 the UK government made BIM mandatory on centrally procured projects. This was known as the Level 2 mandate. The levels came from a maturity model known as the Bew-Richards wedge, after its authors, which set out four levels of BIM maturity numbered from 0 to 3. That model underpinned both the 2016 mandate and a set of British documents called the PAS 1192 suite, where PAS stands for Publicly Available Specification.

The difficulty was that the Levels framework was specific to the UK. Projects increasingly involve clients, designers and contractors from several countries, and international collaboration needs a shared language. So the concepts in PAS 1192 were developed into an international series, ISO 19650. Replacement began in 2019, when the first parts of the series were published as British standards and took over from PAS 1192-2. The PAS documents are no longer the UK reference.

The BS EN ISO 19650 series now has six parts, published between 2018 and 2025. Part 1 sets out concepts and principles. Part 2 covers the delivery phase of assets, and Part 3 the operational phase. Part 4 deals with information exchange. Part 5 sets out a security-minded approach to information management, and Part 6, the most recent, covers health and safety information. Together they define information management across both delivery and operation, using a set of concepts we will meet shortly: organisational, asset, project and exchange information requirements, and the common data environment.

Government policy moved with the standards. In 2021 the Infrastructure and Projects Authority published Transforming Infrastructure Performance: Roadmap to 2030. That roadmap redefined the BIM mandate as the Information Management Mandate, delivered through the UK BIM Framework, which is the UK's guidance for applying the ISO 19650 series. Among other things, it requires clients to define their information requirements, to procure and contract in line with the UK BIM Framework standards, and to maintain a system of record for the information they receive.

You will still see Levels 0 to 3 in older textbooks and papers. Treat them as historical context and use the ISO 19650 vocabulary in your own work. Two changes of wording matter in particular. The common data environment used to be described in terms of areas, and ISO 19650 describes it in terms of states. And a document called the Employer Information Requirements has been renamed. Both changes come back in the next two steps.

So the question of reliable information is now answered in an international vocabulary, and the two parts of that vocabulary we need next are the common data environment and information requirements.

Segment 5: The common data environment

Go back to the fire-stopping installer working from an old drawing. The root cause was not the installer, and it was not the drawing. It was the absence of a managed place where the current version of every piece of information lives, with a clear status. ISO 19650 calls that place the common data environment, or CDE.

ISO 19650-1 defines the CDE as the agreed source of information for any given project or asset, used for collecting, managing and disseminating information containers through a managed process. An information container is a named, persistent set of information that can be retrieved from a file, system or application. In practice it might be a drawing, a model, a programme or a cost plan.

The important word in the definition is managed. A shared folder is not a CDE. A CDE is a workflow with states, gates, permissions and an audit trail. It holds both graphical and non-graphical information containers, so models, drawings, schedules, reports and asset data all sit in the same governed environment. Every container carries a unique identifier, a status, a revision and a classification, applied in line with ISO 19650-2.

To follow information through the CDE, you need the names of the parties. The appointing party is the client, the organisation that receives the information. The lead appointed party is the organisation appointed directly by the client to coordinate a team of suppliers, such as a main contractor. A task team is a group within that supply chain carrying out one piece of work, such as the mechanical design. Governance of the CDE is the duty of the information management function appointed to work for the appointing party.

ISO 19650-1 defines four states, and the clearest way to understand them is to follow one container. Take the mechanical engineer's revised drawing of the duct in our riser.

It begins in the first state, work in progress. Here the drawing is being prepared inside the mechanical task team, and no other task team can see it. When the task team has checked and reviewed it, the team approves it, and it moves to the second state, shared. Now the structural task team can see the new duct route, overlay it on their model and raise the clash with the beam. Once the coordination is resolved, the drawing is reviewed again, and the lead appointed party authorises it. It moves to the third state, published, and is delivered to the client, who then reviews and accepts it. Only published information is used for construction, so the fire-stopping installer works from this version and no other. Alongside these three states sits the fourth, archive. The archive holds a record of every transaction on every container, kept for audit and for future reuse. The previous revision of the drawing is not deleted. It stays in the archive, marked as superseded, with a record of who changed what and when.

So there are three decisions on the path from preparation to use. The task team approves information for sharing, the lead appointed party authorises it for publication, and the client accepts it. These decisions are not paperwork. They are the mechanism that keeps the wrong version of a drawing out of the wrong hands, which is exactly what failed in the riser.

Here is the first change of wording I promised. Older UK guidance under PAS 1192 described these as areas of the CDE. ISO 19650 uses the word states, and states is the term to use.

The CDE answers one part of our question. It makes sure that people work from information with a known status. It does not decide what information should be produced in the first place. That is the job of information requirements.

Segment 6, Part 1: Asking for the right information

A client cannot receive reliable information if it has not said what it needs. ISO 19650 treats this as a hierarchy of requirements, and it runs from the client's whole organisation down to a single appointment.

At the top are the organisational information requirements, what the client needs to run its business. Next come the asset information requirements, what it needs to operate its assets, and the project information requirements, what it needs for a specific project. The exchange information requirements then translate all of that into what each appointment must deliver.

Follow this down for our block of flats. As an organisation, the client must be able to show that its buildings are safe. To operate this asset, it therefore needs a record of every fire damper, with its location, type and test history. On this project, it needs the fire strategy coordinated with the services design at agreed points. And in the mechanical engineer's appointment, those needs become a specific requirement: deliver the damper data, in a stated format, at stated milestones.

That last document is the exchange information requirements, or EIR. It is the specification the client writes to tell the supply chain what information it needs, for what purpose, at what point and in what format. It covers managerial, commercial and technical information. Here is the second change of wording. Under ISO 19650-2, EIR stands for Exchange Information Requirements. Under PAS 1192, the same initials stood for Employer Information Requirements. The older term has been retired. The EIR matters because it drives every plan that follows it down the supply chain.

The EIR also sets the level of information need for each deliverable. Level of information need is one of the most important conceptual updates in the current framework. The concept was introduced in the European standard BS EN 17412-1 in 2020, and it is now defined in the international standard BS EN ISO 7817-1, published in 2024, which replaced the European one. It answers a simple question: how much information do we need at this delivery point, and why?

The older approach used a fixed ladder of geometric development, known as level of development, or LOD, running from LOD 100 to LOD 500. That scale comes from the American Institute of Architects and is still widely used in North America, so you will see it in software. Level of information need works differently. Information is specified against a purpose, not against a generic maturity number.

It does this by asking about three kinds of information separately. Geometrical information covers detail, dimensionality, location, appearance and parametric behaviour. Alphanumerical information covers identification, classification and technical properties. Documentation covers drawings, schedules, reports and linked documents. Take the fire damper. For the purpose of maintenance and safety records, its geometry can be simple, a correctly sized object in the correct place. Its alphanumerical information needs to be complete: a unique identifier, its classification and its fire rating. Its documentation needs to include the test certificate. A single geometric ladder cannot express that combination. Level of information need can, because it asks each question against the purpose.

Segment 6, Part 2: The supply chain's answer

The client has now said what it needs. The supply chain answers with a BIM execution plan, or BEP. The BEP explains how the lead appointed party intends to deliver the information the EIR asks for.

There are two versions, and the difference between them is timing. The pre-appointment BEP is submitted with the tender, and it sets out how the prospective lead appointed party would meet the EIR. The post-appointment BEP is the version agreed at contract, and it is maintained throughout delivery. The BEP sets out roles and responsibilities, the information standards to be used, the methods and procedures for producing information, a responsibility matrix, and the proposed master information delivery plan.

That brings us to the delivery plans. Each task team prepares a task information delivery plan, or TIDP, listing the information it will produce and when. The master information delivery plan, or MIDP, brings all the TIDPs together into one plan for the project. So the chain reads in one direction. The EIR drives the BEP. The BEP proposes the MIDP. And the MIDP governs every TIDP in the supply chain. In our riser, the mechanical task team's TIDP would list the revised duct drawing and the damper data, each with a date, and the MIDP would show the structural coordination that depends on them.

ISO 19650-2 places all of this within an eight-step information delivery process, and it is easiest to hold in mind as two halves. The first four steps happen before anyone is appointed. In the first, assessment and need, the client establishes its requirements. In the second, the invitation to tender, it issues them to the market. In the third, the tender response, bidders reply, including the pre-appointment BEP. In the fourth, appointment, the contract is agreed along with the post-appointment BEP. The second four steps happen after appointment. Mobilisation sets up the team, the CDE and the agreed methods. Collaborative production of information is the long middle of the project, where task teams produce information and move it through the CDE states. Information model delivery is where information is authorised by the lead appointed party and accepted by the client. Project close-out completes the process and passes the information on for use in operation. Each step has defined inputs, outputs and responsibilities.

Put together, this is the information delivery cycle. Requirements flow down from the client's organisation to each appointment. Plans flow back up from each task team to the project. And the information itself moves through the CDE, gaining status as it is checked, approved, authorised and accepted.

Segment 7: After handover

Our question asked about reliable information from the first design meeting to the years the building is in use. So far we have mostly stayed in delivery. Two recent developments show why the answer must extend beyond handover.

The first is the golden thread of information. The Building Safety Act 2022 introduced a statutory duty to keep accurate, current and accessible building safety information across the life cycle of higher-risk buildings in England. A higher-risk building, for this purpose, is a building at least eighteen metres high or with at least seven storeys, containing at least two residential units. Our twelve-storey block qualifies. During design and construction, the golden thread is the responsibility of the dutyholders on the project. Once the building is occupied, it passes to the Accountable Person, who must be able to demonstrate it to the Building Safety Regulator. The Construction Leadership Council's guidance of 2024 sets out these responsibilities for both phases.

The duty reflects the recommendations of Dame Judith Hackitt's review of building regulations and fire safety, published in 2018 after the Grenfell Tower fire. In 2022 the British Standards Institution published BS 8644-1, the first British Standard on the digital management of fire safety information. It is aligned with ISO 19650.

The central point is that the golden thread is not a set of paper files or a document library. It must be structured, digital and traceable, linking design intent, as-built information and operational records. Think about what that requires in our riser. The fire-stopping, the duct penetration and the damper are exactly the kind of information the golden thread must hold. The record of which drawing was current when the wall was sealed, and who authorised it, comes straight from the CDE archive. BIM and ISO 19650 are the practical mechanism for meeting this duty, not an optional addition to it.

The second development is the move from static BIM models towards digital twins. A digital twin is a dynamic digital representation of a physical asset, connected by live data flows from sensors, building management systems and operational records. It extends the information delivered at handover with feedback from the asset in use, and that supports predictive maintenance, energy optimisation and the testing of scenarios during operation.

In the UK, the Centre for Digital Built Britain at the University of Cambridge led this work at national scale. It published the Gemini Principles in 2018, and in 2020 it published a pathway towards an Information Management Framework, written by James Hetherington and Matthew West. Both were intended to support a National Digital Twin of connected infrastructure.

For an individual building, the dependency is direct. ISO 19650 provides the information management foundation on which an asset digital twin is built. Suppose a sensor on the fire damper in our riser reports a fault. The twin can say which damper it is, which wall it protects and when it was last tested, only because that information was specified in the EIR, produced to the right level of information need, moved through the CDE and delivered at handover. Without well-governed information at handover, you cannot build a useful twin in operation.

So the answer to our question does not end at practical completion. The same managed information that made delivery reliable is what makes the golden thread possible and what a digital twin depends on.

Segment 8: Close

Let me draw the episode together.

We set out to answer one question: what does it take for information about a built asset to be reliable enough to base decisions on, across its whole life? The answer is a shared and managed process, set against the ISO 19650 series. The client states what it needs and why, from its organisational requirements down to the exchange information requirements for each appointment. The supply chain answers with a BIM execution plan and delivery plans. Information is specified by purpose through level of information need, produced as objects that carry geometry, time, cost and operational data, and moved through the four states of a common data environment under three clear decisions. It is then carried into operation, where the golden thread and digital twins rely on it.

Replay the riser with all of that in place. The clash with the beam appears in the federated model. The revised drawing moves from work in progress to shared, the structural team sees it, and the route is coordinated. Only the published revision reaches site. The superseded one sits in the archive with its history. The damper is handed over as a recorded asset, and its data feeds the golden thread and, in time, the twin. The same people do the same work, but now the information they act on can be trusted.

There are four things I would ask you to take from this episode. First, define BIM as the standard does, as a shared digital representation that forms a reliable basis for decisions, and judge any model by the decisions it supports. Second, use the current vocabulary in your work: ISO 19650, states rather than areas, Exchange Information Requirements, and level of information need, with Levels 0 to 3 and PAS 1192 treated as history. Third, when you specify or review information, start from its purpose, and trace the chain from the EIR to the BEP, the MIDP and each TIDP. Fourth, treat handover as a transfer rather than an ending, because the golden thread and any digital twin are only as good as the information delivered.

For further reading, start with ISO 19650 Parts 1, 2 and 3, which you will cite throughout your studies, together with BS EN ISO 7817-1 for level of information need and BS 8644-1 for the golden thread. The BIM Handbook by Sacks and colleagues gives the wider context, and the UK BIM Framework guidance is the best source of current practice between revisions of the standards. The first dimension, 3D coordination and federated models, repays a closer look of its own.

A site folder full of old revisions is not inevitable, and showing what replaces it is why I, Dr Sepehr Abrishami, make Reimagining AEC. Trace how information reaches the people on your next project, in practice or in research, and count how many of the riser's three failures could happen there.

Open the transcript file

Hosts and Guests

Nobody is credited on this episode yet.

Credit the people on this episode

Be the first to rate this episode

More episodes

All episodes
  1. Roles and the Responsibility Matrix

    Nov 10, 202633 minAudio

    On Reimagining AEC, his own podcast, Dr Sepehr Abrishami asks which organisation has failed when an information management task on a project goes undone, and how anyone could prove it in writing. A hypothetical council...

    Credit the people on this episode

  2. The Delivery Plans

    Nov 10, 202635 minAudio

    On Reimagining AEC, his own podcast, Dr Sepehr Abrishami asks how many task team plans become one master plan whose dates hold, and what a lead appointed party must do when they cannot. A hypothetical community hub,...

    Credit the people on this episode

  3. The BIM Execution Plan

    Nov 10, 202636 minAudio

    On Reimagining AEC, his own podcast, Dr Sepehr Abrishami asks how one BIM execution plan can serve both the tender and the appointment. A hypothetical community hub for a district council, whose tender cites a withdrawn...

    Credit the people on this episode

  4. The UK BIM Framework and the Move from PAS 1192

    Nov 10, 202634 minAudio

    On Reimagining AEC, his own podcast, Dr Sepehr Abrishami asks what the UK BIM Framework is and is not, and how a legacy document set maps onto the standards in force today. A hypothetical council's information pack,...

    Credit the people on this episode

  5. Management Systems for Information

    Nov 10, 202648 minAudio

    On Reimagining AEC, his own podcast, Dr Sepehr Abrishami asks where information management should sit inside an organisation's quality, risk and safety systems, and what changes when it sits there. A hypothetical design...

    Credit the people on this episode