Few days back I happened to work with Beta version of ECHA new tool called Chesar (CHemical Safety and Assessment tool). This is a tool developed to support in preparing Chemical Safety Assessment and Chemical Safety Report. It has features like getting the data fro IUCLID, Assessment and Exposure Scenario building and generation of Chemical safety report. The exposure estimatio in Chesar is based ECETOC and ERC / EUSES and it can even use external exposure estimation tools. When I created a CSR, it automatically created 45 pages dossier as per the CSR format.
After working with SAP REACh Compliance for so many months, this tool has given me very good insight into a functionality which, I was assuming for past 2 years and also a probable direction on Best Practice Scenario for achieving REACh Compliance cosisting of SAP REACh Compliance and 3rd party tools!
When I see this tool with an overall SAP REACh Compliance business process, it fits into the overall framework either during initial transfer of all uses and substance information directly into IUCLID (which is carried out using IUCLID - EH&S interface) and using the information for actually carrying out exposure estimation, or even after final legal process check and end point gap analysis and transfer the data into IUCLID5 (as per original SAP REACh Compliance 1.1. business logic).
So from SAP EH&S, it would be useful to create a Chesar Property tree consisting of administrative data, Physicochemical data, Environmetnal hazard information and trafer that information for Exposure estimation - since these are the data which system needs. I understad, with the existing REACh property trees (classes/characterisitcs) within SAP REACh, it should be possible to create a flexible property for ease of use for Chesar, it would not only reduce the burden of maintaining additional endpoing documents which are not required for Exposure assessment, but also ease of use. Once exposure estimation is carried out in IUCLID 5.2 it is good idea to take the data back into SAP EH&S eSDS property tree and use that for creation of eSDS or even create eSDS in Chesar (need to wait till June 2010).