EN 17071:2019

2003-01.Slovenski inštitut za standardizacijo. Razmnoževanje celote ali delov tega standarda ni dovoljeno.Informacijska tehnologija - Tehnike za samodejno razpoznavanje in zajem podatkov - Elektronska identifikacijska tablicaInformationstechnik - Automatische Identifikation und Datenerfassungsverfahren - Elektronisches TypenschildTechnologies d'information - Techniques d'identification automatique et de saisie de données - Plaque signalétique électroniqueInformation technology - Automatic identification and data capture techniques - Electronic identification plate35.040.50Tehnike za samodejno razpoznavanje in zajem podatkovAutomatic identification and data capture techniquesICS:Ta slovenski standard je istoveten z:EN 17071:2019SIST EN 17071:2019en,fr,de01-maj-2019SIST EN 17071:2019SLOVENSKI
STANDARD
EUROPEAN STANDARD NORME EUROPÉENNE EUROPÄISCHE NORM
EN 17071
February
t r s { ICS
u wä r v rä w r English Version
Information technology æ Automatic identification and data capture techniques æ Electronic identification plate Technologies de l 5information æ Techniques automatiques d 5identification et de saisie de données æ Plaque signalétique électronique
Informationstechnik æ Automatische Identifikation und Datenerfassungsverfahren æ Elektronisches Typenschild This European Standard was approved by CEN on
t w June
t r s zä
egulations 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ä
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á Former Yugoslav Republic of Macedoniaá Franceá Germanyá Greeceá Hungaryá Icelandá Irelandá Italyá Latviaá Lithuaniaá Luxembourgá Maltaá Netherlandsá Norwayá Polandá Portugalá Romaniaá Serbiaá Slovakiaá Sloveniaá Spainá Swedená Switzerlandá Turkey 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
t r s { CEN All rights of exploitation in any form and by any means reserved worldwide for CEN national Membersä Refä Noä EN
s y r y sã t r s { ESIST EN 17071:2019

Example with simple data and several compression methods . 30 Annex B (informative)
Data Identifier “F” for Hierarchical Structure . 35 Annex C (informative)
Data Extensions for Events . 36 C.1 Data Extensions for Events . 36 C.2 Tree structure for events . 36 Annex D (informative)
Access to External Data Records via Internet . 40 D.1 Use Cases . 40 D.2 With Data Identifiers . 40 D.3 Example for Internet Access via P2P Data Identifier “34L” . 40 D.4 With Application Identifiers . 41 D.5 Example for Internet Access . 41 Annex E (informative)
Logic to Parse Out the Unique Identification When Data Identifiers are used . 42 Bibliography . 43
Figure 1 — Interoperability on data level Once the data are made available in a target application the further processing, e.g. access additional data via the internet- should not depend on the data carrier used for the type label. 2D symbols and human readable text should be easy to use as backup for RFID media, and vice versa, when possible. 4.4 Unique Identification The identifier/identification relate to the object to which the type plate is attached, not to the type plate itself. Each individual instance of serialized objects marked with a type plate is uniquely identified. The unique identification can be within one “monomorphic” data element, or can be splitted in several data elements. 4.5 Data Attributes Unique identification of items is the minimum mandatory information in this standard. Data attributes vary greatly depending on the type of items and the sector of use. Many regulations are mandating the use -especially of human readable- data attributes. Typical data attributes related to identification and approvals are: product code, product version or revision, serial number, lot number, country of origin, production date, company name, company ID Examples of technical data attributes are: operating voltage, power, weight, pressure, length, width, maximum temperature, etc. Data Attributes can be marked on the type label, or can be referred via the type label. 4.6 Data Carriers Data carriers in scope are human readable text, 2D symbols and RFID tags. For human readable text this standard has some requirements, but does not define specific headers or fonts. For 2D symbols this standard allows DataMatrix and QR-Code. SIST EN 17071:2019

Human Readable 2D Symbol RFID HF and UHF RFID NFC Type of information Heading DI/AI EPC, AFI, DI/AI, Relative OID NDEF Value of information Data Data Data Data Format of information Font Syntax Syntax Syntax Communication of information Visual Symbology Air interface protocol Air interface protocol 4.7 Data Structures Human readable text is structured in headers and data. 2D symbols and RFID content is structured with ISO/IEC 15434 Data Transfer Syntax –if more than one element-, and semantics according to ISO/IEC 15418. ISO/IEC 15418 is referring to ANS MH 10.8.2 and GS1 General Specifications. The semantics of data elements is indicated either with ANS MH 10.8.2 Data Identifiers or GS1 Application Identifiers. When RFID (including NFC) is used, then the ISO/IEC 15962 applies in addition. NOTE When NFC is used, the data (according to ISO/IEC 15962, ISO/IEC 15434 and ISO/IEC 15418) is encoded in the “payload” of an NDEF record. 4.8 Detailed Application Standards When more specific application standards do apply in addition to this standard, they can be referred to with the dedicated data element identified with “10N”, when Data Identifiers are used. 5 Data 5.1 General aspects For any machine readable media –RFID or 2D symbol- the content shall contain an ISO/IEC 15459 conform unique identification of the marked item. The tag identification (TID) is not sufficient for the purpose of unique identification of the marked item, as the TID does not directly refer to the object to be identified, but provides “only” the unique identification of the transponder. The TID is used by some anti-collision-protocols for simultaneous reading of several transponders (bulk reading). 5.2 Data Quality Dimensions The data quality is based to the requirements of the users and their situation where the data are used. Data quality is always made dependent on the requirements of the product information. The data and the quality of this data shall always comply with the requirements. The basis for the information are data, thus the data quality affects the quality of the information obtained from the data. The statements regarding to the quality of information refer to how accurately this describes the reality or how reliable it is. However, to measure the quality of data, all possible applications and requests for data shall be understood. The generic data quality issues in conjunction with the specific requirements of the SIST EN 17071:2019

the maximum lifetime of the item.
the maximum time some party may have obligations to provide data related to this item. E.g. as part of fiscal audits covering some years of the past.
the maximum time the reference may be needed for some user process, e.g. for checks in customer databases. The data shall be easily accessible for parties with justified interest. 5.8 Unique Identification 5.8.1 Monomorphic and Combined Unique Identification The unique identification of the item shall conform to ISO/IEC 15459-4 that specifies two methods: 1) Unique identification by class of items / combined unique identification: The unique ID comprises a company identification number (CIN) followed by an identifier of the item class and a serial number. In this case the unique identification results from a combination of several data elements. The first data element shall be globally unique, and the other data element(s) shall be unique within the domain of the first data element. 2) Unique identification by company / monomorphic unique ID. The unique ID comprises a company identification number (CIN) followed by a serial number of the individual item. In this case the unique identification is provided by one data element alone, sometimes described as a “monomorphic” data element for unique identification. Furthermore, ISO/IEC 15459-4 specifies 3 methods to encode data in AIDC carriers: GS1 Application Identifiers, ASC MH 10 Data Identifiers and objet identifiers according ISO/IEC 15962. SIST EN 17071:2019

GS1 Application Identifiers Object identifiers mapping to Application Identifiers ASC MH 10 Data Identifiers Object identifiers mapping to Data Identifiers Unique ID by item class / combined unique ID “01” plus “21” 1 0 15459 4 3 “25P” plus “S” 1 0 15459 4 6 Unique ID by item class / combined unique ID with company code unique n.a. (company code is always part of product code) n.a. (company code is always part of product code) “18V” plus “1P” plus “S” 1 0 15459 4 (DIs may be used in the data string, but there is no implied mapping from OI) Unique ID by company / monomorphic unique ID “8004” 1 0 15459 4 2 “25S” 1 0 15459 4 4 Depending on the data carrier, instead of AIs or DIs objet identifiers according ISO/IEC 15962 can be used. In that case this standard recommends to use only such object identifiers that can be mapped to GS1 Application Identifiers or ASC MH 10 date identifiers to ease interopabibility on data level. ISO/IEC 15459-4 does not limit the possible suite of data qualifiers for the purpose of unique identification to the data qualifiers above. In the example above, the Data Identifier “25S” is used as example of data elements of monomorphic globally unique identifiers. ANS MH 10.8.2 lists some other ISO/IEC 15459-2 compliant globally unique monomorphic data elements, such as “I” (upper case “i”) for a vehicle identification number, or “4I” for the vehicle identification number plus vehicle license plate, which may be used for the unique identification of items. See also informative Annex E for a possible logic to parse out the unique identification when Data Identifiers are used. 5.8.2 Unique ID with Application Identifiers 5.8.2.1 Methods to use GS1 Application Identifiers for the Unique ID All assets start their lifecycle as a trade item (merchandise) identified by a Global Trade Item Number (GTIN). The Global Trade Item Number (GTIN) can be used by a company to uniquely identify all of its trade items. GS1 defines trade items as products or services that are priced, ordered or invoiced at any point in the supply chain. Once a company acquires such a trade item, the company may classify that item as an asset. Each asset requires an appropriate identifier to ensure efficient asset management. Asset identification and management is dependent on the type of application and owner. So we have two ways to create a unique identifier: 1) A trade Item with serial number (SGTIN) SIST EN 17071:2019

Figure 2 — Format of GTIN The Application Identifier (21) indicates that the GS1 Application Identifier data field contains a serial number. A serial number is assigned to an entity for its lifetime. When combined with a GTIN, a serial number uniquely identifies an individual item. The serial number field is alphanumeric and may include all characters contained the figure below. The manufacturer determines the serial number. Figure 3 shows the format of a serial number.
Figure 3 — Format of the Element String Figure 4 shows an example of a GTIN and serial number encoded in a barcode. SIST EN 17071:2019

Figure 4 — Example of GTIN + Serial number encoded in a Barcode 5.8.2.3 Global Individual Asset Identifier (GIAI) Companies can apply a GIAI on any asset to uniquely identify and manage that asset. Companies assigning the GIAI can be either the asset owner or a leasing or rental company. The GIAI can be encoded in a barcode or EPC/RFID tag connected to the asset. Applied electronically, the GIAI enables a company to record individual assets in asset management and accounting systems across company boundaries. Companies can quickly identify the individual asset, and register relevant data such as its location as well as repair and maintenance activities. The GIAI is assigned by the asset owner. Semantical: The Application Identifier (8004) indicates that the GS1 Application Identifier data field contains a GIAI (Global Individual Asset Identifier). This Element String may be used for the unique identification of individual assets to provide a means to store relevant data. The GS1 Company Prefix is allocated by GS1 Member Organisations to the company that allocates the GIAI – here the owner of the individual asset. It makes the number unique worldwide. The structure and content of the Individual Asset Reference is at the discretion of owner of the GS1 Company Prefix to uniquely identify each individual asset. So the key comprises a GS1 Company Prefix and Individual Asset Reference. Therefore, a GIAI always identifies each instance of an individual asset. Figure 5 shows the format of a Global Individual Asset Identifier.
Figure 5 — Format of the Element String Figure 6 shows an example of a GIAI encoded in a barcode.
Figure 6 — Example of GIAI encoded in a Barcode SIST EN 17071:2019

Figure 7 — Example of an UID according to ISO/IEC 15459-4 with Data Identifier „25S“ NOTE When selecting an issuing agency it has to be considered, that the UID is also subject to criteria defined by the issuing agency. The large majority of issuing agencies supports the example with Data Identifier, enhanced with the code for the issuing agency, e.g. “UN” for DUNS, “LE” for EDIFICE, “LH” for EHIBCC or “QC” for industry in general. 5.8.3.2 Unique ID with Data Identifiers 25P plus S (Unique Product Code + Serial Number) This UID construct consists of a Data Identifier “25P”, the code of an issuing agency, the registered company code and the product code. A separated data element consists of the Data Identifier “S” and a serial number, which shall be unique within this product code. The order of the elements does not matter. The elements shall be separated. 5.8.3.3 Unique ID with Data Identifiers 18V, 1P and S (Unique Company Code, Product Code, Serial Number) This UID construct consists of a Data Identifier “18V”, the code of an issuing agency and the registered company code. Another separated data element consists of the Data Identifier “1P” and the product code assigned by the manufacturer. This product code shall be unique within the company code. Another separated data element consists of the Data Identifier “S” and a serial number, which shall be unique within this product code. The order of the elements does not matter. The elements shall be separated. 5.9 Data on Object 5.9.1 Mandatory Data The only mandatory data required by this standard is a unique identification. NOTE: This unique identification is also part of the “basic data”. 5.9.2 Basic Data The relevant “basic data” for an item to be marked depend on the specific items. E.g. for machines, the Machinery Directive defines human readable information to be marked on machines. For other types of items the relevant directives and standards shall be considered. SIST EN 17071:2019

S or 25S (21) Lot number x 1T or 25T (10) 1T or 25T (10) product designation (Machine, model variant, type designation or the like) x n.a. e n.a. n.a. e n.a. Manufacturing date x 16D or 7D or 10D or 23D (11) or (8008) 16D or 7D or 10D or 23D (11) or(8008) Country of origin as “Made in ” followed by full country name x n.a. c n.a. c n.a. c n.a. c Country of origin in EN ISO 3166-1 two character country code n.a. 4L (422) 4L (422) UID (Unique identification according ISO/IEC 15459-4 and ISO/IEC 17367. It contains the unique identification of the object to be identified.) x 25S (8004) or
(01) plus (21) 25S or combination 18V, and S or combination S and 25P (8004) or
(01) plus (21) CE-mark x f n.a. n.a. n.a. n.a. RFID emblem x n.a. n.a. n.a. n.a. a covered by ISO/IEC 15459 conform company ID. SIST EN 17071:2019

use the same syntax and semantics of the basic date elements in this data carrier
are located “later” in the data string than the basic data elements, if the same date elements (designated with corresponding DIs/AIs or relative OIDs) are used e.g. in hierarchical data that may be used for basic data elements 5.9.4 Variable Data Contrary to printed type plates, some transponders offer the feature to write on them later. This feature can be used e.g. to log maintenance activities during the live-time of the equipment. A separate memory segment is recommended –but not required- for this on each transponder to reduce the risk of unintended overwriting / erasing of other data. Any additional variable data are allowed, as long as they fulfill the following criteria:
use the same syntax and semantics of the basic date elements in this data carrier
use the appropriate ISO/IEC 15418 | ANS MH10.8.2 Data or Application Identifiers for all data elements
use the F-structure according ISO/IEC 15418 | ANS MH10.8.2, if there is more than one record in the variable data
are located “later” in the data string than the basic data elements, if the same date elements (designated with corresponding DIs/AIs or relative OIDs) are used e.g. in hierarchical data Apart these minimum requirements, encoding variable data are not in the scope of this standard, but may be specified in industry sector specific application standards as add on to this standard. 5.9.5 Order of the Data Elements These basic data shall be encoded the first time one of these Data Identifiers is used. In case some of these Data Identifiers are used for another additional purpose than to designate the basic data above, e.g. as dates for maintenance activities, these data elements shall be located “later” in the data string and be embedded in the “F-structure” according ISO/IEC 15418 | ANS MH10.8.2. If several of the options for one basic data are provided, e.g. both “1P” and “25P”, then systems not knowing details of the data string beyond this standard shall use at least the first of these data elements for further processing. Apart this, there are no requirements by this standard for the order of the data elements. NOTE This restriction for the order of the data elements facilitates, that all systems -without need for knowing details of the data string beyond this standard- can parse the basic data elements out of this data string. SIST EN 17071:2019

QR Code ISO/IEC 18004 ISO/IEC 15424 Symbology Identifier “]Q1” n.a. ISO/IEC 15434 ISO/IEC 15418 | ANS MH 10.8.2 Data Identifiers
GS1 QR Code ISO/IEC 18004 ISO/IEC 15424 Symbology Identifier “]Q3” n.a. ISO/IEC 15434 ISO/IEC 15418 | ANS MH 10.8.2 Application Identifiers
HF tag 13,56 MHz ISO/IEC 18000-3 Mode 1 n.a. n.a.
HF tag 13,56 MHz ISO/IEC 18000-3 Mode 3 n.a. n.a. ISO/IEC 15434
ISO/IEC 15418 | ANS MH 10.8.2 Data
HF tag 13,56 MHz NFC Forum Type 2 Tag (based on ISO/IEC 14443A) n.a. See specifications from NFC Forum ISO/IEC 15434 ISO/IEC 15418 | ANS MH 10.8.2 Application Identifiers
HF tag 13,56 MHz NFC For
...