Designing Buildings - User contributions [en]

Construction knowledge task group

2022-07-25T09:16:32Z

Cohesive:

{|
| [[File:Cktg_Logo_3.png|link=https://sibforms.com/serve/MUIEACZjn4ykPxvXB_aAARqdx81JikcgdUvYTgzaSYPCahcblJ5NEy0e1o6BpvrzykvlAljibX8XXT-vMvNudjZhir30brip95QU8BGOCdZj12yFMfZ-uFNvkJVj755q9WlDhcmLFjocxxP1JFCJAmLpg-M_Kv8hEY21RkL_Mep92fEwWYwlbMAOUkFIwO4yYb19su_gFplZwXPe]]
|}

The construction industry is not maximising the value it extracts from its knowledge, and so it is less productive, less innovative and more likely to make mistakes than it should be.

Whilst industry data and information have entered the digital age with the development of Building Information Modelling (BIM), the internet of things and digital twins, construction knowledge remains firmly in the past. It is unstructured, fragmented, inaccessible and largely in dumb formats - essentially digital versions of paper documents. To use the analogy of BIM maturity levels, this is the equivalent of BIM level 1 - when CAD simply produced digital versions of paper drawings that were difficult to collaborate on and hard to find, compile, manage and update.

{|
| [[File:Jigsaw_large_2.png|link=File:Jigsaw_large_2.png]]
|}

The Construction Knowledge Task Group (CKTG) includes representatives of institutes, associations and the wider industry. Its purpose is to optimise the creation and dissemination of documented, practical, applicable knowledge that enhances productivity and supports compliance by making it as easy as possible for practitioners and other industry stakeholders to:

* Find the right knowledge when it is needed.
* Access that knowledge.
* Extract the maximum value from that knowledge.

To deliver this vision, the CKTG has developed an industry standard for construction knowledge, '[[Specification_for_Discoverable_Construction_Knowledge|The Specification for Discoverable Construction Knowledge]]', that will allow knowledge producers to achieve Level 2a of the smart knowledge routemap.

[[File:CK_maturity_v5a.jpg|link=File:CK_maturity_v5a.jpg]]This is the first industry-wide standard to make construction knowledge more discoverable. It will help practitioners find the knowledge they need when they need it, making it easier for them to keep up-to-date, follow best practice, adopt innovations and comply with standards.

The next step is to develop a proof of concept tool that demonstrates the potential of the standard in enabling rapid searching, filtering and management of construction knowledge from multiple sources with single queries, and the potential for integrating knowledge into project workflows alongside data and information.

You can contact the CKTG by emailing [mailto:info@designingbuildings.co.uk info@designingbuildings.co.uk].

Or [https://sibforms.com/serve/MUIEACZjn4ykPxvXB_aAARqdx81JikcgdUvYTgzaSYPCahcblJ5NEy0e1o6BpvrzykvlAljibX8XXT-vMvNudjZhir30brip95QU8BGOCdZj12yFMfZ-uFNvkJVj755q9WlDhcmLFjocxxP1JFCJAmLpg-M_Kv8hEY21RkL_Mep92fEwWYwlbMAOUkFIwO4yYb19su_gFplZwXPe sign up for the CKTG newsletter].

= CKTG meetings (most recent first) =

* The fifth meeting of the CKTG Tools Working Group was held on 6 July 2021.
* The fourth workshop of the Construction Knowledge Tools Working Group was held on 18 March 2021. [https://www.designingbuildings.co.uk/w/images/8/8c/CKTG_Tools_meeting_4_notes.pdf See notes].
* The third workshop of the Construction Knowledge Tools Working Group was held on 11 February 2021.
* The second workshop of the Construction Knowledge Tools Working Group was held on 7 January 2021.
* The first workshop of the Construction Knowledge Tools Working Group was held on 30 November 2020. [https://www.designingbuildings.co.uk/w/images/2/23/Construction_tools_workshop_1_notes_30_November_2020.pdf See notes].
* A full meeting of the CKTG was held online on 25 September 2020 to agree the next steps. [https://youtu.be/TPQiBs4CimE See a recording of the meeting].
* A workshop to agree the draft standard was held on 30 July 2020. See [https://docs.google.com/presentation/d/1m2ch2HDe81YPWmKDKF-H2Zk-AnfalbgkGb3vCOxmc9U/edit#slide=id.g5da29ae773_0_73 slides] and [https://www.youtube.com/watch?v=zKPkClRd9gI recording].
* Two workshops were held on 23 July 2020.
* An online workshop was held on 3 June 2020 to develop the draft standard.
* An online workshop was held on 21 May 2020 to develop the draft standard.
* An online workshop was held on 22 April 2020 to discuss the draft schema for construction knowledge developed by Barbal.
* An online workshop was held on 24 March 2020 to update members on the work of Barbal in drafting a knowledge standard.
* A kickoff workshop was held on 13 February 2020 at the London offices of Pearson to begin the process of agreeing a classification system for construction knowledge. The workshop was facilitated by Barbal who have obtained funding from the Lloyds Register Foundation with the support of the Open Data Institute. [https://app.standardsrepo.com/CKTG/MakingConstructionKnowledgeDiscoverable/wiki/13%2F02%2F2020-Kick-Off-Workshop Notes of the workshop are available here].
* The fourth meeting of the CKTG took place on 12 December 2019 at the London offices of CIOB. The CKTG Vision and Routemap were adopted, and it was agreed that a workgroup would be established to deliver level 2a. The possibility of undertaking a pilot project to assess the practical benefits of level 3 was discussed.
* The third meeting of the CKTG took place at the offices of RSHP in the Leadenhall Buildings in London on 1 July 2019. The CKTG Project Initiation Document and Memorandum of Understanding were adopted, and feedback was heard from the three workstreams.
* The second meeting of the of the CKTG took place on Thursday 17 January 2019 in the offices of Cundall. The meeting agreed that three workstreams would be created to scope knowledge indexing, knowledge searching and access to knowledge.
* The first meeting of the CKTG took place on Friday 28 September 2018 in the London Offices of CIOB during which it was agreed to undertake an industry-wide survey about knowledge use in the UK construction industry (see below for results).
* On 9 May 2018 an industry-wide meeting was held at the offices of Buro Happold in London to establish the level of support for creating a Construction Knowledge Task Group.

= CKTG resources =

* [https://www.buzzsprout.com/1788151/9739063 Own the build podcast]. Gregor Harvie talking about the task group. 20 December 2021.
* [https://www.youtube.com/watch?v=IFXBGT26PiI YouTube video of Tom Bartley talking about the task group]. 26 March 2021
* [https://www.youtube.com/watch?v=QhGXj_BdlX0 YouTube video of Gregor Harvie talking about the task group]. 26 March 2021
* [[How_to_apply_the_Specification_for_Discoverable_Construction_Knowledge_to_web_pages|How to apply the Specification for Discoverable Construction Knowledge to web pages]]. 27 August 2020
* [[Construction_knowledge_comes_out_of_the_dark_ages|Construction knowledge comes out of the dark ages]]. Press release 27 August 2020
* [[Discoverable_construction_knowledge_specification|About the Discoverable Construction Knowledge specification]]. 27 August 2020
* [[Specification_for_Discoverable_Construction_Knowledge|Specification for Discoverable Construction Knowledge]]. 31 July 2020
* [[An_interoperable_construction_industry|An interoperable construction industry]]. Article. 2 July 2020
* [[CKTG_press_coverage|CKTG press coverage]].
* [https://app.standardsrepo.com/CKTG/MakingConstructionKnowledgeDiscoverable/wiki/4.-Minutes%2C-Notes-and-Updates Notes and recordings of workshops held to develop the construction knowledge standard].
* [https://www.youtube.com/watch?v=KXDRuVnJ4v0&t=2s Tom Bartley talks about the CKTG to the Open Data Institute]. 10 July 2020
* [https://addons.mozilla.org/en-GB/firefox/addon/designing-buildings-anywhere/ Trial knowledge lookup add-on for Firefox]. 31 March 2020
* [http://sh1.sendinblue.com/2n42f9et1t7e.html?t=1583512558 Newsletter]. 3 March 2020
* [https://www.designingbuildings.co.uk/w/images/7/7c/CKGT_vision_v3.pdf Vison and routemap]. 12 December 2019
* [http://sh1.sendinblue.com/2lcuv9et1t7e.html?t=1583512558 Newsletter]. 11 July 2019.
* [https://www.designingbuildings.co.uk/w/images/7/71/CKTG_MoU.pdf Memorandum of Understanding]. 18 April 2019
* [[Construction_knowledge_survey_results|Construction Knowledge Survey results in full]]. 10 January 2019.
* [[Construction_Knowledge_Task_Group_survey|Construction Knowledge Survey results]]. Press release. 10 January 2019.
* [[Construction_knowledge_survey|Construction Knowledge Survey launch]]. Press release. 1 November 2018.
* [[Knowledge_gap_survey_responses|Knowledge gap survey responses]]. 28 May 2018.
* [[Construction_knowledge_gap_meeting|Construction knowledge gap meeting]]. 9 May 2018.
* [https://cse.google.com/cse?q=+&cx=000396381348080777119:q-qnl9coikq Example industry search engine]. May 2018.
* [[Is_Welsh_timber_suitable_for_use_in_construction%3F|An example RESEARCH FINDINGS article]]. March 2018
* [[Research_findings_dissemination_template|Research findings dissemination template]]. March 2018.
* [[Fit_for_Purpose_launch_event|Fit for Purpose launch event]]. 21 September 2017.
* [[Fit_for_purpose_-_Big_data_reveals_the_construction_knowledge_gap|Fit for purpose - Big data reveals the construction knowledge gap]]. 21 September 2017.
* [[Reports_calling_for_better_construction_industry_knowledge|Reports calling for better construction industry knowledge]]. Live document.
* [[Construction_knowledge_sources|Construction knowledge sources]]. Live document.

= Participants =

Organisations involved in the CKTG include:

* AEC3 UK
* AHMM
* Arup
* Barbal
* BRE
* BSi
* BSRIA
* CIAT
* CIBSE
* CIOB
* Cohesive
* Constructing Excellence
* Construction Leadership Council
* Cundall
* Designing Buildings Wiki
* Geniut Group plc
* Hoare Lea LLP
* i3P / KTN
* ICE
* IHS Markit
* Invennt
* Loughborough University.
* Mace
* National Physical Laboratory
* NBS
* Nottingham University
* Pearson UK Ltd
* RIBA
* Royal Institution of Chartered Surveyors
* Rider Levett Bucknall
* SRM
* Stride Treglown
* Stroma
* Taylor & Francis Group
* The Get It Right Initiative
* UKGBC
* University of Dundee
* Workman

[[Category:DCN_Definition]] [[Category:DCN_Guidance]] [[Category:DCN_Organisation]] [[Category:DCN_Research,_Development_and_Innovation]] [[Category:DCN_Standard]] [[Category:Do_not_autolink]] [[Category:Organisations]] [[Category:Publications_/_reports]] [[Category:Research_/_Innovation]] [[Category:Standards_/_measurements]]

Asset information requirements AIR

2022-07-25T09:15:23Z

Cohesive:

= Introduction =

Asset Information Requirements (AIR) define the information required to operate and maintain a built asset in line with an organisation’s asset management strategy.

= Definition =

Asset Information Requirements (AIR) are part of the Building Information Modelling (BIM) process, defining the graphical and non-graphical data, information and documentation needed for the lifetime operation and management of a built asset.

ISO 19650 defines AIR as 'information requirements in relation to the operation of an asset'; an information requirement is defined as 'specification for what, when, how and for whom information is to be produced'.

PAS 1192 defines AIR as 'data and information requirements of the organisation in relation to the asset(s) it is responsible for' (PAS 1192-3).

= Description =

The efficient delivery and operation of a built asset relies partly on the operators’ ability to make sure the right people have access to the right information, in the right format and at the right time in order to make well-informed decisions and to effectively operate the asset.

In the BIM process, these information needs are called asset information requirements: the information required to operate and maintain a built asset throughout its lifecycle. The information will be about the real-world built asset (i.e. what was actually built, not what was planned).

The asset information requirements will be formally and explicitly defined in a document called the Asset Information Requirements (AIR). This document will define the requirements for the provision and management of information about a built asset in line with the organisation’s wider asset management plan, as defined in the Organisational Information Requirements (OIR).

Asset information requirements, once defined, will help enable the creation of an Asset Information Model (AIM). The data and information collated in response to the AIR comprises the AIM, which will therefore contain all the information required by the asset management plan in the required format for the lifetime operation and maintenance of the asset.

The responsibility to provide data and information to respond to the AIR is likely to be distributed across both the asset owner and/or operator and their supply chain.

The AIR should cover the entire asset lifecycle. As such, the AIR informs the development of the Exchange Information Requirements (EIR (ISO 19650)), or Employer’s Information Requirements (EIR (BS/PAS 1192)), for a capital project.

Trigger events (defined in PAS 1192-3:2014 as a “planned or unplanned event that changes an asset or its status”) often necessitate the assessment of the AIR and when the AIM needs to be updated.

PAS 1192-3 gives further information on how AIR should be used:

“…AIR shall be specified as part of a contract or as an instruction to in-house teams and may use data and information from the AIM relating to the asset management activities being carried out. The AIR shall also specify data and information to be captured and fed into the AIM. Where the activities relate to major works covered by PAS 1192-2, then the AIR will inform the EIR.”

This paragraph instructs that AIR:

* Should be specific to an asset;
* Should be included as part of a contract or delivered as an instruction to in-house teams;
* Will inform the information requirements defined in the EIR, where the asset activities relate to major works covered by PAS 1192-2;
* Will specify data and information that will be captured and added to the AIM; and
* May include information about the asset management activities and strategies being carried out using the AIM.

== Development ==

The AIR should define what information will be required to operate and maintain the asset throughout its lifecycle. These information requirements can be extremely broad and comprehensive. They will inform the contents of both the AIM and the EIR document.

When first writing an AIR, PAS 1192-3 suggests that “the AIR may start as descriptive text”, outlining or summarising the scope of the asset information requirements to be defined.

However, the final document should be very precise and exact. PAS 1192-3 continues on to say that the AIR “should then be developed into a digital plan of deliverables.” This means that the AIR should not only define what information is required, but also how that information should be delivered in order to be used in the operation and maintenance of the asset.

Creating an AIR is a task of considerable scale, and PAS 1192-3 warns that “the effort to complete this should not be underestimated.”

== Contents ==

According to ISO 19650, AIR set out three aspects of asset information:

* Managerial: Defines the information standards and production methods and procedures to be used by the delivery team.
* Commercial: Defines the information standards and production methods and procedures to be used by the delivery team.
* Technical: Details the information specifications to meet the organisational information requirements relevant to the asset.

The following are examples of possible asset information requirements from PAS 1192-3, based on guidance in PAS 55-2:2008 and BS 8587:2012:

{|
|width="50%"| Type of Information
|width="50%"| Examples of Information
|-
| Managerial
|
* Type of asset
* Photograph
* Identification numbers (specification number, product number, serial number)
* Location
* Floor area
* Warranties and guarantee periods
* Access planning and work schedules
* Maintenance and inspection schedules
* Outstanding tasks
* Record of planned and unplanned maintenance
* Standards, processes and procedures
* Hazardous contents or waste
* End of life processes
* Emergency plans
|-
| Commercial
|
* Description
* Function
* Details of supplier
* Lead time
* Condition
* Key performance indicators
* Performance targets or standards
* Non-conformance criteria and actions to be taken
* Criticality to the organisation
* Details of spares
|-
| Technical
|
* Engineering data
* Design parameters
* Interdependencies
* Commissioning dates and data
* Operational data
* Finishes
* Services requirements
* Outputs
|-
| Financial
|
* Original cost
* Operating cost
* Planned maintenance cost
* Historical maintenance cost
* Replacement value
* Downtime impact
|-
| Legal
|
* Ownership
* Maintenance demarcation
* Work instructions
* Contractual information
* Risk assessments and control measures
|}

ISO 19650 also states that trigger events during asset operation should prompt a new set of AIR, and that AIR should refer to security requirements where appropriate.

In defining the AIR, the asset owner and/or operator needs to specify the information-sharing protocols and the information and systems to be deployed. On a capital project, these protocols are prescribed in the EIR. During the operation and maintenance of assets, these protocols should be documented in the Asset Management Plans.

= Standards =

The key standards regarding the creation and use of Asset Information Requirements (AIR) are:

* ISO 19560-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
* PAS 1192-3:2014 Specification for information management for the operational phase of assets using building information modelling
* ISO 55000:2014 Asset management – Overview, principles and terminology
* BS 8536-1:2015 Code of practice for facilities management (Buildings infrastructure)
* BS 8536-2:2016 Design and construction: Code of practice for asset management (Linear and geographical infrastructure)

= Relationships to other parts of the BIM process =

The diagram below shows how the AIR is related to other key parts of the BIM process:

[[File:PCSG-20_Relationship_between_Information_Requirements_and_Information_Models.png|link=File:PCSG-20_Relationship_between_Information_Requirements_and_Information_Models.png]]

== AIR and Organisational Information Requirements (OIR) ==

An asset management strategy should be defined at an organisational level, rather than on an asset-by-asset basis. Asset Information Requirements (AIR) should therefore be developed from organisational information requirements. As with asset information requirements, organisational information requirements are defined in a document entitled Organisational Information Requirements (OIR).

An OIR will describe the information required by an organisation’s asset management systems and other organisational functions. OIRs are therefore not specific to any one project or asset.

According to ISO 19650, the OIR provides the input to the AIR (i.e. is the only source of input to the AIR).

== AIR and Asset Information Model (AIM) ==

The information required to create an Asset Information Model (AIM) is defined in the Asset Information Requirements (AIR).

According to ISO 19650, the AIR determines the content, structure and methodology of the AIM.

The information added to an AIM can come from different sources: existing asset information systems, new information (e.g. if upgrades are made to the existing asset), or information in a Project Information Model (PIM) that was created for the construction of a new asset or the modification of an existing asset.

In the case of a new asset, the AIR will have been used to develop the Exchange/Employer’s Information Requirements (EIR). These will have been incorporated into the tender documentation for the project and used to define the delivery of the asset information.

== AIR and Exchange/Employer’s Information Requirements (EIR) ==

The Exchange Information Requirements (EIR (ISO 19650)), or Employer’s Information Requirements (EIR (BS/PAS 1192)), is the document used to communicate the organisational and asset information requirements (OIR & AIR) to the contractor(s) and subcontractor(s) employed on a project.

Therefore, asset information requirements identified by the OIR and defined in the AIR will be used to create the EIR.

According to ISO 19650, the AIR provides an input to the EIR (i.e. it is not the only input).

== AIR and Asset Management Strategy ==

The diagram below shows the relationship between the AIR, OIR, and AIM in the wider context of an organisation’s asset management plan. (Extract from Figure 5 of PAS 1192-3.)

[[File:PAS_1192-3-2014_Figure_5_-_High-level_asset_information_process_map.png|link=File:PAS_1192-3-2014_Figure_5_-_High-level_asset_information_process_map.png]]

-----
--[[User:Cohesive|Cohesive]]

= Related articles =

* Asset information model.
* BIM.
* COBie.
* Creating an asset register for construction projects.
* Employer’s Information Requirements.
* Information management process.
* Information requirements.
* Organisational Information Requirements.
* PAS 1192-3.
* Project information model.

= External resources =

* ISO 19650-1
* ISO 55000
* BS 8536 parts 1 and 2
* UK Government BIM Working Group, CDE Sub Group: Asset Information Management - Common Data Environment (Functional Requirements) ([https://www.cdbb.cam.ac.uk/news/2018AugCDE https://www.cdbb.cam.ac.uk/news/2018AugCDE])

[[Category:DCN_Definition]] [[Category:DCN_Guidance]] [[Category:DCN_Standard]] [[Category:Client_procedures]] [[Category:Design]] [[Category:BIM]]

7: In use

2022-07-25T09:14:08Z

Cohesive:

6: Handover and close out

2022-07-25T09:13:53Z

Cohesive:

5: Construction

2022-07-25T09:13:36Z

Cohesive:

{|
| [[File:Home_icon_grey.jpg|link=Step-by-step_guide_to_using_BIM_on_projects]]
| [[File:0a_icon_not_bold.jpg|link=0a:_Strategic_definition_(business_justification)]]
| [[File:0b_icon_not_bold.jpg|link=0b:_Strategic_definition_(strategic_brief)]]
| [[File:1a_icon_not_bold.jpg|link=1a:_Preparation_and_brief_(appraisals)]]
| [[File:1b_icon_not_bold.jpg|link=1b:_Preparation_and_brief_(brief_and_information_requirements)]]
| [[File:1c_icon_not_bold.jpg|link=1c:_Preparation_and_brief_(supplier_appointments)]]
| [[File:2_icon_not_bold_v2.jpg|link=2:_Concept_design]]
| [[File:3_icon_not_bold.jpg|link=3:_Developed_design]]
| [[File:4_icon_not_bold.jpg|link=4:_Technical_design]]
| [[File:5_icon_solid.jpg|link=5:_Construction]]
| [[File:6_icon_not_bold.jpg|link=6:_Handover_and_close_out]]
| [[File:7_icon_not_bold.jpg|link=7:_In_use]]
|}

The construction stage (sometimes referred to as 'build and commission') may include both on-site construction and off-site manufacturing, along with activities necessary to prepare for occupation.

If the employer will be responsible for operating the development once completed, an in-house or outsourced team should be appointed to witness testing and commissioning, ready to take over the running of services once practical completion is certified. If they have not already done so, the employer may also wish to appoint site inspectors.

The word ‘contractor’ is used in this stage to describe the supplier that constructs the development. If an integrated supply team has been appointed to design and construct (and perhaps operate) the development then they will be the contractor.

Contract administration tasks (such as certifying payments) are attributed to a contract administrator. Under some forms of procurement they will work for the employer, however, on private finance initiative (PFI) projects, the body funding the integrated supply team may appoint the contract administrator.

-----
Employer’s information requirements and master information delivery plan

-----
If they have just been appointed, the successful contractor submits a post-contract BIM execution plan (BEP) confirming their (and their supply chain’s) capabilities and providing a master information delivery plan (MIDP). This should take into account existing BIM execution plans from suppliers already appointed (such as design consultants), and may include BIM training requirements for the contractor and their supply chain.

The employer’s information requirements and consequently the master information delivery plan should be reviewed and revised, focussing upon the information required to manufacture and procure the equipment and building parts that are installed and built.

-----
Mobilisation

-----
The contractor may need to establish or prepare information such as:

* Schedules of conditions of existing and neighbouring structures.
* A master programme for the construction works.
* A project handbook setting out responsibilities, procedures, and lines of communication for the construction stage.
* A site layout plan for construction.
* A contract register.
* An asset register scheduling assets on site and who they belong to.
* Statutory site registers.
* Any further survey work required.
* Statutory utilities information.
* A construction phase plan.
* A site waste management plan (if required).

This information should be prepared in a way that is consistent with the requirements set out in the employer's information requirements.

Any outstanding performance specified work should be completed and any remaining generic objects replaced with manufacturers' objects, re-linked to associated information.

The project information model might be linked to a project management scheduling tool. It may include; method statements, visualisations of potentially hazardous activities, delivery scheduling, formwork sequencing, traffic diversions and so on.

-----
Construction

-----
The contractor proceeds with constructing the works.

The project information model may be used for activities such as:

* Manufacturing processes.
* Providing access to information on site.
* Site induction and safety briefing.
* Improving familiarity with construction tasks.
* Planning construction sequencing and site logistics.
* Tracking progress.
* Capturing as-installed and other record information.

The contract administrator co-ordinates site inspections and issues instructions as required. The contract administrator holds regular construction progress meetings at which the supply team issue progress reports. The contract administrator in turn prepares construction progress reports for the employer.

If they have not already done so, the employer begins preparations for occupation of the development, including the preparation of an operational policy and a migration strategy or ‘move in programme’, setting out how they will manage the transition into and the operation of the new facility. The soft landings framework suggests that a building readiness sub programme should be prepared in order that proper consideration is given to commissioning, [[Handover_to_client|handover]] and aftercare. Suppliers should be involved in the preparation of these strategies to ensure that interfaces are understood and expectations are managed.

-----
Inspections, commissioning, testing and training

-----
The contractor co-ordinates procedures for inspections, commissioning, testing and employer training in relation to building services and other aspects of the building. Testing and commissioning attribute information should be added to the project information model.

The contractor rectifies any defects that become apparent during commissioning, testing and inspection procedures. Where necessary, the project information model should be updated.

The contractor prepares a draft building owner's manual and a plain language building user's guide. The contractor also co-ordinates the preparation of the building log book providing the employer with information about building services to help them operate the building efficiently (the soft landings framework proposes that this should be incorporated into a wider technical guide for the building operators). The principal designer completes the health and safety file. This information should all be provided in a format that will be easy for the employer to edit in the future, as it may need to be updated during occupation of the completed development.

-----
End of stage report and information exchange

-----
The contractor co-ordinates the preparation of an ‘end of construction’ project information model, which includes as-installed data and information about what has actually been built.

The contractor confirms to the contract administrator that the works are complete.

A construction stage report is prepared identifying variations, claims, cost build up, schedules of defects and so on.

The contractor prepares an information exchange (or 'data drop') as required by the employer's information requirements. This involves issuing published information into the employer's information environment.

-----
Employer’s decision point

-----
The table below sets out examples of plain language questions that an employer might ask at this decision point and the information they might require to answer those questions.

{|
|width="50%"| Plain language questions
|width="50%"| Information required
|-
|
Is the information compliant with the employer's information requirements? Have the works been completed?

Has the development been tested and patent defects rectified?

Should practical completion be certified and the building occupied?

Is there a clear migration strategy and operational strategy in place?

Is any training required?
|
As constructed building information model files in native and industry foundation classes (IFC) format. COBie file

Updated employer's information requirements.

Building owner's manual.

Building user's guide.

Building log book / Technical guide.

Health and safety file.

Construction stage report.
|}

-----
Next stage: [[6:_Handover_and_close_out|6: Handover and close out]].

-----
--[[User:Cohesive|Cohesive]]

[[Category:DCN_Definition]] [[Category:DCN_Guidance]] [[Category:DCN_Template]] [[Category:Client_procedures]] [[Category:Public_procedures]] [[Category:BIM]]

4: Technical design

2022-07-25T09:13:16Z

Cohesive:

3: Developed design

2022-07-25T09:13:03Z

Cohesive:

2: Concept design

2022-07-25T09:12:49Z

Cohesive:

{|
| [[File:Home_icon_grey.jpg|link=Step-by-step_guide_to_using_BIM_on_projects]]
| [[File:0a_icon_not_bold.jpg|link=0a:_Strategic_definition_(business_justification)]]
| [[File:0b_icon_not_bold.jpg|link=0b:_Strategic_definition_(strategic_brief)]]
| [[File:1a_icon_not_bold.jpg|link=1a:_Preparation_and_brief_(appraisals)]]
| [[File:1b_icon_not_bold.jpg|link=1b:_Preparation_and_brief_(brief_and_information_requirements)]]
| [[File:1c_icon_not_bold.jpg|link=1c:_Preparation_and_brief_(supplier_appointments)]]
| [[File:2_icon_solid_v2.jpg|link=2:_Concept_design]]
| [[File:3_icon_not_bold.jpg|link=3:_Developed_design]]
| [[File:4_icon_not_bold.jpg|link=4:_Technical_design]]
| [[File:5_icon_not_bold.jpg|link=5:_Construction]]
| [[File:6_icon_not_bold.jpg|link=6:_Handover_and_close_out]]
| [[File:7_icon_not_bold.jpg|link=7:_In_use]]
|}

The concept design or 'concept' is the initial design response to the project brief.

The project brief should continue to develop throughout this stage and it may be necessary to revise performance targets as a result of the developing concept design. The project brief may be 'frozen' at the end of this stage and change control procedures introduced.

The employer's information requirements will also continue to develop, and the project management plan should be reviewed and updated.

NB Throughout this stage, the word 'supplier' refers either to an integrated supply team appointed to design and construct (and perhaps operate) the proposed development, or to design consultants if suppliers have only been appointed to design the proposed development at this stage.

-----
Post contract BIM execution plan and master information delivery plan

-----
Once the contract for suppliers to design (and perhaps construct, and even operate) the development has been awarded, the successful supplier submits a post-contract BIM execution plan (BEP) providing more detail about their methodology, confirming their (and their supply chain’s) BIM capabilities and providing a master information delivery plan (MIDP). The master information delivery plan sets out when project information will be prepared, by whom, using what protocols and procedures - from the supplier's perspective (the employer's information requirements sets this out from the employer's perspective).

Where more than one supplier is appointed, there may be one overarching BIM execution plan and master information delivery plan, with responsibility for its preparation set out in the appointment documents, and then secondary BIM execution plans prepared by subsequent suppliers, informed by the content of the primary plan.

The supplier may hold a project induction meeting to help develop the post-contract BIM execution plan and master information delivery plan, and to confirm capabilities and capacities, define roles and identify training needs.

The BIM execution plan should include a volume strategy, which describes how the information models will be divided into manageable spatial subdivisions. The separate volumes will be based on important aspects of the design or specialised functions, will allow multiple disciplines to work on project models simultaneously and should be sized to ensure the individual file sizes do not become too large and then become difficult to transfer and read in other software.

-----
Common data environment

-----
If it has not already been provided by the employer, the supplier should set up a common data environment (CDE) to manage the creation, sharing and publishing of project information. This is the single source of all information relating to the project and should be set up to facilitate the spatial coordination and information exchange processes described in PAS 1192.

If it has not already been done, the supplier's information manager ensures that information management solutions function properly, information management processes are in place and that participants have the appropriate skills and competences. If there are any interoperability, training or other issues, these should be resolved before design commences.

-----
Concept design

-----
The supplier develops a concept design which should demonstrate early co-ordination of:

* Aesthetic intent, form and spatial arrangements.
* Outline structural and services designs.
* High-level simulation results to determine whether the design is likely to comply with requirements.
* Outline site and landscape design.
* Outline specifications.
* Schedules and reports demonstrating compliance with the project brief.
* Preliminary construction and phasing sequencing studies and general project programme information.

The information in design models, drawings and documents is collectively known as the ‘project information model’ (PIM). It will generally be made up of a number of federated models that originate with the employer, architect, structural engineer, building services engineer, contractor, sub-contractors, suppliers and so on. At this stage, the built asset might be represented by massing diagrams or 2D symbols representing generic elements, with some critical elements developed in more detail.

The project information model also includes drawings, reports and other structured information directly related to the built asset and its facilities, floors, spaces, zones, systems and components.

It can also be useful at this stage to generate presentation material such as photo visualisations and 3D walk-throughs that help facilitate employer assessments and consultations with user panels, champions, and other stakeholders.

-----
Planning permission

-----
The local planning authority should be consulted to determine the preferred form and content of the planning application, dates of planning committee meetings, committee procedures, possible planning conditions and planning obligations, the amount of the community infrastructure levy, the planning fee and the requirement to undertake an external consultation process.

For large or sensitive projects, it may be necessary to prepare an environmental impact assessment (EIA) and it may be appropriate to seek a screening decision and/or a scoping study from the local planning authority to determine whether an EIA is necessary and what information it should include.

Feedback from consultations may result in changes to the developing design, the project brief and the employer's information requirements.

-----
Cost plan

-----
An elemental cost plan should be produced from the project information model, accompanied by a schedule of assumptions made. This should identify any abnormal costs and whether it may be appropriate to undertake a value management exercise. A cash-flow projection should also be prepared, and an assessment of whole-life costs might be undertaken.

-----
End of stage report and information exchange

-----
An end of stage report should be prepared, summarising key issues, identifying risks, setting out the project programme, identifying what else has to be designed, and assessing the likelihood of receiving planning permission and building regulations approval. It might also set out a soft landings strategy and summarise the outcome of consultations. However, the report should only include required, or key co-ordinated information and necessary interpretation. It should not be filled with unnecessary information and should not duplicate information that already exists elsewhere.

The supplier should prepare an information exchange (or 'data drop') as required by the employer's information requirements. This involves issuing published information into the employer's information environment. For level 2 BIM this information may include:

* A series of federated building information models prepared by different design teams, including non-graphical data and associated documentation, and comprising native and industry foundation classes (IFC) files. IFC is the international standard for building information modelling used for sharing data across different software applications.
* Construction operations building information exchange (COBie) files and other structured data such as schedules. COBie is a non-proprietary multi-page, spreadsheet data format focused on delivering asset data rather than geometric information.
* Drawings and reports. These may be read-only PDFs.

-----
Employer’s decision point

-----
The table below sets out examples of plain language questions the employer might ask at this decision point and the information they might require to answer those questions.

{|
|width="50%"| Plain language questions
|width="50%"| Information required.
|-
|
Is the information compliant with employer's information requirements? Does the concept design satisfy the project brief and business case?

Have necessary consultations been carried out?

Is the concept design affordable or is value management necessary?

Are the proposals likely to satisfy the building regulations and other statutory requirements?

Should the project brief be frozen and change control procedures introduced?

Is planning permission likely to be granted?

Are planning conditions or planning obligations likely to be acceptable?

Should a planning application be prepared?
|
Native and industry foundation classes (IFC) building information model files. COBie file.

Drawings and reports.

Updated employer's information requirements.

Updated project management plan.

Outline specification.

Elemental cost plan.

Project programme.
|}

If a planning application is submitted at this stage, this might include material generated from the project information model, such as; 2D site drawings, plans, elevations, schedules of accommodation, 2D and 3D visualisations from key views, an outline specification, the project programme, the construction sequence and other managed information.

On receipt of a planning decision the employer may, if necessary, consider whether to submit a revised application or to lodge a planning appeal. It may also be necessary to update the project brief, employer's information requirements and project management plan to reflect planning conditions or planning obligations imposed upon the project.

-----
Next stage >> [[3:_Developed_design|3: Developed design]].

-----
--[[User:Cohesive|Cohesive]]

[[Category:Articles_needing_more_work]] [[Category:DCN_Definition]] [[Category:DCN_Guidance]] [[Category:DCN_Template]] [[Category:Client_procedures]] [[Category:Public_procedures]] [[Category:BIM]]

1c: Preparation and brief (supplier appointments)

2022-07-25T09:12:36Z

Cohesive:

1b: Preparation and brief (brief and information requirements)

2022-07-25T09:12:21Z

Cohesive:

{|
| [[File:Home_icon_grey.jpg|link=Step-by-step_guide_to_using_BIM_on_projects]]
| [[File:0a_icon_not_bold.jpg|link=0a:_Strategic_definition_(business_justification)]]
| [[File:0b_icon_not_bold.jpg|link=0b:_Strategic_definition_(strategic_brief)]]
| [[File:1a_icon_not_bold.jpg|link=1a:_Preparation_and_brief_(appraisals)]]
| [[File:1b_icon_solid.jpg|link=1b:_Preparation_and_brief_(brief_and_information_requirements)]]
| [[File:1c_icon_not_bold.jpg|link=1c:_Preparation_and_brief_(supplier_appointments)]]
| [[File:2_icon_not_bold_v2.jpg|link=2:_Concept_design]]
| [[File:3_icon_not_bold.jpg|link=3:_Developed_design]]
| [[File:4_icon_not_bold.jpg|link=4:_Technical_design]]
| [[File:5_icon_not_bold.jpg|link=5:_Construction]]
| [[File:6_icon_not_bold.jpg|link=6:_Handover_and_close_out]]
| [[File:7_icon_not_bold.jpg|link=7:_In_use]]
|}

This is the second part of the 'Preparation and brief' stage (or 'Brief' in PAS 1192:2). It involves preparing documentation for the appointment of 'suppliers'.

These suppliers may be consultants appointed to design the development and perhaps to inspect works on site, or they may be an integrated supply team appointed to design, construct and perhaps even operate the development.

The employer needs to be aware that they are not only making appointments to design, construct and operate the proposed development, they are also procuring vital information that will be necessary to inform decisions during its development and operation, and this information requirement needs to be clearly defined.

-----
Employer's information manager

-----
If it has not already been done, an employer's information manager should be appointed, with initial responsibility for defining the employer's information requirements, establishing information standards methods and procedures and preparing an employer's information environment for the collection, verification, storage, and exploitation of information delivered by suppliers.

-----
Project brief

-----
A full project brief should be developed based on the strategic brief. The project brief is the key document upon which the design will develop.

In order to develop the project brief, the employer’s advisers will carry out consultations with user panels, champions and other stakeholders. This should include consultation with the operators of the completed development, if known, and the soft landings champion. If the operators are not known, it may be necessary to appoint external advisers.

Where possible, requirements set out in the project brief should be scheduled in a requirements management application or spreadsheet that is easy to interrogate and share and that might allow automatic validation of proposals as they develop. This should include measurable performance targets which can be tested, and an assessment of the consequences of targets being missed. Targets should be measured using standard metrics that are easy to compare with other projects.

The project brief will continue to evolve and become more detailed until the end of the concept design stage.

-----
Employer's information requirements (EIR)

-----
The employer's information requirements (EIR) define the information that will be required by the employer from their own internal team and from suppliers for the development of the project and the operation of the completed built asset. They ensure that appropriate information is created in a suitable format at the right time and are crucial to the successful adoption of building information modelling processes during the course of the project.

Relevant extracts from the employer's information requirements will be included in procurement documents for each tier 1 supplier (suppliers appointed directly by the employer), which may include; advisors, consultants, contractors and so on. Prospective suppliers respond to the employer's information requirements with a pre-contract BIM execution plan (BEP).

Employer’s information requirements usually include:

* Standard methods and procedures providing clarity on information formats and naming conventions and guidance on how to supply information.
* Information-related roles and responsibilities giving a clear definition of information-related roles and what is expected from them.
* An information delivery plan or information schedule identifying which information deliverables should be delivered, by whom and when.
* A COBie demand matrix identifying the structured data about the facility, floors, spaces, zones and building components that should be delivered, by whom and when.

The exact nature of the employer's information requirements will depend on the complexity of the project and the experience and requirements of the employer. Experienced employers may develop very detailed employer’s information requirements, whilst others may only set out high-level requirements, leaving the supplier to propose how the information requirements will be met.

The employer's interests will extend beyond design information, to information such as; construction sequencing (4D), cost (5D) and asset information at handover (6D). However, information should only be required where the employer will be able to use it to satisfy a business need, and where this need outweighs the cost of its preparation. Requiring too much information, or too soon, can incur unnecessary costs and can restrict options.

Employer's information requirements will become more detailed as the project progresses:

* They start by identifying the required material, functional and performance information about facilities, floors and spaces.
* As the design progresses they identify more specific requirements about the proposed systems and building components to support procurement.
* By the end of the project they define the need for precise performance information to support the maintenance and operation of systems and components that are actually installed.

Preparing the employer's information requirements begins by developing an information requirements process map or digital plan of works (dPow). This will help identify key employer's decision points during the project and the questions they will need to answer at those decision points. Typically these decision points will be aligned to project stages.

The questions employers need to answer at these decision points should be set out as non-technical, plain language questions (PLQ’s) that everyone can understand. High-level questions might then be divided into component questions, and where possible these might be broken down further into questions that can be answered with specific information.

Employer's information requirements should be reviewed and updated at the end of each stage, and where extracts have been used as the basis of appointments, those extracts should be subject to change control.

NB The UK government-sponsored BIM Toolkit has been developed to support the production of employer's information requirements.

-----
Employer's information systems and environments

-----
If it has not already been done, the employer’s information manager should set up and configure an employer's information environment for the project. This is a digital collaboration area that may be located in the 'cloud' or an on-premise server, where project information defined in the employer's information requirements and supplied by tier 1 suppliers is exchanged, verified and stored.

It provides an employer-side document and data management system for the receipt, validation and approval of project information delivered by suppliers and is the single source of information about the project that the employer uses to make informed decisions.

The employer’s information environment is part of the extended common data environment (CDE) referenced in PAS 1192-2 which will also include the supply-side common data environment used by the project team.

Depending on the employer’s preferences, the supply-side common data environment can be set up and configured by the employer for the supply chain, but it is generally more appropriate to leave this responsibility with the tier 1 suppliers. Either way, responsibility for supplying and managing the supply-side common data environment should be clearly identified in the employer's information requirements.

-----
BIM protocol

-----
A BIM protocol (such as the freely-available CIC BIM protocol) sets out the contractual definition of information-related responsibilities, liabilities and limitations. It obliges suppliers to provide specified information in accordance with referenced aspects of the employer's information requirements.

A BIM protocol enables BIM to be mandated on a project using any form of appointment document or contract by the inclusion of a model enabling amendment clause.

[[Relationship_between_contractual_documents_for_BIM|Click here to see a diagram illustrating the relationship between the contractual documents for BIM]].

-----
Cost assessment

-----
Before appointments are made, the initial cost appraisal should be developed into an elemental cost plan, including a pre-tender estimate and a cash flow projection, to verify that the project is affordable.

At this stage, the elemental cost plan may simply be the total construction cost for the project divided into elements on a percentage basis. This should be prepared in a spreadsheet format that is easy to interrogate and import into BIM costing software and should adopt a standard approach such as that defined by the new rules of measurement (NRM).

-----
Employer’s decision point

-----
The table below sets out examples of plain language questions that an employer might ask at this decision point and the information they might require to answer those questions.

{|
|width="50%"| Plain language questions
|width="50%"| Information required
|-
|
Does the project brief still satisfy the requirements set out in the business case? Has the project brief been developed in sufficient detail for concept design to begin?

Are the employer's information requirements developed sufficiently to make appointments?

Is the project affordable or is value management necessary?

Have roles and responsibilities been adequately defined?

Should appointments be made to design the development?

Are the necessary environments and systems in place?

Is any training necessary?
|
Project brief. Employer's information requirements.

Elemental cost plan.
|}

-----
Next stage >> [[1c:_Preparation_and_brief_(supplier_appointments)|1c: Preparation and brief (supplier appointments)]].

-----
--[[User:Cohesive|Cohesive]]

[[Category:DCN_Definition]] [[Category:DCN_Guidance]] [[Category:DCN_Template]] [[Category:Client_procedures]] [[Category:Public_procedures]] [[Category:BIM]]

1a: Preparation and brief (appraisals)

2022-07-25T09:12:06Z

Cohesive:

Step-by-step guide to using BIM on projects

2022-07-25T09:11:44Z

Cohesive:

{|
| [[File:Home_icon_solid.jpg|link=Step-by-step_guide_to_using_BIM_on_projects]]
| [[File:0a_icon_not_bold.jpg|link=0a:_Strategic_definition_(business_justification)]]
| [[File:0b_icon_not_bold.jpg|link=0b:_Strategic_definition_(strategic_brief)]]
| [[File:1a_icon_not_bold.jpg|link=1a:_Preparation_and_brief_(appraisals)]]
| [[File:1b_icon_not_bold.jpg|link=1b:_Preparation_and_brief_(brief_and_information_requirements)]]
| [[File:1c_icon_not_bold.jpg|link=1c:_Preparation_and_brief_(supplier_appointments)]]
| [[File:2_icon_not_bold_v2.jpg|link=2:_Concept_design]]
| [[File:3_icon_not_bold.jpg|link=3:_Developed_design]]
| [[File:4_icon_not_bold.jpg|link=4:_Technical_design]]
| [[File:5_icon_not_bold.jpg|link=5:_Construction]]
| [[File:6_icon_not_bold.jpg|link=6:_Handover_and_close_out]]
| [[File:7_icon_not_bold.jpg|link=7:_In_use]]
|}

This step-by-step guide explains how Level 2 [[Building_information_model|building information modelling]] (BIM) can be used for the development of a built asset such as a new building.

BIM Level 2 involves developing building information in a collaborative 3D environment with data attached, but created in separate discipline models.It is required as a minimum on centrally-procured public projects in the UK and is commonly used on private-sector projects.

This guide is written for use by people who are not BIM experts and will be helpful for employers, consultants, contractors and suppliers. To help understand BIM, a [[BIM_glossary_of_terms|glossary of BIM terminology]] is provided along with a wide selection of [[BIM_articles|supporting articles]].

Projects that incorporate Level 2 BIM identify the decisions that will need to be made throughout the life of a built asset and the information deliverables required at each stage of the project to support those decisions. This ensures that appropriate information is created and shared in a suitable format at the right time so that better decisions can be made throughout the delivery and operation of built assets.

Information deliverables include model files, documents and structured data files containing information about the facility, floors, spaces, systems and components. Together these create a digital replica of the built asset that starts by representing design intent and matures by the time handover occurs to reflect what has actually been built and installed.

The guide shows how Level 2 BIM can be incorporated into a project following the [[RIBA_plan_of_work|RIBA plan of work 2013]] stages. The first two stages have been broken down into sub-sections where important employer decisions have been identified that are not included within the RIBA plan of work.

The end of each stage is marked by an employer’s decision point, or gateway, at which the employer needs specific information to help them decide whether the project has developed satisfactorily and whether it should continue to the next stage.

The guide is aligned to [[PAS_1192-2|PAS 1192-2]], the standard for Level 2 BIM in the capital/delivery phase of construction projects and in accordance with the other information management industry standards such as [[BS1192|BS1192:2007]], [[BS_1192-4|BS1192:4]] and [[PAS_1192-5:2015_Specification_for_security-minded_building_information_modelling,_digital_built_environments_and_smart_asset_management|PAS1192:5]].

To start, click on the appropriate stage below.

-----
Stage 0: Strategic definition

* [[0a:_Strategic_definition_(business_justification)|0a: Business justification]]
* [[0b:_Strategic_definition_(strategic_brief)|0b: Strategic brief]]

-----
Stage 1: Preparation and brief

* [[1a:_Preparation_and_brief_(appraisals)|1a: Appraisals]]
* [[1b:_Preparation_and_brief_(brief_and_information_requirements)|1b: Brief and information requirements]]
* [[1c:_Preparation_and_brief_(supplier_appointments)|1c: Supplier appointments]]

-----
[[2:_Concept_design|Stage 2: Concept design]]

-----
[[3:_Developed_design|Stage 3: Developed design]]

-----
[[4:_Technical_design|Stage 4: Technical design]]

-----
[[5:_Construction|Stage 5: Construction]]

-----
[[6:_Handover_and_close_out|Stage 6: Handover and close out]]

-----
[[7:_In_use|Stage 7: In use]]

-----
--[[User:Cohesive|Cohesive]]

= Related articles on Designing Buildings =

* [[Building_information_modelling_BIM|Building information modelling BIM]].
* [[BIM_and_facilities_management|BIM and facilities management]].
* [[BIM_articles|BIM articles]].
* [[BIM_glossary_of_terms|BIM glossary of terms]].
* [[BIM_level_2|BIM level 2]].
* [[BIM_resources|BIM resources]].
* [[Employers_information_requirements|Employers information requirements]].
* [[Government_construction_strategy|Government construction strategy]].
* [[Government_soft_landings|Government soft landings]].

[[Category:DCN_Guidance]] [[Category:Do_not_autolink]] [[Category:Client_procedures]] [[Category:Public_procedures]] [[Category:BIM]]

0b: Strategic definition (strategic brief)

2022-07-25T09:11:25Z

Cohesive:

0a: Strategic definition (business justification)

2022-07-25T09:10:59Z

Cohesive:

{|
| [[File:Home_icon_grey.jpg|link=Step-by-step_guide_to_using_BIM_on_projects]]
| [[File:0a_icon_solid.jpg|link=0a:_Strategic_definition_(business_justification)]]
| [[File:0b_icon_not_bold.jpg|link=0b:_Strategic_definition_(strategic_brief)]]
| [[File:1a_icon_not_bold.jpg|link=1a:_Preparation_and_brief_(appraisals)]]
| [[File:1b_icon_not_bold.jpg|link=1b:_Preparation_and_brief_(brief_and_information_requirements)]]
| [[File:1c_icon_not_bold.jpg|link=1c:_Preparation_and_brief_(supplier_appointments)]]
| [[File:2_icon_not_bold_v2.jpg|link=2:_Concept_design]]
| [[File:3_icon_not_bold.jpg|link=3:_Developed_design]]
| [[File:4_icon_not_bold.jpg|link=4:_Technical_design]]
| [[File:5_icon_not_bold.jpg|link=5:_Construction]]
| [[File:6_icon_not_bold.jpg|link=6:_Handover_and_close_out]]
| [[File:7_icon_not_bold.jpg|link=7:_In_use]]
|}

'Business justification' is the first part of the 'Strategic definition' stage (or 'Strategy' in PAS 1192:2 (now replaced by BS EN ISO 19650)). It involves making crucial decisions about whether and how to proceed with the proposed project.

These decisions, along with those made throughout the life of the development, should be information-driven. The purpose of building information modeling (BIM) is to ensure appropriate information is created at the right time.

It is important that this information is prepared in a format that will be of the greatest value through the life of the project, and that it is named and stored in a way that will be consistent with later stages. At this stage, this may simply be a matter of creating a folder in which files can be stored and adopting a standard file naming convention such as that outlined in BS 1192:2007 (now replaced by BS EN ISO 19650).

-----
Tasks

-----
From the assessment of business operations or from the assessment of an existing estate, the employer identifies a need that could require the development of a newly built asset.

They then prepare a statement of need that describes the requirements for the potential project. This will later develop into a strategic brief. The statement of need is likely to be in a report format, however, where possible, information and requirements should be scheduled in a requirement management application or spreadsheet that can be expanded and will be easy to use to test whether proposals satisfy requirements later in the project.

The employer then prepares a preliminary business case based upon the statement of need. This offers a justification for the investment required by the potential project. As with the statement of need, this is likely to be in a report format, however, where possible information should be scheduled in a requirement management application or spreadsheet so that it will be easier to use, test and develop.

-----
Employer's decision point

-----
At key points in the development of the project, the employer will have to decide whether the project should proceed, whether additional information is required or whether the project should be changed or abandoned.

To make this decision, the employer will need to answer a series of questions about the developing project (sometimes described as plain language questions), which will require that specific information is available. Later in the project, the publication of required information may be described as an 'information exchange' or 'data drop'.

The table below sets out examples of plain language questions that an employer might ask at this decision point and the information they might require to answer those questions.

{|
|width="50%"| Plain language questions
|width="50%"| Information required
|-
|
Has the project information been prepared and organized in a way that will be useful in later stages? Does the statement of need adequately define the requirement?

Does the preliminary business case give sufficient justification for the project?

Should the project be pursued and a strategic brief prepared that will allow feasibility studies and options appraisals to be carried out?
| Statement of need. Preliminary business case.
|}

-----
next stage >> [[0b:_Strategic_definition_(strategic_brief)|0b: Strategic definition (strategic brief)]].

-----
--[[User:Cohesive|Cohesive]]

[[Category:DCN_Definition]] [[Category:DCN_Guidance]] [[Category:DCN_Template]] [[Category:Client_procedures]] [[Category:Public_procedures]] [[Category:BIM]]