Utilities_Building_Blocks_China_Preventative Maintenance _885_BPP.doc

EHP3 for SAP ERP 6.0

December 2009

English

Preventative Maintenance for Utility Companies (885)

SAP AGDietmar-Hopp-Allee 1669190 WalldorfGermany

Business Process Documentation

© SAP AG of 32

SAP Best Practices Preventative Maintenance for Utility Companies (885): BPD

Copyright

© Copyright 2009 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 Systems Incorporated 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 of Citrix 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 by Netscape.

SAP, R/3, SAP NetWeaver, Duet, PartnerEdge, ByDesign, SAP Business ByDesign, 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 other countries.

Business Objects and the Business Objects logo, BusinessObjects, Crystal Reports, Crystal Decisions, Web Intelligence, Xcelsius, and other Business Objects products and services mentioned herein as well as their respective logos are trademarks or registered trademarks 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 document serves 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 ("SAP Group") for informational purposes only, without representation or warranty of any kind, and SAP Group shall not be liable for errors or omissions with respect to the materials. The only warranties for SAP Group products and services are those that are set forth in the express warranty statements accompanying such products and services, if any. Nothing herein should be construed as constituting an additional warranty.

© SAP AG of 32


Icons

Icon Meaning

Caution

Example

Note

Recommendation

Syntax

External Process

Business Process Alternative/Decision Choice

Typographic Conventions

Type Style Description

Example text Words or characters that appear on the screen. These include field names, screen titles, pushbuttons as well as menu names, paths and options.

Cross-references to other documentation.

Example text Emphasized words or phrases in body text, titles of graphics and tables.

EXAMPLE TEXT Names of elements in the system. These include report names, program names, transaction codes, table names, and individual key words of a programming language, when surrounded by body text, for example, SELECT and INCLUDE.

Example text Screen output. This includes file and directory names and their paths, messages, source code, names of variables and parameters as well as names of installation, upgrade and database tools.

EXAMPLE TEXT Keys on the keyboard, for example, function keys (such as F2) or the ENTER key.

Example text Exact user entry. These are words or characters that you enter in the system exactly as they appear in the documentation.

<Example text> Variable user entry. Pointed brackets indicate that you replace these words and characters with appropriate entries.

© SAP AG of 32


Contents

1 Purpose.................................................................................................................................. 5

2 Prerequisites........................................................................................................................... 6

2.1 Master Data Used............................................................................................................6

2.2 Roles............................................................................................................................... 7

3 Process Overview Table.........................................................................................................7

3.1 Process 1: Time-Based Maintenance Plan......................................................................7

3.2 Process 2: Performance-Based Maintenance Plan.........................................................8

3.3 Process 3: Condition-Based Maintenance Plan...............................................................9

4 Process Steps........................................................................................................................ 9

4.1 Scenario I: Time-Based Maintenance Plan.....................................................................9

4.2 Scenario II: Performance-Based Maintenance Plan......................................................18

4.3 Scenario III: Condition-Based Maintenance Plan.........................................................27

5 Follow-Up Processes............................................................................................................31

5.1 Process Maintenance Notification.................................................................................31

6 Appendix............................................................................................................................... 32

6.1 Reversal of Process Steps............................................................................................32

6.2 SAP ERP Reports.........................................................................................................33

© SAP AG of 32


Preventative Maintenance for Utility Companies

1 PurposeEnsuring a high availability of equipment in the long term is an important factor for a power company. Preventive maintenance is used to avoid system breakdown or the breakdown of other equipment, which - in addition to the repair costs - often result in much higher costs subsequently owing to production breakdown.

In addition to internal company aspects for preventive maintenance, external factors should also be considered. An increasing number of conditions set by legislative bodies demand more stringent requirements on planned monitoring and maintenance of objects. External requirements can be:

Manufacturer recommendations

The manufacturer of your technical objects may recommend certain procedures to ensure that the objects always function optimally.

Legal requirements

There may be labor protection laws or laws concerning the safety of objects which require you to maintain your technical system regularly.

Environmental requirements

Effective preventive maintenance can also help to prevent breakdowns that could lead to environmental hazards.

Another reason for preventive maintenance is the need of quality assurance, since, for example, the quality of products manufactured at a technical system is substantially affected by the operating condition of the Power generation plant.

It is also often more cost-effective to maintain objects regularly, and therefore prevent a much more expensive breakdown. You can determine the data required for this using past data supplied by the system.

In this scenario, the following three type of maintenance planning will be performed.

Time-Based Maintenance Planning

Performance-Based Maintenance Planning

Condition-Based Maintenance Planning

All the maintenance planning should have a cycle set or strategy. We will perform the Time-Based Maintenance Planning and Performance-Based Maintenance Planning according to their maintenance strategy, single cycle set is also a special and simple strategy.

Time-Based Maintenance PlanningMaintenance is performed in specific cycles for time-based maintenance planning, for example, every two months or every six months. According to different legal requirements, industry standards or recommendations from the manufacturer, some equipment will have some complex maintenance cycles. Different maintenance operations (Task list) are required for different cycles. In our scenario, we will create the maintenance strategy for AC lubricating oil pump, and assign the strategies to its task list. After the maintenance plan is created and scheduled, the

© SAP AG of 32


system will generate a separate order, with different operations, for each equipment, on a due date.

Performance-Based Maintenance PlanningWith performance-based maintenance plans, you can plan regular maintenance based on counter readings maintained for measuring points at pieces of equipment and functional locations.

In the power company, some equipment will be operated according to many parameters or status. This parameter or status information can be got by measuring points. Maintenance takes place when the counter for the equipment has reached a certain reading, for example, every 100 operating hours, or every 500 molding cycles. The readings will be collected by an external system like SCADA. You will create these counters in the SAP system, and also create maintenance cycle sets according to the equipments’ maintenance standard. The maintenance plan will be created and scheduled. When the readings of counters are transferred to the SAP system, the system will create measurement documents (counter readings)to record the readings. The calculated planned date depends on the counter reading at the time of planning, and the estimated annual performance that has been defined for the counter.

Condition-Based Maintenance PlanningSome equipment will be operated by its real time status, or an operation parameter like temperature. These parameters have real time readings that should be monitored every second. The counter or measuring point is often created to simulate the equipment. Ruled by legal requirements or industry standards or recommendation from manufacturer, if the reading is not in the permitted range, the external system will collect the information and send it to the SAP system, the system will then create measuring documents to record it, and create the maintenance order automatically.

2 Prerequisites

2.1 Master Data and Organizational DataSAP Best Practices Standard ValuesEssential master and organizational data was created in your ERP system in the implementation phase, such as the data that reflects the organizational structure of your company and master data that suits its operational focus, for example, master data for materials, vendors, and customers.

This master data usually consists of standardized SAP Best Practices default values, and enables you to go through the process steps of this scenario.

Additional Master Data (Default Values)You can test the scenario with other SAP Best Practices default values that have the same characteristics.

Check your SAP ECC system to find out which other material master data exists.

Using Your Own Master DataYou can also use customized values for any material or organizational data for which you have created master data. For more information on how to create master data, see the Master Data Procedures documentation.

© SAP AG of 32


Use the following master data in the process steps described in this document:

Master / org. data

Value Master / org. data details Comments

Company Code 1000 公司代码 1000

Plant 1000 工厂 1

Main work center UTL-G008 general crew

Task list group YU00011/1 交流润滑油泵-日常YU00011/2 交流润滑油泵-策略

Equipment UTL000008 AC lubricating oil pump

UTL000007 FEEDWATER PUMP 1

UTL000006 shut-off device,locking vapour system

2.2 Roles

UseThe following roles must have already been installed to test this scenario in the SAP NetWeaver Business Client (NWBC). The roles in this Business Process Documentation must be assigned to the user or users testing this scenario. You only need these roles if you are using the NWBC interface. You do not need these roles if you are using the standard SAP GUI.

PrerequisitesThe business roles have been assigned to the user who is testing this scenario.

Business role Technical name Process step

Service Agent SAP_BPR_SERVAGENT-S Create maintenance strategy

Maintaining General Task List

Display Measuring Point

Maintenance Planner

SAP_BPR_PM_IPLM_UTL Create Strategy plan

Create Cycle Sets

Create Maintenance Plan

Maintenance Employee

SAP_BPR_MAINTENANCE-S Scheduling for Maintenance Plan

Starting Maintenance Plan

Monitoring for Maintenance Plan

Notification Processor

SAP_BPR_NOTIFICATION_UTL

Check the Result of Multiple-Counter Maintenance Plan;

Check the Maintenance Notification

3 Process Overview Table

3.1 Process 1: Time-Based Maintenance PlanProcess External Busines Business role Trans- Expected results

© SAP AG of 32


step process reference

s condition

action code

Creating Maintenance Strategies

Service Agent IP11 The maintenance strategy has been created

Maintaining General Task List

Service Agent IA06 Maintained the general task list

Creating Maintenance Plan

Maintenance Planner IP42 Created the maintenance plan

Scheduling for Maintenance Plan

Maintenance Employee IP10 Scheduled and run the maintenance plan

Process Maintenance Order

See 881–Maintenance Order Management with Notification

In this activity, you process the maintenance order.


The maintenance order is processed.

3.2 Process 2: Performance-Based Maintenance PlanProcess step

External process reference

Business condition

Business role Trans-action code

Expected results

Display Measuring Point

Service Agent IE03 Display Measuring Point of the equipment

Creating Cycle Sets

Maintenance Planner IP11Z Created cycle sets

Creating Maintenance Plan

Maintenance Planner IP43 Created maintenance plan

Starting the Maintenance Plan

Maintenance Employee IP10 Start the maintenance plan

Setting Up Deadline Monitoring for Maintenance Plans

Maintenance Employee IP30 Monitor the maintenance plan

Executing N/A. Executing the

© SAP AG of 32


the SCADA Program for Simulation

SCADA program

Checking the Result of Multiple-Counter Maintenance Plan

Notification Processor IW28 Check the result of maintenance plan

Process Maintenance Notification


In this activity, you process the maintenance notification.


The maintenance notification is processed.

3.3 Process 3: Condition-Based Maintenance PlanProcess step

External process reference

Business condition

Business role Trans-action code

Expected results

Display the Measuring Point

Service Agent IE03 Display Measuring Point of the equipment

Executing SCADA Program for Simulating the Measuring Point

N/A. Executing the SCADA program

Checking the Maintenance Notification

Notification Processor IW23 Check the result of maintenance plan

Process Maintenance Notification


In this activity, you process the maintenance notification.


The maintenance notification is processed.

© SAP AG of 32


4 Process Steps

4.1 Scenario I: Time-Based Maintenance Plan

4.1.1 Creating Maintenance Strategies

UseThe maintenance strategy should be created before you create the maintenance plan. You can check and change as you require. The schedule information and parameters are included in the maintenance strategy. This information is needed in the maintenance plan and maintenance task list. Because the maintenance strategy is created, any changes to it will influence all the maintenance plans and maintenance task lists where the strategy is used.

If you re-run this BPD in different language environment, you need to maintain the respective language description about the whole maintenance strategy. Or you only need to check the maintenance strategy.

Procedure1. Access the transaction choosing one of the following navigation options:

Option 1: SAP Graphical User Interface (SAP GUI)

SAP ECC menu Logistics Plant Maintenance Preventive Maintenance Maintenance Planning Maintenance Strategies Change

Transaction code IP11

Option 2: SAP NetWeaver Business Client (SAP NWBC) via Business Role

Business role Service Agent

(SAP_BPR_SERVAGENT-S)

Business role menu Service Processing Notifications Maintain Maintenance Strategies

2. On the Change Maintenance Strategies: Overview screen, choose New Entries.

3. On the Change Maintenance Strategies: Details screen, make the following entries:

Field name Description User action and values Comment

Name YU0001

Description Time_based maintenance strategy

Scheduling indicator

Time

Strategy unit MON

4. On the left screen, double-click Packages, then choose New Entries and make the entries according to the following values:


Package 1

© SAP AG of 32


No.

Cycl.length 1

Unit MON

Maintenance cycle text

1

Cycle ShortText

1

Hierachy 1

Hierachy ShortText

1


Package No.

2

Cycl.length 3

Unit MON


3

Cycle ShortText

3

Hierachy 2

Hierachy ShortText

2


Package No.

3

Cycl.length 6

Unit MON


6

Cycle ShortText

6

Hierachy 3

Hierachy ShortText

3


Package No.

4

Cycl.length 12

Unit MON

© SAP AG of 32



12

Cycle ShortText

12

Hierachy 4

Hierachy ShortText

4

5. Confirm your entries with Enter.

6. Choose Save.

7. Choose Back (F3) to return to the SAP Easy Access screen (SAP GUI) or choose Exit (Shift+F3) and confirm the Business client message with Yes to return to SAP Home (SAP NetWeaver Business Client).

Result The Maintenance Strategy has been created.

4.1.2 Maintaining General Task List

UseMaintenance task lists describe a sequence of individual maintenance activities which must be performed repeatedly within a company. Task lists are used to standardize these recurring work sequences and to plan them more effectively. In this way, you can save the time of creating the maintenance order and making the maintenance plan. The maintenance task list can be used for the maintenance task that is in progress or the periodical maintenance task. Furthermore, the information included in the maintenance task list includes the relevant equipment and tools that are required for the various work steps as well as the time needed to finish the task. When the maintenance strategy is assigned to the maintenance task list, we can assign different maintenance packages according to the operation of the task list.

If you re-run this BPD, you can skip this step.

PrerequisitesThe maintenance strategy should be ready.



SAP ECC menu Logistics Plant Maintenance Preventive Maintenance Work Scheduling Task Lists General Maintenance Task Lists Change

Transaction code IA06




© SAP AG of 32


Business role menu Service Processing Notifications Change General Maintenance Task List

2. On the Change General Task List : Initial Screen, make the following entries:


Group YU00011

Group counter

2

3. Choose Enter to go to the next screen.

4. On the Change General Task List: Operation Overview screen, choose Header to go to the header screen.

5. On the Change General Task List: Header General View screen, you can enter the maintenance strategy YU0001 in the field Maintenance strategy, now the maintenance strategy YU0001 is assigned to the maintenance task list YU00011.

6. Choose Operation to go to the Operation overview screen.

7. On the Change General Task List: Operation Overview screen, choose MntPack.

8. On the Change General Task List: Maintenance Package Overview screen, choose the check box to check and maintain the following values:

Op. 1 3 6 12

0010 X X X X

0020 X X

0030 X X X X

0040 X X X X

0050 X X

0060 X X

0070 X X

0080 X X X X

0090 X X

0100 X X X X

0110 X X X X

9. Confirm your entries with Enter.

10. Choose Save.

11. Choose Continue to confirm the message General task list YU00011 saved.


ResultThe Maintenance Strategy has been assigned to the maintenance task list; and the packages of the General Task List are maintained.

© SAP AG of 32


4.1.3 Creating Maintenance Plan

UseThe maintenance plans are required to improve the availability of equipment; when you create the maintenance plan, you need to get the maintenance strategy information or other information like planning cycle, scope, horizon, adjustment parameter.

PrerequisitesMaintenance plan and maintenance strategy are created, and the task list is assigned to maintenance strategy.



SAP ECC menu Logistics Plant Maintenance Preventive Maintenance Maintenance Planning Maintenance Plans Create Strategy Plan



Business role Maintenance Planner

( SAP_BPR_PM_IPLM_UTL)

Business role menu Preventive Maintenance Maintenance Planning Maintenance Plans Create Strategy Plan

2. On the Create Maintenance Plan : Initial screen, make the following entries:


Maintenance plan

Maint. plan cat.

PM PM order

Strategy YU0001 The strategy was created in the previous step.

3. Choose Enter to go to the next screen Create Maintenance Plan: Strategy plan. Enter the following data:


Maintenance plan

Description field AC lubricating oil pump maintenance plan

4. Scroll down to the lower part of this screen Create Maintenance Plan: Strategy plan, and in the Item tab Reference object area, make the following entries:


Equipment UTL000008

5. In the Planning data area, enter the following data:


© SAP AG of 32


Planning plant

1000

Order Type YU23 Generation Preventive order

Main WorkCtr

Main work center UTL-G008 general crew

6. In the Task list area, make the following entries:


Typ A

Task LstGrp YU00011

GrpCr 2 The strategy was created in the previous step.

7. Choose the tab maintenance plan scheduling parameters and make the following entries:


Call horizon 100 %

Scheduling period

15 MON

8. Choose Save to save it.

9. In the Start Date dialog box, keep the default value:


Cycle start Current Data

You also can change the date according to your requirement.

10. Choose Continue (Enter) to save this maintenance plan and note down the maintenance plan number.


ResultThe Maintenance Plan has been created.

4.1.4 Scheduling for Maintenance Plan

UseYou schedule a maintenance plan for which the system generates maintenance call objects (for example, maintenance orders or service orders) for the defined cycles. You can use automatic deadline monitoring (see Scheduling) to schedule a maintenance plan for the first time or reschedule it. A manual maintenance call allows you to include additional dates for maintenance calls without affecting normal scheduling. You can specify the required call date and maintenance packages which should be due on this date.

Prerequisites

© SAP AG of 32


The maintenance plan has already been created.



SAP ECC menu Logistics Plant Maintenance Preventive Maintenance Maintenance Planning Scheduling for Maintenance Plans Schedule



Business role Maintenance Employee

(SAP_BPR_MAINTENANCE-S)

Business role menu Product Maintenance Planning Schedule Maintenance Plan

2. On Schedule Maintenance Plan :Initial screen make the following entries:


Maintenanceplan

Such as 1. The maintenance plan number you noted in the previous step.


4. On Schedule Maintenance Plan: Strategy plan 0000000000XX screen, choose Start to start the schedule.

5. On the Start Date dialog box, keep the date as current date or change it according to your requirement.

6. Choose Continue (Enter) to continue.

7. Choose Save.

8. On the Schedule Maintenance Plan: Initial screen, choose Enter to do a manual call.

9. On Schedule Maintenance Plan: Strategy plan 0000000000XX screen, in the Scheduling List screen area, select the item that the due package is 1, and choose Manual call.

10. On the Start Date dialog box, choose Continue (Enter) to continue.

11. On the Strategy Package Selection: YU0001 screen, choose the entry 1 and choose Continue (Enter) to continue.


13. On the Schedule Maintenance Plan: Initial screen, choose Enter to check the manual call.

14. On Schedule Maintenance Plan: Strategy plan 0000000000XX screen, select the tab Manual calls, choose the item for example 90,000,000.

15. On the lower part of this screen, choose Display call object to display the maintenance order.

16. On Display Generation Preventive Order: 40000XX : Central Header screen ,choose the tab Operations, you can see all the operations needed for maintenance package 1 (one month) are already there.

17. On Display Generation Preventive Order: 40000XX : Operation Overview screen, choose Back two times to quit this screen and choose Yes to save the maintenance plan.

© SAP AG of 32


18. You can repeat steps 8 to 17 to see the result when due package is another package number.


ResultMaintenance Plan is scheduled. The maintenance order has been created after manual calls or the scheduled time comes.

4.1.5 Follow-Up Processes

4.1.5.1 Process Maintenance Order

UseThis activity will process maintenance order.

Procedure

Maintenance Order Management with Notification (881)To execute this activity, process the following steps using the master data from this document (see also table below):

Steps to process from scenario Maintenance Order Management with Notification (881)

Scheduling the Maintenance Order

Attachment Management

Approving the Maintenance Order

Releasing the Maintenance Order

Components Requirement Quantity Change Management (Optional)

Printing the Work Order Ticket

Withdrawing the Material

Individual Time Confirmation

Technically Completing the Order

Settling the Order

Complete the Order (Optional)

To execute this activity, run the Maintenance Order Management with Notification (881) master data in this document.

© SAP AG of 32


5 Scenario II: Performance-Based Maintenance Plan

5.1 Displaying the Measuring Point

UseDisplay the measuring point of the equipment.

PrerequisitesThis counter has already been created in background.



SAP ECC menu Logistics Plant Maintenance Management of Technical Objects Equipment Display

Transaction code IE03




Business role menu Service Processing Technical Objects Display Equipment

2. On the Display Equipment : Initial Screen, enter your equipment number: UTL000007. Then Choose Enter .

3. On the Display Equipment : General Data screen, choose menu (NWBC: More… )Goto Measuring points/counters, then you have the counters of the equipment UTL000007 displayed as following.

MeasPoint Measurement position

Cat Char. Name

Unit

1（please refer to the actual data as system）

C1-C1021 YU0629 PC

2（please refer to the actual data as system）

PUMP FLUX

YU0002 L

4. Note down the measuring point number and the respective unit


Result The equipment’s measuring points have displayed.

© SAP AG of 32


5.2 Creating Cycle Sets

UseCreate different cycle sets.

PrerequisitesThis counters have already been created, the both measuring points are counters.



SAP ECC menu Logistics Plant Maintenance Preventive Maintenance Maintenance Planning Cycle Sets Change

Transaction code IP11Z



(SAP_BPR_PM_IPLM_UTL)

Business role menu Preventive Maintenance Maintenance Planning Cycle Sets Change

2. On the Change Cycle Sets : Overview screen, choose New Entries and make the following entries:


Name For example:YU0002

Description Pump Cycle sets

If you re-run the BPD, use another new value for the Cycle Sets name.

3. In Dialog Structure, double-click Cycles.

4. Choose New Entries and input the entries according to the following values:


Package No.

1

Cycl.length 20

Unit PC


every 20 pc

Cycle ShortText

1


© SAP AG of 32


Package No.

2

Cycl.length 300

Unit L


Every 300 liter

Cycle ShortText

2

5. Choose Enter to confirm.



Result The cycle sets have been created.

5.3 Creating Maintenance Plan

UseA multiple counter plan is used in counter-based (performance-based) maintenance. This type of maintenance planning is not based on a maintenance strategy. This means that you create a multiple counter plan without a maintenance strategy.

The cycles for a multiple counter plan are linked with either an OR operation or an AND operation.

For an OR operation, a maintenance order is generated for the earliest possible planned date. If maintenance is due, for example, every 100 tons produced or every 50 operating hours or every two weeks, the decisive factor is which occurs first.

For an AND operation, a maintenance order is generated for the last planned date. If maintenance is due, for example, every 100 tons produced or every 50 operating hours or every two weeks, the decisive factor is which occurs last.

PrerequisitesCycle sets and counter were created.



SAP ECC menu Logistics Plant Maintenance Preventive Maintenance Maintenance Planning Maintenance Plans Create Multiple Counter Plan




© SAP AG of 32


(SAP_BPR_PM_IPLM_UTL)

Business role menu Preventive Maintenance Maintenance Planning Maintenance Plans Create Multiple Counter Plan

2. On Create Maintenance Plan : Initial screen, make the following entries:


Maintenance plan

Blank

Maint. plan cat.

PN pm notification

Cycle set YU0002 Cycle set you created in previous step


4. On Create Maintenance Plan : Multiple cntr plan screen, make the following entries:


Maintenance plan

Description multi-counter planning

5. On Create Maintenance Plan : Multiple cntr plan screen, Maintenance plan cycle tab, make the following entries:


Cycle Set Seq.

1

Counter for example, 1 You noted in the previous step. Specially note the counter’s unit according with the item’s unit

Cycle Set Seq.

1

Counter for example, 2 You noted in the previous step.

6. Under the Item tab page, make the following entries.


Cycle Set Seq.

1

7. Scroll down to the lower part of this screen , and in the Reference object area make the following entries:


Equipment UTL000007

8. In the Planning data area, make the following entries:


Planning plant

1000 工厂 1

Notification U1

© SAP AG of 32


type

Main WorkCtr

UTL-G008 general crew

9. choose the tab maintenance plan scheduling parameters and make the following entries:


SchedPeriod

100(day) The planning cycle is 100 days.

AND - link For an AND operation, a maintenance order is generated for the last planned date

OR- link select For an OR operation, a maintenance order is generated for the earliest possible planned date.

Start Date today

10. Choose Save.

11. Note down the maintenance plan number.


ResultThe multiple counters Maintenance Plan has been created.

5.4 Starting the Maintenance Plan

UseSchedule the maintenance plan, in multiple-counter plan, it is very important to know the difference between the OR operation and AND operation.

For an AND operation, a maintenance order is generated for the last planned date.

For an OR operation, a maintenance order is generated for the earliest possible planned date, you can create a manual call by decreasing the shorter cycle. If the planning cycle is too long, the system will get the last call by getting the daily reading (yearly average value of this counter/365), and this date should not be earlier than the call date of the shortest cycle. If the call horizon is not due, the system will not perform any checking on operation.

PrerequisitesThe maintenance plan has been created.



SAP ECC menu Logistics Plant Maintenance Preventive Maintenance

© SAP AG of 32


Maintenance Planning Scheduling for Maintenance Plans Schedule





Business role menu Product Maintenance Planning Schedule Maintenance Plan

2. On Schedule Maintenance Plan: Initial screen, make the following entries:


MaintenancePlan

Such as 2. The maintenance plan number you noted in the previous step.


4. Choose Start to start the schedule.

5. On the Start Date dialog box, keep the date as current date or change it according to your requirement.

6. Choose Continue (Enter).

7. Choose Continue (Enter) to continue on the Display log dialog box.



Result The Maintenance Plan is scheduled.

5.5 Setting Up Deadline Monitoring for Maintenance Plans

UseWhen the deadline monitor is scheduled for this maintenance plan in the background, this maintenance plan will be carried out automatically.



SAP ECC menu Logistics Plant Maintenance Preventive Maintenance Maintenance Planning Scheduling for Maintenance Plans Deadline Monitoring




© SAP AG of 32



Business role menu Product Maintenance Planning MaintSchedule Date Monitoring

2. On the Deadline Monitoring for Maintenance Plans (Batch Input IP10) screen, make the following entries:


Maintenance plan

for example, 2 The plan number you created in the previous step.

3. Choose F9 to continue.

4. On the Background Print Parameters dialog box, make the following entries:


Output Device

LOCL

5. Choose Continue (Shift +F1)

6. Choose Continue (Enter) again to confirm the Information dialog box.

7. On the Start Time dialog box, choose Immediate. （For real business, we give a period value for setting up deadline monitor; in this scenario we choose Immediate to avoid the performance of SAP system is too slow ）

8. Choose Save. The job has been scheduled.


ResultThe deadline monitor is scheduled for this maintenance plan in the background.

5.6 Executing the SCADA Program for Simulation

UseThe SAP system can not read the data from the equipment, but an external system can do this. When the external system reads the data, the interface can import this data into the SAP system, and then measurement documents will be created to record this reading, so the maintenance plan can be triggered if the reading reaches the setting.

Procedure1. Under the folder /Misc/ SCADA_VB, find the counter.exe and double-click it to execute, you

can see a screen like below.

© SAP AG of 32


2. Choose SAP Logon and logon on to the client which you use and login using your own username and password..


Client The demo client number

User The user ID

Password The USER ID’s password

Language EN

3. Choose OK to logon to the SAP System.

4. On SAP System Information dialog box, choose OK

5. Setting the package size (20). It will create a measurement document automatically when the current data is equal to package size.

6. Select the check box under Operation.

7. The counter under the Current Delta will change and if it reaches the package size, it will generate a measuring document in the SAP system. You can get the Measuring document number in the field Meas.Document.

You’d better pause the simulation program by unselect check box under Operation while the first measurement document has been created. Then you can check the maintenance notification at the next step.

ResultThe external system reads the data from the equipment, and imports the data to SAP system.

© SAP AG of 32


5.7 Checking the Result of Multiple-Counter Maintenance Plan

UseAfter you execute the simulation program, you can pause the simulation program to check if there is any new maintenance notification created while the first and second measurement documents have been created.



SAP ECC menu Logistics Plant Maintenance Maintenance Processing Notification List Editing Change

Transaction code IW28


Business role Notification Processor

(SAP_BPR_NOTIFICATION_UTL)

Business role menu Maintenance Notification Notification List Change Data

2. On the Change Notifications: Selection of Notifications screen, make the following entries:


Maintenance Plan

for example, 2 The Maintenance plan you created.

3. Choose Execute to find the notification.


ResultYou have checked if there is any new maintenance notification created.

5.8 Follow-Up Processes

5.8.1 Process Maintenance Notification

UseThis activity will process maintenance notification.

Procedure

Maintenance Order Management with Notification (881)

© SAP AG of 32


To execute this activity, using the master data in this document, and set User Status of your PM Notification is 15 wfr. waitting for release then run all steps except the first step 4.1.1 Creating Maintenance Request of the scenario Maintenance Order Management with Notification (881).

6 Scenario III: Condition-Based Maintenance Plan

6.1 Displaying Measuring Points

UseThis step is used to display the measuring point. Its name should be consistent with the name of the measuring point in the external system.

PrerequisitesThis counter has already been created in background.



SAP ECC menu Logistics Plant Maintenance Management of Technical Objects Equipment Display

Transaction code IE03




Business role menu Service Processing Technical Objects Display Equipment

2. On the Display Equipment: Initial Screen, enter your equipment number: UTL000006. Then Choose Enter to confirm.

3. On the Display Equipment : General Data screen, choose menu (NWBC: More… )Goto Measuring points/counters, then you have the counters of the equipment UTL000006 displayed as following

MeasPoint Measurement position

Cat Char. Name

Unit

3（refer to the actual data as system）

C1-P1001 YU0628 Pa

4. Note down the measuring point number.


© SAP AG of 32


ResultThe equipment’s measuring points have displayed.

6.2 Executing SCADA Program for Simulating the Measuring Point

UseThis step is used to execute the simulation program. In the simulation program, there are two options while the reading data exceeds the defined value. One is to create the measurement document as well as the maintenance notification in the SAP system, the other is to create measurement document only. In this scenario, we choose the first option.

PrerequisitesThe measuring point has been created and its name should be consistent with the name of the measuring point in the external system.

Procedure1. Under the folder /Misc/SCADA_VB, find the measure.exe and double-click it to execute, you

can see a screen like below.

2. Choose SAP Logon and logon to the client which you use, with your own username and password.

3. Choose OK to logon to the SAP System.

4. On SAP System Information dialog box, choose OK.

5. Choose the check box at the left side of Create Notification.

© SAP AG of 32


6. Drag the pointer in the left side up and down, you can see the value of psi will change when you do it.

7. Drag the pointer up and stop it where the value is over 114 or below 14, wait for a while, it will generate the measuring document and the maintenance notification automatically.

8. The measuring document number and the maintenance notification number will appear in the right part of the screen as below.

9. Note down the PM Notification number____________

ResultThe external system reads the data from the equipment, and imports the data to SAP system.

6.3 Checking the Maintenance Notification

UseAfter the maintenance notification was created, you can get the information about the measuring point and the measure document.



SAP ECC menu Logistics Plant Maintenance Maintenance Processing Notification Display

Transaction code IW23


© SAP AG of 32




Business role menu Maintenance Notification Display

2. On the Display PM Notification : Initial Screen, make the following entries:


Notification for example, 100000XX The Maintenance notification number created in the previous step.

3. Choose Enter.

4. On the Display PM Notification: Malfunction Report screen, on the Notification tab, you can find the Equipment number; it is the same number as that in the measure point.

5. From the menu, choose (NWBC: More… ) Extras MeasDocuments.

6. On the Display Measurement Documents: Overview screen, you can check the following fields and their values.


MeasPoint for example, 3 The Maintenance notification number created in the previous step.

Measurement position

C1-P1001

Description C1-P1001

Rdg/CtrRdg Measurement Reading

for example, 120.0


ResultYou have checked if there is any new maintenance notification created.

6.4 Follow-Up Processes6.4.1 Process Maintenance Notification

UseThis activity will process maintenance notification.

Procedure

Maintenance Order Management with Notification (881)To execute this activity, using the master data in this document, run all steps except the two steps 4.1.1 Creating Maintenance Request & 4.1.2 Approving the Maintenance Request of scenario the Maintenance Order Management with Notification (881).© SAP AG of 32


7 Appendix

7.1 Reversal of Process StepsIn the following section, you can find the most common reversal steps, which you can take to reverse some of the activities described in this document.

Maintenance Strategy

Transaction code (SAP GUI) IP11

Reversal: Change Maintenance Strategies




Business role menu Service Processing Notifications Maintain Maintenance Strategies

Comment

Schedule the Maintenance Plan


Reversal: Change the call object (Maintenance order)

Transaction code (SAP GUI) IW32

Business role Service Employee

(SAP_BPR_SERVEMPLOYEE-S)

Business role menu Customer Service Service Processing Change Order

Comment If you do not need the call object (maintenance order),

use one the following options:

If the order is not released:

1. Set the system status NCMP (Not completed) with the function Do Not Execute. .

If the order is released:

1. Set the system status CLSD (Closed) with the function Complete (Business).

Set the system status DLFL (Deletion Flag).

Schedule the Maintenance Plan

© SAP AG of 32



Reversal: Change the call object (Maintenance Notification)

Transaction code (SAP GUI) IW22



Business role menu Maintenance Notification Change

Comment Set the system status DLFL (Deletion Flag).

7.2 SAP ERP Reports

UseThe table below lists the reports that you can use to obtain additional information on this business process.

You can find detailed descriptions of the individual reports in the following BPD documents, which provide a comprehensive compilation of all important reports:

Financial Accounting: SAP ERP Reports for Accounting (221)

Logistics Processes: SAP ERP Reports for Logistics (222)

Note that the descriptions of some reports that are an indispensable part of the process flow may be located directly in the section where they belong.

ReportsReport title Transaction

code ( SAP GUI)Comment

Maintenance plan IP16 A list of maintenance plans

Maintenance schedule overview

IP24 Maintenance schedule overview list

© SAP AG of 32

Utilities_Building_Blocks_China_Preventative Maintenance _885_BPP.doc

Documents

Transcript of Utilities_Building_Blocks_China_Preventative Maintenance _885_BPP.doc