EH&S Industrial Hygiene and Safety SAP Best Practices for Chemicals (India)

SAP Best Practices

© SAP 2008 / Page 2

Purpose The purpose of to describe business processes related to Industrial Hygiene &

Safety.

Benefits Fulfill several legal requirements when hazardous substances such as paints or

solvents are handled or processed by employees

Key process flows covered Define and Edit Work Areas Maintain Industrial Hygiene and Safety Data Set Up Integration with Storage Locations Maintain Exposure Profile Enter Measurement Values for Agents in the Exposure Profile Display a Hazardous Substances Inventory Define Safety Measures Create Work-Area-Related SOPs Display Existing SOPs

Purpose and Benefits:

Scenario Overview – 1

© SAP 2008 / Page 3

Required SAP ECC 6.00 EhP3

Company roles involved in process flows EH&S Clerk

SAP Applications Required:

Scenario Overview – 2

© SAP 2008 / Page 4

Scenario Overview – 3

EH&S Industrial Hygiene & Safety

The purpose of this document is to describe the industrial hygiene and safety scenario of SAP Best Practices for Chemicals.

This scenario is triggered by the creation of a new work area for handling hazardous substances, by first or changed use of a hazardous substance in a certain work area, or by any other change of safety-relevant data. The purpose of this scenario is to fulfill several legal requirements when hazardous substances such as paints or solvents are handled or processed by employees. The industrial hygienist can map the following work processes:

Defining work areas

Maintaining, evaluating and managing the exposure log

Creating hazardous substance registers

Creating work-area-related standard operating procedures

To define useful safety measures, we must first collect and prepare the information required, such as data about the available technical equipment and the exposure situation of the work area. The overall goal of this scenario is to continually and effectively reduce the risk of person-related and environment accidents and damage.

Detailed Process Description:

© SAP 2008 / Page 5

Production/Quality Responsible

Product/Packaging Developer

Product ManagerBusiness

BenefitsChemical Company Supplier Authority

You can use the work area concept to continually and effectively improve the safety situation of the employees concerned.

This is very helpful for evaluations performed at a later stage.

In this scenario, the integration to the storage locations is used to upload data from inventory management for use in the hazardous substances register.

Define Work area

Setting up Integration with Storage

Locations

Maintaining Exposure Profile

Entering Measurement

Values for Agents in the Exposure

Profile

Generating a Hazardous Substances

Register

Maintaining Industrial Hygiene and Safety Data

Business View: Industrial Hygiene & Safety (1)

© SAP 2008 / Page 6

Production/Quality Responsible

Product/Packaging Developer

Product ManagerBusiness

BenefitsChemical Company Supplier Authority

You can include all the agents (for example hazardous substances, noise, mechanical hazards, mental stress) that exist in the company.

The Hazardous Substances Register is displayed, including information on work areas and related agents, amounts stored, received and issued (as far as available in the system) and substance classification.

Chemical Company Supplier Authority

Defining Safety Measures

Displaying Existing SOPs

Creating Work-Area-Related SOPs

Business View: Industrial Hygiene & Safety (2)

© SAP 2008 / Page 7

SAP ERP

Registering the Technical EquipmentCBIH02

Work Area Definition in GeneralCBIH02

Exposure Profile: Adding/Qualifing Agents

CBIH02

Perform Risk AssessmentCBIH12

Setting up Safety Measures for Work Areas

CBIH02

Creating and Release SOPCBIH12

Displaying the Hazardous Substance Register

CBIH63

Interactive View: Industrial Hygiene & Safety

© SAP 2008 / Page 8

Scenario Overview

Collect and maintain data on exposure to hazardous substances

Define safety procedures and apply to plant procedures to ensure safe working conditions

Define Safety Procedures

Define Product Master Data

Requirements

Enter Exposure Data, Collect

Data from Plants and

Warehouses

Map Safety Procedures to

Plant Procedures (Maintenance

etc.)

Generate Reports and

Registers

Business Requirement: Comply with substance exposure regulations and safety procedures

© SAP 2008 / Page 9

Process Flow DiagramEH&S Industrial Hygiene & Safety

EH

&S

Cle

rk

Ev

en

t

Define and edit Work

Areas

IHS legal requirement

Maintain IH&S data

Set up Integration with SLOC

Maintain Exposure

profile

Enter Measurement

Values for Agents

Display Substance inventory

Define Safety

Measure

Create SOP for

Work Area

Display SOP

© SAP 2008 / Page 10

Standard Operating Procedures

© SAP 2008 / Page 11

Legend

Symbol Description Usage Comments

To next / From last Diagram: Leads to the next / previous page of the Diagram

Flow chart continues on the next / previous page

Hardcopy / Document: Identifies a printed document, report, or form

Does not correspond to a task step in a document; instead, it is used to reflect a document generated by a task step; this shape does not have any outgoing flow lines

Financial Actuals: Indicates a financial posting document

Does not correspond to a task step in a document; instead, it is used to reflect a document generated by a task step; this shape does not have any outgoing flow lines

Budget Planning: Indicates a budget planning document

Does not correspond to a task step in a document; instead, it is used to reflect a document generated by a task step; this shape does not have any outgoing flow lines

Manual Process: Covers a task that is manually done

Does not generally correspond to a task step in a document; instead, it is used to reflect a task that is manually performed, such as unloading a truck in the warehouse, which affects the process flow.

Existing Version / Data: This block covers data that feeds in from an external process

Does not generally correspond to a task step in a document; instead, this shape reflects data coming from an external source; this step does not have any incoming flow lines

System Pass / Fail Decision: This block covers an automatic decision made by the software

Does not generally correspond to a task step in the document; instead it is used to reflect an automatic decision by the system that is made after a step has been executed.

Diagram Connection

Hardcopy / Document

Financial Actuals

Budget Planning

Manual Proces

s

Existing Version /

Data

System Pass/F

ail Decisio

n

Symbol Description Usage Comments

Band: Identifies a user role, such as Accounts Payable Clerk or Sales Representative. This band can also identify an organization unit or group, rather than a specific role.

The other process flow symbols in this table go into these rows. You have as many rows as required to cover all of the roles in the scenario.

Role band contains tasks common to that role.

External Events: Contains events that start or end the scenario, or influence the course of events in the scenario.

Flow line (solid): Line indicates the normal sequence of steps and direction of flow in the scenario.Flow line (dashed): Line indicates flow to infrequently-used or conditional tasks in a scenario. Line can also lead to documents involved in the process flow.

Connects two tasks in a scenario process or a non-step event

Business Activity / Event: Identifies an action that either leads into or out of the scenario, or an outside Process that happens during the scenario

Does not correspond to a task step in the document

Unit Process: Identifies a task that is covered in a step-by-step manner in the scenario

Corresponds to a task step in the document

Process Reference: If the scenario references another scenario in total, put the scenario number and name here.

Corresponds to a task step in the document

Sub-Process Reference: If the scenario references another scenario in part, put the scenario number, name, and the step numbers from that scenario here

Corresponds to a task step in the document

Process Decision: Identifies a decision / branching point, signifying a choice to be made by the end user. Lines represent different choices emerging from different parts of the diamond.

Does not usually correspond to a task step in the document; Reflects a choice to be made after step execution

<F

unct

ion>

Ext

erna

l to

SA

P

Business Activity /

Event

Unit Process

Process Reference

Sub-Process

Reference

Process

Decision