ISO/IEC 19987:2015

Information technology — EPC Information services — Specification

ISO/IEC 19987:2015 is a GS1 Standard that defines Version 1.1 of EPC Information Services (EPCIS). The goal of EPCIS is to enable disparate applications to create and share visibility event data, both within and across enterprises. Ultimately, this sharing is aimed at enabling users to gain a shared view of physical or digital objects within a relevant business context. "Objects" in the context of EPCIS typically refers to physical objects that are identified either at a class or instance level and which are handled in physical handling steps of an overall business process involving one or more organizations. Examples of such physical objects include trade items (products), logistic units, returnable assets, fixed assets, physical documents, etc. "Objects" may also refer to digital objects, also identified at either a class or instance level, which participate in comparable business process steps. Examples of such digital objects include digital trade items (music downloads, electronic books, etc.), digital documents (electronic coupons, etc), and so forth. Throughout this document the word "object" is used to denote a physical or digital object, identified at a class or instance level, that is the subject of a business process step. EPCIS data consist of "visibility events," each of which is the record of the completion of a specific business process step acting upon one or more objects. The EPCIS standard was originally conceived as part of a broader effort to enhance collaboration between trading partners by sharing of detailed information about physical or digital objects. The name EPCIS reflects the origins of this effort in the development of the Electronic Product Code (EPC). It should be noted, however, that EPCIS does not require the use of Electronic Product Codes, nor of Radio-Frequency Identification (RFID) data carriers, and as of EPCIS 1.1 does not even require instance-level identification (for which the Electronic Product Code was originally designed). The EPCIS standard applies to all situations in which visibility event data is to be captured and shared, and the presence of "EPC" within the name is of historical significance only. EPCIS provides open, standardised interfaces that allow for seamless integration of well-defined services in inter-company environments as well as within companies. Standard interfaces are defined in the EPCIS standard to enable visibility event data to be captured and queried using a defined set of service operations and associated data standards, all combined with appropriate security mechanisms that satisfy the needs of user companies. In many or most cases, this will involve the use of one or more persistent databases of visibility event data, though elements of the Services approach could be used for direct application-to-application sharing without persistent databases. With or without persistent databases, the EPCIS specification specifies only a standard data sharing interface between applications that capture visibility event data and those that need access to it. It does not specify how the service operations or databases themselves should be implemented. This includes not defining how the EPCIS services should acquire and/or compute the data they need, except to the extent the data is captured using the standard EPCIS capture operations. The interfaces are needed for interoperability, while the implementations allow for competition among those providing the technology and implementing the standard. EPCIS is intended to be used in conjunction with the GS1 Core Business Vocabulary (CBV) standard [CBV1.1]. The CBV standard provides definitions of data values that may be used to populate the data structures defined in the EPCIS standard. The use of the standardized vocabulary provided by the CBV standard is critical to interoperability and critical to provide for querying of data by reducing the variation in how different businesses express common intent. Therefore, a

Technologies de l'information — Services d'information sur les codes de produit électronique — Spécification

General Information

• Status: Withdrawn
• Publication Date: 13-Sep-2015
• Withdrawal Date: 13-Sep-2015
• ICS: 35.200 - Interface and interconnection equipment
• Technical Committee: ISO/IEC JTC 1 - Information technology
• Drafting Committee: ISO/IEC JTC 1 - Information technology
• Current Stage: 9599 - Withdrawal of International Standard
• Start Date: 04-Oct-2017
• Completion Date: 30-Oct-2025

Relations

• Revised: ISO/IEC 19987:2017 - Information technology — EPC Information Services (EPCIS) Standard
• Effective Date: 24-Dec-2016

Standards Content (Sample)

INTERNATIONAL ISO/IEC
STANDARD 19987
First edition
2015-09-15
Information technology — EPC
Information services — Specification
Technologies de l’information — Services d’information sur les codes
de produit électronique — Spécification
Reference number
©
ISO/IEC 2015
© ISO/IEC 2015, Published in Switzerland
All rights reserved. Unless otherwise speci�ied, no part of this publication may be reproduced or utilized otherwise in any form
or by any means, electronic or mechanical, including photocopying, or posting on the internet or an intranet, without prior
written permission. Permission can be re�uested from either ISO at the address below or ISO�s member body in the country of
the requester.
ISO copyright of�ice
Ch. de Blandonnet 8 • CP 401
CH-1214 Vernier, Geneva, Switzerland
Tel. [phone]
Fax [phone]
copyright�iso.org
www.iso.org
ii © ISO/IEC 2015 – All rights reserved

Foreword
ISO (the International Organization for Standardization) and IEC (the International Electrotechnical
Commission) form the specialized system for worldwide standardization. National bodies that are
members of ISO or IEC participate in the development of International Standards through technical
committees established by the respective organization to deal with particular fields of technical
activity. ISO and IEC technical committees collaborate in fields of mutual interest. Other
international organizations, governmental and non‐governmental, in liaison with ISO and IEC, also
take part in the work. In the field of information technology, ISO and IEC have established a joint
technical committee, ISO/IEC JTC 1.
The procedures used to develop this document and those intended for its further maintenance are
described in the ISO/IEC Directives, Part 1. In particular the different approval criteria needed for
the different types of document should be noted. This document was drafted in accordance with the
editorial rules of the ISO/IEC Directives, Part 2 (see www.iso.org/directives).
Attention is drawn to the possibility that some of the elements of this document may be the subject
of patent rights. ISO and IEC shall not be held responsible for identifying any or all such patent
rights. Details of any patent rights identified during the development of the document will be in the
Introduction and/or on the ISO list of patent declarations received (see www.iso.org/patents).
Any trade name used in this document is information given for the convenience of users and does
not constitute an endorsement.
For an explanation on the meaning of ISO specific terms and expressions related to conformity
assessment, as well as information about ISO's adherence to the WTO principles in the Technical
Barriers to Trade (TBT), see the following URL: Foreword — Supplementary information.
The committee responsible for this document is ISO/IEC JTC 1, Information technology.
© ISO/IEC 2015 – All rights reserved iii

EPC Information Services (EPCIS)
GDSN Package Measurement Rules
EPC Information Services (EPCIS)
Version 1.1 Specification
GS1 Standards Document
GS1 Standard
Version 1.1, May 2014
Version 1 13 2 Dec 2013
Version 1.1, May-2014 All contents © 2007–2014 GS1    Page 1 of 169
EPC Information Services (EPCIS)

© 2007–2014 GS1 AISBL
All rights reserved.
GS1 Global Office
Avenue Louise 326, bte 10
B-1050 Brussels, Belgium
Disclaimer
GS1 AISBL (GS1) is providing this document as a free service to interested industries.
This document was developed through a consensus process of interested parties in developing
the Standard. Although efforts have been made to assure that the document is correct, reliable, and technically
accurate, GS1 makes NO WARRANTY, EXPRESS OR IMPLIED, THAT THIS DOCUMENT IS CORRECT,
WILL NOT REQUIRE MODIFICATION AS EXPERIENCE AND TECHNOLOGY DICTATE,
OR WILL BE SUITABLE FOR ANY PURPOSE OR WORKABLE IN ANY APPLICATION,
OR OTHERWISE. Use of this document is with the understanding that GS1 DISCLAIMS ALL
WARRANTIES, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY
IMPLIED WARRANTY OF NON-INFRINGEMENT OF PATENTS OR COPYRIGHTS,
MERCHANTABILITY AND/OR FITNESS FOR A PARTICULAR PURPOSE,
THAT THE INFORMATION IS ERROR FREE, NOR SHALL GS1 BE LIABLE
FOR DAMAGES OF ANY KIND, INCLUDING DIRECT, INDIRECT, INCIDENTAL, SPECIAL,
CONSEQUENTIAL OR EXEMPLARY DAMAGES, ARISING OUT OF USE OR THE INABILITY
TO USE INFORMATION CONTAINED HEREIN OR FROM ERRORS CONTAINED HEREIN.
Version 1.1, May-2014 All contents © 2007–2014 GS1    Page 2 of 169
© ISO/IEC 2015 – All rights reserved

EPC Information Services (EPCIS)
2 Abstract
3 This document is a GS1 Standard that defines Version 1.1 of EPC Information Services (EPCIS).
4 The goal of EPCIS is to enable disparate applications to create and share visibility event data,
5 both within and across enterprises. Ultimately, this sharing is aimed at enabling users to gain a
6 shared view of physical or digital objects within a relevant business context.
7 Status of this document
8 This section describes the status of this document at the time of its publication. Other
9 documents may supersede this document. The latest status of this document series is
10 maintained at GS1. See www.gs1.org/gsmp for more information.
11 This version of the GS1 EPCIS 1.1 Standard is the ratified version and has completed all GSMP
12 steps.
13 Comments on this document should be sent [e-mail].
14 Differences from EPCIS 1.0.1
15 EPCIS 1.1 is fully backward compatible with EPCIS 1.0.1.
16 EPCIS 1.1 includes these new or enhanced features:
17 • Support for class-level identification is added to ObjectEvent,AggregationEvent,
18 and TransformationEvent through the addition of quantity lists.
19 • A new event type, TransformationEvent, provides for the description of events in
20 which inputs are consumed and outputs are produced.
21 • The “why” dimension of all event types are enhanced so that information about the sources
22 and destinations of business transfers may be included.
23 • The “why” dimension of certain event types are enhanced so that item/lot master data may be
24 included.
25 • The SimpleEventQuery is enhanced to encompass the above changes to event types.
26 • The introductory material is revised to align with the GS1 System Architecture.
27 • The XML extension mechanism is explained more fully.
28 • The QuantityEvent is deprecated, as its functionality is fully subsumed by
29 ObjectEvent with the addition of quantity lists.
Version 1.1, May-2014 All contents © 2007–2014 GS1    Page 3 of 169
© ISO/IEC 2015 – All rights reserved

EPC Information Services (EPCIS)
31 Table of Contents
32 1 Introduction.6
33 2 Relationship to the GS1 System Architecture .7
34 2.1 Overview of GS1 Standards . 7
35 2.2 EPCIS in Relation to the “Capture” and “Share” Layers. 8
36 2.3 EPCIS in Relation to Trading Partners . 10
37 2.4 EPCIS in Relation to other GS1 System Architecture Components. 12
38 3 EPCIS Specification Principles.15
39 4 Terminology and Typographical Conventions.16
40 5 EPCIS Specification Framework .16
41 5.1 Layers . 16
42 5.2 Extensibility . 18
43 5.3 Modularity. 18
44 6 Abstract Data Model Layer.19
45 6.1 Event Data and Master Data. 19
46 6.2 Vocabulary Kinds . 22
47 6.3 Extension Mechanisms . 23
48 6.4 Identifier Representation. 25
49 6.5 Hierarchical Vocabularies . 26
50 7 Data Definition Layer .26
51 7.1 General Rules for Specifying Data Definition Layer Modules. 27
52 7.1.1 Content. 27
53 7.1.2 Notation. 28
54 7.1.3 Semantics . 29
55 7.2 Core Event Types Module – Overview . 29
56 7.3 Core Event Types Module – Building Blocks. 33
57 7.3.1 Primitive Types. 33
58 7.3.2 Action Type . 34
59 7.3.3 The “What” Dimension . 34
60 7.3.4 The “Where” Dimension – Read Point and Business Location . 40
61 7.3.5 The “Why” Dimension . 44
62 7.3.6 Instance/Lot Master Data (ILMD). 47
63 7.4 Core Event Types Module – Events . 48
64 7.4.1 EPCISEvent . 48
65 7.4.2 ObjectEvent (subclass of EPCISEvent). 50
66 7.4.3 AggregationEvent (subclass of EPCISEvent). 54
67 7.4.4 QuantityEvent (subclass of EPCISEvent) – DEPRECATED . 60
Version 1.1, May-2014 All contents © 2007–2014 GS1    Page 4 of 169
© ISO/IEC 2015 – All rights reserved

EPC Information Services (EPCIS)
68 7.4.5 TransactionEvent (subclass of EPCISEvent) . 61
69 7.4.6 TransformationEvent (subclass of EPCISEvent) . 67
70 8 Service Layer .71
71 8.1 Core Capture Operations Module . 73
72 8.1.1 Authentication and Authorization . 73
73 8.1.2 Capture Service . 73
74 8.2 Core Query Operations Module . 75
75 8.2.1 Authentication . 75
76 8.2.2 Authorization . 75
77 8.2.3 Queries for Large Amounts of Data . 76
78 8.2.4 Overly Complex Queries. 76
79 8.2.5 Query Framework (EPCIS Query Control Interface) . 77
80 8.2.6 Error Conditions . 87
81 8.2.7 Predefined Queries for EPCIS . 90
82 8.2.8 Query Callback Interface . 109
83 9 XML Bindings for Data Definition Modules.109
84 9.1 Extensibility Mechanism. 109
85 9.2 Standard Business Document Header. 112
86 9.3 EPCglobal Base Schema. 114
87 9.4 Additional Information in Location Fields . 114
88 9.5 Schema for Core Event Types. 115
89 9.6 Core Event Types – Examples (non-normative). 123
90 9.6.1 Example 1 – Object Events with Instance-Level Identification .
...