SIST EN 17367:2023
(Main)Waste Management - Data communication between communication management system and the back office system for stationary waste collection containers - Functional specification and the semantic data model
Waste Management - Data communication between communication management system and the back office system for stationary waste collection containers - Functional specification and the semantic data model
This document defines the standard for exchanging stationary waste collection container information between the collection container system and the back-office systems.
This document defines the way to exchange data between the "Communication Management System" of the collection container and the "Back-Office Systems".
The exchange of data between the "Collection Container Systems" and the "Communication Management Systems" or the "Back-Office Systems" is excluded.
This document targets two streams of information in the waste processing industry:
- The processing of transactions and system information for the deposit of waste from the communication management systems to the back office systems.
- The processing of authorization and configuration information from the back-office systems to the communication management systems.
Abfallwirtschaft - Datenkommunikation zwischen dem Kommunikationsmanagementsystem und dem Hintergrundsystem für stationäre Abfallsammelbehälter - Funktionale Spezifikation und das semantische Datenmodell
Dieses Dokument definiert eine Norm für den Austausch von stationären Abfallsammelbehälterinfor-mationen zwischen dem Sammelbehältersystem und den Hintergrundsystemen.
Dieses Dokument definiert die Art des Datenaustauschs zwischen „Kommunikations-Managementsystemen“ des Sammelbehälters und den „Hintergrundsystemen“.
Der Datenaustausch zwischen „Sammelbehältersystemen“ und den „Kommunikations-Managementsys-temen“ oder „Hintergrundsystemen“ bleibt ausgenommen.
Dieses Dokument zielt auf zwei Informationsflüsse in der Abfallverarbeitungsbranche ab:
- Die Verarbeitung von Transaktionen und Systeminformationen zur Abfalllagerung von den Kommunika¬tions-Managementsystemen zu den Hintergrundsystemen.
- Die Verarbeitung von Autorisierungs- und Konfigurationsinformationen von den Hintergrundsystemen zu den Kommunikations-Managementsystemen.
Gestion des déchets - Communication de données entre le système de gestion des communications et le système de services support pour les conteneurs fixes de collecte des déchets - Spécifications fonctionnelles et modèle sémantique de données
Le présent document définit la norme relative à l’échange d’informations concernant les conteneurs fixes de collecte des déchets entre le système de conteneurs de collecte et les systèmes de services support.
Le présent document définit le mode d'échange de données entre « le Système de gestion des communications du conteneur de collecte » et « les Systèmes de services support ».
L'échange de données entre « les Systèmes de conteneurs de collecte » et « les Systèmes de gestion des communications » ou « les Systèmes de services support » est exclu.
Le présent document se concentre sur deux flux d'informations dans l'industrie du traitement des déchets :
- le traitement des informations de transaction et de système concernant le dépôt de déchets, entre les systèmes de gestion des communications et les systèmes de services support ;
- le traitement des informations d’autorisation et de configuration, entre les systèmes de services support et les systèmes de gestion des communications.
Ravnanje z odpadki - Izmenjava podatkov med komunikacijskim sistemom upravljanja in zalednim sistemom za nepremične zabojnike za zbiranje odpadkov - Funkcijska specifikacija in semantični podatkovni model
Ta dokument določa standard za izmenjavo informacij o nepremičnih zabojnikih za zbiranje odpadkov med sistemom zabojnikov za zbiranje odpadkov in zalednimi sistemi.
Ta dokument določa način izmenjave podatkov med »komunikacijskim sistemom upravljanja« zabojnika za zbiranje in »zalednimi sistemi«.
Izmenjava podatkov med »sistemi zabojnikov za zbiranje odpadkov« in »komunikacijskimi sistemi upravljanja « ali »zalednimi sistemi« ni zajeta.
Ta dokument se osredotoča na dva toka informacij v panogi predelave odpadkov:
– Obdelava transakcij in informacij o sistemu za odlaganje odpadkov iz komunikacijskih sistemov upravljanja v zaledne sisteme.
– Obdelava avtorizacije in informacij o konfiguraciji iz zalednih sistemov v komunikacijske sisteme upravljanja.
General Information
Standards Content (Sample)
SLOVENSKI STANDARD
SIST EN 17367:2023
01-julij-2023
Ravnanje z odpadki - Izmenjava podatkov med komunikacijskim sistemom
upravljanja in zalednim sistemom za nepremične zabojnike za zbiranje odpadkov -
Funkcijska specifikacija in semantični podatkovni model
Waste Management - Data communication between communication management
system and the back office system for stationary waste collection containers - Functional
specification and the semantic data model
Abfallwirtschaft - Datenkommunikation zwischen dem
Kommunikationsmanagementsystem und dem Hintergrundsystem für stationäre
Abfallsammelbehälter - Funktionale Spezifikation und das semantische Datenmodell
Gestion des déchets - Communication de données entre le système de gestion des
communications et le système de services support pour les conteneurs fixes de collecte
des déchets - Spécifications fonctionnelles et modèle sémantique de données
Ta slovenski standard je istoveten z: EN 17367:2023
ICS:
13.030.40 Naprave in oprema za Installations and equipment
odstranjevanje in obdelavo for waste disposal and
odpadkov treatment
35.240.99 Uporabniške rešitve IT na IT applications in other fields
drugih področjih
SIST EN 17367:2023 en,fr,de
2003-01.Slovenski inštitut za standardizacijo. Razmnoževanje celote ali delov tega standarda ni dovoljeno.
---------------------- Page: 1 ----------------------
SIST EN 17367:2023
---------------------- Page: 2 ----------------------
SIST EN 17367:2023
EN 17367
EUROPEAN STANDARD
NORME EUROPÉENNE
May 2023
EUROPÄISCHE NORM
ICS 13.030.40; 35.240.99
English Version
Waste Management - Data communication between
communication management system and the back office
system for stationary waste collection containers -
Functional specification and the semantic data model
Gestion des déchets - Communication de données entre Abfallwirtschaft - Datenkommunikation zwischen dem
le système de gestion des communications et le Kommunikationsmanagementsystem und dem
système de services support pour les conteneurs fixes Hintergrundsystem für stationäre
de collecte des déchets - Spécifications fonctionnelles Abfallsammelbehälter - Funktionale Spezifikation und
et modèle sémantique de données das semantische Datenmodell
This European Standard was approved by CEN on 17 March 2023.
CEN members are bound to comply with the CEN/CENELEC Internal Regulations which stipulate the conditions for giving this
European Standard the status of a national standard without any alteration. Up-to-date lists and bibliographical references
concerning such national standards may be obtained on application to the CEN-CENELEC Management Centre or to any CEN
member.
This European Standard exists in three official versions (English, French, German). A version in any other language made by
translation under the responsibility of a CEN member into its own language and notified to the CEN-CENELEC Management
Centre has the same status as the official versions.
CEN members are the national standards bodies of Austria, Belgium, Bulgaria, Croatia, Cyprus, Czech Republic, Denmark, Estonia,
Finland, 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
© 2023 CEN All rights of exploitation in any form and by any means reserved Ref. No. EN 17367:2023 E
worldwide for CEN national Members.
---------------------- Page: 3 ----------------------
SIST EN 17367:2023
EN 17367:2023 (E)
Contents Page
European foreword . 3
Introduction . 3
1 Scope . 5
2 Normative references . 5
3 Terms and definitions . 5
4 Functional requirements . 6
4.1 Involved systems and their functions. 6
4.2 (Business) processes supported by this standard . 8
4.3 Unique identification of mediums . 9
4.3.1 General. 9
4.3.2 Medium type . 9
4.3.3 Issuer identifier . 10
4.3.4 Medium identifier . 10
4.3.5 Composing the unique identifier. 10
4.4 Unique identification of collection containers . 10
4.4.1 General. 10
4.4.2 Issuer identifier . 10
4.4.3 Container identifier . 11
5 The semantic message models . 12
5.1 Transactions message . 12
5.2 System information message . 14
5.3 Authorizations message . 16
5.4 Authorizations patch . 17
5.5 Configuration message. 18
6 Code lists . 24
6.1 General. 24
6.2 Medium Types . 24
6.3 Registration Types . 24
6.4 Transaction Types . 24
6.5 Event Types . 24
Bibliography . 25
2
---------------------- Page: 4 ----------------------
SIST EN 17367:2023
EN 17367:2023 (E)
European foreword
This document (EN 17367:2023) has been prepared by Technical Committee CEN/TC 183 “Waste
management”, the secretariat of which is held by DIN.
This European Standard shall be given the status of a national standard, either by publication of an
identical text or by endorsement, at the latest by November 2023 and conflicting national standards shall
be withdrawn at the latest by November 2023.
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.
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 organizations of the
following countries are bound to implement this European Standard: 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.
3
---------------------- Page: 5 ----------------------
SIST EN 17367:2023
EN 17367:2023 (E)
Introduction
This standard aims at realizing the interoperability between communication management systems of
waste collection containers and related back-office systems of waste processing companies. This is
intended for use in a single system architecture with (potentially) different vendors, end-users and waste
processing companies. Purposely we strive at making a base for future developments in the branch.
This document has taken the present version 2.1 of the Dutch STOSAG Norm as a starting point.
This document is accompanied by a set of technical specifications for software developers implementing
this standard. Those are made available on Github.com and include:
• REST API specifications in Open API Specification (OAS) format;
• XML schema specifications that are derived from the semantic data models described in this
document;
• XML example files.
The technical specifications can be found here: [1].
4
---------------------- Page: 6 ----------------------
SIST EN 17367:2023
EN 17367:2023 (E)
1 Scope
This document defines the standard for exchanging stationary waste collection container information
between the collection container system and the back-office systems.
This document defines the way to exchange data between the “Communication Management System” of
the collection container and the “Back-Office Systems”.
The exchange of data between the “Collection Container Systems” and the “Communication Management
Systems” or the “Back-Office Systems” is excluded.
This document targets two streams of information in the waste processing industry:
• The processing of transactions and system information for the deposit of waste from the
communication management systems to the back-office systems.
• The processing of authorization and configuration information from the back-office systems to the
communication management systems.
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.
3.1
authorization
relation between the collection container and the unique identifiers specifying whether or not the UID
(unique identifier) can be used to perform a transaction on the collection container
3.2
authorization list
register containing unique identification numbers that shall be refused or handled by the system using
the register
3.3
black list
authorization list that contains unique identifiers that do not allow the deposit of waste, including all kind
of fractions
OR
(authorization list that contains unique identifiers whose holders are not allowed to deposit waste,
including all kind of fractions)
Note 1 to entry: This document does not provide a data model to exchange black list information. Instead, a white
listing mechanism shall be used, see 5.3 for the Authorizations message.
3.4
collection container
reservoir capable of containing waste and fractions for a group of end-users
5
---------------------- Page: 7 ----------------------
SIST EN 17367:2023
EN 17367:2023 (E)
3.5
collection container system
complete set of components, hardware and software to operate a group of collection containers
3.6
communication management system
CMS
part of the collection container system that is responsible for the communication with the back-office
systems and the collection containers in the field
3.7
end-user
party (e.g. citizen, household or business) that wants to dispose of waste, including all kind of fractions
3.8
management and configuration system
part of a waste processing back-office system that is responsible for the data communication with
communication management system(s) of suppliers of collection container systems
3.9
transaction
registration of a deposit of waste and fractions in the collection container
3.10
unique identifier
UID
unique identifier of medium by which an end-user authenticates itself
EXAMPLE This medium can be e.g. a radiofrequency identification (RFID) tag, a nearfield communication
(NFC) chip or a quick response (QR) code.
3.11
waste processing back office system
information system that the waste processing companies use to manage the collection of waste and
fractions, containers and related internal processes
3.12
white list
authorization list that contains unique identifiers that allow the deposit of waste, including all kind of
fractions
OR
(authorization list that contains unique identifiers whose holders are allowed to deposit waste, including
all kind of fractions)
4 Functional requirements
4.1 Involved systems and their functions
This paragraph gives an overview of the relevant systems and the situation in which they interact in
Figure 1.
6
---------------------- Page: 8 ----------------------
SIST EN 17367:2023
EN 17367:2023 (E)
Figure 1 — Overview of the process and involved systems
This document defines the data communication between the communication management system of the
collection containers and back-office systems as depicted by the numbers 1 to 4 in Figure 1. All other
interfaces are out of scope and merely provided as an overview of how a complete system architecture
could look like.
Table 1 gives a description for each of the objects and systems involved.
Table 1 — Descriptions objects and systems
Object or system Description
Medium with UID The medium held by an end-user has a unique identifier (UID)
that can be used to gain access a collection container.
Collection container A container that can be used by multiple end-users to deposit
waste, including all kind of fractions. The container is often
stationary, but this is not necessary.
The design of the collection container is vendor specific. Usually a
collection container consists of several components, including:
• Reader: device, placed on a collection container, capable of
reading data contained on a medium.
• Controller: device capable of interaction with a reader and
converting the data into usable information and controlling
the operation of a collection container
• Antenna for remote communication with vendor system, e.g.
using the mobile network.
Collection container system The collection container system is vendor specific and consists of
a group of collection containers and a communication
management system. The communication management system is
responsible for the interaction with the group of collection
containers it manages. Furthermore, this system has the
responsibility to provide all transaction and system information
to the back-office systems and process received authorization and
configuration information
Back-office systems The back-office systems receive, store and make available the
information of the collection containers systems.
7
---------------------- Page: 9 ----------------------
SIST EN 17367:2023
EN 17367:2023 (E)
4.2 (Business) processes supported by this standard
There are four use cases that are supported by the standard. A description of each of these use cases can
be found in Table 2.
Table 2 — Use case descriptions
Role Use case
Collection 1. The collection container system sends transaction information to the back-office
container systems.
system
2. The collection container system sends system information to the back-office systems.
3. The collection container system receives an authorization list from the back-office
systems.
4. The collection container system receives a configuration list from the back-office
systems.
Back- 1. The back-office systems receive transaction information from the collection container
office system.
systems
2. The back-office systems receive system information from the collection container
system.
3. The back-office systems send an authorization list to the collection container system.
4. The back-office systems send a configuration list to the collection container system.
This results in four interfaces defined between collection container systems and back-office systems as
depicted in Figure 2.
Note that the interface for authorization information is split into 2 sub-interfaces. Interface 3a to send an
initial or complete new/updated authorizations list and 3b to specify incremental changes (patches) to
an existing authorizations list as depicted in Figure 2.
Note that there is no sequential order required for the interfaces to work. The interface numbering is only
for reference purposes within this document.
8
---------------------- Page: 10 ----------------------
SIST EN 17367:2023
EN 17367:2023 (E)
Figure 2 — Sequence diagram of interfaces
4.3 Unique identification of mediums
4.3.1 General
End-user authentication mediums (e.g. RFID tags and NFC chips) shall be uniquely identified by a
combination of a) the medium type, b) an issuer identifier and c) an identifier of the medium itself.
4.3.2 Medium type
The medium type is an 8-bit code according to the Medium Types code list as specified in 6.2.
EXAMPLE An LF RFID tag has medium type code 3 (integer), which corresponds to an 8-bit binary code of
0000 0011.
9
---------------------- Page: 11 ----------------------
SIST EN 17367:2023
EN 17367:2023 (E)
4.3.3 Issuer identifier
The issuer identifier is determined by and the responsibility of the back-office system. It is an 8-bit
identifier that allows for up to 255 different issuers.
This part of the UID of the medium is NOT used to recognize the medium during authentication, but it
serves as a means to be able to prevent duplicate medium identifiers. This is for example the case when
issuing the identifier is not in control of the back-office system itself. The back-office system can “prefix”
the identifiers to prevent duplicates.
In case of mediums that already have a (globally) unique identifier themselves (e.g. the IMEI number of
mobile phones), the issuer identifier MAY be set to an arbitrary value, e.g. 0.
EXAMPLE An issuer identifier with decimal value (13) corresponds to an 8-bit binary code of 0000 1101.
4.3.4 Medium identifier
The medium identifier is a variable length part of the unique identifier because it depends on the type of
medium.
For example:
• LF RFID transponder number with hex value ‘0004 0000 0311 B4B0’
• IMEI number with decimal value ‘49 015420 323751 8’
• UUID v4 identifier with string value ‘e9f64d46-fc97-4754-8c29-913f69465700’
All binary identifiers (e.g. RFID transponder number) SHALL be communicated LSB last.
4.3.5 Composing the unique identifier
All parts of the unique identifier shall be converted to a hexadecimal value and put together.
EXAMPLE The LF RFID tag (medium code 3) issued by issuer 13 with binary transponder number ‘0000 0000
0000 0100 0000 0000 0000 0000 0000 0011 0001 0001 1011 0100 1011 0000’ results in the following hexadecimal
unique identifier: 03 0D 0004 0000 0311 B4B0.
4.4 Unique identification of collection containers
4.4.1 General
Collection containers can be uniquely identified by means of a combination of a) an identifier of the
organization issuing the container identifier and b) an identifier of the collection container itself.
4.4.2 Issuer identifier
The issuer of a container identifier is usually the supplier of the collection container systems, but this is
not necessarily the case.
Issuers of collection container identifiers are specified using the Electronic Address Scheme (EAS) code
list defined and maintained by the European Commission’s Connecting Europe Facility (CEF), see [2].
The EAS code list specifies existing identification schemes, like GS1’s global location number (GLN), EU’s
VAT scheme and national Chamber of Commerce schemes, see [3] and [4]. The combination of such a
scheme identifier and an organization identifier according to that scheme provides a unique identifier for
an issuer.
10
---------------------- Page: 12 ----------------------
SIST EN 17367:2023
EN 17367:2023 (E)
For example:
• A supplier has the following GLN identifier: 5790000435944
• The EAS code for the GLN scheme is 0088
• This combination provides a unique identifier for that supplier.
For more information about the EAS code list and the latest version, see [2].
4.4.3 Container identifier
This norm does not set any restriction on the identifier of the collection container. Organizations are free
to assign any alphanumeric identifier, e.g. ‘C12345’ or a UUID like ‘35d32606-9c96-42f0-bf4b-
3aa59ea1b9fb’.
11
---------------------- Page: 13 ----------------------
SIST EN 17367:2023
EN 17367:2023 (E)
5 The semantic message models
5.1 Transactions message
Table 3 — Semantic data model of the core elements of collection container transactions
Level Min.max Business Term Description Data type Usage note
occurrence
1 1.1 Message identifier Number of the message. Integer Shall be an increasing number. May
restart at 1 after the maximum
number is reached, or after
changing the controller.
1 1.n Transaction The registration of a deposit of waste and fractions
in the collection container.
2 1.1 Transaction Number of the transaction, shall be an increasing Integer
number number. May restart at 1 after the maximum
number is reached, or after changing the controller.
2 1.1 Transaction type The type of the transaction that is used to Integer The allowed values for this element
are specified in the code list:
determine the action of the collection container.
Value: 100 - 999
“Transaction Types”.
2 1.1 Medium UID Unique identifier of the medium that is used to Hexadecimal See 4.3
authenticate for this transaction.
2 1.1 Timestamp The specified date and time the transaction took DateTimestamp
place.
2 1.1 Collection Collection container to which this transaction
container applies.
3 1.1 Container Number by which the collection container can be Alphanumerical Usually the responsibility of
identifier identified. This number has to be unique in the assigning the container identifier
context of the party responsible for assigning the lies at the supplier of the collection
number to the specified container. container system.
12
---------------------- Page: 14 ----------------------
SIST EN 17367:2023
EN 17367:2023 (E)
Min.max
Level Business Term Description Data type Usage note
occurrence
3 1.1 Container Number by which the supplier of the collection Alphanumerical See 4.3
supplier container can be identified.
identifier
3 0.1 Subcontainer Identifier by which a subcontainer (drum/volume Alphanumerical
identifier type/fraction) can be identified if applicable for the
concerning collection container.
2 0.1 Weights Grouping element for weighing information for this
transaction
3 1.1 Weight Specifies the classification of the weighing value Integer This information is needed by the
classification that are specified for this transaction. back-office system for billing
Value: 0 - 3
purposes. Only valid measurements
Allowed values are:
can be used for legal and/or
• 0: valid measurement
invoicing purposes.
• 1: under minimum weight
• 2: over load
• 3: error during measurement
3 0.1 Gross weight The gross weight in gram of the waste and Integer
fractions that is offered during the transaction.
Gross weight includes the weight of the container
parts that hold the waste (e.g. drum or even the full
container).
3 0.1 Net weight The net weight in gram of the waste and fractions Integer
that is offered during the transaction.
3 0.1 Tare weight The tare weight in gram of the empty containers Integer
parts that can hold the waste (e.g. drum). Tare
weight is the difference between the gross weight
and the net weight of the waste and fractions
offered during the transaction.
2 0.1 Volume The volume in millilitre of the waste and fractions Integer
that is offered during the transaction.
Max value:
999999
13
---------------------- Page: 15 ----------------------
SIST EN 17367:2023
EN 17367:2023 (E)
5.2 System information message
Table 4 — Semantic data model of the core elements of collection container system information
Level Min.max Business Term Description Data type Usage note
occurrence
1 1.1 Message identifier Number of the message. Integer Shall be an increasing number. May
restart at 1 after the maximum
number is reached, or after
changing the controller.
1 1.n Container system The registration of system information in a
information collection container.
2 1.1 Timestamp The specified date and time the system DateTimestamp
information registration took place.
2 1.1 Collection container Collection container to which this transaction
applies.
3 1.1 Container Number by which the collection container can be Alphanumerical Usually the responsibility of
identifier identified. This number has to be unique in the assigning the container identifier
context of the party responsible for assigning the lies at the supplier of the collection
number to the specified container. container system.
3 1.1 Container Number by which the supplier of the collection Alphanumerical See 4.4.2
supplier container can be identified.
identifier
3 0.1 Subcontainer Identifier by which a subcontainer Alphanumerical
identifier (drum/volume type/fraction) can be identified if
applicable for the concerning collection
container.
The event that occurred or threshold value that is The allowed values for this element
2 1.1 Trigger Integer
reached that initiated the transmission of a are specified in the code list: “Event
Value: 100 - 599
message from the collection container to the back Types”.
office system.
2 0.1 Software version The version number of the firmware that is Alphanumerical
loaded onto the hardware of the collection
Max length: 16
container.
chars
14
---------------------- Page: 16 ----------------------
SIST EN 17367:2023
EN 17367:2023 (E)
Min.max
Level Business Term Description Data type Usage note
occurrence
2 0.1 Authorization list The unique number of the Authorization message Integer
message identifier in Figure 1 (3) that contained the authorization
list that is currently active.
Configuration The unique number of the Configuration message
2 0.1 Integer
message identifier in Figure 1 (4) that contained the configuration
that is currently active.
The maximum number of units that the container
2 0.1 Maximum load
can contain.
3 1.1 Unit The unit of the specified amount. Alphanumerical Allowed values: centimetres, gram,
millilitre, pieces.
3 1.1 Value The specified amount. Integer
2 0.1 Current load The load of the container on the date and time
specified in the timestamp.
Allowed values: centimetres, gram,
3 1.1 Unit The unit of the specified amount. Alphanumerical
millilitre, pieces.
3 1.1 Value The specified amount. Integer
2 0.1 Battery capacity The amount of power in the battery pack that is Integer Integer is expressed in a round
supplying the collection container with power. percentage.
Value: 0 - 100
2 0.1 Inside temperature The inside temperature of the collection Decimal
container in degrees Celsius.
2 0.1 Signal strength The strength of the wireless signal which the Integer Integer is expressed in a round
container is using to transmit information to the percentage.
Value: 0 - 100
communication management system.
2 0.n System information List of elements that can contain information that This element shall NOT contain
is sent from the container to the back-office information for which separate
system. elements are already defined.
3 1.1 Key Key to identify the information that is sent. Alphanumerical
3 1.1 Value The system information itself. Alphanumerical
...
SLOVENSKI STANDARD
oSIST prEN 17367:2022
01-marec-2022
Ravnanje z odpadki - Izmenjava podatkov med komunikacijskim sistemom
upravljanja in zalednim sistemom za nepremične zabojnike za zbiranje odpadkov -
Funkcijska specifikacija in semantični podatkovni model
Waste Management - Data communication between communication management
system and the back office system for stationary waste collection containers - Functional
specification and the semantic data model
Abfallwirtschaft - Datenkommunikation zwischen dem
Kommunikationsmanagementsystem und dem nachgeordneten Verwaltungssystem für
Stationärcontainer
Gestion des déchets - Communication de données entre le système de gestion des
communications et le système de services support pour les conteneurs fixes de collecte
des déchets - Spécifications fonctionnelles et modèle sémantique de données
Ta slovenski standard je istoveten z: prEN 17367
ICS:
13.030.40 Naprave in oprema za Installations and equipment
odstranjevanje in obdelavo for waste disposal and
odpadkov treatment
35.240.99 Uporabniške rešitve IT na IT applications in other fields
drugih področjih
oSIST prEN 17367:2022 en,fr,de
2003-01.Slovenski inštitut za standardizacijo. Razmnoževanje celote ali delov tega standarda ni dovoljeno.
---------------------- Page: 1 ----------------------
oSIST prEN 17367:2022
---------------------- Page: 2 ----------------------
oSIST prEN 17367:2022
DRAFT
EUROPEAN STANDARD
prEN 17367
NORME EUROPÉENNE
EUROPÄISCHE NORM
December 2021
ICS 13.030.40; 35.240.99
English Version
Waste Management - Data communication between
communication management system and the back office
system for stationary waste collection containers -
Functional specification and the semantic data model
Gestion des déchets - Communication de données entre Abfallwirtschaft - Datenkommunikation zwischen dem
le système de gestion des communications et le Kommunikationsmanagementsystem und dem
système de services support pour les conteneurs fixes nachgeordneten Verwaltungssystem für
de collecte des déchets - Spécifications fonctionnelles Stationärcontainer
et modèle sémantique de données
This draft European Standard is submitted to CEN members for enquiry. It has been drawn up by the Technical Committee
CEN/TC 183.
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, Turkey 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
© 2021 CEN All rights of exploitation in any form and by any means reserved Ref. No. prEN 17367:2021 E
worldwide for CEN national Members.
---------------------- Page: 3 ----------------------
oSIST prEN 17367:2022
prEN 17367:2021 (E)
Contents Page
European foreword . 3
Introduction . 4
1 Scope . 5
2 Normative references . 5
3 Terms and definitions . 5
4 Functional requirements . 6
4.1 Involved systems and their functions. 6
4.2 (Business) processes supported by this standard . 8
4.3 Unique identification of mediums . 9
4.3.1 General. 9
4.3.2 Medium type . 9
4.3.3 Issuer identifier . 10
4.3.4 Medium identifier . 10
4.3.5 Composing the unique identifier. 10
4.4 Unique identification of collection containers . 10
4.4.1 General. 10
4.4.2 Issuer identifier . 10
4.4.3 Container identifier . 11
5 The semantic message models . 12
5.1 Transactions message . 12
5.2 System information message . 14
5.3 Authorizations message . 16
5.4 Authorizations patch . 17
5.5 Configuration message. 18
6 Code lists . 24
6.1 General. 24
6.2 Medium Types . 24
6.3 Registration Types . 24
6.4 Transaction Types . 24
6.5 Event Types . 24
2
---------------------- Page: 4 ----------------------
oSIST prEN 17367:2022
prEN 17367:2021 (E)
European foreword
This document (prEN 17367:2021) has been prepared by Technical Committee CEN/TC 183 “Waste
management”, the secretariat of which is held by DIN.
This document is currently submitted to the CEN enquiry.
3
---------------------- Page: 5 ----------------------
oSIST prEN 17367:2022
prEN 17367:2021 (E)
Introduction
This standard aims at realizing the interoperability between communication management systems of
waste collection containers and related back-office systems of waste processing companies. This is
intended for use in a single system architecture with (potentially) different vendors, end-users and
waste processing companies. Purposely we strive at making a base for future developments in the
branch.
This document has taken the present version 2.1 of the Dutch STOSAG Norm as a starting point.
This document is accompanied by a set of technical specifications for software developers
implementing this standard. Those are made available on Github and include:
• REST API specifications in Open API Specification (OAS) format;
• XML schema specifications that are derived from the semantic data models described in this
standard;
• XML example files.
The technical specifications can be found here: https://github.com/Michiel-s/EN 17367.
4
---------------------- Page: 6 ----------------------
oSIST prEN 17367:2022
prEN 17367:2021 (E)
1 Scope
This document defines the standard for exchanging stationary waste collection container information
between the collection container system and the back-office systems.
This document defines the way to exchange data between the “Communication Management System” of
the collection container and the “Back-Office Systems”.
The exchange of data between the “Collection Container Systems” and the “Communication
Management Systems” or the “Back-Office Systems” is excluded.
This document targets two streams of information in the waste processing industry:
• The processing of transactions and system information for the deposit of waste from the
communication management systems to the back office systems.
• The processing of authorization and configuration information from the back-office systems to the
communication management systems.
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.
3.1
authorization
relation between the collection container and the unique identifiers specifying whether or not the UID
can be used to perform a transaction on the collection container
3.2
authorization list
register containing unique identification numbers that should be refused or handled by the system
using the register
3.3
black list
authorization list that contains unique identifiers that are not allowed to deposit waste and fractions
Note 1 to entry: This standard does not provide a data model to exchange black list information. Instead, a white
listing mechanism shall be used, see 5.3 for the Authorizations message.
3.4
collection container
reservoir capable of containing waste and fractions for a group of end-users
3.5
collection container system
complete set of components, hardware and software to operate a group of collection containers
5
---------------------- Page: 7 ----------------------
oSIST prEN 17367:2022
prEN 17367:2021 (E)
3.6
communication management system
CMS
specific part of the collection container system that is responsible for the communication with the back-
office systems and the collection containers in the field
3.7
end-user
party (e.g. citizen, household or business) that wants to dispose waste and fractions
3.8
management and configuration system
specific part of a waste processing back-office system that is responsible for the data communication
with communication management system(s) of suppliers of collection container systems
3.9
transaction
registration of a deposit of waste and fractions in the collection container
3.10
unique identifier
UID
unique identifier of medium by which an end-user authenticates itself
EXAMPLE This medium can be e.g. a RFID tag, NFC chip or QR code.
3.11
waste processing back office
systems that the waste processing companies use to manage the collection of waste and fractions,
containers and related internal processes
3.12
white list
authorization list that contains unique identifiers that are allowed to deposit waste and fractions
4 Functional requirements
4.1 Involved systems and their functions
This paragraph gives an overview of the relevant systems and the situation in which they interact in
Figure 1.
6
---------------------- Page: 8 ----------------------
oSIST prEN 17367:2022
prEN 17367:2021 (E)
Figure 1 — Overview of the process and involved systems
This norm defines the data communication between the communication management system of the
collection containers and back-office systems as depicted by the numbers 1 to 4. All other interfaces are
out of scope and merely provided as an overview of how a complete system architecture could look like.
Table 1 gives a description for each of the objects and systems involved.
Table 1 — Descriptions objects and systems
Object or system Description
Medium with UID The medium held by an end-user has a unique identifier (UID)
that can be used to gain access a collection container.
Collection container A container that can be used by multiple end-users to deposit
waste and fractions. The container is often stationary, but this is
not necessary.
The design of the collection container is vendor specific. Usually a
collection container consist of several components, including:
• Reader: device, placed on a collection container, capable of
reading data contained on a medium.
• Controller: device capable of interaction with a reader and
transferring the data to usable information and controlling
the behaviour of a collection container.
• Antenna for remote communication with vendor system e.g.
using the mobile network.
Collection container system The collection container system is vendor specific and consists of
a group of collection containers and a communication
management system. The communication management system is
responsible for the interaction with the group of collection
containers it manages. Furthermore this system has the
responsibility to provide all transaction and system information
to the back-office systems and process received authorization and
configuration information
Back-office systems The back-office systems receive, store and make available the
information of the collection containers systems.
7
---------------------- Page: 9 ----------------------
oSIST prEN 17367:2022
prEN 17367:2021 (E)
4.2 (Business) processes supported by this standard
There are four use cases that are supported by the standard. A description of each of these use cases can
be found in Table 2.
Table 2 — Use case descriptions
Role Use case
Collection 1. The collection container system sends transaction information to the back-office
container systems.
system
2. The collection container system sends system information to the back-office
systems.
3. The collection container system receives an authorization list from the back-office
systems.
4. The collection container system receives a configuration from the back-office
systems.
Back- 1. The back-office systems receive transaction information from the collection
office container system.
systems
2. The back-office systems receive system information from the collection container
system.
3. The back-office systems send an authorization list to the collection container.
4. The back-office systems send a configuration list to the collection container.
This resulted in four interfaces defined between collection container systems and back-office systems
as depicted in Figure 2.
Note that the interface for authorization information is split into 2 sub-interfaces. Interface 3a to send
an initial or complete new/updated authorizations list and 3b to specify incremental changes (patches)
to an existing authorizations list.
Note that there is no sequential order required for the interfaces to work. The interface numbering is
only for reference purposes within this document.
8
---------------------- Page: 10 ----------------------
oSIST prEN 17367:2022
prEN 17367:2021 (E)
Figure 2 — Sequence diagram of interfaces
4.3 Unique identification of mediums
4.3.1 General
End-user authentication mediums (e.g. RFID tags and NFC chips) shall be uniquely identified by a
combination of a) the medium type, b) an issuer identifier and c) an identifier of the medium itself.
4.3.2 Medium type
The medium type is an 8-bit code according to the Medium Types code list as specified in 6.2.
EXAMPLE An LF RFID tag has medium type code 3 (integer), which corresponds to an 8-bit binary code of
0000 0011.
9
---------------------- Page: 11 ----------------------
oSIST prEN 17367:2022
prEN 17367:2021 (E)
4.3.3 Issuer identifier
The issuer identifier is determined by and the responsibility of the back-office system. It is an 8-bit
identifier that allows for up to 255 different issuers.
This part of the UID of the medium is NOT used to recognize the medium during authentication, but it
serves as a means to be able to prevent duplicate medium identifiers. This is for example the case when
issuing the identifier is not in control of the back-office system itself. The back-office system can “prefix”
the identifiers to prevent duplicates.
In case of mediums that already have a (globally) unique identifier themselves (e.g. the IMEI number of
mobile phones), the issuer identifier MAY be set to an arbitrary value, e.g. 0.
EXAMPLE An issuer identifier with decimal value (13) corresponds to an 8-bit binary code of 0000 1101.
4.3.4 Medium identifier
The medium identifier is a variable length part of the unique identifier because it depends on the type of
medium.
For example:
• LF RFID transponder number with hex value ‘0004 0000 0311 B4B0’
• IMEI number with decimal value ‘49 015420 323751 8’
• UUID v4 identifier with string value ‘e9f64d46-fc97-4754-8c29-913f69465700’
All binary identifiers (e.g. RFID transponder number) SHALL be communicated LSB last.
4.3.5 Composing the unique identifier
All parts of the unique identifier shall be converted to a hexadecimal value and put together.
EXAMPLE The LF RFID tag (medium code 3) issued by issuer 13 with binary transponder number ‘0000
0000 0000 0100 0000 0000 0000 0000 0000 0011 0001 0001 1011 0100 1011 0000’ results in the following
hexadecimal unique identifier: 03 0D 0004 0000 0311 B4B0.
4.4 Unique identification of collection containers
4.4.1 General
Collection containers can be uniquely identified by means of a combination of a) an identifier of the
organization issuing the container identifier and b) an identifier of the collection container itself.
4.4.2 Issuer identifier
The issuer of a container identifier is usually the supplier of the collection container systems, but this is
not necessarily the case.
Issuers of collection container identifiers are specified using the Electronic Address Scheme (EAS) code
list defined and maintained by the European Commission’s Connecting Europe Facility (CEF).
The EAS code list specifies existing identification schemes, like GS1’s global location number (GLN),
EU’s VAT scheme and national Chamber of Commerce schemes. The combination of such a scheme
identifier and an organization identifier according to that scheme provides a unique identifier for a
supplier.
10
---------------------- Page: 12 ----------------------
oSIST prEN 17367:2022
prEN 17367:2021 (E)
For example:
• A supplier has the following GLN identifier: 5790000435944
• The EAS code for the GLN scheme is 0088
• This combination provides a unique identifier for that supplier
For more information about the EAS code list and the latest version, see:
https://ec.europa.eu/cefdigital/wiki/display/CEFDIGITAL/Code+lists
4.4.3 Container identifier
This norm does not set any restriction on the identifier of the collection container. Organizations are
free to assign any alphanumeric identifier, e.g. ‘C12345’ or a UUID like ‘35d32606-9c96-42f0-bf4b-
3aa59ea1b9fb’.
11
---------------------- Page: 13 ----------------------
oSIST prEN 17367:2022
prEN 17367:2021 (E)
5 The semantic message models
5.1 Transactions message
Table 3 — Semantic data model of the core elements of collection container transactions
Level Min.max Business Term Description Data type Usage note
occurrence
1 1.1 Message identifier Number of the message. Integer Shall be an increasing number. May
restart at 1 after the maximum
number is reached, or after changing
the controller.
1 1.n Transaction The registration of a deposit of waste and fractions
in the collection container.
2 1.1 Transaction Number of the transaction, shall be an increasing Integer
number number. May restart at 1 after the maximum
number is reached, or after changing the controll
...
Questions, Comments and Discussion
Ask us and Technical Secretary will try to provide an answer. You can facilitate discussion about the standard in here.