Dear Friends,
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).
Thanks
Monday, April 12, 2010
Saturday, March 27, 2010
Meeting Regulatory challenges - In testing times
Dear Friends,
A recent market report suggested that nearly sixty percent of the companies they surveyed are not satisfied with their current IT systems. In another report it also highlighted that nearly half of user community will be dissatisfied with the slow rate of IT change in their enterprises. There is likelihood of this dissatisfaction to increase as companies may not invest hugely to change their current IT landscape. On the other side of the coin, organizations are reminded to fulfill or to meet the business requirements, regulatory requirements, and stakeholders’ expectations. Under these testing times, Business process management / Reengineering provide a framework, where organizations can improve the agility and regulatory and sustainable performance.
The typical challenges, an organization a face when it comes to this sphere of business is, more often EH&S / Sustainability need localized execution to meet the regional requirements. The principle steps to reach out to there is i) Assess the company footprint in the world of regulatory compliance / Sustainability, ii) Establish end – end business processes for meeting regulatory / compliance requirements, iii) Standardize the core processes that are stable, like 3rd party data services to manage and automatic processing of information, iv) Look for business process changes and identify localized business processes and adapt global solution and finally v) Migrate to new process, in a planned and systematic way involving key business users.
Thanks
A recent market report suggested that nearly sixty percent of the companies they surveyed are not satisfied with their current IT systems. In another report it also highlighted that nearly half of user community will be dissatisfied with the slow rate of IT change in their enterprises. There is likelihood of this dissatisfaction to increase as companies may not invest hugely to change their current IT landscape. On the other side of the coin, organizations are reminded to fulfill or to meet the business requirements, regulatory requirements, and stakeholders’ expectations. Under these testing times, Business process management / Reengineering provide a framework, where organizations can improve the agility and regulatory and sustainable performance.
The typical challenges, an organization a face when it comes to this sphere of business is, more often EH&S / Sustainability need localized execution to meet the regional requirements. The principle steps to reach out to there is i) Assess the company footprint in the world of regulatory compliance / Sustainability, ii) Establish end – end business processes for meeting regulatory / compliance requirements, iii) Standardize the core processes that are stable, like 3rd party data services to manage and automatic processing of information, iv) Look for business process changes and identify localized business processes and adapt global solution and finally v) Migrate to new process, in a planned and systematic way involving key business users.
Thanks
Wednesday, March 24, 2010
SAP EH&S Learning Thread
Dear Friends,
Few days back I got a mail asking if I take a step by step sessions on how to get into SAP EHS coverinpg important concepts and information. This thread is for that purpose. I will be periodically updating this thread with new information.
Thanks
jak
Learning EH&S – Session 1: What is Specification Database ?
Specification is the central database for EH&S. These data often referred to as Product data. This data includes regulations and laws concerning the products and ingredients. Example of specificaiton data include handling requirements, storage requirements and transport requirements, physical chemical characteristics, safety information and hazardous information. These specifications data are of different types based on the nature of the data they handle and also based on their close association with sub modules of EH&S like Hazard – related to Industrial Hygiene and safety, Waste Code – Related to Waste Management, Dangerous Goods Classification – Related to Dangeorous Goods Management and Substance – for Product Safety. So we can use the same concept to separate the specification database into Different specification Categories based on the broad category of data they contain or in EHS Sub module where they are used like i) Substances ii) Agent (Hazard) iii) Dangerous Goods Data iv) Waste Code.
Substance database contains header information and position data – often called value assignment information containing actual property information. For EH&S to work and function, these data needs to be created, used and updated at a regular intervels of time. It is possible to crate and update specificaiton information in SAP EHS, while for automated updating of the Specification database, 3rd party sources are used. The tools for updating the specification can be EH&S Expert - Open Content Connector – which uses xml format for updating the specification database – which will be covered separately in other session.
Specficiation database is closely linked as a specification model – which is related to Product Structure which we want to map into SAP EHS and at times its useful to sub – divide the broad specification category into small components to handle the data appropriately. For example It makes sense to separate Substance Specification into different Types based on exact piece of information they contain like Real Substances, Listed Substances, Un Listed Substances etc.
To create a specification in SAP EH&S access the T – Code, CG02BD, if you want to specifically create a specification database then CG02 (product Safety), CBIH92 (Industrial Hygiene and Safety), WAO02 (Waste Management).
Thanks
Few days back I got a mail asking if I take a step by step sessions on how to get into SAP EHS coverinpg important concepts and information. This thread is for that purpose. I will be periodically updating this thread with new information.
Thanks
jak
Learning EH&S – Session 1: What is Specification Database ?
Specification is the central database for EH&S. These data often referred to as Product data. This data includes regulations and laws concerning the products and ingredients. Example of specificaiton data include handling requirements, storage requirements and transport requirements, physical chemical characteristics, safety information and hazardous information. These specifications data are of different types based on the nature of the data they handle and also based on their close association with sub modules of EH&S like Hazard – related to Industrial Hygiene and safety, Waste Code – Related to Waste Management, Dangerous Goods Classification – Related to Dangeorous Goods Management and Substance – for Product Safety. So we can use the same concept to separate the specification database into Different specification Categories based on the broad category of data they contain or in EHS Sub module where they are used like i) Substances ii) Agent (Hazard) iii) Dangerous Goods Data iv) Waste Code.
Substance database contains header information and position data – often called value assignment information containing actual property information. For EH&S to work and function, these data needs to be created, used and updated at a regular intervels of time. It is possible to crate and update specificaiton information in SAP EHS, while for automated updating of the Specification database, 3rd party sources are used. The tools for updating the specification can be EH&S Expert - Open Content Connector – which uses xml format for updating the specification database – which will be covered separately in other session.
Specficiation database is closely linked as a specification model – which is related to Product Structure which we want to map into SAP EHS and at times its useful to sub – divide the broad specification category into small components to handle the data appropriately. For example It makes sense to separate Substance Specification into different Types based on exact piece of information they contain like Real Substances, Listed Substances, Un Listed Substances etc.
To create a specification in SAP EH&S access the T – Code, CG02BD, if you want to specifically create a specification database then CG02 (product Safety), CBIH92 (Industrial Hygiene and Safety), WAO02 (Waste Management).
Thanks
Saturday, March 6, 2010
REACh Use and Exposure mapping using SAP EH&S– Industrial Hygiene and Safety
Dear Friends,
Few days back I got a request asking if I write something on Use and Exposure in REACh and How SAP EHS is supported and also about eSDS and GHS. I try to write some high level information. This goes like this –
REACH legislation requires an understanding of how chemical substances are used, specifically, how they are handled throughout their life cycle from manufacture to disposal. For those substances that are hazardous, a risk assessment is required to be performed for each use to demonstrate that it is safe Expsoure scenarios needs to be preparated for hazardous substances tha are produced or imported > 10 t/a. Use and Exposure categories provide specific information tailored to the various user groups about what has to be borne in mind when the substances are used. For REACh Use & Exposure Scenario – Exposure assessment and Risk rating are carried out with Sophisticated 3rd party tools like ECETOC or yet to released CHESAR, for which the current system only the output is stored for reference.
Access the following url to see the Google Presentation on mapping of Use and Exposure in SAP EHS - IH&S Componenet.
http://docs.google.com/fileview?id=0B37ZjPJIaBcONTNiYWVjZDUtZmFiNy00MGNiLTk4ZjUtYWUwMTJhYjBjNWU5&hl=en
Advantages of the model is i) Simplified model taking data from existing systems and proposed REACh – which reduces work effort ii) Mapping multiple substances to one work area – for maintaining Use & Exposure Information further reduces the implementation and reporting effort which can make the system available in shortest possible time period . iii) Existing properties and data is used, as much as possible, such as the existing Use properties from REACh and EH&S.
Some of the classes that can be used without any problem for preparation of eSDS and GHS include– Data maintenance in Exposure Scenario, customer exposure and GHS LABELING. The GHS classification data almost all the data is existing except for some supplementary hazard statement and M-Factors information.
Thanks
Few days back I got a request asking if I write something on Use and Exposure in REACh and How SAP EHS is supported and also about eSDS and GHS. I try to write some high level information. This goes like this –
REACH legislation requires an understanding of how chemical substances are used, specifically, how they are handled throughout their life cycle from manufacture to disposal. For those substances that are hazardous, a risk assessment is required to be performed for each use to demonstrate that it is safe Expsoure scenarios needs to be preparated for hazardous substances tha are produced or imported > 10 t/a. Use and Exposure categories provide specific information tailored to the various user groups about what has to be borne in mind when the substances are used. For REACh Use & Exposure Scenario – Exposure assessment and Risk rating are carried out with Sophisticated 3rd party tools like ECETOC or yet to released CHESAR, for which the current system only the output is stored for reference.
Access the following url to see the Google Presentation on mapping of Use and Exposure in SAP EHS - IH&S Componenet.
http://docs.google.com/fileview?id=0B37ZjPJIaBcONTNiYWVjZDUtZmFiNy00MGNiLTk4ZjUtYWUwMTJhYjBjNWU5&hl=en
Advantages of the model is i) Simplified model taking data from existing systems and proposed REACh – which reduces work effort ii) Mapping multiple substances to one work area – for maintaining Use & Exposure Information further reduces the implementation and reporting effort which can make the system available in shortest possible time period . iii) Existing properties and data is used, as much as possible, such as the existing Use properties from REACh and EH&S.
Some of the classes that can be used without any problem for preparation of eSDS and GHS include– Data maintenance in Exposure Scenario, customer exposure and GHS LABELING. The GHS classification data almost all the data is existing except for some supplementary hazard statement and M-Factors information.
Thanks
Friday, February 26, 2010
Enterprise Carbon Management using SAP Product & REACh Compliance 2.0
Dear Friends,
Enterprise Carbon Management and Product Carbon Management is one of the Principle operational risks companies facing today. Comprehensive solutions should consist of green house gas monitoring, management and reporting capability. Last year SAP acquired CS and re-branded it as SAP Carbon Impact for specifically supporting the carbon calculation and Product Carbon calculation – which is a very good tool to capture GHG inventory, Offset project management, reduction targets etc. However integrating such reduction targets in the main Logistics system is a challenging requirement, the recent release of SAP Product & REACh Compliance 2.0 – would be a useful means to close this gaps.
Organizations can leverage the capabilities of SAP CI, SPRC 2.0 together with SAP BusinessObjects to ensure streamlined process for enterprise wide carbon management. SPRC 2.0 can be used to actually set requirements, check for carbon volumes from different suppliers and use SAP BusinessObjects for optimal decision supporting – using what if analysis.
In SAP EH&S – Carbon related property tree is created to accommodate the capture of key information related to Carbon Management, if required set its volumes in logistics checks and use the SPRC supply chain communication process to capture carbon volumes and also use the supplier self service to enter the details of carbon from shipping documents. For each product, the Bill of Materials, the shipping information utilized. Using the SAP Carbon Impact the total quantity of carbon can be calculated using built in equations.
These are some of the functionalities built into SAP Product and REACh Compliance 2.0 – which can be utilized for Enterprise Carbon management
•Organizational master data from the existing systems - default integration in to logistics and financial data
•The advantage of separating the carbon attributes as environmental characteristics easy handling of information and maintaining the data in the existing data structures.
•Characteristics to attribute carbon relevant - phrases and characteristics value assignment can be used for maintaining carbon relevant information
•Task management and workflows can be configured for supply chain communication and internal data management
•Partner and contact information to find customers for the supply chain collaboration – built in supplier self service for managing and accessing carbon relevant information and using SAP CI for carbon computation.
•Automatic xml or email processing data for importing carbon relevant attributes from supply chain communication
•Built in Report creation and report management and portfolio analysis
•Web services for posting carbon information to Climate registries for probable cap and trade management.
•Possible extension of making use of SAP BusinessObjects – Dashboards for sophisticated what if analysis
•Using SAP CI and SuPM integration for strategy management
Thanks
Enterprise Carbon Management and Product Carbon Management is one of the Principle operational risks companies facing today. Comprehensive solutions should consist of green house gas monitoring, management and reporting capability. Last year SAP acquired CS and re-branded it as SAP Carbon Impact for specifically supporting the carbon calculation and Product Carbon calculation – which is a very good tool to capture GHG inventory, Offset project management, reduction targets etc. However integrating such reduction targets in the main Logistics system is a challenging requirement, the recent release of SAP Product & REACh Compliance 2.0 – would be a useful means to close this gaps.
Organizations can leverage the capabilities of SAP CI, SPRC 2.0 together with SAP BusinessObjects to ensure streamlined process for enterprise wide carbon management. SPRC 2.0 can be used to actually set requirements, check for carbon volumes from different suppliers and use SAP BusinessObjects for optimal decision supporting – using what if analysis.
In SAP EH&S – Carbon related property tree is created to accommodate the capture of key information related to Carbon Management, if required set its volumes in logistics checks and use the SPRC supply chain communication process to capture carbon volumes and also use the supplier self service to enter the details of carbon from shipping documents. For each product, the Bill of Materials, the shipping information utilized. Using the SAP Carbon Impact the total quantity of carbon can be calculated using built in equations.
These are some of the functionalities built into SAP Product and REACh Compliance 2.0 – which can be utilized for Enterprise Carbon management
•Organizational master data from the existing systems - default integration in to logistics and financial data
•The advantage of separating the carbon attributes as environmental characteristics easy handling of information and maintaining the data in the existing data structures.
•Characteristics to attribute carbon relevant - phrases and characteristics value assignment can be used for maintaining carbon relevant information
•Task management and workflows can be configured for supply chain communication and internal data management
•Partner and contact information to find customers for the supply chain collaboration – built in supplier self service for managing and accessing carbon relevant information and using SAP CI for carbon computation.
•Automatic xml or email processing data for importing carbon relevant attributes from supply chain communication
•Built in Report creation and report management and portfolio analysis
•Web services for posting carbon information to Climate registries for probable cap and trade management.
•Possible extension of making use of SAP BusinessObjects – Dashboards for sophisticated what if analysis
•Using SAP CI and SuPM integration for strategy management
Thanks
Sunday, February 21, 2010
REACh Compliance 1.0 to SAP Product and REACh Compliance 2.0 – My journey along
Dear Friends,
It’s almost two years back when I first started working on SAP REACh Compliance. My first exercise understood the development of eSDS based on existing SAP EH&S Classes and characteristics and creation of Extended SDS Template using WWI report tool. By the time it completed we ventured into mapping and interfacing with IUCLID – after a thoughtful discussions we finally concluded it should be based on XI technology with the support of MDM.
At that time the company where I was working (Satyam) participated in SAP REACh Compliance Ramp Up initiative. After a brief stint of one to two days- it becomes SAP REACh Compliance 1.1. When SRC 1.1 is released it has basic functionalities like i) Organizational Data management ii) Material Management iii) Substance Management iv) Legal Process Management v) Supply Chain Communication and vi) Document Management Integration. With the release came two very exciting WebEx presentations on SRC 1.1 with accessibility to wonderful configuration documents. I believe it’s the first time in the history of SAP EH&S product landscape that – literature of that sort was made available publicly. I believe Dr. Marko together Kieran are trendsetters for the availability of literature, which is now carried to almost all new releases of SAP EH&S and Sustainability products.
When SAP REACh Compliance 1.1 is released there were definite missing segments like missing bulk material assessment functionality, SIEF integration segments and IUCLID5 interface. Even at that time was not clear how SAP intended to support Use and Exposure Assessment – as SRC released only Use Descriptors for carrying out Risk Assessment. Even by that time REACh Pre-Registration activity was completed, then it is also realized that there is a missing a Registration Projects integration– Pre-Registration activity – by which all the non available legal entities to be created automatically with a indication about nature of data that should be shared with them.
Then after a span of about 4 months – SAP released SP02 with a useful set of functionalities like integration of Phrases into Material Master and Bulk Material Assessment functionality, Campaign management functionality and Portfolio Reporting capability.
After a span of almost 1 year SAP released major extension of SAP REACh Compliance 1.1 –called SAP Product & REACh Compliance 2.0. This new product encompasses almost all the functionalities of legacy Compliance for Product software. The major features like supporting IMDS, AIAG/IEEE, RoHS, China RoHS and IPCPDMC Conversion Services. Registration Project Management and IUCLID5 Integration for meeting the Product Compliance Management, Component Management, Supply Chain Collaboration Management including Supplier Self Service and Reporting.
The release of SAP PRC supports and matures the REACh Compliance 1.0 to a full fledged module supporting– Cost Monitoring, Volume Monitoring, Endpoint Management, Registration Project Management, SIEF project and Data Export and Reporting as per the original SAP REACh Sales Presentation. One thing which I noticed is this product evolved almost in parallel to REACh Regulation and it has also given me an insight into Product Maturation cycle and how a product evolves into complete offering based on regulatory requirements. Though I have seen the functionality of CfP very closely, would like to work on SPRC sooner or later.
Now what I look forward to is a definite "Best Practices scenario demonstrating the requirements of REACH using SAP EH&S, SAP Product and REACh Compliance and 3rd Party Tools" - which reminds me of very beautiful quote “ Miles to Go before I sleep” in Stopping by Woods on a Snowy Evening – there is so much to learn and accomplish in one's life !
Thanks
It’s almost two years back when I first started working on SAP REACh Compliance. My first exercise understood the development of eSDS based on existing SAP EH&S Classes and characteristics and creation of Extended SDS Template using WWI report tool. By the time it completed we ventured into mapping and interfacing with IUCLID – after a thoughtful discussions we finally concluded it should be based on XI technology with the support of MDM.
At that time the company where I was working (Satyam) participated in SAP REACh Compliance Ramp Up initiative. After a brief stint of one to two days- it becomes SAP REACh Compliance 1.1. When SRC 1.1 is released it has basic functionalities like i) Organizational Data management ii) Material Management iii) Substance Management iv) Legal Process Management v) Supply Chain Communication and vi) Document Management Integration. With the release came two very exciting WebEx presentations on SRC 1.1 with accessibility to wonderful configuration documents. I believe it’s the first time in the history of SAP EH&S product landscape that – literature of that sort was made available publicly. I believe Dr. Marko together Kieran are trendsetters for the availability of literature, which is now carried to almost all new releases of SAP EH&S and Sustainability products.
When SAP REACh Compliance 1.1 is released there were definite missing segments like missing bulk material assessment functionality, SIEF integration segments and IUCLID5 interface. Even at that time was not clear how SAP intended to support Use and Exposure Assessment – as SRC released only Use Descriptors for carrying out Risk Assessment. Even by that time REACh Pre-Registration activity was completed, then it is also realized that there is a missing a Registration Projects integration– Pre-Registration activity – by which all the non available legal entities to be created automatically with a indication about nature of data that should be shared with them.
Then after a span of about 4 months – SAP released SP02 with a useful set of functionalities like integration of Phrases into Material Master and Bulk Material Assessment functionality, Campaign management functionality and Portfolio Reporting capability.
After a span of almost 1 year SAP released major extension of SAP REACh Compliance 1.1 –called SAP Product & REACh Compliance 2.0. This new product encompasses almost all the functionalities of legacy Compliance for Product software. The major features like supporting IMDS, AIAG/IEEE, RoHS, China RoHS and IPCPDMC Conversion Services. Registration Project Management and IUCLID5 Integration for meeting the Product Compliance Management, Component Management, Supply Chain Collaboration Management including Supplier Self Service and Reporting.
The release of SAP PRC supports and matures the REACh Compliance 1.0 to a full fledged module supporting– Cost Monitoring, Volume Monitoring, Endpoint Management, Registration Project Management, SIEF project and Data Export and Reporting as per the original SAP REACh Sales Presentation. One thing which I noticed is this product evolved almost in parallel to REACh Regulation and it has also given me an insight into Product Maturation cycle and how a product evolves into complete offering based on regulatory requirements. Though I have seen the functionality of CfP very closely, would like to work on SPRC sooner or later.
Now what I look forward to is a definite "Best Practices scenario demonstrating the requirements of REACH using SAP EH&S, SAP Product and REACh Compliance and 3rd Party Tools" - which reminds me of very beautiful quote “ Miles to Go before I sleep” in Stopping by Woods on a Snowy Evening – there is so much to learn and accomplish in one's life !
Thanks
Friday, February 12, 2010
Lessons from Toyota - Extending to REACh !!!!
Dear Friends,
Recently Toyota recalled some 2.3 million vehicles to correct an unintended acceleration caused by a software failure while switching between different means of break mechanism. To those who are not aware of it – In electric brand Toyota applies two types of breaks – while switching from mode of break mechanism to another system breaks hold for less than second, making the passenger feel momentarily that his engine breaks are failed.
Assume the similar challenge for REACh Compliance, when a SuperPaint manufacturer produces products, using substances which are not registered or for those there is not Use and Exposure is recorded? The historic recall of toys or recall of cell phones few years back is just a tip of the iceberg, as far as exceeding levels of restricted substances can do damage to the business. The recent extension of SAP REACh Compliance 1.1 to SAP Product and REACh Compliance 2.0 (called SPRC 2.0) will be of immense use for regulatory requirements like RoHS, China RoHA, AIAG, IMDS and REACh.
SPRC helps in automatically identify all substances that fall under the regulations using logistical, production and purchasing processes and continuous tracking for substance complianceOverview of Capabilities of SAP Product and REACh Compliance 2:
- Managing the specification Data
- Worklist based management of specification data
- Automatic / Manual Compliance checks against varous check processes
- Supply Chain communication for additional data - using Supplier portal and Campaigan management
- Compliance analysis and compliance reporting including electronic data exchange by means of various exchange formats, for example AIAG and IMDG.
Thanks
Recently Toyota recalled some 2.3 million vehicles to correct an unintended acceleration caused by a software failure while switching between different means of break mechanism. To those who are not aware of it – In electric brand Toyota applies two types of breaks – while switching from mode of break mechanism to another system breaks hold for less than second, making the passenger feel momentarily that his engine breaks are failed.
Assume the similar challenge for REACh Compliance, when a SuperPaint manufacturer produces products, using substances which are not registered or for those there is not Use and Exposure is recorded? The historic recall of toys or recall of cell phones few years back is just a tip of the iceberg, as far as exceeding levels of restricted substances can do damage to the business. The recent extension of SAP REACh Compliance 1.1 to SAP Product and REACh Compliance 2.0 (called SPRC 2.0) will be of immense use for regulatory requirements like RoHS, China RoHA, AIAG, IMDS and REACh.
SPRC helps in automatically identify all substances that fall under the regulations using logistical, production and purchasing processes and continuous tracking for substance complianceOverview of Capabilities of SAP Product and REACh Compliance 2:
- Managing the specification Data
- Worklist based management of specification data
- Automatic / Manual Compliance checks against varous check processes
- Supply Chain communication for additional data - using Supplier portal and Campaigan management
- Compliance analysis and compliance reporting including electronic data exchange by means of various exchange formats, for example AIAG and IMDG.
Thanks
Subscribe to:
Posts (Atom)