PROJECT IDENTIFICATION
Name: Date ( )
Title:
Name: Date ( )
Title:
Name: Date ( )
Title:
Contents
1 Executive Summary .............................................................................................................................................. 9
1.1 Business Process Master List ....................................................................................................................... 9
2 SAP Organizational Structure .............................................................................................................................10
2.1 Company Code ...........................................................................................................................................10
2.2 Plant ...........................................................................................................................................................10
2.3 Maintenance Planning Plant ......................................................................................................................11
2.4 Maintenance Planner Groups ....................................................................................................................11
3 Master Data .......................................................................................................................................................13
General Process Description ...................................................................................................................................13
3.1 Functional Location ....................................................................................................................................14
3.1.1 High Level System Realization Concept .............................................................................................14
3.1.2 Configuration Considerations ............................................................................................................15
3.1.3 Number Range ...................................................................................................................................15
3.1.4 Reports ...............................................................................................................................................16
3.1.5 Integration Points...............................................................................................................................17
3.2 Equipment ..................................................................................................................................................18
3.2.1 High Level System Realization Concept .............................................................................................18
3.2.2 Configuration Considerations ............................................................................................................19
3.2.3 Number Range ...................................................................................................................................20
3.2.4 Reports ...............................................................................................................................................21
3.2.5 Integration Points...............................................................................................................................21
3.3 Fleet Objects ..............................................................................................................................................22
3.3.1 High Level System Realization Concept .............................................................................................22
3.3.2 Configuration Considerations ............................................................................................................22
3.3.3 Number Range ...................................................................................................................................23
3.3.4 Reports ...............................................................................................................................................23
3.3.5 Integration Points...............................................................................................................................24
3.4 Installation and Dismantling ......................................................................................................................25
3.4.1 High Level System Realization Concept .............................................................................................25
3.4.2 Process Flow:......................................................................................................................................26
3.4.3 Assumptions .......................................................................................................................................26
3.4.4 Reports ...............................................................................................................................................27
1 Executive Summary
This document is the result of detailed study of Business Process Requirements of Health Water Bottling
Company. All the processes mentioned here will be available and can be tested during Realization
phase.
ORGANIZATIONAL STRUCTURE
ID Relevant Corresponding Explanation if necessary
Organizational unit organization
SAP (Customer…)
Company code Finance & Accounting Independent Legal Entity
Company
2.2 Plant
The plant is one of the most important organizational units. It usually represents a production unit of a
company.
The plant, at which the operational systems of a company are installed, is called the maintenance plant.
If the maintenance work is planned at this plant, Locations subdivide a maintenance plant according to
location-based
Criteria, for example, site, building, coordinates.
Global Design Decisions
Health Water Bottling CO Ltd has the following Maintenance Plants
Naming Convention
Planner Group is defined in the system by means of an three character alphanumeric key.
3 Master Data
General Process Description
Master data contains information that is needed again and again in the same way.
These master data records are utilized within transactions, such as notifications and work orders,
throughout the maintenance process. Master data records need to be complete and accurate to
receive maximum benefits from the implementation. These benefits include detailed reports for
costing, labour usage, and maintenance activity scheduling.
In HWB, Master Data objects that are needed to serve maintenance processes are:
1- Functional Locations
2- Equipments
3- Installation and dismantling of equipments
4- Fleet Objects
5- Bill of Material
6- Permits
7- Work Centres
8- Classes
9- Characteristics
10- Measuring Points & Counters
11- Catalogues
12- Task List
13- Maintenance strategy
The purpose of Master Data is to ensure that:
o The time required for managing the technical objects is reduced.
o Maintenance processing and service processing is simplified.
o The time spent entering data during maintenance processing is reduced considerably.
o More specific, thorough and faster evaluation of maintenance and service data.
Functional location is one of the most important master data objects in plant maintenance,
Functional locations are physical objects that are in a hierarchical structure and represent where
work is performed. The hierarchical structure allows maintenance activities to be performed,
tracked, cost allocated, and reported on at any level. Reporting can be detailed to one element in
the structure or as broad as necessary for the type of report required.
The aim of creating a functional location is to structure a technical system or building into units
that are relevant for Plant Maintenance.
Functional locations are used to represent the structures of the technical systems in HWB
according to functional criteria, to track all maintenance and Service tasks performed for an
individual area, to monitor the cost of maintenance and Service tasks and to analyze all usage
conditions that affect a certain area
The following sections will describe in detail:
What is Functional Location and what is its use?
How Functional Locations are mapped in HWB?
Process flow of creation or change of Functional Locations
Functional locations are physical objects that are in a hierarchical structure and represent where
work is performed. The hierarchical structure allows maintenance activities to be performed, tracked,
cost allocated, and reported on at any level. Reporting can be detailed to one element in the
structure or as broad as necessary for the type of report required. This hierarchical structure is
defined in SAP by a structure indicator.
Structure Indicator: The structure indicator of a functional location determines the structure of the
functional location label. It establishes the following factor:
Number of hierarchy levels of a technical system
Key length of the levels
Separators (hyphens)
The structure indicator consists of two input fields:
Coding template
Hierarchy levels
The coding template is used to control which characters may be used for identification (letters,
numbers, or both) and how these characters are grouped together or split.
The hierarchy levels are used to define which level ends at which character and how many hierarchy
levels the structure may contain.
When you create a functional location you have to select the category for functional location you are
creating.
Functional location category lets you differentiate functional locations according to how they are used.
Functional Location Categories to be used in HWB
o Technical System M
The coding template is used to control which characters may be used for identification (letters, numbers,
or both) and how these characters are grouped together or split. The hierarchy levels are used to define
which level ends at which character and how many hierarchy levels the structure may contain.
A functional location can be identified using a maximum of 40 characters (maximum length of the coding
template).
For HWB, it has been determined that One structure indicators will be used. The structure indicator
for HWB is comprised of eight levels.
Level 1: HWB.
Level 2: Plant (1000, 1001 …).
Level 3: the location where the equipments are installed (like Production lines)
3.1.4 Reports
No Description Module
1 Assigning Account Assignment information to Functional Controlling (CO)
Location
3.2 Equipment
A piece of equipment is an individual physical object that is to be maintained
Pieces of equipment usually represent single objects, for which maintenance tasks should be
performed and recorded.
Equipment can be installed at functional locations.
A piece of equipment can be linked with a material (if the equipment can be stored in storage
location).
Production machines, and all supported machines will be treated as equipment
Following sections will describe the following in detail:
What is Equipment and what is its use?
Types of Equipments in HWB.
Process flow of creation or change of Equipments.
The equipment master record uses the following views in the standard system:
General:
It contains fixed data, which generally does not change in the course of time, for
example, the object type, the acquisition value of the equipment, its size and
dimensions, the year of construction and the manufacturer data.
Location:
Organization:
Account assignment (for example, company code, cost center, asset number),
responsibilities (for example, maintenance planning plant, planner group, main work
center)
Structure:
This data is specified to manage equipment not only as individual object, but also
from an inventory management perspective. This data comprises material data as
well as stock
Equipment will be defined as a Material Item in the Material Management with a serial
number profile, and it will be activated from the Plant Maintenance Module as
Equipment, so any movement between the warehouse and the site will influence the
stock balance from this component by adding or issuing
There is a Key for distinguishing individual technical objects according to their use; this key is
called Equipment Category
Structuring is performed using the Equipment Category (for example, machines, fleet
objects, and Tools).
Equipment will be grouped by using Object Type which is used to divide of a technical object
for precise description and can be searched and listed accordingly.
IN HWB:
Equipment Category: M Machines
Object types:
- PRD01: BlowMoulding Machine.
- PRD02: Air Veyor.
- PRD03: Rinser Machine.
- PRD04: Filler Machine.
- PRD05: Bottle Rejector.
- PRD06: Mechanical Conveyor.
- PRD07: Labelling Machine.
- PRD08: Printer.
- PRD09: Carton Erector.
Business Process Blueprint Plant Maintenance Version 1.0 Page 19 of 78
Business Blueprint
PM – Plant Maintenance
- PRD10: Carton Printer
- PRD11: Palletizer Machine.
- PRD12: Plastic Wrapping.
- PRD13: Handle Applicator.
- PRD14: Injection/Blowing.
- PRD15: Date Printer.
- PRD16: Induction Sealer.
- PRD17: Stretch Wrapper
- PRD18: Depallatizing Machine.
- PRD19: Caps Feeder.
- INJ01 : Injection Machine.
- INJ02 : Foil Feeding Machine.
- HPR01: High compressor.
- HPR02: Cooling Tower.
- HPR03: High Air Dryer.
- LPR01: Low Compressor.
- LPR02: Low Air Dryer.
- CHILEER: Chiller.
- R.O01: Ozonated Column.
- R.O02: Storage Tank.
- R.O03: Degassifier.
- R.O04: CIP Tank.
- R.O05: Protec New R.O.#4.
- R.O06: Ozone Generator.
- R.O07: Carbon Filter Tank.
- R.O08: Sand Filter Tank.
- R.O09: Remineralization Unit.
- SUB01: Transformer.
- DEEP01: GRUNFOS Pump.
A piece of equipment must have a unique identification number; this number will be known as equipment
number.
Different Number range is defined for each equipment category.
Internal number assignment will be used for all equipment categories, means that system will
automatically generate equipment number based on the pre-defined number range
HWB equipment numbers will be presented in eight numbers and will use following number ranges:
o M: Production Machines 100000 – 199999
o T: Tools 200000 – 299999
Business Process Blueprint Plant Maintenance Version 1.0 Page 20 of 78
Business Blueprint
PM – Plant Maintenance
3.2.4 Reports
No Description Module
1 Assign Material and Material Serial Number MM
2 Assigning Cost Centres Controlling (CO)
3 Assigning fixed asset number to equipments FI
The SAP system shows a fleet object as an equipment master record with fleet-relevant data. Like
all equipments, you can also use the fleet object as a reference object for maintenance or service
tasks.
1. In HWB the term 'fleet object' includes Cars, Trucks, Van, Refrigerated Truck, and Fork Lift
In addition to the normal components of the equipment master record, the following fleet-relevant
data is available in the SAP system:
Measurement data (for example, height, width)
Transport-relevant data (for example, weight, maximum load weight, maximum load
volume)
Engine data (for example, engine type, engine power, number of revolutions per minute)
Fuel and lubrication data (for example, fuel type, oil type, calculation method)
Note: Additional function can be used with Fleet Objects (Calculating the consumption of fuel) and it
will be covered later in the section (Measuring Points and Counters)
There is a Key for distinguishing individual Fleet Objects according to their use; this key is
called Equipment Category
IN HWB:
Example:
Fleet Object Category: V
Object types:
- VEH01: Pickup.
- VEH02: Sedan.
- VEH03: Diana.
Business Process Blueprint Plant Maintenance Version 1.0 Page 22 of 78
Business Blueprint
PM – Plant Maintenance
- VEH04: Truck.
- VEH05: Mini-bus.
- VEH06: Bus.
- VEH07: Fork Lift.
3.3.4 Reports
No Description Module
1 Assigning Cost Canters to Fleet Objects Controlling (CO)
2 Assigning fixed asset numbers to Fleet Objects Financial (FI)
In HWB, Components can be installed and dismantled at main Equipments. You can monitor the
installation times for any Component from both the Equipment view and the component view.
The Fleet Object, and Equipment are linked with a material that has a serial number, so when the
damaged Fleet Object, or Equipment is dismantled, it can automatically be placed in storage.
Likewise, when the spare part is withdrawn from storage it can automatically be installed at the fleet
object.
The installation locations for any Equipment within a fleet object, or Equipment are documented in
the usage list.
As well as changes to the installation location, the usage list also documents changes to other fields
of the master record (for example, cost center, asset, and so on).
Usage list provides information about Fleet Object. Fleet Object description, valid from date, valid to
date, planning plant, functional location and superior Fleet Object
The table below displays the output from the usage list:
Object Description
Equipment Equipment Code
Description Equipment Description
Valid From Installation Date
Valid To Dismantle Date
Functional Location Old Functional Location
New Functional Location
Superior Fleet Object Old Superior Equipment
New Superior Equipment
Fatal Malfunction
Start
Happened
Create an
Equipment Need
No order for Complete the work order as normal cycle
to change
reapairing
Yes
Order Settlement
Plan the wok order
3.4.3 Assumptions
No Description Module
1 Assigning Cost Centers to technical objects (Main Controlling (CO)
Equipments- Sub-Equipment)
2 Assigning fixed asset numbers to Fleet Objects Financial (FI)
3 Assigning material number and serial number to Fleet Material
Objects Management (MM)
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.
Note:
Business Process Blueprint Plant Maintenance Version 1.0 Page 28 of 78
Business Blueprint
PM – Plant Maintenance
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. 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
Before bills of material can be defined for any module, the materials that make up the bill of
materials must first be defined, typically from the MM (Materials Management) module. Work
with those responsible for the maintenance of material records to define materials required
for BOM use.
Level 0 Car
Material Type used in maintenance BOM is ‘ERSA Spare Parts’, (for more information regarding
material types refer to HWB MM blueprint)
Operating supplies material type, will use a material group for maintenance
Item Category allows you to process data that is relevant to the individual items in a BOM. The item
category is used to control field selection, default values for BOM maintenance, triggering of specific
system activities like purchase requisition in case of the non-stock material, following item categories are
used in Maintenance Bill of Materials
o Stock Item L
o Non-stock Item N
Refer to MM blue print (procurement of consumable materials (126))
Number range for material BOM will be the same for material Type Spare parts.
Internal assignment of number ranges
No Description Module
1 Assigning Material Numbers to BOM Material Management (MM)
3.6 Permits
Permits are used to ensure that special approval must be obtained before orders are executed.
Permits are used to adhere to health and safety regulations, and control order processing.
You can select orders and technical objects according to assigned permits.
The permit can control the release of an order or the completion of an order. If it is controlling the
release of the order, the system will not allow releasing the order without issuing the permit and
same will be the cases where the permit has a control on completion.
The permits assigned to the orders are to be issued by an authorized person after checking
physical condition. One can get the list of permits pending for issue for a particular period. We
can assign multiple permits at a time to an order and these permits are to be issued by the
authorized person.
Because the term ‘permit’ covers all possible types of regulations or conditions, individual
permits are combined in logical permit categories to achieve a better overview of them
It is required to have Central Master Data Maintenance team in order to manage and maintain
the SAP PM Master Data elements. Master Data Maintenance role will be also needed at the
plant level with master data change authorization.
N/A
3.6.5 Reports
N/A
An hourly rate is maintained as a Controlling (CO) Activity type with a cost element used for
planning. The CO Activity type cost element is a loaded average of labor and/or Fleet Object
rates. Actual hourly rate charges are posted to the work order via time confirmation transactions
(IW41).
Work center data forms the basis for: cost, capacity, and target date calculation
In HWB, work center will be only one maintenance workcenter for the whole factory
The following data should be entered at work center creation:
o Costing: You can use costing to determine the costs of an internal activity
(Maintenance activity). Its goal is to assign to the various cost objects the costs
that were incurred by them. If the work center is used in an operation, the link to
the cost center provides activity types for evaluating the operation. Every work
center will be assigned to plant and cost center and one or more activity type.
o Scheduling: You can use scheduling to determine the dates when operations
should be performed. For this, the time required for the operations must be
Business Process Blueprint Plant Maintenance Version 1.0 Page 32 of 78
Business Blueprint
PM – Plant Maintenance
calculated and compared with the time available in the work center. The standard
values and quantities in the operations are used as the basis for this calculation.
During scheduling, the start and end dates for the operations are calculated from
this data using formulas, which have been entered for scheduling in the work
centers.
o Standard values: are planned values for the execution of an operation and are
maintained in the operation. Typical standard values are, for instance, set-up time
and maintenance processing time.
A control key uses the following keys and indicators to determine how an operation or a
sub operation is to be processed in a task list. Examples of such keys and indictors are:
o PM01: Plant maintenance – internal
o PM03: Plant maintenance - external (services)
Every Control Key may contain one or more of the following parameters:
o Scheduling: If you set this indicator, the system carries out scheduling for an
operation or it determines the earliest or latest dates for a sub-operation. If you do not
set this indicator, the system does not schedule the operation or sub-operation, the
system automatically sets the duration to zero.
o Capacity planning: If you set this indicator, the system creates capacity requirement
records for the operation or sub-operation. If you set this indicator for a control key,
you must also set the scheduling indicator.
o Confirmation: Use this indicator to specify whether and how the operation or sub-
operation should be confirmed.
o Costing indicator: Use this indicator to specify whether the operation or the sub-
operation should be costed.
o Time tickets: Use this indicator to specify that time tickets is printed for the operation
or sub operation.
o Print operation: Use this indicator to specify that shop papers are printed for the
operation or sub-operation.
Main work center for maintenance tasks is a Key which uniquely identifies the responsible
work center for this technical object.
Work Center category will always be (0005) Plant Maintenance.
The work center code is constrained by 8 digits and accepts alphanumeric data
A control key uses the following keys and indicators to determine how an operation or a
sub operation is to be processed in a task list. Examples of such keys and indictors are:
o PM01: Plant maintenance – internal
o PM03: Plant maintenance - external (services)
The work center code is constrained by 8 digits and accepts alphanumeric data
3.7.4 Reports
No Description Module
1 Assigning Cost Centers and Activity types to Work Centers Controlling (CO)
2 Employees and qualifications, in work centers HRMS
3.8 Characteristics
Characteristic is a property for describing and distinguishing between objects, such as length,
color, or weight
In HWB we will use characteristics to describe parameters which can't be directly added to
the technical object (Equipment, or Fleet Object):
o For Equipments characteristics will be -for example- Equipment Production Capacity.
o For Vehicles characteristics will be -for example- Gear Type, insurance expiry date.
Name of the characteristic must be stated as well as valid from date for each characteristic in
the initial view.
Basic Data view contains the following:
o Description for every characteristic will be provided.
o The characteristics group can be used to group together similar characteristics. It is used
to make finding characteristics easier
o The characteristic status: gives information on the processing status of the characteristic
(released, in preparation, or locked) and determines whether it can be used elsewhere in
the system.
o Authorization Group: for Characteristics will define whether a user is allowed to maintain
this characteristic or not.
o The data type: shows the format for entering characteristic values (Character format,
Numeric format, Date format, Time format, and Currency format).
o If you want to enter alphanumeric values, select data type CHARS
o Alphanumeric values can be up to 30 characters long.
o You can define whether upper-case and lower-case characters are interpreted as
different. If they are not, all values are automatically converted to upper case.
o Total number of characters that you can enter when you assign a value to this
characteristic can be maintained.
o Characteristics can have single or multiple values.
o You can define that a value must always be assigned to a characteristic during
classification, by setting the Entry required indicator.
N/A
3.8.4 Reports
3.9 Classes
Classification means that you assign objects to classes and use the characteristics of the
classes to describe the objects.
The aim of classification is to assign features in detail to a technical object that cannot be
assigned to the master record by using the fields of the SAP standard system.
In HWB will group the maintained characteristic (for data which are not included in technical
object data) in a class and assign this class the Equipment.
The following sections will describe the following in detail:
What are classes?
What is the use of classes in HWB?
Process flow of Creation and changing of classes
In the initial screen of classes we fill the class name and class type and valid from date
You can use the class type to find objects. The search includes all the classes of a
Class type or you can specify the characteristics that are relevant to your search and
enter values
The class type is used to define a number of parameters, such as:
o The objects that can be classified in a class
o Whether objects of different object types can be classified in the same class
o Whether an object can be classified in more than one class of the same class type
o The class maintenance screens that can be processed
Each class must be assigned to exactly one class type; in HWB we will use Fleet Object
Class Type and Equipment Class type.
In the Basic Data view , we determine:
o Description for every class should be provided.
o Valid from and valid to dates for each class should be maintained.
o Authorization groups to restrict authorizations for class maintenance, classification, and
finding objects for specific classes.
o The class group: can be used to group together similar classes. The class group is used
for finding classes quickly
o The class status: gives information on the processing status of the class (released, in
preparation, or locked) and determines whether it can be used elsewhere in the system.
In Characteristic tab: Characteristics are assigned to class and we can assign more than one
characteristic to one class. There are two assignment functions:
Business Process Blueprint Plant Maintenance Version 1.0 Page 38 of 78
Business Blueprint
PM – Plant Maintenance
o You can assign an object to one or more classes. On the initial screen of this function,
you enter the object. The same assignment function is available when you classify an
object in its master record.
o You can assign several objects to a class at the same time. On the initial screen of this
function, you enter the class.
The classification system is a central SAP component. The class type determines how classes are
processed, and how objects can be classified and retrieved in these classes
Class type used for equipment:
3.9.4 Reports
N/A
Measuring points: are physical and/or logical locations at which a particular condition is
described. They are located at technical objects (Fleet Object or Equipment)
You can use the measuring point category to distinguish between measuring point attributes
that differ from group to group.
Counters: are resources that enable you to represent the wear and tear of an object or the
consumption or reduction in its useful life, for example, the kilometer indicator of a car;
counters are located at technical objects
Counters are special type of measuring points and are represented in the system as a form
of measuring point.
Each measuring point or counter refers to a characteristic with specific measuring unit (for
example, kilometer, liter, operating hours).
Counters can run forwards, the counter readings increase, or backwards, counter readings
decrease, but in HWB we will always use forward counters.
The following sections will describe the following in detail:
What are measuring points and counters?
What is the difference between measuring points and counters?
The use of measuring points and counters in HWB
In HWB we will use fleet objects counters, for this we have to define the counters which are
used to calculate the consumption data of the vehicles, we will use:
o Fuel counter that measures Fuel Consumption,
o Primary counter (performance counter) to measure distance in Kilometers.
On the basis of the counter readings, you can calculate the average daily consumption of the
fleet object, such as the average consumption of the fuel consumed daily.
The characteristic of a measuring point or counter determines the characteristic unit in which
measurement and counter readings are entered.
Number range for counters will be internal and starts from 0000001 to 9999999
You can enter measurement or counter readings for each object to be maintained. This
makes sense if you want to document the condition of an object based on measurement
readings or if the regular maintenance of an object depends on its meter readings.
Measurement Document: is the overall term used to describe the data entered in the system
after measurement at a measuring point or after a meter reading.
A measurement document consists of the following data sections:
Number range for counters will be internal and starts from 0000001 to 9999999
3.10.4 Reports
Display S_ALR_870 You can use this report to display and, where necessary,
Measurement 13421 print out an existing measurement reading entry list. You
Reading Entry use a measurement reading entry list to put together
List measuring points and counters in a freely definable
sequence so that measurement readings can then be
entered for them. You can print out this list for the person
who will be taking the readings, so that he can write his
results on the paper version of the list.
N/A
3.11 Catalogues
Catalogues are used when maintaining notifications for the coded entry of results and
activities. Coded entry is particularly useful for analysis. There are certain standard analyses
in the Plant Maintenance Information System (PMIS), which can be used to analyze these
codes.
The following terminology will be found while creating a catalog profile:
o Catalog: Combination of code groups, grouped together according to content (For
example, damage, cause of damage, object parts, Tasks, and activities)
o Code groups: Combination of codes, grouped together according to content (For
example, damage of Dialysis machine, Blood Warmers, and Chiller unit). and so on
o Codes: Description of damage
The following sections will describe the following in detail:
What are Catalogues?
The structure of Catalogues
The different types of Catalogues
Advantages of Catalogues
Vehicle
Vehicle Vehicle Vehicle
Cause of Vehicle Parts
Tasks Activities Damages
Damages (Catalog)
(Catalog) (Catalog) (Catalog)
(Catalog)
Vehicle Vehicle
Electrical Mechanical
Damages Damages
(Code Group) (Code Group)
Advantages of Catalogues :
N/A
N/A
3.11.4 Reports
N/A
N/A
General maintenance task lists are task lists that are used for general maintenance tasks.
They do not refer to a specific technical object. Using general maintenance task lists, you
can define and manage sequences of maintenance tasks centrally, and use them for
work scheduling.
Within a group, you can create several individual general maintenance task lists. The
system automatically assigns a sequential number, the group counter, to each general
maintenance task list. This clearly identifies each general maintenance task list within the
group.
Use
You can use these task list types for both
Planned maintenance
Unplanned maintenance
Structure
Maintenance task lists (PM task lists) are grouped into task list groups. A task list group
includes all maintenance task lists with similar maintenance flows.
The task list group has more significance for general task lists, as they are called up
using the task list group number. Group numbers for general task lists can be assigned
either internally or externally. Group numbers for Fleet Object task lists and task lists for
functional locations can only be assigned internally.
The master record for the task list uses the following views:
Header Data
Operation
You can describe the individual maintenance tasks to be performed in the operations. An
operation specifies the time, work center and other control information required for the
maintenance task. You can describe how the task is to be performed in the operation
text.
In the maintenance Process, there are basically two options for assigning work to be
performed:
1- Internal Processing:
In this case maintenance tasks to be performed by the internal workshops, which
are defined in the system as maintenance work centers
The following data are required when using internal operations:
o Main Work Center: The main work center usually represents one person or a
department, responsible for ensuring that the maintenance work in an order is
executed by the work centers performing the individual operations.
o Control Key: It is a default value which defines whether the operation should be
done by internal resources or using external services by external company
o The description of the task
o Work: the total amount of man hours used for accomplishing the process
o Number of persons : the number of workers involved in this activity
2- External processing
In this case, the operation will be executed by a third party based on individual
purchase order
Sub operations
You can create sub-operations for all the operations in a maintenance task list.
Sub operation represents an additional level of detail for an operation and is
situated hierarchically below an operation. You can assign several sub-
operations to one operation this can be an advantage if several work centers are
required in one operation.
Standard configuration
3.12.4 Reports
Display Task Lists IA09 You can generate a list of maintenance task lists using
this report.
You will then receive a structured list of all the task lists
that fulfill the selection criteria you have specified.
No Description Module
01 Assign Material Components to a Task List MM
02 Assign External Service Operations to a Task List MM
03 Assign Work Centers and Activity Types to a Task List FICO
Structure
A maintenance strategy consists of:
Strategy Header
Scheduling Parameters
The scheduling parameters (for example, call horizon, shift factor) contain the scheduling
data for the respective maintenance strategy, with which you can influence the
scheduling of maintenance plans. When you create a strategy plan, the system copies
this data to the plan where you can change it.
Scheduling Indicators
Within a maintenance strategy, you can use different scheduling indicators to specify the
type of Scheduling you require:
o Time-based (for example, every 30 days)
o Time-based by key date (for example, every 30 days on the 30th day of the
month)
o Time-based by factory calendar(for example, every 30 working days)
o Performance-based (for example, every 10000 Kilometer)
Maintenance Packages
Maintenance activities that must be performed at a particular date or point in time are
combined into maintenance packages. These contain, for example, the cycle duration
and unit of measurement.
Use
In HWB the two types of maintenance strategies can be used. One will be for time based
maintenance and another will be for (Performance) counter based maintenance. The
counter based strategy consists of Distance traveled (Kilometer), etc.
Business Process Blueprint Plant Maintenance Version 1.0 Page 48 of 78
Business Blueprint
PM – Plant Maintenance
3.13.2 Configuration Considerations
N/A
3.13.4 Reports
N/A
Team
Data
Functional Work
Equipment BOM Catalogs Matetrial
location Centers
Requester/
Initiator
10.0
Start Maintenance
Notification
20.0
Create 30 100 110.0
Maintenance Emergency NO Time Enter Technical
Order YES
Confirmation Findings
Maintenance Planner
80
NO External Service 90.0 120.0
exist YES Service Entry Complete order
30.1 Sheet Technically
40.0
Plan
Release order
Maintenance
Order
Operations
, Materials, Yes
Services
Executer
40.1
Other
In operational maintenance there are two main SAP document used to manage the process:
Maintenance Notification: to report and document all malfunction history
Maintenance Order: to plan and control all maintenance activities and required resources to
execute these activities.
Process Characteristics
Process Trigger Maintenance Notification
Process Input Malfunction data
Process Output Maintenance Order
Process Owner Maintenance Department
Process Volumes
Process Frequencies Daily
4.11 Interfaces
N/A
4.12 Enhancements
N/A
4.14 Authorization
Authorizations
Data Objects
ID Authorization (Sales Order / TA Reason # of employees
code)
Plan the work
order
Release the work
order
Follow up
929- Maintenance
Maintennace Planner Activities
A001
Completion
Confirmation
Technical
Completion of
Order
Team
Data
Functional
Equipment BOM Catalogs Task List
Location
10.0 20.0
Review Maintenance Is Maintenance Frequency
Start
Requirements (Internal & different for various
External) operations
20.1 20.2
Create Strategy based Yes No Create Single Cycle
maintenance plan Maintenance plan
Maintenance Planner /
Fleet controller
30.0
Schedule Maintenance Plan
End No
50.0
40.0
120.0 Yes Automatic Creation of maintenance
Call date falls on run
Complete the order and the work order
date
notification
110.0
Enter Technical findings
60.0
The work order is planned
100.0 automatically
Confirm the work order
Yes
Maintenance
80.0
Executer
90.0 Execute
70.0
All Activities are Maintenance
Print Maintenance Order
Completed? order
No
Team
Data
Functional
Equipment BOM Catalogs Task List
Location
10.0 20.0
Review Maintenance Is Maintenance Frequency
Start
Requirements (Internal & different for various
External) operations
20.1 20.2
Create Strategy based Yes No Create Single Cycle
maintenance plan Maintenance plan
Maintenance Planner /
Fleet controller
30.0 Measure
Schedule Maintenance Plan Document
End No
40.0 50.0
120.0 Targeted counter Yes Automatic Creation of maintenance
Complete the order and the reading reached on work order
notification run date
110.0
Enter Technical findings
60.0
The work order is planned
automatically
100.0
Confirm the work order
Yes
Maintenance
Executer
90.0
80.0 70.0
All Activities are
Execute Maintenance order Print Maintenance Order
Completed?
No
Performance based
o Single counter plan
o Strategy counter plan
Multiple-counter plan
A maintenance plan will be created for individual equipment which operates independently of other
equipment or for a Functional location which may comprise several pieces of equipment.
Pre-defined task lists can be attached to maintenance plans, which will be consisting of the operations to
be carried out at the time of maintenance plan execution.
Process Characteristics
Process Trigger Call date/target measure document
Process Input Measure document
Process Output Preventive Maintenance order
Process Owner Maintenance department
Process Frequencies As per the Plan
Business Process Blueprint Plant Maintenance Version 1.0 Page 60 of 78
Business Blueprint
PM – Plant Maintenance
5.11 Interfaces
N/A
5.12 Enhancements
N/A
5.14 Authorization
Authorizations
Data Objects
ID Authorization Reason # of employees
(Process Step)
Maintenance Planner Create Maintenance Strategies
Create Maintenance Plan
Create Measurement
documents
Schedule Maintenance Plans
Background Scheduling of
930-
A001 Maintenance Plan
Usage Decision for closing the
Inspection
Completion Confirmation
Technical Completion of Order
(TECO)
(Requester) Team
Data
Serial Material
Equipment BOM Permits
number Number
10.0
Initiator
Request for
Start
Refurbishment
Maintenance
20.2
20.0 No Subcontracting
Internal Processing Cycle
Maintenance Planner
YES
20.1 40.0
30.0 80.0 90.0
Create Release
Refurbishment Confirm work Complete the
Refurbishment Refurbishment
Order Planning Order order
Order Order
No
Executer
50.0 YES
60.0 70.0
Print
Order All Activities are
Maintenance
Execution Completed?
order
Departments
110.0
MM Goods MM Goods CO Order
Order Close
Issue Receipt Settlement
In case of external processing for refurbishment maintenance Subcontracting process will be used as
shown in the next process
Process Characteristics
Process Trigger Many defective parts need to be repair
Process Input Refurbishment order
Process Output Refurbishment order
Process Owner Maintenance department
Process Volumes
Process Frequencies Upon request
6.11 Interfaces
N/A
6.12 Enhancements
N/A
6.14 Authorization
Authorizations
Data Objects
ID Authorization (Sales Order / TA Reason # of employees
code)
Maintenance Planner Plan the work
order
Release the work
order
Follow up
Maintenance
887- Activities
A001
Completion
Confirmation
Technical
Completion of
Order
Subcontracting Maintenance
Role Process
Notification Master
(Requester) Team
Data
Serial Material
Equipment BOM Permits
number Number
10.0
Initiator
Request for
Start
Refurbishment
Maintenance
20.2
20.0
YES Refurbishment
Internal Processing
Maintenance Planner
Cycle
NO
60.0 100.0
70.0 80.0 120.0
Other
90.0
Execution by
Subcontractor
Process Characteristics
Process Trigger Many defective parts need to be repaired externally
Process Input Refurbishment order
Process Output Refurbishment order
Process Owner Maintenance department
Process Volumes
Process Frequencies Upon request
7.11 Interfaces
N/A
7.12 Enhancements
N/A
7.14 Authorization
Authorizations
Data Objects
ID Authorization (Sales Order / TA Reason # of employees
code)
Maintenance Planner Plan the work
order
Release the work
order
Follow up
ZPM1- Maintenance
A001 Activities
Completion
Confirmation
Technical
Completion of
Order