PLM320 Work Clearance Management

PLM320 Work Clearance Management

PLM320

Work Clearance Management

THE BEST-RUN BUSINESSES RUN SAP SAP AG 2003  SAP AG©2003

System R/3 – Enterprise 2003/Q2 Materialnummer: 50061236

© SAP AG

PLM320

Preface-1

Copyright

Copyright 2003 SAP AG. All rights reserved. No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG. The information contained herein may be changed without prior notice. All rights reserved.

 SAP AG 2003

Trademarks: Some software products marketed by SAP AG and its distributors contain proprietary software components of other software vendors. Microsoft®, WINDOWS®, NT®, EXCEL®, Word®, PowerPoint® and SQL Server® are registered trademarks of Microsoft Corporation. IBM®, DB2®, DB2 Universal Database, OS/2®, Parallel Sysplex®, MVS/ESA, AIX®, S/390®, AS/400®, OS/390®, OS/400®, iSeries, pSeries, xSeries, zSeries, z/OS, AFP, Intelligent Miner, WebSphere®, Netfinity®, Tivoli®, Informix and Informix® Dynamic ServerTM are trademarks of IBM Corporation in USA and/or other countries. ORACLE® is a registered trademark of ORACLE Corporation. UNIX®, X/Open®, OSF/1®, and Motif® are registered trademarks of the Open Group. Citrix®, the Citrix logo, ICA®, Program Neighborhood®, MetaFrame®, WinFrame®, VideoFrame®, MultiWin® and other Citrix product names referenced herein are trademarks of Citrix Systems, Inc. HTML, DHTML, XML, XHTML are trademarks or registered trademarks of W3C®, World Wide Web Consortium, Massachusetts Institute of Technology. JAVA® is a registered trademark of Sun Microsystems, Inc. JAVASCRIPT® is a registered trademark of Sun Microsystems, Inc., used under license for technology invented and implemented by Netscape. MarketSet and Enterprise Buyer are jointly owned trademarks of SAP AG and Commerce One. SAP, SAP Logo, R/2, R/3, mySAP, mySAP.com, and other SAP products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP AG in Germany and in several other countries all over the world. All other product and service names mentioned are the trademarks of their respective companies. © SAP AG

PLM320

Preface-2

mySAP PLM (ALM Plant Maintenance) PLM305 SAP01

3 days

mySAP.com Overview

SAPPLM

2 days

mySAP PLM Solution Overview

PLM300

5 days

Plant Maintenance

3 days

PLM310

*PLM130

3 days

3 days

Preventive Maintenance and Service

Classification

PLM315

**CA500

PLM316

* See also SCM Curriculum **See also HR Curriculum

3 days

Document Management System

3 days

Maintenance Processing: Operational Functions

ALM = Asset Life-Cycle Management

PLM120

Structuring and Managing Technical Objects

2 days

Cross Application Time Sheet

3 days

Maintenance Processing: Controlling and Reporting Functions

PLM320

3 days

WCM Work Clearance Management

 SAP AG 2003

© SAP AG

PLM320

Preface-3

Course Prerequisites

LO100/PLM300 Plant Maintenance (Level 2)

 SAP AG 2003

© SAP AG

PLM320

Preface-4

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 2003

© SAP AG

PLM320

Preface-5

Course Overview

Contents Course objectives Course content Course overview diagram Main business scenario

 SAP AG 2001

© SAP AG

PLM320

1-1

Course Objectives

At the conclusion of this course, you will be able to Describe the WCM functions Maintain WCM master data Process WCM transactions Configure WCM

 SAP AG 2001

© SAP AG

PLM320

1-2

Course Content

Preface Unit 1

Course overview

Unit 5

Lockout / tagout

Unit 2

Introduction

Unit 6

Order processing

Unit 3

WCM objects

Unit 7

Further functions

Unit 4

Approvals

Unit 8

Customizing

Appendix

 SAP AG 2001

© SAP AG

PLM320

1-3

Course Overview - Overview Diagram

Customizing Further functions Order processing Lockout/Tagout

M C W

Approvals WCM Objects

Course Overview Introduction

 SAP AG 2001

WCM = Work Clearance Management

© SAP AG

PLM320

1-4

Main Business Scenario

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

 SAP AG 2001

© SAP AG

PLM320

1-5

Introduction

Contents General characteristics Asset management Maintenance process

 SAP AG 2001

© SAP AG

PLM320

2-1

Introduction: Objectives

At the conclusion of this unit, you will be able to Integrate WCM with your maintenance process Describe the various structuring options

 SAP AG 2001

© SAP AG

PLM320

2-2

Introduction - Overview Diagram

Customizing Further functions Order processing Lockout/Tagout

M C W

Approvals WCM Objects

Course Overview Introduction

 SAP AG 2001

© SAP AG

PLM320

2-3

General Characteristics

Contents General characteristics Asset management Maintenance process

 SAP AG 2001

© SAP AG

PLM320

2-4

Need for WCM

Maintenance crews are working in a hazardous environment (for example, high voltage, radiation exposure) 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

 SAP AG 2001

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

PLM320

2-5

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

© SAP AG

PLM320

2-6

Asset Management

Contents General characteristics Asset management Maintenance process

 SAP AG 2001

© SAP AG

PLM320

2-7

Basic Elements

Object links Ref. locations Equipment

Functional locations

BOMs

Classification Equipment Func. locs.

Assembly

Spare parts

 SAP AG 2001

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

PLM320

2-8

Structuring of Technical Assets

Func. location Func. location

Func. Func.location location hierarchy hierarchy

Installed Installed Equipment Equipment

Equipment

Equipment Equipment hierarchy hierarchy

Equipment

Equipment Equipment BOMs BOMs Assembly Spare parts

Assembly Assembly BOMs BOMs

 SAP AG 2001

© SAP AG

PLM320

2-9

Structural Display Object Object links links

Documents Documents General General task task lists lists

Measurement Measurement points points

Task Task lists lists

BOMs BOMs

Maintenance Maintenance items items

Material Material stock stock

Scheduling Scheduling overview overview

Multi Multi layer layer list list

Notifications Notifications

Display Create

Objects Objects

Orders Orders

Notifications Notifications

Work Work orders orders

Display Create

 SAP AG 2001

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

PLM320

2-10

Structure Indicator

Edit mask Hierarchy levels

Functional location key

AN-ANN-N-X-X 1 2 3 4 56

A1 A1-B A1-B02 A1-B02- 9 A1-B02- 9-C A1-B02- 9-C- 1

A = Alpha N = Numerical X = Alphanumerical

Plant System Sub-system Function Sub-function Item

 SAP AG 2001

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

PLM320

2-11

Structuring - Example FL

70 70

FL

70 70

FL

70 70

Block 7 LAB10

Feed water supply system Main slide valve

LAB10 LAB10- -AA005 AA005

EQ

Slide valve with drive

1000 1255

EQ

1000 1387

Slide valve DN200

EQ

1000 1389

Variable speed drive

AB

200 154

MT MT AB

Motor

50000379 50000379 50000483 50000483 200 432

Brushes ... Control

FL = Functional location

EQ = Equipment

AB = Assembly

MT = Material

 SAP AG 2001

© SAP AG

PLM320

2-12

Maintenance Process

Contents General characteristics Asset management Maintenance process

 SAP AG 2001

© SAP AG

PLM320

2-13

WCM and the Maintenance Process

Work WorkClearance Clearance Management Management

Maintenance Maintenanceplan plan

Notification Notification

SCADA SCADA

Create Create order order

Plan Plan order order

Release Release order order

Work WorkClearance Clearance Management Management

Confirm Confirm order order

Complete Complete order order

History/analysis History/analysis

 SAP AG 2003

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

PLM320

2-14

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 previous course) You must be able to use the functional location structuring and maintenance processing functions in IDES. This is a prerequisite for 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? ______________________________________________________ ______________________________________________________ ______________________________________________________ ______________________________________________________

© SAP AG

PLM320

2-15

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: PM01 Planning 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:

© SAP AG

_______________

PLM320

2-16

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 ( = ) Extras → Permits ( = + ) Permit assigned: WCM

1-2

Notification / Order 1-2-1 SAP Menu → Logistics → Plant Maintenance → Management of Technical 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 ... (= + )

© SAP AG

PLM320

2-17

WCM Objects

Contents Overview Work approval Applications Work clearance application Additional applications

Work Clearance Documents WCD template Operational WCD

 SAP AG 2001

© SAP AG

PLM320

3-1

WCM Objects: Unit Objectives

At the conclusion of this unit, you will be able to Describe the different WCM objects Explain the differences between WCM objects Create WCM objects

 SAP AG 2001

© SAP AG

PLM320

3-2

WCM Objects - Overview

Customizing Further functions Order processing Lockout/Tagout

M C W

Approvals WCM Objects

Course Overview Introduction

 SAP AG 2001

© SAP AG

PLM320

3-3

Overview

Contents Overview Work approval Applications Work clearance application Additional applications

Work Clearance Documents WCD template Operational WCD

 SAP AG 2001

© SAP AG

PLM320

3-4

Architecture

Order Work Approval Work clearance application

Order

Further applications

Operational WCD

Work Clearance Application Operational WCD

Enhanced model

Standard model

 SAP AG 2003

You can choose between the standard and enhanced model to represent your WCM architecture. The standard model includes the following WCM objects: Work clearance application Operational WCD The enhanced model includes the following additional WCM objects: Work Approval Further applications The decision which model to use is made at individual company level for each planning plant.

© SAP AG

PLM320

3-5

Enhanced Model: Example Order Order 1001 1001

Order Order 1002 1002

Order Order 1003 1003

WAP WAP 2001 2001

WCA WCA 3001 3001

Operational Operational WCD WCD 4001 4001

Operational Operational WCD WCD 4002 4002

Order Order 1004 1004

WAP WAP 2002 2002

WCA WCA 3002 3002

......

Operational Operational WCD WCD 4003 4003

Operational Operational WCD WCD 4004 4004

Operational Operational WCD WCD 4005 4005

 SAP AG 2001

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

PLM320

3-6

Standard Model: Example Order Order 1001 1001

Order Order 1002 1002

Order Order 1003 1003

WCA WCA 3001 3001

Operational Operational WCD WCD 4001 4001

Operational Operational WCD WCD 4002 4002

Order Order 1004 1004

WCA WCA 3002 3002

Operational Operational WCD WCD 4003 4003

Operational Operational WCD WCD 4004 4004

Operational Operational WCD WCD 4005 4005

 SAP AG 2001

The standard model is useful if the main goal is to support lockout/tagout in the system, and other safety measures play a less important role.

© SAP AG

PLM320

3-7

Communication

Order Order

Work WorkApproval Approval

Applications Applications

Plant Maintenance

Plant Maintenance Production

Plant Maintenance

Work clearance application

Production

Applications for Radiation protection

Work WorkClearance Clearance Documents Documents

Fire protection

Production

Operational WCD WCD template

 SAP AG 2003

Integration between Work Clearance Management and the maintenance process requires good communication between plant maintenance and other departments.

© SAP AG

PLM320

3-8

Creation with Reference

Order Order

Work WorkApproval Approval

Filter Filterfor fordata datacopy copy (Customizing) (Customizing)

WCM object

Applications Applications

Work WorkClearance Clearance Documents Documents

 SAP AG 2003

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

PLM320

3-9

Work Approval

Contents Overview Work approval Applications Work clearance application Additional applications

Work Clearance Documents WCD template Operational WCD

 SAP AG 2001

© SAP AG

PLM320

3-10

Work Approval

Only used in the enhanced model

Order

WCM object for control and communication between orders and applications

Work Approval Work clearance application

Further applications

Umbrella WCM object for orders and applications

Operational WCD

Enhanced model

 SAP AG 2003

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 technical system 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

PLM320

3-11

Work Approvals: Data Generic object services: different services are possible Status processing and audit trail: system status and user status

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

 SAP AG 2003

Assignment of technical objects: equipment and functional locations

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. Areas of responsibility 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

PLM320

3-12

Work Approval: Status Sequence (1/2) Orders

Work approval

Applications

CRTE

CRTE

PREP

PREP

EXEC

PWP

PWP

WOCO

CLSD

CLSD

 SAP AG 2003

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

© SAP AG

PLM320

3-13

Work Approval: Status Sequence (2/2) (1)

(4)

CRTE CRTE PREP PREP

INAC INAC INAC INAC

REJC REJC

DLFL DLFL

REJC REJC

DLFL DLFL

CLSD CLSD

REJC REJC

(2)

PREP PREP CHNG CHNG

PWP PWP

CLSD CLSD

INAC INAC

REJC REJC

(5)

DLFL DLFL

(3)

CHNG CHNG PREP PREP

INAC INAC

REJC REJC

 SAP AG 2003

(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 "Deletion Flag" (DLFL). In some cases, there may be additional prerequisites for the individual statuses!

© SAP AG

PLM320

3-14

Work Approval: Links

Order Order 1001 1001

Order Order 1002 1002

Order Order 1003 1003

Order Order 1005 1005

Order Order 1006 1006

WAP WAP 2002 2002

WAP WAP 2003 2003

(R3)

WAP WAP 2001 2001

(R5)

WCA WCA 3001 3001

WCA WCA 3002 3002

WCA WCA 4002 4002

WCA WCA 3003 3003

 SAP AG 2001

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

PLM320

3-15

Work clearance application

Contents: Overview Work approval Applications Work clearance application Additional applications

Work Clearance Documents WCD template Operational WCD

 SAP AG 2003

© SAP AG

PLM320

3-16

Work clearance application Enhanced model

Order

WCM object for control and communication between work approvals and Operational WCDs

Work Approval WC application Operational WCD

Further applications

Umbrella document for work approvals and Operational WCDs

Enhanced model

Standard model WCM object for control and communication between orders and Operational WCDs

Order WC application

Umbrella document for orders and Operational WCDs

Operational WCD

Standard model

 SAP AG 2003

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

PLM320

3-17

Work Clearance Application: Data Generic object services: different services are possible Status processing and audit trail: system status and user status

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

 SAP AG 2003

Assignment of technical objects: equipment and functional locations

General data Short text, use of application, validity period, priority, recall time, general status, overall condition, revision phase Reference object Either functional location or equipment and section. Areas of responsibility 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

PLM320

3-18

Work Clearance Application: Status Sequence (1/2) Orders or work approvals

WC application

Operational WCDs

CRTE PREP PWP TENT ?

CLSD

UNT TEST

 SAP AG 2003

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

PLM320

3-19

Work Clearance Application: Status Sequence (2/2) (1)

(4)

CRTE CRTE PREP PREP

INAC INAC INAC INAC

REJC REJC

DLFL DLFL

REJC REJC

DLFL DLFL

CLSD CLSD

REJC REJC

(2)

PREP PREP CHNG CHNG

PWP PWP

CLSD CLSD

INAC INAC

REJC REJC

TENT TENT

(5)

DLFL DLFL

(3)

CHNG CHNG PREP PREP

INAC INAC

REJC REJC

 SAP AG 2003

(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 "Deletion Flag" (DLFL). In some cases, there may be additional prerequisites for the individual statuses!

© SAP AG

PLM320

3-20

Work Clearance Application: Links WAP WAP 2001 2001

Order Order 1001 1001

WAP WAP 2002 2002

Order Order 1002 1002 (R1)

WCA WCA 3001 3001

Operational Operational WCD WCD 4001 4001

Operational Operational WCD WCD 4002 4002

Operational Operational WCD WCD 4003 4003

Enhanced model

WCA WCA 3001 3001

WCA WCA 3002 3002

Operational Operational WCD WCD 4001 4001

Operational Operational WCD WCD 4002 4002

Standard model

 SAP AG 2001

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). (Assignment rule R2) 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). (Assignment rule R2)

© SAP AG

PLM320

3-21

Additional applications

Contents: Overview Work approval Applications Work clearance application Additional applications

Work Clearance Documents WCD template Operational WCD

 SAP AG 2003

© SAP AG

PLM320

3-22

Additional applications

Order Work Approval Work clearance application

?

Operational WCD

Enhanced model

 SAP AG 2003

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

PLM320

3-23

Work Clearance Documents

Contents Overview Work approval Applications Work clearance application Additional applications

Work Clearance Documents WCD template Operational WCD

 SAP AG 2001

© SAP AG

PLM320

3-24

Work Clearance Document

 SAP AG 2003

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

PLM320

3-25

Work Clearance Document: Structure

WCD template

Header Header

Template library

Item Item

Cannot be used to perform lockout/tagout

Operational WCD Can be assigned to work clearance applications

Item Item

Can be used to perform lockout/tagout

Item Item

... ...  SAP AG 2003

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

PLM320

3-26

Work Clearance Document (Header): Data Generic object services: different services are possible Status processing and audit trail: system status and user status

General data Reference object Areas of responsibility

Assignment of partners: different roles possible Long text processing: several internal remarks

Location data

Assignment of documents: link to document management system

Planning data

Assignment of permits: cross-document, interactive Use of catalog technique: catalog groups and codes

 SAP AG 2003

Assignment of technical objects: equipment and functional locations

General data Short text, use of WCD, validity period, priority, recall time, general status, overall condition, revision phase Reference object Either functional location or equipment and section. Areas of responsibility 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

PLM320

3-27

Work Clearance Document (Item): Data

Item category Technical object or short text

Status processing and audit trail: system status and user status

Operational group Data for the tagging

Long text processing: several internal remarks

Data for the untagging Additional data

Assignment of documents: link to document management system

General data

 SAP AG 2003

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

PLM320

3-28

Operational WCD: System Sequence CRTE CRTE PREP PREP

Header

Item

ITG ITG PROC PROC

CONF CONF

CONF CONF

BTG BTG

ETUG ETUG

PTAG PTAG

PTST PTST

ETG ETG

TEST TEST

ITG ITG

BTUG BTUG

UNT UNT

BTG BTG

ETUG ETUG

PTAG PTAG

PTST PTST

ETG ETG

BTUG BTUG

BUG BUG

BUG BUG

EUG EUG

EUG EUG CLSD CLSD  SAP AG 2003

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

PLM320

3-29

Operational WCD: Links

WCA WCA 3001 3001

Operational Operational WCD WCD 4001 4001

WCA WCA 3002 3002

Operational Operational WCD WCD 4002 4002

Operational Operational WCD WCD 4003 4003

 SAP AG 2001

Observe the following assignment rule: A work clearance application may be assigned to several Operational WCDs, and vice versa (assignment rule R2).

© SAP AG

PLM320

3-30

Data flow

Graphic planning List comparison

Any Work Clearance Document

Current Work Clearance Document

Clipboard

Other Work Clearance Documents

 SAP AG 2003

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

PLM320

3-31

WCM Objects: Summary

You are now able to Describe the different WCM objects Explain the differences between WCM objects Create WCM objects

 SAP AG 2001

© SAP AG

PLM320

3-32

Exercises Unit: WCM Objects

At the conclusion of this unit, you will be able to: • 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 changed should 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:

© SAP AG

PLM320

_______________

3-33

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: 1000 Responsible 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

© SAP AG

PLM320

3-34

Solutions Unit: WCM Objects

2-1

Work clearance application 2-1-1 SAP Menu → Logistics → Plant Maintenance → Maintenance Processing → Order → Change (= IW32) (= + + ) (= )

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 (= + ) (= + )

© SAP AG

PLM320

3-35

Approvals

Contents Overview Approval process across WCM objects

 SAP AG 2001

© SAP AG

PLM320

4-1

Approvals: Unit Objectives

At the conclusion of this unit, you will be able to Explain the term Approvals Differentiate between approvals and work approvals Use approvals

 SAP AG 2001

© SAP AG

PLM320

4-2

Approvals: Overview

Customizing Further functions Order processing Lockout/Tagout

M C W

Approvals WCM Objects

Course Overview Introduction

 SAP AG 2001

© SAP AG

PLM320

4-3

Overview

Contents Overview Approval process across WCM objects

 SAP AG 2001

© SAP AG

PLM320

4-4

Overview

Operational WCD

WAP

...

Order

WCA

 SAP AG 2001

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

PLM320

4-5

Basic Functions

Before starting the approval process Assignment to a WCM object Deleting the assignment

During the approval process Granting approval Withdrawing approval

 SAP AG 2003

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 a WCM 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

PLM320

4-6

Additional Functions (1/3) Hierarchy level support

1

AA

BB

CC

DD

3

FF

EE

2

4

GG Approval

Hierarchy level

 SAP AG 2001

All approvals at a particular hierarchy level must be granted. Within a hierarchy level, there is no fixed order for granting approvals

© SAP AG

PLM320

4-7

Additional Functions (2/3)

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

 SAP AG 2003

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

PLM320

4-8

Additional Functions (3/3)

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

 SAP AG 2001

Missing approval -- Approval granted

© SAP AG

PLM320

4-9

Why can an Approval not be Granted?

A superior approval has not been granted

AA BB CC DD

Required assignments are not in place

The required system or user status is not active

Dependent approvals from assigned WCM objects have not been granted

 SAP AG 2003

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

PLM320

4-10

Approval Process Across WCM Objects

Contents Overview Approval process across WCM objects

 SAP AG 2001

© SAP AG

PLM320

4-11

Approval Process Across WCM Objects

Indicator: process relevant

Approval

Work approval

A

y Approval category Direction

Work clearance application

B

Operational WCD

y

C

y

 SAP AG 2001

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

PLM320

4-12

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

C

X

D

y

A B

B

X

E

y

C D E

A

X

F

y

F

 SAP AG 2001

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

PLM320

4-13

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

A1

?

B

X

E

y

F1

?

A1

A2

B

C D A2

?

C

X

D

y

F2

?

E

F1

F2

 SAP AG 2001

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

PLM320

4-14

Approvals: Summary

You are now able to Explain the term Approvals Differentiate between approvals and work approvals Use approvals

 SAP AG 2001

© SAP AG

PLM320

4-15

© SAP AG

PLM320

4-16

Exercises Unit: Approvals

At the conclusion of this unit, you will be able to: • 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? ____________________________________________________________ ____________________________________________________________

© SAP AG

PLM320

4-17

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? ____________________________________________________________ ____________________________________________________________

© SAP AG

PLM320

4-18

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 been granted 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

PLM320

4-19

Lockout/Tagout

Contents Operational cycle Checks Conflict rules

Simulations Operational protection and protected areas Adjust untagging

 SAP AG 2001

© SAP AG

PLM320

5-1

Lockout/Tagout: Unit Objectives

At the conclusion of this unit, you will be able to Perform lockout/tagout

 SAP AG 2001

© SAP AG

PLM320

5-2

Lockout/Tagout: Overview

Customizing Further functions Order processing Lockout/Tagout

M C W

Approvals WCM Objects

Course Overview Introduction

 SAP AG 2001

© SAP AG

PLM320

5-3

Overview

Contents: Overview Operational Cycle Checks Conflict Rules

Simulations Operational Protection ? Protected Areas Adjust Untagging

 SAP AG 2003

© SAP AG

PLM320

5-4

Lockout/Tagout

Order Work Approval Work clearance application

Order

Further applications

Operational WCD

WC application Operational WCD

Enhanced model

Standard model

 SAP AG 2003

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

PLM320

5-5

Operational Cycle

Contents Overview Operational Cycle Checks Conflict Rules

Simulations Operational Protection

Protected Areas

Adjust Untagging

 SAP AG 2003

© SAP AG

PLM320

5-6

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

Open

Closed  SAP AG 2001

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

PLM320

5-7

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

 SAP AG 2003

Operational types help you to further define same operational conditions. The choice of conflict rules influences the use of the operational type.

© SAP AG

PLM320

5-8

Operational Groups

ON

Electrical

OFF

Open

Mechanical

Logical grouping of operational conditions to minimize conflict rules Where conflict rules apply

Closed

 SAP AG 2001

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

PLM320

5-9

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

 SAP AG 2003

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

PLM320

5-10

Operational Cycle Tagging cycle with temporary untagging phase Tagging Taggingphase phase

Temporary Temporary untagging untaggingphase phase

Untagging Untaggingphase phase

Test cycle Tagging Taggingphase phase

Temporary Temporary untagging untaggingphase phase

Tagging cycle without temporary untagging phase Tagging Taggingphase phase

Untagging Untaggingphase phase

 SAP AG 2003

The operational cycle is a cycle consisting a maximum of three operational phases. The operational cycle may be formed in various different ways: Tagging cycle with temporary untagging phase Test cycle Tagging cycle without temporary untagging phase 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

PLM320

5-11

Operational Cycle: Example Standard operational cycle

Reduced operational cycle

ITG ITG

ITG ITG

Initial status (ITG) Tagging phase Tag (BTG)

BTG BTG

ETUG ETUG

Tag printed (PTAG) Tagged (ETG)

PTAG PTAG

PTST PTST

PTAG PTAG

ETG ETG

BTUG BTUG

ETG ETG

Temporary untagging phase Untag temporarily (BTUG) Test tag printed (PTST) Temporarily untagged (ETUG)

BUG BUG Untagging phase

EUG EUG

EUG EUG

Untag (BUG) Untagged (EUG)

 SAP AG 2003

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

PLM320

5-12

Operational WCD: System Sequence CRTE CRTE PREP PREP

Header

Item

ITG ITG PROC PROC

CONF CONF

CONF CONF

BTG BTG

ETUG ETUG

PTAG PTAG

PTST PTST

ETG ETG

TEST TEST

ITG ITG

BTUG BTUG

UNT UNT

BTG BTG

ETUG ETUG

PTAG PTAG

PTST PTST

ETG ETG

BTUG BTUG

BUG BUG

BUG BUG

EUG EUG

EUG EUG

POST POST

CLSD CLSD

PROT PROT

 SAP AG 2001

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

PLM320

5-13

Checks

Contents. Overview Operational Cycle Checks Conflict Rules

Simulations Operational Protection

Protected Areas

Adjust Untagging

 SAP AG 2003

© SAP AG

PLM320

5-14

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

 SAP AG 2001

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

PLM320

5-15

Further Checks: Overview

Tagging phase BTG

PTAG

Temporary untagging phase ETG

BTUG

PTST

ETUG

Untagging phase BUG

EUG

Reference object Time frame Completeness and correctness Test Cycle Untagging Conflict

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)

 SAP AG 2001

© SAP AG

PLM320

5-16

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.

 SAP AG 2003

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

PLM320

5-17

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.

 SAP AG 2003

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 an operational group not yet confirmed in the system. You cannot ignore the check. You can alter or deactivate the check.

© SAP AG

PLM320

5-18

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.

 SAP AG 2003

Compulsory check If the required untagging condition/type has been maintained for a technical object. At the latest, you must maintain this by the time of (temporary) untagging. You cannot ignore the check.

© SAP AG

PLM320

5-19

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.

 SAP AG 2003

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

PLM320

5-20

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.

 SAP AG 2003

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

PLM320

5-21

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.

 SAP AG 2003

Compulsory check If required operational conditions/types for a technical object can be switched within an operational group. 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 conflict is automatically withdrawn.

© SAP AG

PLM320

5-22

Conflict Rules

Contents: Overview Operational Cycle Checks Conflict Rules

Simulations Operational protection

Protected areas

Adjust Untagging

 SAP AG 2003

© SAP AG

PLM320

5-23

Conflict Rules

General conflict rules

User-defined conflict rules

 SAP AG 2001

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

PLM320

5-24

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

E

Error message (Different)

=

(Same)

Consequences The operational type cannot be overwritten Operational conditions have no impact on the conflict check You cannot define asymmetric conflict rules

 SAP AG 2001

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

PLM320

5-25

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

 SAP AG 2003

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

PLM320

5-26

Simulations

Contents: Overview Operational Cycle Checks Conflict Rules

Simulations Operational Protection

Protected Areas

Adjust Untagging

 SAP AG 2003

© SAP AG

PLM320

5-27

Simulations

What would happen if ...?

 SAP AG 2001

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

PLM320

5-28

Operational Protection

Protected Areas

Contents: Overview Operational Cycle Checks Conflict Rules

Simulations Operational Protection

Protected Areas

Adjust Untagging

 SAP AG 2003

© SAP AG

PLM320

5-29

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.

 SAP AG 2003

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

PLM320

5-30

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.

 SAP AG 2003

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

PLM320

5-31

Protected Areas: Example (1/2)

WCA WCA 3001 3001

(1)

Operational Operational WCD WCD 4001 4001

WCA WCA 3002 3002

Operational Operational WCD WCD 4002 4002

Operational Operational WCD WCD 4003 4003

Operational Protection

(2)

Operational Operational WCD WCD 4004 4004

Protected area

WCA WCA 3001 3001

Operational Operational WCD WCD 4001 4001

WCA WCA 3002 3002

Operational Operational WCD WCD 4002 4002

Operational Operational WCD WCD 4003 4003

Operational Operational WCD WCD 4004 4004

 SAP AG 2003

(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. (2) An operational protection is set for an item of operational WCD 4002. Because of the assigned work clearance application 3001 and 3002, the operational WCDs 4001, 4002, and 4003 form the protected area.

© SAP AG

PLM320

5-32

Protected Areas: Example (2/2)

(3)

WCA WCA 3001 3001

Operational Operational WCD WCD 4001 4001

(4)

Operational Operational WCD WCD 4002 4002

WCA WCA 3001 3001

Operational Operational WCD WCD 4001 4001

WCA WCA 3002 3002

Operational Operational WCD WCD 4003 4003

Operational Operational WCD WCD 4004 4004

WCA WCA 3002 3002

Operational Operational WCD WCD 4002 4002

Operational Operational WCD WCD 4003 4003

Operational Operational WCD WCD 4004 4004

 SAP AG 2003

(3) An operational protection is set for an item of operational WCD 4003. Because of the assigned work 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

PLM320

5-33

Adjust Untagging

Contents: Overview Operational Cycle Checks Conflict Rules

Simulations Operational Protection

Protected Areas

Adjust Untagging

 SAP AG 2003

© SAP AG

PLM320

5-34

Adjust Untagging Operational WCD Technical Object

Untagging condition

P1 V1 V2

ON Open

Untagging type

P1 V1 V2

Technical Object Untagging Untagging condition type P1 V1 V2

Technical Operational Operational object condition type

ON Open

ON Closed Closed

Operational condition

Operational type

ON Closed Closed

2 1 1

2 1 1

 SAP AG 2003

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

PLM320

5-35

Lockout/Tagout: Summary

You are now able to Perform lockout/tagout

 SAP AG 2001

© SAP AG

PLM320

5-36

Exercises Unit: Lockout/Tagout

At the conclusion of this unit, you will be able to: • 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? ______________________________________________________ ______________________________________________________ ______________________________________________________ ______________________________________________________

© SAP AG

PLM320

5-37

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? ______________________________________________________ ______________________________________________________ ______________________________________________________ ______________________________________________________

© SAP AG

PLM320

5-38

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 (= + ) + Set status Prepared (PREP) for the Operational WCD ... → Operational WCD → Change (= WCT7) Operational WCD → Functions → Prepare → Set (= + ) 4-1-2 Grant approval TECH1 to the work clearance application ... → WC application → Change (= WCTL) Goto → Approvals... (= ) Grant approval TECH1 4-1-3 Tag Operational WCD ... → Operational WCD → Change (= WCT7) Goto → Switching operation (= + + ) Carry out tagging

© SAP AG

PLM320

5-39

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 → Order → Change (= IW32) (= + + ) 4-2-2 Setting status Work complete (WOCO) in the order SAP Menu → Logistics → Plant Maintenance → Maintenance Processing → Order → Change (= IW32) (= + + )

4-3

Untagging 4-3-1 Set status Complete (CLSD) for the work clearance application ... → WC application → Change (= WCTL) 4-3-2 Untag Operational WCD ... → Operational WCD → Change (= WCT7) Goto → Switching operation (= + + ) Carry out untagging 4-3-3 Set status Complete (CLSD) for the Operational WCD Operational WCD → Functions → Complete (= + )

© SAP AG

PLM320

5-40

Order Processing

Contents Activating WCM Example

 SAP AG 2001

© SAP AG

PLM320

6-1

Order Processing: Unit Objectives

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

 SAP AG 2001

© SAP AG

PLM320

6-2

Order Processing: Overview

Customizing Further functions Order processing Lockout/Tagout

M C W

Approvals WCM Objects

Course Overview Introduction

 SAP AG 2001

© SAP AG

PLM320

6-3

Activating WCM

Contents: Activating WCM Example

 SAP AG 2003

© SAP AG

PLM320

6-4

WCM and the Maintenance Process

Work WorkClearance Clearance Management Management

Maintenance Maintenanceplan plan

Notification Notification

SCADA SCADA

Create Create order order

Plan Plan order order

Release Release order order

Work WorkClearance Clearance Management Management

Confirm Confirm order order

Complete Complete order order

History/analysis History/analysis

 SAP AG 2003

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

PLM320

6-5

Activating WCM

Work WorkClearance Clearance Management Management

Maintenance Maintenanceplan plan

Notification Notification

SCADA SCADA

Create Create order order

Plan Plan order order

Release Release order order

Confirm Confirm order order

Work WorkClearance Clearance Management Management

Complete Complete order order

History/analysis History/analysis

 SAP AG 2003

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

PLM320

6-6

Valuation

Order Order 1001 1001

Valuation Lockout/tagout Radiation protection Fire protection Hazardous materials ....

WAP WAP 2001 2001

Yes Yes Yes No

WCA WCA 3001 3001

......

Operational Operational Operational Operational WCD WCD WCD WCD 4001 4002 4002 4001

 SAP AG 2003

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 required urgently. As soon as you have valuated all the applications, the system sets the "Valuated" (VAL) status in the order.

© SAP AG

PLM320

6-7

Dependencies: Standard Model Orders WCM

EXEC

WOCO

TECO

Work clearance application PREP

CLSD

Operational WCDs PREP

ETG

UNT

EUG

CLSD

 SAP AG 2003

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

PLM320

6-8

Example

Contents: Activating WCM Example

 SAP AG 2003

© SAP AG

PLM320

6-9

Example (1/7)

Notification Notification

Order Order

Approvals

WCA MECH1 MECH2

System status WCM is active for the order

 SAP AG 2001

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

PLM320

6-10

Example (2/7)

Notification Notification

Order Order

WCA WCA

Operational Operational WCD WCD

Operational Operational WCD WCD

 SAP AG 2001

Work clearance application 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

PLM320

6-11

Example (3/7)

Notification Notification

Order Order

WCA WCA

Operational Operational WCD WCD

Operational Operational WCD WCD

 SAP AG 2001

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

© SAP AG

PLM320

6-12

Example (4/7)

 SAP AG 2001

Operational WCDs The shift manager begins tagging for the Operational WCDs. The shift manager completes tagging for the Operational WCDs.

© SAP AG

PLM320

6-13

Example (5/7)

Notification Notification

Order Order

WCA WCA

Operational Operational WCD WCD

Operational Operational WCD WCD

 SAP AG 2001

Work clearance application The WCM planner grants final approvals in the work clearance application. The traffic light indicator then turns green.

© SAP AG

PLM320

6-14

Example (6/7)

Order EXEC

WOCO

Work clearance application CLSD

 SAP AG 2003

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). Work clearance application Then WCM planner completes the work clearance application.

© SAP AG

PLM320

6-15

Example (7/7)

Work clearance application CLSD

Operational WCD UNT

EUG

CLSD

 SAP AG 2001

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

PLM320

6-16

Order Processing: Summary

You are now able to Activate WCM Use WCM

 SAP AG 2001

© SAP AG

PLM320

6-17

© SAP AG

PLM320

6-18

Exercises Unit: Order Processing

At the conclusion of this unit, you will be able to: • Use Work Clearance Management

At IDES, Work Clearance Management should be an integral part of maintenance order processing.

5-1

Notification / Order 5-1-1 Create a malfunction report for pump set 1. Planner group: I## Planning plant: 1000 Responsible work center: T-ME## How do you do proceed? ______________________________________________________ ______________________________________________________ ______________________________________________________ ______________________________________________________ 5-1-2 Create an order containing an operation for your malfunction report. Order type: PM01 Planning plant: 1000 Business area: 0001 Responsible work center: T-ME## How do you do proceed? ______________________________________________________ ______________________________________________________ ______________________________________________________ ______________________________________________________

© SAP AG

PLM320

6-19

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## How do you do proceed? ______________________________________________________ ______________________________________________________ ______________________________________________________ ______________________________________________________ 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: _______________

© SAP AG

PLM320

6-20

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. How do you do proceed? ______________________________________________________ ______________________________________________________ ______________________________________________________ ______________________________________________________ Tagging for pump set 1 M

To

To

##- B01- 1A

##- B01- 1B ##- B01- 1 M

From

##- B01- 2A

© SAP AG

From

##- B01- 2

PLM320

##- B01- 2B

6-21

© SAP AG

PLM320

6-22

Solutions Unit: Order Processing

5-1

Notification / Order 5-1-1 SAP Menu → Logistics → Plant Maintenance → Management of Technical 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 ... (= + )

5-2

Work clearance application / Operational WCD 5-2-1 SAP Menu → Logistics → Plant Maintenance → Maintenance Processing → Order → Change (= IW32) ( = + + ) (= ) 5-2-2 Goto → Links → Work clearance document (= + ) (= + )

5-3

Tagging / Untagging 5-3-1 Set status Prepared (PREP) for the work clearance application ... → WC application → Change (= WCTL) WC application → Functions → Prepare → Set (= + )

© SAP AG

PLM320

6-23

+ Set status Prepared (PREP) for the Operational WCD ... → Operational WCD → Change (= WCT7) Operational WCD → Functions → Prepare → Set (= + ) Grant approval TECH1 to the work clearance application ... → WC application → Change (= WCTL) Goto → Approvals... (= ) Grant approval TECH1 Tag Operational WCD ... → Operational WCD → Change (= WCT7) Goto → Switching operation (= + + ) 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 SAP Menu → Logistics → Plant Maintenance → Maintenance Processing → Order → Change (= IW32) (= + + )

5-3-2 Setting status Work complete (WOCO) in the order SAP Menu → Logistics → Plant Maintenance → Maintenance Processing → Order → Change (= IW32) (= + + ) Set status Work complete (CLSD) in the work clearance application ... → WC application → Change (= WCTL) Untag Operational WCD ... → Operational WCD → Change (= WCT7) Goto → Switching operation (= + + ) Carry out untagging

5-3-3 Set status Complete (CLSD) for the Operational WCD Operational WCD → Functions → Complete (= + )

© SAP AG

PLM320

6-24

Further Functions

Contents Test cycle Operational classes

 SAP AG 2001

© SAP AG

PLM320

7-1

Further Functions: Unit Objectives

At the conclusion of this unit, you will be able to Carry out test cycles Use operational classes

 SAP AG 2001

© SAP AG

PLM320

7-2

Further Functions: Overview

Customizing Further functions Order processing Lockout/Tagout

M C W

Approvals WCM Objects

Course Overview Introduction

 SAP AG 2001

© SAP AG

PLM320

7-3

Test Cycle

Contents Test cycle Operational classes

 SAP AG 2001

© SAP AG

PLM320

7-4

Test Cycle

PREP?

Yes

Tagging phase

BTG

PTAG

UNT?

Yes

Untagging phase

BUG

ETG

EUG

TEST?

Yes

Temporary untagging phase

ETUG

PTST

BTUG

 SAP AG 2001

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

PLM320

7-5

Dependencies

Work clearance application PREP

CLSD

TENT

Operational WCD PREP

TEST

UNT

CLSD

 SAP AG 2001

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

PLM320

7-6

Operational Classes

Contents Test cycle Operational classes

 SAP AG 2001

© SAP AG

PLM320

7-7

Operational Classes Logical grouping of operational conditions based on the technical characteristics of technical objects

Open

VALVE

Closed

PUMP

ON

OFF

MOTOR

 SAP AG 2001

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

PLM320

7-8

Grouping Operational Conditions Operational group/ operational condition M

OPEN

M

Closed

E

ON

E

OFF

Operational class

Technical object (with master data)

PUMP VALVE MOTOR ...

... A1 A1-B A1-B02 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 Pre-assigning operational conditions for the item

 SAP AG 2001

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

PLM320

7-9

Further Functions: Summary

You are now able to Carry out test cycles Use operational classes

 SAP AG 2001

© SAP AG

PLM320

7-10

Customizing

Contents Architecture Lockout/tagout Printing Authorization objects Roles

 SAP AG 2001

© SAP AG

PLM320

8-1

Customizing: Unit Objectives

At the conclusion of this unit, you will be able to Represent business processes Use Customizing

 SAP AG 2001

© SAP AG

PLM320

8-2

Customizing: Overview

Customizing Further functions Order processing Lockout/Tagout

M C W

Approvals WCM Objects

Course Overview Introduction

 SAP AG 2001

© SAP AG

PLM320

8-3

Architecture

Contents Architecture Lockout/tagout Printing Authorization objects Roles

 SAP AG 2001

© SAP AG

PLM320

8-4

Flexible Settings Nearly all settings are dependent on the planning plant WCM architecture Operational cycle settings Approvals

You can adapt the functions to fit, for example, the functional requirements of different power plants Hydro electric plant Nuclear plant ...

 SAP AG 2003

There are two basic models for the architecture – standard and enhanced. You can choose a model for each planning plant. In this way you define which WCM objects you want to use for the WCM process.

© SAP AG

PLM320

8-5

Architecture Model selection Order Work approval Work clearance application

Order Work clearance application

Further applications

Operational WCD

Operational WCD

Enhanced model

Standard model

Assistant for maintaining additional applications (enhanced model only) Define the direct processing mode Define relationships  SAP AG 2001

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

PLM320

8-6

Lockout/Tagout

Contents Architecture Lockout/tagout Printing Authorization objects Roles

 SAP AG 2001

© SAP AG

PLM320

8-7

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

 SAP AG 2003

The operational cycle may be formed in various different ways: Tagging cycle with temporary untagging phase Test cycle Tagging cycle without temporary untagging phase 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

PLM320

8-8

Printing

Contents Architecture Lockout/tagout Printing Authorization objects Roles

 SAP AG 2001

© SAP AG

PLM320

8-9

How Does Printing Work?

Program (print report)

Read and extract data for WCM objects

Customizing

ABAP/4 ABAP/4 memory memory

Layout program SAPscript form

Printout Printout of of shop shop papers papers for for WCM WCM objects, objects, for for example, example, work work permit, permit, tag tag Log Log output output

 SAP AG 2003

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

PLM320

8-10

Print Guidelines

Print type

Output control Indicator: Show dialog box for print parameters

Print format Short text

Number of printouts

Technical parameters

Indicator: Print immediately

Program

Indicator: Delete after printout

Form (SAPscript)

Indicator: New spool order

Work permit

Spool time Archive mode

 SAP AG 2003

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

PLM320

8-11

Authorization Objects

Contents Architecture Lockout/tagout Printing Authorization objects Roles

 SAP AG 2001

© SAP AG

PLM320

8-12

Authorization Objects: Introduction

An authorization object consists one or more fields. The content of all fields is checked against the authorization profile. 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 2001

© SAP AG

PLM320

8-13

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

© SAP AG

PLM320

8-14

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 2003

© SAP AG

PLM320

8-15

WCM Authorization Objects (2/3)

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 2001

© SAP AG

PLM320

8-16

WCM Authorization Objects (3/3)

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

© SAP AG

PLM320

8-17

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 2003

© SAP AG

PLM320

8-18

Authorization Objects

Contents Architecture Lockout/tagout Printing Authorization objects Roles

 SAP AG 2001

© SAP AG

PLM320

8-19

Roles in Plant Maintenance

Maintenance planner Nicole Potter

Maintenance manager James Taylor

Maintenance supervisor Scott Weiland

Maintenance engineer Harry Meyers

Technician Kate Stevens

Work clearance planner Martin Miller

 SAP AG 2003

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, and monitors 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

PLM320

8-20

Role Functions

Employee Role Leave request

Maintenance engineer Process equipment

Composite role

SAP user Harry Meyers

Single role

Composite role

Single role

Create equipment Change equipment

User menu for Harry Meyers

Change list editing ...

Leave request

Single role

Process equipment ...

 SAP AG 2003

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

PLM320

8-21

Single Roles for WCM

Work Clearance Requester Work Clearance Planner Safety Engineer Information Functions for WCM

 SAP AG 2001

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

PLM320

8-22

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

© SAP AG

PLM320

8-23

Work Clearance Planner Technical name: SAP_PM_WOC_WCM_PLANNER Activities This role includes all functions that a WCM planner requires. Plant Maintenance activities The following activities are available with this role:

• • • •

Processing/displaying Operational WCDs Displaying work approvals Displaying work clearance applications Multi level list display

 SAP AG 2001

© SAP AG

PLM320

8-24

Safety Engineer Technical name: SAP_PM_WOC_WCM_ENGINEER Activities This role includes all functions that a safety engineer requires. Plant Maintenance activities The following activities are available with this role:

• Processing/displaying work approvals • Processing/displaying work clearance applications • Multi level list display

 SAP AG 2001

© SAP AG

PLM320

8-25

Information Functions for WCM Technical name: SAP_PM_WOC_WCM_INFO Activities This role includes all WCM information functions. Plant Maintenance activities The following activities are available with this role:

• • • • •

Displaying work approvals Displaying applications Displaying Operational WCDs Multi level list display Operational log

 SAP AG 2001

© SAP AG

PLM320

8-26

Customizing: Summary

You are now able to Represent business processes Use Customizing

 SAP AG 2001

© SAP AG

PLM320

8-27

Appendix

Contents z Customizing paths

 SAP AG 2001

© SAP AG

PLM320

Appendix-1

© SAP AG

PLM320

Appendix-2

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 → Work Clearance Management → Master Data → Number Ranges → Assign Number Ranges

Maintaining usage and assigning default values

Plant Maintenance and Customer Service → Work 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 → Work Clearance Management → Master Data → 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 → Work Clearance Management → Master Data → Print Control → Generate Basic Print Settings

© SAP AG

PLM320

Appendix-3

Approvals Field name or data type

Path

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 → Work Clearance Management → Approvals → Enhancements → Define Approval Hierarchy

Activating WCM for maintenance orders

Plant Maintenance and Customer Service → Work Clearance Management → Approvals → Work Clearance Management for Maintenance Orders → Define Permits

Lockout/Tagout Field name or data type

Path

Maintaining operational groups

Plant Maintenance and Customer Service → Work Clearance Management → Operational Cycle → Tagging and Untagging Conditions → Maintain Operational Groups

Defining operational conditions

Plant Maintenance and Customer Service → Work Clearance Management → Operational Cycle → Tagging and Untagging Conditions → Define Operational Conditions

Maintaining operational types

Plant Maintenance and Customer Service → Work Clearance Management → Operational Cycle → Tagging and Untagging Conditions → Maintain Operational Types

Assigning data for tagging/untagging

Plant Maintenance and Customer Service → Work Clearance Management → Operational Cycle → Tagging and Untagging Conditions → Maintain Operational Conditions

Assigning default values for operational tags

Plant Maintenance and Customer Service → Work Clearance Management → Operational Cycle → Tagging and Untagging Conditions → Define Print Format for Tags and Test Tags

© SAP AG

PLM320

Appendix-4

Appendix

Contents: z Customizing paths

 SAP AG 1999

© SAP AG

PLM310

Appendix-1

© SAP AG

PLM310

Appendix-2

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 → Maintenance Plans, Work Centers, Task Lists and PRTs → Task Lists → Control Data → Define Profiles with Default Values

Free material assignment

Plant Maintenance and Customer Service → Maintenance Plans, Work Centers, Task Lists 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 Lists and PRTs → Task Lists → Operation Data → Maintain Control Keys

User fields

Plant Maintenance and Customer Service → Maintenance Plans, Work Centers, Task Lists and PRTs → Task Lists → Operation Data → Define User Fields

Edit list

Plant Maintenance and Customer Service → Maintenance Plans, Work Centers, Task Lists 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

© SAP AG

PLM310

Appendix-3

Maintenance plans Field Name or Data Type

Path

Maintenance plan categories

Plant Maintenance and Customer Service → Maintenance Plans, Work Centers, Task Lists and PRTs → Maintenance Plans → Set Maintenance Plan Categories Plant Maintenance and Customer Service → Maintenance Plans, Work Centers, Task Lists and PRTs → Maintenance Plans → Set Maintenance Plan Categories Plant Maintenance and Customer Service → Maintenance Plans, Work Centers, Task Lists and PRTs → Maintenance Plans → Define Number Ranges for Maintenance Plans Plant Maintenance and Customer Service → Maintenance Plans, Work Centers, Task Lists and PRTs → Maintenance Plans → Define Sort Fields for Maintenance Plan Plant Maintenance and Customer Service → Maintenance Plans, Work Centers, Task Lists and PRTs → Maintenance Plans → Define Field Selection for Maintenance Plan Plant Maintenance and Customer Service → Maintenance Plans, Work Centers, Task Lists and PRTs → Maintenance Plans → Set List Editing for Maintenance Plans Plant Maintenance and Customer Service → Maintenance Plans, Work Centers, Task Lists and PRTs → Maintenance Plans → Set List Editing for Maintenance Plan Overall Overview Plant Maintenance and Customer Service → Maintenance and Service Processing → Maintenance and Service Orders → Functions and Settings for Order Types → Configure Order Types Plant Maintenance and Customer Service → Maintenance and Service Processing → Maintenance and Service Orders → Functions and Settings for Order Types → Assign Inspection Types to Maintenance/Service Order Types Quality Management → Quality Planning → Inspection Planning → General → Define Identifier for Inspection Points Quality Management → Quality Planning → Inspection Planning → Operation → Define Control Keys for Inspection Operations Quality Management → Quality Inspection → Inspection Lot Completion → Define FollowUp Actions

Completion data

Number ranges

Sort fields

Field selection

Edit list

Parameters for graphical maintenance scheduling overview

PM-QM: Order type

PM-QM: Inspection type for order type

PM-QM: Inspection point

PM-QM: Control key

PM-QM: Follow-up actions

© SAP AG

PLM310

Appendix-4