Transcript Slide 1

ExESS
REACH compliancy Monitor
9/03/2012
ExESS for REACH Compliancy Monitoring
1
ExESS IT toolbox
ExESS for REACH compliancy monitoring
9/03/2012
ExESS for REACH Compliancy Monitoring
2
Concept in ExESS
1
existing IT
and data
2
Add REACH
data input
3
ExESS = SIMS
4
Define Rules and
Scores
REACH
Compliancy
Monitor
extra
data
REACH
DATA
IN
Inventories
extra
data
EH&S
LOGIC &
RULES
ExESS
as
SIMS
REACH
Cockpit
OUT
extra
data
Bring relevant REACH data in ExESS and apply monitoring logic
9/03/2012
ExESS for REACH Compliancy Monitoring
3
Step 1
Define the need of Relevant Data and identify the source
9/03/2012
ExESS for REACH Compliancy Monitoring
4
Step 2
Bring all the data together in ExESS
9/03/2012
ExESS for REACH Compliancy Monitoring
5
Step 3
Define, Identify and create the logical rules in ExESS
IF <condition1> THEN < Score for KPI = X1
IF <condition2> THEN < Score for KPI = X2
IF <condition3> THEN < Score for KPI = X3
IF <condition4> THEN < Score for KPI = X4
….
IF <conditionN> THEN < Score for KPI = Xn
Sum of Xi = Total KPI Score
KPI levels < level 1
Level 1 < KPI level < level 2
Level 2 < KPI Level
9/03/2012
NOK
WARNING
OK
ExESS for REACH Compliancy Monitoring
6
Step 3
Define, Identify and create the logical rules in ExESS
9/03/2012
ExESS for REACH Compliancy Monitoring
7
Step 4
Present and Report the results
Condition
KPI Score
Final Result
9/03/2012
ExESS for REACH Compliancy Monitoring
8
Step 4
Present and Report the results
9/03/2012
ExESS for REACH Compliancy Monitoring
9
Step 4
Present and Report the results
9/03/2012
ExESS for REACH Compliancy Monitoring
10
Step 4
Present and Report the results
9/03/2012
ExESS for REACH Compliancy Monitoring
11
Step 5
Use ExESS task Management and ExESS based email concepts
to organize the REACH Compliancy follow up
9/03/2012
ExESS for REACH Compliancy Monitoring
12
Step 5
Use ExESS task Management and ExESS based email concepts
to organize the REACH Compliancy follow up
9/03/2012
ExESS for REACH Compliancy Monitoring
13
REACH compliancy communication
Communication can be done based on :
• Internal reporting and access control to ExESS cockpit screens
• Mail system
• Links to other IT or communication systems
• other creative solutions…
9/03/2012
ExESS for REACH Compliancy Monitoring
14
ExESS interfacing
MS office
•
•
•
•
•
•
MS Windows Scheduled task
COPY/PASTE
Excel import
Web Services
Excel export
WORD document generation
Excel document generation
…
Tailor-made interfacing
• CSV, tab delimited, XML, …
ExESS API
• Dedicated developed Application Interface
SAP Environment, Health and Safety - Open
Content Connector (EH&S-OCC)
9/03/2012
ExESS for REACH Compliancy Monitoring
15
ExESS IT structure
9/03/2012
ExESS for REACH Compliancy Monitoring
16
ExESS interfacing : File exchange versus API
ExESS ↔ ERP or ext. IT : file exchange
Existing
ERP/IT systems
Data
file
Manual or tool
(Windows sheduled tasks)
Existing
ERP/IT systems
Web application
9/03/2012
QUESTION
ANSWER
API
ExESS API : Dedicated developed Application Interface
ExESS for REACH Compliancy Monitoring
17
ExESS – SAP Open Content Connector (EH&S-OCC)
http://www.sdn.sap.com/irj/sdn/index?rid=/webcontent/uuid/8a0cfd8f-0801-00105080-c951d990a0ff
The EH&S Open Content Connector (OCC) is an open XML-based interface to load
external content into the SAP EH&S specification database. It focuses on content
for regulatory data for product safety and dangerous goods. Other scopes like
physical/chemical data or regulatory data for other EH&S modules , etc.) are also
supported.
SAP EH&S
SAP EH&S – OCC
REMARK : The integration based on this interface is made tailor/made to match
the ExESS and the SAP properties
9/03/2012
ExESS for REACH Compliancy Monitoring
18
ExESS, more with less
Americas – Asia - Europe
LISAM SYSTEMS | HEMMIS Office Belgium | Vlaanderenstraat 3A - B-8501 Heule |
www.lisam.com
email : [email protected]
Office +32 (0)56 372637 | Fax +32 (0)56 372324 | Mobile +32 (0)477 292519
Lisam America, Inc.
3131 E. 29th Street, Ste. E
Bryan, Texas 77802
+1 979.595.1444
Although the information in this presentation has been presented in good faith and is believed
to be correct at the time of compilation, LISAM SYSTEMS GROUP cannot assure this
presentation to be free of errors or omissions and will not be responsible assuring the
completeness or accuracy of the information in this presentation
9/03/2012
ExESS for REACH Compliancy Monitoring
19