GS1 Industry & Standards Event 26-30 September 2011 Cologne, Germany Creating value together with global standards

1. GS1 Industry & Standards Event26-30 September 2011 Cologne, GermanyCreating value together with global standards Name of session: eCom Major Release 3 Education Time of Session: 09:00 – 10:45 Who May Attend: Everyone Speakers: Anders Grangard, Coen Janssen, Ewa Iwicka

2. GS1 XML 3.0 – background and objective Which messages are new, which were upgraded Which messages will not (yet) be upgraded? What are the plans for the GDSN XML messages? How does GS1 XML 3.0 compare to other XML standards? How does GS1 XML 3.0 rate with respect to CEFACT compliance? GS1 XML 3.0 – functional overview Which messages will be available in GS1 XML 3.0? Brief explanation of the new messages New functions added to the existing messages Which changes were made to the general design? What are the key benefits of GS1 XML 3.0? GS1 XML 3.0 – technical overview How are the XML schemas structured? How are namespaces structured and assigned? What are the key enhancements and benefits on technical level? GS1 XML 3.0 – Deployment Training User Guides Agenda

3. Why a Major Release? • Change Requests requiring non backwards compatible changes • Feed back from users on improvement opportunities • Methodologies, e.g. handling of code lists • Architecture, e.g. simplifying header information • Important new suite of messages • Logistics Interoperability Model – LIM • Last Major was in 2004.

4. The Phased Approach Baseline Release Finalize Foundation Common Requirements Gathered Draft Domain Common Solution Developed & Pilot Executed Finalize Domain Common Publish 3.0 “Baseline” Increment Release(s) Requirements Gathered Solution Developed & Pilot (optionally) executed Publish 3.0 “Increment 1” Requirements Gathered Solution Developed & Pilot (optionally) executed Publish 3.0 “Increment 2” etc…

5. New Messages

6. Approved Change Requests • 15 Simple Change Requests • 4 Non-backwards compatible changes • Affected Messages: • Performance Measurement (PMP) • Purchase Conditions • Configure to Order • Multi Shipment Order • Order Response • Despatch Advice • Receiving Advice • Invoice • Request for Payment

7. [1]Included in LIM (1-13) [2]replaced by 1/36 above [3]replaced by 1/21 above Messages not upgraded • Several messages have not been upgraded from their 2.x version • Old T&L messages functions covered by the LIM based messages • Specialised messages included into generic BMS • Simple invoice → invoice • Multi ship to order → order • Extensions included into the main message • Messages with no known implementation – no matter experts available to support the development • NB! No messages are deleted. Still available and valid for implementation as 2.x. • If requested through due process they will be upgraded as version 3.x. • Changes to version 2.x will not be permitted

8. eCom vs. GDSN XML? • Exchange within the GDSN use different a message set than eCom • Data pool to Data pool • Data pool to/from Global Registry • GDSN and eCom share some components called Common Library • In close cooperation with GDSN we have created three ‘commons’: • Foundation Common – shared by all GS1 BMS • eCom Domain Common – shared by all eCom BMS • GDSN Domain Common – shared by all GDSN BMS (from next GDSN Major Release)

9. GS1 XML and UN XML • Version 3 messages are not profiles/sub-sets of the UN XML from UN/CEFACT • These profiles will be published as a separate suite of messages – currently only a handful of messages. • We align with and reuse UN/CEFACT standards fully or partially whenever possible and relevant • We cannot claim full compliance • GS1 is actively participating in the UN/CEFACT transport and supply chain groups • Members from UN/CEFACT’s groups have actively participated in our development

10. GS1 XML vs. the World • We talk about XML as new technology – it was published 13 years ago • It is based on SGML which is even older • Simple/implementable vs. rich/complex • e.g. Data types • With GS1 XML version 3.0 we have found a good balance between a simple, understandable XML structure whilst yet taking advantage of the XML technology.

11. Timelines & Next Steps • Phase 1 • Pilot (2 messages) – Concluded • Publication – September • Phase 2 • Publication – December • Next version (3.1) • Further LIM based messages • Notably Warehousing messages • Product Recall • Mile stones and publication - tbc

12. GS1 XML 3.0 Functional Overview Coen Janssen Business Process Modeler GS1 Global Office • Which messages will be available in GS1 XML 3.0? • Brief explanation of the new messages • Enhancements of existing messages • Which changes were made to the general design? • What are the key benefits of GS1 XML 3.0?

13. Business Message Standards included in GS1 XML 3.0 (1)

14. Business Message Standards included in GS1 XML 3.0 (2)

15. Role of the Transport Messages (1) BMS Transport Instruction & Response BMS Transport Pick-up Drop-off BMS Transport Status [source: Logistics Interoperability Model, GS1 2007] • Full support for the Transport Execution processes

16. Role of the Transport Messages (2) BMS Transport Capacity Requirements BMS Transport Capacity Plan BMS Transport Capacity Booking & Response [source: BRAD Transport Planning, GS1 2011] • Full support for the Transport Planning processes

17. Role of the Intelligent Packaging messages BMS Artwork Content & Response [source: BRAD Intelligent Packaging, GS1 2010]

18. Order: Integrated MultiShipmentOrder and Order into one single message Added orderTypeCode to header Made orderInstructionCode 0..* instead of 0..1 and added new code value PACK_SEPARATELY Invoice: Integrated the extensions for VAT Added calculation sequence number to Allowance Charge Added excludedFromPaymentDiscountIndicator to Invoice Line Added totalPaymentDiscountBasisAmount to InvoiceTotals Added delivery date information to header and line Despatch Advice: Integrated the extension for crossdocking Added shipmentRemainingQuantityStatusCode to QuantityVariance Added shipmentStatusCode to root Added handlingInstructionCode to Line Added dangerous goods information to Line Receiving Advice Added Purchase Order reference to header and line Enhancements of existing messages

19. Simplified document structure Added free text (notes) to document headers and lines. Layered component libraries Externalized code lists More use of pre-existing codelistssuch as UN/CEFACT based, for example for Allowance Charge codes. Added transactional data to trade party. Added transactional data to trade item. Removed choice constructs Removed unnecessary nestings of elements Reduced mandatory constructs Improvements to the general design

20. Simplified document structure <order:orderMessage> <sh:StandardBusinessDocumentHeader> … </sh:StandardBusinessDocumentHeader> <order> <creationDateTime>2011-08-01T10:00:00</creationDateTime> <documentStatusCode>ORIGINAL</documentStatusCode> <documentActionCode>ADD</documentActionCode> <extension> … </extension> <orderIdentification> <entityIdentification>ON1234</entityIdentification> </orderIdentification> <notelanguageCode="en">XXXXX</note> … </order> </order:orderMessage> • A message always has a distinct root element name. (used to be StandardBusinessDocument) • The Standard Business Document Header is built in to the message (used to be a separate layer) • Each message can contain multiple documents, these have to be of the same type. • Each business document has a documentStatusCode and a documentActionCode(documentActionCode used to be in a separate layer) • Each document has an optional extension point • Most headers and lines have a note element for free text

21. Layered Component Libraries • Reusable components are specified in BMS Shared Common and BMS eCom Common • Also the data types are defined in these two BMS documents • BMS GDSN Common is foreseen for the GDSN components and data types

22. Externalized codes Global Data Dictionary (also in BMS eCom Common) BMS Order <xsd:element name="orderTypeCode" type="ecom_common:OrderTypeCodeType"minOccurs="0"/> BMS eCom Common <xsd:complexType name="OrderTypeCodeType"> <xsd:simpleContent> <xsd:extension base="shared_common:GS1CodeType"/> </xsd:simpleContent> </xsd:complexType> BMS Shared Common <xsd:complexType name="GS1CodeType"> <xsd:simpleContent> <xsd:extensionbase="shared_common:String80Type"> <xsd:attribute name="codeListVersion"> <xsd:simpleType> <xsd:restriction base="xsd:string"> <xsd:maxLength value="35"/> <xsd:minLength value="1"/> </xsd:restriction></xsd:simpleType></xsd:attribute></xsd:extension></xsd:simpleContent></xsd:complexType> • Values are managed in the GDD or by external agencies • Values are not enforced by the XML schema • Applied for codelists that require frequent maintenance • Code value changes do not require a new BMS version.

23. Removed choices, reduced nestings & mandatory constructs GS1 XML 2.6 GS1 XML 3.0

24. Added transactional trade party data • For each party specified in a message it is now possible to include: • Name and address • Contact details • Organization details including legal registration • Tax registration details • Financial institution and account information

25. Added transactional trade item data • For each Trade Item specified in a message it is now possible to include: • Description • Colour details • Size details • Instance data such as serial number and batch number

26. Easier to implement Better support of internal interfacing needs (EAI) Better support for semi-automated processing (e.g. in a web portal). More robust and consistent design Reduced message payload Enhanced business process support (see next slide) Functional benefits of GS1 XML 3.0

27. GS1 XML: A business message standard • Business process requirements driven • A living standard in touch with the needs of the business • GS1 XML 2.x already supported: • the order-to-cash process • advanced replenishment scenarios, such as supplier managed inventoryand consignment inventory. • advanced settlement scenarios, such as evaluated receipt settlementand self-billing. • web-shop integration of consumer orders • GS1 XML 3.0 adds: • support for the packaging artwork design process • support for transport planning and transport execution • GS1 XML 3.1 will add: • support for 3rdparty warehousing • ….

28. GS1 XML Architecture MR3

29. Message Architecture simplification • MR2: layers providing great flexibility, which proved to be unnecessary • MR3: architecture split for GDSN and eCom, following user requirements; eCom greatly simplified MR3 MR2 Transport & routing layer SBDH 1 Message SBDH Message element Service Layer Transaction 1..10000 Command eCom Business Document Business Document 1 Business Document Layer Business Document2 Business Document 3

30. eCom Message architecture 3.0 • GS1 eCom message provides a clear root that contains: • Transport and routing component: (SBDH), mandatory in 3.0 • Business document component: the actual business document(s) • Each message can contain up to 10,000 documents • Only documents of one type are allowed: ONLY Orders or Invoices Message Root 1 eCom Business Message SBDH Transport & Routing component 1..10000 eCom Business Document Business document

31. Transport and routing component OrderMessage InvoiceMessage • Information about routing and processing of the XML instance document • GS1 uses SBDH – Standard Business Document Header, a UN/CEFACT standard root 1 eCom Business Message SBDH 1..10000 eCom Business Document Order Invoice

32. Transport and routing component • SBDH is provides functionality similar to UNH & UNB in EANCOM • SBDH contains information for communication applications: • Document Routing - identifies message sender and receiver; used by message exchange hubs, marketplaces, etc. • Document Identification - used by the middleware to identify and route the message to the appropriate business application without opening it • Document Processing Context - parameters for processing the business document in the context of a business choreography exchange • Payload – container for the business document • www.gs1.org/docs/gsmp/xml/sbdh/SBDH_v1.3_Technical_Implementation_Guide.pdf • SBDH guide for XML 3.0 has been updated: • Value ‘EAN.UCC‘ replaced by ‘GS1’ – consistent with GS1 branding • Schema Guide version added – following user requirement

33. Document actions • Document actions – specify what action should be performed on the business document by the processing application • ADD • CHANGE_BY_REFRESH • DELETE • In MR2 they were defined as Commands in the Service Layer • In MR3 Actions are a part of the Document component

34. Message SBDH . . . Business Document 10,000 Business Document 1 Business Document 2 Business Document 3 Batching of business documents • The architecture allows for batching business documents – transmitting them in one message: • up to 10,000 documents per one message • only one type of documents, e.g. only Orders or only Invoices • mixing various types of documents is not allowed

35. Benefits of the MR3 architecture • Simplified design is easier to understand, thus easier, faster and cheaper to implement • Clear “root” schema for validation • SBDH is an explicitly mandatory component of the message • No need for “Proxy” schemas • Better tool support

36. GS1 schema& package hierarchy

37. Schema Relationships e.g. ebMeatExtension.xsd e.g. DespatchAdvice.xsd Message Schema Extension Schema imports imports StandardBusinessDocumentHeader.xsd e.g. eComCommon.xsd SBDH Schema Domain Common Schema imports imports imports SharedCommon.xsd Shared Common Schema

38. GS1XML 3.0 publication package • The BMS packets are organised by their respective business processes – published as Implementer’s Packets • Each Implementer’s Packet contains the following: • TableofContents.txt – listing all the files included in the given packet • Instance File folder – containing at least one (out of many possible) sample XML file of the message • HTML Sample folder - containing the HTML representation of the sample XML file from the Instance File folder • Schemas folder

39. GS1XML schema folder • Schemas folder contains: • gs1 folder – contains two subfolders: • ecom – includes one schema defining the eCom common library and a schema (or schemas) defining the business document structure. • shared – includes one schema defining the shared common library • sbdh folder – contains the Standard Business Document Header schema

40. GS1 namespaces

41. Namespace structure in XML 3.0 • Namespace hierarchy has been flattened in comparison to 2.0 • Every namespace is used only for one schema file – common library schemas are always imported, never included • Context classification is not used • Namespace ID: ‘gs1’ • urn:gs1:<domain>:<interchange>:<type>:<version-id> • Namespace Scheme

42. Namespace examples urn:gs1:ecom:order:xsd:3 urn:gs1:shared:shared_common:xsd:3 • urn:gs1:ecom:ecom_common:xsd:3 urn:gs1:gdsn:gdsn_common:xsd:3 eCom – Order GS1 Shared Common eCom Domain Common GDSN Domain Common

43. GS1 XML 3.0 Documentation and support

44. GS1 XML 3.0 documentation • Content and structure of business documents are described in BMS • Additional documentation: • SBDH v.1.3 Technical Implementation Guide - updated • GS1 XML MR3 eCom Technical User Guide - under review • BMS package • XML syntax subset used in MR3 • Message architecture • Code list management, etc. • GS1 XML MR3 eCom Functional User Guide – under development • Message set & choreography • Full schema documentation: message hierarchy and definitions • Main actors and their relationship between messages • Identifiers & references • Use of actions • Overview of typical scenarios with message examples: • Order to Cash • Transport execution & planning • Vendor Managed Inventory

45. GS1 XML 3.0 training and support • The on-line training course material explaining GS1 XML rel.3.0 will be published in second half 2012, available via MOs • Set of FAQs updated for MR3 ready to be published at: www.gs1.org/helpdesk • Technical support for user community via GS1 MOs

46. Contact Details GS1 Global OfficeAvenue Louise 326, bte 10B-1050 Brussels, Belgium T +32 3 788 78 00W www.gs1.org