WP3 Framework development Overview of eBIZ-TCF Reference Architecture Porto, 3 / 4 of May 2012

1. STIMULATING INNOVATION IN THE FOOD SUPPLY-CHAIN THROUGH SMART USE OF ICT: ASSISTING SMES PARTICIPATE IN DIGITAL SUPPLY CHAINS IN THE SINGLE MARKET • WP3 Framework development • Overview of eBIZ-TCF Reference Architecture • Porto, 3 / 4 of May 2012

2. eBIZ-TCF, Introduction. • Project similar to eFoodChain • Targets SMEs in the textile/clothing and footwear sectors aiming at “offering a vision of a Reference Architecture for the eBusiness harmonisation in the Textile, Clothing and Footwear (TCF) sectors, establishing thus a coherent and homogeneous framework for representing and documenting existing specifications” • Started in 2008, concluded in June 2010 • Web site: http://www.ebiz-tcf.eu/

3. eBIZ-TCF, ReferenceArchitecture. basedonselectedstandards basedonebXML: CPPA(Collaboration Protocol Profile and Agreement) ebMS(Messaging Service)

4. eBIZ-TCF, ReferenceArchitecture. • Architecture is based on four different types of specifications: • Business processes • Data models (document templates implemented on XML, some of them related with pre-existing EDI specifications) • Collaborationandcommunicationprotocols • Product identification and classification, and party identification • Available in PDF file

5. eBIZ-TCF, ReferenceArchitecture, Product & Partyidentification. • In B2B relationships with retail organisations (downstream part of the supply chain): • For product identification: • GTIN “Global Trade Item Number” • For identification of locations and parties: • GLN “Global Location Number” • In B2B upstream relationships (between manufacturers, between manufacturers and suppliers or between manufacturers and brand owners): • Any kind of identifiers may be used “… it is a duty of the parties to avoid misunderstandings; the parties and locations must be explicitly and extensively described.”

6. eBIZ-TCF, ReferenceArchitecture, Middlewareandcommunicationprotocols. • Inter-company (in a Peer-to-Peer mode or via a connectivity hub) data exchange supported by: • SOAP over HTTP(S) or • SMTP • Idem for inter-hub data exchange with the added guarantees of: • identification of the originator of business documents • assure for non-repudiation of received messages

7. eBIZ-TCF, Reference Architecture, Business Layer. • Three application sub domains: • Production to Retail Relationships (Downstream) • Textile/Clothing Enterprise Networks (TC Upstream) • Footwear Enterprise Networks (FW Upstream) • The following standards/specifications were considered: • MODA-ML, TexWeave, Shoenet, EFNET, GS1, UBL

8. eBIZ-TCF, Reference Architecture, Business Layer. • A harmonised collection of documentation was defined for each application domain as follows: 1. Supply chain description (reference set of business processes) 1.1. Business Process X (set of activities) 1.1.1. Activity X.Y (sequence of simple document-exchange transactions) 1.1.1.1. Transactions X.Y.1 2. Document models necessary for all the processes 3. Lacking elements

9. eBIZ-TCF, Reference Architecture, Business Layer. • XSD schema files are available at: • Textile/Clothing industry upstream area: http://www.moda-ml.net/moda-ml/repository/ebBP/v2008-1/en/ • Footwear industry upstream area: http://spring.bologna.enea.it/eBIZ-footwear/repository/ebbp/v2008-1/en/ • Textile/Clothing and Footwear industry downstream area: http://www.moda-ml.net/eBIZ-retail/repository/ebbp/v2008-1/en/

10. eBIZ-TCF, TheEnd. • Thank for youattention.