Requirements management - Revision history

80.62.117.212 at 12:14, 5 August 2022

2022-08-05T12:14:58Z

← Older revision		Revision as of 12:14, 5 August 2022
Line 3:		Line 3:
	The concept of requirements management (RM) is relatively new to the construction industry, but it is well established in other engineering disciplines such as software development and aerospace engineering.		The concept of requirements management (RM) is relatively new to the construction industry, but it is well established in other engineering disciplines such as software development and aerospace engineering.

−	RM is the process of capturing, structuring, communicating, analysing and verifying the requirements for a facility, with to ensure it will fulfil the needs of the stakeholders who will use, own, acquire and operate it.	+	RM is the process of capturing, structuring, communicating, analysing and verifying the requirements for a facility, with the aim to ensure it will fulfil the needs of the stakeholders who will use, own, acquire and operate it.

	RM overlaps with the concept of briefing, but there is a difference in scope. While briefing traditionally focuses on the early phases of a project (i.e. the briefing phase), RM is a continuous process in which requirements are defined, refined, updated and verified throughout all phases of a facility’s life cycle.		RM overlaps with the concept of briefing, but there is a difference in scope. While briefing traditionally focuses on the early phases of a project (i.e. the briefing phase), RM is a continuous process in which requirements are defined, refined, updated and verified throughout all phases of a facility’s life cycle.

Designing Buildings at 10:05, 3 August 2022

2022-08-03T10:05:48Z

← Older revision		Revision as of 10:05, 3 August 2022
Line 160:		Line 160:
	* Strategic brief.		* Strategic brief.

−	[[Category:DCN_Definition]] [[Category:DCN_Guidance]] [[Category:DCN_Project_Knowledge]] [[Category:Definitions]] [[Category:Construction_management]]	+	[[Category:DCN_Definition]] [[Category:DCN_Guidance]] [[Category:DCN_Project_Knowledge]] [[Category:Definitions]] [[Category:Construction_management]] [[Category:Operations]]

Designing Buildings at 07:51, 7 March 2022

2022-03-07T07:51:57Z

← Older revision		Revision as of 07:51, 7 March 2022
Line 70:		Line 70:
	= Communicating requirements =		= Communicating requirements =

−	~~Needless to say, it~~ is essential to communicate requirements to those who will be designing and building the project. This can be done by means of reports, diagrams and ~~[[Room_data_sheet\|~~datasheets]].	+	It is essential to communicate requirements to those who will be designing and building the project. This can be done by means of reports, diagrams and datasheets.

	Different actors will be interested in different requirements; an architect, for example, may be primarily interested in spatial requirements, a mechanical engineer in the technical requirements.		Different actors will be interested in different requirements; an architect, for example, may be primarily interested in spatial requirements, a mechanical engineer in the technical requirements.
Line 76:		Line 76:
	When communicating requirements, it is crucial that they are up-to-date. Requirements should preferably be accessible via an online platform rather than hidden away in a plethora of emails and reports, so that everybody has access to the same set of up-to-date requirements.		When communicating requirements, it is crucial that they are up-to-date. Requirements should preferably be accessible via an online platform rather than hidden away in a plethora of emails and reports, so that everybody has access to the same set of up-to-date requirements.

−	== Activities ==	+	Activities

	* Giving project actors access to requirements (via documents or an online model).		* Giving project actors access to requirements (via documents or an online model).
Line 84:		Line 84:
	= Analysing requirements =		= Analysing requirements =

−	A requirements analysis is a formal review of the project’s requirements, typically made by the design/delivery team before the start of the design process or during a tender process. It means that all the disciplines involved go through the entire set of requirements and flag requirements that they regard as unclear or risky in terms of costs or feasibility. These outcomes are then fed back to the client as input for further improvement of the requirements.	+	A requirements analysis is a formal review of the project’s requirements, typically made by the design/delivery team before the start of the design process or during the tender process. It means that all the disciplines involved go through the entire set of requirements and flag requirements that they regard as unclear or risky in terms of costs or feasibility. These outcomes are then fed back to the client as input for further improvement of the requirements.

−	== Activities ==	+	Activities

	* Making a risk analysis of the requirements set.		* Making a risk analysis of the requirements set.
Line 96:		Line 96:
	= Linking requirements to BIM models =		= Linking requirements to BIM models =

−	If captured in the right format, requirements can then be linked to ~~[[BIM_model\|~~BIM models]]. The advantage of doing so is that requirements can be integrated into the design process. Requirements can be used as input for parametric or generative design processes or for the automated verification of design solutions ~~(see also below)~~. In particular, requirements concerning room quantities, room sizes and the placement of ~~[[FF%26E\|~~FF&E]] items in rooms can easily be checked.	+	If captured in the right format, requirements can then be linked to BIM models. The advantage of doing so is that requirements can be integrated into the design process. Requirements can be used as input for parametric or generative design processes or for the automated verification of design solutions. In particular, requirements concerning room quantities, room sizes and the placement of FF&E items in rooms can easily be checked.

−	== Activities ==	+	Activities

	* Creating data exports of requirements that are ‘readable’ for BIM models.		* Creating data exports of requirements that are ‘readable’ for BIM models.
Line 106:		Line 106:
	= Verifying compliance =		= Verifying compliance =

−	[[Verification~~\|Verification]]~~ is the process of checking whether a design proposal or built solution is ~~[[Compliance\|~~compliant]] with the defined requirements. Typically it is the design team and/or the contractor who is responsible for this.	+	Verification is the process of checking whether a design proposal or built solution is compliant with the defined requirements. Typically it is the design team and/or the contractor who is responsible for this.

	Verification can be done using a simple compliance matrix, but it can also be a more comprehensive procedure based on specifications concerning verification methods (e.g. calculations, simulations, inspections), verification moments and the documentation that needs to be provided (e.g. test reports).		Verification can be done using a simple compliance matrix, but it can also be a more comprehensive procedure based on specifications concerning verification methods (e.g. calculations, simulations, inspections), verification moments and the documentation that needs to be provided (e.g. test reports).

−	== Activities ==	+	Activities

−	* Developing a verification plan,	+	* Developing a verification plan.
−	* Assigning verifications to various disciplines/actors,	+	* Assigning verifications to various disciplines/actors.
−	* Carrying out verifications in different phases,	+	* Carrying out verifications in different phases.
−	* Monitoring progress and overall compliance rate per phase,	+	* Monitoring progress and overall compliance rate per phase.
−	* Identifying and solving compliance gaps,	+	* Identifying and solving compliance gaps.

	= Managing change =		= Managing change =
Line 122:		Line 122:
	Ideally, requirements do not change during a project, but change cannot be avoided entirely. Changes may come from new insights, budget changes, feedback from contractors or regulatory changes. This need not be a problem as long as change happens in a controlled way.		Ideally, requirements do not change during a project, but change cannot be avoided entirely. Changes may come from new insights, budget changes, feedback from contractors or regulatory changes. This need not be a problem as long as change happens in a controlled way.

−	Once requirements have been formally approved, changes should be made on the basis of formal requests for change (RFCs), which have to reviewed in terms of impact (on costs, time and quality) before they are implemented.	+	Once requirements have been formally approved, changes should be made on the basis of formal requests for change (RFCs), which have to reviewed in terms of impact on costs, time and quality before they are implemented.

−	== Activities ==	+	Activities

	* Setting up a change management procedure.		* Setting up a change management procedure.
Line 138:		Line 138:
	To ensure that standardised requirements are relevant, it is critical to maintain, manage and improve them on the basis of project evaluations.		To ensure that standardised requirements are relevant, it is critical to maintain, manage and improve them on the basis of project evaluations.

−	== Activities ==	+	Activities

	* Developing requirement libraries/templates for common room types, systems or building types.		* Developing requirement libraries/templates for common room types, systems or building types.
	* Evaluating the quality of requirements after each project (e.g. by looking at verification outcomes and the number of RFCs relating to a specific requirement).		* Evaluating the quality of requirements after each project (e.g. by looking at verification outcomes and the number of RFCs relating to a specific requirement).
	* Guiding project teams in the use of requirement libraries/templates in their projects.		* Guiding project teams in the use of requirement libraries/templates in their projects.
−	* ~~Conduct~~ post-occupancy evaluations of projects and ~~incorporate~~ the ‘lessons learnt’ into requirements for new projects.	+	* Conducting post-occupancy evaluations of projects and incorporating the ‘lessons learnt’ into requirements for new projects.
−		+
−	~~= Summarising =~~	+
−		+
−	RM is a fairly new phenomenon in the construction sector, and although it overlaps with the existing practice of [[Briefing\|briefing]], its scope is wider. RM covers the capturing, analysis, communication and verification of all project requirements, through all [[Project_stages\|phases]] of a project. Especially in large and complex projects, there is much to be gained from systematic RM, including avoiding design defects, budget overruns and delivery delays.	+

	--[[User:BriefBuilder\|BriefBuilder]] 15:24, 19 Apr 2021 (BST)		--[[User:BriefBuilder\|BriefBuilder]] 15:24, 19 Apr 2021 (BST)

−	= Related articles on Designing Buildings ~~Wiki~~ =	+	= Related articles on Designing Buildings =

−	* ~~BIM and facilities management~~.	+	* Brief.
−	* ~~Facilities management~~.	+	* Client requirements.
−	* ~~Maintenance, repair and operations procurement~~.	+	* Development brief.
−	* ~~Seasonal and continuous commissioning~~ of ~~buildings~~.	+	* Feasibility studies.
		+	* Mood board.
		+	* Output-based specification.
		+	* Project brief.
		+	* Specification.
		+	* Statement of need.
		+	* Strategic brief.

	[[Category:DCN_Definition]] [[Category:DCN_Guidance]] [[Category:DCN_Project_Knowledge]] [[Category:Definitions]] [[Category:Construction_management]]		[[Category:DCN_Definition]] [[Category:DCN_Guidance]] [[Category:DCN_Project_Knowledge]] [[Category:Definitions]] [[Category:Construction_management]]

Designing Buildings at 07:45, 7 March 2022

2022-03-07T07:45:02Z

80.62.117.25 at 07:18, 22 September 2021

2021-09-22T07:18:44Z

← Older revision		Revision as of 07:18, 22 September 2021
Line 6:		Line 6:

	RM clearly overlaps with the concept of [[Briefing\|briefing]], but there is a difference in scope. While briefing traditionally focuses on the development of a building programme in the early phases of a project (i.e. the [[Preparation_and_briefing\|briefing phase]]), RM is a continuous process in which requirements are defined, refined, updated and verified throughout all phases of a facility’s life cycle.		RM clearly overlaps with the concept of [[Briefing\|briefing]], but there is a difference in scope. While briefing traditionally focuses on the development of a building programme in the early phases of a project (i.e. the [[Preparation_and_briefing\|briefing phase]]), RM is a continuous process in which requirements are defined, refined, updated and verified throughout all phases of a facility’s life cycle.
		+
		+	See the figure below (based on [http://purl.stanford.edu/gh076mt5924 Kiviniemi, 2005)] showing the difference between briefing (as a stage) and requirements management (as a continuous process).
		+
		+	[[File:Process diagrams Arto Kiviniemi-01.png]]

	Another defining aspect of RM is that it not only focuses on the client’s functional and spatial requirements—as briefing primarily does—but also on the technical and operational requirements concerning the building’s [[Building_services\|technical systems]] and elements, the [[Construction_process\|delivery process]], and the [[Facility_management\|operation]] and [[Building_maintenance\|maintenance]] of the facility. As such, requirements management is targeted at the architect, plus all the other actors involved, such as project managers, engineers, expert consultants, (sub)contractors, suppliers, asset managers and service providers.		Another defining aspect of RM is that it not only focuses on the client’s functional and spatial requirements—as briefing primarily does—but also on the technical and operational requirements concerning the building’s [[Building_services\|technical systems]] and elements, the [[Construction_process\|delivery process]], and the [[Facility_management\|operation]] and [[Building_maintenance\|maintenance]] of the facility. As such, requirements management is targeted at the architect, plus all the other actors involved, such as project managers, engineers, expert consultants, (sub)contractors, suppliers, asset managers and service providers.

80.62.116.228 at 10:56, 16 August 2021

2021-08-16T10:56:35Z

← Older revision		Revision as of 10:56, 16 August 2021
Line 34:		Line 34:
	Each of these activities is briefly explained below. The exact order and content of these activities depends on the complexity of the project and the chosen tender procedure.		Each of these activities is briefly explained below. The exact order and content of these activities depends on the complexity of the project and the chosen tender procedure.

−	[[File:~~Requirements management~~.png]]	+	[[File:Requirements_management.png\|link=File:Requirements_management.png]]

−	= ~~Gathering~~ requirements =	+	= Capturing requirements =

	The first step is to collect and elicit the needs and requirements of the project’s [[Stakeholder\|stakeholders]] (i.e. the [[Construction_client\|construction client]], [[Facility_manager\|real estate/facility managers]], [[Building_user\|users]], interest groups). This can be done by means of workshops, interviews, surveys, the examination of reference projects and document analysis.		The first step is to collect and elicit the needs and requirements of the project’s [[Stakeholder\|stakeholders]] (i.e. the [[Construction_client\|construction client]], [[Facility_manager\|real estate/facility managers]], [[Building_user\|users]], interest groups). This can be done by means of workshops, interviews, surveys, the examination of reference projects and document analysis.
Line 113:		Line 113:
	* Monitoring progress and overall compliance rate per phase,		* Monitoring progress and overall compliance rate per phase,
	* Identifying and solving compliance gaps,		* Identifying and solving compliance gaps,
−
−

	= Managing change =		= Managing change =

80.62.116.228 at 10:55, 16 August 2021

2021-08-16T10:55:56Z

← Older revision		Revision as of 10:55, 16 August 2021
Line 3:		Line 3:
	The concept of requirements management (RM) is relatively new to the construction industry, but it is well established in other engineering disciplines such as software development and aerospace engineering. The concept can be defined as follows:		The concept of requirements management (RM) is relatively new to the construction industry, but it is well established in other engineering disciplines such as software development and aerospace engineering. The concept can be defined as follows:

−	RM is the process of ~~gathering~~, structuring, communicating, analysing and verifying the requirements for a facility, with the purpose of ensuring that this facility will fulfil the needs of the stakeholders who will use, own, acquire and operate it.	+	RM is the process of capturing, structuring, communicating, analysing and verifying the requirements for a facility, with the purpose of ensuring that this facility will fulfil the needs of the stakeholders who will use, own, acquire and operate it.

	RM clearly overlaps with the concept of [[Briefing\|briefing]], but there is a difference in scope. While briefing traditionally focuses on the development of a building programme in the early phases of a project (i.e. the [[Preparation_and_briefing\|briefing phase]]), RM is a continuous process in which requirements are defined, refined, updated and verified throughout all phases of a facility’s life cycle.		RM clearly overlaps with the concept of [[Briefing\|briefing]], but there is a difference in scope. While briefing traditionally focuses on the development of a building programme in the early phases of a project (i.e. the [[Preparation_and_briefing\|briefing phase]]), RM is a continuous process in which requirements are defined, refined, updated and verified throughout all phases of a facility’s life cycle.
Line 23:		Line 23:
	Effective RM consists of the following activities:		Effective RM consists of the following activities:

−	* ~~Gathering~~ requirements: collecting and eliciting requirements from project [[Stakeholder\|stakeholders]].	+	* Capturing requirements: collecting and eliciting requirements from project [[Stakeholder\|stakeholders]].
	* Structuring requirements: creating a clear and logically organised set of requirements.		* Structuring requirements: creating a clear and logically organised set of requirements.
	* Communicating requirements: communicating requirements with the design/delivery team.		* Communicating requirements: communicating requirements with the design/delivery team.
	* Analysing requirements: reviewing the clarity and feasibility of requirements.		* Analysing requirements: reviewing the clarity and feasibility of requirements.
−	* Linking requirements to BIM models: linking requirements to objects in 3D-design models.
	* Verifying compliance: checking whether solutions are compliant with the defined requirements.		* Verifying compliance: checking whether solutions are compliant with the defined requirements.
		+	* Linking requirements to BIM models: linking requirements to objects in 3D-design models.
	* Managing change: logging and evaluating changes and requests for change (RFCs).		* Managing change: logging and evaluating changes and requests for change (RFCs).
−	* ~~Evaluating~~ and ~~standardising~~ requirements: creating ~~standardized~~ requirements for new projects.	+	* Standardising and re-using requirements: creating standardised requirements for new projects.

	Each of these activities is briefly explained below. The exact order and content of these activities depends on the complexity of the project and the chosen tender procedure.		Each of these activities is briefly explained below. The exact order and content of these activities depends on the complexity of the project and the chosen tender procedure.

−	[[File:~~RequirementsManagement.png\|link=File:RequirementsManagement~~.png]]	+	[[File:Requirements management.png]]

	= Gathering requirements =		= Gathering requirements =
Line 89:		Line 89:
	* Discussing possible improvements with the client.		* Discussing possible improvements with the client.
	* Allocating requirements to the various project actors (contractor, architect, etc.).		* Allocating requirements to the various project actors (contractor, architect, etc.).
		+
		+	= Linking requirements to BIM models =
		+
		+	If captured in the right format, requirements can then be linked to [[BIM_model\|BIM models]]. The advantage of doing so is that requirements can be integrated into the design process. Requirements can be used as input for parametric or generative design processes or for the automated verification of design solutions (see also below). In particular, requirements concerning room quantities, room sizes and the placement of [[FF%26E\|FF&E]] items in rooms can easily be checked.
		+
		+	== Activities ==
		+
		+	* Creating data exports of requirements that are ‘readable’ for BIM models.
		+	* Executing ‘clash controls’ between design solutions and requirements.
		+	* Discussing outcomes with the client.

	= Verifying compliance =		= Verifying compliance =
Line 104:		Line 114:
	* Identifying and solving compliance gaps,		* Identifying and solving compliance gaps,

−	~~= Linking requirements to BIM models =~~

−	~~If captured in the right format, requirements can then be linked to [[BIM_model\|BIM models]]. The advantage of doing so is that the verification of design solutions can—in part—be automated.~~
−
−	In particular, requirements concerning room quantities, room sizes and the placement of [[FF%26E\|FF&E]] items in rooms can easily be checked. Quantitative requirements concerning walking distances and [[Human_comfort_in_buildings\|indoor climate]] can, in principle, also be verified automatically, but that is very much dependent on how the design team has set up its BIM models.
−
−	~~== Activities ==~~
−
−	* Creating data exports of requirements that are ‘readable’ for BIM models.
−	* Executing ‘clash controls’ between design solutions and requirements.
−	* Discussing outcomes with the client.

	= Managing change =		= Managing change =
Line 130:		Line 130:
	* Communicating changes to the stakeholders.		* Communicating changes to the stakeholders.

−	= ~~Evaluating~~ and ~~standardising~~ requirements =	+	= Standardising and re-using requirements =

	Having developed an effective set of requirements, it makes sense to standardise and reuse them. Large clients may, for example, develop requirements templates for specific room types (e.g. patient rooms or classrooms) or systems (e.g. access control systems). Standardisation will help to create consistency across projects and speed up the specification process.		Having developed an effective set of requirements, it makes sense to standardise and reuse them. Large clients may, for example, develop requirements templates for specific room types (e.g. patient rooms or classrooms) or systems (e.g. access control systems). Standardisation will help to create consistency across projects and speed up the specification process.
Line 145:		Line 145:
	= Summarising =		= Summarising =

−	RM is a fairly new phenomenon in the construction sector, and although it overlaps with the existing practice of [[Briefing\|briefing]], its scope is wider. RM covers the ~~definition~~, analysis, communication and verification of all project requirements, through all [[Project_stages\|phases]] of a project. Especially in large and complex projects, there is much to be gained from systematic RM, including avoiding design defects, budget overruns and delivery delays.	+	RM is a fairly new phenomenon in the construction sector, and although it overlaps with the existing practice of [[Briefing\|briefing]], its scope is wider. RM covers the capturing, analysis, communication and verification of all project requirements, through all [[Project_stages\|phases]] of a project. Especially in large and complex projects, there is much to be gained from systematic RM, including avoiding design defects, budget overruns and delivery delays.

	--[[User:BriefBuilder\|BriefBuilder]] 15:24, 19 Apr 2021 (BST)		--[[User:BriefBuilder\|BriefBuilder]] 15:24, 19 Apr 2021 (BST)

87.49.146.226 at 09:42, 28 June 2021

2021-06-28T09:42:55Z

← Older revision		Revision as of 09:42, 28 June 2021
Line 5:		Line 5:
	RM is the process of gathering, structuring, communicating, analysing and verifying the requirements for a facility, with the purpose of ensuring that this facility will fulfil the needs of the stakeholders who will use, own, acquire and operate it.		RM is the process of gathering, structuring, communicating, analysing and verifying the requirements for a facility, with the purpose of ensuring that this facility will fulfil the needs of the stakeholders who will use, own, acquire and operate it.

−	Rm clearly overlaps with the concept of [[Briefing\|briefing]], but there is a difference in scope. While briefing traditionally focuses on the development of a building programme in the early phases of a project (i.e. the [[Preparation_and_briefing\|briefing phase]]), RM is a continuous process in which requirements are defined, refined, updated and verified throughout all phases of a facility’s life cycle.	+	RM clearly overlaps with the concept of [[Briefing\|briefing]], but there is a difference in scope. While briefing traditionally focuses on the development of a building programme in the early phases of a project (i.e. the [[Preparation_and_briefing\|briefing phase]]), RM is a continuous process in which requirements are defined, refined, updated and verified throughout all phases of a facility’s life cycle.

	Another defining aspect of RM is that it not only focuses on the client’s functional and spatial requirements—as briefing primarily does—but also on the technical and operational requirements concerning the building’s [[Building_services\|technical systems]] and elements, the [[Construction_process\|delivery process]], and the [[Facility_management\|operation]] and [[Building_maintenance\|maintenance]] of the facility. As such, requirements management is targeted at the architect, plus all the other actors involved, such as project managers, engineers, expert consultants, (sub)contractors, suppliers, asset managers and service providers.		Another defining aspect of RM is that it not only focuses on the client’s functional and spatial requirements—as briefing primarily does—but also on the technical and operational requirements concerning the building’s [[Building_services\|technical systems]] and elements, the [[Construction_process\|delivery process]], and the [[Facility_management\|operation]] and [[Building_maintenance\|maintenance]] of the facility. As such, requirements management is targeted at the architect, plus all the other actors involved, such as project managers, engineers, expert consultants, (sub)contractors, suppliers, asset managers and service providers.

Editor at 16:22, 21 May 2021

2021-05-21T16:22:41Z

Show changes

Editor at 16:08, 21 May 2021

2021-05-21T16:08:13Z

Show changes

← Older revision		Revision as of 07:45, 7 March 2022
Line 1:		Line 1:
	= What is requirements management? =		= What is requirements management? =

−	The concept of requirements management (RM) is relatively new to the construction industry, but it is well established in other engineering disciplines such as software development and aerospace engineering. ~~The concept can be defined as follows:~~	+	The concept of requirements management (RM) is relatively new to the construction industry, but it is well established in other engineering disciplines such as software development and aerospace engineering.

−	RM is the process of capturing, structuring, communicating, analysing and verifying the requirements for a facility, with ~~the purpose of ensuring that this facility~~ will fulfil the needs of the stakeholders who will use, own, acquire and operate it.	+	RM is the process of capturing, structuring, communicating, analysing and verifying the requirements for a facility, with to ensure it will fulfil the needs of the stakeholders who will use, own, acquire and operate it.

−	RM ~~clearly~~ overlaps with the concept of ~~[[Briefing\|~~briefing]], but there is a difference in scope. While briefing traditionally focuses on ~~the development of a building programme in~~ the early phases of a project (i.e. the ~~[[Preparation_and_briefing\|~~briefing phase]]), RM is a continuous process in which requirements are defined, refined, updated and verified throughout all phases of a facility’s life cycle.	+	RM overlaps with the concept of briefing, but there is a difference in scope. While briefing traditionally focuses on the early phases of a project (i.e. the briefing phase), RM is a continuous process in which requirements are defined, refined, updated and verified throughout all phases of a facility’s life cycle.

	See the figure below (based on [http://purl.stanford.edu/gh076mt5924 Kiviniemi, 2005)] showing the difference between briefing (as a stage) and requirements management (as a continuous process).		See the figure below (based on [http://purl.stanford.edu/gh076mt5924 Kiviniemi, 2005)] showing the difference between briefing (as a stage) and requirements management (as a continuous process).

−	[[File:~~Process diagrams Arto Kiviniemi~~-01.png]]	+	[[File:Process_diagrams_Arto_Kiviniemi-01.png\|link=File:Process_diagrams_Arto_Kiviniemi-01.png]]

−	Another defining aspect of RM is that it not only focuses on the client’s functional and spatial requirements—as briefing primarily does—but also on the technical and operational requirements concerning the building’s ~~[[Building_services\|~~technical systems]] and elements, the ~~[[Construction_process\|~~delivery process]], and the ~~[[Facility_management\|~~operation]] and ~~[[Building_maintenance\|~~maintenance]] of the facility. As such, requirements management is targeted at the architect, plus all the other actors involved, such as project managers, engineers, expert consultants, ~~(sub)~~contractors, suppliers, asset managers and service providers.	+	Another defining aspect of RM is that it not only focuses on the client’s functional and spatial requirements—as briefing primarily does—but also on the technical and operational requirements concerning the building’s technical systems and elements, the delivery process, and the operation and maintenance of the facility. As such, requirements management is targeted at the architect, plus all the other actors involved, such as project managers, engineers, expert consultants, contractors, suppliers, asset managers and service providers.

−	Because of its broad scope, RM is often facilitated by ~~[[Requirements_management_application\|~~database tools]] that allow project teams to manage a multitude of different requirements in a systematic way.	+	Because of its broad scope, RM is often facilitated by database tools that allow project teams to manage a multitude of different requirements in a systematic way.

	= Why is RM important? =		= Why is RM important? =

−	Requirements are the basis for any design or engineering project. They define what is expected, needed and required from the project in relation to important quality aspects such as ~~[[Usability\|~~usability]], ~~[[Building_sustainability\|~~sustainability]], ~~[[Security\|~~safety and security]], ~~[[Human_comfort_in_buildings\|~~comfort]], ~~[[Wellbeing_and_buildings\|~~health]], ~~[[Design_flexibility\|~~flexibility]], efficiency and user experience.	+	Requirements are the basis for any design or engineering project. They define what is expected, needed and required from the project in relation to important quality aspects such as usability, sustainability, safety and security, comfort, health, flexibility, efficiency and user experience.

−	~~Especially in~~ complex construction projects (e.g. hospitals, labs, infrastructure), there is a lot to gain from a systematic approach to requirements. Such projects typically have to comply with a multitude of requirements, which makes it difficult to maintain an overview. This introduces the risk of requirements being overlooked or ignored, or not properly updated and verified during the project. The potential consequences include design defects, ~~[[Scope_creep\|~~scope creep]], budget overruns and delivery delays due to rework.	+	In complex construction projects (e.g. hospitals, labs, infrastructure), there is a lot to gain from a systematic approach to requirements. Such projects typically have to comply with a multitude of requirements, which makes it difficult to maintain an overview. This introduces the risk of requirements being overlooked or ignored, or not properly updated and verified during the project. The potential consequences include design defects, scope creep, budget overruns and delivery delays due to rework.

	RM aims to avoid such problems. The central idea is that clear and error-free requirements, combined with systematic compliance testing, helps to ensure that projects meet the needs of their stakeholders.		RM aims to avoid such problems. The central idea is that clear and error-free requirements, combined with systematic compliance testing, helps to ensure that projects meet the needs of their stakeholders.
Line 27:		Line 27:
	Effective RM consists of the following activities:		Effective RM consists of the following activities:

−	* Capturing requirements: collecting and eliciting requirements from project ~~[[Stakeholder\|~~stakeholders]].	+	* Capturing requirements: collecting and eliciting requirements from project stakeholders.
	* Structuring requirements: creating a clear and logically organised set of requirements.		* Structuring requirements: creating a clear and logically organised set of requirements.
	* Communicating requirements: communicating requirements with the design/delivery team.		* Communicating requirements: communicating requirements with the design/delivery team.
Line 42:		Line 42:
	= Capturing requirements =		= Capturing requirements =

−	The first step is to collect and elicit the needs and requirements of the project’s ~~[[Stakeholder\|~~stakeholders]] (i.e. the ~~[[Construction_client\|~~construction client]], ~~[[Facility_manager\|real estate/~~facility managers]], ~~[[Building_user\|~~users~~]],~~ interest groups). This can be done by means of workshops, interviews, surveys, the examination of reference projects and document analysis.	+	The first step is to collect and elicit the needs and requirements of the project’s stakeholders (i.e. the construction client, facility managers, users and other interest groups). This can be done by means of workshops, interviews, surveys, the examination of reference projects and document analysis.

−	These activities are classic ~~[[Briefing\|~~briefing]] activities, preferably conducted in the project’s briefing stage. But requirements can also be gathered in a more ‘agile’ way, on an as-needed basis, at later stages in the project.	+	These activities are classic briefing activities, preferably conducted in the project’s briefing stage. But requirements can also be gathered in a more ‘agile’ way, on an as-needed basis, at later stages in the project.

−	== Activities ==	+	Activities

	* Stakeholder mapping/identification.		* Stakeholder mapping/identification.
Line 56:		Line 56:
	= Structuring requirements =		= Structuring requirements =

−	In this step, the information that has been collected ~~in the earlier step—which~~ is often quite ~~‘fuzzy’—is~~ structured and refined. The goal is to produce a single, clear and well-organised set of requirements. Vague requirements are made specific. Inconsistencies are resolved. Missing requirements are added. Duplicate requirements are removed.	+	In this step, the information that has been collected - which is often quite ‘fuzzy’ - is structured and refined. The goal is to produce a single, clear and well-organised set of requirements. Vague requirements are made specific. Inconsistencies are resolved. Missing requirements are added. Duplicate requirements are removed.

	For simple projects, this exercise can be done in Excel or Word. For more complex projects, it will be useful to have a database tool that can handle large numbers of requirements.		For simple projects, this exercise can be done in Excel or Word. For more complex projects, it will be useful to have a database tool that can handle large numbers of requirements.

−	== Activities ==	+	Activities

	* Making breakdown structures of requested spaces and/or systems.		* Making breakdown structures of requested spaces and/or systems.
−	* Making requirements ‘smart’ (i.e. adding explicit values and units of ~~measure~~).	+	* Making requirements ‘smart’ (i.e. adding explicit values and units of measurement).
	* Identifying and solving possible inconsistencies, removing duplicates.		* Identifying and solving possible inconsistencies, removing duplicates.
	* Prioritising requirements (must-have vs. nice-to-have).		* Prioritising requirements (must-have vs. nice-to-have).