GS1 System Architecture Document
GS1 System Architecture DocumentHow GS1 standards fit togetherRelease 9.0, Approved, Feb 2020
GS1 System Architecture DocumentDocument SummaryDocument ItemCurrent ValueDocument NameGS1 System Architecture DocumentDocument DateFeb 2020Document Version9.0Document IssueDocument StatusApprovedDocument DescriptionHow GS1 standards fit togetherLog of ChangesReleaseDate of ChangeSummary of Change1.014 February 2012Initial release2.0February 2013Update based upon recent standard changes3.014 April 2014Update based upon recent standard changes4.0May 2015Applied new GS1 branding and clarifications in the classes of keys (section4.3) and approved following GSMP Community Review.5.0April 2016Updates based upon recent standard changes6.0Feb 2017Updates based upon recent standard changes7.0Feb 2018Updates based upon recent standard changes8.0Feb 2019Updates based upon recent standard changes9.0Feb 2020Major review based upon simplification effort, new GS1 services strategy &recent standard changes.DisclaimerTHIS DOCUMENT IS PROVIDED “AS IS” WITH NO WARRANTIES WHATSOEVER, INCLUDING ANY WARRANTY OFMERCHANTABILITY, NONINFRINGEMENT, FITNESS FOR PARTICULAR PURPOSE, OR ANY WARRANTY OTHER WISE ARISINGOUT OF THIS SPECIFICATION. GS1 disclaims all liability for any damages arising from use or misuse of this document,whether special, indirect, consequential, or compensatory damages, and including liability for infringement of anyintellectual property rights, relating to use of information in or reliance upon this document.GS1 retains the right to make changes to this document at any time, without notice. GS1 makes no warranty for the use ofthis document and assumes no responsibility for any errors which may appear in the document, nor does it make acommitment to update the information contained herein.GS1 and the GS1 logo are registered trademarks of GS1 AISBL.Release 9.0, Approved, Feb 2020 2020 GS1 AISBLPage 2 of 48
GS1 System Architecture DocumentTable of Contents1Introduction . 52Overview of the GS1 System Architecture . 5342.1The role of standards . 52.2Open value networks . 62.3GS1 standards: Identify, Capture, Share . 72.4Digital value networks . 10General considerations . 103.1Standards, guidelines, data services, solutions. 103.2GS1 System Architecture vs. End user system architecture . 123.3Scope of standards . 123.4Consistency across data standards – the Global Data Dictionary . 13Identify – GS1 identification keys . 134.14.1.1Entities . 134.1.2Attributes . 144.1.3Keys . 144.1.4Terms relating to construction of keys . 144.2GS1 identification keys, key qualifiers, and supplementary data . 154.3Classes of GS1 identification keys . 164.45Data modelling terms . 134.3.1Class 1 keys . 164.3.2Class 2 keys . 164.3.3Class 3 keys . 174.3.4Other keys . 174.3.5Summary. 17Identifier Syntax: Plain, GS1 element string, EPC URI, GS1 Digital Link URI . 18Capture – Physical data carriers and data capture infrastructure . 195.15.2Data capture architecture . 19Data carrier independence of data . 205.2.16Different types of GS1 data carriers . 215.3Translation of data during physical data capture . 225.4Data capture infrastructure standards . 235.4.1Barcode data capture infrastructure standards. 235.4.2RFID data capture infrastructure standards . 23Share – Business data and communication . 246.1Content of standardised business data . 256.1.1Master data. 256.1.2Transaction data . 276.1.3Visibility event data. 276.2Communication of business data . 286.3Data and service discovery . 296.3.1Originator Party Service Lookup. 306.3.2Identifier Resolution . 30Release 9.0, Approved, Feb 2020 2020 GS1 AISBLPage 3 of 48
GS1 System Architecture Document6.3.37Data Discovery . 306.4Worldwide federation . 306.5Layering of interface standards – Content vs. Syntax vs. Transport . 31GS1 Services . 327.1Functional scope of GS1 services. 327.2Current GS1 data services . 337.37.2.1GEPIR . 337.2.2GDSN . 33GS1 data services strategy . 338Glossary. 34ASummary of GS1 standards: Identify, Capture & Share . 38A.1Identify . 38A.2Capture . 40A.3BA.2.1Barcodes - Linear. 40A.2.2Barcodes – 2D . 41A.2.3RFID . 42Share . 44Summary of GS1 application standards & solutions . 48Release 9.0, Approved, Feb 2020 2020 GS1 AISBLPage 4 of 48
GS1 System Architecture Document1IntroductionThis document defines and describes the architecture of the GS1 system of standards. The GS1system is the collection of standards, guidelines, solutions, and services created by the GS1community.The primary audience for the GS1 System Architecture includes end users, solution providers, GS1Member Organisations, and others engaged in the definition and implementation of the GS1 system.This document has several aims: To introduce each of the components that are part of the GS1 system and to show how they arerelated. It also shows the relation between GS1 standard components and standards publishedby other organisations such as ISO, UN/CEFACT or W3C. To explain the underlying technical foundations that guide the design of individual standards andservice components within the GS1 system. To provide architectural guidance to end users and solution providers who want to use the GS1system and to set expectations as to how these elements function.Other resources provide the technical details required to implement the GS1 system. Specifically: Individual data, software and hardware interfaces, as well as their use in open value networkapplications. These interfaces are defined by GS1 standards developed by the GS1 Communitythrough the Global Standards Management Process (GSMP). Hardware and software components that implement GS1 standards. Implementers are free toinnovate in the design of components, so long as they implement the interface betweencomponents in accordance with GS1 Standards. GS1 Data Services that are operated and deployed by GS1 itself, by other organisations towhich GS1 delegates responsibility or by third parties.Many parts of the GS1 system are well-established and covered by GS1 standards. Other parts ofthe GS1 system are evolving to meet needs that are determined by industry-prioritised use cases.For those elements of the system that are evolving, architectural analysis may be underway withinthe GS1 Architecture Group for the purpose of ensuring that the GS1 system remains cohesive.This document identifies which parts of the GS1 system are well-established architecturally andwhich parts are expected in the near future.2Overview of the GS1 System Architecture2.1The role of standardsThe GS1 system is based on globally unique identification and digital information. GS1 standardshave the following objectives: To facilitate interoperability in open value networksParties exchanging information must have agreement on the structure, meaning and mechanismof data exchange. The GS1 system includes standards for physical data carriers (i.e., barcodesand RFID tags), data standards (e.g. application identifiers) and information exchange standards(e.g. Electronic Data Interchange). To foster the existence of a competitive marketplace for interoperable system componentsGS1 standards define interfaces between system components that may be produced by differentvendors or by different organisations’ in-house development teams. This enables choice andleads to economies of scale that reduces costs for end users. To encourage innovationGS1 standards define interfaces. Interface standards ensure interoperability between competingsystems. By building upon a standard foundation, implementers can have greater confidence inRelease 9.0, Approved, Feb 2020 2020 GS1 AISBLPage 5 of 48
GS1 System Architecture Documentthe eventual adoption of their products and systems and, therefore, increased confidence toinvest in innovation.GS1’s structure and processes enable it to engage a community of users who collaborate to developstandards and specifications based on business use cases and scenarios. The developments aredone in line with the GS1 architecture principles, which ensures consistency and integrity in the GS1system of standards. As the community of users grows, the benefits to each user multiply.2.2Open value networksA value network is a set of parties who are involved in business relationships with one another. Inmany cases, value networks are concerned with the trade of physical objects such as products,parts, raw materials or digital objects such as music downloads, video-on-demand, data services,and so on.An open value network is one where the complete set of trading partners is not known in advanceand changes over time and where, to a certain degree, trading partners are interchangeable. Thishas great significance for the architecture and design of information systems. Interfaces betweendifferent system components form the basis of interoperability. In a value network, the mostimportant interfaces are those that exist between different organisations.Open value networks need standards-based interfaces. However, standards-based interfaces aregenerally a good approach for closed value networks as well because they may extend over timeand involve parties that were not involved initially.Figure 2-1 Open value networkA and E have no direct trading relationship.Nevertheless, they share an interface becauseA applies a data carrier that E must readParty AParty BParty EThe A-B and C-D relationships start out asindependent, but become co-dependent when Astarts trading with D and C starts trading with BParty DParty C established trading relationship new trading relationshipThe open nature of value network interfaces manifests itself in two ways, as illustrated in the abovefigure.Firstly, an interface may exist between two companies that do not have a direct businessrelationship. For example, a manufacturer may mark a product with machine-readable data in abarcode, the product may then be sold to retailers through distributors. In this case, the barcodecan be read by all retailers who receive the product (because of the use of a common standard). Inthis example, the barcode is an interface between the manufacturer and the retailers, but themanufacturer’s only direct business relationship is with their distributors.Release 9.0, Approved, Feb 2020 2020 GS1 AISBLPage 6 of 48
GS1 System Architecture DocumentSecondly, a company may find over time that it needs to extend an existing interface tocommunicate data to new companies. For example, suppose that Companies A and B are in atrading relationship and utilise an electronic interface for exchanging purchase order and invoicinginformation. Companies C and D are in a similar relationship. Sometime later, Company A may findthat it needs to trade with Company D, and likewise C may find that it needs to trade with B. Thefact that all four companies already use common data interface standards enables Company A touse the identical interfaces and supporting information systems to trade with D as it does to tradewith B, and likewise for C as it trades with B and D.To ensure that standards are broadly adopted, interface definitions need to be negotiated andimplemented outside the context of any trading relationship. Then, they need to be adhered to byall parties to ensure interoperability. For a standard to be adopted broadly, it must enableinteroperability and be maximally applicable to a broad range of business contexts. These areprecisely the foundation that underlie GS1 standards.2.3GS1 standards: Identify, Capture, ShareGS1 standards support the information needs of end users that interact with each other in valuenetworks. The subjects of such information are the entities that are part of those businessprocesses. Entities include things traded between companies, such as products, raw materials,packaging, and so on; equipment needed to carry out the business processes such as containers,transport, machinery; physical locations where business processes are carried out; legal entitiessuch as companies; service relationships; business transactions and documents; and others.Entities may exist in the physical world (such entities are generically called physical objects in thisdocument) or may be digital or conceptual. Examples of physical objects include a consumerelectronics product, a transport container, and a manufacturing site (location entity). Examples ofdigital objects include an electronic music download, an eBook, and an electronic coupon. Examplesof conceptual entities include a trade item class, a product category and a legal entity.GS1 standards may be divided into the following groups, according to their role in supportinginformation needs related to entities in value network business processes: Identification Standards: These provide the means to Identify entities so that electronicinformation may be stored and/or communicated about them among end users. GS1identification keys and key qualifiers may be used by an information system to referunambiguously to an entity such as a trade item, logistics unit, physical location, document orservice relationship. Capture Standards: These provide the means to automatically Capture data that is carrieddirectly on physical objects, bridging the world of physical things and the world of electronicinformation. GS1 data capture standards currently include specifications for barcode and radiofrequency identification (RFID) data carriers. Capture standards also specify consistentinterfaces to readers, printers, and other hardware and software components that read thecontent of data carriers and connect this data to relevant business applications. The industryterm Automatic Identification and Data Capture (AIDC) is sometimes used to refer to thestandards in this group, though in the GS1 System Architecture a clear distinction is maintainedbetween identification and data capture because not all identification is automated and not alldata capture is identification. Share Standards: These standards provide the means to Share information, both betweenorganisations and internally, providing the foundation for electronic business transactions,electronic visibility of the physical and digital world, and other applications. GS1 standards forinformation sharing include standards for master data, business transaction data, and visibilityevent data, as well as communication standards for sharing this data between applications andtrading partners. Other information sharing standards include discovery standards, which helplocate where relevant data resides across a network.While GS1 standards may be used in any combination, the “Identify, Capture, Share” paradigm ispervasive in situations where GS1 standards apply, and most business applications employ GS1standards from all three groups.For example, consider the business processes that support the retail sale of consumer goods. GS1standards are commonly used as follows:Release 9.0, Approved, Feb 2020 2020 GS1 AISBLPage 7 of 48
GS1 Syste
To explain the underlying technical foundations that guide the design of individual standards and service components within the GS1 system. To provide architectural guidance to end users and solution providers who want to use the GS1 system a
Foodstuffs GS1 NPC Supplier Guidelines Version 2.2 Page 4 of 28 GS1 PRODUCTFLOW / NPC PROCESSES As a supplier to Foodstuffs you will need to: Register for GS1 ProductFlow and work with GS1 to achieve GS1 Product Flow Certified status. Foodstuffs will then "activate" your company in the Foodstuffs eXchange to be a ProductFlow user.
healthcare industry through local support initiatives like GS1 Healthcare US in the United States. About GS1 Healthcare US GS1 Healthcare US is an industry group that focuses on driving the adoption and implementation of GS1 Standards in the healthcare industry in the United States to help improve patient safety and supply chain efficiency.
industry through local support initiatives like GS1 Healthcare US in the United States. ABOUT GS1 HEALTHCARE US GS1 Healthcare US is an industry group that focuses on driving the adoption and implementation of GS1 Standards in the healthcare industry in the United States to improve patient safety and supply chain efficiency.
GS1 , under its IP Policy, seeks to avoid uncertainty regarding intellectual property claims by requiring the participants in the Work Group that developed this GS1 AIDC Fresh Foods Sold at Point -of-Sale Implementation Guideline to agree to grant to GS1 members a royalty-free licence or a RAND licence to Necessary Claims, as that term is defined in the GS1
4. GS1 2D Data matrix The 2D Data Matrix should be in accordance with the GS1 guideline [2], ISO/IEC 15415 [10] & ANSI x3.182 [12]. 5. GS1 1D Barcode If applied, the 1D barcode should be displayed below the 2D Data matrix. The bar code should be in accordance with GS1 specification [1], ANSI X3.182 [12] & ISO/IEC 15416 [11]. 6.
Introduction The GS1 System is the most widely used supply chain standards system in the world and comprises the standards, guidelines, solutions and services created in formalised and collaborative processes. . GS1 identification standards, known as GS1 Identification Keys, bring value by permitting secure and portable identification across .
international standard upon which individual GS1 Member Organizations can develop user documentation. Electronic Data Interchange The use of Electronic Data Interchange (EDI) is an integral part of the GS1 System philosophy. Full details on the EDI standards are contained in EANCOM and GS1 XML. EANCOM is an implementation guideline of the
John Terwilliger Abbott John Pearce Axicon Auto ID Ltd John Ryu GS1 Global Office Jonas Buskenfried GS1 Sweden Kai Hachmann Edeka Zentrale AG & Co. KG Karen Arkesteyn GS1 Belgium & Luxembourg . Work request 18-260 Logistic Label placement: Work request 18-270 2D without 1D for Healthcare
