Benefits of using BIM for client requirements management (Baldauf et al., 2020)
| Benefits | Description |
|---|---|
| Visualisation | Requirements must be well structured and easy to be visualised (Kiviniemi, 2005; Shen et al., 2013; Jallow et al., 2014) |
| Storage | Requirement information should be stored in a central and accessible repository (Christiansson et al., 2011; Shen et al., 2013; Jallow et al., 2014) |
| Connection | Requirements must be connected to spaces and components in product models (Kiviniemi, 2005; Koppinen et al., 2008; Christiansson et al., 2011; Shen et al., 2013) |
| Communication | Requirements must be available in a useable format to stakeholders (Kiviniemi, 2005; Christiansson et al., 2011; Shen et al., 2013; Jallow et al., 2014) |
| Assessment | BIM should assist stakeholders in assessing design, based on a set of current requirements (Eastman et al., 2009; Parsanezhad et al., 2016; Macit İlal and Günaydın, 2017) |
| Automation | BIM should support the automation of the design assessment process (Eastman et al., 2009; Jansson et al., 2013; Parsanezhad et al., 2016; Macit İlal and Günaydın, 2017) |
| Traceability | BIM should enable stakeholders to track requirements in order to improve change management and the verification of requirements consistency (Dick, 2004; Jallow et al., 2014) |
| Reuse of requirements | A broad repository of requirements is useful for creating requirement templates that allow a large set of requirements to be reused in different projects (Kiviniemi, 2005; Jallow et al., 2014) |
| Changes control | BIM should assist in monitoring and controlling changes and understanding how other requirements may be affected by a change (Shen et al., 2013; Jallow et al., 2014). It can also be used to communicate in real-time changes in requirements that need to be updated or refined frequently (Jallow et al., 2014; Baldauf et al., 2020) |
| User interface | BIM should facilitate the user interface and its widely accepted by project teams (Eastman et al., 2009) |
| Standardization | BIM can potentially support the standardization of a large number of criteria for assessing design proposals (Baldauf et al., 2020) |
| Comprehensiveness | BIM should support the modelling of different types of requirements and levels of abstraction (Baldauf et al., 2020) |
| Benefits | Description |
|---|---|
| Visualisation | Requirements must be well structured and easy to be visualised ( |
| Storage | Requirement information should be stored in a central and accessible repository ( |
| Connection | Requirements must be connected to spaces and components in product models ( |
| Communication | Requirements must be available in a useable format to stakeholders ( |
| Assessment | BIM should assist stakeholders in assessing design, based on a set of current requirements ( |
| Automation | BIM should support the automation of the design assessment process ( |
| Traceability | BIM should enable stakeholders to track requirements in order to improve change management and the verification of requirements consistency ( |
| Reuse of requirements | A broad repository of requirements is useful for creating requirement templates that allow a large set of requirements to be reused in different projects ( |
| Changes control | BIM should assist in monitoring and controlling changes and understanding how other requirements may be affected by a change ( |
| User interface | BIM should facilitate the user interface and its widely accepted by project teams ( |
| Standardization | BIM can potentially support the standardization of a large number of criteria for assessing design proposals ( |
| Comprehensiveness | BIM should support the modelling of different types of requirements and levels of abstraction ( |
As a benefit of your subscription, you can share temporary access to restricted articles.
Each link will stop working after 30 days or 10 uses. You may create up to 10 links in a 30 day period.
Please sign in to your personal account to gift article access.
As a benefit of your subscription, you can share temporary access to restricted articles.
Each link will stop working after 30 days or 10 uses. You may create up to 10 links in a 30 day period.
Gift articles remaining: --
Each link will stop working after 30 days or 10 uses. You may create up to 10 links in a 30 day period.
Gift articles remaining: --
As a benefit of your subscription, you can share temporary access to restricted articles.
Each link will stop working after 30 days or 10 uses.
You have reached the limit of 10 links within a 30 day period.
Sharing content requires targeting cookies to be enabled. Please update your cookie preferences to use this feature.