1 Work Clearance Management

Use
A component with which the safety measures during maintenance work at technical objects can
be controlled and monitored.
This process creates a safe environment in which staff can work and perform tests. In addition,
applicable environmental safeguards can be adhered to and the reliability of the assets is
guaranteed.

1.1 Master Data

1.1.1 Maintain Application Profile

Use
Application Profile for WCM is defined at Planning Plant level. In application profile the following
are defined:
 The validity of the WCM objects
o Automatic closing of approvals and applications
 Details of reference object check, conflict, etc.

DBPL Rationale:
For DBPL application profile for plant 2003 has been maintained.

Procedure
Title/Organisational Maintain Application Profile
Area
SPRO> Plant Maintenance and Customer Service> Work Clearance
Menu path
Management>Master Data>Maintain Application Profile

Transaction Code SPRO

For Plant 2003

Result
1.1.2 Assistant for Model Selection
Use
In this IMG activity, you choose the model you want to use for your work clearance
management. You can choose one model for each maintenance planning plant. In this way, you
determine which WCM objects you want to use in work clearance management.

The architecture recognizes two basic models: the standard model and the enhanced model.

Rationale:
Two models are available in WCM, namely, standard and enhanced model.
In case, enhanced model has been selected. Enhanced model gives the additional provision of
maintaining additional application such as hot work permit, height work permit, confined space
permit, etc.

Procedure
Title/Organisational Assistant for Model Selection
Area
SPRO> Plant Maintenance and Customer Service> Work Clearance
Menu path Management>Master Data>Maintain Application
Profile>Architecture>Assistant for Model Selection

Transaction Code SPRO

Result
1.1.3 Define Direct Processing Mode
Use
All the WCM objects can be created and maintained either directly from the transaction code or
during navigation. In this IMG activity, the option of creation and change has been enabled from
the transaction code.

DBPL Rationale:
For DBPL the option of creation and change has been enabled from the transaction code.

Procedure
Title/Organisational Direct Processing Mode
Area
SPRO> Plant Maintenance and Customer Service> Work Clearance
Menu path Management>Master Data>Maintain Application
Profile>Architecture>Direct Processing Mode

Transaction Code SPRO

Result

1.1.4 Define Relations

Use
In this section, you maintain the relations between the WCM objects of work clearance
management. You can define how many WCM objects you want to allow for the individual
relationships.

DBPL Rationale:
WCM objects are created and maintained in relation with another WCM object. It has been
defined here that for any WCM object, corresponding WCM object can be created and
maintained. For e.g.,three WC Application can be created and attached to Work Approval.
Procedure
Title/Organisational Define Relations
Area
SPRO> Plant Maintenance and Customer Service> Work Clearance
Menu path Management>Master Data>Maintain Application
Profile>Architecture>Define Relations

Transaction Code SPRO

Result

1.1.5 Define Processing Mode for Relations

Use
In this IMG activity, you maintain the processing mode for instances when you want to link one
WCM object to another.
You can either, choose and allocate an already existing WCM object or you can create a new
WCM object which you then allocate.
DBPL Rationale:
A WCM object can be created during navigation. It is also possible to choose and attach an
existing WCM object to the structure. Both this options are activated in this IMG activity.
Procedure
Title/Organisational Processing Mode for Relations
Area
SPRO> Plant Maintenance and Customer Service> Work Clearance
Menu path Management>Master Data>Maintain Application
Profile>Architecture>Define Processing Mode for Relations

Transaction Code SPRO

Result

1.1.6 Define Processing mode for Navigation

Use
In this IMG activity, you determine which processing mode to permit when you navigate
between linked WCM objects.
You can navigate to the linked WCM object in either "display" or "change" mode. Display mode
is the default value.
You must activate the change mode to be able to navigate in it.

DBPL Rationale:
It is possible to navigate from one WCM object to another and carry out changes. This option is
activated in this IMG activity for DBPL.
Procedure
Title/Organisational Define processing Mode for Navigation
Area
SPRO> Plant Maintenance and Customer Service> Work Clearance
Menu path Management>Master Data>Maintain Application
Profile>Architecture>Define processing Mode for Navigation

Transaction Code SPRO

Result

1.1.7 Maintain Usage for Work Clearance Documents

Use
In this IMG activity, you define the usage for work clearance documents. Depending on the
usage (for example, lockout/tagout, simulation, or test run), an Operational WCD behaves
differently in the following points:

Options for the operational cycle

The following options exist:
 Tagging cycle with temporary untagging phase
 Test cycle
 Tagging cycle without temporary untagging phase
DBPL Rationale:
Usage of Work Clearance Document is used to differentiate between different WCDs such as
PTW and ROMP. Temporary cycle is activated at this level along with the option of printing tags.

Procedure
Title/Organisational Maintain Usage for Work clearance documents
Area
SPRO> Plant Maintenance and Customer Service> Work Clearance
Menu path Management>Master Data>Maintain Application Profile>Use>Maintain
Usage for Work clearance documents

Transaction Code SPRO

Result
1.1.8 Define Train
Use
In this IMG activity, you maintain the trains for your assets. The trains indicate independent
subsystems of the asset. The allocation of a train to the WCM objects supports revision and
maintenance planning from a technical perspective

DBPL Rationale:
Train is a location within the plant which is responsible for issuing the permits. Trains are
maintained in the master data of the technical objects and are copied automatically into the
WCM objects when they are created.
Procedure
Title/Organisational Define Trains
Area
SPRO> Plant Maintenance and Customer Service> Work Clearance
Menu path
Management>Master Data> General Data>Define Trains

Transaction Code SPRO

Result

1.2 Approvals
Use
Approvals are rule or requirement to be observed in work clearance management. It also serves
to log that this rule or requirement is observed.
You can assign approvals to all WCM objects.
The issuing or revoking of approvals takes place in the approval process.
The approval status visualizes the issuing of approvals.

1.2.1 Define Permit Categories

Use
Permit categories are division of permits into logical groups. Every permit must be assigned to a
permit category.

Examples of permit categories include:

 Work permits
 Safety permits
DBPL Rationale:
Permit category “W” has been created to maintain all WCM relevant permits.

Procedure
Title/Organisational Define Permit Categories
Area
SPRO> Plant Maintenance and Customer Service> Work Clearance
Menu path
Management>Approvals> Standard>Define Permit Categories

Transaction Code SPRO

Result

1.2.2 Maintain Approvals

Use
In this IMG activity, you define the approvals you need for work clearance management.
.

DBPL Rationale:
Approvals or permits relevant for WCM are maintained. The permit category for all these
approvals are “W” (WCM).

Procedure
Title/Organisational Maintain approvals
Area
SPRO> Plant Maintenance and Customer Service> Work Clearance
Menu path
Management>Approvals> Standard>Maintain approvals

Transaction Code SPRO

Result

1.2.3 Assign Approvals

Use
The approvals defined are assigned to the WCM objects. This is necessary for the process of
issuing the permits

Procedure
Title/Organisational Assign approvals
Area
SPRO> Plant Maintenance and Customer Service> Work Clearance
Menu path
Management>Approvals> Enhancements>Assign approvals

Transaction Code SPRO

Result
1.2.4 Define Hierarchy of Approvals
Use
The hierarchy of approvals, assigned to a WCM object, is maintained here. This is the sequence
in which the approvals have to be issued.

It can also be define that approvals issued on the basis of the hierarchy level are automatically
revoked.

Procedure
Title/Organisational Define Hierarchy for approvals
Area
SPRO> Plant Maintenance and Customer Service> Work Clearance
Menu path
Management>Approvals> Enhancements>Define Hierarchy for approvals

Transaction Code SPRO

1.2.5 Define Cross Document Approval Process

Use
In this IMG activity, you establish settings for cross-object maintenance of approvals.

Within an approval category you can establish settings so that an approval cannot be issued for
a certain WCM object unless an approval was also issued for an assigned WCM object. To do
this, you must set approvals as relevant to processing.

The direction of a dependency can be either to a higher-level WCM object, to a lower-level

WCM object, or neutral.

The direction of the dependency indicates whether approvals from higher-level WCM objects
("UP") or permits from lower-level WCM objects ("DN") must be taken into account when an
approval is to be issued.

Procedure
Title/Organisational Define Hierarchy for approvals
Area
SPRO> Plant Maintenance and Customer Service> Work Clearance
Menu path
Management>Approvals> Enhancements>Define Hierarchy for approvals

Transaction Code SPRO

Result

1.2.6 Define Dependent on System Status

Use
Settings are maintained for linking the issue of approvals to the System Status of the WCM object.

DBPL Rationale:
The issue of the approval “Tagged” of a WCD is dependent on the system status “Tagged” of
the Operational WCD.

Procedure
Title/Organisational Define Dependent on System Status
Area
SPRO> Plant Maintenance and Customer Service> Work Clearance
Menu path Management>Approvals> Enhancements>Block Issuing of
Approvals>Define Dependent on System Status

Transaction Code SPRO

Result
1.3 Lockout/Tagout
Use
A process in which technical objects are isolated electrically or separated mechanically from
other parts of a technical system during maintenance work or testing.

The process comprises orderly tagging and subsequent untagging of technical objects.
Lockout/tag out ensures a safe environment for maintenance staff to work in and perform tests.

1.3.1 Maintain Operational Groups

Use
Operational groups are used to categorize different tagging and untagging conditions.
DBPL Rationale:
The grouping has been maintained on the basis of whether the tagging and untagging
conditions are relevant for mechanical or electrical processing.

Procedure
Title/Organisational Maintain Operational Groups
Area
SPRO> Plant Maintenance and Customer Service> Work Clearance
Menu path Management>Lockout/Tag out> Operational cycle>Maintain Operational
Groups

Transaction Code SPRO

Result
1.3.2 Maintain Operational Data
Use
Operational data is the mapping of tagging conditions to their respective untagging conditions.
When creating an Operational WCD, this combination is automatically proposed by the system.
The normalizing condition has to be defined as an untagging condition in a separate line.

Procedure
Title/Organisational Maintain Operational data
Area
SPRO> Plant Maintenance and Customer Service> Work Clearance
Menu path Management>Lockout/Tag out> Operational cycle>Maintain Operational
data

Transaction Code SPRO

Result
1.3.3 Maintain Conflict Rules
Use
In this IMG activity, user-defined Conflict Rules that are used in the Operational Cycles. The
conflict rules are defined in an Operational Group. Within the operational group, for all
combinations of Operational Conditions it is defined whether that particular combination:
 is allowed
 should yield a warning
 Is not allowed.
DBPL Rationale:
Following Conflict Rules have been maintained for DBPL

Procedure
Title/Organisational Maintain conflict rules
Area
SPRO> Plant Maintenance and Customer Service> Work Clearance
Menu path
Management>Lockout/Tag out> Maintain conflict rules

Transaction Code SPRO

Result