The NEW eBIZ Reference Architecture and the online validation tool ( Bruxelles, De Sabbata, eBusiness, textile, clothing, supply chain, )
1. eBIZ
Towards one eBusiness
Language for fashion
The NEW eBIZ Reference
Architecture and
the online validation tool
CEN WS eBIZ
Plenary session
Brussels June 26th 2013
Piero De Sabbata
(ENEA)
2. eBIZ
Towards one eBusiness
Language for fashion
2 – Bruxelles, June, 2013
Summary
Interoperability
• Reference Architecture short overview
• Improvements in CEN eBIZ Workshop
• Conformance and validation tool
• Final considerations
3. eBIZ
Towards one eBusiness
Language for fashion
3 – Bruxelles, June, 2013
The problem (business perspective):
being networked
• TRENDs:
– Reduction of time to respond/deliver
– Reduction of the size of the lots and increasing request for customised products
(and services)
– Increasing interdipendence between firms of the same supply chain
• CONSEQUENCE:
– NETWORKS (of knowledge, of demand, of supply, …) as a key factor of
competitiveness
– Better SERVICES are requested (control and planning)
– INCREASING quantity of information/knowledge to exchange for unit of product
• ICT systems are enablers (not sufficient but necessary):
– CROSS organisation data flows are an issue
high costs -> poor collaboration
• Difficulties for firms, especially SMEs and TCF sector:
technology but also organisation
4. eBIZ
Towards one eBusiness
Language for fashion
4 – Bruxelles, June, 2013
The problem (technology
perspective): B2B integration in
many-to-many networks
Applicative Integration
(towards ERPs)
Business processes
Data models and semantic
Data syntax (XML)
Information Transport
(Web services, ebXML MS)
Domain/Applic.
driven
Technology
driven
CRITICAL AREA!
Trade
5. eBIZ
Towards one eBusiness
Language for fashion
6 – Bruxelles, June, 2013
The Reference Architecture concept
eBIZ Reference Architecture defines (few) rules for the applications and the
actors of the TCF supply chains
REQUIREMENTS:
• Neutrality
• Low entry threshold
• Scalability
• Reusability
• Pubblic access
CONTENT:
● Business models
● Business processes
● Data models
● Product identification and classification
● Transport protocols (communication)
It is not a software application
It enables interoperable software applications
It is a public Report supported by online Software resources
6. eBIZ
Towards one eBusiness
Language for fashion
7 – Bruxelles, June, 2013
The Ref. Architecture domain
Trade
Textile Clothing
production
networks
Yarns, fabrics, clothings
Footwear production
components, shoes
Relationship
to retail
Final products
Upstream DownstreamCEN/ISSS
TexWeave
Moda-ML
CEN/ISSS
FINEC
CecMadeShoe
SHOENET,
SHOEBIZ
CecMadeShoe
CEN/ISSS TexWeave,
OASIS UBL use
profiles,
GS1 GTIN, GLN,
SSCC, EPC
eBIZ: sectorial
upstream
specifications
eBIZ: common
downstream
specifications
7. eBIZ
Towards one eBusiness
Language for fashion
8 – Bruxelles, June, 2013
The architecture fits different
priorities in the chain
2 key areas of a public general architecture:
– manufacturing networks (upstream):
Sector specific languages to obtain maximum performance &
flexibility and to quickly react to market trends.
– production to retail (downstream):
Common cross-sectorial specifications to obtain maximum
simplicity with “scalable” (modular) level of complexity to support
different type of products. Mandatory global product identification.
8. eBIZ
Towards one eBusiness
Language for fashion
11 – Bruxelles, June, 2013
Resources supporting the
Architecture
• Full online technical documentation (user guides, XML samples,
XSL, ..)
• XML Schema for data models;
• Schematron to support business rules and use profiles
• ebBP representation of the PROCESSES (ISO15000)
• On-line validation tool (based on xml schema + business rules)
9. eBIZ
Towards one eBusiness
Language for fashion
12 – Bruxelles, June, 2013
Summary
Interoperability
• Reference Architecture short overview
• Improvements in CEN eBIZ Workshop
• Conformance and validation tool
• Final considerations
10. eBIZ
Towards one eBusiness
Language for fashion
13 – Bruxelles, June, 2013
CEN WS eBIZ RA update
1. Abstract business models to be implemented through different
processes (contribution from GS1 Germany); approach based on
the concept of FUNCTION
2. eDocuments flows in parallel to RFID flows
3. Customised products processes for footwear sector
4. Yarn production (laboratory tests transmission, etc)
5. eInvoices
6. AS4 based web service communication
7. Conformance and validation
11. eBIZ
Towards one eBusiness
Language for fashion
Types of business
Logistics
Responsibility of
replenishment
Concessions
Consignment
Store level
Classical
management
Consignment
DC level
Commission
VMI BMI
Distribution
Center CD 2 CD 1
Direct
Delivery
Invoicing
Credit note
PP
Credit note
SP./.Margin
Invoice
PP
Invoice
SP./.Margin
Compensation
key
Modular System for Floor management Systems
Complexity reduction of implemented business solutions by dividing up into 4 main components
(Contribution from GS1 Germany)
Downstream schema
1. Business models
12. eBIZ
Towards one eBusiness
Language for fashion
15 – Bruxelles, June, 2013
eBIZ Production to retail processes
15 – Munich, February, 2013
Process (downstream) Activity
cyclic replenishment program
- CRP
Transfer of base article catalogue (mandatory)
Initial stocking of the area by retailer
Periodic (weekly) replenishment (mandatory)
Report of sales and inventory movements (mandatory)
Invoicing
Synchronizing of stock information (using RFID)
Changes to the article catalogue (mandatory)
classical preorder Initial transfer of order and article data (mandatory)
Transfer of changes to the order
Finalizing of the order
Delivery (mandatory)
Invoicing
Report of sales data (mandatory)
vendor managed inventory -
VMI
Initial stocking of the area by vendor (mandatory)
Daily report of sales and inventory movement (mandatory)
RFID based in between inventory
Permanent replenishment (mandatory)
Invoicing
Returns initiated by the producer
Price adjustments (mandatory)
replenishment on customer
demand
Transfer of base article catalogue (mandatory)
Periodic transfer of article availability information (mandatory)
Initial stocking of the area by vendor and buyer (mandatory)
Periodic replenishment
(mandatory)
Report of sales and inventory movements
Invoicing (mandatory)
13. eBIZ
Towards one eBusiness
Language for fashion
Types of business
Logistics
Responsibility of
replenishment
Concessions
Consignment
Store level
Classical
management
Consignment
DC level
Commission
VMI BMI
Distribution
Center CD 2 CD 1
Direct
Delivery
Invoicing
Credit note
PP
Credit note
SP./.Margin
Invoice
PP
Invoice
SP./.Margin
Compensation
key
Modular System for Floor management Systems
Complexity reduction of implemented business solutions by dividing up into 4 main components
Downstream schema
Business model classification
14. eBIZ
Towards one eBusiness
Language for fashion
Types of business
Logistics
Responsibility of
replenishment
Concessions
Consignment
Store level
Classical
management
Consignment
DC level
Commission
BMI
Distribution
Center CD 2 CD 1
Direct
Delivery
Invoicing
Credit note
PP
Credit note
SP./.Margin
Invoice
PP
Invoice
SP./.Margin
Compensation
key
Modular System for Floor management Systems
Complexity reduction of implemented business solutions by dividing up into 4 main components
(Contribution from GS1 Germany)
Downstream schema for CRP
Business model classification
VMI
15. eBIZ
Towards one eBusiness
Language for fashion
Processo Activity
cyclic replenishment
program - CRP
Transfer of base article catalogue (mandatory)
Initial stocking of the area by retailer
Periodic (weekly) replenishment (mandatory)
Report of sales and inventory movements (mandatory)
Invoicing
Synchronizing of stock information
Changes to the article catalogue (mandatory)
classical preorder Initial transfer of order and article data (mandatory)
Transfer of changes to the order
Finalizing of the order
Delivery (mandatory)
Invoicing
Report of sales data (mandatory)
vendor managed inventory -
VMI
Initial stocking of the area by vendor (mandatory)
Daily report of sales and inventory movement (mandatory)
Permanent replenishment (mandatory)
Invoicing
Returns initiated by the producer
Price adjustments (mandatory)
replenishment on customer
demand
Transfer of base article catalogue (mandatory)
Periodic transfer of article availability information (mandatory)
Initial stocking of the area by vendor and buyer (mandatory)
Periodic replenishment
(mandatory)
Report of sales and inventory movements
Invoicing (mandatory)
Synchronizing of stock information (mandatory)
Changes to the article catalogue (mandatory)
Production to retail (downstream)
16. eBIZ
Towards one eBusiness
Language for fashion
19 – Bruxelles, June, 2013
2. RFID usage support
• Support to EPC Gen 2 (tags and readers) and EPC product
identification specifications
• Relevant RFID use cases list
• Improvement of downstream processes with RFID usage
• Improvement of data models related with RFID (Despatch Advices,
Inventory reports, Darning commission orders…) in order to allow
to communicate RFID codes in parallel to the goods flows
• Pays attention to NFC technologies for future developments
(Contributions from GS1 Germany, LOGIS LAB, LAB#ID)
17. eBIZ
Towards one eBusiness
Language for fashion
20 – Bruxelles, June, 2013
Improved downstream processes
20 – Munich, February, 2013
Process (downstream) Activity
cyclic replenishment program
- CRP
Transfer of base article catalogue (mandatory)
Initial stocking of the area by retailer
Periodic (weekly) replenishment (mandatory)
Report of sales and inventory movements (mandatory)
Invoicing
Synchronizing of stock information (using RFID)
Changes to the article catalogue (mandatory)
classical preorder Initial transfer of order and article data (mandatory)
Transfer of changes to the order
Finalizing of the order
Delivery (mandatory)
Invoicing
Report of sales data (mandatory)
vendor managed inventory -
VMI
Initial stocking of the area by vendor (mandatory)
Daily report of sales and inventory movement (mandatory)
RFID based in between inventory
Permanent replenishment (mandatory)
Invoicing
Returns initiated by the producer
Price adjustments (mandatory)
replenishment on customer
demand
Transfer of base article catalogue (mandatory)
Periodic transfer of article availability information (mandatory)
Initial stocking of the area by vendor and buyer (mandatory)
Periodic replenishment
(mandatory)
Report of sales and inventory movements
Invoicing (mandatory)
18. eBIZ
Towards one eBusiness
Language for fashion
21 – Bruxelles, June, 2013
3. Customised products processes for
footwear sector:
Manufacturing networks (footwear)
Process Activity
Component supply
Transfer Of Order
Status Report
Technical Specification
Delivery
Product Design Transfer of Model Design
Pre-Series order
Status Report
Delivery
Customised made shoes for health sector Technical Specification for custom product
Transfer Of custom product order
Custom Component Supply
Status Report for custom product
Delivery of custom product
Technical Specification for custom product
Fashion custom made shoes Technical Specification for custom product
Transfer of custom product order
Custom Component Supply
Status Report for custom product
Delivery of custom product
(Contributions from INESCOP)
19. eBIZ
Towards one eBusiness
Language for fashion
22 – Bruxelles, June, 2013
4. Yarn production (laboratory tests
transmission, etc) in Manufacturing
networks (textile-clothing)
To support high quality yarn supplying
• Modelling of new “YARN selection” activity
• New YARNQualityReport, YARNOfferRequest, YARNOffer and
YARN Technical Sheet
(supporting data to identify the yarn-article and to specify
manufacturing characteristics and mechanical-physical-chemical
properties)
(Contributions from Tecnotessile, CentroCOT, X-Rite, Cariaggi,
Marchi & Fildi, Domina)
20. eBIZ
Towards one eBusiness
Language for fashion
23 – Bruxelles, June, 2013
Process Activity
Fabric subcontracted darning Subcontracted fabric darning
Fabric subcontracted
manufacturing
Subcontracted warping
Subcontracted weaving
Subcontracted fabric dyeing-finishing
Subcontracted fabric printing
Fabric supply Selection of fabrics
Purchase of fabrics
Fabric delivery with quality reporting by Producer
Despatch of fabrics with groupage
(Alternative to the previous one)
Fabric delivery with quality reporting by Controller
(Alternative to the previous one)
Invoicing of fabrics
Garment accessory supply Purchase of Garment accessory
Delivery of Garment accessories
Knitwear subcontracted
manufacturing
Knitting and assembling
Knitwear finishing
On line stock service Offer stocks on-line
Yarn subcontracted manufacturing Subcontracted dyeing of raw material
Subcontracted spinning of raw material
Subcontracted yarn twisting
Subcontracted yarn dyeing
Yarn supply Selection of yarn
Purchase of yarn
Delivery of yarn
4. Yarn production (laboratory tests
transmission, etc)
Manufacturing networks (textile-clothing)
21. eBIZ
Towards one eBusiness
Language for fashion
24 – Bruxelles, June, 2013
5. eInvoices
Being aware of
• the position of the European Commission communication
COM(2010)712 final about electronic invoicing
• the experiences of countries where it is already mandatory in public
procurement
• the initiatives running at CEN, ISO, UN/CEFACT, OASIS,…
The eBIZ Invoice data model supports all the information required
by the 2010/45/EU directive.
NOTE that
• the need for the issuer to manage possible additional national
requirements
• issues related to signature and storage are out of the scope of eBIZ
(Contributions from ENEA)
22. eBIZ
Towards one eBusiness
Language for fashion
25 – Bruxelles, June, 2013
6. AS4 based web service communication
The new AS4 protocol has been adopted in order to support Web
Services
in a four corners model
The four-corner model (used in various domains, for example EU
PEPPOL) is currently being standardized within the OASIS Business
Document Exchange (BDX) committee.
(Contributions from Sonnenglanz and ENEA)
23. eBIZ
Towards one eBusiness
Language for fashion
26 – Bruxelles, June, 2013
Summary
Interoperability
• Reference Architecture short overview
• Improvements in CEN eBIZ Workshop
• Conformance and validation tool
• Final considerations
24. eBIZ
Towards one eBusiness
Language for fashion
7. Conformance and validation
1) Software packages correctly implementing eBIZ must be recognised
(«conformance»)
2) Minimise risk of interoperability gap between applications (thus time
to setup inter-company collaborations)
WHY?
WHAT: MINIMAL CRITERIA
An application can be eBIZ compliant even if it satisfies only a core
subset of the whole specification (we speak about different levels of
conformance)
the minimal core subset is constituted by semantics and data models
and syntax used for each of the implemented transaction, none
excluded (‘eBIZ-conformance to document level for a specific
process’).
25. eBIZ
Towards one eBusiness
Language for fashion
• On-line artifacts (based on XML Schema and Schematron) in order
to check XML Document conformance to eBIZ semantic and data
models
• eBIZ-TCF document Validator: a web application (basedon the
delivered artifacts) to automatically check XML documents.
• Validator has a twofold role:
• To assist developers when testing their implementations in order
to improve their correctness
• To support the eBIZ experts in the formal validation of the
documents submitted by an eBIZ compliant candidate
7. Conformance and validation/2
HOW?
26. eBIZ
Towards one eBusiness
Language for fashion
29 – Bruxelles, June, 2013
eBIZ validation service
http://
www.ebiz-tcf.eu/index.php/2012-09-20-14-10-25/news-upcoming-events/13-news/
27. eBIZ
Towards one eBusiness
Language for fashion
30 – Bruxelles, June, 2013
eBIZ validation service/2
Line 13: standard UBL element is not admitted in eBIZ use profile (restriction)
Line 36: an element is required to have a LEGAL invoice
(but not for internal use)
LINE 145: a business rule allows to check the value of an element against an
expression involving two others
28. eBIZ
Towards one eBusiness
Language for fashion
31 – Bruxelles, June, 2013
Summary
Interoperability
• Reference Architecture short overview
• Improvements in CEN eBIZ Workshop
• Conformance and validation tool
• Final considerations
29. eBIZ
Towards one eBusiness
Language for fashion
• Processes supporting anticounterfeiting actions
(based on RFID or others)
• NFC (Near Field Communication) technologies
use
• Made to measure/customised apparel processes
• Traceability, Origin certificates, …
• Systematic support to interoperability between ERP
and CRM and eCommerce platforms
• International multi-tier logistic
What is out of the present RA
but might be in the future
30. eBIZ
Towards one eBusiness
Language for fashion
Conclusions
CEN WS eBIZ consolidated existing eBIZ RA maintaining back
compatibility
Systematization of business models create a solid platform for
future business processes improvements
New sector specific processes and activity have been modelled
demonstrating the capability of incremental growth of the RA
A number of organisations directly contributed to new
developments.
31. eBIZ
Towards one eBusiness
Language for fashion
34 – Bruxelles, June, 2013
Thanks
Piero De Sabbata
ENEA, piero.desabbata@enea.it
www.ebiz-tcf.eu
eBIZ group on