Electronic Product Code Information Services (EPCIS) is a global GS1 Standard for creating and sharing visibility event data, both within and across enterprises, to enable users to gain a shared view of physical or digital objects within a relevant business context.[1] "Objects" in the context of EPCIS typically refers to physical objects that are handled in physical 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 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.
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). However, 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.[1]
EPCIS 1.0 was first ratified in April 2007.[2] At the time of ratification, over 30 companies had used the draft EPCIS standard to exchange data and collaborate with trading partners[3] As of 2014, 24 commercial products had received certificates of compliance to the EPCIS standard from GS1.[4] EPCIS 1.1 was ratified by GS1 in May, 2014.[5] EPCIS 1.2 was ratified by GS1 (in conjunction with CBV 1.2) in September 2016.
Historyedit
In 2001, the MIT Auto-ID Center published a paper proposing the Physical markup language (PML), intended as "a common 'language' for describing physical objects, processes and environments".[6] PML was one of four components of an "intelligent infrastructure" envisioned by the Auto-ID Center, the other three components being RFID tags, the Electronic Product Code, and the Object Naming Service. As the work of the MIT Auto-ID Center was taken up by EPCglobal in 2004, the PML concept was renamed Electronic Product Code Information Services (EPCIS), and efforts began to create a global standard. In 2005, the first version of the EPCglobal Architecture Framework was published, which introduced EPCIS as a standard under development and showed how it related to other components of an envisioned architecture for RFID-based tracking of physical objects within supply chains.[7]
EPCIS 1.0 was first ratified in April 2007.[2] A companion standard, the EPC Core Business Vocabulary 1.0, was ratified by EPCglobal in October, 2010.[8] Despite the RFID-oriented origins of EPCIS, it came to be used in applications that used bar codes exclusively or bar codes in combination with RFID tags.[9]
EPCIS 1.1 and CBV 1.1 were ratified in May 2014.[5] New features in EPCIS 1.1 include support for class-level identification (needed especially in bar code applications), a new event type to describe processes where inputs are transformed into outputs, and additional event data to describe business transfers and instance- or lot-level master data.[10]
EPCIS 1.2 and CBV 1.2 were ratified in September 2016. New features include a mechanism to declare a previous event as being erroneous, and a mechanism for including master data into the EPCIS document header.[11]
^ abRoberti, Mark, "The EPCIS Standard in Perspective," RFID Journal, April 2007.
^Meranda, Mike, "The Ratification of EPCIS," RFID Journal, April 2007.
^GS1, EPCglobal Software Certification Program, retrieved 26 October 2014.
^ abBeth Bacheldor, RFID News Roundup, RFID Journal, 29 May 2014.
^Brock, D. L., "The Physical Markup Language: A Universal Language for Physical Objects," MIT Auto-ID Center Whitepaper MIT-AUTOID-WH-003, February, 2001.
^Traub, K., et al, The EPCglobal Architecture Framework, July, 2005.
^EPCglobal, "Core Business Vocabulary Standard," EPCglobal Standard, October, 2010.
^GS1, "RFID Bar Code Interoperability," GS1 Guideline, August, 2012.
EPCIS and EPC Core Business Vocabulary standard page at GS1
EPCIS standard version 1.2. GS1, Version 1.2, September 2016
CBV standard version 1.2.2
EPCIS and CBVImplementation Guideline
EPCIS Workbench (formerly Visibility Data Workbench), a free interactive tool for encoding and decoding EPCIS data and interacting with EPCIS repositories
December 20, 2023
epcis, this, article, relies, excessively, references, primary, sources, please, improve, this, article, adding, secondary, tertiary, sources, find, sources, news, newspapers, books, scholar, jstor, october, 2022, learn, when, remove, this, template, message, . This article relies excessively on references to primary sources Please improve this article by adding secondary or tertiary sources Find sources EPCIS news newspapers books scholar JSTOR October 2022 Learn how and when to remove this template message Electronic Product Code Information Services EPCIS is a global GS1 Standard for creating and sharing visibility event data both within and across enterprises to enable users to gain a shared view of physical or digital objects within a relevant business context 1 Objects in the context of EPCIS typically refers to physical objects that are handled in physical 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 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 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 However 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 1 EPCIS 1 0 was first ratified in April 2007 2 At the time of ratification over 30 companies had used the draft EPCIS standard to exchange data and collaborate with trading partners 3 As of 2014 24 commercial products had received certificates of compliance to the EPCIS standard from GS1 4 EPCIS 1 1 was ratified by GS1 in May 2014 5 EPCIS 1 2 was ratified by GS1 in conjunction with CBV 1 2 in September 2016 History editIn 2001 the MIT Auto ID Center published a paper proposing the Physical markup language PML intended as a common language for describing physical objects processes and environments 6 PML was one of four components of an intelligent infrastructure envisioned by the Auto ID Center the other three components being RFID tags the Electronic Product Code and the Object Naming Service As the work of the MIT Auto ID Center was taken up by EPCglobal in 2004 the PML concept was renamed Electronic Product Code Information Services EPCIS and efforts began to create a global standard In 2005 the first version of the EPCglobal Architecture Framework was published which introduced EPCIS as a standard under development and showed how it related to other components of an envisioned architecture for RFID based tracking of physical objects within supply chains 7 EPCIS 1 0 was first ratified in April 2007 2 A companion standard the EPC Core Business Vocabulary 1 0 was ratified by EPCglobal in October 2010 8 Despite the RFID oriented origins of EPCIS it came to be used in applications that used bar codes exclusively or bar codes in combination with RFID tags 9 EPCIS 1 1 and CBV 1 1 were ratified in May 2014 5 New features in EPCIS 1 1 include support for class level identification needed especially in bar code applications a new event type to describe processes where inputs are transformed into outputs and additional event data to describe business transfers and instance or lot level master data 10 EPCIS 1 2 and CBV 1 2 were ratified in September 2016 New features include a mechanism to declare a previous event as being erroneous and a mechanism for including master data into the EPCIS document header 11 References edit a b EPCIS 1 2 p 9 a b Roberti Mark The EPCIS Standard in Perspective RFID Journal April 2007 Meranda Mike The Ratification of EPCIS RFID Journal April 2007 GS1 EPCglobal Software Certification Program retrieved 26 October 2014 a b Beth Bacheldor RFID News Roundup RFID Journal 29 May 2014 Brock D L The Physical Markup Language A Universal Language for Physical Objects MIT Auto ID Center Whitepaper MIT AUTOID WH 003 February 2001 Traub K et al The EPCglobal Architecture Framework July 2005 EPCglobal Core Business Vocabulary Standard EPCglobal Standard October 2010 GS1 RFID Bar Code Interoperability GS1 Guideline August 2012 EPCIS 1 1 p 3 EPCIS 1 2 p 4External links editEPCIS and EPC Core Business Vocabulary standard page at GS1 EPCIS standard version 1 2 GS1 Version 1 2 September 2016 CBV standard version 1 2 2 EPCIS and CBVImplementation Guideline EPCIS Workbench formerly Visibility Data Workbench a free interactive tool for encoding and decoding EPCIS data and interacting with EPCIS repositories Retrieved from https en wikipedia org w index php title EPCIS amp oldid 1178979528, wikipedia, wiki, book, books, library,
