ALM

Work Clearance
Management
GBU PLM

SAP AG

mySAP Product Lifecycle Management

PLM Solution Map, Edition 2002

Life-Cycle Data
Management

Product Structure
Management

Document Management

Asset Life-Cycle
Management

Technical Assets
Management

Program & Project

Management

Strategic Program Management

Life-Cycle
Collaboration
Quality Management
Environment, Health
& Safety

Design
Collaboration

Preventive Maintenance

Collaborative
Project
Management

Audit Management
Product Safety /
Hazardous Substance
Management

Work Clearance Management

Life-Cycle Profitability Analysis

Quality
Collaboration

Dangerous Goods
Management

Change & Configuration

Management

Integration

MRO Supplier
Collaboration

Quality Control
Industrial Hygiene &
Safety

Work Order Cycle

Project Management
Enterprise Portal
Content

PLM Analytics

Quality Improvement

Waste Management

Occupational Health

SAP AG 2002

SAP AG

Work Clearance Management

Enhancements for continuous WCM process improvement:
n Valuation of applications
n Improved incorporation of turnarounds/outage planning
n Optimization of the creation of a library of WCD templates
n Integration with a graphical lockout/tag-out system

SAP AG 2002

SAP AG

General Round-Offs
Optimized revision planning
n Preprinting of tags

Continual process improvements

n
n
n
n
n

Link to the generic object services

Reporting
Customizing
Documentation of safety type
Ergonomic improvements

SAP AG 2002

Preprint of tags (before the tagging cycle)

Links from the WCM objects (work clearance document, application, and work approval) to the generic
object services

Output control for non-critical messages can be configured individually for the conflict verification in
Customizing

Safety type: for example, lock with chain, band, decal information, ...

SAP AG

Usability: Enhanced List Editing

SAP AG 2002

SAP AG

Usability: Single Hit

SAP AG 2002

SAP AG

Usability: ABAP List Viewer

SAP AG 2002

SAP AG

Technical Objects from Several Planning Plants

WCD
WCDHeader
Header

Pl.Plant
Pl.Plant1000
1000

Item
Item10:
10:TechObj
TechObjAA

1000

Item
Item20:
20:TechObj
TechObjBB

1000

Item
Item30:
30:TechObj
TechObjCC

1000

Item
Item40:
40:TechObj
TechObjDD

2000

Item
Item50:
50:TechObj
TechObjEE

2000

1000

2000

Technical objects from other planning plants can be integrated in

an item of a work clearance document.
The rules from the planning plant in the work clearance
document header are used for the processing of the WCDs.
SAP AG 2002

SAP AG

Technical Objects from Several Planning Plants

(Customizing)

SAP AG 2002

In Customizing, you can define that work clearance documents may contain technical objects from several
planning plants by setting the shown indicator.

SAP AG

Customizing: Groups/Grouping

SAP AG 2002

SAP AG

10

Customizing: Groups/Grouping 1

SAP AG 2002

In work clearance management, you can define groups according to

System status: In this activity you define which system statuses should be grouped into one group
Approval status: In this activity you define which approval statuses should be grouped into one group
Additional data: In this activity you define which additional data (for example, partners) should be
grouped into one group

In general, groups are used to support very specialized functions. There are several functions that depend
on the system status and the approval status.

SAP AG

11

Customizing: Groups/Grouping 2

SAP AG 2002

One of the functions that depend on the system status is shown above:
In this IMG activity, depending on the system status, you restrict how a WCM object can be used as a
template.
A work clearance application, which is either inactive or rejected, may not be used as a template.
- 1. You define a group that contains the above system status.
- 2. You assign this group to the work clearance application.

SAP AG

12

Example: Creation Using Templates Forbidden

SAP AG 2002

Here, you can see that the given template cannot be used due to the settings made in Customizing.

SAP AG

13

Customizing: Functional Enhancements

SAP AG 2002

SAP AG

14

Customizing: Parameter for Text Processing

SAP AG 2002

In this IMG activity, you define the parameters for text processing.

Standard settings are:

A log line is incorporated into the long text when the text is changed.
Subsequent changes to an existing long text are not possible.

SAP AG

15

Customizing: Define Physical Blocking Types

SAP AG 2002

In this IMG activity you define which physical blocking types there are.

Examples for physical blocking types are:

Bolts
Chains
Locks

SAP AG

16

Evaluation of Safety Measures

Order
Order
1001
1001

Valuation
Lockout/tagout
Yes
Fire protection
No
Radiation protection Yes
....

WorkApp
WorkApp
2001
2001
WCA
WCA
3001
3001
Op.
Op.WCD
WCD
4001
4001

......

Op.
Op.WCD
WCD
4002
4002

You can valuate which safety measures are required for every
order.
At the level of the work approval, the check is performed against
the valuation concerned.

SAP AG 2002

The valuation of maintenance tasks in relation to safety measures takes place in the maintenance order.
This determines which safety measures are necessary, that is, with an explicit YES or NO. This explicit
valuation comes from the BMI guidelines (KKW) or from the SIM guidelines (FKW).

The valuation of the safety measures is documented with the name of the processor and the date.

Changes to the valuation are possible (including revoking all safety measures).

The valuation is allowed up to the point where the status Released for execution is assigned.

The status Released for execution is only allowed by the program, when all the necessary safety
measures have been valuated.

SAP AG

17

Example: Valuation

SAP AG 2002

In Customizing under Define Valuation you can determine, which work clearance documents you need.

You activate the graphic WCM planning in Customizing under Maintain Application Profile:
There is the option of integrating any external systems for processing work clearance documents. The
most prevalent example is the integration of a graphic planning system which you can use to process items
for work clearance documents. Integrating the two systems is realized through an individual RFC server,
which acts as middleware between SAP R/3 and the external system. The server consists of two
components:
Generic component: This is the statistical server library (WCMRFC.LIB) delivered by SAP. It gives
you RFC functions tailored for work clearance documents which simplify the development of a specific
RFC server. This library encapsulates relevant functions of the RFC server which are included in the
standard RFC library.
Individual component: This is an executable program based on the above server library. You must
develop this program additionally to implement an individual integration with a specific external
system.

SAP AG

18

Customizing: Valuation

SAP AG 2002

SAP AG

19

Optimized Construction of a Library of Work Clearance

Documents
n Template identification
n List comparison
n Navigation support
n Extended reporting

Current:

Template:

SAP AG 2002

Integration of templates within an operational WCD

Create with template The reference to the template remains
=> This enables you to compare the templates with the operational WCDs

Support for the following questions:

Which active lockouts/tagouts exist for a given lockout/tagout?
Are the operational WCDs subsequently changed in relation to their templates?
Which template was the basis for the given lockout/tagout?

SAP AG

20

List Comparison: Settings

You can make

individual settings
for each user!

SAP AG 2002

SAP AG

21

Integration with a Graphical WCM Planning System

WCD

Export of data for

visualization of the
work clearance
documents

Graphic WCM
Planning System

Import of changes in the configuration phase:

- Changing of items
- Adding of items
- Deletion of items

SAP AG 2002

General interface for integration with graphical WCM planning.

WCM is the leading system.

Visualization or maintenance of one of the work clearance documents generated in WCM in a graphical
WCM system.

The coupling between the two systems is supported via an individual RFC server working as middleware
between SAP R/3 WCD processing and any external system managing WCM data. The server consists of
two components:
-

Generic component: static WCM server library.

This library (WCMRFC.LIB) is delivered by SAP, it provides WCD specific RFC functionality for easy
implementation of an individual RFC server.
The library encapsulates relevant RFC server functionality provided by the standard RFC library.

Individual component: executable program.

This program has to be developed additionally (e.g. by a third party) to set up an individual coupling to a
specific external system. It is based on the static WCM library.

SAP AG

22

Interface to Graphical WCM Planning System

SAP R/3
Enterprise
WCM

SAP RFC
Library
RFC+
WCM specific
static Library

Server

Any (graphical)
WCM program

SAP AG 2002

The static WCM server library WCMRFC.LIB delivered by SAP provides generic functionality for easy
implementation of an individual RFC server working as middleware between SAP R/3 (when processing a
WCD document) and any external (graphical) system managing WCM data.

The WCM library encapsulates the standard RFC functionality (provided by the standard RFC library)
that is necessary to implement a specific RFC server in a straightforward way. It contains the following
three hierarchical classes:

The WCM library will be (freely) accessible on an appropriate internet page, e.g. the SAP service market
place.

Further details will be provided in an official OSS consultant note: Its number is 514711.

SAP AG

23

Copyright 2002 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.
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, OS/2, DB2/6000, Parallel Sysplex, MVS/ESA, RS/6000, AIX, S/390, AS/400, OS/390, and
OS/400 are registered trademarks of IBM Corporation.
ORACLE is a registered trademark of ORACLE Corporation.
INFORMIX-OnLine for SAP and Informix Dynamic ServerTM are registered trademarks of Informix Software
Incorporated.
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.
SAP, SAP Logo, R/2, RIVA, R/3, SAP ArchiveLink, SAP Business Workflow, WebFlow, SAP EarlyWatch, BAPI,
SAPPHIRE, Management Cockpit, mySAP.com Logo and mySAP.com are trademarks or registered
trademarks of SAP AG in Germany and in several other countries all over the world. All other products
mentioned are trademarks or registered trademarks of their respective companies.

SAP AG 2002

SAP AG

24