011000358700003536222005 e

7/25/2019 011000358700003536222005 e

http://slidepdf.com/reader/full/011000358700003536222005-e 1/46

Work ClearanceManagement

SAP AG

7/25/2019 011000358700003536222005 e


Process with Mobile WCM

General Overview

Process without Mobile WCM

7/25/2019 011000358700003536222005 e


© SAP AG 2005

Maintenance crews are working in a hazardous environment

(high voltage, radiation exposure, hot steam, ... )

The guarantee of supply requires maintenance work while

systems are up and running

The functionality of a technical system must not be affected

under any circumstances

There are typical work-related illnesses, which require special

health and safety measures

Why do Companies need WCM?

7/25/2019 011000358700003536222005 e


© SAP AG 2005

What are the Key Benefits?

Authorization process

Open model

Easy to learn & use

Standardized procedures

Generates templates

Meets OSHA regulations

Increases productivity

Lockout/Tagout

Full integration with the maintenance processes of EAM

7/25/2019 011000358700003536222005 e


© SAP AG 2005

Utilities

Process Industries

Oil & Gas

Mining

Public Transport

What are our Focus Industries?

7/25/2019 011000358700003536222005 e


© SAP AG 2005

WCM Objects

Work Approval (WAP)

Applications

Work Clearance Application (WCA)

Application for Fire Protection

...

Work Clearance Documents (WCD) WCD Template

Operational WCD

If a cus tomer has other safety appl icat ions beside

WCM, SAP recomm ends the enhanced mod el

Order

Work Approval

Work Clearance

Application

Operational WCD

Enhanced Model

Further

Applications

Order

Work Clearance

Application

Operational WCD

Standard Model

7/25/2019 011000358700003536222005 e


© SAP AG 2005

Maintenance Process with WCM

Work Clearance

Management

Work Clearance

Management

Notification

Notification Create

Order

Create

Order

Release

Order

Release

Order

Confirm

Order

Confirm

Order

Complete

Order

Complete

Order

Analyze HistoriesAnalyze Histories

Plan

Order

Plan

Order

SCADASCADA

Maintenance planMaintenance plan

Work Clearance

Management

Work Clearance

Management

7/25/2019 011000358700003536222005 e


© SAP AG 2005

Why Work Clearance Management (WCM) is Critical

WCM controls and monitors the safety measures

Necessary maintenance work on technical objects, such as inspections,

preventive maintenance or repairs, can only be executed once all the

measures to ensure a safe working environment have been implemented.

These safety measures can include for example:

Lockout/Tagout

Fire protection and

Radiation protection

Ensure safe working conditions for the employees in your

maintenance department

Adhere to environmental protection regulations,

Guarantee the reliability of your technical systems.

7/25/2019 011000358700003536222005 e


© SAP AG 2005

The Lockout/Tagout Process

To provide safe working conditions the

The Orderly Tagging and Subsequent Untagging

of technical objects is very important for the maintenance staff.

Safe conditions before work starts and remain so during the work

on the technical system require the observation of 5 safety rules:

1. Tag electrically, lock out, or decouple mechanically

2. Protect against being switched on again

3. Ensure absence of residual voltage

4. Earth and short-circuit

5. Save neighboring parts that are under stress

7/25/2019 011000358700003536222005 e


© SAP AG 2005

How WCM is Documented in SAP-EAM

The Work Clearance Document

Describes Lockout/Tagout

Contains technical objects of an asset, which are to be switched or

monitored in Work Clearance Management

Controls the physical blocking and switching of the technical objectsaffected

Contains a detailed description of how the system should be isolated

7/25/2019 011000358700003536222005 e


© SAP AG 2005

The Operational Lists

The Operational List

is the printout of an Operational Work Clearance Document.

There are two types of operational lists:

A list for tagging

A list for untagging

Tagging and Untagging is logged with the operational list.

Instead of printing operational lists you can

use Mobile WCM

7/25/2019 011000358700003536222005 e


© SAP AG 2005

What Does Mobile Work Clearance Management?

Mobile Work Clearance Management:

Supports the Lockout/Tagout process

Replaces the printout of operational lists

End User Actions on the Mobile Device:

Confirm the execution of the activity

Reject the activity for switching items only

Confirm completion of the activity

A il bl R l

7/25/2019 011000358700003536222005 e


© SAP AG 2005

Available Releases

Release WCM mobile WCM

ISU-WCM 1.2 (4.0B)

ISU-WCM 4.61 (4.6C) / R/3 4.6C

SAP R/3 Enterprise PLM Extension 1.1

SAP R/3 Enterprise PLM Extension 2.0

mySAP ERP 2004

mySAP ERP 2005

7/25/2019 011000358700003536222005 e



General Overview


7/25/2019 011000358700003536222005 e


© SAP AG 2005

“Tag” Pump Set P2

7/25/2019 011000358700003536222005 e


© SAP AG 2005

Checks and Simulations

Checks and simulations ensure that

Lockout/Tagout can be processed safely and free

of conflict

The checks run automatically

Checks can be mandatory or optional.

7/25/2019 011000358700003536222005 e


© SAP AG 2005

Screenshot: Status of the Operational WCD: “Tag (BTG)”

7/25/2019 011000358700003536222005 e


© SAP AG 2005

Printing of the Tagging List

7/25/2019 011000358700003536222005 e


© SAP AG 2005

Operational List for Tagging was Printed

7/25/2019 011000358700003536222005 e


© SAP AG 2005

Printout of a Tagging List

7/25/2019 011000358700003536222005 e


© SAP AG 2005

Execution of the Activities on Site

OPENOPEN

CLOSEDCLOSED

1. The safety technician must pick-up the tagging

list in the office.

2. The safety technician must execute the

activities on site.

3. The safety technician must log the execution of

the activities in the tagging list.

4. The safety technician must return the tagging

list into the office.

7/25/2019 011000358700003536222005 e


© SAP AG 2005

Confirmation of the Activities in the System

7/25/2019 011000358700003536222005 e


© SAP AG 2005

Activities are Confirmed in the System

Th t i li t t b k t l i th f

7/25/2019 011000358700003536222005 e


© SAP AG 2005

The tagging list must be kept several years in the safedeposit

7/25/2019 011000358700003536222005 e



General Overview


7/25/2019 011000358700003536222005 e


© SAP AG 2005

“Tag” Pump Set P2

7/25/2019 011000358700003536222005 e


© SAP AG 2005

Checks and Simulations

Checks and simulations ensure that

lockout/tagout can be processed safely and free

of conflict

The checks run automatically

Checks can be mandatory or optional.

7/25/2019 011000358700003536222005 e


© SAP AG 2005

Status of the Operational WCD: “Tag (BTG)”

7/25/2019 011000358700003536222005 e


© SAP AG 2005

Creation Tagging List for Mobile Processing

7/25/2019 011000358700003536222005 e


© SAP AG 2005

Creation of Tagging List for Mobile Processing

Process Data on the

Mobile Device

WCAHE

WCAMC

WCAME

Creation of Operational Lists for

Mobile Processing

Transfer the Data to the

Mobile Device

(Synchronization)

Transfer Data from

the Mobile Device

(Synchronization)

WCAITWCAMC

WCAME

WCAMI

Both Archive of Processed Data

and Update of Operational WCDs

(Background Job)

Operational List for Tagging was Created;

7/25/2019 011000358700003536222005 e


© SAP AG 2005

Operational List for Tagging was Created; Switching Items are Locked for Further Changes

Status MOBI Locks Switching Item for

Further Changes in the Backend

G l O i d D t il d O i

7/25/2019 011000358700003536222005 e


© SAP AG 2005

General Overview and Detailed Overview

Operational List Released

Released

Action On Site

T f th D t t th M bil D i

7/25/2019 011000358700003536222005 e


© SAP AG 2005

Transfer the Data to the Mobile Device

Process Data on the

Mobile Device

WCAHE

WCAMC

WCAME


Mobile Processing


Mobile Device

(Synchronization)

Transfer Data from

the Mobile Device

(Synchronization)

WCAITWCAMC

WCAME

WCAMI



(Background Job)

Process Data on the Mobile Device

7/25/2019 011000358700003536222005 e


© SAP AG 2005

Process Data on the Mobile Device

ReleasedAction On Site2ndSwitching location of

Valve V2

Close Valve V2

CompletedAction On SiteExecuted1stSwitching location ofValve V1Close Valve V1

ProcessedStatusWhen?WhereWhat?OFFENOFFEN

ZUZU

Transfer the Data from the Mobile Device

7/25/2019 011000358700003536222005 e


© SAP AG 2005

Transfer the Data from the Mobile Device

Process Data on the

Mobile Device

WCAHE

WCAMC

WCAME


Mobile Processing


Mobile Device

(Synchronization)

Transfer Data from

the Mobile Device

(Synchronization)

WCAIT

WCAMC

WCAME

WCAMI



(Background Job)

Both Archive of Processed Data and

7/25/2019 011000358700003536222005 e


© SAP AG 2005

Update of Operational WCDs

Process Data on the

Mobile Device

WCAHE

WCAMC

WCAME


Mobile Processing


Mobile Device

(Synchronization)

Transfer Data from

the Mobile Device

(Synchronization)

WCAIT

WCAMC

WCAME

WCAMI



(Background Job)

Confirmation of the Activities in the System;

7/25/2019 011000358700003536222005 e


© SAP AG 2005

Switching Items are Unlocked for Further Changes

Both the Last Status, which Confirm the

Activity on Site was set, and the Status MOBI

which Locks the Item for Further Changes in

the Backend was removed


7/25/2019 011000358700003536222005 e


© SAP AG 2005


Operational List Processed; Complete

Completed

Action On Site Executed

The Process on the Mobile Device (1)

7/25/2019 011000358700003536222005 e


© SAP AG 2005


Start screen of the

mobile WCM Application.

The user gets information

about the last synchronisation and hisoperational lists


7/25/2019 011000358700003536222005 e


© SAP AG 2005


The mobile User sees his tagging and

untagging lists on his mobile device.

The status icon shows the actual

situation of the list (eg. Released,completed…)


7/25/2019 011000358700003536222005 e


© SAP AG 2005

( )

This screen shows the items of the

selected Tagging List with information

of the object, the tagging sequence

and the status.


7/25/2019 011000358700003536222005 e


© SAP AG 2005

( )

On the tagging item the user has the

Following possibilities:

- Action executed (tagging confirmed)

- Action rejected ( no tagging ex. Valveis broken)

-Feedback (the user can describe his

decision)


7/25/2019 011000358700003536222005 e


© SAP AG 2005

The system changes the status into

„executed“ which is status „etg“ in the

Backend system.


7/25/2019 011000358700003536222005 e


© SAP AG 2005

The summary list shows all objects

Which were changed since the last

Synchronisation.


7/25/2019 011000358700003536222005 e


© SAP AG 2005

By pushing the „Sync“ button ,

the information is passed to the

Backend System.

Copyright 2005 SAP AG. All Rights Reserved

7/25/2019 011000358700003536222005 e


© SAP AG 2005

No part of this publication may be reproduced or transmitted in any form or for any purpose without the express

permission of SAP AG. The information contained herein may be changed without prior notice.

Some software products marketed by SAP AG and its distributors contain proprietary software components of other

software vendors.

Microsoft, Windows, Outlook, and PowerPoint are registered trademarks of Microsoft Corporation.

IBM, DB2, DB2 Universal Database, OS/2, Parallel Sysplex, MVS/ESA, AIX, S/390, AS/400, OS/390, OS/400, iSeries,

pSeries, xSeries, zSeries, z/OS, AFP, Intelligent Miner, WebSphere, Netfinity, Tivoli, and Informix are trademarks or

registered trademarks of IBM Corporation in the United States and/or other countries.

Oracle is a registered trademark of Oracle Corporation.

UNIX, X/Open, OSF/1, and Motif are registered trademarks of the Open Group.

Citrix, ICA, Program Neighborhood, MetaFrame, WinFrame, VideoFrame, and MultiWin are trademarks or registered

trademarks of Citrix Systems, Inc.

HTML, XML, XHTML and W3C are trademarks or registered trademarks of W3C®, World Wide Web Consortium,

Massachusetts Institute of Technology.

Java is a registered trademark of Sun Microsystems, Inc.

JavaScript is a registered trademark of Sun Microsystems, Inc., used under license for technology invented andimplemented by Netscape.

MaxDB is a trademark of MySQL AB, Sweden.

SAP, R/3, mySAP, mySAP.com, xApps, xApp, SAP NetWeaver and other SAP products and services mentioned herein

as well as their respective logos are trademarks or registered trademarks of SAP AG in Germany and in several other

countries all over the world. All other product and service names mentioned are the trademarks of their respectivecompanies. Data contained in this document serves informational purposes only. National product specifications may vary.

These materials are subject to change without notice. These materials are provided by SAP AG and its affiliated

companies ("SAP Group") for informational purposes only, without representation or warranty of any kind, and SAP Group

shall not be liable for errors or omissions with respect to the materials. The only warranties for SAP Group 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.