wcm structure

8/12/2019 Wcm Structure

1/41

Work Clearance Management (PM-WCM)

HELP.PMW

CM

Release 4 .6C


2/41

Work Clearance Management (PM-WCM) SAP AG

2 April 2001

Copyright

Copyright 2001 SAP AG. All rights reserved.

No part of this publication may be reproduced or transmitted in any form or for any purposewithout the express permission of SAP AG. The information contained herein may be changedwithout prior notice.

Some software products marketed by SAP AG and its distributors contain proprietary softwarecomponents of other software vendors.

Microsoft, WINDOWS

, NT

, EXCEL

, Word

, PowerPoint

and SQL Server

are registered

trademarks ofMicrosoft Corporation.

IBM, DB2

, OS/2

, DB2/6000

, Parallel Sysplex

, MVS/ESA

, RS/6000

, AIX

, S/390

,

AS/400, OS/390

, and OS/400

are registered trademarks of IBM Corporation.

ORACLEis a registered trademark of ORACLE Corporation.

INFORMIX-OnLine for SAP and Informix

Dynamic Server

TM

are registered trademarks ofInformix Software Incorporated.

UNIX, X/Open

, OSF/1

, and Motif

are registered trademarks of the Open Group.

HTML, DHTML, XML, XHTML are trademarks or registered trademarks of W3C, World Wide

Web Consortium,Massachusetts Institute of Technology.

JAVAis a registered trademark of Sun Microsystems, Inc.

JAVASCRIPTis a registered trademark of Sun Microsystems, Inc., used under license for

technology invented and implemented by Netscape.

SAP, SAP Logo, R/2, RIVA, R/3, ABAP, SAP ArchiveLink, SAP Business Workflow, WebFlow,SAP EarlyWatch, BAPI, SAPPHIRE, Management Cockpit, mySAP.com Logo and mySAP.comare trademarks or registered trademarks of SAP AG in Germany and in several other countriesall over the world. All other products mentioned are trademarks or registered trademarks of theirrespective companies.


3/41

SAP AG Work Clearance Management (PM-WCM)

April 2001 3

Icons

Icon Meaning

Caution

Example

Note

Recommendation

Syntax

Typographic Conventions

Type Style Description

Example text Words or characters that appear on the screen. These include fieldnames, screen titles, pushbuttons as well as menu names, paths andoptions.

Cross-references to other documentation

Example text Emphasized words or phrases in body text, titles of graphics and tables

EXAMPLE TEXT Names of elements in the system. These include report names,program names, transaction codes, table names, and individual keywords of a programming language, when surrounded by body text, forexample, SELECT and INCLUDE.

Example text Screen output. This includes file and directory names and their paths,messages, names of variables and parameters, source code as well asnames of installation, upgrade and database tools.

Example text Exact user entry. These are words or characters that you enter in thesystem exactly as they appear in the documentation.

Variable user entry. Pointed brackets indicate that you replace thesewords and characters with appropriate entries.

EXAMPLE TEXT Keys on the keyboard, for example, function keys (such as F2) or theENTERkey


4/41


4 April 2001

Contents

Work Clearance Management (PM-WCM).........................................................5

Architecture ................................................................................................................................... 7

Standard Model ............................................................................................................................. 9

Enhanced Model.......................................................................................................................... 11

Work Clearance Management Object ........................................................................................ 13

Work Approval............................................................................................................................. 15

Application ................................................................................................................................... 16

Work Clearance Application..................................................................................................... 17Additional Application ............................................................................................................... 19

Work Clearance Document......................................................................................................... 20

Work Clearance Document Template...................................................................................... 21Operational Work Clearance Document .................................................................................. 22

Lockout/Tagout ........................................................................................................................... 24

Operational Cycle ........................................................................................................................ 25

Check............................................................................................................................................ 28

Check: Reference Object ......................................................................................................... 30Check: Time Frame.................................................................................................................. 31Check: Completeness and Correctness ..................................................................................32Check: Test Cycle .................................................................................................................... 33Check: Untagging..................................................................................................................... 34Check: Conflict......................................................................................................................... 35

Conflict Rules...................................................................................................................... 36

Operational Protection................................................................................................................ 38

Maintenance Order Processing with Work Clearance Management...................................... 40


5/41



April 2001 5


Purpose

Necessary maintenance work at technical objects, such as inspections, preventive maintenanceor repairs, can only be executed once all the measures to ensure a safe working environmenthave been implemented. These safety measures can include, for example, lockout/tagout, fireprotection and radiation protection.

In lockout/tagout, for example, technical objects are isolated electrically or separatedmechanically from other parts of the technical system whilst maintenance work or special testsare performed, so that work on these technical objects can be performed safely.

You can use the Work Clearance Management(PM-WCM) component to control and monitor thesafety measures. You can ensure safe working conditions for the employees in yourmaintenance department, adhere to environmental protection regulations, and guarantee thereliability of your technical systems.

To ensure that the numerous safety conditions in the workplace are observed, work clearancemanagementmust be planned exactly and organized consistently.

Safety in the workplace can be influenced by the following factors:

Type of tasks

Technical specifications of technical systems

Qualifications of employees

Organization within the maintenance department

If you use the Work Clearance Managementcomponent, you can ensure the following:

Standardized process for enforcing safety measures

Approvals and status tracking

Adherence to legal and internal company safety standards

Verification (using change documents and time stamp for changes)

Implementation Considerations

The use of the work clearance managementcomponent is recommended in all companies wherespecific safety regulations apply. These regulations can include laws on the maintenance ofindustrial health and safety standards and requirements for dealing with hazardous goods.

However, the use of this component is also recommended for the following operationalrequirements:

Your employees in Plant Maintenance work in a critical environment, in which they areexposed to high levels of danger. This can include high voltage, radioactivity and gases.

Your employees have to work under difficult conditions. These can include restricted spaceor visibility, heat, noise and dust.

In your industry, there are typical work-related illnesses that necessitate special health andsafety measures.


6/41



6 April 2001

You must also perform maintenance work whilst the system is operative.

Effective safety devices are not available for all the technical systems.

You often use external personnel.

Other parts of the system should not be affected under any circumstances.

This component is typically used in the chemical, oil, gas, and supply industries.

Integration

Work Clearance Managementis integrated into the Plant Maintenance(PM) component. It isthereby possible to consider aspects of safety in the workplace, in addition to the traditional tasksof planning maintenance work (material planning, scheduling). Not only the different maintenancetasks must be planned exactly, but also how the affected system parts can be processed.

Features

The Work Clearance Managementcomponent is an open system with different work clearance

management objects and flexible Customizing.The functions available include:

Approving, scheduling and controlling safety measures

Combining orders for collective safety measures

Printing shop papers


7/41


Architecture

April 2001 7

Architecture

Definition

A model structure that defines the relationships between individual work clearance managementobjects [Page 12].

Use

When representing the architecture of your work clearance management, you can choosebetween the standard model [Page 8]and enhanced model [Page 10].

The standard model comprises the following work clearance management objects:

Work clearance application [Page 16]

Operational work clearance document [Page 21]

The enhanced model comprises the following work clearance management objects:

Work approval [Page 14]

Additional applications [Page 18]

The model selected is decided separately for each planning plant in a company.

We recommend that you use:

Standard model, if you only require lockout/tagout [Page 23]

Enhanced model, if you require other applications in addition to lockout/tagout, for example,fire or radiation protection

For both models, certain company-specific rules must be defined for the relationships betweenthe work clearance management objects. For example, you can define that only one operationalwork clearance document should be assigned to a work clearance application.

Order

Work approval

Work

clearance

application

Operational

WCD

Order

Work

clearance

application

Operational

WCD

Enhanced model Standard model

Additional

applications


8/41


9/41


Architecture

April 2001 9

Standard Model

Definition

A model structure that defines the relationships between the following work clearance

management objects [Page 12]:



Use

Use of the standard model is advisable if lockout/tagout [Page 23]is of primary importance andother safety measures, such as radiation protection, safety in the workplace, and fire protection,play a less significant role.

Structure

The architecture of the standard model is as follows:

Note the following rules of assignment:

A work clearance application can be assigned to several orders. However,

an order can only ever be assigned to one work clearance application.(assignment rule R1)

A work clearance application can be assigned to several operational workclearance documents, and vice-versa. (assignment rule R2)

Order

Work

clearance

application

Operational

WCD


10/41


Architecture

10 April 2001

The following graphic illustrates the possible links:

Order

1001

Order

1002

Order

1003

Work

clearance

application

2001

Operational

WCD3001

Operational

WCD3002

Workclearance

application

2002

Operational

WCD3003


11/41


12/41


Enhanced Model

12 April 2001

A work approval can be assigned to several orders. However, an order canonly ever be assigned to one work approval. (assignment rule R3)

An application can be assigned to several work approvals, and vice-versa.(assignment rule R4)

A work approval can only be assigned to one application of an applicationtype. For example, it is not possible for several work clearance applicationsto be assigned to one work approval. (assignment rule R5)



Order 1 Order 2 Order 3

Work approval

1Work approval

2

Order 4

Work clearance

application

1

Work clearance

application

2

Operational

WCD

1

Operational

WCD

2

Operational

WCD

3

Application for

radiation protection

Application for

fire protection


13/41


Work Clearance Management Object

April 2001 13


Definition

Object that supports you during work clearance management.

Use

In work clearance management objects, you can:

Maintain administrative data, reference object, responsibilities, location and planning data

Assign user statuses

Assign partners with different functions

Assign long texts

Assign documents using the Document Management System

Assign and grant approvals

Assign catalog groups and codes

Assign technical objects using the object list

Structure

The following table shows which work clearance management objects occur in which areas ofresponsibility and features:

Work ClearanceManagement Object

Area of Responsibility Feature

Work approval [Page 14] Plant Maintenance,

Production

Application [Page 15] Plant Maintenance,Production


Possible additional applications [Page18],for example, boiler inspection certificate,permit for working with radioactivematerials, or permit for working withopen flames

Work clearancedocument [Page 19]

Production Operational work clearance document[Page 21]

Work clearance document template

[Page 20]


14/41



14 April 2001

The following table contains the system statuses that are possible for all work clearancemanagement objects:

ID Name Meaning

CRTE Created Initial status of a work clearance management object

PREP Prepared Authorization is required

Further changes are not allowed

Approvals can be granted

Status can be reset

CHNG Change mode Authorization is required

Approvals can be granted

Status can be reset

PWP Work permit printed Authorization is required

Printing is dependent on approval status

CLSD Completed Authorization is required

Work clearance management object was processedsuccessfully

No more changes/activities allowed

REJC Rejected Authorization is required

No more changes/activities allowed

INAK Object deactivated No more changes/activities allowed

Status can be reset

DLFL Deletion flag No more changes/activities allowed

Status can be reset

Integration

Good communication between departments is essential when using work clearance managementobjects:

Work approvals and applications require communication between units performing the work(for example, Plant Maintenance) and administrative units (for example, the security office).

The operational work clearance document and work clearance applications requirecommunication between administrative units (for example, the security office) and units

performing the work (for example, Production).


15/41


Work Approval

April 2001 15

Work Approval

Definition

Work clearance management object [Page 12]for controllingcommunication betweenmaintenance orders and applications. In the work approval, measures are requested to ensure asafe environment for work at a technical system. As a higher-level work clearance managementobject, the work approval can combine the work clearance application [Page 16]with otheradditional applications [Page 18], for example, boiler inspection certificate, permit for workingwith radioactive materials, permit for working with open flames, and so on.

Use

The work approval is only used in the enhanced model [Page 10]of work clearance managementand represents the central safety certificate. Maintenance personnel request work approvals, forexample, from those responsible for work safety or radiation protection.

On the one hand, work approvals are assigned to orders where they control the system statusReleased for execution; on the other hand, work approvals are assigned to applications thatthey control and monitor.


A work approval can be assigned to several orders. However, an order canonly ever be assigned to one work approval. (assignment rule R3)


A work approval can only be assigned to one application of an applicationtype. For example, it is not possible for several work clearance applications

to be assigned to one work approval. (assignment rule R5)


Order

1001

Order

1002

Order

1003

Approval

2001

Work

clearance

application

3001

Work

clearance

application

3002

Order

1005

Approval

2002

Work

clearance

application

3003

Order1006

Approval

2003

(R...) = is contrary to the assignment rule...

(R5)

(R3)


16/41


Work Approval

16 April 2001

Definition

Work clearance management object that represents a safety certificate and is used for

communication between different areas.A special featureof the application for lockout/tagout [Page 23]is that the application is alreadyavailable in the system as a work clearance application [Page 16].


17/41


Work Clearance Application

April 2001 17


Definition

Work clearance management object [Page 12]in work clearance management. The workclearance application represents the safety certificate especially forlockout/tagout [Page 23].

It is used to control maintenance processing with lockout/tagout and groups together operationalwork clearance documents [Page 21]. These are controlled and monitored by the work clearanceapplication.

Use

Standard Model

In the standard model [Page 8], a work clearance application is used to control communicationbetween orders and operational work clearance documents. Through its direct assignment to theorders, the work clearance application controls the status Released for execution in the order.


A work clearance application can be assigned to several orders. However,an order can only ever be assigned to one work clearance application.(assignment rule R1)


Enhanced Model

In the enhanced model [Page 10], a work clearance application is used to control communicationbetween work approvals [Page 14]and operational work clearance documents. It is subordinateto the work approval.



A work approval can only be assigned to one application of an applicationtype. For example, it is not possible for several work clearance applicationsto be assigned to one work approval. (assignment rule R5)




18/41



18 April 2001

Structure

In addition to the system statuses that apply for all work clearance management objects, thefollowing system statuses are also possible for the work clearance application:

ID Name Meaning

TENT Test cycle Tagging/untagging is allowed in the test cycle for assigned operationalwork clearance documents (For more information about test cycles,see Operational Cycle [Page 24])

Status can be reset

Work

approval

2001

Work

approval

2001

Work

clearance

application

3001

Work

clearance

application

3001

Work

approval

2002

Work

approval

2002

Operational

WCD

4001

Operational

WCD

4001

Operational

WCD

4002

Operational

WCD

4002

Operational

WCD

4003

Operational

WCD

4003

Enhanced model

Order

1002

Order

1002

Work

clearance

application

3001

Work

clearance

application

3001

Work

clearance

application

3002

Work

clearance

application

3002

Operational

WCD

4001

Operational

WCD

4001

Operational

WCD

4002

Operational

WCD

4002

Standard model

Order

1001

Order

1001

(R1)

(R...) = is contrary to the assignment rule


19/41


Additional Application

April 2001 19


Definition

Work clearance management object[Page 12]in work clearance management. In addition to awork clearance application, which represents the safety certificate especially for lockout/tagout[Page 23], it can be necessary to consider additional safety measures, for example, for radiationprotection or fire protection. These safety measures are represented in the additionalapplications.

Use

The additional applications can only be used in the enhanced model [Page 10]of work clearancemanagement. They are combined with the work clearance applications [Page 16]under the workapproval [Page 14].

The additional applications are industry-specific and necessary if other safety measures must bemanaged in the system as independent work clearance management objects. They areprogrammed using the ABAP Workbench.

To facilitate programming and guarantee integration in the enhanced model, a generalapplication is available that can be used as a copy model for programming.



A work approval can only be assigned to one application of an applicationtype. For example, it is not possible for several work clearance applicationsto be assigned to one workapproval. (assignment rule R5)


Work approval

1

Work approval

2

Application 1 for

fire protection

Application 2 for

fire protection

(R5)

(R...) = is contrary to the assignment rule...


20/41



20 April 2001

Definition

Work clearance management object [Page 12]in work clearance management. The work

clearance document:

Describes lockout/tagout [Page 23]

Contains a list of the technical objects in a technical system to be tagged or monitored

Controls the physical blocking and signposting of the technical objects affected

Contains a detailed description of how the system should be isolated

Use

In the work clearance document, you enter all the technical objects that should be processed inconjunction with a lockout/tagout. The work clearance document can contain pieces ofequipment, functional locations, technical objects, which are not managed in the R/3 technical

system structure, and comments.You can do the following for each item:

Maintain descriptive data for tagging and untagging

Assign user statuses

Assign a long text

Assign documents using the Document Management System

Structure

There are two types of work clearance document:

Work clearance document template [Page 20]

This is only used as a template for other work clearance documents.


This is used for lockout/tagout.


21/41


Work Clearance Document Template

April 2001 21

Work Clearance Document Template

Definition

Work clearance document [Page 19]used as a copy model when creating work clearancedocuments.

Use

The work clearance document template itself cannot be used to perform lockout/tagout [Page23]. Therefore, it cannot be tagged/untagged or assigned. The work clearance documenttemplate is used as a copy model for work clearance documents. This means, for example, thatwork clearance documents for complex structures of technical systems do not always have to berecreated.

You can use work clearance document templates to create a library of reference data.

A library of work clearance document templates makes planning a lockout/tagout much easier

and thereby ensures greater safety.


22/41


Operational Work Clearance Document

22 April 2001


Definition

Work clearance document [Page 19]that is used for the lockout/tagout [Page 23]of technicalobjects and can therefore be tagged/untagged.

Structure

The operational work clearance document is subordinate to the work clearance applications[Page 16].

In addition to the system statuses that apply for all work clearance management objects, thefollowing system statuses are also possible for the operational work clearance document:

ID Name Meaning

PROC Processing The operational process has begun

UNT Untaggable The operational work clearance document can be untagged

Status can be reset

TEST Test cycle A test cycle is allowed for the operational work clearance document

Status can be reset

The following table contains the possible system statuses for an item in the operational workclearance document:

ID Name Meaning

ITG Initial tagging status Initial status for an item to be tagged/untagged

BTG Tag Initial status of tagging phase

PTAG Tag printed Print status of tagging phase

ETG Tagged Final status of tagging phase

Status cannot be suppressed

Item cannot be deactivated

BTUG Untag temporarily Initial status of temporary untagging phase


PTST Test tag printed Print status of temporary untagging phase


ETUG Temporarily untagged Final status of temporary untagging phase


BUG Untag Initial status of untagging phase



23/41



April 2001 23

EUG Untagged Final status of untagging phase


CONF Conflict Conflict for item to be tagged/untagged was ignored

POST Postscript Item was added subsequently in change mode

PROT Operational protection Operational protection [Page 37]was set for the item tobe tagged/untagged

INAK Object deactivated No more changes/activities allowed

Status cannot be reset




See also:

Operational Cycle [Page 24]

Work

clearance

application

3001

Work

clearance

application

3001

Operational

WCD

4001

Operational

WCD

4001

Operational

WCD

4002

Operational

WCD

4002

Work

clearance

application

3002

Work

clearance

application

3002

Operational

WCD

4003

Operational

WCD

4003


24/41


25/41


Operational Cycle

April 2001 25

Operational Cycle

Purpose

The operational cycle is used to describe the operational processing of lockout/tagout [Page 23].

Prerequisites

To start using lockout/tagout, the operational work clearance document [Page 21]must have thestatus Prepared.

Process Flow

The operational cycle is divided into the following operational phases:

Tagging

Temporary untagging

Untagging

In the operational cycle, the items in an operational work clearance document run throughseveral statuses for each operational phase in a specific sequence.

The first status within each operational phase serves notice of an activity, that is, the change ofan operational condition/type:

Tag

Untag temporarily

Untag

If an operational tag is printed, the status that confirms printing is assigned.

Tag printed

Test tag printed

In addition to operational tags, a list can also be printed for tagging or untagging.

The last status confirms the execution of an activity on site:

Tagged

Temporarily untagged

Untagged

The following diagram illustrates the maximum pre-defined operational cycle:


26/41


Operational Cycle

26 April 2001

You can also reduce the operational cycle. For example, you can hide statuses, such as Tag,Untagor Test tag printed. The processes for this status are then performed completely in thebackground. For the minimum set-up of the operational cycle, only the statuses of the user thatconfirm the execution of the activity on site must be set.

For each operational step, the system checks whether:

The user is authorized for tagging/untagging

Tagging/untagging is blocked by an approval

Tagging/untagging is blocked by an operational protection [Page 37]

It is a valid operational step

You can still change the untagging condition/type (or temporary untagging condition/type) of anitem until you enter the respective untagging phase (or temporary untagging phase). However,when the activity is notified, it is automatically frozen.

Progress in the operational cycle is displayed in the item and the header for the operational workclearance document:

If all the items have the same operational status, this operational status is also displayed inthe header.

If a conflict only occurs during tagging/untagging, this is displayed in the header.

The following operational cycles are possible:

Tagging cycle with temporary untagging phase

Initial tagging status (ITG)

Tag (BTG)

Tag printed (PTAG)

Tagged (ETG)

Untag temporarily (BTUG)

Test tag printed (PTST)

Temporarily untagged (ETUG)

Untag (BUG)

Untagged (EUG)

NFSITG

DFSZPTAG

IFSETG

SFSBTG

STNMBTUG

ITNMETUG

DTSTPTST

SNMBUG

INMEUG

Taggingphase

Untaggingphase

Temporaryuntaggingphase


27/41


Operational Cycle

April 2001 27

This operational cycle consists of the tagging phase, temporary untagging phase anduntagging phase.

Tagging cycle without temporary untagging phase

This operational cycle consists of the tagging phase and untagging phase.

Test cycle

This operational cycle consists of the tagging phase and temporary untagging phase.


28/41


Check

28 April 2001

Check

Purpose

You can use checks to ensure that lockout/tagout [Page 23]can be processed safely and free ofconflict. Some checks may be optional, others are obligatory. You can deactivate optional checksin Customizing.

Checks made include whether:

An authorization is available

Tagging/untagging is blocked by an approval

Tagging/untagging is blocked by an operational protection

It is a valid operational step

The following checks are possible in work clearance management:

Reference object [Page 29]

Time frame [Page 30]

Completeness and correctness [Page 31]

Test cycle [Page 32]

Untagging [Page 33]

Conflict [Page 34]

Checks are made in the operational phases of the operational cycle [Page 24]for the followingstatuses:

Tagging Phase

Tag

BTG

Tag printed

PTAG

Tagged

ETG

Reference object X

Time frame X

Completeness and correctness

Test cycle

Untagging

Conflict X

Temporary Untagging Phase

Untag temporarily

BTUG

Test tag printed

PTST

Temporarily untagged

ETUG


29/41


Check

April 2001 29

Reference object

Time frame X

Completeness and

correctness

X

Test cycle X

Untagging

Conflict X

Untagging Phase

Untag

BUG

Untagged

EUG

Reference object

Time frame X

Completeness and correctness X

Test cycle

Untagging X

Conflict X


30/41


Check: Reference Object

30 April 2001

Check: Reference Object

Use

Optional check whether the technical object to be tagged/untagged is not already the referenceobject for an active lockout/tagout [Page 23].

The check is purely informative and does not have any influence on tagging/untagging.

Features

The system logs the corresponding reference object from start to finish of a lockout/tagout. If thesystem notices during the check that the technical object to be tagged/untagged is already areference object in another active lockout/tagout, a message appears on the screen to this effect.

Activities

You can also deactivate the check.


31/41


Check: Time Frame

April 2001 31

Check: Time Frame

Use

Optional check whether a technical object, which should be tagged/untagged and thereby obtaina new operational condition or type, does not already have another operational condition/type notyet confirmed in the system within an operational group.

Features

At the start of each operational phase, an activity, that is, a change in the operationalcondition/type is notified. As long as you do not confirm the execution of this activity, it remainsundefined in the system, even if it has already been executed.

At the start of the operational phase, the system logs the operational condition/type, which thetechnical object should obtain for each operational group. This entry is only deleted again whenyou confirm the new operational condition/type.

If another entry already exists using an intended operational condition/type, the technical objectcan not be tagged/untagged, unless the intended operational condition/type and the one alreadyavailable have been enteredas permissible in Customizing.

Activities

You cannot ignore the check. However, you can change or deactivate it.

Example

There are three operational work clearance documents WCD 1, WCD 2 and WCD 3. In eachoperational work clearance document, the technical object Valve Ashould be tagged/untaggedas follows:

Operational Work ClearanceDocument

Technical Object Tagging Condition Tagging Type

WCD 1 Valve A ON 1

WCD 2 Valve A ON 1

WCD 3 Valve A OFF 1

This is a simplified example, in which the same operational group is assumed.

You exit the lockout/tagout for operational work clearance document 1. This means that you haveset the status to Tag. Before you confirm this, operational work clearance documents 2 and 3should also be tagged. The check will not generate a message for the tagging of operationalwork clearance document 2 because the technical object Valve Aretains the same taggingcondition as in operational work clearance document 1. However, the tagging of operational workclearance document 3 is stopped because the tagging condition is different from the workclearance document already exited.


32/41


Check: Completeness and Correctness

32 April 2001

Check: Completeness and Correctness

Use

Obligatory check whether the required untagging condition/type of a technical object has beenmaintained. This must be maintained at the untagging or temporary untagging stage at the latest.

Features

At the start of the untagging or temporary untagging phase, the system checks whether theuntagging condition/type of the technical object, which should be tagged/untagged, has beenmaintained.

Activities

You cannot ignore the check.

See also:



33/41


Check: Test Cycle

April 2001 33

Check: Test Cycle

Use

Obligatory check whether a test cycle is possible for the operational work clearance document[Page 21].

Prerequisites

All the work clearance applications [Page 16]assigned to the operational work clearancedocument are either Completed or allow a test cycle.

Activities

You can also ignore the check. However, you require a special authorization for this.

See also:Operational Cycle [Page 24]


34/41


Check: Untagging

34 April 2001

Check: Untagging

Use

Obligatory check whether untagging is possible for the operational work clearance document[Page 21].

Prerequisites

All the work clearance applications [Page 16]assigned to the operational work clearancedocument are Completed, that is, the operational work clearance document can be untagged.

Activities

You can also ignore the check. However, yourequire a special authorization for this.

See also:Operational Cycle [Page 24]


35/41


Check: Conflict

April 2001 35

Check: Conflict

Use

Obligatory check whether the required operational conditions/types of a technical object can alsobe tagged/untagged within an operational group.

Features

A conflict record is written by the system at the start of a new tagging phase. This entry is onlydeleted again once the position has been untagged or temporarily untagged.

At the start of each operational phase, the system checks all available conflict records to seewhether the operational conditions/types required for a technical object can also betagged/untagged in the operational work clearance document [Page 21]. This check is based ongeneral and user-defined conflict rules [Page 35], which are checked for tagging, untagging andtemporary untagging.

Activities

In the case of a conflict, you can:

Stop tagging/untagging and remove the conflict

Ignore the conflict and continue tagging/untagging. However, you require a specialauthorization for this.

If you ignore a conflict, the status CONF(= conflict) is also assigned to the technical object by thesystem. If during lockout/tagout, the technical object for which the conflict arose is, for example,untagged, then the conflict is automatically withdrawn.

See also:



36/41


37/41


Conflict Rules

April 2001 37

Example

Example of general conflict rules:

If the conditions CLOSEDand LOCKEDbelong to the same operational type, then their

combination leads to a conflict.

Example of user-defined conflict rules:

For example, a user-defined conflict rule states that the condition LOCKEDcan follow thecondition CLOSED, but the condition CLOSEDis not allowed to follow the condition LOCKED.

Example calculation of the number of user-defined conflict rules:

In an operational group E (= electrical), there are two operational conditions ONand OFF, eachwith three operational types RED, YELLOWand WHITE. There are therefore six possiblecombinations of operational condition and operational type. When the rules are created, all ofthese combinations can also be reversed, so that a total of 36 (= 6 x 6) conflict rules are enteredin Customizing.


38/41


Operational Protection

38 April 2001


Use

Protection which ensures that a technical object, which is managed as an item in an operationalwork clearance document, can only be tagged/untagged from certain operational work clearancedocuments [Page 21].

After an operational protection has been set, tagging/untagging is only possible from thoseoperational work clearance documents that are linked together directly by the superior workclearance applications [Page 16]. These operational work clearance documents then form theprotected area.

The operational protection can be used to protect the temporary untagging of aposition of the operational work clearance document against other operational workclearance documents for test purposes.

Prerequisites

The operational work clearance documents with technical objects to be protected are linkedto one another using work clearance applications.

The technical objects that should be protected are managed as items in the operational workclearance documents that are linked to one another.

The operational protection always refers to the technical object and its assignedoperational group.

Features

The operational protection can be used to create protected areas. A protected area is definedusing the following criteria:

Operational protection of items in operational work clearance documents that representtechnical objects

Direct linking of operational work clearance documents using superior work clearanceapplications

A technical object with operational protection can be tagged/untagged within the protected area.However, it is not possible to tag/untag the technical object outside of the protected area.


39/41



April 2001 39

Example

The protected area exists through the protection of items 1 and 2 (that is, technical objects A100and A200) in operational work clearance document 201 and the linking of operational workclearance documents 201 and 202 using work clearance application 1001.

Technical objects A100 and A200 can only be tagged/untagged within the protected area, that is,in operational work clearance documents 201 and 202.

The operational work clearance documents 202 and 203 are linked together using workclearance application 1002. However, technical objects A100 and A200 can no longer betagged/untagged from operational work clearance document 203.

Technical objects A300 and A400 can be tagged/untagged from all the operational workclearance documents.

This is a simplified example, in which the same operational group is assumed.

Work

clearance

application

1001

Operational

WCD

201

Operational

WCD

202

Items

Item 1: A100 (protected)

Item 2: A200 (protected)

Item 3: A300

Item 4: A400

.......

Operational

WCD

203

Items

Item 1: A100

Item 2: A200

Item 3: A300

Item 4: A400

......

Items

Item 1: A100

Item 2: A200

Item 3: A300

Item 4: A400

......

Protected area

Work

clearance

application

1002


40/41


Maintenance Order Processing with Work Clearance Management

40 April 2001

Maintenance Order Processing with Work ClearanceManagement

Purpose

Aspects of safety in the workplace must often be considered when executing maintenance workin order to ensure a safe working environment. These safety measures can include issuingpermits for radiation protection, fire protection or lockout/tagout.

Prerequisites

In these cases, the execution of maintenance work not only necessitates the planning ofmaintenance tasks, but also the planning of a procedure for how to work safely on the affectedparts of the system. In addition, clear communication between all the employees or departmentsinvolved in maintenance work using work clearance management is essential.

Owing to the complexity of the process, it is important to regulate all areas of responsibility

clearly and assign the necessary tasks accordingly. For example, employees with specialoperational authorizations are required, who are allowed to issue an availability permit.

Process Flow

Work

Clearance

Management

Work

Clearance

Management

Work

Clearance

Management

Work

Clearance

Management

NotificationNotificationCreate

order

Create

orderRelease

order

Release

orderConfirm

order

Confirm

orderComplete

order

Complete

order

History/AnalysisHistory/Analysis

Plan

order

Plan

order

SCADASCADA

Maintenance planMaintenance plan


41/41


Maintenance Order Processing with Work Clearance Management

The standard process flow for order processing in the SAP component Plant Maintenance(PM)using the enhanced model [Page 10]of work clearance management comprises the followingsteps:

1. Notifying a maintenance requirement

This can be performed manually using a malfunction report or automatically using aSCADA system in the control room, or by using deadline monitoring of maintenanceplans in preventive maintenance.

2. Creating and planning an order

You plan the activities and resources required, create a cost estimate and performscheduling. If the work to be executed requires safety measures, you must also assignspecial approvals, which initiate work clearance management, to the order.

3. Creating a work approval

You create the necessary work approval [Page 14]. This contains all the applications,such as the work clearance application [Page 16]with the corresponding operationalwork clearance documents [Page 21].

4. If a lockout/tagout [Page 23]is performed: Tag technical objects

During lockout/tagout, you alter the operational conditions of the technical objects, whichare listed in the items of the operational work clearance documents, to ensure a safeworking environment.

Once all the items have been tagged, the operational work clearance document istagged.

Once all the operational work clearance documents have been tagged, you confirm thatthe lockout/tagout has been executed in the work clearance application.

5. Confirming the implementation of safety measures

Once all the safety measures have been implemented, you confirm this in the work

approval.6. Issuing the status Released for execution

Once the safety measures have been implemented, the status Released for executionfor maintenance work to start can be issued.

7. Executing the work and confirming its completion

During and after the completion of the work, you confirm the resources required (forexample, materials, times, and external services) and technical findings.

8. Completing the work approval and applications

9. If a lockout/tagout is performed: Untag technical objects

10. Completing an order and copying to an order history

After the order has been technically completed, the business completion is performedwith settlement of the order. The order is then copied into the order history, where it isavailable for evaluations in the SAP component Plant Maintenance Information System(PM-IS).

wcm structure

Documents