FprCEN/TS 17011-3

Electronic Public Procurement - Architecture - Part 3: Customisation Guideline

This document describes:
-   the rationale for building customisation supporting business cases that are specific to their business environment while maintaining organisational and semantic interoperability with the TC 440 specifications;
-   the difference between Usage specification and Extension specification;
-   a methodology on how to define customisations on:
-   BII Transaction specification,
-   Business rules,
-   Code lists;
-   how to claim compliance or conformance to a customisation of a TC 440 specification;
-   the connection to the eProcurement Ontology project.
This specification does not describe the detailed process of building an extension.

Elektronische öffentliche Auftragsvergabe - Architektur - Teil 3: Leitfaden für die Anpassung

Dieses Dokument beschreibt:
   die Begründung für die Entwicklung von Anpassungen, um spezifische Geschäftsfälle für ein bestimmtes geschäftliches Umfeld zu unterstützen und dabei die organisatorische und semantische Interoperabilität mit den TC 440 Spezifikationen aufrechtzuerhalten;
   den Unterschied zwischen Nutzungsspezifikation und Erweiterungsspezifikation;
   eine Methodologie zur Definition von Anpassungen der:
   BII Transaktionsspezifikation,
   Geschäftsregeln,
   Codelisten;
   wie die Compliance oder Conformance mit einer Anpassung einer TC 440-Spezifikation zu beanspruchen ist;
   die Verbindung mit dem e Beschaffungs-Ontologieprojekt.
Der genaue Prozess zur Erstellung einer Erweiterung wird in dieser Spezifikation nicht beschrieben.

Marchés publics électroniques -– Architecture -– Partie 3: Directive de adaptation

Elektronska javna naročila - Arhitektura - 3. del: Smernice za prilagajanje

General Information

• Status: Not Published
• Publication Date: 09-Oct-2024
• ICS: 35.240.20 - IT applications in office work
• ICS: 35.240.63 - IT applications in trade
• Technical Committee: CEN/TC 440 - Project Committee - Electronic Public Procurement
• Drafting Committee: CEN/TC 440/WG 1 - Architecture
• Current Stage: 5060 - Closure of Vote - Formal Approval
• Start Date: 15-Aug-2024
• Due Date: 09-Sep-2024
• Completion Date: 15-Aug-2024
• Ref Project: kSIST-TS FprCEN/TS 17011-3:2024 - Electronic Public Procurement - Architecture - Part 3: Customisation Guideline

Standards Content (Sample)

SLOVENSKI STANDARD
01-julij-2024
Elektronska javna naročila - Arhitektura - 3. del: Smernice za prilagajanje
Electronic Public Procurement - Architecture - Part 3: Customisation Guideline
Elektronische öffentliche Auftragsvergabe - Architektur - Teil 3: Leitfaden für die
Anpassung
Marchés publics électroniques - Architecture - Partie 3: Directive de adaptation
Ta slovenski standard je istoveten z: FprCEN/TS 17011-3
ICS:
35.240.20 Uporabniške rešitve IT pri IT applications in office work
pisarniškem delu
35.240.63 Uporabniške rešitve IT v IT applications in trade
trgovini
2003-01.Slovenski inštitut za standardizacijo. Razmnoževanje celote ali delov tega standarda ni dovoljeno.

FINAL DRAFT
TECHNICAL SPECIFICATION
SPÉCIFICATION TECHNIQUE
TECHNISCHE SPEZIFIKATION
May 2024
ICS 35.240.20; 35.240.63
English Version
Electronic Public Procurement - Architecture - Part 3:
Customisation Guideline
Marchés publics électroniques -¿ Architecture -¿ Partie Elektronische öffentliche Auftragsvergabe -
3: Directive de adaptation Architektur - Teil 3: Leitfaden für die Anpassung

This draft Technical Specification is submitted to CEN members for Vote. It has been drawn up by the Technical Committee
CEN/TC 440.
CEN members are the national standards bodies of Austria, Belgium, Bulgaria, Croatia, Cyprus, Czech Republic, Denmark, Estonia,
Finland, France, Germany, Greece, Hungary, Iceland, Ireland, Italy, Latvia, Lithuania, Luxembourg, Malta, Netherlands, Norway,
Poland, Portugal, Republic of North Macedonia, Romania, Serbia, Slovakia, Slovenia, Spain, Sweden, Switzerland, Türkiye and
United Kingdom.
Recipients of this draft are invited to submit, with their comments, notification of any relevant patent rights of which they are
aware and to provide supporting documentation.

Warning : This document is not a Technical Specification. It is distributed for review and comments. It is subject to change
without notice and shall not be referred to as a Technical Specification.

EUROPEAN COMMITTEE FOR STANDARDIZATION
COMITÉ EUROPÉEN DE NORMALISATION

EUROPÄISCHES KOMITEE FÜR NORMUNG

CEN-CENELEC Management Centre: Rue de la Science 23, B-1040 Brussels
© 2024 CEN All rights of exploitation in any form and by any means reserved Ref. No. FprCEN/TS 17011-3:2024 E
worldwide for CEN national Members.

Contents Page
European foreword . 4
Introduction . 5
1 Scope . 6
2 Normative references . 6
3 Terms and definitions . 7
4 The challenge of interoperability . 8
4.1 Interoperability through standardization . 8
4.2 Challenges . 9
4.3 The purpose of Usage Specifications and Extension specifications . 9
4.3.1 Extension specification . 9
4.3.2 Usage specification . 9
4.4 Who will develop Usage or Extension specifications and why? . 9
4.5 Managing Usage and Extension specifications . 10
4.5.1 Publication of specifications . 10
4.5.2 Mapping an Extension Specification to syntax . 11
4.5.3 Relation between different specifications . 11
4.5.4 Governance of Extension and Usage specifications . 11
4.5.5 Identification of Extension and Usage specifications . 11
4.5.6 Validation . 11
5 Business process compliance . 12
6 Rules about Usage specifications . 12
6.1 Semantic compliance . 12
6.2 Compliance of a Usage specification . 12
6.2.1 General . 12
6.2.2 What can be specified in a Usage specification . 13
6.3 Compliance of sending or receiving party . 15
6.4 Compliance of an eProcurement document instance . 15
7 Rules about Extension specifications . 15
7.1 Semantic conformance . 15
7.2 Compliance of an Extension specifications . 15
7.2.1 General . 15
7.2.2 What can be specified in an Exention specification . 16
7.3 Compliance of sending or receiving party . 17
7.4 Conformance of an instance document . 17
8 Methodology . 18
8.1 How parties agree on using an Extension or Usage specifications. 18
8.2 Process for defining Extension specifications . 18
8.3 Statement of objectives . 19
8.4 Gathering business requirements. 19
8.5 Mapping against the norms . 19
8.6 Re-assess requirements or process . 19
8.7 List requirements . 19
8.8 Define required changes. 19
8.9 Create specification . 20
8.10 Evaluate type of changes . 20
8.11 Publish extension specification . 20
8.12 Bind to syntax. 20
Bibliography . 21

European foreword
This document has been prepared by the Technical Committee CEN/TC 440 “Electronic Public
Procurement”, the secretariat of which is held by DIN.
This document is currently submitted to the Vote on TS.
This document is part of a series of multi-part documents prepared, or under preparation, by
CEN/TC 440:
— 17011-series: eProcurement Architecture, providing a set of specifications outlining different
aspects of the eProcurement architecture for Business Interoperability Specifications.
— 17014-series: eTendering Business Interoperability Specifications, providing a set of
specifications outlining business choreography, transaction, syntax binding specifications and
guidelines required to support the eTendering processes.
— 17015-series: eCatalogue Business Interoperability Specifications, providing a set of
specifications outlining business choreography, transaction, syntax binding specifications and
guidelines required to support the eCatalogue processes.
— 17016-series: eOrdering Business Interoperability Specifications, providing a set of
specifications outlining business choreography, transaction, syntax binding specifications and
guidelines required to support the eOrdering processes.
— 17017-series: eFulfilment Business Interoperability Specifications, providing a set of
specifications outlining business choreography, transaction, syntax binding specifications and
guidelines required to support the e-Delivery processes.
Introduction
To enable flexible and streamlined development of the eProcurement specifications, this document has
been designed to provide generic rules applicable to any eProcurement specification, to support
adaptations required by the context, set out either by national rules or by sectorial needs.
It highlights the needs aimed to be covered, the various solutions and the rules they must adhere to so
that interoperability can be achieved.
The terms “shall”, “shall not”, “should”, “should not”, “may”, “need not” “can” and “cannot” are to be
interpreted according Annex H of Part 3 of the CEN-CENELEC Internal Regulations .

https://www.cenelec.eu/membersandexperts/referencematerial/internalregulation.html
1 Scope
This document describes:
— the rationale for building customisation supporting business cases that are specific to their business
environment while maintaining organisational and semantic interoperability with the TC 440
specifications;
— the difference between Usage specification and Extension specification;
— a methodology on how to define customisations on:
— BII Transaction specification,
— Business rules,
— Code lists;
— how to claim compliance or conformance to a customisation of a TC 440 specification;
— the connection to the eProcurement Ontology project.
This specification does not describe the detailed process of building an extension.
2 Normative references
EN 17014-2 Electronic Public Procurement – Pre-Award – Part 2: Transactions
CEN/TS 17014-3-X, Electronic Public Procurement – Pre-Award – Part 3-X: Syntax Binding, X
prEN 17015-2, Electronic Public Procurement – Catalogue – Part 2: Transactions
CEN/TS 17015-3-X, Electronic Public Procurement – Catalogue – Part 3-X: Syntax Binding, X
prEN 17016-2, Electronic Public Procurement – Ordering – Part 2: Transactions
CEN/TS 17016-3-X, Electronic Public Procurement – Ordering – Part 3-X: Syntax Binding, X
EN 17017-2, Electronic Public Procurement – Fulfilment – Part 2: Transactions

Under preparation.
Under preparation.
Under preparation.
Under preparation.
Under preparation.
Under preparation.
Under preparation.
CEN/TS 17017-3-X, Electronic Public Procurement – Fulfilment – Part 3-X: Syntax Binding, X
3 Terms and definitions
3.1
agent
person, organization, or system that act in procurement or have the power to act in procurement
3.2
business process
sequence or network of activities and collaborations between two or more agents [3.1]
3.3
business process variant
specification of a business process [3.2] belonging to a choreography [3.4]
Note 1 to entry: Different variants may support different electronic information exchange or col
...