Guidance Part 2 - Parties Teams and Processes For The Delivery Phase of Assets - Edition 6 PDF
Guidance Part 2 - Parties Teams and Processes For The Delivery Phase of Assets - Edition 6 PDF
Guidance Part 2 - Parties Teams and Processes For The Delivery Phase of Assets - Edition 6 PDF
Edition 6
Published by
2 | Guidance Part 2 Edition 6 - February 2021
Parties, teams and processes for the delivery phase of the assets
Editions
Edition 1 July 2019 First release
Edition 2 October 2019 Update includes:
About the common data environment (CDE) ISO 19650-2 clause
5: analysis and activities (covering clauses 5.1, 5.2, 5.3, 5.4, 5.8)
Edition 3 January 2020 Update includes:
ISO 19650-2 resource map About information requirements
About the BIM execution plan
ISO 19650-2 clause 5: analysis and activities (covering clauses
5.5, 5.6, 5.7)
Edition 4 April 2020 Update includes:
About exchange information requirements
About the level of information need
About information delivery planning
About open data and buildingSMART
Nothing in this guidance constitutes legal advice or gives rise to a solicitor/client relationship. Specialist legal advice should be taken in
relation to specific circumstances.
The contents of this guidance are for general information purposes only.
Permission to reproduce extracts from the ISO 19650 series is granted by BSI Standards Limited (BSI) and the copyright in Figure 2 used
in this report belongs to BSI. No other use of this material is permitted.
British Standards can be obtained in PDF or hard copy formats from the BSI online shop: http://www.bsigroup.com/Shop or by contacting
BSI Customer Services for hard copies only: Tel: +44 (0)20 8996 9001, Email: [email protected]
Any data or analysis from this guidance must be reported accurately and not used in a misleading context.
If using any information from this report, then its source and date of publication must be acknowledged.
Table of contents
Message from the UK BIM Alliance Chair 3
Acknowledgments4
About BS EN ISO 19650 and building information modelling (BIM) 5
Abbreviations and acronyms 6
About this guidance document 7
1.0 About ISO 19650 parties and teams 8
1.1 U
nderstanding your role and the team context 8
1.2 Understanding activities and stages 13
1.3 Appointing party 14
1.4 Lead appointed party 18
1.5 Appointed party/task team 24
2.0 ISO 19650-2 clause 5: analysis and activities 28
3.0 About the 2021 National Annex 72
3.1 Changes in the 2021 National Annex 73
3.1.1 Information Container ID Applicability 73
3.1.2 Field/String Length 74
3.1.3 Project Identifier 75
3.1.4 Originator Identifier 76
3.1.5 Functional Breakdown Identifier 77
3.1.6 Spatial Breakdown Identifier 78
3.1.7 Form Identifier 79
3.1.8 Discipline Identifier 81
3.1.9 Unique Number Identifier 83
3.1.10 Status 84
3.1.11 Classification 87
3.2 A pplying the 2021 National Annex 88
3.2.1 A pplication guidance for assessment and need 88
3.2.2 Application guidance for the remainder of the delivery phase 89
4.0 Information management process summary 90
5.0 Summary 102
2 | Guidance Part 2 Edition 6 - February 2021
Parties, teams and processes for the delivery phase of the assets
List of figures
Figure 1: ISO 19650 guidance framework 7
Figure 2: Interfaces between parties and teams 8
Figure 3: Simple party/appointment relationship 9
Figure 4: The scenario where there are multiple lead appointed parties and appointed parties (note
the parties identified are for illustration only). 10
Figure 5: Example appointing party and lead appointed party relationships, early design stage (note
the parties identified are for illustration only) 11
Figure 6: The change in the architect’s appointment from a pre to post novation scenario (note the
parties identified are for illustration only) 12
Figure 7: Make-up of the delivery team (note the parties identified are for illustration only) 12
List of tables
Table 1: Abbreviations and acronyms 6
Table 2: Activities and stages 13
Table 3: Information management components of the lead appointed party’s appointment 15
Table 4: A ppointing party activity focus 16
Table 5: Information management components of the lead appointed party’s appointment 19
Table 6: Information management components of the appointed party’s appointment 20
Table 7: Lead appointed party activity focus 22
Table 8: Information management components of the appointed party’s appointment 25
Table 9: Appointed party/task team activity focus 27
3 | Guidance Part 2 Edition 6 - February 2021
Parties, teams and processes for the delivery phase of the assets
The UK BIM Framework provides the the “end in mind” and consideration from an
fundamental step towards digital organizational, whole life perspective. This
transformation of the UK’s built environment then informs the detailed requirements right
industry. The Framework is based on the ISO down to appointment level.
19650 series, which first developed out of the
UK’s former BIM Level 2, but incorporates The work behind developing this Guidance
and anticipates global and future digital has been considerable. I would like to thank
perspectives. Sarah Davidson and David Churcher for their
tireless commitment in continuing to bring this
The UK BIM Framework embraces and assists work together – I so enjoy working with you
in the implementation of the standards both. Secondly, I would like to thank the many
for managing information for the whole authors who have contributed so generously
life of assets of the built environment. The to the writing of the Guidance – and been so
Framework anticipates the potential for patient in the criticisms and changes that have
integration across portfolios. The Framework been required of them. Finally, I would like to
provides extensive Guidance which continues thank the many people who have spared time
to be developed, including the addition of to review and feedback on the Guidance – the
supplementary tools and materials to enable Focus Groups in particular, but also those who
a firm basis for the evolving National Digital have contacted us separately. Without this
Twin Programme. feedback we would not be able to incorporate
the wide-ranging experience and testing which
This Guidance has been developed to help is occurring around the industry.
industry to implement the concepts and
principles of the ISO 19650 series upon which We welcome your continued feedback and
the UK BIM Framework is based. It has shared experiences. You can provide this via
been continually updated to keep track of [email protected].
the publication of the different parts of ISO
19650, and to reflect lessons learnt as further
experience is gained in its implementation.
Acknowledgments
This guidance represents the collaborative efforts of
the following people and organizations
Editors
David Churcher Hitherwood Consulting Ltd Author: Sections 1 and 2
Sarah Davidson University of Nottingham Author: Sections 1 and 2
Anne Kemp Atkins
Authors
Andy Boutle Kier Author: Section 2
Paul Dodd Scottish Futures Trust Author: Section 2
Jack Dearlove ISG Author: Section 2
Emma Hooper Bond Bryan Author: Section 2
John Ford Galliford Try Author: Section 2 and 3
Dan Rossiter British Standards Institution Author: Section 2
Ryan Tennyson Scottish Futures Trust Author: Section 2
Neil Thompson Atkins Author: Section 2
May Winfield Buro Happold Author: Section 2
Sonia Zahiroddiny
HS2 Author: Section 2
Contributors
Nigel Davies Evolve Consultancy
Stephen Holmes Cadventure Ltd
Michael Hudson Flanagan Lawrence
Simon Lewis Womble Bond Dickinson
David Philp Centre for Digital Built Britain
Casey Rutland Royal Haskoning DHV
Production
Centre for Digital Built Britain
5 | Guidance Part 2 Edition 6 - February 2021
Parties, teams and processes for the delivery phase of the assets
This guidance includes a number of abbreviations and acronyms as set out in Table 1.
Table 1: Abbreviations and acronyms
ISO 19650
Guidance Part 1
Concepts
ISO 19650 ISO 19650 ISO 19650 ISO 19650 ISO 19650 ISO 19650
Guidance A Guidance B Guidance C Guidance D Guidance E Guidance F
The Open data, Facilitating the Developing Tendering and Information
information buildingSMART CDE (workflow information appointments delivery
management and COBie and technical requirements planning
function & solutions)
resources
Guidance part 2 is written to support the As with all guidance supporting the UK
implementation of ISO 19650-2 and is BIM Framework, we invite comment and
relevant to any organization involved in the feedback on this guidance part 2 at
delivery phase of an asset. It considers the [email protected].
arrangement of parties and teams according
to ISO 19650-2 and the activities associated
with each sub-clause within ISO 19650-2
clause 5.
Key:
Appointing
A Party
1
3 2
Lead
B Appointed Party C
C
Appointed Party C
1 C
Project Team
2 B ...
2
Delivery Team
3
Task Team(s)
... B
3
A
Information requirements
and information exchange
within a delivery team and
with the appointing party
B 2
Information co-ordination
between delivery teams
3
C
Appointing party
(the client)
Appointment
Lead appointed
party
(for example for
construction)
Appointment
Appointed party
(for example the
steelwork
sub-contractor)
Appointed party
(the structural engineer)
Appointed
party
(the architect)
Key:
Appointing Party
Appointment
Figure 4: The scenario where there are multiple lead appointed parties and appointed parties (note the parties identified
are for illustration only).
11 | Guidance Part 2 Edition 6 - February 2021
Parties, teams and processes for the delivery phase of the assets
Appointed party
(the structural engineer)
Key:
Appointing Party
Appointment
Figure 5: Example appointing party and lead appointed party relationships, early design stage (note the parties
identified are for illustration only)
12 | Guidance Part 2 Edition 6 - February 2021
Parties, teams and processes for the delivery phase of the assets
Appointed party
(the structural engineer)
Lead appointed
Key: party
Appointing Party (for construction)
Appointment
Appointment pre-novation
Figure 6: The change in the architect’s appointment from a pre to post novation scenario (note the parties identified are
for illustration only)
A lead appointed party and their appointed Where there is a lead appointed party
party/parties make up a delivery team as there will be a delivery team (even if the
shown in Figure 7. delivery team only consists of one lead
appointed party organization). Most projects
will therefore comprise multiple delivery
teams, regardless of the structure of the
overall project (traditional, design and build,
management and so on).
Appointed
Delivery party
(the architect) The project team comprises the appointing
team
party (the client) plus all delivery teams as
Lead appointed show in this guidance and ISO 19650-2 Figure
party 2. It is therefore essential that information
(for
architecture) Appointed is coordinated across delivery teams as well
party as within delivery teams. This requirement is
(the interior
designer) explored further in ISO 19650 guidance A.
Key:
Appointment
Figure 7: Make-up of the delivery team (note the parties identified are for illustration only)
13 | Guidance Part 2 Edition 6 - February 2021
Parties, teams and processes for the delivery phase of the assets
Per Project
1
3 2
C
C If you are a client or are managing information on behalf
C
2 B ... of a client this means that you are fulfilling the role of the
... B “appointing party” – you are effectively the party “owning” the
A
3
appointment/project in the context of the ISO 19650 series.
B 2 As appointing party you are a member of the Project Team.
3
C
Your activities and outputs can be Then for each separate piece of work you are
summarized as: sending out to tender, you need to establish
your information requirements. Your outputs
Firstly – to make sure that your information
in compiling each tender package should
management function is fulfilled by people
consider, and where appropriate include:
within your organization or people acting on
your behalf or a combination of both. • E xchange information requirements (EIR)
Then wherever the ISO 19650 series refers • Existing information and resources that are
to the “appointing party” this means relevant to the tendering opportunity
the organization(s) fulfilling the client’s • Details of how the tender will be evaluated
information management function. • Overall project requirements for
information delivery, standards and
Going forward then, in respect of the whole processes
project and before any invitations to tender
• The project’s information protocol.
are issued, your activities as appointing party
are to: It is up to you to determine how these project
level and appointment specific resources are
• E stablish the project’s information
assembled into the tender and appointment
requirements, information delivery
package for a lead appointed party
milestones and information standards
• Identify specific procedures for the In the process of confirming an appointment
production of information including (of the lead appointed party for example the
its generation, delivery and secure main contractor) you will both need to agree
management any changes to the information standards
• Identify existing information and/or and they should inform you of any risks/
resources that are relevant to the delivery issues which could impact project information
teams you will be appointing to this project delivery milestones. The appointment
• Establish the project’s information documents should then include information
protocol for incorporation into all project and information requirements relevant to the
appointments. appointment.
You will also need to establish a common data This is a process/activity that is repeated for
environment (CDE) to support the project and each confirmed appointment.
the collaborative production of information.
You may wish to appoint a third party to host,
manage or support the CDE.
Information protocol ✓
1
3 2
C
C
C If you are responsible for coordinating information between the
2 B ...
...
delivery team that you are part of and the appointing party
B
3 A (client) this means that you are fulfilling the role of the “lead
appointed party” in the context of the ISO 19650 series.
B 2 You are a member of both the Project Team and a Delivery
3 Team.
C
Then wherever the ISO 19650 series refers The outputs from these activities should form
to the “prospective lead appointed party” part of your overall tender response.
or “lead appointed party” this means the
organization(s) fulfilling your information
management function.
Information protocol ✓
Your first activity at this point is to update You are also responsible for compiling the
and confirm the BEP in collaboration with master information delivery plan (MIDP)
each (to be) appointed party. Any required through the collation of the task information
additions or amendments to the project’s delivery plans (TIDPs) generated by each task
information standard, its production methods team (as a lead appointed party you may
and procedures, and its information protocol also have to undertake task team activities so
will need to be agreed with the appointing you may have your own TIDP).
party. The BEP will have contained a high
level responsibility matrix and this now See ISO 19650 guidance A to see the
needs to be separately refined, developed relationships between the appointment
and sufficiently detailed to identify what resources and ISO 19650 guidance E to see
information is to be produced, when and by more detail about the BEP.
whom (i.e. which task team).
See ISO 19650 guidance D to see more detail
As lead appointed party, you may have your
about information requirements
own information requirements in addition
to those provided to you by the appointing
party. A key activity at this stage is therefore
articulating these combined EIR relevant to
each prospective appointed party within your
delivery team so that each has clear direction
about what is required of them.
20 | Guidance Part 2 Edition 6 - February 2021
Parties, teams and processes for the delivery phase of the assets
You then need to mobilize resources. This This process should repeat and continue
means getting people within the delivery team throughout your appointment.
suitably trained with technology and processes
in place, tested and up and running. The Another activity of the lead appointed party
project’s common data environment (CDE) is is to capture lessons learned, in collaboration
fundamental to successful information based with the appointing party - ideally throughout
activities and as lead appointed party you your appointment, as opposed to just at the
should be made aware of any issues task end of it.
teams experience with its operation, or with
the information/resources accessed through
it. Only then is the delivery team in a position
to generate, assure, review and authorize
information for sharing.
1
3 2
C
C
C If you are tendering for or appointed to a project
2 B ...
...
generally, this means that you are fulfilling the role of
B
3 A an “appointed party” in the context of the ISO 19650
series. You are a member of both the Project Team and
B 2 a Delivery Team.
3 Your organization may include a number of task teams
C
within it.
ethod of specifying level of information need: What method of describing the level
M
of information need has been established for the project.
For example, the information standard may establish that the NBS level of definition
convention shall be used. In which case it will likely either cross-reference to an
external source or include the textual description and an associated code for each
level of detail and level of information.
For example, the information standard may establish additional information that
should be incorporated such as the use of NRM3 codes in addition to Uniclass 2015
classification.
It should be noted that as the information standard is project-specific, some of the
established information standards may not be applicable depending on the nature of
the appointment.
For example, additional handover information may be included within the
information standard which are not relevant for an appointment to produce a
concept design.
Remember that the information standard is set out at a project rather than
appointment level. Its amalgamation with the information production methods
and procedures may prove beneficial as both are project-specific and often used
in tandem (unlike the exchange information requirements, which is an appointment
specific resource).
Clause: 5.1.5 Establish the project’s information production methods and procedures
The primary party active Insight:
within the clause:
When establishing the information production methods and procedures, the
Appointing party appointing party considers:
Contributing parties to Capture of existing asset information: How existing information will be captured.
the clause:
n/a For example, the information production methods and procedures may establish
what properties need to be captured about existing asset information, the permitted
When the activity within values, or measurement units. It may also specify which information container(s) this
the clause should be
information is captured within.
carried out:
Before tendering the first eneration, review or approval of new information: How information is produced,
G
lead appointed party reviewed or approved.
appointment
For example, the information production methods and procedures may establish that
The level of the activity: information should be produced within a specified software application. It may also
Project specify how to review information by providing a procedure or a specific workflow to
be followed.
For example, the information production methods and procedures may establish
that additional meta-data relating to a security rating should be applied to all
information containers. It may also specify the common data environment (CDE)
solution to be used for the distribution of information.
For example, the information production methods and procedures may establish
what procedure to follow when delivering information such as whether additional
checks are required or if an additional CDE solution is to be used.
It should be noted that as the information production methods and procedures are
project-specific, some of the established production methods and procedures may not
all apply to all appointed parties.
For example, additional handover procedures may be included within the information
production methods and procedures which are not relevant for an appointment to
produce a concept design.
Remember that the information production methods and procedures are set out at
project rather than appointment level. Its amalgamation with the standard may prove
beneficial as both are project-specific and often used in tandem (unlike the exchange
information requirements, which is an appointment specific resource).
Summary of activities within the clause (as appropriate):
n/a
ISO 19650-2 related clauses:
5.2.1 Establish the appointing party’s exchange information requirements
5.2.4 Compile the invitation to tender information
5.3.2 Establish the delivery team’s (pre-appointment) BIM execution plan
5.6.2 Generate information
5.6.3 Undertake quality assurance check
5.6.4 Review information and approve for sharing
5.6.5 Information model review
5.7.4 Review and accept the information model
5.8.1 Archive the project information model
34 | Guidance Part 2 Edition 6 - February 2021
Parties, teams and processes for the delivery phase of the assets
Clause: 5.1.6 Establish the project’s reference information and shared resources
The primary party active Insight:
within the clause:
The appointing party considers existing reference information and shared resources to
Appointing party support tender of all appointed parties.
Contributing parties to Reference information could be relevant to the overall project, such as Ordnance
the clause: Survey mapping or information relating to adjacent assets and/or utilities owned by
n/a other organizations. Reference information could also be selected information from
When the activity within the existing asset information model, such as low-temperature hot water and chilled
the clause should be water schematics or layouts to be used in an office refurbishment project.
carried out: In addition, reference information may include the information delivered during
Before tendering the first a preceding appointment, usually by a different delivery team. For example,
lead appointed party performance specifications prepared by the appointing party’s design team
appointment for tendering a design and build contract. It is possible for a prospective lead
The level of the activity: appointed party to receive reference information that it produced itself in a previous
Project appointment, for example a masterplan produced by multi-disciplinary practice X
would be reference information for the subsequent design development package that
the same practice is bidding for along with a number of other practices.
Not providing reference information means that prospective lead appointed parties
are likely to either include costs to generate it themselves, or include a risk allowance
in their pricing, or both. Alternatively, in ignorance, they may proceed on the basis
of incomplete reference information which may ultimately impact the quality of
their deliverable, through no fault of their own. These are the kinds of unnecessary
costs and pitfalls that information management according to the ISO 19650 series is
intended to avoid.
Shared resources can take many forms, such as document templates, 3D object
libraries or custom line styles and clause 5.1.6 provides examples.
To provide a practical illustration the client might provide a template for the BIM
execution plan, to be used by all prospective lead appointed parties, to make sure
that this part of each tender submission is structured in the same way and can be
consistently evaluated.
For example: as part of the PIR (see insight clause 5.1.2) one of the purposes for
information is to support the ongoing progression of the project. Within the EIR the
appointing party identifies that the information required is a construction
programme report which summarizes where the programme is ahead/ behind
schedule in PDF format.
For example: from the AIR the appointing party requires asset information for
maintenance purposes which will feed into their facilities management system. For
this they specify in the EIR the exact information required against the relevant
asset(s) which enables it to be imported into their system.
During project delivery each EIR provides the mechanism for reviewing and accepting
information models for the duration of the associated lead appointed party
appointment.
For example: please explain how you will manage and mitigate risk associated with
information delivery?
Ensure use of appointment specific questions that are relevant to the appointment
within the context of the project, and the scope of works to be undertaken by the
delivery team. Evaluation criteria should be measurable.
Clause: 5.3.2 Establish the delivery team’s (pre-appointment) BIM execution plan
See ISO 19650 guidance E to understand more about the BIM execution plan
The primary party active Insight:
within the clause:
The BIM execution plan is defined in ISO 19650-2 clause 3.1.3.1. The (pre-
Prospective lead appointed appointment) BIM execution plan is established by a prospective lead appointed
party party on behalf of the delivery team and is included in their tender response. The
provision of the (pre-appointment) BIM execution plan is a requirement of ISO 19650-
Contributing parties to 2.
the clause:
Clause 5.3.2 identifies seven areas that the prospective lead appointed party should
n/a
consider in establishing their (pre-appointment) BIM execution plan. However, it is
important to understand what the appointing party expects the (pre-appointment)
When the activity within BIM execution plan to contain and to cover this accordingly. Note that the appointing
the clause should be party may have their own BIM execution plan template, which should comply with ISO
carried out: 19650-2. Assuming this is the case, this template should be made available as part of
Any prospective appointed the invitation to tender documentation.
parties that are known at
this time Establishing the (pre-appointment) BIM execution plan should involve collaboration
with prospective appointed parties (anticipated members of the delivery team) where
known, so that it reflects what the delivery team as a whole will do, not simply what
The level of the activity: the lead appointed party will do, or would like prospective appointed parties to do.
Appointment The (pre-appointment) BIM execution plan provides an opportunity for the
prospective lead appointed party to identify additions and/or amendments to the
project’s production methods and procedures and its information standard. This
might be needed so that:
• Information can be effectively generated, reviewed, approved, authorized and
exchanged by the different parties involved, and
• Distribution and delivery of information is secure and effective
Contributing parties to For example: the BIM execution plan’s information delivery strategy identifies the use
the clause: of a specific software package to manage information. Do the members of the task
n/a team have experience in managing their information using this software?
It is important to accurately assess task team capability and capacity and to be able
to provide evidence if necessary.
In addition, while ISO 19650-2 identifies this as a task team activity, task teams can
seek certification as a means of demonstrating capability through an independent
third party.
Contributing parties to
the clause:
Prospective task teams/
appointed parties
The actual list will depend on the specific requirements of the appointment.
Contributing parties to
the clause:
n/a
For example: the detailed responsibility matrix may show that “ABC Architects” is
responsible for providing this information.
Whilst preparing the detailed responsibility matrix, it is important to bear in mind that
the task information delivery plans and master information delivery plan are governed
by the rules set by the matrix, but will be working at an information container
level. However, the detailed responsibility matrix must refer back to the exchange
information requirements received from the appointing party, to be clear how each
requirement is being met.
Summary of activities within the clause (as appropriate):
n/a
ISO 19650-2 related clauses:
5.4.4 Establish the task information delivery plan(s)
5.4.5 Establish the master information delivery plan
51 | Guidance Part 2 Edition 6 - February 2021
Parties, teams and processes for the delivery phase of the assets
Clause: 5.4.3 Establish the lead appointed party’s exchange information requirements
See ISO 19650 guidance D to understand more about information requirements
The primary party active Insight:
within the clause:
The lead appointed party should define a set of exchange information requirements
Lead appointed party (EIR) for each appointment it makes just like the appointing party does (see ISO
19650-2, 5.2.1).
Contributing parties to
the clause: Each EIR should detail the information required by the lead appointed party from
n/a the appointed party. This may include relevant aspects of appointing party’s EIR,
creating a cascade throughout the supply chain. These are detailed requirements and
should be defined around the concept of the level of information need to ensure all
When the activity within
facets of information are captured.
the clause should be
carried out: For example: a tier 1 contractor manages programme and cost; therefore, they may
During completion of the require specific information from certain sub-contractors to enable them to carry out
appointment these tasks.
The level of the activity: In addition, the appointing party may require asset information for maintenance
Appointment purposes which will be delivered by certain sub-contractors.
This information is included within the lead appointed party’s exchange information
requirements and hence the tender information for the relevant sub-contractors.
During project delivery the exchange information requirements provide the mechanism
for the lead appointed party to authorize information models.
Appointed party
There will be times when the intended team members are no longer available when
the appointment starts. This situation needs to be managed, by identifying and
upskilling new team members to take their place. The important aspect is to make
sure that the new team members have equivalent or better skills than those they are
replacing.
This activity should address gaps found in the assessment of task team capacity in
5.3.4 and where necessary will feed in to the next points on developing and delivering
education and training.
Develop and deliver education
The intention of this activity is to develop appointed party knowledge about the
information management resources, required processes and associated obligations.
Develop and deliver training
The intention here is to ensure that individuals are competent (skilled) to generate or
manage information.
Tip: make sure that the time for mobilization confirmed in the mobilization plan
is actually allocated to planning and implementing training. Time required could
include the lead times for training providers/content providers.
Mobilization of resources may not be a one-off activity and will need to be repeated
when new individuals join the delivery team and/or other circumstances change.
A successful outcome of 5.5.1 would be sufficient individuals who are knowledgeable
and competent to generate or manage information.
Any risks generated through this mobilization activity should be recorded in the
delivery team’s risk register.
57 | Guidance Part 2 Edition 6 - February 2021
Parties, teams and processes for the delivery phase of the assets
When the activity The mobilization activity should result in technology being in place, configured and
within the clause should suitably tested to support the generation and exchange of information between all
members of the project team. This is to ensure that information can be confidently
be carried out:
exchanged between members of the delivery team and between the appointed parties
Before any information is and the appointing party.
generated within a task
Mobilization of information technology covers five core activities which are set out in
team.
clause 5.5.2.
The level of the Procure, implement, configure and test software, hardware and IT infrastructure
activity:
Mobilization of information technology is about more than just getting the hardware
Appointment delivered - it also needs the software to be installed and it all needs to be tested. A
further consideration is ensuring that software versions and add-ons do not impact on
interoperability.
It is therefore important to ensure that the right technologies are in place and there is
enough of them (in terms of licensing for example).
Tip: it is crucial that service level agreements and terms and conditions will effectively
support the duration of the appointment (for example, consider the timing of renewal
agreements).
For example, this might include testing delivery team specific work-flow, setting up
access and administration permissions.
Clause: 5.5.3 Test the project’s information production methods and procedures
The primary party Insight:
active within the clause: As noted in the insight to clause 5.5.1, the alignment of an activity with a documented
Lead appointed party process is a common theme throughout the ISO 19650 series. The mobilization
activities should therefore follow the mobilization plan submitted with the delivery
Contributing parties to team’s tender response (see ISO 19650-2 clauses 5.3.5 and 5.3.7).
the clause: Clause 5.5.3 is focussed on ensuring that the methods and procedures for information
Task team(s)/appointed production and exchange are understood by all members of the delivery team and
parties can be implemented from the outset of the information generation activities.
When the activity This will involve testing the project’s information production methods and procedures.
within the clause should For example, testing will include a review of the federation strategy and information
be carried out: container breakdown structure to establish that they remain appropriate. If this is
Before any information is not the case, refinement should be explored to ensure that the information container
generated within a task breakdown structure supports the federation strategy.
team.
For example, testing the visibility of information containers and the information
The level of the within them to ensure that security requirements for the management of sensitive
activity: information can be adhered to.
Appointment In thinking about information production, the lead appointed party may need to
develop shared resources for use by the delivery team.
The final activity within this clause is to ensure that the project’s information
production methods and procedures are cascaded to every task team within the
delivery team.
Although the activities within clause 5.5.3 are assigned to the lead appointed party,
they should be undertaken in a collaborative manner including all delivery team
members.
A successful outcome of 5.5.3 would be assurance that the project’s information
production methods and procedures will support the generation and management of
information.
Any risks generated through this mobilization activity should be recorded in the
delivery team’s risk register.
Summary of activities within the clause (as appropriate):
• Review and test the project’s information production methods and procedures
• Make refinements as required
• Communicate the project’s information production methods and procedures to all task teams
ISO 19650-2 related clauses:
5.1.5 Establish the project’s information production methods and procedures
5.3.5 Establish the delivery team’s mobilization plan
5.3.6 Establish the delivery team’s risk register
5.3.7 Compile the delivery team’s tender response
5.4.7 Complete appointed party’s appointment documents
5.5.1 Mobilize resources
5.5.2 Mobilize information technology
61 | Guidance Part 2 Edition 6 - February 2021
Parties, teams and processes for the delivery phase of the assets
Clause: 5.7.1 Submit information model for lead appointed party authorization
See ISO 19650 guidance C to understand how an information container transitions between states
The primary party active Insight:
within the clause:
This clause is the first step in the process of delivering the information model as an
Task team(s)/appointed information exchange to the appointing party and having it accepted as Published
parties information. Each task team seeks the lead appointed party’s authorization of their
Contributing parties to relevant information containers.
the clause: The process of submission should be in accordance with project’s information
n/a production methods and procedures.
In line with the UK National Annex, the information containers within the information
model would have a status code of S6 or S7 depending on whether the information
When the activity within
exchange is happening before or at Plan of Work stage 6 (Handover) – see BS 8536-1
the clause should be
carried out: for further information about the Plan of Work stages.
At the start of a process of
information exchange with
the appointing party
The level of the activity:
Appointment
For example, if information model delivery is not complete, its output as reference
information for another delivery team will be unreliable.
An information exchange that is just within the delivery team (because the
information model is not being delivered to the appointing party) will be complete
after successful conclusion of this step and will not involve ISO 19650-2 clauses 5.7.3
and 5.7.4.
Summary of activities within the clause (as appropriate):
• Review the exchange information requirements (appointing party and lead appointed party)
• Check the information model
• If the review is successful then move to clause 5.7.3 as appropriate
• If the review is unsuccessful, reject the information model and instruct task teams accordingly
ISO 19650-2 related clauses:
5.4.6 Complete lead appointed party’s appointment documents
5.4.7 Complete appointed party’s appointment documents
5.6.2 Generate information
5.7.1 Submit information model for lead appointed party authorization
5.7.3 Submit information model for appointing party acceptance
68 | Guidance Part 2 Edition 6 - February 2021
Parties, teams and processes for the delivery phase of the assets
For example, if information model delivery is not complete, its output as reference
information for another delivery team will be unreliable.
The published information will then be available as reference information for other
delivery teams. This may then trigger a new appointment process.
The National Annex for ISO 19650-2:2018 has • Lack of agreement on which role codes
been revised and was released in February should be applied to certain originators.
2021 in BS EN ISO 19650-2:2018 & Revised For example, an interior designer (I) is also
NA. This guidance refers to the previous a subcontractor (X) by appointment but
National Annex as the “2018 National Annex” also a specialist designer (Y). So should
a façade contractor have their own code
and the new National Annex as the “2021
like an interior designer or would they be
National Annex”. The need to update the a subcontractor or specialist designer? This
2018 National Annex was based largely upon stemmed from the fact that disciplines
feedback received for how that National and roles were being confused and
Annex did not perform as efficiently as interchanged
expected.
• Uncertainty about what the A1, A2, A3 etc.
A few of the reasons, some of which stem status codes meant in terms of purpose.
back to experience of trying to implement BS
1192:20071, included: These, as well as other reasons, led to the
conclusion that the National Annex must be
• Using terminology (e.g. Volume) from the updated to resolve the confusion caused by
withdrawn 1192 series which was no longer the 2018 National Annex and BS 1192:2007.
defined anywhere
This guidance provides an insight into
• Providing a Field ID for information the changes and their impacts and gives
containers, but not making clear what examples of how the 2021 National Annex
types of information containers it should be
can be applied along with the considerations
applied to (as it did in BS1192:2007)
including those parts that have not changed.
• Lack of agreement (within the user
community) on which “Type” codes to assign
within the Field ID resulting in multiple
codes that could be applied to the same
information container type. This was
because some “Type” codes focussed on
the contents of the information container
whereas others focused on the presentation
or form of the information container
1 BS 1192:2007 Collaborative production of architectural, engineering and construction information. Code of practice
73 | Guidance Part 2 Edition 6 - February 2021
Parties, teams and processes for the delivery phase of the assets
Change
The 2021 National Annex makes it clear that the Field codification described in the
National Annex only applies to files whereas the 2018 National Annex did not make
this distinction. The project’s information standard (developed and maintained by the
appointing party in agreement with lead appointed parties) should define which file
types the Field codification should be applied to.
Justification
The 2018 National Annex was not clear on which information containers this ID applied
to, for example: files, layers, directories, or objects. Clarity was requested as the Field
ID in the 2018 National Annex did not logically suit layers or objects. Information
containers that are layers should refer to BS EN ISO 13567-2 and this is clarified in the
2021 National Annex.
Potential benefits
No negative impact is anticipated unless the 2018 National Annex was applied to
anything other than files.
74 | Guidance Part 2 Edition 6 - February 2021
Parties, teams and processes for the delivery phase of the assets
Change
The 2021 National Annex removes the 2018 National Annex recommended limit on the
field lengths. It does however contain a recommendation that these should be kept as
short as possible. The structure of the information container ID is now guided by the use
of the delimiter as defined by 2021 National Annex clause NA.2.3.
Requirements for field lengths should be defined in the project’s information standard.
Justification
Both BS 1192:2007 and the 2018 National Annex were inconsistent in applying some field
limits but not others, meaning that standardization across industry was still not possible.
In addition, feedback reported that those restrictions made it difficult to apply to some
projects/types in some cases. What was established was that the field length was less
important providing the delimiter was used properly.
Potential benefits
Perceived restrictions imposed by BS 1192:2007 and the 2018 National Annex that some
felt were detrimental to their projects have been withdrawn and appointing parties are
now free to identify the appropriate field lengths for their projects.
Previous field lengths that were based on the 2018 National Annex could be affected
by an appointing party`s decision to change them to suit their personal preference.
Without careful consideration of field lengths by the appointing party there could be
inconsistency across an organization and a project.
If solutions offered by software vendors are rigid and can only accommodate 2018
National Annex requirements then they will now need to accommodate flexibility guided
by the delimiter.
75 | Guidance Part 2 Edition 6 - February 2021
Parties, teams and processes for the delivery phase of the assets
Change
Justification
The restriction of 2-6 characters recommended by BS 1192:2007 and the 2018 National
Annex did not lead to substantive standardization anyway. The restriction has been
removed entirely in the 2021 National Annex.
Potential benefits
There is now more evident flexibility for the appointing party in determining the field
length. This change does not limit any previous approach.
There are no potential negative impacts providing the delimiter is used correctly.
76 | Guidance Part 2 Edition 6 - February 2021
Parties, teams and processes for the delivery phase of the assets
Change
Change of field length – recommended field length restrictions have been removed.
Justification
Originator Code clarification – feedback indicated uncertainty about who the originator
code should be assigned to, with some considering it should be a task team and others
that it should be a lead appointed party. The 2021 National Annex makes it clear that
the originator code represents the organization of the information author identified in a
TIDP (see ISO 19650-2 clause 5.4.4).
Although the lead appointed party is “accountable” for ensuring the timely and complete
production of information as agreed in its MIDP, each appointed party is “responsible”
for generating the information assigned to it. This responsibility, and the agreed
deliverables defined in the TIDP must be contractually agreed as defined in clause
5.4.7 of ISO 19650-2. Note, a single organization can be responsible for managing
information (lead appointed party) and generating information (appointed party) –
refer to ISO 19650 guidance documents 2 and A for examples.
Potential benefits
Change of field length - there is now more evident flexibility for the appointing party in
determining the field length. This change does not limit any previous approach.
Originator Code clarification – there is now clear direction on who the originating code
should be assigned to. The appointing party can also generate an accurate record
of who the information originators were on their project. For example, rather than
recording a lead appointed party (such as a main contractor) as the originator of
all information containers in their control, the originator code will indicate the actual
organization who generated an information container (such as the steelwork fabricator).
Change of field length – there are no potential negative impacts providing the delimiter
is used correctly.
Originator Code clarification - those who have considered the “originator” to be a lead
appointed party or another organization that doesn’t naturally carry out clause 5.4.4 of
ISO 19650-2 may be impacted and may need to reconsider their approach in using this
field.
77 | Guidance Part 2 Edition 6 - February 2021
Parties, teams and processes for the delivery phase of the assets
Change
Change of field Length - recommended field length restrictions have been removed.
Change of field name – the field name has been changed from “Volume/System” to
“Functional Breakdown”.
Justification
Potential benefits
Change of field length - there is now more evident flexibility for the appointing party in
determining the field length. This change does not limit any previous approach.
Change of field name – the new field can be used much more flexibly in comparison
to the superseded “volume/system” field. This means that if users wish they may still
adopt an embedded strategy even though the name has changed. For example, under
the superseded volume/system term users may have split volumes into various packets
of design based on function such as ventilation design, mixed services design or piling
design. This allowed the filtering of information containers based on aspects of the design.
This approach may still be applied to help those trying to find information to understand
the contents. Sometimes however, users may want to split the information containers by
something other than design function.
Those who were unfamiliar with, or did not understand, the term “Volume/system” in BS
1192:2007+A2:2016 and the 2018 National Annex will no longer be exposed to it.
Change of field length – there are no potential negative impacts providing the delimiter is
used correctly.
Change of field name – guidance, literature or training resources that still use “Volume/
system” terminology will require an update. Tools such as document management
platforms that have named column values for this field ID as “Volume/system” will also
need updating. If this cannot be done, this may be mitigated by inserting a clarification
about what this withdrawn term means.
2 S ISO 81346-12:2018 Industrial systems, installations and equipment and industrial products. Structuring principles and
B
reference designations. Construction works and building services
78 | Guidance Part 2 Edition 6 - February 2021
Parties, teams and processes for the delivery phase of the assets
Change
Change of field Length - recommended field length restrictions have been removed.
Change of field name – the new name of “Spatial Breakdown” was introduced to align
to ISO 19650 terminology and to allow for wider scope in infrastructure.
Justification
Change of field name – the BS 1192:2007 and 2018 National Annex label for this
field “Levels/Location” covers two spatial descriptors so the rationale was to simply
call it “Spatial” to represent either. Furthermore, as ISO 19650 makes it clear a spatial
breakdown has to be considered, “Spatial Breakdown” was assigned as a replacement.
Potential benefits
Change of field length - there is now more evident flexibility for the appointing party
in determining the field length. This change does not limit any previous approach.
Change of field name – although the name has changed, a previous use and approach
to this field can be retained if preferred. Spatial breakdowns can go into significant
detail to complement a federation strategy but this degree of detail may not be
needed for the information container ID. What can be achieved with the broader
definition of “Spatial Breakdown”, is the ability to link information containers to more
than just locations and levels, such as sections, elevations, spatial zones or connections
such as risers, secure/unsecure locations, lift shaft, chainage etc.
Change of field length – there are no potential negative impacts providing the
delimiter is used correctly.
Change of field name – guidance, literature or training resources that still use “Levels/
locations” terminology will require an update. Tools such as document management
platforms that have named column values for this field ID as “Levels/locations” will also
need updating. If this cannot be done, this may be mitigated by inserting a clarification
about what this withdrawn term means.
79 | Guidance Part 2 Edition 6 - February 2021
Parties, teams and processes for the delivery phase of the assets
Change
Change of field Length - recommended field length restrictions have been removed.
Justification
In the 2021 National Annex this field only captures the form that the information has
been presented in (in reference to the form codes set out in BS ISO 29845:2011 3). Using
the previous example, the same 3D topographical survey would be recorded as a model
(M). Had the same information been recorded on a drawing (D) or as a list (L) of
coordinates, the form would have changed to reflect this.
This focuses on the form of presentation used rather than content and type, which may
be covered by the classification metadata.
Potential benefits
Change of field length - there is now more evident flexibility for the appointing party in
determining the field length. This change does not limit any previous approach. Note
that even though the standard codes are single characters, the field itself does not have
a length limit.
Change of field`s purpose - this field now allows a project team member to search by
how information has been presented rather than its content, which would be covered by
classification metadata. As the common data environment is intended to aid with the
location and discovery of information, the ability to filter by a smaller set of permitted
values will improve the likelihood of information being found. In addition, the omission
of overlapping descriptions (such as schedule and schedule of accommodation) allows
less ambiguity in the application of this field. This improves the ability to locate relevant
information. As the 2021 National Annex permits the expansion of recommended codes,
an organization’s existing list could be integrated with that included in the 2021 National
Annex, so long as it is recorded within the project’s information standard.
Change of field length – there are no potential negative impacts providing the delimiter
is used correctly.
Change of field`s purpose – this narrowing of codes from the 2018 National Annex to
focus on “Form” may take some getting used to.
In addition, some may find the selection of an appropriate form difficult for deliverables
that potentially use multiple forms of presentation. The 2018 National Annex (clause
NA.3.6 Note 2) recommends that for information containers with complex forms the
principal form is used to define the code. For example:
Note: further examples of how the Form code can be assigned are set out BS ISO
29845.
81 | Guidance Part 2 Edition 6 - February 2021
Parties, teams and processes for the delivery phase of the assets
Change
Change of field Length – recommended field length restrictions have been removed.
Change of field`s purpose – the “Role” field in BS 1192:2007 and the 2018 National
Annex has been changed to identify the “discipline” which an information container
relates to.
Justification
Change of field`s purpose - The role codes in BS 1192:2007 and the 2018 National
Annex had conflicts, mingling between contractual status (such as client, contractor
and sub-contractor) and job title such architect or building surveyor (the particular use
of architect in the list was inappropriate because of its protected status). This created
confusion resulting in examples of a subcontractor being identified by an “X” code
(subcontractor) on one project, on another being assigned “Y” code (specialist designer)
and another again the “M” code (mechanical engineer) when in fact their work is the
same on all three projects and technically all three code assignments are correct.
Note that the discipline code for producing information management resources could
be assigned a discipline code “X” (non-discipline specific or not applicable), “O” (other
discipline), or a two character project-specific code.
Potential benefits
Change of field length - there is now more evident flexibility for the appointing party in
determining the field length. This change does not limit any previous approach.
Change of field`s purpose - The “Discipline” identifier allows improved flexibility for
identifying each information container’s discipline while retaining who produced
the information from the Originating Identifier. In the case of a multi-disciplinary
organization this enables each technical team to be identified separately (for example,
the architecture team (A code), the civil engineering team (C code) and the ground
engineering team (G code). Alternatively, there may be a one to one relationship
between originator and discipline for example, a building surveying organization might
be the only one producing building surveying content (B code).
Change of field Length – there are no potential negative impacts providing the delimiter
is used correctly.
Change of field`s purpose - certain approaches to using the old role field are not
possible with the 2021 National Annex. For example, appointing parties (clients) and
lead appointed parties (such as a main contractor) would have been assigned codes
that no longer apply.
82 | Guidance Part 2 Edition 6 - February 2021
Parties, teams and processes for the delivery phase of the assets
In addition, it was common for main contractors to assign the BS 1192: 2007 and 2018
National Annex role code of subcontractor or specialist designer so they could separate
their consultants from their trade contractors. Now, where there is a broad discipline
code, such as E, electrical engineering, the “Functional Breakdown” code could be used to
identify the sub-divisions of this discipline, such as lighting, low voltage or high voltage
power or data cabling. It is recommended that this be reviewed and standardized clearly
in the project information standard and accompanying information production methods
and procedures.
83 | Guidance Part 2 Edition 6 - February 2021
Parties, teams and processes for the delivery phase of the assets
Change
Justification
Potential benefits
There is now more evident flexibility for the appointing party in determining the field
length. This change does not limit any previous approach.
3.1.10 Status
Change
Addition of a new Shared status code - status code S5 is a new code, specifically aligned
to ISO 19650-2 clause 5.7.3 – appointing party review and acceptance.
Change to Shared status codes – status codes S1, S2, and S3 are now aligned with ISO
19650-2 clause 5.6.5 (information model review) and S4 is aligned with ISO 19650-2
clause 5.7.1 (submit information model for lead appointed party authorization). S4 has
also had its purpose reworded.
Justification
Removal of Shared status codes S6 and S7 - by explicitly aligning the status codes with
ISO 19650-2 activities, user confusion about what to apply when, should be eradicated.
Addition of a new Shared status code S5 - it was recognized that some clients or specific
approval routes may need to have dedicated suitability codes for clauses 5.7.1 and 5.7.3.
New status code S5 was therefore introduced in the 2021 National Annex to distinguish
between the activities of sharing information containers for review and authorization
(S4) and sharing them for review and acceptance (S5).
Although ISO 19650-2 clauses 5.7.1 and 5.7.3 record these tasks as being performed
separately, there might be instances where they are combined into a single activity,
for example where a delivery team contains only one organization that is both lead
appointed party and appointed party.
Change to Shared status code S4 – the introduction of new Shared status code S5,
meant it was possible to refine the previously ambiguous definition of Shared status
code S4 “Stage Approval” by aligning S4 with clause 5.7.1 of ISO 119650-2.
Potential benefits
Removal of Shared status codes S6 and S7 - if these codes were unclear to users before,
then this removal is going to help with adoption of the 2021 National Annex.
Addition of a new Shared status code S5 - uncertainty about when to use Shared status
code S4 in regards to clause 5.7.1 and 5.7.3 of ISO 19650-2 is now removed as S4 is
complimented with S5. The different steps in the information review process can now be
clearly distinguished through these separate Shared status codes.
Change to Shared status code S4 – as noted above, uncertainty about when to use
Shared status code S4 is now removed.
Generally: any previous processes, guidance or training that referred to the Shared
status codes in BS 1192: 2007+A2:2016 or the 2018 National Annex will need revising to
reflect the 2021 National Annex.
85 | Guidance Part 2 Edition 6 - February 2021
Parties, teams and processes for the delivery phase of the assets
Change
Clarification of Published status codes A1, An etc. – the 2021 National Annex now
provides distinction between authorization and acceptance (these are separate activities
within the ISO 19650-2 process). Note 2 has been added to clarify that Published
status codes do not imply particular reasons for issuing information and these should be
explained in the project’s information standard.
The B codes are now deprecated (which means that people are strongly advised not to
use them).
Justification
Removal of Published status code CR – this status code was duplicating one of the A
status codes.
Clarification of published status codes A1, An etc. - The A codes introduced in the
2018 National Annex were more nuanced than the A code of BS 1192:2007. This was
to reflect the increased complexity of the information management process. The
2021 National Annex provides a more general approach to support authorization or
acceptance of information containers at any point in the project life-cycle, not just at
handover from design to construction. Neither BS 1192:2007+A2:2016 nor the 2018
National Annex provided a suitable solution for this approach.
The 2021 National Annex clarifies that the purpose for issuing a Published information
container should be documented in the project’s information standard, alongside each
An status code, for example:
• A4 = Authorized and Accepted as suitable for construction (if using the RIBA 2020
stage outcome definition for stage 4 which defines a stage 4 completed deliverable
as construction ready)
• A5 = Authorized and accepted as suitable as a construction record (if using the RIBA
2020 stage outcome definition for stage 5).
Now, if a user wants to know if the drawing they have is for construction or not, they
would refer to the assigned status code and the project information standard defines.
Note that the default definition of project stages for the 2021 National Annex is as per
BS 8536 4 and although an alternative can be used (the RIBA plan of work, CIC, APM,
GRIP, PCF), the stage outputs must be defined in the project’s information standard
explaining exactly what each code represents in terms of what uses or purposes its
suitable for by the recipients.
4 BS 8536-1:2015 Briefing for design and construction - Part 1: Code of practice for facilities management (Buildings
infrastructure)
86 | Guidance Part 2 Edition 6 - February 2021
Parties, teams and processes for the delivery phase of the assets
Potential benefits
Removal of Published status code CR – there is no longer any duplication with the A1-An
codes meaning an An code can be used to reflect final issue information containers.
Clarification of the Published status codes A1-An - uncertainty about when to use the
Published status codes is now removed providing that these are properly documented in
the project’s information standard.
Generally: any process, guidance or training that referred to the Published status codes
in BS 1192: 2007+A2:2016 or the 2018 National Annex will need revising to reflect the
2021 National Annex.
87 | Guidance Part 2 Edition 6 - February 2021
Parties, teams and processes for the delivery phase of the assets
3.1.11 Classification
Change
The requirement for the CDE to enable each information container to be assigned
classification as metadata has not changed, nor has the requirement for information
containers to be classified in accordance with Uniclass 2015 as the UK implementation
of ISO 12006-2:2018. However, 2021 National Annex clause NA4.4 now provides
direction that the Uniclass 2015 PM table should be used where possible as the source for
classification metadata.
Justification
The Uniclass 2015 PM table has been developed to classify information container content
and is therefore a suitable and manageable reference point.
Potential benefits
1. S
election of classification metadata is more straightforward because there is direction
to a specific Uniclass 2015 table rather than to the entire Uniclass 2015 system
2. The convention for information container classification becomes consistent across
multiple delivery teams and across multiple projects
3. Information container classification becomes predictable and logical. Reliance on
free text descriptions to identify information can be reduced
4. Information deliverables can be aligned across information planning resources and
with EIR. This provides a mechanism for automating the verification of information
deliverables.
The adoption of any classification system is not without its complications; a classification
system is never complete and is always in development. The contents of the PM table
may change throughout the life of an appointment or a project. It is therefore important
for the appointing party (client) to record the status and revision date of the version of
the PM table to be used in the project’s information standard and to take a considered
review before implementing any subsequently updated versions.
Where an information container includes mixed information (for example, a business case
containing cost models) a higher level of the PM table hierarchy could be used – in this
case PM_50_30 Economic viability information.
As it is an appointment resource, any changes to the project’s information standard would
need to be agreed with parties already appointed.
88 | Guidance Part 2 Edition 6 - February 2021
Parties, teams and processes for the delivery phase of the assets
3.2 A
pplying the 2021 National The 2021 National Annex provides an
appointing party with a standardized
Annex approach for how the information container
unique ID and metadata assignments should
Guidance explaining how to apply the 2021 be approached. At this stage, the appointing
National Annex throughout the whole delivery party need only define in their project
phase will be released in the next edition information standard that the unique ID and
of ISO 19650 guidance 2. We would like to metadata conform to “BS EN ISO 19650-
invite you to propose situations or scenarios 2:2018 & Revised NA” and then specify any
that you would like us to address in the next project particulars including:
edition – please let us have these by emailing
[email protected] • T
he project code. This should be defined
noting that it must be used by all
3.2.1 A
pplication guidance for
assessment and need • A
ny known organizations. Each should
have an assigned originator code
This section of guidance relates to a client
• If Functional Breakdown has been
body as an appointing party. Information is
considered before any appointed parties
exchanged between the appointing party and
are engaged, then this should be explained
appointed parties either way, as file-based
and relevant codes assigned. If not, clarify
information containers.
“XX” should be used
At the very earliest stages of a project very
• If Spatial Breakdown has been considered
little will be known about the information that
before any appointed parties are engaged,
will be produced and exchanged throughout
then this should be explained and relevant
the project. But somethings need to be
codes assigned. If not, clarify “XX” should
considered, even before any appointments
be used
are made and design has taken place. The
appointing party should consider how they will • A
ny additions the appointing party
want information to be stored, exchanged and wishes to make to the Form and Discipline
retrieved, including in the strategic stage of a codes should be recorded. If not, then
project. Even at this stage, there will be some a note stating no changes apply or just
information to manage. These considerations referencing the annex will suffice
could then be defined as part of the
information standard and the information • The length of the Number field.
production methods and procedures as
defined by ISO 19650-2 clause 5.1.4 and
clause 5.1.5 (see ISO 19650 Guidance E). Any
requirements detailed in these resources (such
as the information container unique ID and
assigned metadata) must then be supported
through the implementation of the common
data environment workflows and technical
solutions (see ISO 19650-2 clause 5.1.7).
89 | Guidance Part 2 Edition 6 - February 2021
Parties, teams and processes for the delivery phase of the assets
3.2.2 A
pplication guidance for the
remainder of the delivery phase
Key:
Activity to be undertaken
Decision point
Information exchange
Sequence flow
New appointment
Invitation to Tender
(19650-2 clause 5.2) 5.2.1
(Creating information 5.2.2 5.2.3
for tender (for a
5.2.4 Invitation to
prospective lead tender
appointed party))
Tender Response
(19650-2 clause 5.3) 5.3.1
(Prospective lead 5.3.2
appointed party
tender submission 5.3.4 Selection 5.3.3
process) 5.3.5 5.3.6
5.3.7
Tender response
Selection
Appointment
(19650-2 clause 5.4) 5.4.1 5.4.1 5.4.1
(Finalization and 5.4.2
confirmation of 5.4.3
appointments)
5.4.5 5.4.4
5.4.6 5.4.7
Appointment executed Appointment executed
Mobilization
(19650-2 clause 5.5) 5.5.1 5.5.1
(Getting the delivery 5.5.2 5.5.2 5.5.2
team ready to go)
5.5.3 5.5.3
Collaborative
Production of 5.6.1
Information 5.6.2
(19650-2 clause 5.6) Information Information
model rejected model rejected 5.6.3
(Work in progress and Shared
shared information) information
5.6.5 5.6.4
5.6.5
Next Information iteration
Information
Information Model Information for
publishing Milestone
Delivery
5.7.2 5.7.1
(19650-2 clause 5.7)
Information for
(Checking of publishing
information for 5.7.4 5.7.3
publishing at an
information milestone) End of milestone
Project Close-Out
(19650-2 clause 5.8) 5.8.1 5.8.2 5.8.2
(End of project)
End of project
92 | Guidance Part 2 Edition 6 - February 2021
Parties, teams and processes for the delivery phase of the assets
Appointing party
New Project
5.1.1
Appoint individuals to
undertake the information
management function
5.1.2 5.1.3
Establish the project’s Establish the project’s
information requirements information delivering
milestones
5.1.7 5.1.8
Establish the project’s Establish the project’s
common data environment information protocol
93 | Guidance Part 2 Edition 6 - February 2021
Parties, teams and processes for the delivery phase of the assets
Appointing party
New appointment
5.2.1
Establish the appointing
party’s exchange
information requirements
5.2.2 5.2.3
Assemble reference Establish tender response
information and shared requirements and
resources evaluation criteria
5.2.4
Compile invitation to tender
information
Invitation
to tender
94 | Guidance Part 2 Edition 6 - February 2021
Parties, teams and processes for the delivery phase of the assets
5.3.1
Nominate individuals
to undertake
the information
management function
5.3.2
Establish the
delivery team’s (pre-
appointment) BIM
execution plan
5.3.4 5.3.3
Establish the delivery Assess each task
team’s capability and Selection
team capability and
capacity capacity
5.3.5 5.3.6
Establish the delivery Establish the
team’s mobilization delivery team’s risk
plan register
5.3.7
Compile the delivery
team’s tender response
Tender
response
Selection
95 | Guidance Part 2 Edition 6 - February 2021
Parties, teams and processes for the delivery phase of the assets
5.4.2
Establish the delivery
team’s detailed
responsibility matrix
5.4.3
Establish the lead
appointed party’s
exchange information
requirements
5.4.5 5.4.4
Establish the master Establish the task
information delivery plan information delivery plans
5.4.6 5.4.7
Complete lead appointed Complete appointed
party’s appointment party’s appointment
documents documents
5.5.1 5.5.1
Mobilize resources Mobilize resources
5.5.3 5.5.3
Test the project’s Test the project’s
information information
production methods production methods
and procedures and procedures
97 | Guidance Part 2 Edition 6 - February 2021
Parties, teams and processes for the delivery phase of the assets
5.6.1
Check availability of
reference information and
Unsuccessful review
shared resources
5.6.2
Generate information
Unsuccessful check
5.6.3
Undertake
quality assurance
check
Shared
information 5.6.4
5.6.5
Information model Review information
review and approve for
sharing
5.6.5
Information model
review
Information
Milestone
Information model rejected
Information
5.7.2 for publishing 5.7.1
Review Submit information
and authorize the model for lead
information appointed party
model authorization
Information
5.7.4 for publishing 5.7.3
Review Submit information
and accept the model for appointing
information
party acceptance
model
End of milestone
99 | Guidance Part 2 Edition 6 - February 2021
Parties, teams and processes for the delivery phase of the assets
End of
project
100 | Guidance Part 2 Edition 6 - February 2021
Parties, teams and processes for the delivery phase of the assets
5.0 Summary
The Centre for Digital Built Britain is part of the Construction Innovation Hub programme,
funded by UK Research and Innovation through the Industrial Strategy Challenge Fund.