SAP Environmental Compliance 3.0 was historically used to manage the emission and environmental compliance (EC) requirements. However SAP recently released Environmental Management (EM) module as part of EHS management within ECC - Component Extensions and also as part of S4HANA releases. I happened to work very closely with Environmental Compliance 2.0 / 3.0 and have previously set up proof of concept system for Environmental Management as well.
Few days back many news agencies reported J&J recalled 33,000 bottles of its baby powder lot bearing the number 22318RB after health regulators found traces of asbestos. Its not uncommon that we hear such reports from different products which undergo recall to manage the risk and lawsuits. Usually such analysis of products when they are in supply chain is a critical requirement for many companies.
Recently Greenhouse Gas emissions account to major concern owning its beings a potential cause of Global warning. There are various sources / sinks for GHG emissions be it due to use of energy consumption or practices of agriculture methods or other anthropogenic sources.
It was almost 15 years since I worked on multi-objective Air Quality Monitoring site selection using Geographic Information System. At that time use of ArcGIS / Python was in nascent stage in ESRI product. We were using python as a scripting languages with use around some minor level of automation.
As mentioned in the CCPS Process Safety Guide, an essential element of any improvement program is measure of existing and future performance. The proper analysis of such measures like Leading and Lagging metrices is critical for successful process safety management. Generally, a safety pyramid consists of mix of three types of metrices like Lagging metrices – which are retrospective set of measures, Leading metrices – which are forward looking metrices and finally Near-miss which are less severe incidents, which however are very good indicators for future likelihood.