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 Anwendungsspezifikation 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
Published
Publication Date
17-Dec-2024
Current Stage
6060 - Definitive text made available (DAV) - Publishing
Start Date
18-Dec-2024
Due Date
09-Dec-2024
Completion Date
18-Dec-2024

Buy Standard

Technical specification
TS CEN/TS 17011-3:2025
English language
22 pages
sale 10% off
Preview
sale 10% off
Preview
e-Library read for
1 day

Standards Content (Sample)


SLOVENSKI STANDARD
01-maj-2025
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: CEN/TS 17011-3:2024
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.

CEN/TS 17011-3
TECHNICAL SPECIFICATION
SPÉCIFICATION TECHNIQUE
December 2024
TECHNISCHE SPEZIFIKATION
ICS 35.240.20
English Version
Electronic Public Procurement - Architecture - Part 3:
Customisation Guideline
Marchés publics électroniques - Architecture - Partie 3: Elektronische öffentliche Auftragsvergabe -
Directive de adaptation Architektur - Teil 3: Leitfaden für die Anpassung
This Technical Specification (CEN/TS) was approved by CEN on 16 September 2024 for provisional application.

The period of validity of this CEN/TS is limited initially to three years. After two years the members of CEN will be requested to
submit their comments, particularly on the question whether the CEN/TS can be converted into a European Standard.

CEN members are required to announce the existence of this CEN/TS in the same way as for an EN and to make the CEN/TS
available promptly at national level in an appropriate form. It is permissible to keep conflicting national standards in force (in
parallel to the CEN/TS) until the final decision about the possible conversion of the CEN/TS into an EN is reached.

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.
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. CEN/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 . 6
4 The challenge of interoperability . 8
4.1 Interoperability through standardization . 8
4.2 Challenges . 8
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 . 10
4.5.3 Relation between different specifications . 10
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 . 14
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 . 18
8.4 Gathering business requirements. 18
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 . 19
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 (CEN/TS 17011-3:2024) has been prepared by the Technical Committee CEN/TC 440
“Electronic Public Procurement”, the secretariat of which is held by DIN.
Attention is drawn to the possibility that some of the elements of this document may be the subject of
patent rights. CEN shall not be held responsible for identifying any or all such patent rights.
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.
Any feedback and questions on this document should be directed to the users’ national standards body.
A complete listing of these bodies can be found on the CEN website.
According to the CEN/CENELEC Internal Regulations, the national standards organisations of the
following countries are bound to announce this Technical Specification: 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 the
United Kingdom.
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 .

extension://efaidnbmnnnibpcajpcglclefindmkaj/https://boss.cen.eu/media/BOSS%20CENELEC/ref/ir3_e.pdf
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
The following documents are referred to in the text in such a way that some or all of their content
constitutes requirements of this document. For dated references, only the edition cited applies. For
undated references, the latest edition of the referenced document (including any amendments) applies.
EN 17015 (all parts), Electronic Public Procurement — Catalogue
EN 17015-2, Electronic Public Procurement — Catalogue — Part 2: Transactions
EN 17016 (all parts), Electr
...

Questions, Comments and Discussion

Ask us and Technical Secretary will try to provide an answer. You can facilitate discussion about the standard in here.