1. Implementation of SDSComXML Step-by-Step approach
(C) eSDScom Alliance UG,
Licensed under CC-BY-SA 4.0:

2. Scope and Goals
SDScom = Safety Data Sheet communication: All SDS content in a machine-processible format
Best Practice, maintained by an expert group from chemical and IT industry as well as associations
Speeds up downstream communication
No typing errors, increases data quality
Saves money for downstream users

3. SDScom Features
Covers electronic exchange of European SDSs in XML
Non-proprietary specification
Freely available under an Open Source license (Creative Commons BY-ND 4.0)
More info:

4. SDScomXML Implementation Roadmap
STEP 1: Convince your managament
Give a presentation about costs & benefits; use this presentation
STEP 2: Find company internal funding (e.g. projects under Industry 4.0)
With support of your management
STEP 3: Find pilot project partner
Use the opportunity during BDI XML Workshops or ask directly your suppliers
STEP 4: Implement the SDScomXML Interface:
Implement a SDSComXML Import interface – testing with a project partner
Implement a SDSComXML Export interface – testing with an internal partner
Implementation support: eSDScom Alliance UG (
STEP 5: Share your experience (lessons learned)
Use the next BDI XML Workshop to share your experience with others
STEP 6: Further development of the standard
Be active in further development of the open standard

5. STEP 1
Benefits & Costs

6. Benefits: Less work by manual editing of incoming SDS information
More simple process for entering data in inhouse IT system (enables further automation of data entry)
Potential interface for communication between internal IT systems (other trademarks, after sales)
Less issues with compliance (SDScom is endorsed and promoted by ACEA – see position paper)

7. SDS Processing costs:
Formulator A: 800 € per SDS, including validation, performed by a designated team in Eastern Europe
End user B: Between 1 and 4 hours for retyping, (depending on number of fields and phrases), plus 1 hour validation
Service Provider C: Offers retyping in customer‘s IT for 400 € (without validation of the data)
Processing crucial fields costs at least 100 €, in realistic scenarios 200 € to 400 € per supplier SDS.
Processing time with XML: max. 1 min. per SDS (w/o validation)
Saving: ca. 249 min. per SDS!
Corresponds to ca. 4 h
Corresponds to ca. 2 FTE (Full-Time-Equivalent)

8. Funding (project money)
STEP 2
Funding (project money)
This differs from company to company.
Discuss with your management or financial department how to proceed.

9. STEP 3 Find project partners
Ask your supplier if they have already implemented an SDScomXML
interface or whether they plan to do so.
Visit XML Workshop or ask company‘s who have already implemented a
XML interface.
If they use one of the following IT systems they should already be capable to
deliver SDS in XML (see next slide).

10. Enterprise-Range Solutions
IT providers with SDScom capability
(source:
Enterprise-Range Solutions

11. Implementation of SDScomXML
STEP 4
Implementation of SDScomXML
Download the XML format from the Homepage
Map the structure with your IT system.
If you need support, contact eSDScomXML Alliance.
Because the service is not cost-free, it‘s recommended to include a financial
position into the budget.
Discuss technical issues / implementation problems on Github:
Test the performance with your pilot project partner

12. STEP 5 Share your experience
Next BDI XML Workshop is planned for 19. May 2019 in Berlin.
If you have already started with implemenation or plan to start,
use this platform for discussion, sharing experiences and information.
Find project partners or alternatively present yourself as a project partner.
Contact and ask the BDI team or
whether you are allowed to present something during next Workshop.
Show your presentation on other events, e.g. in your own association.
etc.

13. Further development of the standard
STEP 6
Further development of the standard
Be active in further development of the open standard
SDScomXML is an open standard and needs active support (work in the SDScomXML political organisation) and passive support (financial sponsoring).
The Steering Committee and ACEA detected the further add-ons which would be valid for future development (see next slide)

14. Future Requests for SDScom tools
Validator, including content – should ideally guarantee SDS acceptance
Editor for Safety Data Sheets and Exposure Scenarios, stored as SDScom and ESCom files – with EuPhraC phrases
Print templates for SDScom safety data sheets
Use-based compliance checker
Scaling tool for formulators

15. (Background information)
What is SDScomXML?
(Background information)

16. Transfer of SDS with SDScomXML
Current standard Process:
PDF
S/M* Supplier 1
Customer
(OEM)
Excel
S/M* Supplier 2
Word
S/M* Supplier 3
Printout
S/M* Supplier 4
SDS Creation either
manually or with software
Manual SDS Processing
(Analyzing, Checking, Implementing, …)
*S/M: Substances / Mixtures
Transfer of SDS with SDScomXML
SDScomXML
S/M* Supplier 1
Customer
(OEM)
SDScomXML
Currently already possible Process:
S/M* Supplier 2
SDScomXML
S/M* Supplier 3
XML
SDScomXML
S/M* Supplier 4
SDS Creation with software -> In House Tool
-> eSDScomXML for ext. SDS
Semi-automatic SDS Processing (Analyzing, Checking, Implementing, …)
-> In House Tool (e.g VW, BMW, Daimler)
-> already existing IT Inhouse tools can be
adjusted with low internal effort.
*S/M: Substances / Mixtures

17. SDScomXML benefits in a nutshell
Compared with typical current SDS provision (see previous slide), communicating SDSs via an electronic tool using a standard SDS XML format could have a number of benefits…
…for Suppliers
…for Recipients
…for Industry in General
Easily send new/revised SDSs to multiple Recipients
Replace multiple methods ( /mail/customer portals/etc.) with just one
Increase in data quality due to potential for built-in data validity checks and accumulated recipient comments
Define SDS reviews, based on one consistent format
Upload SDS data directly into in-house systems
Consistency and clarity of exchanged data - allows analysis of SDS data from multiple suppliers
Audit trail for SDS communication (i.e. send/ receipt/acceptance history with version and language traceability)
Improved overall efficiency in SDS supply chain
Increase SDS quality as suppliers respond to recipient comments, less manual human errors, decreased administrative burden
Employees view SDSs with consistent appearance, increasing ease of reading and understanding
Eliminate manual indexing/data extraction
Facilitate processing of voluminous information
Visibility and tracking data exchange
Longer term Add-ins: elimination of hard-copy (e)SDS’s and validation tool
Compared with typical current SDS provision (see previous slide), communicating SDSs via an electronic tool using a standard SDS XML format could have a number of benefits…

18. SDScomXML is NOT a software!
Definition of XML in general
● XML = Extensible Markup Language (meta language for development
of the markup language for logical structuring on the Internet).
● XML Schema defines the frame conditions with which the content of
e.g. Safety Data Sheets can be exchanged structured electronically.
● XML Schema is cross-industry usable and internationally applicable.
● XML Schema defines for example how and where the flashpoint of a
substance is to be stated.
SDScomXML is NOT a software!

19. SDScomXL will reduce costs for communication of safe use information
What is SDScomXML?
SDScom is an XML based standard for the system-independent electronic exchange of safety-data-sheets.
SDScom introduces XML-Schema-files for basic and complex data types to cover the whole content of safety-data-sheets according to REACH and CLP (GHS)
SDScom is open for national extensions covering requirements from regional legislation.
SDScom is prepared to deal with standard phrase catalogues (e.g EuPhraC), but is also working with other standard phrases catalogues
The SDScom specification is maintained and discussed on Github. There is and will be no license fee for using SDScom.
SDScomXL will reduce costs for communication of safe use information

20. Exchange format example
<HazardIdentification>
<Classification>
<ClpClassification>
<ClpHazardClassification>
<ClpHazardClassCategory>Skin irritation - Category 2</ClpHazardClassCategory>
<ClpHazardStatement PhraseId=" " PhraseCatalogueId="0">
<PhraseCode>315</PhraseCode>
<FullText>Causes skin irritation.</FullText>
</ClpHazardStatement>
</ClpHazardClassification>
<ClpHazardClassCategory>Eye irritation - Category 2A</ClpHazardClassCategory>
<ClpHazardStatement PhraseId=" " PhraseCatalogueId="0">
<PhraseCode>319</PhraseCode>
<FullText>Causes serious eye irritation.</FullText>
</ClpClassification>
</Classification>
<HazardLabelling>
<ClpLabellingInfo>
<ClpHazardPictogram>
<PhraseCode>GHS07</PhraseCode>
</ClpHazardPictogram>
<ClpSignalWord PhraseId=" " PhraseCatalogueId="0">
<PhraseCode>WNG</PhraseCode>
<FullText>Warning</FullText>
</ClpSignalWord>
<ClpPrecautionaryStatement PhraseId=„
PhraseCatalogueId="0">
<PhraseCode>280</PhraseCode>
<FullText>Wear protective gloves

21. „Future“ add-ins PDF plus embedded XML-file = PDF/A-3 really only
<HazardIdentification>
<Classification>
<ClpClassification>
<ClpHazardClassification>
<ClpHazardClassCategory>Skin irritation - Category 2</ClpHazardClassCategory>
<ClpHazardStatement PhraseId=" " PhraseCatalogueId="0">
<PhraseCode>315</PhraseCode>
<FullText>Causes skin irritation.</FullText>
</ClpHazardStatement>
</ClpHazardClassification>
<ClpHazardClassCategory>Eye irritation - Category 2A</ClpHazardClassCategory>
<ClpHazardStatement PhraseId=" " PhraseCatalogueId="0">
<PhraseCode>319</PhraseCode>
<FullText>Causes serious eye irritation.</FullText>
</ClpClassification>
</Classification>
<HazardLabelling>
<ClpLabellingInfo>
<ClpHazardPictogram>
<PhraseCode>GHS07</PhraseCode>
</ClpHazardPictogram>
<ClpSignalWord PhraseId=" " PhraseCatalogueId="0">
<PhraseCode>WNG</PhraseCode>
<FullText>Warning</FullText>
</ClpSignalWord>
<ClpHazardStatement PhraseId=" " Phrase
<PhraseCode>315
<FullText>
data
plausibility
check
customer
internal
IT system
other
apps
PDF plus embedded XML-file = PDF/A-3 really only
adds a single feature, but it’s an important one.
It enables users to embed any files into a PDF.
This includes files, such as XML.
This addition creates many new applications.
With PDF/A-3, your PDF can act as a delivery
vehicle or container for any file type.
In essence, PDF becomes a zip archive.

22. The European maintenance organisation structure
BDI
(coordination)
CEFIC
(coordination)
cooperation
EuPhraC + SDScom
Steering Committee
EScom
Steering Committee
EuPhraC Phrases
Working Group
SDScomXML
Working Group
Escom XML
Working Group
Escom Phrases
Working Group
SDScomChem
SDScomBau
PIC XML
eSDSCom

24. Overview on all open standards
free
tools
standard phrases proposal
and Online-discussion
SDS templates
and other tools
open
standards
EuPhraC
European Standard Phrase Catalogue
SDScom + ESCom
XML data exchange
SDS + exposure scenario
Implem.
commercial provider
translations
in 30+ languages
SDS creation
online and offline tools

25. SDScomXML – Cooperation with other European stakeholders

26. Maintenance on github – free input possible

27. Workshops on a regulatory basis
Next Workshop
planned
for
18. May 2019
in Berlin.
Please
Save-the-date!

28. Similar XML formats SDScomXML  SDB Hauptteil http://www.sdscomxml.eu/
User:
Norwegian product data base
- GISBAU-SDS-interface: SDSComBau
schnitt_start.htm (branche solution)
BG-RCI-interface: SDSComChem
SDBtransfer project (
Poison information centers (notification) (
ESComXML  Exposure scenarios
Implementing-reach/IT-Tools/