ESComXML: Status Quo
6th Meeting of the Exchange Network on Exposure Scenarios (ENES6)
Helsinki, 13-14 May 2014
Mathias Glockner, SAP AG
(on behalf of the ESComXML IT Provider Group)
Purpose of the information present in ESComXML
Scope of Version 2.0

Store and use ES-relevant information in the company EHS
system
 The use of ES-relevant information includes:
 Printing of Exposure Scenarios from the EHS system
 Inclusion of imported Exposure Scenarios for own products
 Comparison of Use Conditions with own use scenarios
Future Scope

Support scaling and compliance checks

Consolidation of substance ES information into ES information
for a mixture
© 2014 SAP AG. All rights reserved.
This presentation and SAP‘s strategy and possible future developments are subject to change and may be changed by SAP at any time for any reason without notice. This document is
provided without a warranty of any kind, either express or implied, including but not limited to, the implied warranties of merchantability, fitness for a particular purpose, or non-infringement
Customer
2
ESComXML Data Model: Two Alternatives

First one based on the
ECHA Guidance 2010/12 for
the ES-Format

Second one based on the
simplified (harmonized)
ES-Format
© 2014 SAP AG. All rights reserved.
This presentation and SAP‘s strategy and possible future developments are subject to change and may be changed by SAP at any time for any reason without notice. This document is
provided without a warranty of any kind, either express or implied, including but not limited to, the implied warranties of merchantability, fitness for a particular purpose, or non-infringement
Customer
3
Two ESComXML Data Model Alternatives

ECHA Guidance 2010/12 for the ES-Format
 Used as base for structuring ES data in most IT-solutions

Simplified ES-Format
 introduced by ECHA based on the feedback from industry
that the 2010 format was too complex
 It serves as basis for the ESCom Phrase catalogue metadata
 is supported by ECHA IT tools

Main differences:
 Number and phrasing of sub-headings under section 2
 Level of structuring of condition of use information
© 2014 SAP AG. All rights reserved.
This presentation and SAP‘s strategy and possible future developments are subject to change and may be changed by SAP at any time for any reason without notice. This document is
provided without a warranty of any kind, either express or implied, including but not limited to, the implied warranties of merchantability, fitness for a particular purpose, or non-infringement
Customer
4
ESComXML: Status Quo

Two alternatives were discussed within IT Provider group

Two alternatives were presented to ESCom phrase group

ESCom Phrase Group has committed to support both
alternatives
 IT Provider group has to decide on the data model

We all agreed on that there will be only one 2.0 version
stable for at least 2 years
© 2014 SAP AG. All rights reserved.
This presentation and SAP‘s strategy and possible future developments are subject to change and may be changed by SAP at any time for any reason without notice. This document is
provided without a warranty of any kind, either express or implied, including but not limited to, the implied warranties of merchantability, fitness for a particular purpose, or non-infringement
Customer
7
ESCom: Next Steps

Meeting of IT Provider Group on May 20th to decide on the
preferred XML data model format

Finalize the ESComXML data model format

ESCom Standard Phrases Working Group to map the
catalogue phrases to the XML (adapt metadata)

Release and publish the ESComXML data model definition
plus guiding document
Publish a new version of the ESCom phrase catalogue
(planned Q4)

© 2014 SAP AG. All rights reserved.
This presentation and SAP‘s strategy and possible future developments are subject to change and may be changed by SAP at any time for any reason without notice. This document is
provided without a warranty of any kind, either express or implied, including but not limited to, the implied warranties of merchantability, fitness for a particular purpose, or non-infringement
Customer
8
SAP Team
Architect & Dev.
Product Owner
Michael Schalk
Mathias Glockner
Product Owner
Environment, Health & Safety
Senior Developer
Environment, Health & Safety
SAP AG
SAP AG
Dornierstrasse 3
88677 Markdorf
T +49 7544 970-266
M +49 151 62345826
mailto: m.schalk@sap.com
http://www.sap.com
Dornierstrasse 3
88677 Markdorf
T +49 7544 970-919
© 2014 SAP AG. All rights reserved.
mailto: mathias.glockner@sap.com
http://www.sap.com
This presentation and SAP‘s strategy and possible future developments are subject to change and may be changed by SAP at any time for any reason without notice. This document is
provided without a warranty of any kind, either express or implied, including but not limited to, the implied warranties of merchantability, fitness for a particular purpose, or non-infringement
Customer
9