Introduction to GS1 Standards - GS1 | The Global Language ... · Work in progress or planned Work...

Introduction to GS1 Standards

GS1 Healthcare Conference, GS1 Healthcare Conference,

28 October 2008

GS1 System of Standards

© 2008 GS1

Roadmap towards Global Standards

200920082007

Packaging/

Direct MarkingCarrier

AIDC Application Standards (Ph1)

AutoID Data

Serialisation

GTIN Allocation

Schedule for deliverables to the GS1 Global Standards Management Process

– approx. 6 months needed for final standard approval

© 2008 GS13

Version 1.8 – September 2008

Work in progress or planned Work finalised or near closure

Traceability

Data Synchronisation & Classification



Review GTS

Implement. Guide

Pilot

Attribute Gap Analysis

Pilot Strategy (GDSN-GPC)

Healthcare Extension

Long Term ClassificationInventory Classif systems

GS1 Identification Keys and GS1 BarCodes

28 October 200828 October 2008

Scott Gray

10 Things You Should KnowAbout GS1 Automatic Identification

1. GS1 Dumb vs. GS1 Smart

2. What’s in a Number

6. Attributes (extra info)

7. Validation Rules

© 2008 GS15

3. What Keys

4. Key Messages

5. Key Rules

8. Symbol Types

9. How it fits together

10. Where to find more information

GS1 Dumb Versus GS1 Smart

GS1 Identification Numbers (Keys) are Dumb

Nice Guys, but Dumb

© 2008 GS16

GDSN, GS1 eCom, EPCIS are Smart

Guys with the answers

What’s In a Number?

1. Who Governs the Number’s Meaning (GS1 or other “Issuing Agency” per ISO)

2. What data is about to be read (is it a trade item number, a date, a location, other?)

© 2008 GS17

item number, a date, a location, other?)

3. What is the number and what does it point to (item catalog file, Despatch Advice)

GS1 “Keys”

Serial Shipping Container Codes (SSCC)Individual Logistics Units

Global Returnable Asset Identifier (GRAI)Returnable Assets

Global Location Numbers (GLNs) forLegal or Functional Entities and Locations

Global Trade Item Number (GTIN)Products or Services

© 2008 GS18

Global Service Relation Number (GSRN)Recipient of services

Returnable Assets

Global Individual Asset Identifier (GIAI)Fixed Assets

Global Shipment Identification Number (GSIN)Multiple Logistic Units for Trade (Shipper Assigned)

Global Identification Number for Consignment (GINC)Multiple Logistic Units for Transport (Transport Company Assigned)

Global Document Type Identifier (GSRN)Document Type

Keys to Messages

Despatch AdviceSSCC

GTIN

Item CatalogSynch

GTIN

© 2008 GS19

SSCC

AdviceSSCC

GLN

PartySynch

GLN

GTINGLN

Order,Invoice,Payment

GTINGLN

Key “Allocation” Rules

© 2008 GS110

http://www.gs1.org/gtinrules/

Keys & Key Attributes

Lot # for Production Batch

GTIN toIdentify the Brand

Other Attributes

• Trade Item Measures• Logistic Unit Measures• Dates

© 2008 GS111

Batch

Serial # forProduction Unit (Instance)

• Dates

GS1 General SpecificationsHas complete list of 100+GS1 Application Identifiers

Automatic IdentificationValidation Rules

GTIN + Serial Number

SSCC +Logistics Measure

Some know how to pull it together

© 2008 GS112

GTIN A + GTIN BOn Product A

GTIN A OnProduct A andProduct B

Some find itmore of a challenge

GS1 BarCodes: Approved Options

EAN/UPC

GS1 DataBar

GS1-128

© 2008 GS113

CompositeComponent

ITF-14

GS1DataMatrix

GS1 BarCodes Approved forRetail Point-of-Sale Trade Items

EAN/UPC

GS1 DataBar (in 2010)

GS1-128

© 2008 GS114

CompositeComponent

ITF-14

GS1DataMatrix

GS1 BarCodes That Carry Keys + Additional Data

EAN/UPC

GS1 DataBar (expanded)

Composite

© 2008 GS115

CompositeComponent

(not Key)

ITF-14

GS1DataMatrix

GS1 BarCodesDirect Marking

EAN/UPC

GS1 DataBar

GS1-128

© 2008 GS116

CompositeComponent

ITF-14 (Cartons)

GS1DataMatrix

(Parts)

GS1 BarCodesUsed in Healthcare

EAN/UPC

GS1 DataBar

© 2008 GS117

CompositeComponent

ITF-14

GS1DataMatrix

Basic Information Flow Model

As trading begins, trading partners exchange information on four basic information flow

transaction areas: purchasing, delivery, invoicing, and payment.

Trading Partner A

Trading Partner B

© 2008 GS118

Purchase Deliver Invoice Pay

Basic Physical Flow Model

When movement of goods begins, trading partners repeat four basic physical flow

transaction areas: receiving, replenishment, processing, and shipping.

Trading Partner A

Trading Partner B

© 2008 GS119

Receive Replenish Process Ship

Event: Purchasing

Information and physical flows combine as orders are exchanged

using GS1 standard identifiers like the Global Trade Item Number (GTIN) or

Global Location Number (GLN).


Trading Partner A

Trading Partner B

© 2008 GS120

Receive Replenish Process Ship Receive Replenish Process Ship

GTINGLN

Event: Replenishment

As they receive raw materials or finished goods, companies

replenish their inventory levels and plan production.


Trading Partner A

Trading Partner B

© 2008 GS121


GTINGLN

Event: Processing

Next the company processes the inventory in some way. This means different things

depending on the situation (manufacturing, assembly, packaging, or storage).


Trading Partner A

Trading Partner B

© 2008 GS122


GTINGLN

Event: Shipping Notice

After processing is completed, the company readies the order for shipment and sends a message called a Despatch Advice to alert

their customer the goods will soon arrive.


Trading Partner A

Trading Partner B

© 2008 GS123


SSCCGTINGLN

GTINGLN

Event: Shipping

During shipping, the company marks the logistics unit with a label that has the Serialized Shipping Container

Code (SSCC) identifier in a bar code.


Trading Partner A

Trading Partner B

© 2008 GS124

SSCCGTINGLN

GTINGLN


SSCC

Event: Shipment Receiving


Receiving is automated by using the logistics unit identifier, SSCC, to unlock

the shipment content information (GTINs contained) in the Despatch Advice.

Trading Partner A

Trading Partner B

© 2008 GS125

SSCCGTINGLN

GTINGLN

SSCC SSCCGTINGLN


SSCC

Event: Invoicing

Upon receipt of the goods, a request for payment or invoicing occurs.

Trading Partner A

Trading Partner B


© 2008 GS126

SSCCGTINGLN

GTINGLN

SSCC SSCCGTINGLN


GTINGLN

Event: Payment


Upon receipt of the invoice, paymentoccurs according to terms. This

concludes the basic order to payment cycle between two companies.

Trading Partner A

Trading Partner B

© 2008 GS127

SSCCGTINGLN

GTINGLN

SSCC SSCCGTINGLN


GTINGLN

Introduction to EPCglobal

28 October 2008Peter J. Alvarez

Topics

RFID Basics

Tangible Results/Case Studies

© 2008 GS1 29

Basic RFID System

© 2008 GS1 30

Reader

Module

Antenna TagHost

Four main ‘globally established’ frequencies on which RFID operates

Key RFID Frequencies

© 2008 GS1 31

• Low Frequency (LF): 125 - 132 kHz

• High Frequency (HF): 13.56 MHz – Expected: EPC Gen2, by end of 2008

• Ultra High Frequency (UHF): 850 - 950 MHz– EPC Gen2 - today

• Microwave .2.4 GHz

Transponder Layout

© 2008 GS1 32

Inlay Microchip Antenna

Benefits of RFID

– Non-line of sight

– Range

– Bulk read - Speed

– 0HIO

– Zero Human

© 2008 GS1 33

– Zero Human Involvement Operations

– Durability

– Read/Write

– Visibility into the movement of physical objects in the supply chain at new levels

AutomationIntegration of physical and computer worlds

Benefits of RFID


– Range

– Bulk read - Speed– 0HIO

© 2008 GS1 34

– 0HIO


– Durability

– Read/Write


Benefits of RFIDNon-line of sight, Range, Bulk read - Speed

© 2008 GS135

Benefits of RFID


– Range

– Bulk read - Speed

– 0HIO

– Zero Human

© 2008 GS1 36


– Durability

– Read/Write


Benefits of RFIDZero Human Involvement Operations

© 2008 GS137

Benefits of RFIDZero Human Involvement Operations

© 2008 GS138

Data management:What’s new with RFID

New types of information• EPC/RFID event related, sensor data

More detailed location information• Locations within companies

More items tracked

© 2008 GS1

More items tracked• Not just pallets

More frequent information collection• Many times per day

Information shared with multiple partners (EPCIS)• Logistics, distributors, suppliers

EPCglobal

Unique ID for objects - serialised• Electronic Product Code (EPC)

Automated reading and tracking of physical events• RFID (bar codes in some circumstances)

© 2008 GS1

Physical activity automatically updates computer systems• Accurate, detailed, real time

Computer systems accurately reflect the real world• Improved control

• Lower costs, better quality, improved service

Overview

About EPCglobal

Tangible Results/Case Studies

`

© 2008 GS1 41

Tangible Examples

• Electronic proof of delivery

– Avoiding waste of resources.

– EPC data was able to refute received amount 80% of occasions

• Department of Defense

– Reduced order backlog from 92k to 11k orders

© 2008 GS1 42

– Reduced order backlog from 92k to 11k orders

– $1.7bn ROI over 7 years

– Improving “confidence” in the supply chain

• Baggage tracking

– Improving control and accuracy

– 99% read rate helping to solve a $1.6bn problem

(Significant transport and logistics project now starting)

Tangible Examples

• Apparel

– Improving customer availability

– 20% improvement in accuracy (size and colours)

• Prompt movement of promotional items to sales floor

© 2008 GS1 43

– Retailer 19% sales lift

– Supplier 26% sales increase

Data Synchronisation and Classification in Healthcare

Peter Alvarez

28 October 2008

Work Team UpdateWork Team Update

Managing data in the Healthcare supply chain

Manufacturer Distributor, wholesaler, GPO, …

PatientHealthcare provider

Transport provider

© 2008 GS146

wholesaler, GPO, … provider

Unit Case Pallet UnitCasePallet

Inaccurate or bad data at many points in the supply chain

�No standardised location and product identification / information

�Inadequate infrastructure to share data among supply chain partners

Roadmap towards Global Standards

200920082007

Packaging/

Direct MarkingCarrier


AutoID Data

Serialisation

GTIN Allocation


– approx. 6 months needed for final standard approval

© 2008 GS147

Version 1.8 – September 2008

Work in progress or planned Work finalised or near closure

Traceability

Data Synchronisation & Classification



Review GTS

Implement. Guide

Pilot

Attribute Gap Analysis

Pilot Strategy (GDSN-GPC)

Healthcare Extension

Long Term ClassificationInventory Classif systems

Global Data Synchronisation & Product Classification

Objective: Develop a data synchronisation standard, including a classification solution, which will allow the Healthcare industry to use the GS1 GDSN (Global Data Synchronisation Network)

Completed:

• GDSN gap analysis (228 data requirements are supported by the current GDSN standard - 27

Next steps:

• Completed global GDSN healthcare pilot (June

08)

© 2008 GS1

the current GDSN standard - 27 new requirements need to be defined and added to the GDSN standard)

• Inventory of classification systems in use across the world (approximately 35 different classification and nomenclature systems in use in various parts of the world)

• Strategy (data synchronisation & product classification) for global GDSN pilot

• Create GDSN Extension for Healthcare (Q2

‘09): Combine new attributes and the existing 228 data requirements, add healthcare specific business rules and validations

• Develop long term recommendation for product classification (June‘09)

Tokyo Meeting Objectives and Topics for the week

• Work progress overview: Data Sync and Classification

• GDSN pilot overview

• GSMP Healthcare GDSN Extension BRAD review and

© 2008 GS1

• GSMP Healthcare GDSN Extension BRAD review and input

• Overview of Classification Project plan – Phase 2

• Classification Inventory update and input

• Solution Provider Information Session

49

Week-at-a-Glance

TUESDAY WEDNESDAY THURSDAY

9:00 - 10:00

9:00 - 10:00Training Session: Introduction

to GS1 Standardsand the GSMP 9:00 - 12:50

Plenary SessionOpen to all

Open10:00 - 11:0010:00 - 10:15Coffee Break

11:00 - 12:0010:15 - 12:30

Welcome, Opening and

© 2008 GS150

Plenary SessionOpen to all

12:00 - 13:00

13:00 - 14:00 LUNCH LUNCH LUNCH

14:00 - 15:00

14:00 - 18:00Data Sync and Classification

Joint Working Session

14:00 - 17:00Data Sync and Classification

Joint Working Session, continued

14:00 - 17:30Plenary Session

Open to all

15:00 - 16:00

16:00 - 17:00

17:00 - 18:0017:00 - 18:00

Solution Provider Session

18:30 +Networking Dinner

Synchronising data in HealthcareGS1 GDSN

Global Data Synchronisation NetworkGlobal Data Synchronisation Network

The Global Data Synchronisation Network

GS1 GDSN

Global Data Synchronisation Network

Global Registry Data

Pool

© 2008 GS152

RegistryPool

Data Pool

Data Pool

Manufacturer

Distributor/Wholesaler/GPO

Healthcare Provider

A global network

•GDSN Data Pool•GDSN-Certified

•Electronic catalogues of standardised master data

•Ensure the confidentiality

•GS1 Global Registry•GDSN's "information directory“

•Details who has subscribed to trade item or party data

© 2008 GS1

•Ensure the confidentiality and integrity of user information

•Are fully interoperable

to trade item or party data

•Guarantees the uniqueness of the registered productsand organisation

53

How GDSN works

1. Load Data

The seller registers product and company information in its data pool

2. Register Data

A small subset of this data is sent to the GS1 Global Registry

3. Request Subscription

Source internal database

Source datapool

1

2 3

© 2008 GS154

The buyer, through its own data pool, subscribes to receive a seller's information

4. Publish Data

The seller’s data pool publishes the requested information to the buyer’s data pool

5. Confirm & Inform

The buyer sends a confirmation to the seller via each company's data pool, which informs the supplier of the action taken by the retailer using the information

GS1

Global Registry

Recipient datapool

Recipient internal database

3

4

Additional eCollaboration Activities

GDSN foundational for eCollaboration

© 2008 GS1

Foundation for eCollaboration

Source: AT Kearney

GDSN data attributes

Mandatory and optional attributes supported in GDSN

Overview – GDSN Attributes

This section provides a basic overview of the mandatory attributes required by the Global Data Synchronisation Network (GDSN).

© 2008 GS1

These attributes are required regardless of the sector or product for which data is being synchronised.

57

Overview - continuedGDSN Mandatory Attributes

There are 24 Mandatory Attributes Required to Operate in the GDSN

The first 7 attributes are required to register products in the GS1 Global Registry

© 2008 GS1

the GS1 Global Registry• Target Market Sub-division is optional

The other 17 attributes are required to exchange data across the network (within one date pool or across two or

more data pools)

• Of these 17 attributes, 10 require Yes/No responses related to the product

• The other 7 attributes require actual product related data

Mandatory attributesGS1 Global Registry

Mandatory attributes Description

1 GLN of source Data Pool The data pool that serves as the entry point into the GDSN and connection to other certified data pools.

2 GLN of data source Global Location Number of the source of the information published in the Global Registry. Typically the manufacturer.

3 GTIN The Global Trade Item Number of the product (drugs, medical device, non medical supply (e.g. light bulbs).

4 Target Market Country The country where the product is intended to be sold.

© 2008 GS1

4 Target Market Country Code

The country where the product is intended to be sold.

5 Target Market Subdivision Code(optional)

The code for country sub-division definition used to indicate the geo-political subdivision of the target market.

6 GPC The Global Product Classification is the GS1 classification system used in the Global Registry. The GPC identifies a category for the product (GTIN) registered.

7 State The status of the product registered.

The four states are: Registered , Cancelled, In Progress, and Discontinued.

8 Date May have a combination of the following dates: cancel, deletion, discontinued, last changed, or registration date.

60

Mandatory attributesGDSN


9 GLN of manufacturer Entity that provides the global data synchronization network with Master Data.

10 Hierarchy level per GS1 code list

Describes the hierarchical level of the trade item. TradeItemUnitIndicator is mandatory. Examples: "CASE" , ”PALLET”. For listing refer to Appendix A.

11 Brand name The recognizable name used by a brand owner to uniquely identify a line of trade item or services.

© 2008 GS1

line of trade item or services.

12 Description Describes use of the product or service by the consumer. Should help clarify the product classification associated with the GTIN.

13 Base Unit? (Y/N) An indicator identifying the trade item as the base unit level of the trade item hierarchy. This is y/n (Boolean) where y indicates the trade item is a base unit.

14 Consumer Unit? (Y/N) Identifies whether the current hierarchy level of a trade item is intended for a ultimate consumption. For retail, this trade item will be scanned at point of sale. At retail, this data is commonly used to select which GTINs should be used for shelf planning and for front end POS databases. This value reflects the intention of the Information Provider which may not necessarily be reflected by the retailer.

62



15 Despatch Unit? (Y/N) An indicator identifying that the information provider considers the trade item as a dispatch (shipping) unit. This may be relationship dependent based on channel of trade or other point to point agreement.

16 Invoice Unit? (Y/N) An indicator identifying that the information provider will include this trade item on their billing or invoice. This may be relationship dependent based on channel of trade or other point to point

© 2008 GS1

agreement.

17 Orderable Unit? (Y/N) An indicator identifying that the information provider considers this trade item to be at a hierarchy level where they will accept orders from customers. This may be different from what the information provider identifies as a despatch unit. This may be a relationship dependent based on channel of trade or other point to point agreement.

18 Variable Measure? (Y/N) Indicates that an article is not a fixed quantity, but that the quantity is variable. Can be weight, length, volume. trade item is used or traded in continuous rather than discrete quantities.

19 Returnable packaging? (Y/N)

Trade item has returnable packaging. Attribute applies to returnable packaging with or without deposit.

63



20 Batch/Lot Number? (Y/N) BatchNumber: Indication whether the base trade item is batch or lot number requested by law, not batch or lot number requested by law but batch or lot number allocated, or not batch or lot number allocated. A batch or lot number is a manufacturer assigned code used to identify a trade item's trade item on batch or lot. Differs from Serial Number which is a manufacturer assigned code during the trade item on cycle to identify a unique trade item.

© 2008 GS1

21 Non-sold item returnable? (Y/N)

Is NonSoldTrade Item Returnable: Indicates that the buyer can return the articles that are not sold. Used, for example; with magazines and bread. This is a y/n (Boolean) where y equals right of return. This is at least relevant to General Merchandise, Publishing industries and for some FMCG trade item.

22 Marked Recyclable? (Y/N) Is Trade Item Marked As Recyclable: Trade item has a recyclable indication marked on it. This may be a symbol from one of many regional agencies.

64



23 Height & UoM The measurement of the height of the trade item. The vertical dimension from the lowest extremity to the highest extremity, including packaging. At a pallet level the trade item Height will include the height of the pallet itself. Business Rules: Measurements are relative to how the customer normally views the trade item. Needs to be associated with a valid UoM.

24 Width & UoM The measurement from left to right of the trade item. Measurements

© 2008 GS1

24 Width & UoMare relative to how the customer normally views the trade item. Needs to be associated with a valid UoM.

25 Depth & UoM The measurement from front to back of the trade item. Measurements are relative to how the customer normally views the trade item. Needs to be associated with a valid UoM.

65

Summary

24 Mandatory Attributes Required to Operate in the GDSN

• 7 attributes are required by the GS1 Global Registry

• The other 17 attributes are required to exchange data

© 2008 GS1

• The other 17 attributes are required to exchange data across the network• 10 attributes require Yes/No responses related to the product for which

you are synchronising data

• 7 attributes require actual product related data

Traceability in Healthcare

28 October 2008Janice KiteJanice Kite

Topics

Traceability in GS1Traceability in Healthcare Work Team

• What have we achieved• What have we achieved• Where are we now• What is our focus at this conference• What next

Traceability in GS1

Global Traceability Standard (GTS)

When?

January 2006

Why?

Avoid development of conflicting traceability solutions across

© 2008 GS169

Avoid development of conflicting traceability solutions across technologies, sectors, applications…

Ensure consistency of GS1 Traceability guidelines

What?

It’s a PROCESS standard

Minimum requirements for traceability

Framework for sector specific traceability

Common definition of the traceability process

Topics

Traceability in GS1Traceability in Healthcare Work Team

• What have we achieved• What have we achieved• Where are we now• What is our focus at this conference• What next

Traceability in Healthcare Work Team

Co-Chairs and Facilitator

Frédérique FremontOrganisation Engineer Hospital: C.H.I Robert Ballanger, Aulnay-sous-Bois, France

Member of the GS1 Healthcare Leadership Team

© 2008 GS171

Tim MarshSenior Manager of Global Packaging Technology

Pfizer

Co-Chair, GS1 Healthcare Leadership Team

Janice KiteGlobal Project Manager, GS1 Traceability in Healthcare

GS1 Global Office

Traceability in Healthcare Work Team

What we have achieved

December 2007 – June 2008: Review of generic/sector agnostic versions of GS1 Global Traceability Standard (GTS):

Is it truly generic? (Was developed by FMCG members)

Does it meet the needs of healthcare?

© 2008 GS172

This work resulted in a Change Request (CR) to GTS – submitted into GSMP 24Jun08 (Ref. CR08/130)

Reviewed and edited this Draft GTS to make it Healthcare Specific

Changed FMCG/Food wording to healthcare wording

Changed FMCG/Food examples to healthcare examples

This work resulted in Change Request for GTS for Healthcare (GTSH) -submitted into GSMP 08Aug08 (Ref. CR08/201)

GSMP Traceability Work Group

• Objective: achieve approval of two CRs by end of 2008

• Meetings scheduled every 2nd and 4th Tuesday, 15:00-16:30 CET

© 2008 GS1

• Project Plan:

Public Review - 30 calendar days 24 September to 24 October

Comment resolution 14 to 28 October (dependent on the number

and/or complexity of comments received)

eBallot (open for at least 14 days) Earliest 29 October - 12 Nov

Motion to Progress 18th November

Posting December 2008

73

What now? In parallel to GSMP CRs approval activity

Phase 2: Developing Business Implementation Guidelines for Healthcare

Call to Action for this phase issued 08Aug08

Work team calls: Every 1st and 3rd Tuesday, 13:00-14:30 CET

Briefing webinars for Solutions Providers (every six weeks, Wednesday, 16:00-16:30 CET (started 24Sep08))

So far:

Gathered requirements for structure and content of draft Business Implementation

© 2008 GS174

Gathered requirements for structure and content of draft Business Implementation Guideline structure

Began drafting the content

What next?

Continuous review of written content on conference calls

Gather Healthcare traceability case study/best practice examples

Obtain work team approval of draft Healthcare Traceability Business Implementation Guideline

Submit to GSMP

ALL BEFORE THE END OF THIS CALENDAR YEAR!

Summary of where we are:

Healthcare

Phase 1: Standard Development


20092008

T

R

A

C

E

2010

CR for GTS (08/130)

CR for GTSH (08/201)

© 2008 GS175

Phase 2: Development Implementation

GuidelineHealthcare

Version 1.0 – July 2008

E

A

B

I

L

I

T

Y

GSMP Traceability Work Group

Work in GSMPWork in progress or planned Work finalised or near closure

Progress to approval

GTS V1.1 and

GTSH V1.0

GSMP Traceability Business Requirement Group (BRG)

Focus this week…

Continuing review and approval of Implementation Guideline contentcontent

Introduction to GS1 Standards - GS1 | The Global Language ... · Work in progress or planned Work...

Documents

Transcript of Introduction to GS1 Standards - GS1 | The Global Language ... · Work in progress or planned Work...