EAM-Prev. Maint. Multiple Cntr Plan-SAP

8/17/2019 EAM-Prev. Maint. Multiple Cntr Plan-SAP

1/11

SAP COMMUNITY NETWORK SDN - sdn.sap.com | BPX - bpx.sap.com | BOC - boc.sap.com | UAC - uac.sap.com

© 2011 SAP AG 1

Plant Maintenance-Multiple Counter Planwith Cycle Sets for Performance BasedMaintenance

Appl ies to:

It applies to SAP ECC 6.0 EHP4 and later releases.

Summary

In Plant Maintenance Module, Preventive Maintenance plays a major role, with different types of plans formaintenance planner, to execute them without the human intervention. One of them is Performance basedmaintenance, which is decided on the operated hours of the Asset OR a fixed time interval.

This document guides the consultant through the steps required to manage the process of ‘Multiple CounterPlan’, with cycle sets.

Author : James Prabaharan

Company : TVS Infotech Ltd., Chennai

Created on : 10 October, 2011

Author Bio

James Prabaharan has an experience of 32 years in maintenance, of which 15 years was in AircraftInstrumentation (Indian Air Force), 10 years of Electrical maintenance in various manufacturing industriesand 7 years of SAP implementation in the Plant Maintenance module.

Presently he is working as Lead Consultant at TVS Infotech Ltd., Chennai.


2/11


3/11

Plant Maintenance-Multiple Counter Plan with Cycle Sets for Performance Based Maintenance


© 2011 SAP AG 3

I. Pre-requisites:

• Equipment master, with measuring point, defined as counter.

• Cycle sets as per requirement.

II. Measuring Point:

Please ensure filling-up of Annual Estimate tab. This will enable the system to calculate the

scheduled calls in advance, based on per day operation hours, as can be seen later .


4/11



© 2011 SAP AG 4

III. Cycle Set creation:

T.Code: IP11Z

Note: The cycle set may be created with different cycles, pertaining to specific equipment /

vehicle.For example, above cycles are suitable for utility equipment like compressors or generators,

since we use unit of measurement as operating hours.

By keeping the cycle text as the type of inspection, easy understanding of the cycle is possible.

The required logic (OR/AND) can be determined while creating maintenance plan.


5/11



© 2011 SAP AG 5

IV. Maintenance Plan creation:

T.Code: IP43

The required cycle set is selected in the initial screen and execution brings all the selected sets

in the maintenance plan header.

Please note how ‘Cycle Set Seq’ (1st row of header) is numbered.

As can be seen, each pair (4 month OR 250 Hours) is marked as single number. This number

is used in the item screen, as seen below.

Note: Each cycle may contain counters of different dimension also. Eg. Nos and hours can be

used in case of aircraft-No. of landings and flying hours.


6/11



© 2011 SAP AG 6

In the above plan, the vehicle mentioned has to under-go all the above 4 cycles in sequence.

Hence 4 line items are created with the same equipment, but with different Cycle Set Seq, as

seen above.Different task lists, as per frequency can be attached to respective line items, since strategy

cannot be used here.


7/11



© 2011 SAP AG 7

Following screen shows the assignment of logic, date determination and start date of the plan.

Note: 1. As illustrated above, it should be noted that the start date is in header level, and

hence applicable for all items of the plan.

2. As the equipment is assigned, the respective counter number is automatically picked-up

at header level, as shown below.

V. Maintenance Plan Scheduling:

Schedule the maintenance plan through T.Code: IP10, and save. Here we have following

options.


8/11



© 2011 SAP AG 8

1. Start: This button starts the plan from cycle set 1- that is from 4 Months OR 250 Hours

inspection.

2. Start In Cycle: This button opens a new screen asking for the cycle to be started with.

Required cycle may be entered and the scheduling starts with that cycle.

3. Restart: If plan is already scheduled, then this will restart the scheduling.

4. When scheduled, the current counter reading is updated in the plan.

5. Option is available to either to delete or skip the plans, when rescheduling.

VI. Schedul ing overview: (T.Code: IP03)

Select a cycle and click the icon. This will show the algorithm, based on which the call was

made.


9/11



© 2011 SAP AG 9

Here the call was made on the anticipated operating hours, which is calculated on the ‘Annual

estimate’ given in the respective measuring point.

This can be viewed by the following method.

In T.Code IP10, under cycles, select the cycle with counter and click button.

Please refer illustration below.

The system will calculate a near accurate plan date, based on the latest measurement document

reading.


10/11


11/11



© 2011 SAP AG 11

Copyright

© Copyright 2011 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, Excel, Outlook, and PowerPoint are registered trademarks of Microsoft Corporation.

IBM, DB2, DB2 Universal Database, System i, System i5, System p, System p5, System x, System z, System z10, System z9, z10, z9,iSeries, pSeries, xSeries, zSeries, eServer, z/VM, z/OS, i5/OS, S/390, OS/390, OS/400, AS/400, S/390 Parallel Enterprise Server,PowerVM, Power Architecture, POWER6+, POWER6, POWER5+, POWER5, POWER, OpenPower, PowerPC, BatchPipes,BladeCenter, System Storage, GPFS, HACMP, RETAIN, DB2 Connect, RACF, Redbooks, OS/2, Parallel Sysplex, MVS/ESA, AIX,Intelligent Miner, WebSphere, Netfinity, Tivoli and Informix are trademarks or registered trademarks of IBM Corporation.

Linux is the registered trademark of Linus Torvalds in the U.S. and other countries.

Adobe, the Adobe logo, Acrobat, PostScript, and Reader are either trademarks or registered trademarks of Adobe SystemsIncorporated in the United States 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, ICA, Program Neighborhood, MetaFrame, WinFrame, VideoFrame, and MultiWin are trademarks or registered trademarks ofCitrix Systems, Inc.

HTML, XML, XHTML and W3C 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 byNetscape.

SAP, R/3, SAP NetWeaver, Duet, PartnerEdge, ByDesign, SAP Business ByDesign, and other SAP products and services mentionedherein as well as their respective logos are trademarks or registered trademarks of SAP AG in Germany and other countries.

Business Objects and the Business Objects logo, BusinessObjects, Crystal Reports, Crystal Decisions, Web Intelligence, Xcelsius, andother Business Objects products and services mentioned herein as well as their respective logos are trademarks or registeredtrademarks of Business Objects S.A. in the United States and in other countries. Business Objects is an SAP company.

All other product and service names mentioned are the trademarks of their respective companies. Data contained in this documentserves informational purposes only. National product specifications may vary.

These materials are subject to change without notice. These materials are provided by SAP AG and its affiliated companies ("SAPGroup") for informational purposes only, without representation or warranty of any kind, and SAP Group shall not be liable for errors oromissions with respect to the materials. The only warranties for SAP Group products and services are those that are set forth in theexpress warranty statements accompanying such products and services, if any. Nothing herein should be construed as constituting anadditional warranty.

EAM-Prev. Maint. Multiple Cntr Plan-SAP

Documents

Transcript of EAM-Prev. Maint. Multiple Cntr Plan-SAP