888_erp607_process_overview_en_xx.ppt

Work Clearance Management

SAP Best Practices for Chemicals

© 2014 SAP SE or an SAP affiliate company. All rights reserved. 2

Purpose, Benefits, and Key Process Steps

Purpose This process creates a safe environment for the maintenance staff to perform maintenance work. In addition, applicable environmental safeguards can be adhered to and the reliability of the assets is guaranteed.

Benefits• A component with which the safety measures during maintenance work at technical objects can be controlled and

monitored

• The WCM process is fully integrated with the work order process

• All permit in WCM objects must be issued before execution of actual maintenance

• A protection that ensures that a technical object that is managed as an item in an Operational WCD can only be orderly tagged or untagged from certain Operational WCDs

Key Process Flows Covered• Creating Maintenance Order with WCM Requirement

• Creating Work Approval (WAP)

• Creating Work Clearance Application (WCA)

• Creating additional application Hot Work

• Creating Operational Work Clearance Document (WCD)

• Performing Permit Approval process

• Performing operational cycle of Lockout / Tag out

• WCM objects for a planned maintenance order are generated from a maintenance plan


Required SAP Applications and Company Roles

Required SAP Applications SAP ECC 6.00 enhancement package 7

Company Roles Maintenance Employee WCM Planner Administrator


Detailed Process Description

Work Clearance ManagementThe design of the scope item is based on SAP WCM enhancement model, and fully integrated with the work order process.

The WCM planner can create work approval from a maintenance order, then the reference information in the maintenance order can be copied into work approval automatically. Same result when creating WCA and Hot Work from WAP, WCD from WCA.

Once determines to activate the WCM process during maintenance process to ensure maintenance staff’s safety, all permit must be issued before execution of actual maintenance.

Lockout/Tag out consists of orderly tagging and subsequent un-tagging of technical objects, so that work and tests on technical objects can be performed safety.

Maintenance employee can create a maintenance plan to regularly generate maintenance order. All WCM objects could be generated automatically and link to the maintenance order.


Process Flow DiagramWork Clearance Management

IT

Ad

min

istr

ato

rE

ven

tC

he

mic

als

: M

ain

ten

an

ce

Sp

ec

iali

stP

M-W

CM

Ma

inte

na

nc

e P

lan

ner

Create Maint. Order with

WCM Requirement

Maintain Activation of Work Clearance for Maintenance

Orders

Safety Measure before Actual Maint. Work

Create Work Approval from

Maint Order

Create WCA from Work Approval

Create Addit. Application for Hot Work from

WAP

Create Operational

WCD from WCA

Assign External Document to Operational

WCD

Setting WAP to Prepared

Setting WCA to Prepared

Setting Hot Work

Application to Prepared

Approve Tagging for WCA before

Hot Work is Approved

Approving Hot Work Permit

Approve Tagging for WCA after Hot Work is Approved

Set WCD to Prepared to

Start Tagging

Perform Tagging

Approve Safety Measurement in

WCA

Print Work Permit

Release Execution for Work Order

Execute Actual Maintenance

Work

Perform Test Cycle

Maintenance Work

Completed

Set Work Order to Work

Completed

Set Work Approval to

Closed

Set Application for Hot Work to

Closed

Set WCA to Closed

Perform Untagging

Set WCD to Closed

Operational Maintenance (929) – Step

4.15


4.16


4.17

Maintenance Plan Scheduling

Create Maintenance

Plan

Schedule Maintenance

Plan

Run Program RIWC0016 to

Generate WCM Objects

Check Call Object


Legend

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.


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


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

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


Budget Planning: Indicates a budget planning document


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.

<F

unct

ion>

Ext

ern

al t

o S

AP

Business Activity / Event

Unit Process

Process Reference

Sub-Process

Reference

Process Decision

Diagram Connection

Hardcopy / Document

Financial Actuals

Budget Planning

Manual Proces

s

Existing Version /

Data

System Pass/Fail Decision


© 2014 SAP SE or an SAP affiliate company. All rights reserved.

No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP SE or an SAP affiliate company.

SAP and other SAP products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP SE (or an SAP affiliate company) in Germany and other countries. Please see http://global12.sap.com/corporate-en/legal/copyright/index.epx for additional trademark information and notices.

Some software products marketed by SAP SE and its distributors contain proprietary software components of other software vendors.

National product specifications may vary.

These materials are provided by SAP SE or an SAP affiliate company for informational purposes only, without representation or warranty of any kind, and SAP SE or its affiliated companies shall not be liable for errors or omissions with respect to the materials. The only warranties for SAP SE or SAP affiliate company products and services are those that are set forth in the express warranty statements accompanying such products and services, if any. Nothing herein should be construed as constituting an additional warranty.

In particular, SAP SE or its affiliated companies have no obligation to pursue any course of business outlined in this document or any related presentation, or to develop or release any functionality mentioned therein. This document, or any related presentation, and SAP SE’s or its affiliated companies’ strategy and possible future developments, products, and/or platform directions and functionality are all subject to change and may be changed by SAP SE or its affiliated companies at any time for any reason without notice. The information in this document is not a commitment, promise, or legal obligation to deliver any material, code, or functionality. All forward-looking statements are subject to various risks and uncertainties that could cause actual results to differ materially from expectations. Readers are cautioned not to place undue reliance on these forward-looking statements, which speak only as of their dates, and they should not be relied upon in making purchasing decisions.

888_erp607_process_overview_en_xx.ppt

Documents