Jeremy Morton GS1 Sweden

Agenda GS1 EDI changes the way you do business EDI – it’s been around for ages EDIFACT Syntax Messages, transactions, processes, scenarios GS1’s role and deliverables Where are we heading? EDI/BizTalk

GS who? 1970 – UCC – Uniform code council North America 1975 – EAN – European article numbering Europe Many names – CCG, ANA, AECOC, INDICOD, … 1980 – EAN International Global Even more names – Uniscan, HKAna, SANC, 2000 – EAN + UCC = EAN.UCC Two cultures Two systems Two boards 2005 – GS1 “One world; One name; One global language of business” > 100+ countries; > staff; > 1.3 million registered users

Information carriers Identification Electronic commerce The GS1System GS1 system EAN13EAN8 ITF14 EAN128 Databar RFID/EPC EANCOMXML GTIN Article number GLN Location number SSCC Package number GRAI RTI number GPC Product classification GSRN Relation number GIAI Asset identifier

Stock Control Order Order Processing Production Confirmation Delivery Invoicing Payment Credit A typical business situation

Stock Control Order Order Processing Production Delivery Payment Credit Order Response What EDI wants to achieve

Business relationship Business transactions Information EDI CustomerSupplier

Components of e-business Business relationship Based on personal contact Expressed as an agreement (prices, delivery terms) Business transactions Order, Invoice, Price list, etc. Information By mail, fax, telephone, …

Business transactions rarely come alone a payment refers to an invoice which refers to a delivery advice which refers to an order confirmation which refers to an order which refers to a price list which..... The same information is involved from ”cradle to grave” Scenarios

10 SupplierBuyer Pricelist Calloff Payment Confirmation Despatch advice Invoice

11 Order-specific Custom items Critical for reconciliation Pull or push Linked to product data SupplierBuyer Pricelist

12 Starts the supply process Unambiguous item numbers Unambiguous locations Unambiguous quantities Agreed prices SupplierBuyer Calloff

13 Yes/No/Maybe What When How many Substitution SupplierBuyer Confirmation

14 What When Where How many Package identification Transport information SupplierBuyer Despatch advice

15 Simple Correct Timely SupplierBuyer Invoice

16 Simple Correct Timely SupplierBuyer Payment

17 Supplier Buyer Messaging Network Business Application EDI system Communi- cation

Goals of EDI To get essential data into your business partner’s computer system without manual intervention of e-Business To improve and simplify a business relationship using EDI

EDI – as old as computers EDIFACTANSI X.12Proprietary (US)GTDI Proprietary (Europe) UN/EDIFACT 1960’s1970’s EDI/BizTalk

EDI syntax – what really happened EDIFACT ANSI X.12 Proprietary (US) GTDI Proprietary (Europe) UN/EDIFACTUN/CEFACT EDI/BizTalk TRADACOMS (UK) XML/EDI

Goal of EDI To get structured data from the sender’s system to the receiver’s system Timely Reliably Unambiguously EDI/BizTalk21

Structured data - 1 “Line number”, “Item number”, “Quantity” 1, 1234, 99 2, 5678, 50 … All records the same EDI/BizTalk22

Structured data - 2 HEAD ONUM ABC123 DATE LINE 1 ITEM 1234 QUAN 99 LINE 2 ITEM 5678 QUAN 50 DONE EDI/BizTalk23 This method was used extensively in early EDI. It is flexible, but takes a lot of space (2400 bits/s was fast in those days!)

Structured data - 3 ABC EDI/BizTalk24 This is where we are heading. It is flexible, but takes even more space (1 Mbit/s is slow today)

Structured data - 4 The EDIFACT (and X.12) compromise BGM+220+ABC123’ DTM+4: :102’ LIN :MF’ QTY+21:99’ LIN :MF’ QTY+21:50’ EDI/BizTalk25 Flexible and compact But unreadable!

EDIFACT syntax (simplified) BGM+220+ABC123’ DTM+4: :102’ LIN :MF’ QTY+21:99’ LIN :MF’ QTY+21:50’ EDI/BizTalk 26 A segment A simple data element A composite data element A component data element Segment tag Separators CODES

EDIFACT messages UNH+9876+ORDERS:D:97A:UN:EAN007’ BGM+220+ABC123’ DTM+4: :102’ LIN :MF’ QTY+21:99’ LIN :MF’ QTY+21:50’ UNT ’ EDI/BizTalk27 Header segment Trailer segment

EDIFACT messages UNH+9876+ORDERS:D:97A:UN:EAN007’ First there was INVOIC Today there are dozens of UNSMs They are too complicated to use directly So subsets are used EDI/BizTalk28 Message number Message type UNSM Catalogue ID Implementation subset

EDIFACT interchanges UNB+UNOC:3+FROMME+TOYOU :1200+REF123’ UNH+9876+ORDERS:D:97A:UN:EAN007’ … UNT ’ UNZ+1+REF123’ EDI/BizTalk29 Interchange header Interchange trailer

EDIFACT syntax summary An Interchange consists of one or more Messages which are made up of Segments with a Tag and one or more Simple data elements or Composite data elements with Component data elements all kept in place with Separators and full of Codes EDI/BizTalk30

The Tower of Babel EDIFACT One language Many dialects UN/EDIFACT One standard Many interpretations

GS1’s role For e-Business to work we need to agree Scenarios Transactions Information Semantics Documents Communication …

GS1’s role GS1 has developed Standard identifiers (items, places, shipments, …) Standard scenarios (FMCG, Public procurement, …) Standard semantics (Global Data Dictionary) Standard EDIFACT subset (EANCOM) Standard XML messages …

Plug-and-pray So what’s the hold-up? EDI standards work between actors But for e-Business to work, the data and processes have to be well-organized inside the firewall That’s where integration software helps EDI/BizTalk34

Conclusion EDI is a comparatively simple IT exercise it gets rid of paper and makes the information flow more efficient e-Business is a management technique that still really has not caught on but only e-Business will bring dividends

A few links Me: GS1 Sweden: Implementation guides (in Swedish): GS1 International: EANCOM: UN/CEFACT: GEFEG: EDI/BizTalk36