ESCom XML 2.0 Implementation and

Version 2.1 Status

Leo Oves

Proprietary and Confidential. © 3E Company Environmental, Ecological and Engineering.

Do not distribute without authorization from Verisk 3E.

Verisk 3E and Intelligent Compliance

ACHIEVEProduct Compliance

OPTIMIZEGlobal Chemical Registration,

Notification & Reporting

INCREASEChemical & Workplace Safety

IMPROVESupply Chain Stewardship

STREAMLINERegulatory Research & Monitoring

ENHANCEHazard Communication /

SDS Authoring

Proprietary and Confidential. © 3E Company Environmental, Ecological and Engineering.

Do not distribute without authorization from Verisk 3E.

REACH Supply Chain Communication

Registration

(ECHA)

REACH-IT

IUCLID (Identification,

properties, hazards)

Chesar (CSA – CSR – ES

for SDS + ESCom XML)

i6z

Authoring software 1

(Registrant), e.g. 3E Generate

(SDS ES)

ESCom XML

Use maps by IS for

CSA (OC’s, RMM’s)Excel

Authoring software 2

(Downstream User 1),

(SDS ES)

ESCom XML

Authoring software 3

(Downstream User 2),

(SDS ES)

ESCom XML

ESCom XML

Presented by the ESCom Phrase/XML groups (in part) @ ENES 11

ESCom XML 2.0 Pilot Project

Proprietary and Confidential. © 3E Company Environmental, Ecological and Engineering.

Do not distribute without authorization from Verisk 3E.

ESCom XML Pilot Objectives and Structure

■ Initiative: Pilot project with ESCom XML 2.0, involving key players within the chemical

industry chain

■ Objectives:

□ Demonstrate that the ESCom Package is fit for purpose and works

□ Collect information on interoperability, pro’s/con’s, and implementation lessons

Proprietary and Confidential. © 3E Company Environmental, Ecological and Engineering.

Do not distribute without authorization from Verisk 3E.

Pilot Details

■ Participants: 1 manufacturer, 1 distributor, 1 downstream user, 4 IT providers

■ 10 Exposure scenarios (mainly, worker) with an average of 7 contributing scenarios

created by IT providers

■ Test scenarios

□ Chesar => IT Providers

□ IT Provider / Manufacturer => IT Provider / Distributor

□ IT Provider / Manufacturer => IT Provider / Downstream user

□ IT Provider / Distributor => IT Provider / Downstream user

Proprietary and Confidential. © 3E Company Environmental, Ecological and Engineering.

Do not distribute without authorization from Verisk 3E.

Pilot Results

■ ESCom XML data exchange is successful

■ Use of the ESCOM phrase library is critical

■ Feedback on the identified issues and enhancements has been collected and discussed

■ Manual ES data input in EHS IT system (including creation of ES/CS in EHS IT system): 2-4 hrs (120 - 240 min) per ES (depending on level of experience of employees)

■ Electronic ES data input in EHS IT system

□ Without missing phrases (non-ESCom phrases): ~5 min per ES (quality check/review)

□ With 25% missing phrases (manual replacement by non-ESCom phrases): 30 - 60 min per ES plus ~5 min per ES (quality check/review)

Time savings (no missing phrases): 115 – 235 min per ES

Time savings (25% missing phrases): 85 – 175 min per ES

* NOTE: the initial effort to implement ESCom XML (interfaces, data migration) is not taken into account

ESCom XML 2.0 Implementation at Verisk 3E

Proprietary and Confidential. © 3E Company Environmental, Ecological and Engineering.

Do not distribute without authorization from Verisk 3E.

3E Generate Implementation - I

■ Scenario 1

□ 3 ESs with 9 CSs (generated from Chesar 3.2)

□ 16 pages; 60 phrases “free text”

■ Estimation of saved time

□ Manual effort

■ Time to create materials = 12 minutes

■ 16 pages * 0.5 hours = 8 hours

■ QC = 45 min

■ Total time = ca. 9 hours

□ ESCom import

■ 3.54 min to import file, generate document

■ 60 phrases to create and assign = 1 min per phrase = 60 min.

■ QC = 45 min

■ Total time = ca. 2 hours

■ Efficiency gain: 9 hours vs. 2 hours

Proprietary and Confidential. © 3E Company Environmental, Ecological and Engineering.

Do not distribute without authorization from Verisk 3E.

3E Generate Implementation - II

■ Scenario 2

□ 2 ESs with 4 CSs (generated from Chesar 3.2)

□ 18 pages; 37 phrases “free text”

■ Estimation of saved time

□ Manual effort

■ Time to create materials = 6 minutes

■ 18 pages * 0.5 hours = 9 hours

■ QC = 30 min

■ Total time = ca. 9.5 hours

□ ESCom import

■ 4.27 min to import file, generate document

■ 37 phrases to create and assign = 37 min.

■ QC = 30 min

■ Total time = ca. 1.1 hours

■ Efficiency gain: 9.5 hours vs. 1.1 hours

Proprietary and Confidential. © 3E Company Environmental, Ecological and Engineering.

Do not distribute without authorization from Verisk 3E.

Before ESCom After ESCom

■ Export and import file

■ Quality check/review

■ CSR/eSDS reading

■ Data extraction

■ Data mapping

■ Data re-entry

■ Quality check/review

On behalf of the ESCom XML Group

ESCom XML 2.1 Status

Proprietary and Confidential. © 3E Company Environmental, Ecological and Engineering.

Do not distribute without authorization from Verisk 3E.

ESCom XML 2.1 Status

■ ESCom XML v2.1 draft is available at https://github.com/esdscom/escom-xml

■ ESCom XML v2.1 is published under the same Creative commons license that is

used for ESCOM phrases

■ The draft includes all changes agreed upon during joint ESCom Phrase and ESCom

XML groups meeting in October of 2018

■ The open and closed issues are available in https://github.com/esdscom/escom-

xml/issues/ directory

■ As soon as you created your Github account, you can comment on ESCom issues or

raise new issues for changes/enhancements

■ V2.1 release is expected May-June, 2019

Questions