Input specification vs output specification - Revision history

Designing Buildings at 07:10, 4 March 2021

2021-03-04T07:10:30Z

← Older revision		Revision as of 07:10, 4 March 2021
Line 26:		Line 26:
	* Tender process.		* Tender process.

−	[[Category:~~Definitions~~]] [[Category:~~DCN_Definition~~]] [[Category:Contracts_/_payment]] [[Category:Design]] [[Category:Procurement]]	+	[[Category:DCN_Definition]] [[Category:DCN_Guidance]] [[Category:Definitions]] [[Category:Contracts_/_payment]] [[Category:Design]] [[Category:Procurement]]

Designing Buildings at 08:16, 19 May 2020

2020-05-19T08:16:14Z

← Older revision		Revision as of 08:16, 19 May 2020
Line 1:		Line 1:
−	Traditional specifications are ‘input specifications’. They are prescriptive, that is, they describe in detail the products, materials and work (the inputs) required by a contract. Typically, the development of the solution required by the contract is complete and no (or little) further development is required by the supplier. The specification is ~~conserved~~ to be a ‘closed specification’.	+	Traditional specifications are ‘input specifications’. They are prescriptive, that is, they describe in detail the products, materials and work (the inputs) required by a contract. Typically, the development of the solution required by the contract is complete and no (or little) further development is required by the supplier. The specification is considered to be a ‘closed specification’.

−	Prescriptive input specifications give the client ~~much more~~ certainty about the end product when making investment decisions, but place a greater burden on them to ensure the product has been thoroughly considered, developed and described. They tend to be used where a very specific end result required.	+	Prescriptive input specifications give the client certainty about the end product when making investment decisions, but place a greater burden on them to ensure the product has been thoroughly considered, developed and described. They tend to be used where a very specific end result required.

−	Output specifications define only the outcomes (or outputs) that are required ~~from~~ the contract, that is, what it will enable the client to do. They do not attempt to address how those outputs might be achieved. For example, an output specification might require the provision of a space for teaching 30 primary pupils, but it would not specify the nature of the space, the types of doors and windows etc. The standard for what is required might be defined, for example, by reference to performance targets.	+	Output specifications define only the outcomes (or outputs) that are required by the contract, that is, what it will enable the client to do. They are open specifications that do not attempt to address how those outputs might be achieved. For example, an output specification might require the provision of a space for teaching 30 primary pupils, but it would not specify the nature of the space, the types of doors and windows etc. The standard for what is required might be defined, for example, by reference to performance targets.

−	It is argued that output ~~specifciations~~ can get the best value from the supply team by allowing them to adopt innovative solutions to the client's requirements and reduce whole-life costs rather than simply developing the client's pre-conceived solutions at the lowest price.	+	It is argued that output specifications can get the best value from the supply team by allowing them to adopt innovative solutions to the client's requirements and reduce whole-life costs rather than simply developing the client's pre-conceived solutions at the lowest price.

	For more information see: Output-based specification.		For more information see: Output-based specification.
Line 26:		Line 26:
	* Tender process.		* Tender process.

−	[[Category:Definitions]] [[Category:Contracts_/_payment]] [[Category:Design]] [[Category:Procurement]]	+	[[Category:Definitions]] [[Category:DCN_Definition]] [[Category:Contracts_/_payment]] [[Category:Design]] [[Category:Procurement]]

Designing Buildings: Created page with "Traditional specifications are ‘input specifications’. They are prescriptive, that is, they describe in detail the products, materials and work (the inputs) required by a con..."

2020-05-19T08:13:07Z

Created page with "Traditional specifications are ‘input specifications’. They are prescriptive, that is, they describe in detail the products, materials and work (the inputs) required by a con..."

New page

Traditional specifications are ‘input specifications’. They are prescriptive, that is, they describe in detail the products, materials and work (the inputs) required by a contract. Typically, the development of the solution required by the contract is complete and no (or little) further development is required by the supplier. The specification is conserved to be a ‘closed specification’.

Prescriptive input specifications give the client much more certainty about the end product when making investment decisions, but place a greater burden on them to ensure the product has been thoroughly considered, developed and described. They tend to be used where a very specific end result required.

Output specifications define only the outcomes (or outputs) that are required from the contract, that is, what it will enable the client to do. They do not attempt to address how those outputs might be achieved. For example, an output specification might require the provision of a space for teaching 30 primary pupils, but it would not specify the nature of the space, the types of doors and windows etc. The standard for what is required might be defined, for example, by reference to performance targets.

It is argued that output specifciations can get the best value from the supply team by allowing them to adopt innovative solutions to the client's requirements and reduce whole-life costs rather than simply developing the client's pre-conceived solutions at the lowest price.

For more information see: Output-based specification.

= Related articles on Designing Buildings Wiki =

* Briefing documents.
* Feasibility studies.
* Final specifications.
* Insulation specification.
* Outline specification.
* Output specification
* Output-based specification.
* Performance specification.
* Prescriptive specification.
* Procurement.
* Service level specification.
* Specification.
* Tender documentation.
* Tender process.

[[Category:Definitions]] [[Category:Contracts_/_payment]] [[Category:Design]] [[Category:Procurement]]