GS1 XML 3.0 Driving Momentum Together

Coen Janssen, Ewa Iwicka, Nora Kaci GS1 Global Office February 17, 2012

© 2012 GS1

Agenda

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

© 2012 GS1

Why a Major Release?

3

• 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.

© 2012 GS1

Approved Change Requests

4

• 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

© 2012 GS1

Messages not upgraded

5

• 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

© 2012 GS1

eCom vs. GDSN XML?

6

• 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 two ‘common libraries’: • Shared Common Library – shared by all GS1 BMS • eCom Domain Common – shared by all eCom BMS

• To be developed: GDSN Domain Common – shared by all GDSN BMS (for next GDSN Major Release)

© 2012 GS1

GS1 XML and UN XML

7

• 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

© 2012 GS1

GS1 XML vs. the World

8

• 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.

GS1 XML 3.0 Functional Overview Coen Janssen Business Process Modeler GS1 Global Office

9

• Which messages are 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?

© 2012 GS1

Business Message Standards included in GS1 XML 3.0 (1)

TRADE

ALIGN

Item Data Notification

PLAN

Goods Requirements

Goods Requirements Response

Replenishment Request

Replenishment Proposal

Purchase Conditions

Inventory Report

Trading Partner Performance Measurement

ORDER

Order

Order Response

Configure to Order

DELIVER

Despatch Advice

Receiving Advice

Consumption Report

Despatch Advice - Meat Product Extension

PAY

Invoice

Settlement

Debit Credit Advice

Advanced Remittance Notification

Request for Payment

Buyer Reconciliation of Request for Payment

Claims Notification

© 2012 GS1

Business Message Standards included in GS1 XML 3.0 (2)

11

LOGISTIC SERVICES

TRANSPORT PLANNING

Transport Capacity Requirements

Transport Capacity Plan

Transport Capacity Booking & Confirmation

TRANSPORT EXECUTION

Transport Instruction & Response

Transport Status Request & Notification

Transport Pick-up Drop-off Request & Confirmation

OTHER

INTELLIGENT PACKAGING

Artwork Content & Response (Pilot)

PRODUCT RECALL

Product Recall Notification, Confirmation & Closeout

SERVICE MESSAGES

Application Receipt Acknowledgement

COMPONENT LIBRARIES

Shared Common

eCom Common

© 2012 GS1

Role of the Transport Messages (1)

12

BMS Transport Instruction & Response

BMS Transport Status

BMS Transport Pick-up Drop-off

Full support for the Transport Execution processes

[source: Logistics Interoperability Model, GS1 2007]

© 2012 GS1

Role of the Transport Messages (2)

13

BMS Transport Capacity Requirements

BMS Transport Capacity Plan

BMS Transport Capacity Booking & Response

Full support for the Transport Planning processes

[source: BRAD Transport Planning, GS1 2011]

© 2012 GS1

Role of the Intelligent Packaging messages (pilot)

14

Version 3 - May 27, 2010

Reconciliation Process

Artw

ork

Stu

dio

Man

ufac

ture

r

Receive Packaging

Content

Studio Content

Changed/Not Linked?

Yes

*

GREEN = PLM/CMS

Legend

BLUE=GS1 Color represents Process/System Used

Receive Final

Notification

PDF Acceptable?

No

NoNotify “Artwork is Final” & store

in System of Record

Yes

END

Send “Frozen”

Packaging Content

Create/Modify Artwork

Annotate PDF

Mfr Changed

Copy?

Change & Approve

Content in CMS

Receive Packaging

Content

Send :”Response”

ContentSend PDF

Request PDF

Changes

Receive PDF

Markups

Yes

All Changes/Choices okay?

Yes Accept Changes in CMS

No

Reject Changes in CMS

Some Changes/Choices okay?

No

Yes Accept Changes in CMS

Note: Studio made changes they shouldn’t have

Note: Content did not change & it is Linked

Receive PDF

No

BMS Artwork

Content & Response

[source: BRAD Intelligent Packaging, GS1 2010]

© 2012 GS1

Enhancements of existing messages

15

• 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

© 2012 GS1

Improvements to the general design

16

Simplified document structure Added free text (notes) to document headers and lines.

Layered component libraries

Externalized code lists More use of pre-existing codelists such 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

© 2012 GS1

Simplified document structure

17

Business Message

Standard Business Document

Header

Document

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

<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> <note languageCode="en">XXXXX</note> … </order> </order:orderMessage>

© 2012 GS1

Layered Component Libraries

18

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

Shared Common eCom Common

Address Levied Duty Fee Tax

Contact Transactional Party

Document Reference Transactional Trade Item

Communication Channel Handling Instructions

Trade Item Classification Dangerous Goods Information

Party Identification Delivery Terms

Trade Item Identification Legal Registration

Currency Exchange Rate Information

Financial Institution Information

Date Time Range Logistic Event

… …

Shared Common eCom

Common

eCom Message

1

eCom Message

2 ….

GDSN Common

GDSN Message

1

GDSN Message

2 ….

Shared Common eCom Common

GTIN OrderTypeCode

Amount HandlingInstructionCode

… …

© 2012 GS1

Externalized codes

19

BMS Order

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.

<xsd:complexType name="OrderTypeCodeType"> <xsd:simpleContent> <xsd:extension base="shared_common:GS1CodeType"/> </xsd:simpleContent> </xsd:complexType>

<xsd:element name="orderTypeCode" type="ecom_common:OrderTypeCodeType" minOccurs="0"/>

<xsd:complexType name="GS1CodeType"> <xsd:simpleContent> <xsd:extension base="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>

BMS eCom Common

BMS Shared Common

Global Data Dictionary (also in BMS eCom Common)

© 2012 GS1

Removed choices, reduced nestings & mandatory constructs

20

<order> <creationDateTime>2011-08-01T10:00:00 </creationDateTime> <documentStatusCode>ORIGINAL</documentStatusCode> <documentActionCode>ADD</documentActionCode> <orderIdentification> <entityIdentification>ON1234</entityIdentification> </orderIdentification> <orderTypeCode>220</orderTypeCode> <additionalOrderInstruction languageCode="en">abcdefghijklmnopqrstuvwxyz </additionalOrderInstruction> <buyer> <gln>1111111111116</gln> </buyer> <seller> <gln>2222222222222</gln> </seller> <orderLogisticalInformation> <shipTo> <gln>3333333333338</gln> </shipTo> <orderLogisticalDateInformation> <requestedDeliveryDateTime> <date>2011-09-01</date> </requestedDeliveryDateTime>

<order:multiShipmentOrder creationDateTime="2011-08-01T10:00:00" documentStatus="ORIGINAL"> <orderIdentification> <uniqueCreatorIdentification>ON1234 </uniqueCreatorIdentification> <contentOwner> <gln>1111111111116</gln> </contentOwner> </orderIdentification> <additionalOrderInstruction> <language> <languageISOCode>en</languageISOCode> </language> <longText>abcdefghijklmnopqrstuvwxyz</longText> </additionalOrderInstruction> <orderPartyInformation> <seller> <gln>1111111111116</gln> </seller> <buyer> <gln>2222222222222</gln> </buyer> </orderPartyInformation> <orderLogisticalInformation> <shipToLogistics> <shipTo> <gln>3333333333338</gln> </shipTo> </shipToLogistics> <orderLogisticalDateGroup> <requestedDeliveryDate> <date>2011-09-01</date> </requestedDeliveryDate>

GS1 XML 3.0 GS1 XML 2.6

© 2012 GS1

Added transactional trade party data

21

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

© 2012 GS1

Added transactional trade item data

22

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

© 2012 GS1

Functional benefits of GS1 XML 3.0

23

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)

© 2012 GS1

GS1 XML: A business message standard

24

• 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 inventory and consignment inventory. • advanced settlement scenarios, such as evaluated

receipt settlement and 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 3rd party warehousing • ….

GS1 XML Architecture MR3

© 2012 GS1

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

Transport & routing layer

Service Layer

Business Document Layer

Message element

SBDH

Transaction

Command

Business Document 3

Business Document 2

Business Document 1

MR2

eCom Business Document

1..10000

Message SBDH 1

MR3

© 2012 GS1

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

eCom Business Document

1..10000

eCom Business Message SBDH 1

Message Root

Business document

Transport & Routing

component

© 2012 GS1

Transport and routing component

• Information about routing and processing of the XML instance document

• GS1 uses SBDH – Standard Business Document Header, a UN/CEFACT standard

eCom Business Document

1..10000

Order Invoice

eCom Business Message SBDH 1 root

OrderMessage InvoiceMessage

© 2012 GS1

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

© 2012 GS1

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

© 2012 GS1

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

Message

SBDH

Business Document 10,000

Business Document 1

Business Document 2

Business Document 3

. . .

© 2012 GS1

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

GS1 schema & package hierarchy

© 2012 GS1

Schema Relationships

Message Schema

Extension Schema

Shared Common Schema

imports

imports

e.g. DespatchAdvice.xsd e.g. ebMeatExtension.xsd

e.g. eComCommon.xsd

Domain Common Schema

SharedCommon.xsd

imports imports

SBDH Schema

imports

StandardBusinessDocumentHeader.xsd

© 2012 GS1

GS1 XML 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

GS1 namespaces

© 2012 GS1

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’

Element Purpose Example

Domain GS1 Business Area, Service, Technology

eCom, GDSN, GEPIR, EPC

Interchange Artefact within the GS1 Domain

Business Document / Extension / Header Message Layer

Type Resource type xsd

Version ID Version of the Interchange 3

urn:gs1:<domain>:<interchange>:<type>:<version-id>

Namespace Scheme

© 2012 GS1

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

GS1 XML 3.0 Documentation and support

© 2012 GS1

GS1 XML 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

© 2012 GS1

GS1 XML 3.0 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 DEMO

© 2012 GS1

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

GS1 XML 3.0 Marketing & Communication

© 2012 GS1

Marketing GS1 XML 3.0

45

Solutions: • Order-to-cash (downstream)

• Retail • Webshop integration (B2C)

• Upstream Integration • Delivery management (SSCC, Logistics Label, Despatch Advice) • Transport Management • Product Recall • Intelligent Packaging (under way)

Improved eCom website DEMO

Communication: • How to help communicate on GS1 XML 3.0 press release, social networks,

forums, … Discussion

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

Contact Details