SIST EN 15969-2:2011
(Main)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 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.
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
Diese Europäische Norm beschreibt die für die Tourverwaltung notwendige Datenstruktur, indem Aufträge von gemessenen und ungemessenen Produkten online zum Tankwagen übertragen werden. Abgefertigte Aufträge werden jedes Mal, wenn der Tankwagen online ist, sofort oder später zum Zentralrechner im Büro zurück übertragen.
Die Norm legt den Austausch kommerzieller und logistischer Daten zwischen den elektronischen Einrich-tungen, dem Bordcomputer des Tankfahrzeuges und stationären Einrichtungen für alle Kommunikationswege zwischen diesen Stellen fest.
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
La présente Norme européenne décrit la structure de données requise 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é.
La présente norme 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.
Posode za prevoz nevarnih snovi - Digitalni vmesnik za prenos podatkov med vozilom s posodo in stacionarnimi napravami - 2. del: Komercialni in logistični podatki
Ta evropski standard določa strukturo podatkov, potrebno za upravljanje poti, tako da prek povezave do vozila sproti razvršča naročila izmerjenih in neizmerjenih proizvodov. Obdelana naročila se prenesejo nazaj do gostitelja v pisarni takoj ali pozneje, vsakič ko je vozilo povezano. Določa prenos komercialnih in logističnih podatkov med opremo transportnega vozila, računalnikom na vozilu s posodo in stacionarno opremo po vseh komunikacijskih kanalih med temi stranmi.
General Information
Relations
Standards Content (Sample)
2003-01.Slovenski inštitut za standardizacijo. Razmnoževanje celote ali delov tega standarda ni dovoljeno.SRGDWNLTanks 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 DatenCiternes 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 logistiquesTanks for transport of dangerous goods - Digital interface for the data transfer between tank vehicle and with stationary facilities - Part 2: Commercial and logistic data35.240.60Uporabniške rešitve IT v transportu in trgoviniIT applications in transport and trade23.020.20Posode in vsebniki, montirani na vozilaVessels and containers mounted on vehicles13.300Varstvo pred nevarnimi izdelkiProtection against dangerous goodsICS:Ta slovenski standard je istoveten z:EN 15969-2:2011SIST EN 15969-2:2011en,fr,de01-november-2011SIST EN 15969-2:2011SLOVENSKI
STANDARD
SIST EN 15969-2:2011
EUROPEAN STANDARD NORME EUROPÉENNE EUROPÄISCHE NORM
EN 15969-2
September 2011 ICS 35.240.60 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 dangereuses -Interface numérique pour le transfert de données sur des véhicules citernes et avec des installations fixes -Partie 2 : Données commerciales et logistiques
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 This European Standard was approved by CEN on 18 June 2011.
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, Romania, Slovakia, Slovenia, Spain, Sweden, Switzerland and United Kingdom.
EUROPEAN COMMITTEE FOR STANDARDIZATION
COMITÉ EUROPÉEN DE NORMALISATION EUROPÄISCHES KOMITEE FÜR NORMUNG
Management Centre:
Avenue Marnix 17,
B-1000 Brussels © 2011 CEN All rights of exploitation in any form and by any means reserved worldwide for CEN national Members. Ref. No. EN 15969-2:2011: ESIST EN 15969-2:2011
EN 15969-2:2011 (E) 2 Contents Page Foreword .3Introduction .41Scope .62Normative references .63Terms and definitions .64General .75Files .75.1Format identifiers.75.2Relations .85.3File naming conventions . 116Fields of special types . 116.1Text module reference . 116.2Geo-Coordinates . 126.3UTF-8 strings . 127Price calculation rules . 127.1General . 127.2Low volume (surcharge) . 127.3Pricing of packed products, container, pieces . 137.3.1Article records . 137.3.2Low volume (surcharge) . 137.3.3Price calculation
methods . 137.4Taxes . 148Description of trip management . 148.1Handling of several trips . 148.2Handling of a pseudo-trip with a pool of orders . 148.3Handling of orders . 148.4Handling of products . 159Fields and records of RC_File . 1510Multi-Order Data (Subnode RC_FILE) . 4010.1General . 4010.2Node RC_File . 4010.3Information concerning application. 4110.3.1Simple trip plan, using FTL connection . 4110.3.2Simple Trip Plan, Using FTP and RC_FILE . 4210.3.3Managing static data, using FTL connection . 4410.3.4Managing static data under FTP . 44 SIST EN 15969-2:2011
EN 15969-2:2011 (E) 3 Foreword This document (EN 15969-2:2011) has been prepared by Technical Committee CEN/TC 296 “Tanks for 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 March 2012, and conflicting national standards shall be withdrawn at the latest by March 2012. Attention is drawn to the possibility that some of the elements of this document may be the subject of patent rights. CEN [and/or CENELEC] shall not be held responsible for identifying any or all such patent rights. This European Standard EN 15969, Tanks for transport of dangerous goods – Digital interface for the data transfer between tank vehicle and with stationary vehicles, is divided into the following parts: Part 1 — Protocol Specification – Control, measurement and event data Part 2 — Commercial and logistic data 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, Romania, Slovakia, Slovenia, Spain, Sweden, Switzerland and the United Kingdom. SIST EN 15969-2:2011
EN 15969-2:2011 (E) 4 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 European Standard specifies data format for all interconnecting communication paths for commercial issues. This European Standard 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; Trip management; Data for invoicing with surcharge; Data for delivery packaged goods; Handle planned and unplanned deliveries. SIST EN 15969-2:2011
EN 15969-2:2011 (E) 5
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 SIST EN 15969-2:2011
EN 15969-2:2011 (E) 6 1 Scope 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. 2 Normative references The following referenced documents are indispensable for the application 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 the product recognition device EN 15969-1:2011, 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 codes (ISO 3166-1:2006) ISO 639-1, Codes for the representation of names of languages — Part 1: Alpha-2 code ISO 4217, Codes for the representation of currencies and funds ISO/IEC 10646-1, Information technology — Universal Multiple-Octet Coded Character Set (UCS) — Part 1: Architecture and Basic Multilingual Plane 3 Terms and definitions For the purposes of this document, the terms and definitions given in EN 15969-1:2011 and the following apply. 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 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 SIST EN 15969-2:2011
EN 15969-2:2011 (E) 7 4 General This document shall only be used in conjunction with EN 15969-1 and shall not modify or override any of the requirements of EN 15969-1. 5 Files 5.1 Format identifiers According to EN 15969-1. Table 1 — Record identifier and file type Record identifier Short description Description of file contents and possible destinations of the file Primary Key Deletion Identifier A Article List of all goods and/or services provided a_art_id a_deleted C Customer Customer database
c_cus_id c_deleted FB FTL batch Record type used to mark batch commands inside RC_file; see Table 11. - - SIST EN 15969-2:2011
EN 15969-2:2011 (E) 8 Table 1 (continued) Record identifier Short description Description of file contents and possible destinations of the file Primary Key Deletion Identifier H Trip A trip consists of a list of trip stops, which could be stops at customers (typ. unloading) or depots (typ. loading). h_tour_no h_deleted L Location All locations (depots, customers, etc) l_loc_id l_deleted LR Location restriction Restrictions for a location (time windows, vehicle accessibility, permitted actions) lr_loc_id lr_deleted N Notes Notes that can be specified for any object. n_ref_obj n_obj_id n_seq_no n_deleted O Order Represents a stop in a trip. This could be both a loadstop and an orderstop. per stop, several actions 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 o_tour_no o_ord_no o_deleted OR Order restrictions Order restrictions, used for scheduling and routing. or_ord_id or_deleted P Order lines Specifies the goods and services to be delivered at this stop (o-record). p_tour_no p_ord_no p_pos_no p_deleted R Driver List of all drivers r_drv_id r_deleted S Text-module reference Static texts for any object. provides text module references, to add a variable number of static texts to an object for printout. s_ref_obj s_obj_id s_seq_no s_deleted T Tax Different applicable VAT rates, used for invoice calculation. t_tax_id t_deleted X Text modules Texts which are repetitively used, may be stored in this database and referred to by a three-digit
numeric code in the S-record. x_blk_id x_lang_id x_deleted Y Annotations Optional annotations to any other type, this annotations are used to add manufacturer specific fields to 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. y_ann_obj y_obj_id y_ann_key y_deleted
5.2 Relations Figure 2 shows the relations between the different record types and contains only the fields relevant for these relations. SIST EN 15969-2:2011
EN 15969-2:2011 (E) 9
SIST EN 15969-2:2011
EN 15969-2:2011 (E) 10
SIST EN 15969-2:2011
EN 15969-2:2011 (E) 11 Key Symbol Meaning
Primary key, shall be unique
Foreign key, this attribute is referencing/reference
Attribute
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 5.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 Table 3 of
EN 15969-1:2011. If more than one file is transferred, they shall be processed in ascending order of file names. 6 Fields of special types 6.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. SIST EN 15969-2:2011
EN 15969-2:2011 (E) 12 EXAMPLE
Value Explanation99.0 Only record no. 99 is printed. 99.2 Record no. 99, 100, 101 are printed.
6.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
6.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-1. At most, x-times four bytes are required for storage.
7 Price calculation rules 7.1 General All prices shall be net prices. 7.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. SIST EN 15969-2:2011
EN 15969-2:2011 (E) 13 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 7.3 Pricing of packed products, container, pieces 7.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. 7.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. 7.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. 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'. SIST EN 15969-2:2011
EN 15969-2:2011 (E) 14 Formula:
price
= p_unit_prc 7.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 8 Description of trip management 8.1 Handling of several trips Any number of orders of record type O, combined in trips 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 trips at the truck. This trip record is duplicated into the return data, filled with the actual data and saved. The internal trip number h_tour_no in the return data starts at 1 and is incremented by 1 at every trip. The internal tour number in the return data is not related with the internal tour number in the planned data. In the office, the correlation of the planned data to the return data is shown in field h_tour_id. If field h_tour_id is empty, it is an unplanned trip. If a planned trip 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.
8.2 Handling of a pseudo-trip with a pool of orders It is also possible to work with only one (pseudo-) trip 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 trip. This trip is a pseudo trip and always contains the orders for the next few hours. There is no need to select a trip at the truck. This option is configurable at the truck. Within the return data, the trip data contains the completed orders in chronological sequence, e.g. by day, or by shift, after a driver change.
8.3 Handling of orders Within a trip 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 trip 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 is not related to the internal order number in the planned data. In the office, the correlation of the planned data to the return data is shown in the field o_ord_id. If field o_ord_id is empty, it is an unplanned order, which has to 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 has to be handled manually in the office. SIST EN 15969-2:2011
EN 15969-2:2011 (E) 15 8.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 is not related with the internal number in the planning data. In the office, the correlation of the planned data to the return data is 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, is must be processed in the office. 9 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 SIST EN 15969-2:2011
EN 15969-2:2011 (E) 16 Table 5— Fields and records of RC_File Index Fieldname Data Type RequiredDEST Description Detailed description 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. primary key. e.g. SAP product no. A02 a_art_no N3 U T Short product code number, as defined by the host system Short product no, used for manual input from driver, e.g. 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 (SI units shall be used when applicable) e.g. 'L', kg', 'm³', 'pieces' A08 a_unit_msr N1 X T Unit of measure 0: litres 1: gallons 2: kilograms 3: cubic metres 4: millimetres 5: hPa 6 pieces See #L1007 of EN 15969-1:2011 SIST EN 15969-2:2011
EN 15969-2:2011 (E) 17 Table 5 (continued) Index Fieldname Data Type RequiredDEST Description Detailed description A09 a_pck_txt U30
T Packing name e.g. “Pieces”, “Drum”,… A10 a_prc_fac N4
T Unit price factor This factor will typically be 1, 10, 100 or 1000 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
XT Metered product code
0 - all unmetered products 1 to 99 - metered products (met_prod) according to EN 14116 A15 a_add_id C16 T Product code of additive that shall be injected links to #A01.
A16 a_add_ppm N5 T Ratio in ppm Ratio concerning #A14; may be used to set on board injection system A17 a_sup_id C16 T code of supplementary product that might be added links to #A01. The article referenced may be added
when this article is delivered. e.g. deposit, ADR surcharge, see #A18 A18 a_sup_cat B T Category of supplementary product
If an supplementary product is specified in #A17 this field specifies whether it is: 0 – mandatory 1 - optional A19 a_art_cat N1 T Category of product 0 – available product 1 – common product (frequently used) 2 – fixed charge incurred (common supplementary product) SIST EN 15969-2:2011
EN 15969-2:2011 (E) 18 Table 5 (continued) Index Fieldname Data Type RequiredDEST Description Detailed description A20 a_fp_cl C2 T Flashpoint classes A1: flashpoint < 21 °C A2: flashpoint ≥ 21 °C, < 55 °C A3: flashpoint ≥ 55 °C A21 a_crny_sym C3 T Currency symbol according to ISO 4217, e.g. EUR, GBP, DKK, SEK, … A22 a_dens_15c N4.1 HT Density at 15°C
kg m-3 A23 a_prt_grs B
T Print gross quantity 0 – not print gross quantity, only net quantity 1 - print both, gross and net quantity In accordance with national regulations A24 a_pid_grd N3 X
PID - Grade
according to EN 14116, 0 non oil products A25 a_p_compc N5 X
Company code
Unique oil company code according to EN 14116 0 not specified > 0 specific company code
A26 a_p_prodc N10 X
Product code Company specific unique product code according to EN 14116. 0 not specified > 0 specific product code A27 a_lead_r N3
T Lead rate mg/l A28 a_sulphur
N4
T Sulphur content Unit PPM A29 a_lubr N4
T Lubricant agent Unit PPM A30 a_freez N4
T Anti-freezing agent Unit PPM A31 a_dye_c N1
T Dye code Dyed product d=0: unknown – don’t care d=1: undyed product
d=2: dyed product, red SIST EN 15969-2:2011
EN 15969-2:2011 (E) 19 Index Fieldname Data Type RequiredDEST Description Detailed description d=3: dyed product, green d=4: dyed product, blue d=5: dyed product, yellow d=6: dyed product, purple d=7: dyed product, brown A32 a_dye_r N3
T Dye ratio Unit PPM
SIST EN 15969-2:2011
EN 15969-2:2011 (E) 20 Table 5 (continued) Index Fieldname Data Type Required DESTDescription Detailed description C – Customer Customer data C00 c_deleted B X T Cancelled-flag If this Boolean is set to “1”, this record shall be deleted from the list of records on the destination system. If a customer record is deleted, all corresponding S
...
Questions, Comments and Discussion
Ask us and Technical Secretary will try to provide an answer. You can facilitate discussion about the standard in here.