Designing Buildings - User contributions [en]

0a: Strategic definition (business justification)

2022-07-25T09:10:13Z

Coheisve:

{|
| [[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:Coheisve|Coheisve]]

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

0a: Strategic definition (business justification)

2022-07-25T09:09:58Z

Coheisve:

{|
| [[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:Coheisve|Coheisve]] 10:09, 25 Jul 2022 (BST)

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

0a: Strategic definition (business justification)

2022-07-25T09:09:43Z

Coheisve:

{|
| [[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:Cohsive|Cohsive]]

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

User:Cohesive

2022-07-25T09:07:34Z

Coheisve:

Cohesive brings you the world's leading digital engineering, enterprise asset management, asset delivery and asset service performance optimisation capabilities. Utilising the power of data, digital twins, artificial intelligence, and capitalising on new technology to optimise and automate operations, building digital talents and cultures for better long-term sustainable results.

We provide strategic advice, integration services, systems deployment, and service operations to enable our clients to excel in achieving their business outcomes. We respond with agility to rapidly changing market conditions, preparing you for the future whilst maximising value and resources, operating in a way that safeguards the planet in a sustainable way.

-----
Infinitely better

-----
Long-term strategic asset life cycle partnership, or short-term project trouble shooting, we partner with our clients to provide the best possible service to deliver optimal financial, environmental, and social outcomes, for you and your customers.

Cohesive is a global lifecycle asset systems integrator, focusing on using data to transform businesses operational efficiency, carbon performance and provide outstanding customer performance. With a focus on optimising your ESG we are the partner to provide better performance.

Our CEO, Dr. Mark Bew MBE, led the development of the UK Government's BIM Level 2 Mandate and chaired the UK BIM Task Group, which delivered the pioneering BIM Level 2 programme. Mark also led the development of the Government’s Digital Built Britain Strategy (BIM Level 3), which seeks to transform our approach to infrastructure development, construction and service provision.