SIST EN 16271:2014

2003-01.Slovenski inštitut za standardizacijo. Razmnoževanje celote ali delov tega standarda ni dovoljeno.Upravljanje vrednosti - Funkcijski opis potreb in funkcijska specifikacija zmogljivosti - Zahteve za opisovanje in vrednotenje potreb, ki jim je treba zadostiti v okviru procesa nakupovanja ali nabave izdelkaValue Management - Funktionale Beschreibung der Bedürfnisse und funktionale Leistungsbeschreibung - Anforderungen an das Beschreiben und Validieren der Bedürfnisse, die während der Erstellung oder des Erwerbs eines Produktes zu befriedigen sindManagement par la valeur - Expression fonctionnelle du besoin et cahier des charges fonctionnel - Exigences pour l'expression et la validation du besoin à satisfaire dans le processus d'acquisition ou d'obtention d'un produitValue management - Functional expression of the need and functional performance specification - Requirements for expressing and validating the need to be satisfied within the process of purchasing or obtaining a product03.100.40Raziskave in razvojResearch and development03.100.10Nabava. Dobava. LogistikaPurchasing. Procurement. Management of stockICS:Ta slovenski standard je istoveten z:EN 16271:2012SIST EN 16271:2014en01-marec-2014SIST EN 16271:2014SLOVENSKI
STANDARD



SIST EN 16271:2014



EUROPEAN STANDARD NORME EUROPÉENNE EUROPÄISCHE NORM
EN 16271
December 2012 ICS 03.100.10 English Version
Value management - Functional expression of the need and functional performance specification - Requirements for expressing and validating the need to be satisfied within the process of purchasing or obtaining a product
Management par la valeur - Expression fonctionnelle du besoin et cahier des charges fonctionnel - Exigences pour l'expression et la validation du besoin à satisfaire dans le processus d'acquisition ou d'obtention d'un produit
Value Management - Funktionale Beschreibung der Bedürfnisse und funktionale Leistungsbeschreibung - Anforderungen an das Beschreiben und Validieren der Bedürfnisse, die während der Erstellung oder des Erwerbs eines Produktes zu befriedigen sind This European Standard was approved by CEN on 27 October 2012.
CEN members are bound to comply with the CEN/CENELEC Internal Regulations which stipulate the conditions for giving this European Standard the status of a national standard without any alteration. Up-to-date lists and bibliographical references concerning such national standards may be obtained on application to the CEN-CENELEC Management Centre or to any CEN member.
This European Standard exists in three official versions (English, French, German). A version in any other language made by translation under the responsibility of a CEN member into its own language and notified to the CEN-CENELEC Management Centre has the same status as the official versions.
CEN members are the national standards bodies of Austria, Belgium, Bulgaria, Croatia, Cyprus, Czech Republic, Denmark, Estonia, Finland, Former Yugoslav Republic of Macedonia, France, Germany, Greece, Hungary, Iceland, Ireland, Italy, Latvia, Lithuania, Luxembourg, Malta, Netherlands, Norway, Poland, Portugal, Romania, Slovakia, Slovenia, Spain, Sweden, Switzerland, Turkey and United Kingdom.
EUROPEAN COMMITTEE FOR STANDARDIZATION
COMITÉ EUROPÉEN DE NORMALISATION EUROPÄISCHES KOMITEE FÜR NORMUNG
Management Centre:
Avenue Marnix 17,
B-1000 Brussels © 2012 CEN All rights of exploitation in any form and by any means reserved worldwide for CEN national Members. Ref. No. EN 16271:2012: ESIST EN 16271:2014



EN 16271:2012 (E) 2 Contents Page Foreword .40Introduction .50.1General .50.2Basis .50.3Organisation and presentation of processes and deliverables .50.4Functional need analysis (FNA) .60.5Functional Need Expression (FNE) .70.6FPS .70.7Fields of use .70.8Relationships with Value Analysis and Design To Objective (DTO) .81Scope .92Normative references .93Terms and definitions . 104Requirements applicable to the deliverable “Functional Need Expression” . 144.1General . 144.2Adaptation of the requirements to the FNE usage context . 154.3Global Need Definition . 154.3.1(FNE.01) Global need formulation . 154.3.2(FNE.02) Product integration into a 'larger' system . 164.4Definition of the strategic elements of the target market and product outlet (Customer side) . 164.4.1(FNE.03) Definition of the economic stakes . 164.4.2(FNE.04) List of the inquirer's strategic data . 164.4.3(FNE.05) Fields of processed needs . 174.4.4(FNE.06) study of each targeted functional coverage. 174.5Highlighting of Principles/Concepts Selected Beforehand . 174.5.1(FNE.07) Statement of principles or concepts selected beforehand . 174.6Description of the functions to be provided and their compliance with the constraints . 184.6.1Depth, fineness of analysis (granulation) and field to be covered . 184.6.1.1(FNE.08) Identification of the fineness (granulation) of the Need description . 184.6.2Life cycle and interacting agents . 184.6.2.1(FNE.09) Selection and description of life cycle phases . 184.6.2.2(FNE.10) List and description of interacting agents . 184.6.3Description of the functions and the constraints . 194.6.3.1(FNE.11) List of user-related functions . 194.6.3.2(FNE.12) Technical neutrality of user-related functions . 194.6.3.3(FNE.13) Organisation of functions . 194.6.3.4(FNE.14) Function characterisation . 204.6.3.5(FNE.15) Function ranking/weighting . 204.6.3.6(FNE.16) Identification of mandatory and possible additional characterisation elements . 204.6.3.7(FNE.17) Possible functional variations . 214.6.3.8(FNE.18) Organised list and constraints description . 215Requirements applicable to the deliverable “Functional Performance Specification” . 215.1General . 215.2FPS contents . 225.2.1(FPS.01) Mandatory sections of an FPS . 225.2.2(FPS.02) Other sections of an FPS . 235.2.3(FPS.03) Structure adaptation to the defined usage of the FPS . 235.3Characteristics defining the quality of an FPS . 245.3.1(FPS.04) Compliance with the processes . 245.3.2(FPS.05) Legibility and understanding by the recipient . 24SIST EN 16271:2014



EN 16271:2012 (E) 3 5.3.3(FPS.06) Capacity to support the usage phase . 246Requirements applicable to the three processes (the FNA process, the process for the drawing up of the FPS, FPS utilisation process) . 246.1General . 246.2Common requirements applicable to the three processes . 256.2.1(PROC.01) Framing of the subject of the action . 256.2.2(PROC.02) Supported decision for starting an action . 256.2.3(PROC.03) Mandate of the person in charge of the action . 256.2.4(PROC.04) Mobilisation of resources and implementation of an operational structure . 266.2.5(PROC.05) Search for information and consolidation . 266.2.6(PROC.06) Handling of possible conflicts or contradictions . 266.2.7(PROC.07) Traceability of the action . 266.3Particular requirements applicable to the FNE generation process: Functional Need Analysis . 266.3.1(PROC.08) Adaptation of the resources to the need to be described . 266.3.2(PROC.09) FNE validation . 276.4Particular requirements applicable to the drawing up process of the functional performance specification . 276.4.1General . 276.4.2(PROC.10) FPS integration into the process used to obtain a product . 276.4.3(PROC.11) Selection of the FNE elements to be integrated into the FPS . 276.4.4(PROC.12) Transmissibility to a third party . 286.4.5(PROC.13) FPS validation . 286.5Particular requirements applicable to the process implemented to make use of the functional performance specification . 286.5.1General . 286.5.2(PROC.14) Search for and selection of potential providers . 296.5.3(PROC.15) FPS appropriation by a provider . 296.5.4(PROC.16) Drawing up of the final version of the FPS . 296.5.5(PROC.17) Suggestion processing recording . 296.5.6(PROC.18) Intellectual property, rights of the partners . 306.5.7(PROC.19) Arbitration processing . 306.5.8(PROC.20) Examination of proposals . 30Annex A (informative)
The variety of situations where FNE and FPS can be used . 31A.1General . 31A.2Universality . 31A.3Initial condition of the object under study . 31A.4Use of the FNA and FNE in a VA approach. 32A.5Use of the FNE and the FPS in the process used to obtain a product . 32A.6Use of the FPS with Design To Objective . 33A.7Relationships with other methods . 33Annex B (informative)
Conditions of use of deliverables . 34B.1Background for the drawing up of a FNE . 34B.2Variety of FPS (or FNE) usage cases . 34B.3Compatibility with the rules applicable to public contracts . 35Bibliography . 36 SIST EN 16271:2014



EN 16271:2012 (E) 4 Foreword This document (EN 16271:2012) has been prepared by Technical Committee CEN/TC 279 “Value management, value analysis, functional analysis”, the secretariat of which is held by AFNOR. This European Standard shall be given the status of a national standard, either by publication of an identical text or by endorsement, at the latest by June 2013, and conflicting national standards shall be withdrawn at the latest by June 2013. Attention is drawn to the possibility that some of the elements of this document may be the subject of patent rights. CEN [and/or CENELEC] shall not be held responsible for identifying any or all such patent rights. According to the CEN/CENELEC Internal Regulations, the national standards organisations of the following countries are bound to implement this European Standard: Austria, Belgium, Bulgaria, Croatia, Cyprus, Czech Republic, Denmark, Estonia, Finland, Former Yugoslav Republic of Macedonia, France, Germany, Greece, Hungary, Iceland, Ireland, Italy, Latvia, Lithuania, Luxembourg, Malta, Netherlands, Norway, Poland, Portugal, Romania, Slovakia, Slovenia, Spain, Sweden, Switzerland, Turkey and the United Kingdom. SIST EN 16271:2014



EN 16271:2012 (E) 5 0 Introduction 0.1 General This European Standard states the conditions for the successful implementation of the Functional Need Analysis, Functional Need Expression and Functional Performance Specification and determines the compliance requirements for the parties involved. It extends the generic standard on Value Management, EN 12973. It separately presents the requirements applicable to the processes that have to be implemented and those applicable to the deliverables derived from these processes.
0.2 Basis In highly competitive markets, the durability and the development of organisations depend on their capacity to provide competitive products which are best suited to satisfy the need, whether expressed or implicit, of the users. The statement of the need in a functional form, i.e. in terms of purpose, without reference to solutions (technical, administrative, procedural, and organisational, etc.) likely to satisfy it, ensures there is every chance that competitive and innovative solutions will emerge at the design stage. The statement of the need in a functional form is essential. It permits the expression of the:  reference of this need in validated terms (in terms of obligations, expected services, rather than in terms of means) which can be used to control the evolution of this reference at the later stages of the product's life;  level of importance of the main requirements which make up the cost of a product. Using a structured need statement approach in a functional form promotes the:  offer of competitive and innovative products;  mobilisation of all the interested parties to obtain a unified expression of the need which can be used at each step - from the development to the evaluation of offers satisfying the same need;  dialogue between the partners, while respecting the responsibilities of each partner and with a clearer relationship between the customer and the provider. This European Standard addresses the quality of specification under the responsibility of the enquirer, the handling of the customer/provider relationship and the search for the optimum solution in relation to the expressed need. The standard also addresses the performance levels and the grade of quality required by the enquirer. 0.3 Organisation and presentation of processes and deliverables Figure 1 below shows schematically the relationship between the three key processes (Functional Need Analysis (FNA) process, the Process for drawing up the Functional Performance Specification (FPS), and the FPS utilisation process:  The Functional Need Analysis (FNA) process: this enables the defining of the result named Functional Need Expression (FNE).  The process for the drawing up of the Functional Performance Specification (FPS) from the FNE: this process generates a document (FPS) used within the framework of external enquiries, calls for tenders, the Design To Objective (DTO) approach, or internally by certain organisations. SIST EN 16271:2014



EN 16271:2012 (E) 6  The FPS utilisation process: this enables, from the initial FPS, a stabilised and final version of the selected need (FPS reference version) to be defined so that the future product shall satisfy.
Figure 1 — Process organisation and relations between deliverables Annex B proposes a detailed presentation of the processes and deliverables highlighting the respective roles of the owner or project manager and of designers/producers. 0.4 Functional need analysis (FNA) The FNA is a process which applies to a physical object, as well as an organisation, a service, an intellectual service, a process, software, an information system or any combination of the preceding elements. The functions (User Related Functions) that any product provides shall be defined before it is made, thus justifying its acquisition or, more generally, its procurement. The FNA:  highlights and takes into account the point of view of all the interested parties involved;  relates to the entire life cycle, from upstream (supply, storage etc.), utilisation, to downstream (maintenance in operational conditions, upgrading and end-of-life operations) phases, and thus introduces the consideration of time;  defines the expected results and not the means to be implemented. The FNA makes it possible to avoid the premature freezing of technical solutions. Therefore, the FNA is fully in line with the perspective of a sustainable development since it takes account of all the interests involved and contributes to optimising resources by focusing on what is essential: to determine sound and acceptable objectives prior to any action. SIST EN 16271:2014



EN 16271:2012 (E) 7 0.5 Functional Need Expression (FNE) The FNE materialises the results obtained with the FNA. The FNE:  organises information according to a rigorous and detailed explanatory logic. It gives an assessment of the elements, enabling decision-making with full knowledge of the facts;  makes it possible to initiate the design and the making of the product which is the most appropriate to provide the desired service, the most suitable for the expected use, with the best suitable performance;  is a reference of the customer need for all the product development steps. Seen from this perspective, the FNE complies with the transparency or visibility principle defined in the sustainable development approaches. 0.6 FPS The FPS is a structured and detailed presentation of the need based on the FNE. It enables inquirers to begin a dialogue (or even an initial negotiation) with providers or developers responsible for meeting an identified and specified need. The FPS:  is used to introduce and make competitive dialogue easier between owners or project managers and providers since they raise a legitimate issue and require a tailor-made response;  leaves to the provider a broad initiative in the search for original and efficient solutions with regard to the quality/price/lead-times/risks ratios;  allows all parties to appreciate the differences between the solutions and the need, and makes comparisons easier between competing solutions;  allows verification and evaluation of the effective results by reference to an expressed expectation. The implementation of an approach with the FPS changes the 'customer-provider' relationship from an obligation to respond to a predetermined technical specification to an obligation to achieve a result. 0.7 Fields of use The FNA, FNE and FPS concepts are applicable whenever any entity (organisation or an internal department thereof etc.) expresses a request to another entity which has sufficient capacities and competences to propose to it a product as a response. The FNE establishes the accurate definition of the need to be satisfied by the product:  either within the framework of relationships between a customer and their providers; or  between two entities belonging to the same organisation; or  within the framework of work groups where it is an integral part of various methods (value analysis, dependability, security analysis, etc.); or  within the framework of larger and 'integrating' managerial policies and approaches, such as sustainable development, system engineering, design to objective, etc. These concepts are applicable to all economic sectors, including the service sector. The desired end products or projects may be intended for public or professional use, for investment or for consumption, based on current or future needs. The required products/services may consist of mature products (consisting of subsets at different levels of maturity) as well as products that come from research and exploration. SIST EN 16271:2014



EN 16271:2012 (E) 8 The FNE may be successfully applied to projects of any size and complexity by adapting this approach.
0.8 Relationships with Value Analysis and Design To Objective (DTO) The processes and documents produced in compliance with the recommendations of this standard are also integrated into other Value Management approaches. The Value Analysis and Design To Cost/Objective which are core methods of the Value Management (EN 12973) are particularly concerned. SIST EN 16271:2014



EN 16271:2012 (E) 9 1 Scope This European Standard is a tool to be used by any partner wishing to draft and make use of the reference of any need to be satisfied. In light of this purpose, it: a) states the interests and fields of application of the Functional Need Analysis, Functional Need Expression and Functional Performance Specification concepts; b) determines the contents requirements of the functional need expression structured in four main bodies: 1) global definition of the need; 2) definition of the strategic elements and the consolidation of needs; 3) highlighting of principles, and concepts chosen beforehand, if any; 4) description of the functions to be provided and of the constraints to be complied with. c) determines the requirements on the composition and contents of a functional performance specification and those used to assess its quality, i.e. requirements concerning: 1) its contents and structure; 2) the assessment of the characteristics which define its quality. d) precisely specifies, in the form of requirements: 1) the conditions for a successful Functional Need Analysis (FNA) action producing a deliverable called Functional Need Expression (FNE); 2) the conditions for drawing up a successful functional performance specification (FPS) based on the available functional need expression (FNE); 3) the conditions of use of the FPS by the inquirer and the various partners involved (the provider for example); e) specifies the various conditions of use of these concepts. This European Standard is applicable in principle to all product types and dimensions (from the elementary tangible object to the definition of an organisation and its strategy, including the systems or processes and activities implemented by an organisation) and to all sectors of activity (including the service sector). Lastly it is applicable within the framework of relationships between external partners (between a customer and its providers) or internally (between two entities of the same organisation for example). 2 Normative references The following documents, in whole or in part, are normatively referenced in this document and are indispensable for its application. For dated references, only the edition cited applies. For undated references, the latest edition of the referenced document (including any amendments) applies. EN 1325-1:1996, Value Management, Value Analysis, Functional Analysis vocabulary  Part 1: Value Analysis and Functional Analysis EN 1325-2:2004, Value Management, Value Analysis, Functional Analysis vocabulary  Part 2: Value Management SIST EN 16271:2014



EN 16271:2012 (E) 10 3 Terms and definitions For the purposes of this document, the terms and definitions in EN 1325-1:1996 and EN 1325-2:2004 and the following apply. 3.1 user person or organisation for which the product is designed and which exploits at least one of its functions at any time during its life cycle Note 1 to entry: A user can be an external or internal customer. 3.2 need what is necessary for or desired by the user Note 1 to entry:
A need can be declared or undeclared; it can be an existing or a potential one. 3.3 product result of activities or processes Note 1 to entry:
A product can include service, hardware, processed materials, software or a combination thereof. Note 2 to entry:
A product can be tangible (e.g. assemblies or processed materials) or intangible (e.g. knowledge or concepts) or a combination thereof. Note 3 to entry:
A product can be either intended (e.g. offering to customers) or unintended (e.g. pollutant or unwanted effects). [SOURCE: EN ISO 9000:2005, modified] 3.4 constraint characteristic, result or design feature which is made compulsory or has been prohibited for any reason, with no alternative possibility being left Note 1 to entry:
Constraints are generally restrictions on the choice of solutions in a VA project. Note 2 to entry:
The constraints can result from laws, from standards, from the demand of the market. These
...