PLM320 Work Clearance Management

8/14/2019 PLM320 Work Clearance Management

http://slidepdf.com/reader/full/plm320-work-clearance-management 1/190

© SAP AG PLM320 Preface-1

SAP AG 2003

PLM320 Work Clearance Management

THE BEST RUN BUSINESSES RUN SAP

© SAP AG 2003

PLM320Work Clearance Management

System R/3 – Enterprise 2003/Q2

Materialnummer: 50061236






SAP AG 2003

mySAP PLM (ALM Plant Maintenance)

PLM300

Plant Maintenance

5 days

PLM310

PreventiveMaintenance andService

3 days

PLM305

Structuring andManagingTechnical Objects

3 days

PLM315

MaintenanceProcessing:OperationalFunctions

3 days

PLM316

MaintenanceProcessing:Controlling andReporting Functions

3 days

*PLM130

Classification

3 days

PLM320

WCM WorkClearanceManagement

3 days

**CA500

Cross ApplicationTime Sheet

2 days

PLM120

Document

ManagementSystem

3 days

ALM = Asset Life-Cycle Management

* See also SCM Curriculum

**See also HR Curriculum

SAP01

mySAP.com

Overview

3 days

SAPPLM

mySAP PLMSolution Overview

2 days




SAP AG 2003

LO100/PLM300 Plant Maintenance (Level 2)

Course Prerequisites




SAP AG 2003

Target Audience

Participant

Project leaders who are responsible for the implementation

of WCM

Project teams that implement the WCM related business

processes

Consultants preparing for a WCM implementation

Duration: 3 days



© SAP AG PLM320 1-1

SAP AG 2001

Course objectives

Course content

Course overview diagram

Main business scenario

Contents

Course Overview




SAP AG 2001

At the conclusion of this course, you will be able to

Describe the WCM functions

Maintain WCM master data

Process WCM transactions

Configure WCM

Course Objectives






SAP AG 2001

Course Overview - Overview Diagram

Course Overview

Introduction

WCM Objects

Approvals

Lockout/Tagout

Order processing

Further functions

Customizing

W C M

WCM = Work Clearance Management




SAP AG 2001

IDES wants to ensure safety in the workplace while

maintenance work is performed WCM uses a clearly defined and easily

understandable process to make sure that

assets/technical systems are safe

Main Business Scenario




SAP AG 2001

General characteristics

Asset management

Maintenance process

Contents

Introduction




SAP AG 2001

Integrate WCM with your maintenance process

Describe the various structuring options

At the conclusion of this unit, you will be able to

Introduction: Objectives




SAP AG 2001

Introduction - Overview Diagram

WCM Objects

Approvals

Lockout/Tagout

Order processing

Further functions

Customizing

W C M

Course Overview

Introduction




SAP AG 2001


Asset management

Maintenance process

Contents

General Characteristics




SAP AG 2001

Need for WCM

Maintenance crews are working in a hazardous

environment (for example, high voltage, radiationexposure)

Maintenance measures need to be performed while

systems are operational

Operation of a technical system must not be affected

under any circumstances

There are work-related illnesses, which require special

health and safety measures

Inspections, repairs, or maintenance work for a technical object may only be carried out when measures

to ensure work safety have been implemented. These safety measures include, for example,lockout/tagout, fire protection, radiation protection.

Work Clearance Management (PM-WCM) enables you to control and monitor these activities. This

means you are able to ensure safe and secure working conditions for maintenance employees, observe

environmental regulations, and guarantee technical system availability.




SAP AG 2001

WCM Administration - Goals

Safety at work through

Formal communication

Data consistency

Approval and status control

Compliance with safety standards from regulatory agencies

Verification through

Change documents

Time stamp for all changes




SAP AG 2001

Asset Management


Asset management

Maintenance process

Contents




SAP AG 2001

Object links

Ref. locations

Functional locations

Equipment

Assembly Spare parts

ClassificationEquipment Func. locs.

BOMs

Basic Elements

Functional locations describe the structure of a technical system.

Individual components are described as equipment.

Object links represent connections between different technical systems.

The hierarchy of functional locations and equipment is used to structure technical assets.

Classification (classes and their characteristics) describes technical data for all kinds of objects.






SAP AG 2001

Structural Display

BOMsBOMs

Maintenanceitems

Maintenanceitems

General task listsGeneral task lists

Schedulingoverview

Schedulingoverview

Tasklists

Tasklists

Material stockMaterial stock

Object

links

Object

links DocumentsDocuments

Measurement pointsMeasurement points

Multi layer

list

Multi layer

list

NotificationsNotifications

Display

Create

ObjectsObjects OrdersOrders NotificationsNotifications Workorders

Workorders

Display

Create

Search for technical objects in a list or structural graphic

Hierarchical search, or search in object links

Display all object types (for example, functional locations, equipment, assemblies, spare parts)

Easy access to all information

No knowledge of numbering required




SAP AG 2001

Structure Indicator

Edit mask

Hierarchy levels

A = Alpha

N = Numerical

X = Alphanumerical

Plant

System

Sub-system

Function

Sub-functionItem

Functional

location keyA1

A1-B

A1-B02

A1-B02- 9

A1-B02- 9-CA1-B02- 9-C- 1

1 2 3 4 5 6

AN-ANN-N-X-X

You use the structure indicator to help you to identify a functional location. The structure indicator

includes two entry fields:

Edit mask

Hierarchy levels

You use the edit mask to control which marks are used for indicators (letters, numbers, or both). It also

controls how these indicators are grouped and how they are separated. The field hierarchy levels

defines where in the indicator each level ends, and how many hierarchy levels the structure can have in

total.

The indicator for a functional location can be up to 40 characters long (= maximum length of the the

edit mask).




SAP AG 2001

Structuring - Example

7070

7070

LAB10

LAB10 - AA005LAB10 - AA005

1000 12551000 1255

1000 13871000 1387

1000 13891000 1389

200 154

5000037950000379

200 432

FL

FL

FL

EQ

EQ

EQ

AB

MT

MT

AB

Block 7

Feed water supply system

Main slide valve

Slide valve with drive

Slide valve DN200

Variable speed drive

Motor

Brushes

...

Control

5000048350000483

FL = Functional location EQ = Equipment

AB = Assembly MT = Material

7070




SAP AG 2001


Asset management

Maintenance process

Contents

Maintenance Process




SAP AG 2003

WCM and the Maintenance Process

Work Clearance

Management

Work Clearance

Management

Work Clearance

Management

Work Clearance

Management

NotificationNotification Create

order

Create

order Release

order

Release

order Confirm

order

Confirm

order Complete

order

Complete

order

History/analysisHistory/analysis

Plan

order

Plan

order

SCADASCADA

Maintenance planMaintenance plan

Orders are linked to WCM at order header level.

For WCM-relevant orders you cannot perform the maintenance tasks until you have released them

(status "Released for Execution" (EXEC)). Setting the tasks to "released" depends on the WCM

architecture and whether the valuation was activated.

Connecting orders to WCM is not absolutely necessary. Work clearance management enables you to

carry out safety measures without an order. For example, this is the case if every change within the

asset should or must be documented but the order is not needed for planning or to collect costs.




Exercises

Unit: Introduction

At the conclusion of this unit, you will be able to:

• Use the structural display

• Identify the permits assigned to a technical object

• Create a notification or order (repeat of step from previouscourse)

You must be able to use the functional location structuring and

maintenance processing functions in IDES. This is a prerequisitefor the implementation of Work Clearance Management.

1-1 Functional location structure / Permits

1-1-1 Display the functional location structural display for your purification plant ##

(## is the number of your group). How do you do proceed? ______________________________________________________

______________________________________________________

______________________________________________________

______________________________________________________

1-1-2 Identify the permits that have been assigned to pump set 2. How do you do

this? ______________________________________________________

______________________________________________________

______________________________________________________

______________________________________________________




1-2 Notification / Order

1-2-1 Create a malfunction report for pump set 2.

Planner group: I##Planning plant: 1000

Main work center: T-ME##

How do you do proceed? ______________________________________________________

______________________________________________________

______________________________________________________

______________________________________________________

1-2-2 Create an order containing an operation for your malfunction report.

Order type: PM01Planning plant: 1000

Business area: 0001

Main work center: T-ME##How do you do proceed?

______________________________________________________

______________________________________________________

1-2-3 Set the order to Release (REL) without printing.

Malfunction report: _______________

Order: _______________




Solutions

Unit: Introduction

1-1 Functional location structure / Permits

1-1-1 SAP Menu Logistics Plant Maintenance Management of Technical

Objects Functional Location Structural Display (= IH01)

1-1-2 Select pump set 2

Environment Display object master record ( = <F6>)

Extras Permits ( = <Ctrl> + <F4>)

Permit assigned: WCM



Objects Functional Location Structural Display (= IH01) Select pump set 2

Goto Create notification Malfunction report

1-2-2 Maintenance notification Order Create Direct

1-2-3 Order Functions Release ... (= <Ctrl> + <F1>)




SAP AG 2001

Overview

Work approval

Applications

Work clearance application

Additional applications

Work Clearance Documents

WCD template

Operational WCD

Contents

WCM Objects




SAP AG 2001

Describe the different WCM objects

Explain the differences between WCM objects

Create WCM objects


WCM Objects: Unit Objectives




SAP AG 2001

WCM Objects - Overview

Approvals

Lockout/Tagout

Order processing

Further functions

Customizing

W C M

Course Overview

Introduction

WCM Objects




SAP AG 2001

Overview

Work approval

Applications




WCD template

Operational WCD

Contents

Overview






SAP AG 2001

Order

1001

Order

1001

Operational

WCD

4001

Operational

WCD

4001

WAP

2001

WAP

2001

Operational

WCD

4002

Operational

WCD

4002

Order

1002

Order

1002

WAP

2002

WAP

2002

Operational

WCD

4004

Operational

WCD

4004

Operational

WCD

4005

Operational

WCD

4005

Order

1004

Order

1004Order

1003

Order

1003

Operational

WCD

4003

Operational

WCD

4003

WCA

3002

WCA

3002WCA

3001

WCA

3001......

Enhanced Model: Example

The enhanced model is useful if you want to use the system to monitor other safety measures (for

example, radiation or fire protection) in addition to lockout/tagout.






SAP AG 2003

Order Order

Work ApprovalWork Approval

ApplicationsApplications

Work Clearance

Documents

Work Clearance

Documents

Plant Maintenance

Plant Maintenance

Production

Production

Production

Plant Maintenance Work clearance

application

Applications for

Radiation protection

Fire protection

Operational WCD

WCD template

Communication

Integration between Work Clearance Management and the maintenance process requires good

communication between plant maintenance and other departments.




SAP AG 2003

WCM object

Filter for data copy

(Customizing)

Filter for data copy

(Customizing)

Order Order

Work ApprovalWork Approval

ApplicationsApplications

Work Clearance

Documents

Work Clearance

Documents

Creation with Reference

Data to be copied

Header data

Items (just for work clearance documents)

Additional data (just for WCM objects)

- Long texts

- Object list

- Documents

- Catalogs




SAP AG 2001

Overview

Work approval

Applications




WCD template

Operational WCD

Contents

Work Approval




SAP AG 2003

Work Approval

Work

clearance

application

Operational WCD

Enhanced model

Further

applications

Order

Work Approval

Only used in the

enhanced model

WCM object for control

and communication

between orders and

applications

Umbrella WCM object for

orders and applications

The work approval is a WCM object for controlling communication between maintenance orders and

applications. The work approval requires safety measures designed to ensure that work on a technicalsystem is carried out in a hazard-free environment. As a superior WCM object, the work approval may

include a work clearance application with additional applications (for example, boiler inspection

certificate).

Work approval is only used in the enhanced model, and represents the central safety certificate.

On the one hand, work approvals are assigned to orders where tehy control the status "Released for

execution". On the other hand, work approvals are assigned to applications that they control and check.




SAP AG 2003

Work Approvals: Data

General data

Reference object

Areas of responsibility

Location data

Planning data

Assignment of partners:

different roles possible

Long text processing:

several internal remarks

Assignment of documents:

link to document management system

Assignment of permits:

cross-document, interactive

Use of catalog technique:

catalog groups and codes

Status processing and audit trail:

system status and user status

Assignment of technical objects:

equipment and functional locations

Generic object services:

different services are possible

General data

Short text, use of work approval, validity period, priority, recall time, general status, overall condition,revision phase

Reference object

Either functional location or equipment and section.


Maintenance planning plant, maintenance planner group, WCM work center, plant for work center and

authorization group

Location data

Maintenance plant, location, room, and business area

Planning data

Basic date, scheduling, and actual date




SAP AG 2003

Work Approval: Status Sequence (1/2)

CLSDCLSDCLSDCLSD

CRTECRTE

PREPPREP

PWPPWP

WOCOWOCO

EXECEXEC

Orders ApplicationsWork approval

CRTECRTE

PREPPREP

PWPPWP

You can only complete (CLSD) the work approval when work is completed (WOCO) for all orders

that are assigned.




SAP AG 2003

Work Approval: Status Sequence (2/2)

(3)

REJCREJCINACINACPREPPREP

CHNGCHNG


CRTECRTE

DLFLDLFL

(1)

DLFL

DLFLREJCREJC

INACINAC

(4)

PWPPWPCHNGCHNG

PREPPREP

INACINAC REJCREJC

(2)

CLSDCLSD(5)

CLSDCLSD REJCREJC

DLFLDLFL

(1) The status "Created" (CRTE) is a prerequisite for the status "Prepared" (PREP), "Object

deactivated" (INAC), "Rejected" (REJC) and "Deletion Flag" (DLFL).

(2) The status "Prepared" (PREP) is a prerequisite for the status "Change mode" (CHNG), "Work

permit printed" (PWP), "Object deactivated" (INAC), "Rejected" (REJC) and "Deletion Flag"

(DLFL).

(3) The status "Change mode" (CHNG) is a prerequisite for the status "Prepared" (PREP), "Object

deactivated" (INAC), and "Rejected" (REJC).

(4) The status "Object deactivated" (CRTE) is a prerequisite for the status "Rejected" (REJC) and

"Deletion Flag" (DLFL).

(5) The status "Completed" (CLSD) or the status "Rejected" (REJC) is a prerequisite for the status


In some cases, there may be additional prerequisites for the individual statuses!




SAP AG 2001

Order

1001

Order

1001Order

1002

Order

1002Order

1003

Order

1003

WAP

2001

WAP

2001

WCA

3001

WCA

3001WCA

3002

WCA

3002

Order

1005

Order

1005

WAP

2002

WAP

2002

WCA

3003

WCA

3003

Order

1006

Order

1006

WAP

2003

WAP

2003

Work Approval: Links

WCA

4002

WCA

4002

(R3)

(R5)

Observe the following assignment rules:

You can assign a work approval to several different orders. Only one work approval may be assigned

to each order. (Assignment rule R3)

An application may be assigned to several work approvals (and vice versa). (Assignment rule R4)

A work approval can only be assigned to one application per application type – this means, for

example, that you cannot assign several work clearance applications to a work approval. (Assignment

rule R5)




SAP AG 2003

Overview

Work approval

Applications




WCD template

Operational WCD

Contents:





SAP AG 2003


Enhanced model

WCM object for control and

communication between workapprovals and Operational

WCDs

Umbrella document for work

approvals and Operational

WCDs

Standard model

WCM object for control and

communication between orders

and Operational WCDs

Umbrella document for orders

and Operational WCDs

Order

WC

application

Operational WCD

Standard model

Order

Work Approval

WC

application

Operational

WCD

Enhanced model

Further

applications

The work clearance application represents the safety certificate for lockout/tagout.

In the enhanced model, you use a work clearance application to control communication between work

approvals and Operational WCDs.

In the standard model, you use a work clearance application to control communication between orders

and Operational WCDs. Direct assignment to orders enables the work clearance application to control

the issuing of the status "Released for execution" in the order through the approval status.




SAP AG 2003

Work Clearance Application: Data

General data

Reference object


Location data

Planning data

















General data

Short text, use of application, validity period, priority, recall time, general status, overall condition,revision phase

Reference object




authorization group

Location data


Planning data





SAP AG 2003

Work Clearance Application: Status Sequence (1/2)

Orders or

work approvals Operational WCDsWC application

PREPPREP

PWPPWP

TENTTENT

CLSDCLSD

UNTUNT

TESTTEST

CRTECRTE

??

Enhanced model

You can only complete (CLSD) the work clearance application when all work approvals assigned

have been completed (CLSD).

Standard model

You can only complete (CLSD) the work clearance application when work is completed (WOCO)

for all orders that are assigned.




SAP AG 2003

Work Clearance Application: Status Sequence (2/2)

(3)


CHNGCHNG


CRTECRTE

DLFLDLFL

(1)

PWPPWPCHNGCHNG

PREPPREP

INACINAC REJCREJC

(2)

CLSDCLSD

DLFLDLFL

REJCREJC

INACINAC

(4)

(5)

CLSDCLSD REJCREJC

DLFLDLFLTENTTENT

(1) The status "Created" (CRTE) is a prerequisite for the status "Prepared" (PREP), "Object

deactivated" (INAC), "Rejected" (REJC) and "Deletion Flag" (DLFL).

(2) The status "Prepared" (PREP) is a prerequisite for the status "Change mode" (CHNG), "Work

permit printed" (PWP), "Object deactivated" (INAC), "Rejected" (REJC) and "Deletion Flag"

(DLFL).

(3) The status "Change mode" (CHNG) is a prerequisite for the status "Prepared" (PREP), "Object

deactivated" (INAC), and "Rejected" (REJC).

(4) The status "Object deactivated" (CRTE) is a prerequisite for the status "Rejected" (REJC) and


(5) The status "Completed" (CLSD) or the status "Rejected" (REJC) is a prerequisite for the status


In some cases, there may be additional prerequisites for the individual statuses!




SAP AG 2001

WAP

2001

WAP

2001

WCA

3001

WCA

3001

WAP

2002

WAP

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

WCA

3001

WCA

3001WCA

3002

WCA

3002

Operational

WCD

4001

Operational

WCD

4001

Operational

WCD

4002

Operational

WCD

4002

Standard model

Order

1001

Order

1001

Work Clearance Application: Links

(R1)

Observe the following assignment rules:

Enhanced model

- An application may be assigned to several work approvals (and vice versa). (Assignment rule R4)

- A work approval can only be assigned to one application per application type – this means, for

example, that you cannot assign several work clearance applications to a work approval.

(Assignment rule R5)

- A work clearance application may be assigned to several Operational WCDs (and vice versa).


Standard model

- You can assign a work clearance application to several different orders. Only one order can be

assigned to each work clearance application. (Assignment rule R1)

- A work clearance application may be assigned to several Operational WCDs (and vice versa).





SAP AG 2003


Overview

Work approval

Applications




WCD template

Operational WCD

Contents:




SAP AG 2003

Order

Work

clearance

application

Operational WCD

Enhanced model

?

Work Approval


Stipulate whether you want to document and track different safety measures separately in your system.

If this is the case, you need additional applications.

As well as a work clearance application that displays the safety certificate especially for the

lockout/tagout, it can also be necessary to take additional safety measures into consideration, for

example, radiation protection, fire protection, or boiler protection. These safety measures are

represented in the additional applications.

The additional applications can only be used in the enhanced model of Work Clearance Management.

They are combined with the work clearance applications under the work approval.

The additional applications are industry-specific and necessary if additional safety measures must be

managed as independent WCM objects in the system. They are programmed using the ABAP

workbench.




SAP AG 2001

Overview

Work approval

Applications




WCD template

Operational WCD

Contents





SAP AG 2003

Work Clearance Document

The work clearance document contains a detailed description of lockout/tagout.

The work clearance document is the only WCM object that also has items apart from the header data.

As items, specify all the technical objects that are to be processed in connection with a lockout/tagout.

The WCD may include equipment, functional locations, technical objects, that are not managed in the

R/3 structure, and comments.

The work clearance document has a header like every WCM object. It also has the following screens:

Maintenance screen

Switching screen (not for WCD templates)




SAP AG 2003

Header Header

ItemItem

ItemItem

ItemItem

......

Work Clearance Document: Structure

WCD template

Template library Cannot be used to perform

lockout/tagout

Operational WCD

Can be assigned to work

clearance applications

Can be used to perform

lockout/tagout

There are two types of WCD:

WCD template

The WCD template is not used itself to perform lockout/tagout. You cannot switch or assign the

WCD template. The WCD template serves only as a standard template. This means that you do not

always have to create a new WCD for complex technical system structures.

The WCD template enables you to create a template library.

A library of WCD templates makes planning a lot simpler for lockout/tagout, improving safety.

The advantage of creating a WCD template is that these work clearance documents are higher

quality. When you copy from another operational WCD, particular attention is needed with regard to

altered untagging conditions.

Operational WCD

You use the Operational WCD to perform lockout/tagout - you can switch and assign the Operational

WCD.




SAP AG 2003

Work Clearance Document (Header): Data

General dataGeneral data

Reference objectReference object

Areas of responsibilityAreas of responsibility

Location dataLocation data

Planning dataPlanning data

















General data

Short text, use of WCD, validity period, priority, recall time, general status, overall condition, revision phase

Reference object




authorization group

Location data


Planning data





SAP AG 2003

Work Clearance Document (Item): Data

Item categoryItem categoryTechnical object or short textTechnical object or short text

Operational groupOperational group

Data for the taggingData for the tagging

Data for theData for the untagginguntagging

Additional dataAdditional data

General dataGeneral data







Item category Technical object or short text

Operational group

Data for the tagging Tagging condition, tagging type, and sequence of the tagging

Data for the untagging Untagging condition, untagging type, and sequence of the untagging.

Additional data Indicator: Physical safety required, safety category, indicator: tag required, print

format and tag number.

General Data Location, switching location, and commentary




SAP AG 2003

PREPPREP

CRTECRTE

PROCPROC

ITGITG

PTAGPTAG

BTGBTG

UNTUNT

ETGETG

EUGEUG

BUGBUG

CLSDCLSD

PTSTPTST

ETUGETUG

BTUGBTUGTESTTESTPTAGPTAG

BTGBTG

ETGETG

EUGEUG

BUGBUG

PTSTPTST

ETUGETUG

BTUGBTUG

ITGITG

Header Item

CONFCONFCONFCONF

Operational WCD: System Sequence

Progress in the operational cycle is displayed for the item and also in the Operational WCD header:

If all items have the same operational status, the status is displayed in the header.

If only one conflict appears during switching, this is displayed in the header.




SAP AG 2001

WCA

3001

WCA

3001

Operational

WCD

4001

Operational

WCD

4001

Operational

WCD

4002

Operational

WCD

4002

WCA

3002

WCA

3002

Operational

WCD

4003

Operational

WCD

4003

Operational WCD: Links

Observe the following assignment rule:

A work clearance application may be assigned to several Operational WCDs, and vice versa

(assignment rule R2).




SAP AG 2003

Data flow

Current


Other Work Clearance Documents

Clipboard

List comparison

Graphic planning

Any


You can use any work clearance document as a template for creating another work clearance document.

You have the option of connecting any external systems for processing, visualizing, and maintaining

work clearance documents. The most common example is connecting to a graphic planning system,

with which you can process items for work clearance documents.

You can compare a work clearance document with your template or with other work clearance

documents. The system then compares only the items of the work clearance documents to be compared.

To track changes in the template or adapt one work clearance document to another, you can copy items

in the clipboard.

You can copy items from other work clearance documents to the clipboard.




SAP AG 2001

Describe the different WCM objects

Explain the differences between WCM objects

Create WCM objects

You are now able to

WCM Objects: Summary




Exercises

Unit: WCM Objects


• Create a work clearance application

• Create a WCD template

• Create an Operational WCD based on a WCD template

• Assign an Operational WCD to a work clearance application

At IDES, you must first create a work clearance application for

the order before performing maintenance tasks.

Technical objects whose operational condition is to be changedshould be listed in an Operational WCD.

You can use a WCD template to speed up the creation of the

Operational WCD.

2-1 Work clearance application

2-1-1 Create a work clearance application for your order.Planning plant: 1000

Responsible work center: T-ME##How do you do proceed?

______________________________________________________

______________________________________________________

______________________________________________________

______________________________________________________

Work clearance application: _______________




2-2 WCD template

2-2-1 Use the tagging for pump set 2 to create a WCD template. Copy the pump

station and pump set 1 to the object list.

Planning plant: 1000Responsible work center: T-ME##

How do you do proceed?

______________________________________________________

______________________________________________________

______________________________________________________

______________________________________________________

WCD template: _______________

2-3 Operational WCD

2-3-1 Assign an Operational WCD to your work clearance application. This

Operational WCD is based on your WCD template.How do you do proceed?

______________________________________________________

______________________________________________________

______________________________________________________

______________________________________________________

Operational WCD: _______________

Tagging for pump set 2




Solutions

Unit: WCM Objects

2-1 Work clearance application

2-1-1 SAP Menu Logistics Plant Maintenance Maintenance Processing

Order Change (= IW32)

<WC application> (= <Ctrl> + <Shift> + <F9>)

<Copy> (= <F5>)

2-2 WCD template

2-2-1 ... SAP Menu Logistics Plant Maintenance Work Clearance

Management WCD template Create (= WCT1)

2-3 Operational WCD

2-3-1 ... WC application Change (= WCTL)

Goto Links Work clearance document (= <Shift> + <F8>)

<Create> (= <Shift> + <F5>)




SAP AG 2001

Overview

Approval process across WCM objects

Contents

Approvals




SAP AG 2001

Explain the term Approvals

Differentiate between approvals and work

approvals

Use approvals


Approvals: Unit Objectives




SAP AG 2001

Approvals: Overview

Lockout/Tagout

Order processing

Further functions

Customizing

W C M

Course Overview

Introduction

WCM Objects

Approvals




SAP AG 2001

Overview


Contents

Overview




SAP AG 2001

Overview

Operational

WCD

...

WCA

Order

WAP

WCM approvals belong to the approvals for Plant Maintenance.

The approvals are assigned to WCM objects at header level. It is possible to assign an approval to

several WCM objects. This is not recommended.

Processing depends on authorization.

All activities are recorded.




SAP AG 2003

Basic Functions

Before starting the approval process

Assignment to a WCM object Deleting the assignment

During the approval process

Granting approval

Withdrawing approval

The approval process begins when you set the status "Prepared" (PREP) in the WCM object. This

means that you can now grant or revoke approvals, but you can no longer assign or delete approvals to aWCM object.

You always assign an approval at the header level of the WCM object. This means you approve the

entire WCM object and not individual items.

You can assign more than one approval to a WCM object. However, each approval may only be used

once for each WCM object. You can also assign an approval to more than one WCM object; however,

this is not recommended for reasons of clarity.




SAP AG 2001

Additional Functions (1/3)

1

4

2

3

AA

BB

GG

DDCC

EE FF

Approval Hierarchy level

Hierarchy level support

All approvals at a particular hierarchy level must be granted.

Within a hierarchy level, there is no fixed order for granting approvals




SAP AG 2003


Automatic withdrawal of approvals based on

the hierarchy level

a system status

Automatic assignment of approvals when you create a WCM

object

Protecting approvals from deletion

Traffic light indicator for approval status

Automatic granting of approvals

The traffic light indicator colors signify the following:

Red No required approval has been granted.

Yellow At least one required approval has been granted, but at least one

required approval is missing.

Green All required approvals have been granted.

We recommend that exactly two approvals influence the traffic light indicator. This ensures that the

relationship between colors and approvals is absolutely clear.




SAP AG 2001


Blocking granting of approvals

Based on existing assignments to WCM objects

An assignment must exist for the approval

Identify the direction

This function safeguards the approval process across WCM

objects

Based on system or user status

Status is assigned to an approval

Approval can only be granted when the status assigned is

active

Missing approval -- Approval granted




SAP AG 2003

Why can an Approval not be Granted?

BB

AA

CC

DD

A superior approval has notbeen granted

Dependent approvals from

assigned WCM objectshave not been granted

Required assignments are not

in place

The required system or user

status is not active

Your goal is:

Approval A should be granted before approval B:

Assign approval A to hierarchy level 1, and approval B to hierarchy level 2. This means that

approvals cannot be granted at superior hierarchy levels (for example, 2) until they have been granted

at lower hierarchy levels (for example, 1).

Approval may only be granted if an Operational WCD has been assigned:

Activate the assignment function for the work clearance application. Ensure that there is a

dependence with subordinate WCM objects (Operational WCDs).

Approval for an Operational WCD can only be granted when the Operational WCD is tagged:

Assign the system status Tagged (ETG) to the approval. This means the person responsible can only

issue approval when the Operational WCD is tagged.




SAP AG 2001

Overview


Contents

Approval Process Across WCM Objects




SAP AG 2001

Approval Process Across WCM Objects

Approval

Approval category

Indicator:process relevant

Direction

A y

B y

C y

Work approval

Operational WCD

Work clearance

application

The approval process transports information at all levels of the WCM object.

Each level can trigger or block the approval process.

Within an approval category you can specify that approval will be granted for a WCM object dependent

on whether an approval has already been granted to an assigned WCM object.

The dependency may be in the direction of a superior WCM object, a subordinate WCM object, or

neutral.

The direction defines from which direction approvals should be considered – from superior (UP) or

from subordinate (DN) WCM objects.

For approvals in an approval category, if a dependency from a superior WCM object to a subordinate

WCM object has been defined (and the opposite is also true), these dependencies will be completely

ignored. Missing approval – Approval granted




SAP AG 2001

Approval Process Across WCM Objects: Example (1/2)

B

A

C

D

E

FF y

A X

E y

B X

D y

C X

Type x approvals are controlled from below to above – that means approvals are required at lower

levels.

Type y approvals are controlled from above to below – that means approvals are required at higher

levels.




SAP AG 2001

Approval Process Across WCM Objects: Example (2/2)

F1

E

B

A1

X

y

?

?

F2

D

C

A2 ?

?

X

yF1 F2

E

D

C

B

A1 A2

Type y approvals are controlled from below to above – that means approvals are required at lower

levels.

Type x approvals are controlled from above to below – that means approvals are required at higher

levels.




SAP AG 2001

Explain the term Approvals

Differentiate between approvals and work

approvals

Use approvals

You are now able to

Approvals: Summary







Exercises

Unit: Approvals


• Explain the reason for approvals

• Use approvals

IDES uses approvals to guarantee safe and secure work clearance

management.

3-1 At what level do you assign approvals to WCM objects? ____________________________________________________________

____________________________________________________________

3-2 Is it possible to assign approvals to items in a WCD? ____________________________________________________________

____________________________________________________________

3-3 How do you initiate the approval process?

____________________________________________________________ ____________________________________________________________

3-4 What is the relationship between WCM approvals and permits for Plant Maintenance?

____________________________________________________________

____________________________________________________________

3-5 Is it possible to define dependencies between approvals: – in a WCM object?

– between two WCM objects?

____________________________________________________________ ____________________________________________________________




3-6 What logical connection links approvals at a hierarchy level? ____________________________________________________________

____________________________________________________________

3-7 Do all approvals affect the approval status?

____________________________________________________________

____________________________________________________________

3-8 Is it possible to automate the approval process?

____________________________________________________________

____________________________________________________________

3-9 How can the granting of an approval be blocked?

____________________________________________________________ ____________________________________________________________

3-10 Is it possible to copy approvals? ____________________________________________________________

____________________________________________________________

3-11 Is it possible to construct a reciprocal relationship between the approval processes in

different WCM objects?

____________________________________________________________ ____________________________________________________________

3-12 How does the system deal with missing approvals?

____________________________________________________________ ____________________________________________________________

3-13 What problem may arise here? ____________________________________________________________

____________________________________________________________

3-14 How can you protect the reciprocal relationship between different WCM objects?

____________________________________________________________ ____________________________________________________________

3-15 When or where are approvals granted automatically? ____________________________________________________________

____________________________________________________________




Solutions

Unit: Approvals

3-1 At WCM object header level.

3-2 No, the assignment only takes place at header level in the WCM object.

3-3 The WCM object must be prepared (PREP).

3-4 WCM approvals form part of the permits for Plant Maintenance.

3-5 Yes, you can define dependencies in a WCM object and between WCM objects.

3-6 The AND connection – all approvals at a given hierarchy level must have beengranted before approvals at the next hierarchy level can be processed.

3-7 No, only the approval for which the corresponding flag was set.

3-8 Yes, you can automate the approval process.

3-9 You can use User status, for example, to block granting of approvals.

3-10 No, you cannot copy approvals.

3-11 Yes, you can build a reciprocal relationship.

3-12 Missing approval = Approval granted

3-13 If you delete an approval assignment, that corresponds to granting an approval.

3-14 You make the assignment compulsory.

3-15 In the change mode of the corresponding WCM object.




SAP AG 2001

Operational cycle

Checks

Conflict rules

Simulations

Operational protection and protected areas

Adjust untagging

Contents

Lockout/Tagout




SAP AG 2001

Perform lockout/tagout


Lockout/Tagout: Unit Objectives




SAP AG 2001

Lockout/Tagout: Overview

Order processing

Further functions

Customizing

W C M

Course Overview

Introduction

WCM Objects

Approvals

Lockout/Tagout




SAP AG 2003

Overview

Overview

Operational Cycle

Checks

Conflict Rules

Simulations

Operational Protection ? Protected Areas

Adjust Untagging

Contents:




SAP AG 2003

Lockout/Tagout

Order

WC

application

Operational WCD

Standard model

Order

Work

clearance

application

Operational WCD

Enhanced model

Further

applications

Work Approval

This process is composed of the orderly tagging and later untagging of technical objects, so that

maintenance tasks and tests can be performed safely at the technical objects.

The operational processing of lockout/tagout is described with the help of the operational cycle.

For a lockout/tagout that is assigned to locations, shop papers are required on site for the switching.

This involves an operational list, that is a list of the individual switching actions to be performed, and

so-called tags and test tags. Operational lists and tags and test tags can be printed according to the

layout details of the plant concerned.

Checks and simulations help you to ensure that lockout/tagout is safe and can be processed without any

conflicts.




SAP AG 2003

Overview

Operational Cycle

Checks

Conflict Rules

Simulations

Operational Protection Protected Areas

Adjust Untagging

Contents

Operational Cycle




SAP AG 2001

Operational Condition

Operational conditions give a detailed description of

conditions or parameters for technical objects (for

example, Open, Closed ):

Tagging condition = operational condition for tagging

Untagging condition = operational condition for (temporary)

untagging

OpenOpen

ClosedClosed

For each operational condition you can define whether it is valid for tagging, (temporary) untagging, or

for both.

You can group operational conditions logically:

An operational group is a logical grouping of operational conditions designed to minimize conflict

rules.

An operational class is a logical grouping of operational conditions based on the technical

characteristics of technical objects.




SAP AG 2003

Operational Types

Operational types allow use of different tags for the same

operational condition (for example, red/yellow/white tags)

Tagging type = operational type for tagging

Untagging type = operational type for (temporary)

untagging

Operational types help you to further define same operational conditions.

The choice of conflict rules influences the use of the operational type.




SAP AG 2001

Operational Groups

ElectricalMechanical

OFF

Open

Closed

ON

Logical grouping of

operational conditions

to minimize conflict

rules

Where conflict rules

apply

You can assign operational conditions to several operational groups.

We recommend that you only assign an operational condition to one operational group.

Operational groups are not the same as Operational classes




SAP AG 2003

Operational Phase

Phase in the operational cycle during which an

Operational WCD item goes through several statuses in

a certain order.

Condition changes are recorded. There are three

operational phases:

Tagging phase

Temporary untagging phase

Untagging phase

The first status in the operational phase gives notices of an activity - a change of operational

condition/type:

Tag (BTG)

Untag temporarily (BTUG)

Untag (BUG)

An operational tag is printed, the status following confirms the print:

Tag printed (PTAG)

Test tag printed (PTST)

The last status confirms that the activity has been performed on location:

Tagged (ETG)

Temporarily untagged (ETUG)

Untagged (EUG)




SAP AG 2003

Operational Cycle

Temporaryuntagging phase

Temporaryuntagging phase Untagging phaseUntagging phaseTagging phaseTagging phase

Tagging cycle with temporary untagging phase

Temporary

untagging phase

Temporary

untagging phaseTagging phaseTagging phase

Test cycle

Untagging phaseUntagging phaseTagging phaseTagging phase

Tagging cycle without temporary untagging phase

The operational cycle is a cycle consisting a maximum of three operational phases.

The operational cycle may be formed in various different ways:


Test cycle


In each operational cycle, the Operational WCD items go through several statuses in a particular order:

Tagging phase = tag (BTG), tag printed (PTAG), tagged (ETG)

Temporary untagging = untag temporarily (BTUG), test tag printed (PTST), temporarily untagged

(ETUG)

Untagging phase = untag (BUG), untagged (EUG)




SAP AG 2003

Operational Cycle: Example

Standard operational cycle

ITGITG

PTAGPTAG

ETGETG

BTGBTG

BTUGBTUG

ETUGETUG

PTSTPTST

BUGBUG

EUGEUG

Reduced operational cycle Initial status (ITG)

Tagging phase

Tag (BTG)

Tag printed (PTAG)

Tagged (ETG)

Temporary untagging phase

Untag temporarily (BTUG)

Test tag printed (PTST)

Temporarily untagged (ETUG)

Untagging phase

Untag (BUG)

Untagged (EUG)

ITGITG

PTAGPTAG

ETGETG

EUGEUG

You can reduce the operational cycle.

If you use Operational WCDs you can skip the following statuses

Starting status

- Tag (BTG)

- Untag temporarily (BTUG)

- Untag (BUG)

Print status

- Tag printed (PTAG)

- Test tag printed (PTST)

End status

- Temporarily untagged (ETUG)

- Untagged (EUG)

The entire operational cycle is processed internally




SAP AG 2001

PREPPREP

CRTECRTE

PROCPROC

ITGITG

PTAGPTAG

BTGBTG

UNTUNT

ETGETG

EUGEUG

BUGBUG

CLSDCLSD

PTSTPTST

ETUGETUG

BTUGBTUGTESTTESTPTAGPTAG

BTGBTG

ETGETG

EUGEUG

BUGBUG

PTSTPTST

ETUGETUG

BTUGBTUG

ITGITG

Header Item

CONFCONFCONFCONF

POSTPOST PROTPROT

Operational WCD: System Sequence

Progress in the operational cycle is displayed for the item and also in the Operational WCD header:

If all items have the same operational status, the status is displayed in the header.

If only one conflict appears during tagging/untagging, this is displayed in the header.




SAP AG 2003

Overview

Operational Cycle

Checks

Conflict Rules

Simulations


Adjust Untagging

Contents.

Checks




SAP AG 2001

General Checks

For each operational step, the system checks if

The user has authorization

Tagging/untagging is blocked by an approval

Tagging/untagging is blocked by operational protection

This is a valid operational step

Checks help you to ensure that lockout/tagout is safe and that it avoids conflicts. Some checks are

optional, some compulsory.

You can deactivate optional checks in Customizing.




SAP AG 2001

Further Checks: Overview

BTG PTAG ETG BTUG PTST ETUG BUG EUG

Reference object

Time frame

Completeness

and correctness

Test Cycle

Untagging

Conflict

Tagging phase Temporary untagging phase Untagging phase

Tagging phase Temporary untagging phase Untagging phase

Tag (BTG) Untag temporarily (BTUG) Untag (BUG)

Tag printed (PTAG) Test tag printed (PTST) Untagged (EUG)

Tagged (ETG) Temporarily untagged (ETUG)




SAP AG 2003

Check: Reference Object

Prerequisite

When the operational process begins, a reference object log

is kept in the system until the Operational WCD is completed.

Check

For each technical object to be tagged/untagged, the system

checks if this object is already a reference object in a

processed Operational WCD. Every agreement is displayed.

Optional check to see if the object to be tagged/untagged is not already a reference object in an active

lockout/tagout situation.

The check is for information purposes only and does not affect tagging/untagging.

You can deactivate the check.




SAP AG 2003

Check: Time Frame

Prerequisite

At the start of a new operational phase, the system logs the

chosen operational condition/type. This entry is only deleted

once the operational condition/type is confirmed.

Check

The system checks if there are existing entries for technical

objects to be tagged/untagged. A technical object cannot

have different operational conditions.

Optional check whether a technical object (that should be tagged/untagged and thereby obtain a new

operational condition/type) does not already have another operational condition/type within anoperational group not yet confirmed in the system.

You cannot ignore the check.

You can alter or deactivate the check.




SAP AG 2003

Check: Completeness and Correctness

Prerequisite

Unlike the tagging condition/type, the untagging

condition/type must first be maintained for (temporary)

untagging.

Check

The system checks at the start of the (temporary) untagging

phase if the untagging condition/type has been maintained.

Compulsory check

If the required untagging condition/type has been maintained for a technical object. At the latest, youmust maintain this by the time of (temporary) untagging.

You cannot ignore the check.




SAP AG 2003

Check: Test Cycle

Prerequisite

All work clearance applications assigned are either complete,

or they permit a test cycle - this means a test cycle is allowed

for the Operational WCD.

The system checks if a test cycle is possible for the

Operational WCD.

Compulsory check

The system checks if a test cycle is permitted for the Operational WCD.

You cannot ignore the check. Special authorization is required to do that.




SAP AG 2003

Check: Untagging

Prerequisite

All work clearance applications assigned are complete - this

means the Operational WCD is untaggable.

Check

The system checks if the Operational WCD is untaggable.

Compulsory check

The system checks if the Operational WCD can be untagged.

You cannot ignore the check. Special authorization is required to do that.




SAP AG 2003

Check: Conflict

Prerequisite

A conflict record is written at the start of a new tagging

phase. You can only delete this entry when the item is

(temporarily) untagged.

Check

At the beginning of an operational phase, the desired

operational condition/type for a technical object is checked

against all conflict records. This check is based on general or

user-defined conflict rules.

Compulsory check

If required operational conditions/types for a technical object can be switched within an operationalgroup.

In case of conflict, you can

Cancel switching and deal with the conflict or

Ignore the conflict and go ahead with the switching. Special authorization is required to do that.

In the case of a conflict that you have ignored, the system assigns the status conflict (CONF) to the

technical object. The system always assumes that the switch was performed. For example: the

operational condition/type A generates conflicts. If you ignore these conflicts, then A is the new

operational condition/type for the system.

If the technical object for which the conflict occurred is untagged during the switching, then the conflictis automatically withdrawn.




SAP AG 2003

Overview

Operational Cycle

Checks

Conflict Rules

Simulations

Operational protection Protected areas

Adjust Untagging

Contents:

Conflict Rules




SAP AG 2001

Conflict Rules

User-defined

conflict rules

General conflict

rules

The conflict check is based on the conflict rules.

Conflict rules apply to tagging and untagging.

You can decide whether to use the general or user-defined conflict rules. The decision is taken at

company level for each planning plant.

The conflict rules only apply within an operational group.




SAP AG 2001

General Conflict Rules

If the user does not define conflict rules, the system compares

the current and target operational types.

The result is either N = Note (Same)

E = Error message (Different)

Consequences

The operational type cannot be overwritten

Operational conditions have no impact on the conflict check

You cannot define asymmetric conflict rules

For operational group E (= electrical) we have two different operational conditions:

(ON/OFF)

Two different operational types are required for these operational conditions:

(1, 2)




SAP AG 2003

User-Defined Conflict Rules

If the user defines conflict rules, the system compares the

current and target operational conditions/types.

The result is either N = Note

W = Warning

E = Error

Consequences

You can overwrite the operational type

Operational conditions influence the conflict check

You are able to define asymmetric conflict rules

The system interprets missing conflict rules as errors

For operational group E (= electrical) we have two different operational conditions:

(ON/OFF)

There are three different operational types for these operational conditions:

(RED, YELLOW, WHITE)

2 x 3 = 6 possible combinations from operational condition/type

When performing conflict checks, the system will compare current operational condition/type and

target operational condition/type. In this case, that means a possible 6 x 6 = 36 conflict rules.




SAP AG 2003

Overview

Operational Cycle

Checks

Conflict Rules

Simulations


Adjust Untagging

Contents:

Simulations




SAP AG 2001

Simulations

What would happen if ...?

You can run each check as a simulation.

There are simulations without a corresponding check.

You can start each simulation manually.

Some simulations start automatically.




SAP AG 2003

Overview

Operational Cycle

Checks

Conflict Rules

Simulations


Adjust Untagging

Contents:





SAP AG 2003

Operational Protection

This ensures that the operational condition of a technical

object in an Operational WCD may only be changed from

specific Operational WCDs.

Once operational protection has been set, you can only change

operational condition from Operational WCDs that are directly

linked as a result of superior work clearance applications (=

protected areas).

The operational protection only applies within an operational

group.

Operational protection enables you, for example, to shield the change in Operational condition of an

Operational WCD item against other Operational WCDs for test purposes.

Usage defines if an Operational WCD is able to set operational protection.

The operational protection always applies to the technical object and the operational group assigned to

it.




SAP AG 2003

Protected Areas

Operational WCDs from which it is possible to change the

operational status of a technical object (after operational

protection has been set).

The protected area includes all Operational WCDs that are

directly linked as a result of superior work clearance

applications.

A technical object can be switched within the protected area, but outside the protected area a technical

object cannot be switched.

The protected area is displayed on the switching screen.




SAP AG 2003

Protected Areas: Example (1/2)

WCA

3001

WCA

3001WCA

3002

WCA

3002

Operational

WCD

4001

Operational

WCD

4001

Operational

WCD

4002

Operational

WCD

4002

Operational

WCD

4003

Operational

WCD

4003

Operational

WCD

4004

Operational

WCD

4004

WCA

3001

WCA

3001WCA

3002

WCA

3002

Operational

WCD

4001

Operational

WCD

4001

Operational

WCD

4002

Operational

WCD

4002

Operational

WCD

4003

Operational

WCD

4003

Operational

WCD

4004

Operational

WCD

4004

(1)

(2)

Protected areaOperational Protection

(1) An operational protection is set for an item of operational WCD 4001. Because of the assigned work

clearance application 3001, both operational WCDs 4001 and 4002 form the protected area.


clearance application 3001 and 3002, the operational WCDs 4001, 4002, and 4003 form the protected

area.




SAP AG 2003

Protected Areas: Example (2/2)

WCA

3001

WCA

3001WCA

3002

WCA

3002

Operational

WCD

4001

Operational

WCD

4001

Operational

WCD

4002

Operational

WCD

4002

Operational

WCD

4003

Operational

WCD

4003

Operational

WCD

4004

Operational

WCD

4004

WCA

3001

WCA

3001WCA

3002

WCA

3002

Operational

WCD

4001

Operational

WCD

4001

Operational

WCD

4002

Operational

WCD

4002

Operational

WCD

4003

Operational

WCD

4003

Operational

WCD

4004

Operational

WCD

4004

(3)

(4)


clearance application 3002, the operational WCDs 4002 and 4003 form the protected area.

(4) An operational protection is set for an item of operational WCD 4004. As there is no work clearance

application assigned to the operational WCD, operational WCD 4004 forms the protected area.




SAP AG 2003

Overview

Operational Cycle

Checks

Conflict Rules

Simulations


Adjust Untagging

Contents:

Adjust Untagging




SAP AG 2003

Adjust Untagging

Technicalobject

Operationalcondition

Operationaltype

P1 ON 2

V1 Closed 1

V2 Closed 1

Operational WCD

Technical Object Untagging

condition

Untagging

type

Operational

condition

Operational

type

P1 ON ON 2

V1 Open Closed 1

V2 Closed 1

Technical

Object

Untagging

condition

Untagging

typeP1 ON

V1 Open

V2

You can compare the untagging condition/type with the current operational condition/type.

The following prerequisites apply:

We are dealing with an Operational WCD.

The Operational WCD is either "Prepared" (PREP) or in "Change mode" (CHNG).

The item is not in the temporary untagging phase or untagging phase.

The system knows the current operational condition/type for the item.




SAP AG 2001

Perform lockout/tagout

You are now able to

Lockout/Tagout: Summary




Exercises

Unit: Lockout/Tagout


• Carry out tagging

• Carry out untagging

Before you begin lockout/tagout, we recommend you run a test

for the entire process.

4-1 Tagging

4-1-1 Activate the approval process for your work clearance application and

Operational WCD. How do you do proceed?

______________________________________________________

______________________________________________________

______________________________________________________

______________________________________________________

4-1-2 Perform all necessary tasks so tagging can begin. How do you do proceed?

______________________________________________________

______________________________________________________

______________________________________________________

______________________________________________________

4-1-3 Carry out tagging. How do you do proceed?

______________________________________________________

______________________________________________________

______________________________________________________

______________________________________________________




4-2 Plant Maintenance

4-2-1 Arrange for the maintenance work to be carried out. How do you do proceed?

______________________________________________________

______________________________________________________

______________________________________________________

______________________________________________________

4-2-2 Confirm that maintenance work has been carried out. How do you do proceed?

______________________________________________________

______________________________________________________

______________________________________________________

______________________________________________________

4-3 Untagging

4-3-1 Perform all necessary tasks so untagging can begin. How do you do proceed?

______________________________________________________

______________________________________________________

______________________________________________________

______________________________________________________

4-3-2 Carry out untagging. How do you do proceed?

______________________________________________________

______________________________________________________

______________________________________________________

______________________________________________________

4-3-3 When untagging has been performed, complete your Operational WCD. How

do you do proceed?

______________________________________________________ ______________________________________________________

______________________________________________________

______________________________________________________




Solutions

Unit: Lockout/Tagout

4-1 Tagging

4-1-1 Set status Prepared (PREP) for the work clearance application

... WC application Change (= WCTL)

WC application Functions Prepare Set

(= <Ctrl> + <F1>)

+Set status Prepared (PREP) for the Operational WCD

... Operational WCD Change (= WCT7)

Operational WCD Functions Prepare Set

(= <Ctrl> + <F1>)

4-1-2 Grant approval TECH1 to the work clearance application


Goto Approvals... (= <F7>) Grant approval TECH1

4-1-3 Tag Operational WCD


Goto Switching operation (= <Ctrl> + <Shift> + <F2>) Carry out tagging




4-2 Plant Maintenance

4-2-1 Approving a work clearance application

... WC application Change (= WCTL) Approval TECH2 is granted automatically

Set status Released for execution (EXEC) in order

SAP Menu Logistics Plant Maintenance Maintenance Processing


<Released for execution> (= <Ctrl> + <Shift> + <F10>)

4-2-2 Setting status Work complete (WOCO) in the order



<Work complete> (= <Ctrl> + <Shift> + <F11>)

4-3 Untagging

4-3-1 Set status Complete (CLSD) for the work clearance application

... WC application Change (= WCTL) <Yes>

4-3-2 Untag Operational WCD... Operational WCD Change (= WCT7)

Goto Switching operation (= <Ctrl> + <Shift> + <F2>)

Carry out untagging

4-3-3 Set status Complete (CLSD) for the Operational WCD

Operational WCD Functions Complete (= <Ctrl> + <F2>)




SAP AG 2001

Activating WCM

Example

Contents

Order Processing




SAP AG 2001

Activate WCM

Use WCM


Order Processing: Unit Objectives




SAP AG 2001

Order Processing: Overview

Further functions

Customizing

W C M

Course Overview

Introduction

WCM Objects

Approvals

Lockout/Tagout

Order processing




SAP AG 2003

Activating WCM

Example

Contents:

Activating WCM




SAP AG 2003

WCM and the Maintenance Process

Work Clearance

Management

Work Clearance

Management

Work Clearance

Management

Work Clearance

Management


order

Create

order Release

order

Release

order Confirm

order

Confirm

order Complete

order

Complete

order


Plan

order

Plan

order

SCADASCADA


Orders are linked to WCM at order header level.

For WCM-relevant orders you cannot perform the maintenance tasks until you have released them

(status "Released for Execution" (EXEC)). Setting the tasks to "released" depends on the WCM

architecture and whether the valuation was activated.

Connecting orders to WCM is not absolutely necessary. Work clearance management enables you to

carry out safety measures without an order. For example, this is the case if every change within the

asset should or must be documented but the order is not needed for planning or to collect costs.




SAP AG 2003

Activating WCM

Work Clearance

Management

Work Clearance

Management

Work Clearance

Management

Work Clearance

Management


order

Create

order Release

order

Release

order Confirm

order

Confirm

order Complete

order

Complete

order


Plan

order

Plan

order

SCADASCADA


You must activate WCM for orders to ensure that safety measures are performed for maintenance tasks.

These orders are marked as WCM-relevant orders.

There are two options for activating WCM:

Through approvals, which you assign to the maintenance order and have configured in Customizing

such that WCM is activated

Through operations in maintenance orders with the control key WCM

A partially completed valuation prohibits you from withdrawing the activation.




SAP AG 2003

Valuation

Order

1001

Order

1001

Valuation

Lockout/tagout Yes

Radiation protection Yes

Fire protection Yes

Hazardous materials No

....

Operational

WCD

4001

Operational

WCD

4001

WAP

2001

WAP2001

Operational

WCD

4002

Operational

WCD

4002

WCA

3001

WCA

3001

......

You can activate the valuation for WCM-relevant orders so that the maintenance employees can decide

themselves whether safety measures are required.

For the valuation you must define explicitly for each application whether or not it is required.

When the valuation is activated and the applications are determined, each WCM-relevant order must be

valuated, that is, when you are processing an order you must specify for each application whether or not

it is required.

As soon as at least one application is valuated, the order immediately becomes relevant for WCM.

For the valuation, the system checks if you are authorized to valuate the application. It also documents

who makes the valuation at what time.

You can change a valuation until it is "put in process" (status "Released for execution" (EXEC)). The

valuation is based on the order being put in process, that is, applications marked with yes are requiredurgently.

As soon as you have valuated all the applications, the system sets the "Valuated" (VAL) status in the

order.




SAP AG 2003

Dependencies: Standard Model

Orders

EXEC WOCO TECOWCM

PREP CLSD

PREP CLSDUNT EUGETG

Operational WCDs


WOCO Work complete

CLSD WCM object is "completed"

EXEC The order is "released for execution", that is, work can begin

WCM WCM is active

ETG The Operational WCD is "tagged"

EUG The Operational WCD is "untagged"

UNT The Operational WCD is "untaggable"

TECO The order is "technically complete"

PREP The WCM object is "prepared"




SAP AG 2003

Activating WCM

Example

Contents:

Example




SAP AG 2001

Example (1/7)

Order Order NotificationNotification

MECH1

WCA

MECH2

Approvals

System status WCM is active for the order

Problem – leaky pump in feed water system

Malfunction report

Shift workers create a damage report.

Order

The maintenance planner creates an order.

Lockout/tagout is required for pump repairs




SAP AG 2001

Example (2/7)

WCAWCA


OperationalWCD

Operational

WCD OperationalWCD

Operational

WCD


The maintenance planner creates a work clearance application.

The traffic light indicator is red.

Operational WCDs

A WCM planner looks for an Operational WCD for the work clearance application.

The WCM planner creates an Operational WCD with reference to a WCD template. The planner then

assigns this to the work clearance application.




SAP AG 2001

Example (3/7)

WCAWCA


OperationalWCD

Operational

WCD OperationalWCD

Operational

WCD


The WCM planner grants approvals in the work clearance application. The traffic light indicator then

turns yellow.




SAP AG 2001

Example (4/7)

Operational WCDs

The shift manager begins tagging for the Operational WCDs.

The shift manager completes tagging for the Operational WCDs.




SAP AG 2001

Example (5/7)

WCAWCA


OperationalWCD

Operational

WCD OperationalWCD

Operational

WCD


The WCM planner grants final approvals in the work clearance application. The traffic light indicator

then turns green.




SAP AG 2003

Example (6/7)

Order

EXEC WOCO

CLSD


Order

The maintenance planner sets the order status "Released for execution" (EXEC).

Repairs were carried out and confirmed to the order

Order

The maintenance planner sets the order status Work is completed (WOCO).


Then WCM planner completes the work clearance application.




SAP AG 2001

Example (7/7)

CLSD

CLSDUNT EUG


Operational WCD

Operational WCDs

The shift manager begins untagging for the Operational WCDs.

The shift manager completes untagging.

The shift manager completes the Operational WCDs.

Order

The maintenance planner sets the order status Technically complete (TECO).

The maintenance planner describes the work that has been carried out.

The order is settled.

The maintenance planner keeps the history.




SAP AG 2001

Activate WCM

Use WCM

You are now able to

Order Processing: Summary







Exercises

Unit: Order Processing


• Use Work Clearance Management

At IDES, Work Clearance Management should be an integral part

of maintenance order processing.


5-1-1 Create a malfunction report for pump set 1.

Planner group: I##

Planning plant: 1000Responsible work center: T-ME##


______________________________________________________

______________________________________________________

______________________________________________________

______________________________________________________

5-1-2 Create an order containing an operation for your malfunction report.

Order type: PM01

Planning plant: 1000Business area: 0001

Responsible work center: T-ME##


______________________________________________________

______________________________________________________

______________________________________________________

______________________________________________________




5-1-3 Set the order to Release (REL) without printing.

Malfunction report: _______________

Order: _______________

5-2 Work clearance application / Operational WCD

5-2-1 Create a work clearance application for your order.

Planning plant: 1000

Responsible work center: T-ME##


______________________________________________________

______________________________________________________

______________________________________________________

______________________________________________________

5-2-2 Use the tagging for pump set 1 to create an Operational WCD for your work

clearance application. How do you do proceed?

______________________________________________________

______________________________________________________

______________________________________________________

______________________________________________________

Operational WCD: _______________

Work clearance application: _______________




5-3 Tagging / Untagging

5-3-1 Carry out all tasks required for maintenance work to begin. How do you do

proceed?

______________________________________________________

______________________________________________________

______________________________________________________

______________________________________________________

5-3-2 When you have confirmed the maintenance work, undertake all steps

necessary for untagging to begin. How do you do proceed?

______________________________________________________

______________________________________________________ ______________________________________________________

______________________________________________________

5-3-3 When untagging has been performed, complete your Operational WCD. Howdo you do proceed?

______________________________________________________

______________________________________________________

______________________________________________________

______________________________________________________

Tagging for pump set 1

M

M

##- B01- 1A ##- B01- 1B

##- B01- 2B ##- B01- 2A

##- B01- 1

##- B01- 2

To To

From From







Solutions

Unit: Order Processing



Objects Functional Location Structural Display (= IH01) Select pump set 1

Goto Create notification Malfunction report

5-1-2 Maintenance notification Order Create Direct

5-1-3 Order Functions Release ... (= <Ctrl> + <F1>)

5-2 Work clearance application / Operational WCD

5-2-1 SAP Menu Logistics Plant Maintenance Maintenance Processing

Order Change (= IW32)<WC application> ( = <Ctrl> + <Shift> + <F9>)

<Copy> (= <F5>)

5-2-2 Goto Links Work clearance document (= <Shift> + <F8>)

<Create> (= <Shift> + <F5>)

5-3 Tagging / Untagging

5-3-1 Set status Prepared (PREP) for the work clearance application


WC application Functions Prepare Set

(= <Ctrl> + <F1>)




+

Set status Prepared (PREP) for the Operational WCD


Operational WCD Functions Prepare Set

(= <Ctrl> + <F1>)

Grant approval TECH1 to the work clearance application


Goto Approvals... (= <F7>) Grant approval TECH1

Tag Operational WCD


Goto Switching operation (= <Ctrl> + <Shift> + <F2>) Carry out tagging

Approve work clearance application... WC application Change (= WCTL) Approval TECH2 is granted automatically

Set status Released for execution (EXEC) in the order



<Released for execution> (= <Ctrl> + <Shift> + <F10>)

5-3-2 Setting status Work complete (WOCO) in the order SAP Menu Logistics Plant Maintenance Maintenance Processing


<Work complete> (= <Ctrl> + <Shift> + <F11>)

Set status Work complete (CLSD) in the work clearance application

... WC application Change (= WCTL) <Yes>

Untag Operational WCD


Goto Switching operation (= <Ctrl> + <Shift> + <F2>) Carry out untagging

5-3-3 Set status Complete (CLSD) for the Operational WCD

Operational WCD Functions Complete (= <Ctrl> + <F2>)




SAP AG 2001

Test cycle

Operational classes

Contents

Further Functions




SAP AG 2001

Carry out test cycles

Use operational classes


Further Functions: Unit Objectives




SAP AG 2001

Further Functions: Overview

Customizing

W C M

Course Overview

Introduction

WCM Objects

Approvals

Lockout/Tagout

Order processing

Further functions




SAP AG 2001

Test cycle

Operational classes

Contents

Test Cycle




SAP AG 2001

Test Cycle

PREP? UNT?

TEST?

Tagging phase Untagging phase

Temporary

untagging phase

Yes

ETUG BTUGPTST

EUGBUGETGPTAG

Yes

Yes

BTG

Test cycle = temporary untagging phase + tagging phase

The test cycle briefly interrupts lockout/tagout

You can place each item in an Operational WCD through a test cycle

You can repeat the test cycle as many times as you want

You can print test tags




SAP AG 2001

Dependencies

PREP CLSD


TENT

PREP CLSDUNT

Operational WCD

TEST

The work clearance application requires a test cycle.

If work clearance applications have the status Test cycle (TENT), you can carry out a test cycle for

Operational WCDs that are assigned to the applications.

If work clearance applications have the status Complete (CLSD), you can carry out untagging for

Operational WCDs that are assigned to the applications.

You may perform a test cycle for an Operational WCD if all work clearance applications assigned have

the status Test cycle (TENT) or Completed (CLSD).

The status Test cycle (TEST) for the Operational WCD is set internally.




SAP AG 2001

Test cycle

Operational classes

Contents

Operational Classes




SAP AG 2001

Operational Classes

Open

Closed

VALVE

OFF

ONPUMP

MOTOR

Logical grouping of

operational conditions based

on the technical

characteristics of technicalobjects

You can assign operational conditions and technical objects with master data to several operational

classes.

Operational groups are not the same as Operational classes.




SAP AG 2001

Grouping Operational Conditions

Pre-assigning operational conditions for the item

Operational group/

operational condition

Technical

object

(with master data)

Closed

OPEN

ON

OFF

M

M

E

E

Operational

classA1

A1-B02

A1-B

A1-B02-9

A1-B02-9-C

A1-B02-9-C-1

...

...

Testing an item's operational condition against the

operational conditions in the operational class

PUMP

VALVE

MOTOR

...

Pre-assigning operational conditions

Prerequisite

The technical object with master data is assigned to an operational class.

Operational conditions were assigned to the operational class.

Maintain items

Technical object with master data Values from operational conditions

The F4 help only displays operational conditions assigned to the technical object.




SAP AG 2001

Carry out test cycles

Use operational classes

You are now able to

Further Functions: Summary




SAP AG 2001

Architecture

Lockout/tagout

Printing

Authorization objects

Roles

Contents

Customizing




SAP AG 2001

Represent business processes

Use Customizing


Customizing: Unit Objectives




SAP AG 2001

Customizing: Overview

Course Overview

Introduction

WCM Objects

Approvals

Lockout/Tagout

Order processing

Further functions

Customizing

W C M




SAP AG 2001

Architecture

Lockout/tagout

Printing


Roles

Contents

Architecture






SAP AG 2001

Architecture

Model selection

Assistant for maintaining additional applications

(enhanced model only) Define the direct processing mode

Define relationships

Order

Work approval

Work clearance

application

Operational WCD

Order

Work clearance

application

Operational WCD

Enhanced model Standard model

Further

applications

You can define, for example;

An Operational WCD can only be changed using the work clearance application assigned

An Operational WCD can only be assigned to a work clearance application

The model and WCM architecture lead to certain restrictions on relationships. You may not change

these under any circumstances. Only a 1:1 relation is permitted for the following relationships:

Standard model

- Order > Work clearance application

Enhanced model

- Order > Work approval

- Work approval > Work clearance application

- Work approval > Application




SAP AG 2001

Architecture

Lockout/tagout

Printing


Roles

Contents

Lockout/Tagout




SAP AG 2003

Operational Cycle

The following features are cross-planning plant:

Operational group

Operational condition

Operational type

The following features are dependent on the planning plant:

Combination of operational group, condition, and type

Conflict rules

The operational cycle may be formed in various different ways:


Test cycle


It is possible to ignore the following statuses:

Starting status

- "Tag" (BTG)

- "Untag temporarily" (BTUG)

- "Untag" (BUG)

Print status

- "Tag printed" (PTAG)

- "Test tag printed" (PTST)




SAP AG 2001

Architecture

Lockout/tagout

Printing


Roles

Contents

Printing




SAP AG 2003

Log outputLog output

Program (print report) Customizing

Printout of shop papers for WCM objects, for example,

work permit, tag

Printout of shop papers for WCM objects, for example,

work permit, tag

How Does Printing Work?

ABAP/4

memory

ABAP/4

memory

Layout

program

SAPscript form

Read and extract

data for WCM objects

In WCM, you can print the following shop papers:

Work permit (The work permit is a printout confirming that measures or activities are to be

performed in WCM. You can print a work permit for each WCM object.)

Operational lists (An operational list is the printout of an operational WCD. This printout contains

the information required on site and supports the execution of a lockout/tagout.)

Tags and test tags (A tag or test tag is the printout of an item of an operational WCD. This printout

is affixed to a technical object on site and indicates that the technical object was switched.)




SAP AG 2003

Print Guidelines

Print type

Print format

Short text

Technical parameters

Program

Form (SAPscript)

Work permit

Output control

Indicator: Show dialog box for print

parameters

Number of printouts

Indicator: Print immediately

Indicator: Delete after printout

Indicator: New spool order

Spool time

Archive mode

The system distinguishes between general and user-specific print guidelines.

Short text, technical parameter, and work permit cannot be changed by the user.

Print type

Header data (1)

Operational list for tagging (2) and/or untagging (3)

Tag (4) and/or Test tag (5)

Work permit (6)




SAP AG 2001

Architecture

Lockout/tagout

Printing


Roles

Contents

Authorization Objects




SAP AG 2001

Authorization Objects: Introduction

An authorization object consists one or more fields.

The content of all fields is checked against the authorizationprofile.

You differentiate, for example, between

One dimensional authorization objects

I_TCODE: Transaction code

Only the transaction code is checked

Two dimensional authorization objects

I_SWERK: Transaction code and location

The combination of both fields is checked




SAP AG 2003

Maintenance Authorization Objects

S_TCODE: Transaction code

(TCODE): For all transactions

I_BEGRP: Authorization group

(TCODE, BEGRP): For WCM objects

I_INGRP: Maintenance planner group

(TCODE, IWERK, INGRP): For WCM objects

I_IWERK: Maintenance planning plant

(TCODE, IWERK): For WCM objects

I_SWERK: Location

(TCODE, SWERK): For WCM objects

I_SOGEN: Approval

(SWERK, PMSOG): For WCM objects




SAP AG 2003

WCM Authorization Objects (1/3)

I_VAL: Valuation

(IWERK, VAL): for orders

IWERK: Maintenance planning plant

Val: Valuation

I_CONFLICT: Checks and Simulations

(IWERK, WC_CONFTYP): For Operational WCDs

IWERK: Maintenance planning plant

WC_CONFTYP: Conflict type

Test cycle (B) Check: Test Cycle

Untagging (C) Check: Untagging

Conflict (D) Check: Conflict




SAP AG 2001


I_WCUSE: Use of WCM objects

(IWERK, OBJART, OBJTYP, WCUSE, AKTTYP):

For WCM objects

IWERK: Planning plant

OBJART + OBJTYP: WCM object

WCUSE: Use of WCM object

AKTTYP: Transaction type (create, change, display)




SAP AG 2003


I_FCODE: Function code

(IWERK, OBJART, OBJTYP, WC_FCODE):

For WCM objects

IWERK: Planning plant

OBJART + OBJTYP: WCM object

WC_FCODE: Function code

Header level

- Prepared (PREP) and Change mode (CHNG)

- Completed (CLSD) and Rejected (REJC)

- Work permit (PRI0)

Item level

- Object deactivated (INAC)

- Operational cycle (BTG, PTAG,...., EUG)




SAP AG 2003

WCM Profile

I_WCM_ALL:

All WCM authorizations

I_VAL_ALL:

All authorizations for the valuation

I_CONF_ALL:

All authorizations for checks and simulations

I_FCODE_ALL:

All authorizations for the function codes

I_WCM_ALL:

All authorizations for the usages

I_PM_ALL:

All maintenance authorizations for Plant

Maintenance




SAP AG 2001

Architecture

Lockout/tagout

Printing


Roles

Contents

Authorization Objects




SAP AG 2003

Roles in Plant Maintenance

Maintenance planner

Nicole Potter

Maintenance supervisor

Scott Weiland

Technician

Kate Stevens

Maintenance engineer

Harry Meyers

Maintenance manager

James Taylor

Work clearance planner

Martin Miller

You can access the plant maintenance transactions in the general SAP menu, or through a role-specific

menu designed around the duties of a specific employee.

The following five sample roles for Plant Maintenance are available in the standard system:

Maintenance plannerDeals with and monitors malfunctions and requirements, plans and monitors

maintenance orders. Different people may assume the role of maintenance planner, depending on the

organization (for example, centralized or decentralized planning).

Maintenance supervisorResponsible for a workshop/maintenance group and for the processing of

maintenance orders in this area.

Maintenance technicianCarries out maintenance orders.

Maintenance engineerResponsible for the mapping and preventive maintenance of technical systems.

Maintenance managerResponsible for the overall maintenance process, prepares budgets, andmonitors cost/damage trends.

Work clearance planner (safety engineer)In WCM (currently only used in power plants), is

responsible for ensuring that conditions are safe before maintenance work proceeds in a dangerous

environment.




SAP AG 2003

Role Functions

SAP user

Harry Meyers

Maintenance engineer

Process equipment

...

Create equipment

Change equipment

Change list editing

Composite role

Single role

Single role

User menu for Harry Meyers

Leave request

Process equipment

...

Employee Role

Leave request

Single role

Composite role

Each of the composite roles contains a group of transactions required for the function in an individual

menu.

Each composite role is composed of a number of single roles. Each single role is composed of a group

of thematically-related transactions that are compiled into single roles in the menu. The authorizations

for the individual transactions can also be stored in the single roles.

One or more composite roles are assigned to an SAP user. The composite roles assigned to a user form

the user menu.

Example: Harry Meyers works as a maintenance engineer at IDES AG. His role as employee means

that he needs to access general functions, for example, creating a leave request. In his role as

maintenance engineer he manges technical objects in Plant Maintenance. The composite roles Employee

and Maintenance engineer are assigned to his SAP user profile and his user menu is then available.




SAP AG 2001

Single Roles for WCM

Work Clearance Requester

Work Clearance Planner

Safety Engineer

Information Functions for

WCM

Three individual roles are available for WCM.

Note: other roles in plant maintenance are available as composite roles - there are no composite roles

for WCM. You must either create these separately or combine available single roles with an existing

composite role.




SAP AG 2001

Work Clearance Requester

Technical name: SAP_PM_WOC_WCM_REQUESTER

Activities

This role includes all functions that an employee making a work

clearance application requires.

Plant Maintenance activities

The following activities are available with this role:• Creating work approvals

• Creating work clearance applications

• Multi level list display




SAP AG 2001

Work Clearance Planner

Technical name: SAP_PM_WOC_WCM_PLANNER

Activities

This role includes all functions that a WCM planner requires.


The following activities are available with this role:• Processing/displaying Operational WCDs

• Displaying work approvals

• Displaying work clearance applications





SAP AG 2001

Safety Engineer

Technical name: SAP_PM_WOC_WCM_ENGINEER

Activities

This role includes all functions that a safety engineer requires.


The following activities are available with this role:• Processing/displaying work approvals

• Processing/displaying work clearance applications





SAP AG 2001

Information Functions for WCM

Technical name: SAP_PM_WOC_WCM_INFO

Activities

This role includes all WCM information functions.


The following activities are available with this role:• Displaying work approvals

• Displaying applications

• Displaying Operational WCDs


• Operational log




SAP AG 2001

Represent business processes

Use Customizing

You are now able to

Customizing: Summary



© SAP AG PLM320 Appendix-1

SAP AG 2001

Appendix

Customizing paths

Contents







Customizing Paths

Access to Customizing:

SAP Menu Tools Customizing IMG Edit Project

Button SAP Reference IMG

WCM Objects

Field name or data type Path

Model selection Plant Maintenance and Customer Service

Work Clearance Management Master Data Architecture Assistant for Model

Selection

Maintaining number ranges Plant Maintenance and Customer Service

Work Clearance Management Master Data

Number Ranges Maintain Number

Ranges for ...

Assigning number ranges Plant Maintenance and Customer Service


Number Ranges Assign Number Ranges

Maintaining usage and assigning default values Plant Maintenance and Customer ServiceWork Clearance Management Master Data

Uses Maintain Usage for ....

Plant Maintenance and Customer Service

Work Clearance Management Operational

Cycle Usage for Work Clearance Documents

Assigning user status profiles Plant Maintenance and Customer Service


User Status Assign User Status Profiles

Generating fields for data transfer Plant Maintenance and Customer Service

Work Clearance Management Master Data Data Transfer When Creating with Template

Determine Basic Settings

Generating basic print settings Plant Maintenance and Customer Service


Print Control Generate Basic Print

Settings




Approvals


Defining permit categories Plant Maintenance and Customer Service

Basic Settings Permits Define

Permit Categories

Maintaining approvals Plant Maintenance and Customer Service

Work Clearance Management

Approvals Standard Maintain

Approvals

Assigning approvals Plant Maintenance and Customer Service

Work Clearance Management Approvals

Enhancements Assign Approval

Defining approval hierarchies Plant Maintenance and Customer Service


Enhancements Define Approval Hierarchy

Activating WCM for maintenance orders Plant Maintenance and Customer Service


Work Clearance Management for Maintenance

Orders Define Permits

Lockout/Tagout


Maintaining operational groups Plant Maintenance and Customer Service


Cycle Tagging and Untagging Conditions

Maintain Operational GroupsDefining operational conditions Plant Maintenance and Customer Service



Define Operational Conditions

Maintaining operational types Plant Maintenance and Customer Service



Maintain Operational Types

Assigning data for tagging/untagging Plant Maintenance and Customer Service

Work Clearance Management OperationalCycle Tagging and Untagging Conditions

Maintain Operational Conditions

Assigning default values for operational tags Plant Maintenance and Customer Service



Define Print Format for Tags and Test Tags




SAP AG 1999

Customizing paths

Contents:

Appendix







Customizing Paths: Task Lists and Maintenance

Planning

To access Customizing:

SAP Menu Tools Customizing IMG Edit Project

Select SAP Reference IMG

Task lists

Field Name or Data Type Path

Define task list usage Plant Maintenance and Customer Service

Maintenance Plans, Work Centers, Task Lists

and PRTs Task Lists General Data

Define Task List Usage

Profile Plant Maintenance and Customer Service


and PRTs Task Lists Control Data

Define Profiles with Default Values

Free material assignment Plant Maintenance and Customer Service


and PRTs Task Lists Control Data

Define Presetting for Free Assignment of

Material

Control key Plant Maintenance and Customer Service

Maintenance Plans, Work Centers, Task Listsand PRTs Task Lists Operation Data

Maintain Control Keys

User fields Plant Maintenance and Customer Service


and PRTs Task Lists Operation Data

Define User Fields

Edit list Plant Maintenance and Customer Service


and PRTs Task Lists Set List Editing for

Task Lists

Preset list display Plant Maintenance and Customer Service Maintenance Plans, Work Centers, Task Lists

and PRTs Task Lists Presetting for List

Display of Multi-Level Task Lists



Maintenance plans

Field Name or Data Type PathMaintenance plan categories Plant Maintenance and Customer Service


and PRTs Maintenance Plans Set

Maintenance Plan Categories Completion data Plant Maintenance and Customer Service

Maintenance Plans, Work Centers, Task Listsand PRTs Maintenance Plans Set

Maintenance Plan Categories

Number ranges Plant Maintenance and Customer Service


and PRTs Maintenance Plans Define

Number Ranges for Maintenance Plans

Sort fields Plant Maintenance and Customer Service


and PRTs Maintenance Plans Define Sort

Fields for Maintenance Plan

Field selection Plant Maintenance and Customer Service Maintenance Plans, Work Centers, Task Lists

and PRTs Maintenance Plans Define