EN 16271:2012

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
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

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

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

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

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

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 elements contribute to the characterisation of the functions. It is wise to record the relationship between them and the functions to which they apply (traceability). Note 3 to entry:
Given the importance which the constraints can have on the definition of the product, it is good practice to justify any specified constraint. Note 4 to entry:
To facilitate the reading of the results of the Function Analysis, constraints can be included in a particular chapter. 3.5 enquirer person or organisation in search of a product and who is responsible for issuing the Functional Performance Specification, with a view to its purchase or requisition and use by itself or by others 3.6 designer - producer (of a product/system) entity responsible for the design of a product/system which, in addition to the technical requirements, takes the risks, the costs, and the realisation and development times into account SIST EN 16271:2014

The designer - producer is either an external organisation, or a department from the same organisation as the inquirer. Note 2 to entry:
In certain trades, he/it is generally called a ‘consulting engineer’. 3.7 project owner
entity responsible for the definition of the need and for the specified objective, which takes charge of the management of the project, the selection of the designers, pilots the action in partnership with them, and assures the finances of the activity Note 1 to entry:
If it is not the end user of the studied product, the project owner will give the designer(s) all the information available on needs to be satisfied to allow the search for a real optimisation. Note 2 to entry:
The entity name used can vary according to the particular business sector. In its function of entity in charge of the definition of the need, it is also called "an enquirer” or "Project owner". 3.8 function effect of a product or of one of its constituents 3.9 Function Analysis
FA process that describes completely the functions and their relationships, which are systematically characterised, classified and evaluated Note 1 to entry:
The function structure is a part of the result of Function Analysis. Note 2 to entry:
Function Analysis covers two approaches: the Functional Need Analysis (or External Function analysis) and the Technical Function Analysis (or Internal Function analysis). Note 3 to entry:
Function Analysis combines problem definition and problem solving. 3.10 Functional Need Analysis
FNA part of function analysis which describes the need that the product shall satisfy in the form of user-related functions and constraints Note 1 to entry:
Sometimes FNA is referred to as 'External Function Analysis' or ‘Customer Function Analysis’. 3.11 Technical Function Analysis
TFA part of function analysis which contributes to studying and formalising the product architecture by identifying the product-related functions of the sub-assemblies or components Note 1 to entry:
Sometimes TFA is referred to as ‘Internal Function Analysis'. 3.12 Functional Need Expression
FNE result of a Functional Need Analysis and the reference in obtaining a product Note 1 to entry:
The Functional Need Expression is used as a basis to draw up the main part of the FPS, if formalised. Note 2 to entry:
Obtaining a product may consist for example in the acquisition, in exploratory studies, or in a development followed by a supply. SIST EN 16271:2014

URF effect expected of a product, or performed by it, in order to meet a part of the need of a definite user Note 1 to entry:
The users and the market are only interested in user related functions. Note 2 to entry:
Customer needs and specifications may be expressed as a set of user related functions. Note 3 to entry:
User related functions are either use or esteem functions. 3.14 product related function
PRF effect of a constituent of a product or the effect between the constituents of the product for the purpose of performing user related functions Note 1 to entry:
When choosing an overall solution, the designer or organiser determines the product related functions sometimes called internal functions. Note 2 to entry:
The product related functions of a complete product or system can be the user related functions of a constituent element used into the composition of this product.
Note 3 to entry:
The product related functions can be related to the available technology. 3.15 Function Structure arrangement of functions resulting from Function Analysis, which can be presented in the forms of a tree, or of a diagram, giving a complete, visual, written presentation Note 1 to entry:
When product related functions are considered, the function structure shows the way in which the functions interact. 3.16 Functional Performance Specification
FPS document in which the enquirer expresses his needs (or those which he is instructed to express) in terms of user related functions and constraints Note 1 to entry:
For each of these functions, evaluation criteria are defined together with their performance levels. A certain degree of flexibility is assigned to each one. Note 2 to entry:
In its role as need definition manager, the inquirer is also called ‘owner or project manager' or 'procuring authority' or “contracting authority”.
3.17 granulation measure of fineness, detail level (zoom, magnifying glass, etc.), richness of the elementary information chosen to make an FNE Note 1 to entry:
Granulation needs to be chosen carefully: a too coarse granulation gives a simplistic description with no added value. On the one hand, a too fine granulation may implicitly impose solution groups, restricting the solution search field; on the other hand it may require hardly justifiable heavy work. Note 2 to entry:
In theory, proposed by the action manager to reach the expected results; it will be validated by the decision-makers. Note 3 to entry:
The project maturity and progress stage are essential elements upon which the chosen FNE granulation level depends. SIST EN 16271:2014

'Withdrawal' needs to be understood as the final elimination of the product beyond its withdrawal from service. [SOURCE: ISO/IEC 15288:2002, modified] 3.19 life situation product usage condition (for transport, handling, storage, maintenance, various missions, etc.) with the respective occurrences and duration [SOURCE: NF X 50-144-1:2000, modified] 3.20 interactive agent element of the product environment interacting with the product during its life cycle (systemic point of view) Note 1 to entry:
Two interactive agent types can be distinguished. Human interactive agents: individual: called Interested party, and tangible and intangible interactive agents: called environmental interactive agents. Note 2 to entry:
The interested parties are the people or groups of people involved or affected by a product from the time when it exists, which includes the:  stakeholders, which include the customers, users of this product and organisations contributing to its distribution, maintenance in working order until the withdrawal from service and possible dismantling of the product;  impacted parties which includes those in relationship with it without using it or supporting it. Note 3 to entry:
Some interactive agents are stable. Others are flexible and will take part in the adjustment between the Need (from the initial Need to the selected Need) and the ability of the Product to deliver. Note 4 to entry:
The tracking of evolution for an interactive agent contributes to the traceability of requirements. 3.21 evaluation criterion characteristic used to evaluate the performance expected from, or provided by the VA subject Note 1 to entry:
Evaluation criteria can be specified for one or more functions or for the whole product. Note 2 to entry:
Several evaluation criteria are generally necessary to precisely specify a function. 3.22 level of an evaluation criterion position on the scale of measurement or estimation for a function evaluation criterion Note 1 to entry:
This level can be the one sought as a goal set in the functional performance specification for instance. Alternatively, it can be the level reached by a proposed technical solution which is used to formulate a judgement of the solution. 3.23 flexibility of a level set of indications given by the enquirer regarding the possibility of adjusting the level sought for an evaluation criterion Note 1 to entry:
This flexibility can be expressed in:  a qualitative way ("classes" of flexibility); SIST EN 16271:2014

For example, define four classes of flexibility:  no flexibility (F0): imperative level;  low flexibility (F1): little negotiable level;  moderate flexibility (F2): negotiable level;  large flexibility (F3): optional level. Note 2 to entry:
The qualitative aspect of such an indication allows an easier expression of the levels of the evaluation criteria and is often adopted by the enquirer. 3.25 limit of acceptance level of a criterion of acceptance below which, or above which according to the case, the need is considered unsatisfied Note 1 to entry:
Any solution not respecting a limit of acceptance of a user related function is unacceptable. Therefore, the enquirer needs to be extremely aware of the consequences of the choice of the limits. Note 2 to entry:
A limit of acceptance can also be defined by a deviation, absolute or relative, positive or negative, with regard to the requested level of the evaluation criterion. Note 3 to entry:
In certain sectors, the choice of the limits of acceptance can be expressed by means of standard classes. 3.26 trade off rate or “exchange rate” ratio declared acceptable by the enquirer between the variation of the price (or cost) and the corresponding variation of the level of a function evaluation criterion, or ratio between the levels variations of two or more function evaluation criteria Note 1 to entry:
In the case of a Function Performance Specification, the reference point of the variations is defined by the objectives of costs and levels of evaluation criteria; these variations are the deviations. Note 2 to entry:
It is acceptable to express the deviations in relative value. Note 3 to entry:
The specified trade off ratio relationships can result from calculations of optimisation, from enquiries with users, with desires of incentive, or other consideration of the enquirer. 4 Requirements applicable to the deliverable “Functional Need Expression”
4.1 General This section draws up the list of requirements that shall be satisfied by any Functional Need Expression (FNE) resulting from a functional need analysis. This section draws up the list of requirements that any Functional Need Expression (FNE) resulting from a functional need analysis shall satisfy. SIST EN 16271:2014

d) Definition of the functions to be provided and of the constraints to be complied with (see 4.6)
The set of requirements defined in this section makes it possible to establish a rigorous functional expression consistent with the project objectives (inquirer) and in accordance with the usage that will be made of it by the project partners (inquirer and designer). Each requirement is presented as follows:  requirement title expressing the purpose and its number in brackets;  the requirement to be complied with (shall +verb);  notes used to detail the requirements (should + verb);  purpose that bears out the interest of the requirement by formalising the aimed objective. At the end of the document, a detailed summary will be presented, in an informative annex, listing all the requirements with their numbering. 4.2 Adaptation of the requirements to the FNE usage context The compliance with all the requirements applicable to the FNE contents shall be adapted to the expected usage context. Purpose: to adapt the efforts and results to the usage expected for the FNE. 4.3 Global Need Definition 4.3.1 (FNE.01) Global need formulation The FNE shall give a synthetic presentation of the Need that the product shall meet to satisfy the targeted Market. NOTE The synthetic need expression describes the bull’s eye of the problem to be handled (definition of What). SIST EN 16271:2014
...