Plant Maintenance

Overview of Plant Maintenance (PM)
PDF download from SAP Help Portal:

http://help.sap.com/saphelp_46c/helpdata/en/66/15864d547611d182cc0000e829fbfe/content.htm
Created on January 20, 2016
The documentation may have changed since you downloaded the PDF. You can always find the latest information on SAP Help
Portal.
Note
This PDF document contains the selected topic and its subtopics (max. 150) in the selected structure. Subtopics from other structures are not included.
2016 SAP SE or an SAP affiliate company. 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 SE. The information contained herein may be changed without prior notice. Some software products marketed by SAP
SE and its distributors contain proprietary software components of other software vendors. National product specifications may vary. These materials are
provided by SAP SE 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 and other SAP products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP SE in
Germany and other countries. Please see www.sap.com/corporate-en/legal/copyright/index.epx#trademark for additional trademark information and notices.
Table of content
PUBLIC
2014 SAP SE or an SAP affiliate company. All rights reserved.
Page 1 of 22
Table of content
1 Overview of Plant Maintenance (PM)
1.1 Plant Maintenance
1.1.1 Technical Objects (CS-BD/PM-EQM)
1.1.1.1 Equipment (CS-BD/PM-EQM-FL)
1.1.1.2 Functional Locations (CS-BD/PM-EQM-FL)
1.1.1.3 Object Networking (CS-BD/PM-EQM-ON)
1.1.1.4 Maintenance Bills of Material (CS-BD/PM-EQM-BM)
1.1.1.5 Additional Functions
1.1.1.5.1 Measuring Points and Counters (CS-IB-MC/PM-EQM-SF-MPC)
1.1.1.5.2 Warranties (CS-AG-WA/PM-EQM-SF)
1.1.1.5.3 Permits (CS-SE/PM-EQM-SF)
1.1.2 Preventive Maintenance
1.1.2.1 Task Lists (CS-AG/PM-PRM-TL)
1.1.2.2 Maintenance Planning (CS-AG/PM-PRM-MP)
1.1.3 Maintenance Processing
1.1.3.1 Notifications (CS-CM-SN/PM-WOC-MN)
1.1.3.2 Orders (CS-SE/PM-WOC-MO)
1.1.3.3 Capacity Planning in Plant Maintenance (PM-WOC-CP)
1.1.3.4 Completion Confirmations (CS-SE-CON/PM-WOC-JC)
1.1.3.5 Maintenance History (PM-WOC-MH)
1.1.4 Maintenance Projects
1.1.4.1 Project Structure (Plant Maintenance)
1.1.4.2 Networks (Plant Maintenance)
1.1.4.3 Project Management (Plant Maintenance)
1.1.5 Information System
1.1.5.1 Reporting
1.1.5.2 Planning
1.1.5.3 Interface to Logistics Information Library
1.1.5.4 Data Collection
1.1.5.5 Early Warning System
PUBLIC
Page 2 of 22
1 Overview of Plant Maintenance (PM)
1.1 Plant Maintenance

Purpose
This component contains the functions for Plant Maintenance.
Plant Maintenance comprises the following activities:
Inspection
All measures which establish the actual condition of a technical system
Preventive maintenance
All measures which maintain the ideal condition of a technical system
Repair
All measures which restore the ideal condition of a technical system
Other measures taken using the maintenance organization
Integration
Through integration with other modules (for example, Materials Management, Production, Sales and Distribution, Personnel Management, and Controlling) the
data is always kept current and processes that are necessary for Plant Maintenance and Customer Service are automatically triggered in other areas (for
example, a purchase requisition for non-stock material in the Materials Management/Purchasing area).
1.1.1 Technical Objects (CS-BD/PM-EQM)

Purpose
If DP-supported maintenance is to be set up properly at a company, it is necessary to structure the existing technical systems on the basis of technical
objects.
Advantages of structuring:
The time required for managing the technical objects is reduced.
Maintenance processing is simplified.
The time spent entering data during maintenance processing is reduced considerably.
More specific, thorough and faster evaluation of maintenance data.
Implementation Considerations
You should allow sufficient time for planning the structure. Weigh up all the pros and cons for your company that each structuring approach will bring. Note that
it takes longer to restructure objects later than it does to structure them in the first place.
Before you start representing technical objects in the system, it is imperative that you read the corresponding texts in the R/3 Implementation
Guide (IMG).
Integration
Structuring your systems forms the basis for implementing the application components Plant Maintenance (PM) and Customer Service (CS) .
Features
Before you begin representing technical objects in the system, you should be aware of the organization of maintenance planning within your company. You
should focus primarily on the structure of the entire company. This involves defining correctly the maintenance plants and maintenance planning plants in your
system.
Maintenance Plant
The maintenance plant for a technical object is the plant at which it is installed.
PUBLIC
Page 3 of 22
Clarification plant C1 is located in plant 0001. Plant 0001 is therefore the maintenance plant for the clarification plant C1.
Maintenance Planning Plant
The maintenance planning plant for a technical object is the plant in which the maintenance tasks for the object are planned and prepared. Maintenance
planner groups work at the maintenance planning plant to plan and prepare the maintenance tasks for the plants that are assigned to the maintenance planning
plant. The following activities are performed at the maintenance planning plant:
Definition of task lists
Material planning based on bills of material in task lists and orders
Management and scheduling of maintenance plans
Creation of maintenance notifications
Execution of maintenance orders
The maintenance plant for the clarification plant C1 is plant 0001. Plant 0001 does not perform its own maintenance planning. It is assigned to
plant 0002, in which a maintenance planner group works, and that, for this reason, is indicated in the system as being a maintenance planning
plant. The maintenance planner group in plant 0002 plans for plants 0001 and 0002.
The maintenance planning plant for the clarification plant C1 is therefore plant 0002.
The way in which you represent the organization of maintenance planning in your company depends on the structure of the entire company. You have three
options:
Centralized maintenance planning
Decentralized maintenance planning
Partially centralized maintenance planning
Centralized Maintenance Planning
With centralized maintenance planning, you can have the following combinations of plants:
A The company comprises only one plant which is both maintenance plant and maintenance planning plant for all the technical objects.
B The company has several maintenance plants, however, only one plant in which maintenance planning is performed. The plant in which maintenance
planning is performed is indicated in the system as the maintenance planning plant. All other plants are assigned to this plant as maintenance plants, for which
the maintenance tasks must be planned in the maintenance planning plant.
Plants:
0001, 0002, 0003
Maintenance plants:
0001, 0002, 0003
Maintenance planning plant:
0001
Plants assigned to the maintenance planning plant:

0002, 0003
Decentralized Maintenance Planning
The company comprises several maintenance plants. Each plant performs its own maintenance planning. In this case, all the plants in the system are
indicated as maintenance planning plants.
Plants:
0001, 0002, 0003
Maintenance plants:
0001, 0002, 0003
Maintenance planning plants:
0001, 0002, 0003
Partially Centralized Maintenance Planning

The company comprises several maintenance plants. Some of the maintenance plants perform their own maintenance planning, others do not. The plants
without their own maintenance planning are assigned to maintenance planning plants in which planning is also performed for them, whilst the plants in which
maintenance planning is performed are indicated in the system as being maintenance planning plants.
Plants:
0001, 0002, 0003, 0004, 0005
Maintenance plants:
0001, 0002, 0003, 0004, 0005
Maintenance planning plants:
0001, 0004
Plants assigned to maintenance planning plant 0001:

0002, 0003
Plants assigned to maintenance planning plant 0004:
0005
Once you have represented the organizational structure of your company, you can choose between three different options for representing technical objects:
Functional structuring (only functional locations)
Object-related structuring (only equipment)
Combination (equipment at functional locations)
PUBLIC
Page 4 of 22
Functional Structuring
With this type of structuring, you subdivide your technical system into functional locations. For example, when you subdivide a production line into functional
locations, you can represent the individual function units as functional locations in the system.
If you use functional locations when structuring your technical system, you can also take into account the process-oriented or spatial structure of the system.
For more information, see
Functional Location and Reference Functional Location.
Object-Related Structuring
With this type of structuring, you subdivide your technical system into pieces of equipment. A piece of equipment is an individual, physical object that is to
be maintained independently, and that can be installed in a technical system or part of a technical system.
Combination
You can combine object-related structuring using pieces of equipment with functional structuring using functional locations. In this case, the pieces of
equipment are installed at functional locations (installation/dismantling of individual objects at a functional location).
The functional location represents the site where the technical tasks are performed.
The piece of equipment represents the object with which the technical tasks are performed.
Within damage analysis, you will then be able to recognize, for example, whether or not damage occurring repeatedly is linked to the usage site, or is specific
to the objects made by a particular manufacturer.
For more information, see:
Equipment
Hierarchical Equipment Structure
Equipment at Functional Locations
Structuring from a Technical and/or Accounting Perspective
When you perform structuring from a technical perspective, you assign the technical objects of the system to particular object classes (equipment, functional
location and assembly classes).
You can use this type of structuring in addition to structuring from a functional and/or object-related perspective.
Classification of Technical Objects.
When you perform structuring from an accounting perspective, you assign the system and its technical objects to certain cost centers or tangible assets.
You can use this type of structuring in addition to structuring from a functional and/or object-related perspective.
Equipment as Units of Tangible Assets.
1.1.1.1 Equipment (CS-BD/PM-EQM-FL)

Purpose
A piece of equipment is an individual object that is to be maintained independently. Each piece of equipment is managed independently in the system, so that
you can:
Manage individual data from a maintenance perspective for the object
Perform individual maintenance tasks for the object
Keep a record of the maintenance tasks performed for the object
Collect and evaluate data over a long period of time for the object
Pieces of equipment can be installed and dismantled at functional locations. The usage times for a piece of equipment at a functional location are documented
over the course of time.
You should always create an equipment master record for a technical object if:
Individual data is to be managed for the object (for example, year of construction, warranty period, usage sites)
Maintenance tasks are to be performed for the object, either regular, planned or resulting from damage
A record of the maintenance tasks performed for the object must be kept (for example, for insurance or compulsory annual inspection purposes)
Technical data on the object is to be collected and evaluated over a long period of time
The costs of maintenance tasks are to be monitored for the object
Records of usage times at functional locations are required for the object
Integration
PUBLIC
Page 5 of 22
You can use pieces of equipment by themselves (pure object-related structuring), or in combination with the component Functional locations (function and
object-related structuring).
You can create warranties in the system using the Customer Service (CS) application component .
You can also use pieces of equipment in the following application areas:
Production Planning and Control (PP):
Production resources/tools
Quality Management (QM):
Test equipment
Materials Management (MM): Serialized material
Sales and Distribution (SD):
Customer devices
1.1.1.2 Functional Locations (CS-BD/PM-EQM-FL)

Purpose
Functional locations are elements of a technical structure (for example, functional units within a system). You create functional locations hierarchically, and
can also structure them based on the following criteria:
Functional
Process-related
Spatial
Each functional location is managed independently in the system, so that you can:
Manage individual data from a maintenance perspective for the object
Perform individual maintenance tasks for the object
Keep a record of the maintenance tasks performed for the object
Collect and evaluate data over a long period of time for the object
You implement this component if:
You want to represent systems or operational structures within your company according to functionality
Maintenance tasks (in the broadest sense) are to be performed for the individual areas of your system or operational structure
Records are to be kept of the maintenance tasks that are performed for the individual areas of your system or operational structure
Technical data is to collected and evaluated over long periods of time for the individual areas of your system or operational structure
The costs of maintenance tasks are to be monitored for the individual areas of your system or operational structure
You want to perform analyses on the influence of usage conditions on the damage susceptibility of the pieces of equipment installed
You require different views of a location structure (for example, a technical procedure view and a measurement/control technique view).
Refer to
Reference Functional Location and Functional Location, before you start representing functional locations and reference functional locations in the system.
Integration
Pieces of equipment can be installed and dismantled at functional locations. The usage times for a piece of equipment at a functional location are documented
over the course of time. If you want to use pieces of equipment, you need to implement the component Equipment .
Features
The hierarchical structure of the functional location enables you to maintain centrally data that is on higher levels for all levels located below (hierarchical
data transfer).
For more information on hierarchical data transfer, see
Data Transfer.
You can also work with reference functional locations within this component. When doing this, you only have to define each specific type of data once.
The reference location provides the corresponding locations located horizontally with the type-specific data (horizontal data transfer).
PUBLIC
Page 6 of 22
You can display the objects of the entire technical system using various structure views.
You can create functional locations and reference locations much quicker using list editing, than by creating them individually.
You can assign several labels to each functional location. You define the label that you work with the most as the primary label and all others as
alternative labels. You use this function if different views of functional locations structures are required.
Certain users then identify a functional location in the technical procedure view or labeling system 1 using label A, while other users identify the same
functional location in their measurement/control technique view or labeling system 2 using label B.
1.1.1.3 Object Networking (CS-BD/PM-EQM-ON)

Purpose
The Plant Maintenance (PM) application component provides functions with which you can represent the links that exist between various technical objects or
systems (pieces of equipment or functional locations). Such links exist, for example, between production units alone, between production systems and supply
systems and between supply and disposal systems. You represent an object network using the object links. You can therefore structure your technical
systems horizontally.
The following are reasons for using object links:
You want to see the connections between various objects, in order to be able to recognize possible causes in predefined object systems when analyzing
malfunctions.
You want to be able to see at all times the objects which supply another object, so that you know when planning a maintenance task which particular
supply systems might have to be shut down.
You want to be able to see at all times the objects which supply another object, so that you know when planning a maintenance task which particular
objects will be affected when a system is shut down.
Integration
In addition to horizontal structuring using object networks, the PM application component also provides structuring options that allow the user to structure
technical systems vertically, in other words, hierarchically. Horizontal and vertical structuring options can be combined.
PM provides the following options for structuring technical systems hierarchically:
Functional structuring in functional locations
Object-related structuring in pieces of equipment
Technical structuring according to particular object classes
For more information on hierarchic structuring types, see
Technical Objects (Structuring of Technical Systems).
1.1.1.4 Maintenance Bills of Material (CS-BD/PM-EQM-BM)

Purpose
A maintenance bill of material (BOM) is a complete, formally structured list of the components making up a technical object or an assembly. The list contains
the object numbers of the individual components together with their quantity and unit of measure. The components can be stock or non-stock spares or
assemblies, which in turn can be described using maintenance BOMs.
Maintenance BOMs are primarily used for the following purposes:
Structure description
A maintenance BOM describes the structure of a technical object or material. Using maintenance BOMs you can specify exactly where maintenance
tasks are to be performed on a technical object.
Assignment of spare parts
A maintenance BOM is used in plant maintenance to assign spares for a technical object or material. This is shown in the figure below:
PUBLIC
Page 7 of 22
Using maintenance bills of material presents the following advantages:
Materials planning
(when using maintenance task lists)
The use of maintenance BOMs is advantageous for material planning, because you can perform material planning when creating a maintenance task
list. The link between the task list and the maintenance BOM is created as follows:
Using the technical object BOM for maintenance task lists for technical objects
Using the assembly in the header for general task lists
The link to a maintenance BOM enables you to assign materials that have already been planned for the technical object or the assembly to the
individual operations in the task list. You can use the structure list or the structure graphic to do this. As both display options provide a detailed
overview of all the materials of the BOM, material planning is simplified considerably.
For more information on maintenance task lists, refer to the document PM - Maintenance Task Lists .
Materials/spares planning
(when using maintenance orders)
Maintenance bills of material support you during materials or spares planning by providing you with an overview of all materials/spare parts that could be
required in the maintenance order. This enables you to assign to the order all the materials you require and makes materials/spares planning
considerably easier.
For more information on maintenance orders, refer to the document PM - Maintenance Orders .
Locating malfunctions
(when using maintenance notifications)
Maintenance bills of material support you when locating malfunctions by providing you with an overview of all components that make up a technical
object. From this overview you can easily select the object for which you want to create a malfunction report. This enables you to locate the
malfunction in the technical object more precisely.
For more information on maintenance notifications, read the document PM - Maintenance Notifications.
Integration
BOMs contain important master data, which is used in many organizational areas, such as production, materials planning, product costing and maintenance.
Features
In Plant Maintenance, multi-level bills of material (BOMs) are usually used. They can have as many levels as required. The highest level in a multi-level BOM
(Level 0 in the figure below) represents a piece of equipment or a complete technical object. The lower levels of the BOM (Levels 1 and 2 in the figure below)
represent the components making up the technical object, and their components:
The BOM structure is reflected in the different technical categories of BOM provided in the PM system:
Simple BOM
PUBLIC
Page 8 of 22
The first BOM that you create for a technical object or material has no defined technical category and a simple structure. It is described as a "simple
BOM".
Variant BOM
Variant BOMs have a more complex structure. They are used to group together several BOMs to describe different objects that have a high proportion
of identical parts.
Multiple BOM
Multiple BOMs have the most complex structure. They are used to group together several BOMs to describe one object, for which different
combinations of materials are used for different production methods. Multiple BOMs are usually used in production planning and have little or no use for
plant maintenance.
For more information on multiple bills of material, refer to the document PP - Bills of Material Guide.
1.1.1.5 Additional Functions

Purpose
This component comprises the management of additional functions for pieces of equipment and functional locations.
Features
More specifically, it handles the additional functions of the following components:
Measuring Points and Counters
Warranties
Permits
1.1.1.5.1 Measuring Points and Counters (CS-IB-MC/PM-EQMSF-MPC)

Purpose
You use this component in Plant Maintenance (PM) or Customer Service (CS) to enter measurement and counter readings for
technical objects. This can be of use in the following situations:
You want to document the condition of a technical object at a particular point in time.
Documenting the condition of a particular object is of great importance in cases where detailed records regarding the correct condition have to be kept for legal
reasons. This could involve critical values recorded for environmental protection purposes, hazardous working areas that are monitored for health and safety
reasons, the condition of equipment in hospitals (intensive care units), as well as measurements of emissions and pollution for objects of all types.
You want to perform
counter-based maintenance.
Condition and counter-based maintenance tasks are forms of preventive maintenance. Generally, these tasks should reduce the number of breakdowns for
your objects.
In the case of counter-based maintenance, maintenance activities are always performed when the counter of the technical object has reached a particular
counter reading, for example, every 100 operating hours.
You want to perform
condition-based maintenance.
In the case of condition-based maintenance, maintenance activities are always performed when the measuring point of a technical object has reached a
particular state, for example, every time a brake pad has been worn away to the minimum thickness permitted.
Integration
This component is composed as follows:
You enter data manually into the R/3 System using the R/3 user interface.
You use the
Internet Application Component (IAC) to enter data in an entry screen in the browser and transfer this data to the R/3 System using the Internet.
You can enter data using a
barcode reader and transfer it to the R/3 System using the
PM-PCS interface.
The PM-PCS Interface is an interface between the R/3 System and external systems, such as a Process Control System (PCS).
You can enter data using a laptop and transfer it to the R/3 System using the PM-PCS Interface.
Data from a process control system is data that arises during the monitoring, control, regulation, and optimization of a technical process. You can
transfer this data to the R/3 System using the PM-PCS Interface.
When transferring data, you can use a SCADA System (Supervisory Control and Data Acquisition System) which filters the data from the process control
system and only transfers the data that is actually relevant to the R/3 System.
You can use the
PUBLIC
Page 9 of 22
customer exit to automate your business processes.

Overview of all Elements of the Component
Measuring Points and Counters
For more information on the maintenance planning functions in the R/3 System (for example, creating a maintenance plan, scheduling) see
Maintenance Planning.
Features
Within the R/3 components PM and CS, the component Measuring Points and Counters is divided into:
Basic functions, which are the prerequisites for using measuring points and counters
Additional functions , whose use is optional
1.1.1.5.2 Warranties (CS-AG-WA/PM-EQM-SF)

Purpose
Warranties define the scope of the services that a company performs at a technical object in the event of damage or problems.
Integration
You can assign warranties to pieces of equipment, functional locations, or serial numbers.
Features
Using this component, you can cover the following warranties from the viewpoint of the system user:
Warrantee (inbound) (for example, manufacturer or vendor warranty)
Example:
You buy a new piece of equipment and receive a warranty from the manufacturer that covers a certain period or usage (manufacturer warranty).
Guarantor (outbound) (for example, customer warranty)
Example:
You sell or lease a piece of equipment and concede a warranty to your customer.
1.1.1.5.3 Permits (CS-SE/PM-EQM-SF)

Definition
PUBLIC
Page 10 of 22
Agreement required depending on setting before an order may be released or technically completed.
Permit Status:
Condition:
Created
The permit has been created as a master record.
Deleted
The master record for the permit has been deleted.
Assigned
The permit has been assigned to either a technical object or an order.
Not relevant
The assignment of the permit to a technical object or order is currently not

effective.
Issued
The permit has been issued by an employee responsible for it.
Canceled
The permit was canceled by an employee, after it had already been issued.
Use
You can use permits to ensure that special approval must be obtained before orders are executed.
Permits can be assigned to the following objects:
Technical objects functional locations and equipment
Orders
Structure
Permits can cover the following areas:
The way the order is executed or the safety aspects involved
Safety precautions for the employees and surroundings: Providing ear protection for employees or acidproof equipment, safeguarding the work area,
installing a flame-proof zone, work clearance certificate
How the execution of an order is organized
Budget guarantee, approval of plant manager
It is therefore advisable to group permits into permit categories, for example, safety permits or work permits.
1.1.2 Preventive Maintenance

Purpose
Preventive maintenance should maintain the high availability of technical systems, for example, production plants, in the long term.
Integration
You can only use this component in conjunction with the following components:
Equipment and/or Functional Locations
Maintenance Orders
For performance-based preventive maintenance, you must also select the 'Measuring Points and Counters' component.
Features
You can use this component to:
Store activities to be performed, in the form of maintenance task lists
Define the extent of preventive maintenance and inspection work and when it should be performed at pieces of equipment and functional locations
Define the frequency of recurring maintenance and service tasks, either:
Time-based or counter-based
Time-based and counter-based
Define the cost-based assignment of preventive maintenance and inspection activities from the start
Make a cost preview of preventive maintenance and inspection work to be performed in the future
1.1.2.1 Task Lists (CS-AG/PM-PRM-TL)

PUBLIC
Page 11 of 22
Purpose
Maintenance 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. Many manufacturers deliver their technical objects together with maintenance
task lists; these task lists are, however, frequently created within the company itself.
Activities for a technical object include for example
Inspections
Maintenance
Repairs
Task lists help to reduce the maintenance effort when standardized work sequences change, for example as a result of new legal regulations. You must carry
out the changes at exactly one place in the corresponding maintenance task list. All maintenance orders and maintenance items that refer to the maintenance
task list automatically receive the actual status of the work sequences.
Integration
Using maintenance task lists, you can reduce the time required to create maintenance orders and maintenance items as you can refer back to the operations
and sequences already entered in the maintenance task list.
Moreover, you can include inspection characteristics from the Quality Management module in maintenance task lists and if necessary, include the task lists in
the test equipment management function. This is advisable, for example, if you want to keep individual data for each piece of test equipment or if you want to
have a record of the results history. For more information, see
Test Equipment Management.
Features
You can use maintenance task lists in the following areas of Plant Maintenance:
Planned maintenance
Ongoing maintenance
Maintenance task lists contain important information such as the spares and tools required for the work steps or the time required to perform the work.
Planned Maintenance
The term "Planned maintenance" includes all the maintenance work you can plan for the scope of work and deadlines, that is, inspection, maintenance and
planned repairs.
In the PM application component, you can also define the intervals at which individual work steps should be executed in the task list for planned maintenance.
You assign these task lists to a maintenance plan in maintenance planning. This ensures that only operations in the maintenance order that have been
assigned to the maintenance package due can be copied when scheduling work. The system creates maintenance orders when a maintenance plan is due.
Maintenance Planning
Ongoing Maintenance
All maintenance work that does not come under planned maintenance is classed under ongoing maintenance.
Task lists for ongoing maintenance serve as the basis for a maintenance order and can be used based on the results of the current inspection.
You can also use maintenance task lists as a model and aid for capturing data when processing maintenance orders by assigning a task list to an order. This
considerably reduces the amount of work preparation for maintenance activities.
If, for example, you are creating a maintenance order for a task whose operations have already been described in detail in a maintenance task list, enter only
this task list and the performance deadlines in the order. The system will copy the individual operations from the maintenance task list.
For further information, see
Work Scheduling with Maintenance Task Lists
Configurable Maintenance Task Lists
It is also possible to create super task lists in which you describe all possible operations for maintenance activities for different object types. According to
requirements, you can configure a suitable variant for a technical object from the super task list which means that you do not have to create your own task list
every time.
Configurable General Maintenance Task Lists
1.1.2.2 Maintenance Planning (CS-AG/PM-PRM-MP)

Purpose
Ensuring a high availability of objects in the long term is an important part of Plant Maintenance. Preventive maintenance is used to avoid system breakdowns
or the breakdown of other objects, which - in addition to the repair costs - often result in much higher costs subsequently owing to production breakdown.
There are many benefits in using preventive maintenance within your company. It is the generic term for inspections, maintenance and planned repairs, for
which the time and scope of the work can be planned in advance.
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:
PUBLIC
Page 12 of 22
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 on a regular basis.
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 for quality assurance, since, for example, the quality of products manufactured at a technical system is
substantially affected by the operating condition of the production 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.
Integration
The Maintenance Planning component is integrated with the following components and sub-components of the SAP System:
Plant Maintenance application component
Maintenance task lists
Maintenance orders
Maintenance notifications
Customer Service application component
Service orders
Service notifications
Materials Management application component
Service procurement
Service entry sheets
Quality Management application component
Inspection characteristics
Inspection lots
Sales and Distribution application component
Outline agreements
Features
You can use maintenance planning to describe the dates and scope of corrective maintenance and inspection activities at technical objects. You can ensure
that your technical objects are maintained on time and thereby function optimally.
Generation of Maintenance Call Objects
The system generates
maintenance call objects during the scheduling process. The following maintenance call objects are available in the overview:
For rough planning of tasks
Maintenance notification
Service notification
For detailed planning of tasks
Maintenance order
Service order
For detailed planning of tasks and history for the damage processed in the notification
Maintenance notification and maintenance order simultaneously
Service notification and service order simultaneously
For Customer Service
Maintenance plans with reference to an outline agreement
For Quality Management using the link to QM inspection characteristics
Inspection lots
For service procurement in purchasing
Service entry sheets
Graphical scheduling overview
List with calculated maintenance dates
PUBLIC
Page 13 of 22
Cost display for maintenance plans

Archiving of maintenance plans
Split-Level Maintenance
One of the most significant advantages offered by the Plant Maintenance application component is the option of split-level maintenance. You can create a
maintenance plan, and consequently the maintenance call objects, for example, at the following levels:
Pieces of equipment
Functional locations
Materials
Material and serial numbers
Assemblies
The possibility of split-level maintenance allows you to plan and perform maintenance tasks for the following objects:
An individual piece of equipment which operates independently of other equipment (for example, a vehicle)
Functional locations
(for example, a production line) which may comprise several pieces of equipment
You can thereby maintain the whole functional location, rather than the independent technical objects it comprises.
An assembly within a piece of equipment (for example, a pump motor)
Materials
Material and serial numbers
1.1.3 Maintenance Processing

Purpose
Maintenance processing comprises several levels, which do not necessarily all have to be implemented in full.
It is therefore possible to process a repair using many planning stages, such as preliminary costing, work scheduling, material provision, resource planning and
permits. However, it is also possible to react immediately to damage events causing production shutdown, and to produce the required orders and shop papers
with the minimum of entries in the shortest possible time.
Features
Maintenance processing can be divided into the following three areas:
Description of the object condition
The most important element in this area is the maintenance notification. This is used to describe the condition of the technical object, or to report a
malfunction at a technical object and request the damage is repaired.
Execution of maintenance tasks
The most important element in this area is the maintenance order. This is used to plan the execution of maintenance activities in detail, monitor the
progress of work and settle the costs of maintenance tasks.
Completion of maintenance tasks
The most important element in this area is the maintenance history. This is used for long-term saving of the most important maintenance data. This
data can be called up for evaluation at any time.
These elements allow you to process all the tasks that must be executed in Plant Maintenance, as well as operations which do not belong directly to Plant
Maintenance, such as investments, restructuring, modifications and so on.
PUBLIC
Page 14 of 22
1.1.3.1 Notifications (CS-CM-SN/PM-WOC-MN)

Here you can find information about notifications in the Customer Service (CS) and Plant Maintenance (PM) application components.
Service Notifications (CS-CM-SN)
Maintenance Notifications (PM-WOC-MN)
For more information about the simplified notification processing, see
Notifications (CA-NO).
1.1.3.2 Orders (CS-SE/PM-WOC-MO)

Purpose
Orders form an important part of the detailed planning of tasks and their accompanying documentation in Plant Maintenance or Customer Service.
A technician on site must execute tasks at a technical object. For this, materials, utilities and staff must be planned and costs estimated. The order supports
you with these tasks, since it primarily contains data for planning and executing tasks, which must be performed at the technical object in question.
You can also supplement them with
notifications. However, it is not necessary to use notifications in order to use orders.
Integration
The extensive functions available for orders are supplemented through integration with the following application components:
Materials Management (MM)
Representation of all the processes required for the management of parts or materials
Management of repairable spares to be refurbished
Inventory Management.
External procurement of materials and services
Purchase Requisitions and
Basic Process for Procurement of Service.
Project System (PS)

Representation of complex tasks which cover several orders and for which certain dependencies exist between the orders
Project System.
Quality Management (QM)
Automatic generation of inspection lots for the calibration inspection
Planning of Calibration Inspection.
Management of test equipment used in QM
Test Equipment Management and
Where-Used Lists and Central Replacement.
Detailed results documentation for inspections with subsequent where-used list

Results Recording.
Production Planning and Control (PP)
Provision of data about maintenance or repair activities at work centers in Production using the graphical planning board
Capacity Planning in Customer Service and Capacity Planning in Plant Maintenance.
Financial Accounting (FI)
Management of customer and vendor data
Creditor Master Data and Debitor Master Data.
Invoice creation and verification
Invoice/Credit Memo Entry and Logistics Invoice Verification.
Funds Management (FI)
Cash budget monitoring
Completion of settlement of services, operations or material, which can lead to a commitment without special account assignment
PUBLIC
Page 15 of 22
Funds Management.
Asset Accounting (FI-AA)
Direct settlement of activities which must be capitalized to the affected system
Display of the connection between business and maintenance-specific views of your system
Asset Accounting (Overview).
Controlling (CO)
Definition of settlement records for work centers
Cost Center Planning.
Settlement of orders with internal activity allocation of actual costs
Settlement.
Evaluation of maintenance tasks, for example, by cost center
Information System.
Investment Management (IM)
Detailed monitoring of accounts for complex measures
Management of budgets for all measures
Use of investment orders
Investment Management (Overview).
Personnel Management (PA)
Provision of data on the qualifications of employees, so that you can find suitable personnel for the activities required
Personnel Administration.
Workflow Management (BC-BMT-WFM)
Automatic control and editing of process flows for all jobs during the planning and execution of tasks
Maintenance and Service Orders (PM-WOC-MO/CS-SE).
The following interfaces to external systems are also available:
External System
Application Scenario
SAP Business-to-Business Procurement for material planning using external

catalogs on the Internet
From the PC, you call up catalogs, which are stored on the Internet, choose
the required materials and copy them to the order.
SAP ArchiveLink for optical storage of incoming documents
You can assign different documents (for example, photographs of damage,

the fax of a malfunction report) to the tasks and display them directly from the
SAP System at any time.
Plant Maintenance and Customer Service.
Spare parts procurement using external catalogs with user exit

EXIT_SAPLCOMK_003
From the PC, you call up spare parts catalogs, which are stored there in
electronic form, choose the required materials and copy them to the order.
Features
Functions are available in the following areas:
Specific
planning with regard to type, scope, dates and resources
Execution and monitoring of tasks
Drawing up of
rules for account assignment and settlement
Definition of budgets
Entry, assignment and
settlement of costs incurred
Technical and business
completion
Billing and Controlling for service orders
Archiving
1.1.3.3 Capacity Planning in Plant Maintenance (PM-WOC-CP)

Purpose
Capacity planning supports you in detailed work scheduling for the individual maintenance work centers (maintenance groups).
The capacities available to the work centers must be utilized as fully as possible in view of the changing daily requirements. Therefore, capacity planning can
PUBLIC
Page 16 of 22
help you in determining which work centers and individual persons are available, and help in assigning them to orders and order operations. You can use this
component to specify which work centers or persons can or should complete which activities by which date.
Integration
You can only use this component in connection with the following application components:
Maintenance Orders
(PM-WOC-MO)
Capacity Planning
(PP-CRP)
To plan persons, you also require the following application components:
Personnel Management
(PA)
Time Management
(PT)
To optimize the use of capacity planning, certain settings must be made in the system. The system administration enters the settings in Customizing for
Production Planning and Plant Maintenance.
Capacity Planning (PP-CRP), and the individual function descriptions in the unit Capacity Planning in Customer Service and Plant Maintenance.
1.1.3.4 Completion Confirmations (CS-SE-CON/PM-WOC-JC)

Purpose
You use the Completion Confirmations (PM-WOC-JC) component to document the status of the processing of a service or maintenance order.
As soon as an order has been released and the work is begun, the employees involved can enter
completion confirmations in the system.
Integration
The Completion Confirmations (PM-WOC-JC) component is integrated with the following SAP components for different functions:
Function
Integration with the R/3 Application Component
Confirmation of material used
Inventory Management (MM-IM)
Confirmation of external services and external material
Purchasing (MM-PUR)
Invoice Verification (MM-IV)
Confirmation of services
Services (MM-SRV)
Entry of general data on attendance and absence
Time Management (PT)
Entry of time and additional data in Time Management

Time collation
Features
The Completion Confirmations (PM-WOC-JC) component provides the following functions:
Time completion confirmation
Completion confirmation of material used
Completion confirmation of measurement and counter readings
Completion confirmation of installation and dismantling information
Technical completion confirmation
Completion confirmation of services
Completion confirmation of external services or external material
Cancellation of completion confirmation
Display of completion confirmations
Processing of incorrect completion confirmations
Cost determination and display of actual costs
Decoupling of completion confirmation processes
PUBLIC
Page 17 of 22
1.1.3.5 Maintenance History (PM-WOC-MH)

Purpose
When managing technical systems, you not only want to document and support the planning of maintenance processing, you also want long-term verification
documents in the form of a maintenance history.
A long-term maintenance history (PM history) is important for the following reasons:
Recording maintenance activities
For safety reasons, it must be possible to prove that the preventive maintenance and inspections requested in the past were actually performed.
Investing in replacements
The history of a technical object contains important information for investing in replacements. In addition to costs, information on breakdown behavior
and damage frequency can have a considerable influence on decisions regarding new investments.
Repetitive planning
A detailed history is highly beneficial for maintenance planning. Analyzing completed orders enables comparisons to be made between plants, technical
systems, equipment or assemblies in order that conclusions may be drawn on how to create an optimum PM strategy. For the short-term planning of
individual orders, you can refer to a similar historical order and thus considerably simplify and speed up the planning process for the current order.
Features
A good maintenance history must facilitate a differentiated analysis that is object-specific, function-related or task-oriented, and thereby provide answers to the
following questions:
At which functional locations was a particular piece of equipment installed in recent years? What was its breakdown behavior in relation to the usage
site? (object-related history)
What pieces of equipment were installed at a particular functional location in recent years? Were pieces of equipment from different manufacturers
equally well suited to this functional location? (function-related history)
At which functional locations or pieces of equipment was a particular problem or type of damage established in recent years, that was repaired by
installing a replacement material? (task-related history)
Structure of the Maintenance History
The maintenance history is structured largely automatically by the PM system. The data which will later make up the maintenance history is derived by
maintaining the master data, entering and processing maintenance notifications, scheduling maintenance plans or executing orders.
The maintenance history comprises the following sections:
Usage history for pieces of equipment at functional locations (see
The Usage History)
Notification history and technical completion confirmation documentation (see
The Notification History)
Order history (see
The Order History)
These three sections form the basis for a differentiated analysis. Object and function-related questions are answered from the usage history, and task-oriented
questions are answered from the notification and order histories.
1.1.4 Maintenance Projects

Purpose
This component enables you to do the following:
Process maintenance tasks using revisions
PUBLIC
Page 18 of 22
Process maintenance tasks using functions from the Project System (PS)
Here you can assign maintenance orders to projects and thereby include them in the project structure.
You can assign maintenance orders to the networks to obtain detailed scheduling.
Integration
You can only use this component in conjunction with the following components:
Equipment and/or Functional Locations
Maintenance Processing
Project System
If you want to perform maintenance projects by only using the revision number, you do not require the Project System application component.
1.1.4.1 Project Structure (Plant Maintenance)

Purpose
The project structure and its elements support you when structuring and planning maintenance projects. You can use this to define the content of maintenance
projects, which are already broadly structured, and assign maintenance orders to these projects. The orders are given broad scheduling data through the
project structure, and their budget can be monitored.
1.1.4.2 Networks (Plant Maintenance)

Purpose
Networks are used in Plant Maintenance to perform maintenance order operations, which are themselves part of extensive maintenance tasks, in a certain
way, in a predefined order and within a set period of time. The operations are also linked to one another by relationships and scheduled in accordance with one
another.
A relationship is the linking of the start and finish points of operations in a master recipe.
1.1.4.3 Project Management (Plant Maintenance)

Purpose
Project management in Plant Maintenance comprises the execution of maintenance orders, which are planned by means of project system functions and
processed using maintenance order management functions.
1.1.5 Information System

Purpose
The Plant Maintenance Information System can be used at a variety of levels in the decision-making process as an instrument for monitoring, controlling and
planning your business operations.
It is a flexible tool for collecting, aggregating and evaluating data from Plant Maintenance. The information system allows you to view all information in the
operative application from a wide range of perspectives. You can also define the level of detail in which you wish to see the information.
Integration
The Plant Maintenance Information System is part of the Logistics Information System (LIS) which also includes the Shop Floor Information System and
Inventory Controlling. All information systems in LIS make use of the same techniques for analyzing data and they all have the same user interface.
Use of the Plant Maintenance application component is a prerequisite for the 'Plant Maintenance Information System' component. It is also possible,
however, to include external data (for example, from non-SAP systems).
PUBLIC
Page 19 of 22
If you select the 'Plant Maintenance Information System' component while you are in the Plant Maintenance application component itself, then you do not
need to select the 'Logistics Information System' component at Logistics General level.
Features
The Plant Maintenance Information System allows you to evaluate breakdown behavior, or the maintenance tasks of a technical system or machine. It is also
possible to analyze the costs incurred or the party responsible for the maintenance tasks and the exact activities that have been performed. A wide range of
informative key figures is available for analyzing functional processes. Target criteria can be permanently controlled and transferred to tasks at an early stage.
The data is evaluated using either standard analyses or flexible analyses. Flexible planning, the Early Warning System and the Logistics Information Library
are integrated into the Plant Maintenance Information System.
Tools are available in Customizing which allow you to apply a self-defined structure to your information system and tailor it to meet your own specific
requirements.
1.1.5.1 Reporting
Purpose
The 'Reporting' component comprises the standard analyses and flexible analyses for the Plant Maintenance Information System. The standard and flexible
analyses enable you to analyze and evaluate data, which is written to the Plant Maintenance Information System.
Features
The standard analyses are based on statistical data from Plant Maintenance and provide a wide range of options for evaluating data. A wide range of functions
are available as part of the standard analyses. These functions enable you to target specific key figures and to analyze them in detail (for example, ABC
analysis, cumulative frequency curve, correlation curve, previous year comparison, planned/actual comparison, and so on). You can specify the level of detail
of information you require. The values for each list can also be viewed graphically.
Flexible analyses allow you to group together and aggregate key figures, and to create reports easily. This makes use of the functions in the Report Writer.
Different display types enable you to vary the layout of your reports.
1.1.5.2 Planning
Purpose
The planning functions of the LIS information systems are integrated into the Sales & Operations Planning (SOP) component.
Sales & Operations Planning (SOP) is a flexible planning and forecasting tool with which sales, production, and other supply chain targets can be defined on
the basis of historical, existing, and/or estimated future data. Rough planning can also determine the amounts of the capacities and other resources required to
meet these targets.
Integration
This component focuses on flexible planning.
To use SOP in a distributed environment, you also need to select Application Link Enabling (ALE).
Features
SOP features support both the high-level planning of complex planning hierarchies and the detailed planning of finished products. Therefore, both a top-down
and a bottom-up approach to planning are possible. The system can be configured either so that the target key figures defined at one organizational level are
distributed automatically and consistently to all the other organizational levels in the hierarchy, or so that each level is planned separately.
Sales & Operations Planning consists of two elements: Standard SOP and flexible planning.
The standard SOP comes largely pre-configured by SAP.
Flexible planning offers multiple options for customized settings. Planning in standard SOP is based on product group hierarchies and is always implemented
level by level. Flexible planning is made for hierarchies containing any chosen organizational levels. Moreover, in flexible planning the content and layout of
planning screens can be defined by the users.
PUBLIC
Page 20 of 22
1.1.5.3 Interface to Logistics Information Library

Purpose
The Logistics Information Library (LIL) helps you to create, classify and find key figures in the area of Logistics and is integrated in all information systems of
the Logistics Information System (LIS) as an individual menu option.
Features
The Logistics Information Library uses simple search strategies, which enable you to access all key figures in the LIS information systems. The LIL also
offers you the option of cataloging and structuring key figures.
The LIL allows you to access key figures that are not integrated in any key figure system and those that have been created specifically for your own business
purposes. The LIL enables you to integrate reports, transactions, information systems and tables from different areas of Logistics, such as Purchasing, Sales
and Production.
It is possible to search for and call up a specific key figure, without knowing the exact name of the report, the transaction code or the menu path.
1.1.5.4 Data Collection

Purpose
The 'Data Collection' component (Logistics Data Warehouse) is central to the Logistics Information System (LIS) and is integrated in all LIS information
systems.
Integration
The selection of the 'Data Collection' component is a prerequisite for using all other components in the logistics information systems.
Features
The functions for this component allow you to define and construct your own Logistics Data Warehouse. This takes place in the 'Data Collection' component
using variable data structures to satisfy the various requirements of different user groups or applications. The self-defined information structures play a key
role in this process. A variety of tools allow these structures to be filled with customer-specific data (also external data).
In addition, the 'Data Collection' component contains functions, which allow you to define the way in which statistical data from the application is written to the
information system. Update groups and update rules are also available.
1.1.5.5 Early Warning System

Purpose
The Early Warning System aids the decision-making process by enabling you to select and monitor weak points within Plant Maintenance.
Integration
The Early Warning System is integrated into the Plant Maintenance Information System. The key figures of the Plant Maintenance Information System form
the basis for the analysis.
Features
The Early Warning System allows you to search for exceptional situations and thus helps you to detect and resolve potential problems at an early stage.
You can define your own exceptional situations in the form of exceptions, as well as the conditions for subsequent follow-up processing. If an exceptional
situation occurs, then you can be informed automatically by mail or fax, for instance, or you can view the critical data in the system. The display of the critical
data is supported by various visualization techniques.
PUBLIC
Page 21 of 22
PUBLIC
Page 22 of 22

Plant Maintenance

Uploaded by

Document Information

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Plant Maintenance

Uploaded by

Copyright:

Available Formats

Overview of Plant Maintenance (PM)

PDF download from SAP Help Portal:

1 Overview of Plant Maintenance (PM)

1.1 Plant Maintenance

1.1.1 Technical Objects (CS-BD/PM-EQM)

0001, 0002, 0003

0001, 0002, 0003

Maintenance planning plant:

Plants assigned to the maintenance planning plant:

0001, 0002, 0003

0001, 0002, 0003

Maintenance planning plants:

0001, 0002, 0003

Partially Centralized Maintenance Planning

0001, 0002, 0003, 0004, 0005

0001, 0002, 0003, 0004, 0005

Maintenance planning plants:

Plants assigned to maintenance planning plant 0001:

1.1.1.1 Equipment (CS-BD/PM-EQM-FL)

1.1.1.2 Functional Locations (CS-BD/PM-EQM-FL)

1.1.1.3 Object Networking (CS-BD/PM-EQM-ON)

1.1.1.4 Maintenance Bills of Material (CS-BD/PM-EQM-BM)

1.1.1.5 Additional Functions

1.1.1.5.1 Measuring Points and Counters (CS-IB-MC/PM-EQMSF-MPC)

customer exit to automate your business processes.

1.1.1.5.2 Warranties (CS-AG-WA/PM-EQM-SF)

1.1.1.5.3 Permits (CS-SE/PM-EQM-SF)

The permit has been created as a master record.

The master record for the permit has been deleted.

The permit has been assigned to either a technical object or an order.

The assignment of the permit to a technical object or order is currently not

The permit has been issued by an employee responsible for it.

1.1.2 Preventive Maintenance

1.1.2.1 Task Lists (CS-AG/PM-PRM-TL)

1.1.2.2 Maintenance Planning (CS-AG/PM-PRM-MP)

Cost display for maintenance plans

1.1.3 Maintenance Processing

1.1.3.1 Notifications (CS-CM-SN/PM-WOC-MN)

1.1.3.2 Orders (CS-SE/PM-WOC-MO)

Basic Process for Procurement of Service.

Project System (PS)

Where-Used Lists and Central Replacement.

Detailed results documentation for inspections with subsequent where-used list

SAP Business-to-Business Procurement for material planning using external

SAP ArchiveLink for optical storage of incoming documents

You can assign different documents (for example, photographs of damage,

Spare parts procurement using external catalogs with user exit

1.1.3.3 Capacity Planning in Plant Maintenance (PM-WOC-CP)

1.1.3.4 Completion Confirmations (CS-SE-CON/PM-WOC-JC)

Integration with the R/3 Application Component

Confirmation of material used

Inventory Management (MM-IM)

Confirmation of external services and external material

Entry of general data on attendance and absence

Time Management (PT)

Entry of time and additional data in Time Management

1.1.3.5 Maintenance History (PM-WOC-MH)

1.1.4 Maintenance Projects

1.1.4.1 Project Structure (Plant Maintenance)

1.1.4.2 Networks (Plant Maintenance)

1.1.4.3 Project Management (Plant Maintenance)

1.1.5 Information System

1.1.5.3 Interface to Logistics Information Library

1.1.5.4 Data Collection