PLM - Work Clearance Mgmt_NoRestriction

8/9/2019 PLM - Work Clearance Mgmt_NoRestriction

1/24


2/24

© SAP AG 2

SAP AG 2002

mySAP Product Lifecycle Management

Life-Cycle Data

ManagementDocument Management

Product Structure

ManagementIntegration

Change & Configuration

Management

Asset Life-Cycle

Management

Technical AssetsManagement

Preventive Maintenance Work Clearance Management Work Order Cycle

Program & Project

ManagementStrategic Program Management Life-Cycle Profitability Analysis Project Management

Life-Cycle

Collaboration

Design

Collaboration

Collaborative

ProjectManagement

Quality

Collaboration

MRO Supplier

Collaboration

Enterprise Portal

ContentPLM Analytics

Quality Management Audit Management Quality Control Quality Improvement

Environment, Health

& Safety

Product Safety /

Hazardous Substance

Management

Dangerous Goods

Management

Industrial Hygiene &

SafetyWaste Management Occupational Health

PLM Solution Map, Edition 2002


3/24

© SAP AG 3

SAP AG 2002

Work Clearance Management

Enhancements for continuous WCM process improvement:

Valuation of applications Improved incorporation of turnarounds/outage planning

Optimization of the creation of a library of WCD templates

Integration with a graphical lockout/tag-out system


4/24

© SAP AG 4

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 2002

General Round-Offs

Optimized revision planning

Preprinting of tags

Continual process improvements

Link to the generic object services

Reporting

Customizing

Documentation of safety type

Ergonomic improvements


5/24

© SAP AG 5

SAP AG 2002

Usability: Enhanced List Editing


6/24

© SAP AG 6

SAP AG 2002

Usability: Single Hit


7/24

© SAP AG 7

SAP AG 2002

Usability: ABAP List Viewer


8/24

© SAP AG 8

SAP AG 2002

Technical Objects from Several Planning Plants

Technical objects from other planning plants can be integrated inan item of a work clearance document.

The rules from the planning plant in the work clearancedocument header are used for the processing of the WCDs.

Item 10: TechObj AItem 10: TechObj A

Item 20: TechObj BItem 20: TechObj B

Item 30: TechObj C Item 30: TechObj C

Item 50: TechObj EItem 50: TechObj E

Item 40: TechObj DItem 40: TechObj D

1000

2000

1000

1000

1000

2000

2000

WCD Header Pl.Plant 1000WCD Header Pl.Plant 1000


9/24

© SAP AG 9

In Customizing, you can define that work clearance documents may contain technical objects from several

planning plants by setting the shown indicator.

SAP AG 2002

Technical Objects from Several Planning Plants(Customizing)


10/24

© SAP AG 10

SAP AG 2002

Customizing: Groups/Grouping


11/24

© SAP AG 11

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 2002

Customizing: Groups/GroupingCustomizing: Groups/Grouping – 1


12/24

© SAP AG 12

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 2002

Customizing: Groups/GroupingCustomizing: Groups/Grouping – 2


13/24

© SAP AG 13

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

SAP AG 2002

Example: Creation Using Templates Forbidden


14/24

© SAP AG 14

SAP AG 2002

Customizing: Functional Enhancements


15/24


16/24

© SAP AG 16

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

Examples for physical blocking types are:

Bolts

Chains

Locks

SAP AG 2002

Customizing: Define Physical Blocking Types


17/24

© SAP AG 17

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 2002

Evaluation of Safety Measures

Order 1001

Order 1001

Valuation

Lockout/tagout Yes

Fire protection NoRadiation protection Yes

....

Op. WCD

4001

Op. WCD

4001

WorkApp

2001

WorkApp2001

Op. WCD

4002

Op. WCD

4002

WCA3001

WCA

3001......

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.


18/24

© SAP AG 18

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 thestandard 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 2002

Example: Valuation


20/24

© SAP AG 20

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 2002

Optimized Construction of a Library of Work ClearanceDocuments

Template identification

List comparison

Navigation support

Extended reporting

Current: Template:


22/24

© SAP AG 22

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 2002

Integration with a Graphical WCM Planning System

Export of data for

visualization of the

work clearance

documents

Import of changes in the configuration phase:

- Changing of items

- Adding of items

- Deletion of items

WCD

Graphic WCM

Planning System


23/24


24/24

SAP AG 2002

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 ofMicrosoft Corporation.

IBM ® , DB2 ® , OS/2 ® , DB2/6000®, Parallel Sysplex ® , MVS/ESA ® , RS/6000®, AIX®, S/390 ® , AS/400 ® , OS/390 ® , and

OS/400 ® are registered trademarks of IBM Corporation.

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.

Copyright 2002 SAP AG. All rights reserved