prEN 17016-1
(Main)Electronic Public Procurement - Ordering - Part 1: Choreographies
Electronic Public Procurement - Ordering - Part 1: Choreographies
This choreographies document describes ordering between Buyer and Seller where the Buyer wants to reach an agreement with the Seller about an order. It describes a series of activities that govern communication between the parties and refers to the specifications where information and rules that apply are described.
The various possible behaviours of the Seller and Buyer subsequent to the first order communication are conveyed by variants of this choreography that are described in 5.2.
Previous activities (e.g. cataloguing) and subsequent activities (e.g. invoicing) are outside the scope of this document. If performed electronically, their implementation is covered by other choreographies.
The identifier of this choreographies document is EN 17016-1:2022.
How to claim conformance to this choreography is described in 5.2.3.
Elektronisches öffentliches Beschaffungswesen - Bestellung - Teil 1: Choreographien
Dieses Choreographiendokument beschreibt den Bestellvorgang zwischen Käufer und Verkäufer, in dessen Rahmen der Käufer eine Vereinbarung mit dem Verkäufer über eine Bestellung treffen möchte. Es beschreibt eine Reihe von Aktivitäten, die die Kommunikation zwischen den Parteien regeln, und bezieht sich auf die Spezifikationen, in denen die geltenden Informationen und Regeln beschrieben sind.
Die verschiedenen möglichen Verhaltensweisen von Verkäufer und Käufer nach der ersten Kommunikation im Rahmen einer Bestellung werden durch Varianten dieser Choreographie vermittelt, die in 5.2 beschrieben sind.
Vorgeschaltete Aktivitäten (z. B. Katalogisierung) und nachgeschaltete Aktivitäten (z. B. Fakturierung) befinden sich außerhalb des Anwendungsbereichs dieses Dokuments. Wenn diese elektronisch durchgeführt werden, ist ihre Implementierung von anderen Choreographien abgedeckt.
Der Identifikator dieses Choreographiendokuments ist EN 17016 1:2022.
Wie die Konformität mit dieser Choreographie beansprucht wird, ist in 5.2.3 beschrieben.
Passation électronique des marchés publics - Gestion des commandes - Partie 1 : Chorégraphies
Le présent document sur les chorégraphies décrit la procédure de gestion des commandes entre un acheteur et un vendeur lorsque l'acheteur souhaite conclure un accord avec le vendeur au sujet d'une commande. Il présente une série d'activités qui régissent la communication entre les parties et renvoie aux spécifications où sont décrites les informations et les règles applicables.
Les différents comportements possibles du vendeur et de l'acheteur faisant suite aux échanges d'informations dans le cadre de la première commande sont exprimés par des variantes de cette chorégraphie, qui sont décrites en 5.2.
Les activités antérieures (par exemple, l'établissement d'un catalogue) et les activités ultérieures (par exemple, la facturation) n'entrent pas dans le domaine d'application du présent document. Toutefois, si elles sont effectuées par voie électronique, leur mise en œuvre est couverte par d'autres chorégraphies.
Le présent document sur les chorégraphies est identifié par la référence EN 17016-1:2022.
Le paragraphe 5.2.3 indique les critères à respecter pour revendiquer la conformité à cette chorégraphie.
Elektronska javna naročila - Naročanje - 1. del: Koreografije
General Information
Standards Content (Sample)
SLOVENSKI STANDARD
oSIST prEN 17016-1:2023
01-februar-2023
Elektronska javna naročila - Naročanje - 1. del: Koreografije
Electronic Public Procurement - Ordering - Part 1: Choreographies
Elektronisches öffentliches Beschaffungswesen - Bestellung - Teil 1: Choreographien
Passation électronique des marchés publics - Gestion des commandes - Partie 1 :
Chorégraphies
Ta slovenski standard je istoveten z: prEN 17016-1
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 17016-1:2023 en,fr,de
2003-01.Slovenski inštitut za standardizacijo. Razmnoževanje celote ali delov tega standarda ni dovoljeno.
---------------------- Page: 1 ----------------------
oSIST prEN 17016-1:2023
---------------------- Page: 2 ----------------------
oSIST prEN 17016-1:2023
DRAFT
EUROPEAN STANDARD
prEN 17016-1
NORME EUROPÉENNE
EUROPÄISCHE NORM
December 2022
ICS
English Version
Electronic Public Procurement - Ordering - Part 1:
Choreographies
Elektronisches öffentliches Beschaffungswesen -
Bestellung - Teil 1: Choreographien
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
© 2022 CEN All rights of exploitation in any form and by any means reserved Ref. No. prEN 17016-1:2022 E
worldwide for CEN national Members.
---------------------- Page: 3 ----------------------
oSIST prEN 17016-1:2023
prEN 17016-1:2022 (E)
Contents Page
European foreword . 3
Introduction . 4
1 Scope . 5
2 Normative references . 5
3 Terms and definitions . 5
4 Business environment and high level business requirements . 6
4.1 Choreographies (business) Goals . 6
4.2 Business environment . 7
4.3 Organization and business partners involved . 8
4.4 High level business process requirements . 9
5 Processes . 11
5.1 Introduction . 11
5.2 Business process variants. 11
5.3 Business process variant A – Simple ordering . 14
5.4 Business process variant B – Buyer managed ordering . 17
5.5 Business process variant C – Ordering with simple Response . 21
5.6 Business process variant D – Buyer Managed Ordering with Seller’s response . 25
5.7 Business process variant E – Ordering . 31
5.8 Business process variant F – Advanced ordering . 35
5.9 Business process variant G – Simplified advanced ordering . 43
5.10 Business process variant H – Order Agreement . 51
6 BII Transactions involved . 54
6.1 Summary . 54
6.2 Basic collaborations . 56
6.3 Buyer sends Order (BC-17016-1:20xx-1) . 57
6.4 Buyer changes Order (BC-17016-1:20xx-2) . 58
6.5 The Buyer cancels Order (BC-17016-1:20xx-3) . 58
6.6 Seller confirms Order (BC-17016-1:20xx-4) . 59
6.7 Seller rejects Order (BC-17016-1:20xx-5) . 60
6.8 Seller confirms Order Change (BC-17016-1:20xx-6) . 61
6.9 Seller rejects Order Change (BC-17016-1:20xx-7) . 62
6.10 Seller confirms Order Cancellation (BC-17016-1:20xx-8) . 63
6.11 Seller rejects Order Cancellation (BC-17016-1:20xx-9) . 64
6.12 Seller accepts Order partially or with changes (BC-17016-1:20xx-10) . 65
6.13 Seller changes Order (BC-17016-1:20xx-11) . 66
6.14 Buyer confirms Order Response (BC-17016-1:20xx-12) . 67
6.15 Buyer rejects Order Response (BC-17016-1:20xx-13). 68
6.16 Buyer confirms Order Change (BC-17016-1:20xx-14) . 69
6.17 Buyer rejects Order Change (BC-17016-1:20xx-15) . 70
6.18 Seller sends Order Agreement (BC-17016-1:20xx-16) . 71
Annex A (informative) Overview of the clauses and sub-clauses which fall under derivative
use . 73
Bibliography . 73
2
---------------------- Page: 4 ----------------------
oSIST prEN 17016-1:2023
prEN 17016-1:2022 (E)
European foreword
This document (prEN 17016-1:2022) 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 falls under a CEN-CENELEC pilot on derivative use (as approved by the CEN/CA
(Administrative Board) through decision 37/2019). For more information about the implementation of
derivative use in CEN/TC 440, see here.
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.
— 17016-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", "can" and "cannot" are interpreted
1
according to Clause 7 of the CEN-CENELEC Internal Regulations Part 3 .
1
https://boss.cen.eu/reference-material/refdocs/pages/
3
---------------------- Page: 5 ----------------------
oSIST prEN 17016-1:2023
prEN 17016-1:2022 (E)
Introduction
Derivative use pilot
This document 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 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 subclause, which falls under derivative use, will be clearly marked with a note. The degree to
2
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 subclauses of the publication which
fall under derivative use.
2
Under development.
4
---------------------- Page: 6 ----------------------
oSIST prEN 17016-1:2023
prEN 17016-1:2022 (E)
1 Scope
This choreographies document describes ordering between Buyer and Seller where the Buyer wants to
reach an agreement with the Seller about an order. It describes a series of activities that govern
communication between the parties and refers to the specifications where information and rules that
apply are described.
The various possible behaviours of the Seller and Buyer subsequent to the first order communication
are conveyed by variants of this choreography that are described in 5.2.
Previous activities (e.g. cataloguing) and subsequent activities (e.g. invoicing) are outside the scope
of this document. If performed electronically, their implementation is covered by other
choreographies.
The identifier of this choreographies document is EN 17016-1:2022.
How to claim conformance to this choreography is described in 5.2.3.
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.
3
EN 17016-2 , Electronic Public Procurement — Ordering — Part 2: Transactions
3 Terms and definitions
For the purposes of this document, the following terms and definitions apply.
ISO and IEC maintain terminology databases for use in standardization at the following addresses:
— IEC Electropedia: available at https://www.electropedia.org/
— ISO Online browsing platform: available at https://www.iso.org/obp
3.1
agent
person, organization, or system that act in procurement or have the power to act in procurement
[SOURCE: eProcurement Ontology]
3.2
business process
sequence or network of activities and collaborations between two or more agents
3.3
business process variant
specification of a business process 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
Under development.
5
---------------------- Page: 7 ----------------------
oSIST prEN 17016-1:2023
prEN 17016-1:2022 (E)
3.4
choreography
set of business processes having the same goals
3.5
collaboration
interaction between two or more agents that result in the exchange of data between the agents involved
as part of a business process
3.6
role
part played by an agent in a particular business process, including its responsibilities (options and
obligations) to perform certain activities and collaborations in that business process
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 organization of an agent.
3.7
state
set of options and obligations of the participating agents at a defined step in a business process to
perform specific activities and collaborations
Note 1 to entry: Additional information: an activity of an agent or a collaboration may cause the transition of one
state to another in a predefined set of next steps.
3.8
transaction
content of data exchanged or shared between the agents in a collaboration
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 Business environment and high level business requirements
4.1 Choreographies (business) Goals
The business goals supported by implementing this choreography are described in Table 1:
Table 1 — Business goals
ID Description
G-17016-1:20xx-1 Enable trading partners to communicate without a previous bi-lateral
setup or agreement.
G-17016-1:20xx-2 Enable the automation of handling orders in a semi-manual environment.
G-17016-1:20xx-3 Enable customers to set up a standardized acquisition process.
G-17016-1:20xx-4 Enable SMEs to offer their trading partners the option of exchanging
standardised documents in a uniform way and thereby move all orders
into electronic form.
6
---------------------- Page: 8 ----------------------
oSIST prEN 17016-1:2023
prEN 17016-1:2022 (E)
The main business benefits to be gained by implementing this choreography are described in Table 2:
Table 2 — Business benefits
ID Description
G-17016-1:20xx-5 Realize significant savings both by customers and suppliers through
automating and streamlining in-house processes of ordering and
subsequent activities as well through increasing quality of data exchanged.
G-17016-1:20xx-6 Pave the way for the buyer to enforce a formal process of approval and
cost control within its organization.
G-17016-1:20xx-7 Facilitate the processing of the invoice and so faster payments
4.2 Business environment
4.2.1 Introduction
The intended scope for this choreography includes public procurement, but the choreography may also
be used in Business to Business (B2B) relations.
This choreography is intended to support use of electronic documents for processing in (semi-)
automated processes. The legal requirements that were taken into account are requirements from
European legislation, particularly the EU directives, as mentioned in the Bibliography of this document.
The list of the transactions being part of this choreography is defined in Clause 6.
4.2.2 Business context
This choreography belongs to the e-Ordering business area that is described in Figure 1:
Figure 1— Position of the Ordering BII Choreography in the Procurement process
7
---------------------- Page: 9 ----------------------
oSIST prEN 17016-1:2023
prEN 17016-1:2022 (E)
4.2.3 Positioning in EIRA
EIRA provides a reference model that enables architects to position the IOP specifications. This
document provides a domain-specific IOP specification to which any SBB implementing the ABB should
be compliant to. The positioning of this document in the EIRA context is described in Table 3.
IoP specifications provide a valuable source of information to formulate requirements during
architecture development and solution development. By identifying architectural building blocks
through a common terminology, it
— helps reuse of cross domain building blocks such for instance e-Signature Verification and
Validation Service, and e-Timestamp Creation Service;
— helps synchronization with European solutions such as CEF eDelivery;
— and will provide guidance in using them to provide the prescribed capability enabling, thus
managing and rationalizing IT portfolios.
Table 3 — Positioning in EIRA
EIRA ID Title Domain Interface Scope Modality
EN 17016-1:20xx Electronic Procurement Machine • e-procurement Endorsing
Public /Customer extension of ABB176
Procurement - Organizational
Machine
Ordering - Interoperability
/Supplier
Choreography Specification
• e-procurement
extension of ABB12
Business Capability,
• e-procurement
extension of ABB170
Exchange of Business
Information
• E-procurement
extension of ABB16
Business Rule
4.3 Organization and business partners involved
The following business partners participate in this BII Choreography, acting in the roles as defined in
Table 4 and Figure 2 below.
Table 4 — Roles
Key Role Description
Buyer A role of an agent that awards the contract. Additional information:
Examples of The Buyer may be the role of contracting authority, contracting
entity, a defence contractor, an international organization, or an
organization awarding a contract subsidized by a contracting authority.
Seller A role played by any natural or legal person or public entity or group of such
persons and/or entities, including any temporary association of
undertakings acting on behalf of a supplier who sells goods, works or
services to the buyer
8
---------------------- Page: 10 ----------------------
oSIST prEN 17016-1:2023
prEN 17016-1:2022 (E)
Figure 2 — Ordering BII Choreography Roles
4.4 High level business process requirements
4.4.1 High level business requirements
Based on the goals and scope of this choreography the following set of high-level requirements is
identified. Each requirement is connected to a goal.
Additionally, requirements of major business processes that are frequently supported within ordering
are listed.
These requirements are relevant for all variants depicted within this choreography and described in
Table 5.
Table 5 — High level business requirements
Req. ID Requirement statement Ref. to goal
HLR-17016-1:20xx-1 A Buyer submits an Order for delivery of goods, G-17016-1:20xx-1
services or works to a Seller.
HLR-17016-1:20xx-2 Actors involved in the ordering process require a G-17016-1:20xx-2
gradual automation of all information exchange
of the ordering process:
Depending on their capabilities, the
organizations may be willing to exchange
electronically only some transactions
participating in the process.
HLR-17016-1:20xx-3 Depending on the general rules of a national G-17016-1:20xx-1
environment and/or the sector specific
G-17016-1:20xx-2
rules/contractual terms actors may be willing to
G-17016-1:20xx-3
exchange electronic documents on the basis of
different business processes.
HLR-17016-1:20xx-4 Actors involved in the ordering process require a G-17016-1:20xx-2
gradual automation of all information exchange
G-17016-1:20xx-3
of the ordering process:
Depending on their capabilities, the
organizations may be willing to exchange
electronically only some core information in a
structured manner.
HLR-17016-1:20xx-5 Structured Ordering: The Order transaction G-17016-1:20xx-2
should support the structured ordering of goods
G-17016-1:20xx-3
and services, using free text or use of identifiers.
The information source of the ordered products
may be a (paper or electronic) catalogue.
9
---------------------- Page: 11 ----------------------
oSIST prEN 17016-1:2023
prEN 17016-1:2022 (E)
Req. ID Requirement statement Ref. to goal
HLR-17016-1:20xx-6 An Order may refer to framework agreement for G-17016-1:20xx-1
its items and conditions; Otherwise the
Customer terms and conditions apply.
HLR-17016-1:20xx-7 An Order may contain items (goods or services) G-17016-1:20xx-3
with item identifiers or items with free text
description or item specification
HLR-17016-1:20xx-8 If the Order is accepted, a contractual G-17016-1:20xx-1
commitment is established between the Buyer
and the Seller.
HLR-17016-1:20xx-9 Accounting: The ordering process shall support G-17016-1:20xx-6
the allocation of budgets, so the value amounts
of the ordered products may be stated. The
buyer may provide some information that the
supplier is required to place on the invoice for
aiding and automating the invoice processing.
HLR-17016-1:20xx-10 Invoice verification: The buyer may provide G-17016-1:20xx-7
some information that the supplier is required to
place on the invoice for aiding and automating
invoice approval.
HLR-17016-1:20xx-11 VAT reporting: VAT reporting is not a general G-17016-1:20xx-7
requirement on orders. The level of support in
orders is to:
- Enable VAT reporting in invoices by providing
VAT number of buyers in case of reverse
charges.
VAT can be stated as an estimate to enable
buyers to state expected value of order. This can
be helpful in automated matching of orders and
invoices. VAT information is informative and
does not affect the terms of trade.
HLR-17016-1:20xx-12 Transport and delivery: Only limited support is G-17016-1:20xx-3
in scope for transport related information, but it
is recognized that the buyer needs to be able to
provide some information about requested
delivery location (by use of identifiers or full
textual description).
HLR-17016-1:20xx-13 Inventory: Supporting inventory management is G-17016-1:20xx-3
not in scope, but structured orders based on
catalogues can be used to automate picking at
supplier warehouses.
NOTE:
Payment:
Information about pre-payment or arrangement of payment are not considered core functionality in order and are
therefore not supported.
10
---------------------- Page: 12 ----------------------
oSIST prEN 17016-1:2023
prEN 17016-1:2022 (E)
5 Processes
5.1 Introduction
In order to encompass the various maturity levels of organizations, (see HLR-17016-1:20xx-2), the
approach is to specify variants of business processes that use a set of activities around exchanging
information in different combinations, still fulfilling the goals set out in 4.1.
The state machine diagram depicted in Figure 3 provides information on the common states for systems
to get in agreement.
Figure 3 — Ordering State machine diagram [informative]
4
5.2 Business process variants
5.2.1 Introduction
Eight variants are identified as reported in the following table. They allow for supporting different
levels of interoperability maturity of the organizations willing to automate the exchange of information
in the business area at stake as defined by High level requirement HLR.
The variants combine in various ways the basic processes defined above through various collaborations
between Buyer and Seller as described in Table 6.
4
Subclause 5.2 falls under derivative use (as set out in the Introduction). When replicating the section, the content
may be modified.
11
---------------------- Page: 13 ----------------------
oSIST prEN 17016-1:2023
prEN 17016-1:2022 (E)
Table 6 — Business process variants
Business Process Short name Description
Variant
BPV-17016-1:20xx:A Simple Ordering The Buyer sends an Order to the Seller.
The Seller does not respond to the Buyer.
BPV-17016-1:20xx:B Buyer Managed The Buyer sends an Order to the Seller.
Ordering
The Seller does not respond to the Buyer.
The Buyer may send message/s to the Seller to
change/cancel an Order until the Order is fully
delivered.
The Seller does not respond to the Buyer to
accept/reject changes or cancellation.
BPV-17016-1:20xx:C Ordering with The Buyer sends an Order to the Seller.
Simple Response
The Seller responds to the Buyer in any case.
The Seller may:
• state that the Order was received;
• accept the Order without changes;
• reject the Order.
BPV-17016-1:20xx:D Buyer Managed The Buyer sends an Order to the Seller.
Ordering with
The Seller responds to the Buyer in any case.
Seller’s response
The Seller may:
• state that the Order was received;
• accept the Order without changes;
• reject the Order.
The Buyer may send message/s to the Seller to
change/cancel a confirmed Order until the Order is
fully delivered.
The Seller responds to the Buyer to accept/reject
changes or cancellation.
BPV-17016-1:20xx:E Ordering The Buyer sends an Order to the Seller.
The Seller responds to the Buyer in any case.
The Seller may:
• state that the Order was received;
• accept the Order with or without changes;
• reject the Order.
The Seller may send message/s to the Buyer to
change a confirmed Order until the Order is fully
delivered.
The Buyer does not respond to the Seller to
accept/reject the changes.
12
---------------------- Page: 14 ----------------------
oSIST prEN 17016-1:2023
prEN 17016-1:2022 (E)
Business Process Short name Description
Variant
BPV-17016-1:20xx:F Advanced The Buyer sends an Order to the Seller.
Ordering
The Seller responds to the Buyer in any case.
The Seller may:
...
Questions, Comments and Discussion
Ask us and Technical Secretary will try to provide an answer. You can facilitate discussion about the standard in here.