JIT which stands for Just in Time has been a…
I remember my research days some 20 years back working on presentation on Cleaner Production Technologies and Circular Economy. This CE has taken prominence in recent years due to increased pressure on Natural resources and changing consumer behavior. As we all know increased resource consumption results in increased waste generation which returns to environment, if not properly managed. That is the linear economic model (take, make, use, dispose) is an unsustainable practice. Recent heightened interest in carbon emission management, smart cities, waste management, water usage etc, are also acting as enablers for adoption of CE models. Given the recent explosion of technologies like Big Data & IoT, mobility changes, there seems tremendous opportunity to enable rapid adoption of CE in manufacturing and other sectors.
This is not the first time that we have been…
SAP Software technologically has been changed over the years and currently it is available with version S/4 HANA 1909. Each version differs from the previous version in terms of big shift in the technology and functionality and user experience. There are majorly two different versions available for EHS. The modules like Incident Management, Risk Assessment, Environmental Management, Management of Change Products and Product Compliance modules comes under the SAP LoB or S/4 HANA Core modules. The other modules like SAP EHS Product Safety, GLM, SVT and Dangerous Goods Mgmt and Product Compliance – DI falls under the compatibility version of S/4 HANA 1909 Release. Compatibility versions are the ones which are continued to ensure business continuity and SAP will eventually may/ may not move the functionalities into core.
There are various options available when it comes to implementing the SAP EHS solution to S/4 HANA, that migrating the current ECC ERP version to S/4 HANA. Be it called side car scenario, System conversion, Landscape Transformation or even Green Field implementation. In this blog I would like to cover few basics around SAP S/4 HANA system conversion and how you can convert or implement EHS system for your client.
A recent study pointed out that on an average 3.5 clinical encounters are recorded per patient per Year in United States and number of such encounters are equally same for employees when its comes to their annual medical examinations, vaccination programmes or even adhoc medical check-ups.
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.
Incident / Accident Management is requirement for many guidelines and regulations and needed to be properly managed within an organization. If an incident is not properly managed it results in loss of information, chances for incident avoidance in future and monetary challenges. Deep Learning Techniques like Tensorflow / Keras along with OpenCV and other libraries can be used to automatically manage incidents / accidents within an organization.
Safety Data Sheet suppliers are usually required to provide emergency telephone number in section 1 of the SDSs. Some regulations even recommend having 24/7 local emergency telephone numbers. OSHA clearly states that the telephone number should be provided for person / entity who is either knowledgeable of the hazardous material being shipped and who has comprehensive emergency response and incident mitigation information for that material. However, companies are facing issues with availability of knowledgeable persons / staff who can be available for 24/7 to carry out such tasks.