FprEN 17015-2
(Main)Electronic Public Procurement - Catalogue - Part 2: Transactions
Electronic Public Procurement - Catalogue - Part 2: Transactions
This document describes the transaction information requirements of the transactions used in the basic
collaborations described in EN 17015-1 Electronic Public Procurement – Catalogue – Choreographies.
For each transaction there is an overview, the transaction business requirements and the transaction information requirements model containing definitions of terms, usage descriptions and cardinality of the information elements.
The document describes the following transactions:
1) Catalogue;
2) Catalogue Response
3) Pre-award Catalogue Request
4) Pre-award Catalogue
5) Shopping Cart
How to claim compliance to a transaction is described in paragraph 6.
How to claim conformance to a transaction is described in paragraph 6.
Elektronisches öffentliches Beschaffungswesen - Katalog - Teil 2: Transaktionen
Dieses Dokument beschreibt die Anforderungen an Transaktionsinformationen hinsichtlich der Transaktionen, die im Rahmen der in FprEN 17015 2 beschriebenen grundlegenden Formen der Zusammenarbeit verwendet werden. Für jede Transaktion besteht eine Übersicht, transaktionsbezogene geschäftliche Anforderungen und ein Anforderungsmodell für Transaktionsinformationen, das Begriffsdefinitionen, Anwendungsbeschreibungen und Kardinalität der Informationselemente sowie Geschäftsregeln umfasst.
Dieses Dokument beschreibt die folgenden Transaktionen:
1) Katalog;
2) Katalogantwort;
3) Pre-Award-Kataloganforderung;
4) Pre-Award-Katalog;
5) Einkaufswagen.
Dieses Dokument gilt nicht für Choreographien, die in den festgelegten Transaktionen verwendet werden. Diese Choreographien sind in der einschlägigen FprEN 17015 1 festgelegt. Die Beziehung zwischen den Choreographien und der Transaktion ist in Abschnitt 6 beschrieben.
Der Identifikator dieses Transaktionsdokuments ist CEN/EN 17015 2:2024.
Wie die Übereinstimmung mit diesen Transaktionen beansprucht wird, ist im Abschnitt 7 "Beanspruchung der Übereinstimmung" beschrieben.
Wie die Übereinstimmung mit diesen Transaktionen beansprucht wird, ist im Abschnitt7 "Beanspruchung der Übereinstimmung" beschrieben.
Passation électronique des marchés publics - Catalogue - Partie 2: Transactions
Le présent document décrit les exigences en matière d'informations sur les transactions utilisées dans les collaborations de base décrites dans le FprEN 17015-2. Pour chaque transaction, il existe une vue d'ensemble, les exigences commerciales de la transaction et le modèle des exigences d'information de la transaction contenant les définitions des termes, les descriptions d'utilisation et la cardinalité des éléments d'information, ainsi que les règles commerciales.
Le présent document décrit les transactions suivantes :
1) catalogue ;
2) accusé de réception de catalogue ;
3) demande de catalogue préadjudication ;
4) catalogue préadjudication ;
5) panier d'achat.
Le présent document ne s'applique pas aux chorégraphies utilisées dans les transactions spécifiées. Ces chorégraphies sont spécifiées dans le projet de norme FprEN 17015-1 associé. La relation entre les chorégraphies et les transactions est décrite à l'Article 6.
Le présent document sur les transactions est identifié par la référence CEN/EN 17015-2:2024.
Le paragraphe « Déclaration de conformité » de l'Article 7 précise les critères à respecter pour revendiquer la conformité à ces transactions.
Elektronska javna naročila - Katalog - 2. del: Transakcije
General Information
Standards Content (Sample)
SLOVENSKI STANDARD
oSIST prEN 17015-2:2024
01-maj-2024
Elektronska javna naročila - Katalog - 2. del: Transakcije
Electronic Public Procurement - Catalogue - Part 2: Transactions
Elektronisches öffentliches Beschaffungswesen - Katalog - Teil 2: Transaktionen
Marchés publics électroniques - Catalogue - Partie 2: Transactions
Ta slovenski standard je istoveten z: prEN 17015-2
ICS:
03.100.10 Nabava. Dobava. Logistika Purchasing. Procurement.
Logistics
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
oSIST prEN 17015-2:2024 en,fr,de
2003-01.Slovenski inštitut za standardizacijo. Razmnoževanje celote ali delov tega standarda ni dovoljeno.
oSIST prEN 17015-2:2024
oSIST prEN 17015-2:2024
DRAFT
EUROPEAN STANDARD
prEN 17015-2
NORME EUROPÉENNE
EUROPÄISCHE NORM
March 2024
ICS
English Version
Electronic Public Procurement - Catalogue - Part 2:
Transactions
Marchés publics électroniques - Catalogue - Partie 2: Elektronisches öffentliches Beschaffungswesen -
Transactions Katalog - Teil 2: Transaktionen
This draft European Standard is submitted to CEN members for enquiry. It has been drawn up by the Technical Committee
CEN/TC 440.
If this draft becomes a European Standard, 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.
This draft European Standard was established by CEN 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, 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 European Standard. It is distributed for review and comments. It is subject to change without
notice and shall not be referred to as a European Standard.
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. prEN 17015-2:2024 E
worldwide for CEN national Members.
oSIST prEN 17015-2:2024
prEN 17015-2:2024 (E)
Contents Page
European Foreword . 3
Introduction . 4
1 Scope . 5
2 Normative references . 5
3 Terms and definitions . 5
4 Symbols and abbreviated terms . 8
5 Positioning in EIRA . 8
6 Collaborations and transactions. 9
6.1 Transactions involved in Catalogue choreographies . 9
6.2 Transactions identifiers . 9
7 Claiming compliance and conformance . 9
8 Business requirements .10
8.1 Common business requirements .10
8.2 Catalogue (T-17015-2:20xx-1) specific business requirements .11
8.3 Catalogue Response (T-17015-2:20xx-2) specific business requirements .13
8.4 Pre-award Catalogue Request (T-17015-2:20xx-3) specific business requirements 13
8.5 Pre-award Catalogue (T-17015-2:20xx-4) specific business requirements.14
8.6 Shopping Cart (T-17015-2:20xx-5) specific business requirements .15
9 Data models .16
9.1 Use of the eProcurment ontology .16
9.2 Legend .16
9.3 Catalogue (T-17015-2:20xx-1) .18
9.4 Catalogue Response (T-17015-2:20xx-2) .91
9.5 Pre-award Catalogue Request (T-17015-2:20xx-3).99
9.6 Pre-award Catalogue (T-17015-2:20xx-4) . 102
9.7 Shopping Cart (T-17015-2:20xx-5) . 175
9.8 Header only data model . 198
9.8.1 Use of the header only data model . 198
9.8.2 Header only data model description . 198
10 Business rules . 198
10.1 Common business rules . 198
10.2 Catalogue (T-17015-2:20xx-1) business rules . 199
10.3 Catalogue Response (T-17015-2:20xx-2) business rules . 200
10.4 Pre-award Catalogue Request (T-17015-2:20xx-3) business rules . 201
10.5 Pre-award Catalogue (T-17015-2:20xx-4) business rules . 201
10.6 Shopping Cart (T-17015-2:20xx-5) business rules . 202
Annex A (informative) Overview of the clauses and subclauses which fall under derivative
use . 203
Bibliography . 204
oSIST prEN 17015-2:2024
prEN 17015-2:2024 (E)
European Foreword
This document (prEN 17015-2:2024) 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 CEN Enquiry.
This document is part of a series of multi-part documents prepared, or under preparation, by CEN/TC
440:
• 17011-series: e-Procurement Architecture, providing a set of specifications outlining different
aspects of the e-Procurement architecture for Business Interoperability Specifications.
• 17015-series: e-Catalogue Business Interoperability Specifications, providing a set of specifications
outlining business choreography, transaction, syntax binding specifications and guidelines required
to support the e-Catalogue processes.
• 17015-series: e-Ordering Business Interoperability Specifications, providing a set of specifications
outlining business choreography, transaction, syntax binding specifications and guidelines required
to support the e-Ordering processes.
• 17017-series: e-Fulfilment Business Interoperability Specifications, providing a set of specifications
outlining business choreography, transaction, syntax binding specifications and guidelines required
to support the e-Delivery processes.
The terms "shall", "shall not", "should", "should not", "may", "need not" "can" and "cannot" shall be
interpreted according annex H of part 3 of the CEN-CENELEC internal regulations .
https://www.cenelec.eu/membersandexperts/referencematerial/internalregulation.html
oSIST prEN 17015-2:2024
prEN 17015-2:2024 (E)
Introduction
Derivative use pilot
This publication falls under a CEN-CENELEC pilot on derivative use (as approved by the CEN/CA
(Administrative Board) through decision 38/2019).
CEN has the copyright to all CEN publications, including their entire content and associated metadata, as
described in CEN-CENELEC Guide 10 "Policy on dissemination, sales and copyright of CEN-CENELEC
Publications". However, through the derivative use pilot, CEN gives permission to the copying, replication
and translation of content from a CEN/TC 440 deliverables in specific circumstances.
Under the derivative use pilot, specific sections of CEN/TC 440 publications may be copied, replicated
and translated in cases, where this is a necessary condition for the meaningful implementation of the
publication. The sections which fall under derivative use will typically be elements, such as semantic
definitions and rules related to the use of information elements, and the name, definition and description
of processes and transactions, which are needed in software solutions, whether intended for sale in the
private market or for use in the public sector, and documents guiding the implementation and use in
specific countries and/or business sectors.
Under derivative use, any use of content, which has been copied, replicated, or translated from a CEN/TC
440 publication, must comply with the intended use of the publication. Derivative use cannot be applied
in use cases other than those the publication is intended to support. The intended use of this publication
is set out below.
Intended use of this publication
This document has been developed for any organization looking for guidance on the implementation and
use of electronic procurement deliverables as well as for organizations developing or implementing
software applications related to electronic procurement, such as software providers, business entities
and national authorities. These software applications must be in conformance with this publication.
Parts of the document to which derivative use apply
Each sub-clause, which falls under derivative use, will be clearly marked with a note. The degree to which
the specific content can be modified, is defined in CEN/TS 17011-3, Electronic Public Procurement –
Architecture – Part 3: Customization Guideline.
Annex A provides an overview of the line number references to all sub-clauses of the publication which
fall under derivative use.
oSIST prEN 17015-2:2024
prEN 17015-2:2024 (E)
1 Scope
This document describes the transaction information requirements of the transactions used in the basic
collaborations described in FprEN 17015-2. For each transaction there is an overview, the transaction
business requirements and the transaction information requirements model containing definitions of
terms, usage descriptions and cardinality of the information elements, as well as business rules.
The document describes the following transactions:
1) Catalogue;
2) Catalogue Response
3) Pre-award Catalogue Request
4) Pre-award Catalogue
5) Shopping Cart
This document does not apply to the choreographies using in the specified transactions. These
choreographies are specified in the related FprEN 17015-1. The relationship between the choreographies
and the transaction is described in Clause 6.
The identifier of this transactions document is CEN/EN 17015-2:2024.
How to claim compliance to these transactions is described in the section 7 “Claiming compliance”
section.
2 Normative references
There are no normative references in this document.
3 Terms and definitions
For the purposes of this document, the following terms and definitions apply.
ISO and IEC maintain terminological databases for use in standardization at the following addresses:
• IEC Electropedia: available at http://www.electropedia.org/
• ISO Online browsing platform: available at http://www.iso.org/obp
3.1
agent
person, organization, or system that acts in procurement or has the power to act in procurement
[SOURCE: eProcurement Ontology, v3.1.0, 2022-12-17]
3.2
business process
sequence or network of activities and collaborations between two or more agents (3.1)
oSIST prEN 17015-2:2024
prEN 17015-2:2024 (E)
3.3
business process variant
specification of a business process (3.2) belonging to a choreography ()
Note 1 to entry: Different variants may support different electronic information exchange or collaborations.
Agents may publicly advertise their capability to support one or more variants in an automated fashion.
3.4
buyer
role (3.14) of an agent (3.1) that awards a contract and/or purchases items (3.11)
Note 1 to entry: In pre-award, the buyer generally awards the contract, however future purchasers may be
foreseen. In post-award the buyer generally refers to the purchaser of items.
[SOURCE: eProcurement Ontology, v3.1.0, 2022-12-17, modified Note 1 to entry has been added]
3.5
catalogue
document describing a set of items (3.11) offered for purchase that can be processed in an electronic way
Note 1 to entry: The terms “eCatalogue” and “Post-award Catalogue” are synonyms for this term.
[SOURCE: eProcurement Ontology, v3.1.0, 2022-12-17, modified Note 1 to entry has been added]
3.6
catalogue provider
role (3.14) of an agent (3.1) compiling and supplying a catalogue (3.5)
Note 1 to entry: The catalogue provider role is usually played by the agent that acts as a seller, or by another
agent that acts on behalf of the seller.
[SOURCE: eProcurement Ontology, v3.1.0, 2022-12-17, modified Note 1 to entry has been added]
3.7
catalogue receiver
role (3.14) of an agent (3.1) processing a catalogue (3.5)
Note 1 to entry: The catalogue receiver may not only receive it but also validate it, process it, etc. The catalogue
receiver role is usually played by the agent that acts as a buyer, or by another agent that acts on behalf of the buyer.
[SOURCE: eProcurement Ontology, v3.1.0, 2022-12-17, modified Note 1 to entry has been added]
3.8
catalogue response
single message from the catalogue receiver (3.7) to the catalogue provider (3.6) on the acceptance of the
related catalogue (3.5) sent by the catalogue provider (3.6)
[SOURCE: eProcurement Ontology, v3.1.0, 2022-12-17, modified Note 1 to entry has been added]
3.9
choreography
set of business processes (3,2) having the same goals
oSIST prEN 17015-2:2024
prEN 17015-2:2024 (E)
3.10
collaboration
interaction between two or more agents (3.1) that results in the exchange of data between the agents
(3.1) involved as part of a business process (3.2)
3.11
item
single product or service
Note 1 to entry: An item can be an atomic thing or a composition of things that together are seen as a unit, e.g., a
tetrabrik of milk or an indivisible package of six tetrabriks.
[SOURCE: eProcurement Ontology, v3.1.0, 2022-12-17, modified Note 1 to entry has been added]
3.12
pre-award catalogue
catalogue (3.5) that is submitted as a tender in response to a call for tenders
3.13
pre-award catalogue request
document describing the requirements on items (3.11) to be tendered and on the catalogue (3.5) that
should be submitted as a tender
3.14
role
part played by an agent (3.1) in a particular business process (3.2), including its responsibilities (options
and obligations) to perform certain activities and collaborations (3.10) in that business process (3.2)
Note 1 to entry: The role is used to show the division of labour and responsibility amongst the agents involved in
the process or within the organisation of an Agent.
[SOURCE: eProcurement Ontology, v3.1.0, 2022-12-17, modified Note 1 to entry has been added]
3.15
seller
role (3.14) of an agent (3.1) legally responsible for providing goods and services bought by a buyer (3.4)
[SOURCE: eProcurement Ontology, v3.1.0, 2022-12-17, modified Note 1 to entry has been added]
3.16
state
set of options and obligations of the participating agents (3.1) at a defined step in a business process to
perform specific activities and collaborations (3.10)
Note 1 to entry: An activity of an agent or a collaboration may cause the transition of one state to another in a
predefined set of next steps.
oSIST prEN 17015-2:2024
prEN 17015-2:2024 (E)
3.17
transaction
content of data exchanged or shared between the agents (3.1) in a collaboration (3.10)
Note 1 to entry: A transaction is the atomic unit that leads to a synchronized state in the information systems of
collaborating agents. It is the basic building block to define the choreography between agents. When an agent
recognizes an event that changes the state of a business object within a business process, it uses a transaction to
synchronize with the collaborating agent. A transaction therefore changes the state of a business process. It carries
the intention of the initiating agent and is represented by a data structure that is defined by a data model. The
exchange of a transaction may alter legal obligations between business partners.
4 Symbols and abbreviated terms
ABB Architectural Building Block
EIF European Interoperability Framework
EIRA European Interoperability Reference Architecture
5 Positioning in EIRA
Table 1 — Positioning in EIRA
EIRA ID Title Domain Interface Scope Modality
CEN/EN 17015- Machine • e-procurement
Electronic Procurement Endorsing
2:20xx /Customer extension of
Public
ABB176
Procurement
Machine
Organisational
- Catalogue -
/Supplier
Interoperability
Transactions
Specification
• e-procurement
extension of
ABB12
Business
Capability,
• e-procurement
extension of
ABB170
Exchange of
Business
Information
• e-procurement
extension of
ABB16
Business Rule
oSIST prEN 17015-2:2024
prEN 17015-2:2024 (E)
6 Collaborations and transactions
6.1 Transactions involved in Catalogue choreographies
Table 2 — Transactions identifiers
Role Capability Collaboration Collabor Transacti Transaction Variant
ID ation on ID
A B C D E
Catalog Send BC-17015– Catalogue T-17015- Catalogue M M
ue Catalogue 1:202x-1 Provider 2:20xx-1
Provid send
er Catalogue
Catalog BC-17015– Catalogue T-17015- Catalogue M
ue 1:202x-2 receiver 2:20xx-2 Response
Receiv Catalogue
er Response
Catalog BC-17015– Catalogue T-17015- Pre-award M
ue 1:202x-3 Receiver 2:20xx-3 Catalogue
Receiv sends Request
er Pre-
award
Catalogue
Request
Catalog BC-17015– Catalogue T-17015- Pre-award M M
ue 1:202x-4 Provider 2:20xx-4 Catalogue
Provid sends
er Pre-
award
Catalogue
Seller BC-17015– Seller T-17015- Shopping Cart M
1:202x-5 sends 2:20xx-5
shopping-
cart
6.2 Transactions identifiers
Table 3 — Transactions identifiers
Transaction ID Transaction Name
T-17015-2:20xx-1 Catalogue
T-17015-2:20xx-2 Catalogue Response
T-17015-2:20xx-3 Pre-award Catalogue Request
T-17015-2:20xx-4 Pre-award Catalogue
T-17015-2:20xx-5 Shopping Cart
7 Claiming compliance and conformance
A transaction instance is compliant to a specified transaction, if the following conditions are met
— all specified business terms of that transaction are included according to their cardinalities as well
as all corresponding business rules are fulfilled,
oSIST prEN 17015-2:2024
prEN 17015-2:2024 (E)
— no additional business terms were added
— additional business rules may have been added, which shall not conflict with the specification
A transaction instance is conformant to a specified transaction, if the following conditions are met
— all specified business terms of that transaction are included according to their cardinalities as well
as all corresponding business rules are fulfilled
— additional business terms may have been added
— additional business rules may have been added, which shall not conflict with the specification
8 Business requirements
8.1 Common business requirements
Table 4 — Common business requirements
ID Description
R-17015-2:20xx-X1 A transaction shall provide information about its identity, type, issue date
and validity.
R-17015-2:20xx-X2 All amounts in a transaction shall be stated in the same currency.
R-17015-2:20xx-X3 A transaction shall contain non-negative prices and quantities.
R-17015-2:20xx-X4 The transactions shall contain all information necessary for its application
i.e., it shall not rely on the availability of external references such as a
centralised repository of item information. To ease the processing of a
catalogue, no external data sources are needed.
R-17015-2:20xx-X7 A transaction shall contain information on the organisations sending
respectively receiving the transaction.
R-17015-2:20xx-X8 A transaction shall provide information about corresponding business
process variant it is used in.
Section 7.1 falls under derivative use (as set out in the introduction). When replicating the section, the content can
be modified as specified in CEN/TS 17011-3 Electronic Public Procurement – Architecture – Part 3: Customization
Guideline.
oSIST prEN 17015-2:2024
prEN 17015-2:2024 (E)
8.2 Catalogue (T-17015-2:20xx-1) specific business requirements
Table 5 — Catalogue business requirements
ID Description
T-17015-2:20xx-1-R- To support changing of the previously sent catalogue, the catalogue shall
1 provide information on its version history and how changes shall be
applied. Changes may be fully or partial updates and deletion of
information sent in previous version of a catalogue.
T-17015-2:20xx-1-R- To support an easy identification for end-users on the buying side, a name
3 of the catalogue may be provided in a catalogue.
T-17015-2:20xx-1-R- To ensure that a catalogue can be understood by the end-users on the
X23 buying side, the language used in the catalogue shall be provided.
T-17015-2:20xx-1-R- To restrict the validity of a catalogue, a period of time the catalogue is valid
4 may be defined in the catalogue. A catalogue without a stated validity
period is assumed to be valid until it is cancelled. Sometimes products are
offered only for a certain period of time or the prices for the product are
assured to be fixed by the catalogue provider only during this period of
time.
T-17015-2:20xx-1-R- If a catalogue is based on a contract, e.g., a framework agreement, a
5 catalogue shall include details on the contract the catalogue is based on. In
such a contract, further requirements on the catalogue may be specified.
T-17015-2:20xx-1-R- To support use cases where the catalogue receiver is not the buyer,
X11 information on the organisation buying the items offered in the catalogue
may be provided in the catalogue.
T-17015-2:20xx-1-R- To support cases where the catalogue provider is not the seller,
X12 information on the organisation buying the items offered in the catalogue
may be provided in the catalogue.
T-17015-2:20xx-1-R- A catalogue must have information that makes it possible to reference
X18 specific instances of the catalogue.
T-17015-2:20xx-1-R- To support offering an item with different condition such as different
X16 prices, delivery times, validity periods, orderability, warranties, packaging
etc, an item may be more the once provided in a catalogue along with the
information on the varying condition. Such a combinations of an item and
conditions shall be uniquely identifiable.
T-17015-2:20xx-1-R- An item shall be referenceable uniquely by an identifier. Such an identifier
X8 may be an identifier assigned by the seller, buyer, manufacturer or an
identifier according to an international identification scheme.
T-17015-2:20xx-1-R- To allow selection of an item by the end-user on the buying side, a name of
X26 the item shall be provided in the catalogue.
Section 7.2 falls under derivative use (as set out in the introduction). When replicating the section, the content can
be modified as specified in CEN/TS 17011-3 Electronic Public Procurement – Architecture – Part 3: Customization
Guideline.
oSIST prEN 17015-2:2024
prEN 17015-2:2024 (E)
ID Description
T-17015-2:20xx-1-R- To support searching for items in buy-side ordering systems, additional
X27 names, e.g., if an item was rebranded, additional descriptions and
keywords may be provided in the catalogue.
T-17015-2:20xx-1-R- To support end-users on the buying side, additional documents, e.g.,
X9 images, manuals, brochures etc. may be provided in the catalogue. These
documents may be provided by references to external sources.
T-17015-2:20xx-1-R- To support the buying decision information on how an items is priced shall
X28 be provided in a catalogue including additional charges like VAT. This also
includes factors that have influence on the price as well as relationships to
other parts of the catalogue that may have impact on the price. The price
may also be dependent on factors, e.g., order size, delivery region (down to
the city level), allowance, charges, currency, etc. Prices must not be
negative.
T-17015-2:20xx-1-R- To ease comparing the prices of items in a catalogue, a priced for a
X29 standardised order unit may be provided in the catalogue.
T-17015-2:20xx-1-R- It must be possible to specify the kind of the item in the context of its
X13 delivery.
T-17015-2:20xx-1-R- To support supply-chain due diligence processes, information on the origin
X14 of the item as well as on other involved organisation involved in the
production/provision of the item may be provided in the catalogue.
T-17015-2:20xx-1-R- An item in the catalogue may be classified according to a standardised
X17 classification system, e.g., CPV, UNSPSC, ECLASS, and GPC. Such
classifications may be mandated by the Buyer or by legal frameworks.
T-17015-2:20xx-1-R- To support the automated evaluation of an item, a structured description
X15 according to a standardised property systems may be provided in a
catalogue.
T-17015-2:20xx-1-R- To support logistics processes on the buying side, details on transporting
X24 and handling an item in logistics processes may be provided in a catalogue.
T-17015-2:20xx-1-R- To support the assessment of the sustainability of an item as well as
X25 supply-chain due diligence processes, information on relevant labels,
certificates etc. proofing the conformance of an item to relevant
sustainability requirements may be provided in a catalogue.
T-17015-2:20xx-1-R- To fulfil regulatory requirements on hazardous items, information on the
X29 hazardous nature of an item may be provided in a catalogue.
T-17015-2:20xx-1-R- To allow a reload of a catalogue, a URL may be provided in a catalogue,
X30 where the catalogue can be retrieved as well.
T-17015-2:20xx-1-R- To support offering perishable goods, dates on the durability and
X31 expiration of an item may be provided in catalogue.
T-17015-2:20xx-1-R- To support offering items related to a selected item together in an ordering
X32 system, information on the relationship between various items may be
provided in a catalogue. Examples of such relationships are replacement
items, accessory items etc.
oSIST prEN 17015-2:2024
prEN 17015-2:2024 (E)
8.3 Catalogue Response (T-17015-2:20xx-2) specific business requirements
Table 6 — Catalogue Response business requirements
ID Description
T-17015-2:20xx-2-R- A catalogue response shall contain the date and time when the catalogue
Y2 response was sent.
T-17015-2:20xx-2-R- A catalogue response shall refer catalogue transaction it is the response to.
Y3
T-17015-2:20xx-2-R- The catalogue response shall provide information if the related catalogue
Y4 was accepted or rejected. In the case of rejection or a partial rejection, the
reason for the rejection shall be provided in the catalogue response. The
catalogue receiver can reject a catalogue transaction if it does not conform
to the agreement under which the catalogue is provided. By proving the
information about the rejection, the catalogue provider will be enabled to
submit a valid catalogue.
T-17015-2:20xx-2-R- The issuer of the response shall be provided to proof that the catalogue
Y5 response is sent by the valid catalogue receiver.
T-17015-2:20xx-2-R- The receiver of the response shall be provided to proof that the catalogue
Y6 response is sent to the valid provider of the original catalogue transaction.
T-17015-2:20xx-2-R- The catalogue response may contain textual notes that may be used to
Y7 make any comments or instructions relevant to the response.
8.4 Pre-award Catalogue Request (T-17015-2:20xx-3) specific business requirements
Table 7 — Pre-award Catalogue Request business requirements
ID Description
T-17015-2:20xx-3-R- As pre-award catalogue request is part of a call for tenders, a pre-award
X1 catalogue request shall contain a reference to the corresponding call for
tenders.
T-17015-2:20xx-3-R- To ensure a vendor-neutral description of requirements on item to be
X2 tendered, a pre-award catalogue request shall support the structured
description according to a standardised property systems may be provided
in a pre-award catalogue request.
T-17015-2:20xx-3-R- As a pre-award catalogue request is part of a call for tenders, a reference to
X3 the corresponding call for tender shall be provided to ensure that the pre-
award catalogue request can evaluated in the corresponding context.
Section 7.3 falls under derivative use (as set out in the introduction). When replicating the section, the content can
be modified as specified in CEN/TS 17011-3 Electronic Public Procurement – Architecture – Part 3: Customization
Guideline.
Section 7.4 falls under derivative use (as set out in the introduction). When replicating the section, the content can
be modified as specified in CEN/TS 17011-3 Electronic Public Procurement – Architecture – Part 3: Customization
Guideline.
oSIST prEN 17015-2:2024
prEN 17015-2:2024 (E)
ID Description
T-17015-2:20xx-3-R- To ensure a consistent set up of the post-award process, requirements on
X4 the on the pre-award catalogue to be submitted as a tender may be
provided in a pre-award catalogue request. This includes information
requirement on the items, information requirements on the pre-award
catalogue as well as on how the item can be ordered and how the item will
be delivered.
T-17015-2:20xx-3-R- To support referencing an item request, an item request shall be uniquely
X5 identifiable.
T-17015-2:20xx-3-R- To ease the understanding of an item request, a vendor-neutral name may
X6 be provided for an item request.
T-17015-2:20xx-3-R- An item request in the pre-award catalogue request may be classified
according to a standardised classification system, e.g., CPV, UNSPSC,
X7
ECLASS, and GPC. Such classifications may be mandated by the Buyer or by
legal frameworks.
T-17015-2:20xx-3-R- To provide details on the requested items, information on the relationship
X8 between various item requests may be provided in a pre-award catalogue
request. Examples of such relationships are replacement items, accessory
items etc.
8.5 Pre-award Catalogue (T-17015-2:20xx-4) specific business requirements
Table 8 — Pre-award Catalogue business requirements
ID Description
T-17015-2:20xx-4-R- To support the evaluation of the pre-award catalogue, the pre-award
X1 catalogue shall contain a reference to the corresponding call for tenders.
T-17015-2:20xx-4-R- To support sending a pre-award catalogue as part of a set of tender
X2 documents, a pre-award catalogue may contain a reference to a tender.
T-17015-2:20xx-4-R- To facilitate the set-up of post-award processes, a pre-award catalogue
X3 shall be reusable as a catalogue in post-award processes.
Section 7.5 falls under derivative use (as set out in the introduction). When replicating the section, the content can
be modified as specified in CEN/TS 17011-3 Electronic Public Procurement – Architecture – Part 3: Customization
Guideline.
oSIST prEN 17015-2:2024
prEN 17015-2:2024 (E)
8.6 Shopping Cart (T-17015-2:20xx-5) specific business requirements
Table 9 — Shopping Cart business requirements
ID Description
T-17015-2:20xx-5-R- If a shopping cart is based on a contract, e.g., a framework agreement, a
X1 shopping cart shall include details on the contract the catalogue is based
on. In such a contract, further requirements on the shopping cart and the
punch-out process may be specified.
T-17015-2:20xx-5-R- To restrict the validity of a shopping cart, a period of time the shopping cart
X2 is valid may be defined in the shopping cart. A shopping cart without a
stated validity period is assumed to be valid until indefinitely. This may
apply for parts of the shopping cart as well.
T-17015-2:20xx-5-R- An item shall be referenceable uniquely by an identifier. Such an identifier
X4 may be an identifier assigned by the seller, buyer, manufacturer, or an
identifier according to an international identification scheme.
T-17015-2:20xx-5-R- To support buying an item to different condition such as different prices,
X5 delivery times, validity periods, orderability, warranties etc, an item may
be more the once provided in a shopping cart along with the relevant
information on the varying condition. Such a combinations of an item and
conditions shall be uniquely identifiable.
T-17015-2:20xx-5-R- To support supply-chain due diligence processes, information on the origin
X6 of the item as well as on other involved organisation involved in the
production/provision of the item may be provided in the shopping-cart.
T-17015-2:20xx-5-R- To ease the identification of the selected item for the end-users, the name
X7 and description of the item may be provided in the shopping cart.
T-17015-2:20xx-5-R- To support the automated evaluation of an item, a structured description
X8 according to a standardised property systems may be provided in a
shopping cart.
T-17015-2:20xx-5-R- To support the assessment of the sustainability of an item as well as
X9 supply-chain due diligence processes, information on relevant labels,
certificates etc. proofing the conformance of an item to relevant
sustainability requirements may be provided in a shopping cart.
T-17015-2:20xx-5-R- An item in the shopping cart may be classified according to a standardised
classification system, e.g., CPV, UNSPSC, ECLASS, and GPC. Such
X10
classifications may be mandated by the Buyer or by legal frameworks.
T-17015-2:20xx-5-R- To support the ordering process, additional documents, e.g., images,
X11 manuals, brochures etc. may be provided in the catalogue. These
documents may be provided by references to external sources.
T-17015-2:20xx-5-R- To place the final order, information on how an items is priced shall be
X12 provided in a catalogue including additional charges like VAT. This also
includes factors that have influence on the price as well as relationships to
Section 7.6 falls under derivative use (as set out in the introduction). When replicating the section, the content can
be modified as specified in CEN/TS 17011-3 Electronic Public Procurement – Architecture – Part 3: Customization
Guideline.
oSIST prEN 17015-2:2024
prEN 17015-2:2024 (E)
ID Description
other parts of the catalogue that may have impact on the price. The price
may also be dependent on factors, e.g., order size, delivery region (down to
the city level), allowance, charges, currency, etc. Prices must not be
negative.
T-17015-2:20xx-5-R- To support selling items which are be sold together, e.g., for a certain price,
X13 it may be indicated that no changes of the shopping cart are allowed when
placing the order based on this shopping cart.
9 Data models
9.1 Use of the eProcurment ontology
Table 10 — Information elements
ID Level Cardinality Business eProcurement Description Usage Requirement Semantic
Term Concept note ID data
type
9.2 Legend
Each information element, as well as groups of information elements, that constitutes the semantic data
model is described as a row in the tables documented in clauses 8.3.2 and 8.4.2, where the following
information is provided.
ID: An identifier for the information element (BT – Business Term) and group of information elements
(BG – Business term Group).
Level: Indicates on which level in the model the information element occurs:
— +: The first level of the model;
— ++: The second level of the model. The information element (or the group of information elements)
is part of a group of information elements which is specified at the first level of the model;
— +++: The third level of the model. The information element (or the group of information elements) is
part of a group of information elements which is specified at the second level of the model;
— ++++: The fourth level of the model. The information element is part of a group of information
elements which is specified at the third level of the model.
Cardinality: Also known as multiplicity, is used to indicate if an information element (or group of
information elements) is mandatory or conditional, and if it is repeatable. The cardinality shall always be
analysed in the context of where the information element is used. Example: the Payee Name is mandatory
in the core invoice model, but only when a Payee is stated and is relevant.
The following cardinalities exist:
— 1.1: Mandatory, minimum 1 occurrence and maximum 1 occurrence of the information element (or
group of information elements) shall be present in any conformant instance document;
— 1.n: Mandatory and repeatable, minimum 1 occurrence and unbounded upper maximum occurrence
of the information element (or group of information elements) shall be present in any conformant
instance document;
oSIST prEN 17015-2:2024
prEN 17015-2:2024 (E)
— 0.1: Conditional, minimum 0 occurrences and maximum 1 occurrence of the information element
(or group of information elements) may be present in any conformant instance document; it's use
depends on business rules stated as well as the regulatory, commercial and contractual conditions
that applies to the business transaction;
— 0.n: Conditional and repeatable, minimum 0 occurrences and unbounded upper maximum
occurrence of the information element (or group of information elements) may be present in any
conformant instance document; it’s use depends on business rules stated as well as the regulatory,
commercial and contractual conditions that applies to the business transaction.
Business Term: The name of the information element used in the core invoice model or the name of a
coherent group of related information elements, provided to give logical meaning.
Description: A description of the semantic meaning of the information element.
Usage Note: Clarifying information on how the information element shall or may be used (such as
calculation rules).
Req. ID: The requirement identifier, provided to show the traceability of the information element with
the corresponding requirement specified in Clause 7.
Semantic data type: The data format that applies to the information element.
oSIST prEN 17015-2:2024
prEN 17015-2:2024 (E)
9.3 Catalogue (T-17015-2:20xx-1)
Table 11 — Information elements
ID L. C. Busine eProcurement Concept Description Usage note Requi Sem
ss remen anti
Term t ID c
data
type
A document describing a set of Items
BT Catalog epo-cat:Catalogue
offered for purchase that can be
- ue
processed in an electronic way.
X1
BT + 1 Catalog adms:Identifier A character string to identify and The unique identifier of the R- Iden
- ue distinguish uniquely, one instance of catalogue. 17015 tifier
(epo:hasUUID)
X2 Identifi an object in an identification scheme -
er from all other objects in the same 2:20xx
scheme together with relevant -X1
supplementary information.
BT + 1 Busines n/a n/a A code referring the to business R- Code
- s process variant this transaction 17015
X1 Process instance is used in. -
93 Variant 2:20xx
-X8
BT + 0. Catalog dct:title A short text by which a thing is The name of the catalogue. T- Text
- .1 ue known or referred to. Sometimes the name refers to a 17015
X3 Name special event the catalogue is -
created for, e.g., summer season. 2:20xx
-1-R-3
Section 8.3 falls under derivative use (as set out in the introduction). When replicating the section, the content can be modified as specified in CEN/TS 17011-3
Electronic Public Procurement – Architecture – Part 3: Customization Guideline.
oSIST prEN 17015-2:2024
prEN 17015-2:2024 (E)
ID L. C. Busine eProcurement Concept Description Usage note Requi Sem
ss remen anti
Term t ID c
data
type
BT + 1 Catalog epo:hasOfficialLanguage n/a Language of all names and T- Code
- ue descriptions in the catalogue. 17015
X4 Langua -
ge 2:20xx
-1-R-
X23
BT + 1 Catalog dct:issued Date of formal issuance of the The date and time the catalogue R- Date
- ue Issue resource. was sent by the catalogue 17015 Time
X5 Date provider. -
2:20xx
-X1
BT + 0. Catalog epo:hasAccessURL Location where the resource can be T- Docu
-5 .n ue accessed. 17015 men
Referen - Refe
ce 2:20xx renc
-1-R- e
X30
BT + 0. Catalog epo:hasVersion A number that identifies a specific The version number of the T- Text
-6 .1 ue state of a document. catalogue. 17015
Version -
2:20xx
-1-R-1
A document containing a catalogue.
BT + 0. Source epo-cat:Catalogue Represents a previous version of a T-
-7 .1 Catalog (epo-cat:Cata
...
Questions, Comments and Discussion
Ask us and Technical Secretary will try to provide an answer. You can facilitate discussion about the standard in here.