Tanks for transport of dangerous goods - Digital interface for the data transfer between tank vehicle and with stationary facilities - Part 2: Commercial and logistic data

This European Standard specifies the data structure needed for tour management, scheduling orders of measured and unmeasured products online to the truck. Processed orders are transferred back to the host in the office at once or later every time the truck is online.
It specifies the transfer of commercial and logistic data between transport vehicle equipment, on board computer of the tank vehicle and stationary facilities for all communication channels between these parties.
This document should only be used in conjunction with EN 15969-1 and should not modify or override any of the requirements of EN 15969-1.

Tanks für die Beförderung gefährlicher Güter - Digitale Schnittstelle für den Datenaustausch zwischen Tankfahrzeugen und stationären Einrichtungen - Teil 2: Kommerzielle und logistische Daten

Dieses Dokument legt die Datenstruktur fest, die für die Tourverwaltung und die Übertragung von Aufträgen über  gemessene und ungemessene Produkte online zum Tankwagen notwendig ist. Abgefertigte Aufträge werden sofort oder später, jedes Mal, wenn der Tankwagen online ist, zum Host im Büro zurückübertragen.
Es legt den Austausch kommerzieller und logistischer Daten zwischen den elektronischen Einrichtungen, dem Bordcomputer des Tankfahrzeuges und stationären Einrichtungen für alle Kommunikationswege zwischen diesen Stellen fest.
Dieses Dokument wird in Verbindung mit EN 15969-1 angewendet und hebt weder die Anforderungen von EN 15969-1 auf noch ändert es sie.

Citernes destinées au transport de matières dangereuses - Interface numérique pour le transfert de données entre des véhicules-citernes et des installations fixes - Partie 2 : Données commerciales et logistiques

Le présent document décrit la structure de données exigée pour la gestion des tournées ainsi que la planification des commandes de produits mesurés et non mesurés connectée avec le camion. Les commandes traitées sont renvoyées vers l’hôte dans le bureau, immédiatement ou ultérieurement, chaque fois que le véhicule est connecté.
Le présent document spécifie les modes de transfert de données commerciales et logistiques entre l’équipement de véhicule de transport, l’ordinateur embarqué sur le véhicule-citerne et les installations fixes pour toutes les voies de communication entre ces parties.
Le présent document est utilisé conjointement avec l’EN 15969-1 et ne remplace ni ne modifie aucune des exigences de l’EN 15969-1.

Cisterne za prevoz nevarnega blaga - Digitalni vmesnik za prenos podatkov med cisterno in stacionarnimi napravami - 2. del: Komercialni in logistični podatki

General Information

Status
Published
Public Enquiry End Date
02-Jul-2021
Publication Date
14-Nov-2022
Technical Committee
Current Stage
6060 - National Implementation/Publication (Adopted Project)
Start Date
27-Oct-2022
Due Date
01-Jan-2023
Completion Date
15-Nov-2022

RELATIONS

Buy Standard

Standard
SIST EN 15969-2:2022
English language
46 pages
sale 10% off
Preview
sale 10% off
Preview
e-Library read for
1 day
Draft
oSIST prEN 15969-2:2021
English language
44 pages
sale 10% off
Preview
sale 10% off
Preview
e-Library read for
1 day

Standards Content (sample)

SLOVENSKI STANDARD
SIST EN 15969-2:2022
01-december-2022
Nadomešča:
SIST EN 15969-2:2018
Cisterne za prevoz nevarnega blaga - Digitalni vmesnik za prenos podatkov med
cisterno in stacionarnimi napravami - 2. del: Komercialni in logistični podatki

Tanks for transport of dangerous goods - Digital interface for the data transfer between

tank vehicle and with stationary facilities - Part 2: Commercial and logistic data

Tanks für die Beförderung gefährlicher Güter - Digitale Schnittstelle für den
Datenaustausch zwischen Tankfahrzeugen und stationären Einrichtungen - Teil 2:
Kommerzielle und logistische Daten

Citernes destinées au transport de matières dangereuses - Interface numérique pour le

transfert de données entre des véhicules-citernes et des installations fixes - Partie 2 :

Données commerciales et logistiques
Ta slovenski standard je istoveten z: EN 15969-2:2022
ICS:
13.300 Varstvo pred nevarnimi Protection against dangerous
izdelki goods
23.020.10 Nepremične posode in Stationary containers and
rezervoarji tanks
35.240.60 Uporabniške rešitve IT v IT applications in transport
prometu
SIST EN 15969-2:2022 en,fr,de

2003-01.Slovenski inštitut za standardizacijo. Razmnoževanje celote ali delov tega standarda ni dovoljeno.

---------------------- Page: 1 ----------------------
SIST EN 15969-2:2022
---------------------- Page: 2 ----------------------
SIST EN 15969-2:2022
EN 15969-2
EUROPEAN STANDARD
NORME EUROPÉENNE
November 2022
EUROPÄISCHE NORM
ICS 13.300; 23.020.10; 35.240.60 Supersedes EN 15969-2:2017
English Version
Tanks for transport of dangerous goods - Digital interface
for the data transfer between tank vehicle and with
stationary facilities - Part 2: Commercial and logistic data

Citernes destinées au transport de matières Tanks für die Beförderung gefährlicher Güter - Digitale

dangereuses - Interface numérique pour le transfert de Schnittstelle für den Datenaustausch zwischen

données entre des véhicules-citernes et des Tankfahrzeugen und stationären Einrichtungen - Teil

installations fixes - Partie 2 : Données commerciales et 2: Kommerzielle und logistische Daten

logistiques
This European Standard was approved by CEN on 5 September 2022.

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

© 2022 CEN All rights of exploitation in any form and by any means reserved Ref. No. EN 15969-2:2022 E

worldwide for CEN national Members.
---------------------- Page: 3 ----------------------
SIST EN 15969-2:2022
EN 15969-2:2022 (E)
Contents Page

European foreword ....................................................................................................................................................... 3

Introduction .................................................................................................................................................................... 5

1 Scope .................................................................................................................................................................... 7

2 Normative references .................................................................................................................................... 7

3 Terms and definitions ................................................................................................................................... 7

4 Files ...................................................................................................................................................................... 8

4.1 Format identifiers ........................................................................................................................................... 8

4.2 Relations ............................................................................................................................................................. 9

4.3 File naming conventions ............................................................................................................................ 10

5 Fields of special types ................................................................................................................................. 11

5.1 Text module reference ............................................................................................................................... 11

5.2 Geo-Coordinates ........................................................................................................................................... 11

5.3 UTF-8 strings .................................................................................................................................................. 11

6 Price calculation rules ................................................................................................................................ 12

6.1 General ............................................................................................................................................................. 12

6.2 Low volume (surcharge) ............................................................................................................................ 12

6.3 Pricing of packed products, container, pieces ................................................................................... 12

6.3.1 Article records ............................................................................................................................................... 12

6.3.2 Low volume (surcharge) ............................................................................................................................ 12

6.3.3 Price calculation methods ......................................................................................................................... 12

6.4 Taxes ................................................................................................................................................................. 13

7 Description of tour management ........................................................................................................... 13

7.1 Handling of several tours .......................................................................................................................... 13

7.2 Handling of a pseudo-tour with a pool of orders .............................................................................. 13

7.3 Handling of orders ....................................................................................................................................... 14

7.4 Handling of products .................................................................................................................................. 14

8 Fields and records of RC_File ................................................................................................................... 14

9 Multi-Order Data (Subnode RC_FILE) ................................................................................................... 40

9.1 General ............................................................................................................................................................. 40

9.2 Node RC_File ................................................................................................................................................... 40

9.3 Information concerning application ..................................................................................................... 41

9.3.1 Simple tour plan, using FTL connection ............................................................................................... 41

9.3.2 Simple Tour Plan, Using FTP and RC_FILE ........................................................................................... 43

9.3.3 Managing static data, using FTL connection ....................................................................................... 45

9.3.4 Managing static data under FTP ............................................................................................................. 45

---------------------- Page: 4 ----------------------
SIST EN 15969-2:2022
EN 15969-2:2022 (E)
European foreword

This document (EN 15969-2:2022) has been prepared by Technical Committee CEN/TC 296 “Tanks for

the transport of dangerous goods”, the secretariat of which is held by AFNOR.

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 May 2023, and conflicting national standards shall be

withdrawn at the latest by May 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.

This document supersedes EN 15969-2:2017.
With regard to EN 15969-2:2017 the following fundamental changes are given:
— fields for air craft refilling added;
— Index C09 “process identification” included;
— Index O32 “process identification” amended;
— Index P42 “delivery path” included.

The EN 15969 series, Tanks for transport of dangerous goods - Digital interface for the data transfer

between tank vehicle and with stationary facilities, consists of the following 2 parts:

— Part 1: Protocol specification - Control, measurement and event data;
— Part 2: Commercial and logistic data.

This document forms part of a coherent standards programme comprising the following standards:

— EN 13616-1, Overfill prevention devices for static tanks for liquid fuels - Part 1: Overfill prevention

devices with closure device;

— EN 13616-2, Overfill prevention devices for static tanks for liquid fuels - Part 2: Overfill prevention

devices without a closure device;

— EN 13922, Tanks for transport of dangerous goods - Service equipment for tanks - Overfill prevention

systems for liquid fuels;

— EN 14116, Tanks for transport of dangerous goods - Digital interface for product recognition devices

for liquid fuels;

— EN 15207, Tanks for the transport of dangerous goods - Plug/socket connection and supply

characteristics for service equipment in hazardous areas with 24 V nominal supply voltage;

— EN 15208, Tanks for transport of dangerous goods - Sealed parcel delivery systems - Working principles

and interface specifications;

— EN 15969-1, Tanks for transport of dangerous goods - Digital interface for the data transfer between

tank vehicle and with stationary facilities - Part 1: Protocol specification - Control, measurement and

event data.
---------------------- Page: 5 ----------------------
SIST EN 15969-2:2022
EN 15969-2:2022 (E)

Any feedback and questions on this document should be directed to the users’ national standards body.

A complete listing of these bodies can be found on the CEN website.

According to the CEN-CENELEC Internal Regulations, the national standards organisations of the

following countries are bound to 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.
---------------------- Page: 6 ----------------------
SIST EN 15969-2:2022
EN 15969-2:2022 (E)
Introduction

FTL is an acronym for Fuel Truck Link, the interface between electronic system(s) on board of a tank

truck (Tank-Vehicle-Equipment) and any external computer, Part 2 mainly for a host installed in the

office and connected via Internet (TCP/IP); for illustration, see Figure 1.

This document specifies data format for all interconnecting communication paths for commercial issues.

This document offers the user following features:
— multiple orders (batch processing);
— pricing;
— master data (e.g. products, customers, drivers, taxes);
— additional texts for the printout;
— information for the drivers;
— tour management;
— data for invoicing with surcharge;
— data for delivery packaged goods;
— handle planned and unplanned deliveries.
---------------------- Page: 7 ----------------------
SIST EN 15969-2:2022
EN 15969-2:2022 (E)
Key
→ direction of communication (client → server)

a may be either two independent units or one single unit which incorporates both functions OBC and TVE

Figure 1 — Communication structure
---------------------- Page: 8 ----------------------
SIST EN 15969-2:2022
EN 15969-2:2022 (E)
1 Scope

This document specifies the data structure needed for tour management, scheduling orders of measured

and unmeasured products online to the truck. Processed orders are transferred back to the host in the

office at once or later every time the truck is online.

It specifies the transfer of commercial and logistic data between transport vehicle equipment, on board

computer of the tank vehicle and stationary facilities for all communication channels between these

parties.

This document is used in conjunction with EN 15969-1 and does not modify or override any of the

requirements of EN 15969-1.
2 Normative references

The following documents are referred to in the text in such a way that some or all of their content

constitutes requirements of this document. For dated references, only the edition cited applies. For

undated references, the latest edition of the referenced document (including any amendments) applies.

EN 14116, Tanks for transport of dangerous goods - Digital interface for product recognition devices for

liquid fuels

EN 15969-1:2022 , Tanks for transport of dangerous goods - Digital interface for the data transfer between

tank vehicle and with stationary facilities - Part 1: Protocol specification - Control, measurement and event

data

EN ISO 3166-1, Codes for the representation of names of countries and their subdivisions - Part 1: Country

code (ISO 3166-1)

ISO 639-1, Codes for the representation of names of languages — Part 1: Alpha-2 code

ISO 4217, Codes for the representation of currencies
ISO/IEC 10646:2020, Information technology — Universal coded character set (UCS)
3 Terms and definitions

For the purposes of this document, the terms and definitions given in EN 15969-1:2022 and the

following apply.

ISO and IEC maintain terminological 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
dispatcher
person who planes tour at the host system
Under preparation. Stage at the time of publication: FprEN 15969-1:2022.
---------------------- Page: 9 ----------------------
SIST EN 15969-2:2022
EN 15969-2:2022 (E)
3.2
operator
driver
person who operates the truck and the truck management computer
3.3
tour

set of at least one 'Order Record' and related records, which describes a collection of stops at different

customers and the ordered products, so that the driver knows where to go and what to deliver

3.4
article
goods and/or services provided
4 Files
4.1 Format identifiers
Format identifiers are specified in EN 15969-1.

If the tank vehicle accepts LC-files (see Table 1) for backwards compatibility it shall also treat L-files from

the office as LC-files. Record identifier and file type according to Table 1.

NOTE The change from L-files to LC-files in this edition of this document was required because EN 15969-1

and EN 15969-2 used the same name (L) for different types of files.
Table 1 — Record identifier and file type
Record Short Description of file contents and Primary Key Deletion
identifier description possible destinations of the file Identifier
List of all goods and/or services a_art_id a_deleted
A Article
provided
C Customer Customer database c_cus_id c_deleted
Record type used to mark batch — —
FB FTLbatch commands inside RC_file; see
Table 11
A tour consists of a list of tour stops, h_tour_no h_deleted
which could be stops at customers
H Tour
(typ. unloading) or depots (typ.
loading)
LC Location All locations (depots, customers, etc.) lc_loc_id lc_deleted
Restrictions for a location (time lr_loc_id lr_deleted
Location
LR windows, vehicle accessibility,
restriction
permitted actions)
Notes that can be specified for any n_ref_obj n_deleted
object
N Notes n_obj_id
n_seq_no
Represents a stop in a tour. This o_tour_no o_deleted
O Order
could be both a loadstop and an
o_ord_no
orderstop. Per stop, several actions
---------------------- Page: 10 ----------------------
SIST EN 15969-2:2022
EN 15969-2:2022 (E)
Record Short Description of file contents and Primary Key Deletion
identifier description possible destinations of the file Identifier
can be performed. These are specified
in the p-records of this o-record.
If field o_ord_id is 0, the order is
unplanned
Extension to O-File for aviation oa_tour_no oa_deleted
Order Aviation
specific delivery and scheduling data
Extension
oa_ord_no
Order Aviation Extension to OA-File for aviation of_tour_no of_deleted
OF Extension for specific frequently changed order and
of_ord_no
real time data scheduling information data
Order Order restrictions, used for or_ord_id or_deleted
restrictions scheduling and routing
Specifies the goods and services to be p_tour_no p_deleted
delivered at this stop (o-record)
P Order lines p_ord_no
p_pos_no
R Driver List of all drivers r_drv_id r_deleted
Static texts for any object. Provides s_ref_obj s_deleted
Text-module text module references, to add a
s_obj_id
reference variable number of static texts to an
s_seq_no
object for printout
Different applicable VAT rates, used t_tax_id t_deleted
T Tax
for invoice calculation
Texts which are repetitively used may x_blk_id x_deleted
be stored in this database and
x_lang_id
X Text modules
referred to by a three-digit numeric
code in the S-record
Optional annotations to any other y_ann_obj y_deleted
type, these annotations are used to
y_obj_id
add manufacturer specific fields to
y_ann_key
Y Annotations any record, which trigger an action on
the truck and are not only used for
printout. It is not allowed to define
fields of type y within this standard
FTL batch - Commands of Fuel Truck Link according to EN 15969-1.
4.2 Relations

Figure 2 shows the relations between the different record types and contains only the fields relevant for

these relations.
---------------------- Page: 11 ----------------------
SIST EN 15969-2:2022
EN 15969-2:2022 (E)
Key
PK primary key
FK foreign key
R reference
one-to-one relationship, both objects shall exist
one-to-one relationship, the object on the right side is optional (zero or one)
one-to-many relationship, both objects shall exist

one-to-many relationship, the object on the right side is optional (zero, one or many)

Figure 2 — Work data and master data
4.3 File naming conventions

When files are being transferred using FTP connection, the file(s) shall be named

RC_CCYYMMDDhhmmss.FTL. CCYYMMDDhhmmss is the timestamp according to EN 15969-1:2022 ,

Table 3.

If more than one file is transferred, they shall be processed in ascending order of file names.

---------------------- Page: 12 ----------------------
SIST EN 15969-2:2022
EN 15969-2:2022 (E)
5 Fields of special types
5.1 Text module reference
Table 2 — Text module reference
Type Size Explanation
R N4.1 Text module reference

Text module fields according to Table 2 have the special functionality described below.

The text module selection will be done by a key number. Each record of type X can be used as a single line

or as a set of lines. To differentiate between single line and set, the pointer has a special structure.

The text module reference s_txt_id is defined as a numeric value with the size: 4.1.

The leading 4 digit number is the key-field of the record of type X (field x_txt_id). The 1 digit number

behind the decimal point counts the number of records following the first record, i.e. this number is used

to increment the pointer.
EXAMPLE
Value Explanation
99.0 Only record no. 99 is printed.
99.2 Record no. 99, 100, 101 are printed.
5.2 Geo-Coordinates
Geo-coordinate fields shall be according to Table 3.
Table 3 — Geo-coordinate field
Type Size Explanation

G N4.6 Longitude and latitude values shall be in degrees and decimal fractions of degree:

— negative value of longitude is west of Greenwich; positive value is east of
Greenwich;

— positive value of latitude is north of equator; negative value is south of equator.

Examples for longitude GPS:
+007.512500 = 7,512500° E = 7° 30′ 45” E = 7° 0,750’ E
7. 5125 = 7,512500° E = 7° 30′ 45” E
−007. 512500 = 7,512500° W = 7° 30′ 45” W
Examples for latitude GPS:
+07.512500 = 7,512500° N = 7° 30′ 45” N
5.3 UTF-8 strings
UTF-8 strings according to Table 4.
Table 4 — UTF-8 string field
Type Explanation

Ux Text with maximum length of x printable characters coded in UTF-8 according to

ISO/IEC 10646:2020. At most, x-times four bytes are required for storage.
---------------------- Page: 13 ----------------------
SIST EN 15969-2:2022
EN 15969-2:2022 (E)
6 Price calculation rules
6.1 General
All prices shall be net prices.

For the definitions of all mentioned fields (e.g p_del_qty, p_unit_price and a_prc_fac) in Clause 6 see

Table 5.
6.2 Low volume (surcharge)

In the event of the actual delivered volume being less than the planned delivered volume, negative price

discounts (surcharges) may be applied.

These fields are used to calculate the applicable surcharges. Two surcharge levels may be used, depending

on the difference between the actual delivered volume and the planned delivered volume. For example,

if this difference is between “p_low_vol1” and “p_low_vol2” then surcharge “p_sur_vol1” shall be used, and

if between “p_low_vol2” and “p_low_vol3” then surcharge “p_sur_vol2” shall be used.

In any of these cases the driver has the possibility to change from invoice to delivery note.

Where the actual delivered volume is so small that it is less than “p_low_vol3”, (the limit of prior agreed

surcharges) then no price calculation shall be made and only a delivery ticket issued.

Formula:
Price = p_del_qty ∙ p_unit_price / a_prc_fac
Surcharge = p_del_qty ∙ p_sur_voln / a_prc_fac
6.3 Pricing of packed products, container, pieces
6.3.1 Article records

Packed goods can also be delivered, packed goods have a_met_prod = 0, a_met_prod is the reference to

the metered product on the truck.
6.3.2 Low volume (surcharge)

For this type of product there are also quantity limits available. The conditions are the same as for liquid

products.
6.3.3 Price calculation methods
— by piece ('a_prc_code' = 0)

If a_pck_cnt = 0 the driver inputs the number of pieces, which is stored in p_del_qty. If a_pck_cnt > 0,

the driver inputs the number of packings, the quantity is calculated by a multiplication of the number

of packings and a_pck_cnt is stored in the data field p_del_qty. The price will be the unit price

p_unit_prc. The a_prc_fac shall be taken into consideration. The text for unit of measure is given in

a_unit_txt, e.g. can.
Price-Formula:
price = p_del_qty ∙ p_unit_prc / a_prc_fac
---------------------- Page: 14 ----------------------
SIST EN 15969-2:2022
EN 15969-2:2022 (E)
— by quantity ('a_prc_code' = 1)

If a_case_cnt > 0, a special calculation shall be made to get the delivered quantity 'p_del_qty'. The text

for unit of measure is given in 'p_unit_msr'. If a_case_cnt = 0, the driver inputs the quantity directly.

Formula:
p_del_qty = number of packings ∙ a_pck_cnt
price = p_del_qty ∙ p_unit_prc / a_prc_fac
— by fixed price ('a_prc_code' = 2)

A price calculation is not needed because this price is negotiated. No quantity input is necessary, the

delivered quantity is the preset quantity, text for unit of measure is given in 'p_unit_msr'.

Formula:
price = p_unit_prc
6.4 Taxes

Taxes are defined in the 'Tax Records' and will be referenced by the ordered products and thereby

ordered article (a_tax_id). If tax id is zero, this product is tax free.

The tax records contain an expiration date that defines the start of a new tax value that is also defined in

this record.
Formula:
tax = (price ∙ t_tax_val1) / 100
If expiration date is reached:
tax = (price ∙ t_tax_val2) / 100
7 Description of tour management
7.1 Handling of several tours

Any number of orders of record type O, combined in tours of record type H, can be transferred to the

truck. Each order record may be followed by 0 to n product records of type P.

The operator selects one of the pre-planned tours at the truck. This tour record is duplicated into the

return data, filled with the actual data and saved. The internal tour number h_tour_no in the return data

starts at 1 and is incremented by 1 at every tour. The internal tour number in the return data are not

related with the internal tour number in the planned data. In the office, the correlation of the planned

data to the return data are shown in field h_tour_id. If field h_tour_id is empty, it is an unplanned tour. If

a planned tour is selected repetitively, field h_tour_id in the return data contains the original information.

The field h_tour_id is unique in the planned data, but it may not be unique in the return data.

7.2 Handling of a pseudo-tour with a pool of orders

It is also possible to work with only one (pseudo-) tour with a pool of orders. The office deletes executed

orders and adds new orders or modifies existing orders of this pool, but always within this tour. This tour

is a pseudo-tour and always contains the orders for the next few hours. There is no need to select a tour

---------------------- Page: 15 ----------------------
SIST EN 15969-2:2022
EN 15969-2:2022 (E)

at the truck. This option is configurable at the truck. Within the return data, the tour data contains the

completed orders in chronological sequence, e.g. by day, or by shift, after a driver change.

7.3 Handling of orders

Within a tour, 0 to n orders exist. The operator chooses one of the given orders at the truck, this order

record is duplicated into the return data and will be filled with the actual processed data and saved. The

internal order number o_ord_no within the tour is created in the return data, starts at 1 and is

incremented by 1 at every order. The internal order number in the return data are not related to the

internal order number in the planned data. In the office, the correlation of the planned data to the return

data are shown in the field o_ord_id. If field o_ord_id is empty, it is an unplanned order, which shall be

processed manually. If a planned order is selected a second time, e.g. because the first processing was not

completed, field o_ord_id in the return data contains the original information. The field o_ord_id is unique

in the planned data and may not be unique in the return data. If the field o_ord_id is empty, this order

shall be handled manually in the office.
7.4 Handling of products

Within an order, 0 to 99 product records may exist. The operator chooses one of the given product

records at the truck. This record is duplicated into the return data, filled with the actual data of the

transaction (loading or delivery), and saved. The internal number p_pos_no within the order is created in

the return data, starts at 1 and is incremented by 1 for every product record. The internal number in the

return data are not related with the internal number in the planning data. In the office, the correlation of

the planned data to the return data are shown in field p_pos_id. If field p_pos_id is empty, it is an

unplanned product record. If a planned product record is chosen a second time, e.g. because the first time

failed, field p_pos_id in the return data contains the original information. The field p_pos_id is unique in

the planned data and may not be unique in the return data. If an order contains unplanned product

records or product records which are handled twice, shall be processed in the office.

8 Fields and records of RC_File
A record container (RC) file may contain records of one or more different types.
Fields and records of RC_File according to Table 5.
---------------------- Page: 16 ----------------------
SIST EN 15969-2:2022
EN 15969-2:2022 (E)
...

SLOVENSKI STANDARD
oSIST prEN 15969-2:2021
01-junij-2021
Cisterne za prevoz nevarnega blaga - Digitalni vmesnik za prenos podatkov med
cisterno in stacionarnimi napravami - 2. del: Komercialni in logistični podatki

Tanks for transport of dangerous goods - Digital interface for the data transfer between

tank vehicle and with stationary facilities - Part 2: Commercial and logistic data

Tanks für die Beförderung gefährlicher Güter - Digitale Schnittstelle für den
Datenaustausch zwischen Tankfahrzeugen und stationären Einrichtungen - Teil 2:
Kommerzielle und logistische Daten

Citernes destinées au transport de matières dangereuses - Interface numérique pour le

transfert de données entre des véhicules-citernes et des installations fixes - Partie 2:

Données commerciales et logistiques
Ta slovenski standard je istoveten z: prEN 15969-2
ICS:
13.300 Varstvo pred nevarnimi Protection against dangerous
izdelki goods
23.020.10 Nepremične posode in Stationary containers and
rezervoarji tanks
35.240.60 Uporabniške rešitve IT v IT applications in transport
prometu
oSIST prEN 15969-2:2021 en,fr,de

2003-01.Slovenski inštitut za standardizacijo. Razmnoževanje celote ali delov tega standarda ni dovoljeno.

---------------------- Page: 1 ----------------------
oSIST prEN 15969-2:2021
---------------------- Page: 2 ----------------------
oSIST prEN 15969-2:2021
DRAFT
EUROPEAN STANDARD
prEN 15969-2
NORME EUROPÉENNE
EUROPÄISCHE NORM
June 2021
ICS 13.300; 23.020.10; 35.240.60 Will supersede EN 15969-2:2017
English Version
Tanks for transport of dangerous goods - Digital interface
for the data transfer between tank vehicle and with
stationary facilities - Part 2: Commercial and logistic data

Citernes destinées au transport de matières Tanks für die Beförderung gefährlicher Güter - Digitale

dangereuses - Interface numérique pour le transfert de Schnittstelle für den Datenaustausch zwischen

données entre des véhicules-citernes et des Tankfahrzeugen und stationären Einrichtungen - Teil

installations fixes - Partie 2: Données commerciales et 2: Kommerzielle und logistische Daten

logistiques

This draft European Standard is submitted to CEN members for enquiry. It has been drawn up by the Technical Committee

CEN/TC 296.

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 15969-2:2021 E

worldwide for CEN national Members.
---------------------- Page: 3 ----------------------
oSIST prEN 15969-2:2021
prEN 15969-2:2021 (E)
Contents Page

European foreword ....................................................................................................................................................... 3

Introduction .................................................................................................................................................................... 4

1 Scope .................................................................................................................................................................... 6

2 Normative references .................................................................................................................................... 6

3 Terms and definitions ................................................................................................................................... 6

4 Files ...................................................................................................................................................................... 7

4.1 Format identifiers ........................................................................................................................................... 7

4.2 Relations ............................................................................................................................................................. 8

4.3 File naming conventions ............................................................................................................................... 9

5 Fields of special types ................................................................................................................................. 10

5.1 Text module reference ............................................................................................................................... 10

5.2 Geo-Coordinates ........................................................................................................................................... 10

5.3 UTF-8 strings .................................................................................................................................................. 10

6 Price calculation rules ................................................................................................................................ 11

6.1 General ............................................................................................................................................................. 11

6.2 Low volume (surcharge) ............................................................................................................................ 11

6.3 Pricing of packed products, container, pieces ................................................................................... 11

6.4 Taxes ................................................................................................................................................................. 12

7 Description of tour management ........................................................................................................... 12

7.1 Handling of several tours .......................................................................................................................... 12

7.2 Handling of a pseudo-tour with a pool of orders .............................................................................. 12

7.3 Handling of orders ....................................................................................................................................... 13

7.4 Handling of products .................................................................................................................................. 13

8 Fields and records of RC_File ................................................................................................................... 13

9 Multi-Order Data (Subnode RC_FILE) ................................................................................................... 39

9.1 General ............................................................................................................................................................. 39

9.2 Node RC_File ................................................................................................................................................... 39

9.3 Information concerning application ..................................................................................................... 40

---------------------- Page: 4 ----------------------
oSIST prEN 15969-2:2021
prEN 15969-2:2021 (E)
European foreword

This document (prEN 15969-2:2021) has been prepared by Technical Committee CEN/TC 296 “Tanks

for the transport of dangerous goods”, the secretariat of which is held by AFNOR.

This document is currently submitted to the CEN Enquiry.
This document supersedes EN 15969-2:2017.
With regard to EN 15969-2:2017 the following fundamental changes are given:
— fields for air craft refilling added.
— Index C09 “process identification” included;
— Index O32 “process identification” amended;
— Index P42 “delivery path” included.

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.

EN 15969, Tanks for transport of dangerous goods — Digital interface for the data transfer between tank

vehicle and with stationary facilities, consists of 2 parts:
— Part 1: Protocol specification — Control, measurement and event data;
— Part 2: Commercial and logistic data.

This European Standard forms part of a coherent standards programme comprising the following

standards:

— EN 13616-1, Overfill prevention devices for static tanks for liquid fuels — Part 1: Overfill prevention

devices with closure device;

— EN 13616-2, Overfill prevention devices for static tanks for liquid fuels — Part 2: Overfill prevention

devices without a closure device;

— EN 13922, Tanks for transport of dangerous goods — Service equipment for tanks — Overfill

prevention systems for liquid fuels;

— EN 14116, Tanks for transport of dangerous goods — Digital interface for product recognition devices

for liquid fuels;

— EN 15207, Tanks for the transport of dangerous goods — Plug/socket connection and supply

characteristics for service equipment in hazardous areas with 24 V nominal supply voltage;

— EN 15208, Tanks for transport of dangerous goods — Sealed parcel delivery systems — Working

principles and interface specifications;

— EN 15969-1, Tanks for transport of dangerous goods — Digital interface for the data transfer

between tank vehicle and with stationary facilities — Part 1: Protocol specification - Control,

measurement and event data.
---------------------- Page: 5 ----------------------
oSIST prEN 15969-2:2021
prEN 15969-2:2021 (E)
Introduction

FTL is an acronym for Fuel Truck Link, the interface between electronic system(s) on board of a tank

truck (Tank-Vehicle-Equipment) and any external computer, Part 2 mainly for a host installed in the

office and connected via Internet (TCP/IP); for illustration, see Figure 1.

This document specifies data format for all interconnecting communication paths for commercial

issues.
This document offers the user following features:
— multiple orders (batch processing);
— pricing;
— master data (e.g. products, customers, drivers, taxes);
— additional texts for the printout;
— information for the drivers;
— tour management;
— data for invoicing with surcharge;
— data for delivery packaged goods;
— handle planned and unplanned deliveries.
---------------------- Page: 6 ----------------------
oSIST prEN 15969-2:2021
prEN 15969-2:2021 (E)
Key
→ direction of communication (client → server)

a may be either two independent units or one single unit which incorporates both functions OBC and TVE

Figure 1 — Communication structure
---------------------- Page: 7 ----------------------
oSIST prEN 15969-2:2021
prEN 15969-2:2021 (E)
1 Scope

This document specifies the data structure needed for tour management, scheduling orders of

measured and unmeasured products online to the truck. Processed orders are transferred back to the

host in the office at once or later every time the truck is online.

It specifies the transfer of commercial and logistic data between transport vehicle equipment, on board

computer of the tank vehicle and stationary facilities for all communication channels between these

parties.

This document is used in conjunction with EN 15969-1 and does not modify or override any of the

requirements of EN 15969-1.
2 Normative references

The following documents are referred to in the text in such a way that some or all of their content

constitutes requirements of this document. For dated references, only the edition cited applies. For

undated references, the latest edition of the referenced document (including any amendments) applies.

EN 14116, Tanks for transport of dangerous goods — Digital interface for product recognition devices for

liquid fuels

prEN 15969-1:2021, Tanks for transport of dangerous goods — Digital interface for the data transfer

between tank vehicle and with stationary facilities — Part 1: Protocol specification — Control,

measurement and event data

EN ISO 3166-1, Codes for the representation of names of countries and their subdivisions - Part 1: Country

code (ISO 3166-1)

ISO 639-1, Codes for the representation of names of languages — Part 1: Alpha-2 code

ISO 4217, Codes for the representation of currencies
ISO/IEC 10646:2020, Information technology — Universal coded character set (UCS)
3 Terms and definitions

For the purposes of this document, the terms and definitions given in prEN 15969-1:2021 and the

following apply.

ISO and IEC maintain terminological 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
dispatcher
person who planes tour at the host system
3.2
operator
driver
person who operates the truck and the truck management computer
---------------------- Page: 8 ----------------------
oSIST prEN 15969-2:2021
prEN 15969-2:2021 (E)
3.3
tour

set of at least one 'Order Record' and related records, which describes a collection of stops at different

customers and the ordered products, so that the driver knows where to go and what to deliver

3.4
article
goods and/or services provided
4 Files
4.1 Format identifiers
According to EN 15969-1.

If the tank vehicle accepts LC-files for backwards compatibility it shall also treat L-files from the office

as LC-files. Record identifier and file type according to Table 1.

NOTE The change from L-files to LC-files in this edition of this standard was required because EN 15969-1

and EN 15969-2 used the same name (L) for different types of files.
Table 1 — Record identifier and file type
Record Short Description of file contents and Primary Key Deletion
identifier description possible destinations of the file Identifier
List of all goods and/or services a_art_id a_deleted
A Article
provided
C Customer Customer database c_cus_id c_deleted
Record type used to mark batch — —
FB FTL batch commands inside RC_file; see
Table 11.
A tour consists of a list of tour stops, h_tour_no h_deleted
which could be stops at customers
H Tour
(typ. unloading) or depots (typ.
loading).
LC Location All locations (depots, customers, etc) lc_loc_id lc_deleted
Restrictions for a location (time lr_loc_id lr_deleted
Location
LR windows, vehicle accessibility,
restriction
permitted actions)
Notes that can be specified for any n_ref_obj n_deleted
object.
N Notes n_obj_id
n_seq_no
Represents a stop in a tour. This o_tour_no o_deleted
could be both a loadstop and an
o_ord_no
orderstop. per stop, several actions
can be performed. These are specified
O Order
in the p-records of this o-record.
If field o_ord_id is 0, the order is
unplanned
---------------------- Page: 9 ----------------------
oSIST prEN 15969-2:2021
prEN 15969-2:2021 (E)
Record Short Description of file contents and Primary Key Deletion
identifier description possible destinations of the file Identifier
Extension to O-File for aviation oa_tour_no oa_deleted
Order Aviation
specific delivery and scheduling data
Extension
oa_ord_no
Order Aviation Extension to OA-File for aviation of_tour_no of_deleted
OF Extension for specific frequently changed order and
of_ord_no
real time data scheduling information data
Order Order restrictions, used for or_ord_id or_deleted
restrictions scheduling and routing.
Specifies the goods and services to be p_tour_no p_deleted
delivered at this stop (o-record).
P Order lines p_ord_no
p_pos_no
R Driver List of all drivers r_drv_id r_deleted
Static texts for any object. Provides s_ref_obj s_deleted
Text-module text module references, to add a
s_obj_id
reference variable number of static texts to an
s_seq_no
object for printout.
Different applicable VAT rates, used t_tax_id t_deleted
T Tax
for invoice calculation.
Texts which are repetitively used may x_blk_id x_deleted
be stored in this database and
x_lang_id
X Text modules
referred to by a three-digit numeric
code in the S-record.
Optional annotations to any other y_ann_obj y_deleted
type, these annotations are used to
y_obj_id
add manufacturer specific fields to
y_ann_key
Y Annotations any record, which trigger an action on
the truck and are not only used for
printout. It is not allowed to define
fields of type y within this standard.
4.2 Relations

Figure 2 shows the relations between the different record types and contains only the fields relevant for

these relations.
---------------------- Page: 10 ----------------------
oSIST prEN 15969-2:2021
prEN 15969-2:2021 (E)
Key
PK Primary key
FK Foreign key
R Reference
One-to-one relationship, both objects shall exist
One-to-one relationship, the object on the right side is optional (zero or
one)
One-to-many relationship, both objects shall exist
One-to-many relationship, the object on the right side is optional (zero,
one or many)
Figure 2 — Work data and master data
4.3 File naming conventions

When files are being transferred using FTP connection, the file(s) shall be named

RC_CCYYMMDDhhmmss.FTL. CCYYMMDDhhmmss is the timestamp according to prEN 15969-1:2021,

Table 3.

If more than one file is transferred, they shall be processed in ascending order of file names.

---------------------- Page: 11 ----------------------
oSIST prEN 15969-2:2021
prEN 15969-2:2021 (E)
5 Fields of special types
5.1 Text module reference
Table 2 — Text module reference
Type Size Explanation
R N4.1 Text module reference

Text module fields according to Table 2 have the special functionality described below.

The text module selection will be done by a key number. Each record of type X can be used as a single

line or as a set of lines. To differentiate between single line and set, the pointer has a special structure.

The text module reference s_txt_id is defined as a numeric value with the size: 4.1.

The text module reference s_txt_id, is defined as a numeric value with the size: 4.1. The leading 4 digit

number is the key-field of the record of type X (field x_txt_id). The 1 digit number behind the decimal

point counts the number of records following the first record, i.e. this number is used to increment the

pointer.
EXAMPLE
Value Explanation
99.0 Only record no. 99 is printed.
99.2 Record no. 99, 100, 101 are printed.
5.2 Geo-Coordinates
Geo-coordinate fields shall be according to Table 3.
Table 3 — Geo-coordinate field
Type Size Explanation

G N4.6 Longitude and latitude values shall be in degrees and decimal fractions of degree:

— negative value of longitude is west of Greenwich; positive value is east of
Greenwich;

— positive value of latitude is north of equator; negative value is south of equator.

Examples for longitude GPS:
+007.512500 = 7,512500° E = 7° 30′ 45” E = 7° 0,750’ E
7. 5125 = 7,512500° E = 7° 30′ 45” E
−007. 512500 = 7,512500° W = 7° 30′ 45“ W
Examples for latitude GPS:
+07.512500 = 7,512500° N = 7° 30′ 45” N
5.3 UTF-8 strings
UTF-8 strings according to Table 4.
Table 4 — UTF-8 string field
Type Explanation

Ux Text with maximum length of x printable characters coded in UTF-8 according to

ISO/IEC 10646:2020. At most, x-times four bytes are required for storage.
---------------------- Page: 12 ----------------------
oSIST prEN 15969-2:2021
prEN 15969-2:2021 (E)
6 Price calculation rules
6.1 General
All prices shall be net prices.
6.2 Low volume (surcharge)

In the event of the actual delivered volume being less than the planned delivered volume, negative price

discounts (surcharges) may be applied.

These fields are used to calculate the applicable surcharges. Two surcharge levels are allowed,

depending on the difference between the actual delivered volume and the planned delivered volume.

For example, if this difference is between “p_low_vol1” and “p_low_vol2” then surcharge “p_sur_vol1”

shall be used, and if between “p_low_vol2” and “p_low_vol3” then surcharge “p_sur_vol2” shall be used.

In any of these cases the driver has the possibility to change from invoice to delivery note.

Where the actual delivered volume is so small that it is less than “p_low_vol3”, (the limit of prior agreed

surcharges) then no price calculation shall be made and only a delivery ticket issued.

Formula:
Price = p_del_qty ∙ p_unit_price / a_prc_fac
Surcharge = p_del_qty ∙ p_sur_voln / a_prc_fac
6.3 Pricing of packed products, container, pieces
6.3.1 Article records

Packed goods can also be delivered, packed goods have no a_met_prod, a_met_prod is the reference to

the metered product on the truck.
6.3.2 Low volume (surcharge)

For this type of product there are also quantity limits available. The conditions are the same as for

liquid products.
6.3.3 Price calculation methods
— by piece ('a_prc_code' = 0)

If a_pck_cnt = 0 the driver inputs the number of pieces, which is stored in p_del_qty. If a_pck_cnt > 0,

the driver inputs the number of packings, the quantity is calculated by a multiplication of the

number of packings and a_pck_cnt is stored in the data field p_del_qty. The price will be the unit

price p_unit_prc. The a_prc_fac shall be taken into consideration. The text for unit of measure is

given in a_unit_txt, e.g. can.
Price-Formula:
price = p_del_qty ∙ p_unit_prc / a_prc_fac
— by quantity ('a_prc_code' = 1)

If a_case_cnt > 0, a special calculation shall be made to get the delivered quantity 'p_del_qty'. The

text for unit of measure is given in 'p_unit_msr'. If a_case_cnt = 0, the driver inputs the quantity

directly.
---------------------- Page: 13 ----------------------
oSIST prEN 15969-2:2021
prEN 15969-2:2021 (E)
Formula:
p_del_qty = number of packings ∙ a_pck_cnt
price = p_del_qty ∙ p_unit_prc / a_prc_fac
— by fixed price ('a_prc_code' = 2)

A price calculation is not needed because this price is negotiated. No quantity input is necessary,

the delivered quantity is the preset quantity, text for unit of measure is given in 'p_unit_msr'.

Formula:
price = p_unit_prc
6.4 Taxes

Taxes are defined in the 'Tax Records' and will be referenced by the ordered products and thereby

ordered article (a_tax_id). If tax id is zero, this product is tax free.

The tax records contain an expiration date that defines the start of a new tax value that is also defined in

this record.
Formula:
tax = (price ∙ t_tax_val1) / 100
If expiration date is reached:
tax = (price ∙ t_tax_val2) / 100
7 Description of tour management
7.1 Handling of several tours

Any number of orders of record type O, combined in tours of record type H, can be transferred to the

truck. Each order record may be followed by 0 to n product records of type P.

The operator selects one of the pre-planned tours at the truck. This tour record is duplicated into the

return data, filled with the actual data and saved. The internal tour number h_tour_no in the return data

starts at 1 and is incremented by 1 at every tour. The internal tour number in the return data are not

related with the internal tour number in the planned data. In the office, the correlation of the planned

data to the return data are shown in field h_tour_id. If field h_tour_id is empty, it is an unplanned tour. If

a planned tour is selected repetitively, field h_tour_id in the return data contains the original

information. The field h_tour_id is unique in the planned data, but it may not be unique in the return

data.
7.2 Handling of a pseudo-tour with a pool of orders

It is also possible to work with only one (pseudo-) tour with a pool of orders. The office deletes

executed orders and adds new orders or modifies existing orders of this pool, but always within this

tour. This tour is a pseudo-tour and always contains the orders for the next few hours. There is no need

to select a tour at the truck. This option is configurable at the truck. Within the return data, the tour

data contains the completed orders in chronological sequence, e.g. by day, or by shift, after a driver

change.
---------------------- Page: 14 ----------------------
oSIST prEN 15969-2:2021
prEN 15969-2:2021 (E)
7.3 Handling of orders

Within a tour 0 to n orders exist. The operator chooses one of the given orders at the truck, this order

record is duplicated into the return data and will be filled with the actual processed data and saved. The

internal order number o_ord_no within the tour is created in the return data, starts at 1 and is

incremented by 1 at every order. The internal order number in the return data are not related to the

internal order number in the planned data. In the office, the correlation of the planned data to the

return data are shown in the field o_ord_id. If field o_ord_id is empty, it is an unplanned order, which

shall be processed manually. If a planned order is selected a second time, e.g. because the first

processing was not completed, field o_ord_id in the return data contains the original information. The

field o_ord_id is unique in the planned data and may not be unique in the return data. If the field

o_ord_id is empty, this order shall be handled manually in the office.
7.4 Handling of products

Within an order, 0 to 99 product records may exist. The operator chooses one of the given product

records at the truck. This record is duplicated into the return data, filled with the actual data of the

transaction (loading or delivery), and saved. The internal number p_pos_no within the order is created

in the return data, starts at 1 and is incremented by 1 for every product record. The internal number in

the return data are not related with the internal number in the planning data. In the office, the

correlation of the planned data to the return data are shown in field p_pos_id. If field p_pos_id is empty,

it is an unplanned product record. If a planned product record is chosen a second time, e.g. because the

first time failed, field p_pos_id in the return data contains the original information. The field p_pos_id is

unique in the planned data and may not be unique in the return data. If an order contains unplanned

product records or product records which are handled twice, shall be processed in the office.

8 Fields and records of RC_File
A record container (RC) file may contain records of one or more different types.
Fields and records of RC_File according to Table 5.
---------------------- Page: 15 ----------------------
oSIST prEN 15969-2:2021
prEN 15969-2:2021 (E)
Table 5 — Fields and records of RC_File
Index Fieldname Data Required DEST Description Detailed description
Type
A-Article
Goods and service description

A00 a_deleted B X — Cancelled-flag If this Boolean is set to “1”, this record shall be deleted

from the list of records on the destination system.
If an article record is deleted, all corresponding S records
shall be deleted automatically!
A01 a_art_id C16 PK T Unique article identification. e.g. SAP product no.
primary key.

A02 a_art_no N3 U T Short product code number, as Short product no, used for manual input from driver, e.g.

defined by the host system CPDP code
A03 a_art_txt U30 X T Article name —
A04 a_pck_cnt N4.2 — T Content of packing in unit, as —
given in #A07 for pricing

A05 a_ovr_pck N4 — — Number of items in overpack e.g. 20 cans per box (only for information, not used for any

calculation)
A06 a_tare_wgh N5.2 — T Empty weight of packing (in —
kg)

A07 a_unit_txt U6 X T Abbreviation of unit of measure e.g. 'L', kg', m3', 'pieces'

(SI units shall be used when
applicable)
A08 a_unit_msr N1 X T Unit of measure See #L1007 of prEN 15969-1:2021
A09 a_pck_txt U30 — T Packing name e.g. “Pieces2”, “Drum”,…

A10 a_prc_fac N4 — T Unit price factor This factor will typically be 1, 10, 100 or 1000

---------------------- Page: 16 ----------------------
oSIST prEN 15969-2:2021
prEN 15969-2:2021 (E)
Index Fieldname Data Required DEST Description Detailed description
Type

A11 a_prc_code N1 — T Price code This code indicates how to handle 'a_unit_prc' within

calculations:
0 = piece, the multiplier for 'p_unit_prc' ist field #P14
1 = quantity, the multiplier for 'p_unit_prc' is field #P14
2 = fixed price, the field #P07 'p_unit_prc' is the valid price.
No calculations will take place.
A12 a_unit_prc N5.4 — T Price for unplanned delivery —
A13 a_tax_id C16 — T Tax reference links to #T01.
A14 a_met_prod N3 X T Metered product code 0 - all unmetered products
1 to
...

Questions, Comments and Discussion

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