FreeOCR Notes

FreeOCR notes
1) For best results set your scanner to 300 DPI , 200 DPI is the minimum setting to achieve acceptable
results.
2) Use the rotate buttons (to the left of the image) if your image is upside down or rotated
3) If your document has columns or pictures then just select the text area by drawing a box on the image
with the left mouse button
4) After OCR you can use the export button to Word or copy/paste the text into any Windows
application.
Note: You can press the red X to clear this text window before OCR'ing
. ._ , ,/1
\__>,"-is S aLmg\_|;.lAU.u
K'T V35 Q .,.a,.i.,..;.......,.;.,
_ CORRECTIVE MAINTENANCE
BUSINESS PROCESS. (TP_EAM_O3)
_ ESTDAMA NAQEL/
DIVISION" TRANSMISSION POWER
Condential DEWA_SAP_WAVE-3_Tra.nsrnissi0n_EAM_B1ueprint_C0rrective Maintenence_Final_V1.l
(TP-EAM-03) Page 1 of 77
-_ i
KPIT Vesta ,
Table of Contents
oo\1_o~ul.:>w|\>-
>\oooo\u\ul-|>
. Document Control ............................................................................... ..
. RACI Record ........
. Submission Record
Conrmation Record..............
. As-Is Document Reference........ ............................................................... ..
Overview
. Module Overview.........
. Assumptions ................................................................................... ..l2
9. Glossary................. ......13
10. B1ueprintMeetings........................................ ......15
11. Business Process: Corrective Maintenance .......................................................................... ..16
11.1 Corrective Notication ......l7
l1.2Corrective Work ......l8
11.3 Operational Account Assignment and Inspection Rounds .................................... ..
11.3.1 Operational Account Assignment
11.3.2 Inspections Rounds Functionality ..........
12. Business Process Flow Diagram ......................................................... ..
12.1 Process: Corrective Maintenance Notication ...............
12.1.1 Process Steps: Corrective Maintenance Notication........
12.2 Process: Corrective Maintenance Work Order ..................... ..
12.2.1 Process Steps: Corrective Maintenance Work Order........
12.3Process: Non-WCM Planning ............................
12.3.1 Process Steps: Non-WCM Plarming .............
13. Business Process Design Details and Information ............ ..38
13.1 Corrective Notication .........................
13.1.1 Notication Design Details ........... ..
13.1.2 Conguration ........ ............ ..39
13.1.3 NoticationCatalogs.......
13.2Work Order .................................... ..
13.2.1 Design Details Infonnation....... ......................... ..48
13.2.2 Conguration ............
14. Process Issues (As-ls) ....... ..
15. Process Requirements...... ......................................... ..60
16. Guiding Principles ......................................... ..61
Condential DEWA_SAP_WAVE-3_Transmission_EAM_B1ueprint__Corrective Maintenence_Final_Vl .1
(TP-EAM03) Page 2 of 77
~<
I<I=""' Vem J
17. Process Assumptions................. .
18. ProcessTerminology.................
19. Process Results and Benets.........
20. RICEFW Summary....................
21. Reports ................. ..................................................................................................... ..66
21.1 SAP Standard Reports
2l.2Repo11 Requirements............................
21.3 Management Reports & Dashboards ..............................
2l.4Reports, Management Reports & Dashboards FIT GAP
22. Data Consideration .........................................................
23. Organizational Impact
7.4. Process Decision Records..........
25. Integration Test Requirements ....................................................................................
26. Issues ...................
27. Next Steps/Actions
28. References ........ .......75
29. Functional Gaps........ .......76
30. Roles ................. .......76
31. Risk ............................. .......77
32. Additional Information....... .......77
Condential DEWA_SAP_WAVE-3_Transmission_EAM_Blueprint_Corrective Maintenence4Final_Vl .1
KPIT Vesta I
1. Document Control
Item I Description
Document Title: I Work Management - Corrective Maintenance
Classication: I o Public I o Intemal I @ Condential I o Highly Condential
Status: I Final I Type: I SAP Implementation
Publish Date: I 02/03/2015
Revision Date: I
Version No. I Date I Author(s)
Remarks
V0.1
I 05/11//2014
I Axjan van der Hout
I
I First Draft
V0.2
| 12/11/2014
I Arjan van der Hout
Input DA incorporated
V0.3
I 12/11/2014
I Axj an van der Hout
Input DA incorporated
V0.4
I 17/11/2014
I Arjan van der Hout
Reviewed by Kevin
V0.5
I 19/11/2014
Aljan van der Hout
I Reviewed by DEWA IT
V0.6
I 26/11/2014
I Alj an van der Hout
I Informal Released
V04
I 01/03/2015
I Kevin Heard
I Fourth Draft submitted to Business
V1.1
I 02/03/2015
I Kevin Heard
Final , added changes on remarks Business 3
march
Version No.
Date
I Reviewer(s)
Remarks
V.03
12/11/2014
I Amir Shalish
V.O3
I 12/11/2014
I Len Harms
V.03
| 12/11/2014
I Jos Nederveen
Version N 0.
I Date
I Agprover(s)
Remarks
V01
I 17/11/2014
I DEWA Transmission Power
V02
I 08/01/2015
Reworked based on TP comments 15-12-
I
I Informal draft.
I 2014 and comment review sessions.
V03
I 19/01/2015
I Reworked layout adjustment.
V03
I 06/02/2015
I Reworked based on TP comments 03-02-
Z0 l 5.
V03
I 12/02/2015
I BBP Walk-through with Core Team.
V04
I 02/03/2015
I BBP Walk-through with Core Team.
Condential DEWA_SAP_WAVE-3_Transmission_EAM_Blueprint_Correetive Maintenence_Final_Vl .1
KPIT vesra
2. RACI Record
RACI Record names acceptance authority of the function owners. Personnel in the various categories
remain committal
to their roles in conrmation of the function in its entirety.
RACI Category Name Designation Department Signature / Date
Responsible
Accountable
Consultant
I Information
3. Submission Record
Provides connnation from the Implementer on their understanding of the proposed functional scope
vis-a-vis current
practice / requirement.
Team Details
Name
Designation
Signature Date
Implementer:
Functional
Consultant
Kevin Heard
EAM Consultant
@7/~
I / /'
ON ghbwei/,4 3 '3l '
(w/+<,-1 294)
KPIT Project
| Manager
J os Nederveen
Project Manager
1
Z"
Business
Project
Manager
Ashraf Ahmad
Manager -
Transmission Asset
Management
/
R
IT Project
Manager
Haitham Khalifa
Project Manager 0 lb
Condential DEWA_SAP_WAVE-3_Transmission_EAM_Blueprint_Corrective Maintenence_Final_Vl .l
(TP-EAM-O3) Page 5 of 77
KPIT Vesta -J
4. Conrmation Record
Record concurrence of the Project Drivers and Project Facilitators involved in the study and
documentation of requirements
for the proposed function / process. Any Remark below should be considered a part of the process /
.ll1CliOl'l / documentation
and is to be treated as mandatory. Clearance om the Project Steering Committee shall be considered as
nal connnation
of the document.
Team Details
Name
Designation
Signature Date
MARYAM KHAMIS
SALMIN
Senior Engineer -
Transmission Asset
Management
(Transformer)
is
\Z rt. 206
RAAFAT MOHAMED
AHMED SARHAN
Manager - Transmission
Asset Management
(Transformer)
ll
/Z~/~Z5
AM] AD AHMAD
SALEM AL-BLEWI
Manager -Transmission.
Asset Management (OHL)
Q
/~r-./._'\
MAGDY ABDELSALAM
OSMAN ISMAIL
Dy. Manager.-Oil Lab
AHMED IKHTIER
ALAM
Engineer-Transmission
Asset Management (swgr)
@Z~__1,,__ <1-Q. (9
ASHISH GEORGE
ELLENGICAL
Senior Engineer-
Transmission Asset
Management
(Transformer)
VENKATA RAMANAN
RAMA DASS
Engineer-Transmission
Asset Management
(Cables)
\
$1
)4/Z I3/1-Ll-//1;
HUSSAM ISMAIL
Manager-
Transmission Equipment
"5; )___ l-2/<<//3
SHAMSA ALMEHAIRI
Manager-
Transmission Equipment
'Z>
MOHAMED ABDEL
AAL ALI FARAHAT
Manager- Transmission
Asset Management
(Cables)
MOHD HU S SAIN
SHAHUL HAMEED
Senior Engineer-
Transmission Line P
atrol
\"*\
Condential DEWA_SAP_WAVE-3_Transmission_EAM_Blueprint_Corrective Maintenenee_FinaI_Vl .1
KPIT vesta -J
NOWSHAD TAJUDEEN
SAINABA
Assistant Engineer-
Transmission line (NOC)
/M/L
/6 /+/aw/F
RENATO ORLINA
PADILLA
Assistant Manager-
Transmission Line
Maintenance OH L
TAMER SALAH ABD
ELSAMIE HASSA
Senior Engineer
Transmission Line
Maintenance Cable
%/
L% /7!/Q//1)/'
/Z
1 2,/Lu Z015
ASHRAF MAHMOUD
JOUDA
Assistant Manager Civil
Maintenance Department
%%"
12/L///s
F IRAS ABU AL HASAN
Asst. Manager-
Transmission Operation
~;=%
:2 Aw L;>i5
OSAMA TEAIMA
Senior Engineer -
Transmission Protection
IQ, Li- 15
WAIS MAHMOOD
Specialist distribution
SCADA project
";_
1% *
S
4
.20--i-I5
AB_ID HUSSAIN BAIG
Engineer-SCADA Asset
Management
if
14/ M] 1.:/f
KHOLOUD SAMARA
Engineer SCADA Asset
Management
-C J
it
/-/'* >
'-1 I ii 1,;
TP Departments
Head
Mo i')aMe,i A |,</mi
Transmission Operations
KHALIFA ALMEHAIRI
Act:/zj \/inc f3'elidr;il
Vice President
Transmission Maintenance
ZX/>\
ALI ALAWAZI
Vice President -
Transmission Protection
/,,, Z4:-"'
2/1//K
Abdulla Bel Ghuzooz
Actg. Vice President-
SCADA Network
/ Qzltqis
Business Project
Manager
Ashraf Khaled Ahmad
Manager - Transmission
Asset Management (swgr)
%s.;.
$13/ls
EVP-TP
Hussain Essa Lootah
EVP - Transmission Power
L_%_/55>
2/7+?
Condential DEWA_SAP_WAVE-3_Transmissi0n_EAM_Blueprint__C0rrective Maintenence_Final_Vl .1
1<=-IT vwa Eff?

J
ITD Team / KPIT Team
Designation
Name Signature Date
Acting CIO
Y9
Moza AlAkraf \
Senior Manager -
Projects & KAM
Hatem Mohamed AlShafei
@
Deputy Senior
Manager - Projects
. /V
Abeer AlSharaf % 5. /Z/101.;
IT Applications
Support
f15>t~.al.m;-.A.<#.~/\1 -51.<t 4,
SharafPillai "' ~ *
IT Project Manager
&,{,,,,, A9 . '9/'c3~P1~\!
\h7@i-~/ii-*--X"1 rt /W we
Haitham Khalifa
KPIT Project
Manager
Z ,~
J os Nederveen
Design Authority
Len Hanns
\. W H
QQN \\ \'~a\ . t/v\'?_0lS
'\\
girl A \t'\MZMS
Amir Shalish
QV\
\.
ISO 55000
Michael Kuijl
Q\t\
\.
",\'\\'\\/t 106
\
Remarks
Insert any assumptions or constraints or limitations or concerns for the project.
5. As-Is Document R
eference
Provide reference to
description or indicat
current process study document pertaining to this business process. Include the AS-l S process
e the document reference number.
Sln
I Document Reference
. . Enclosed
Description I (Y/N)
l
Processing of TOD NOD process Y
Transmission Real
Time Raised NODs(
GQP-52)
2
Management of NODs TAM Management of NODs
j
IPT
I
W I Permit To Work process
I3
4
ala
Procedure for attending Flow chart to attend alarms in 400/132 KV substations
-<1
THIS Rev2
Condential
DEWA_SAP_WAVE-3_Transmission_EAM_Blueprint_C0rrective Maintenence_Final_Vl .1 (TP-EAM03)
Page 8 of 7'7
/<=-I-r v-ma E7157 J

6. Overview
This document will list the design decisions resulting from the Blueprint phase of the SAP EAM Project
for DEWA. It will
become the User Acceptance document at the end of the Blueprint phase, and will be added to during
the Realization phase
of the project as additional design decisions and renements are made.
This project will focus on implementing SAP EAM and PS/PPM for the following Divisions; Generation,
Transmission
Power, Water and Civil, Business Support and BPC for Finance.
SAPs Document Management module will also be included in this project. It will be used to store
information currently
held in the Key File document management system, Vendors Equipment data, Instrument Calibration
and Work Process
data.
Enteggrise Asset Management:
Asset Management is, as dened by the ISO 55000, the coordinated activity of an organization to realize
value from
assets. SAP Enterprise Asset Management (EAM) enables organizations in capital-intensive industries to
manage all
phases of the asset life cycle. For physical assets a large part of these coordinated activities consist of
Maintenance
Activities. A separation can be made between planned activities triggered by a Maintenance Plan with a
certain Strategy
and unplanned or ad hoc activities:
Unplanned Maintenance 0 Corrective Maintenance
o Breakdown Maintenance
0 Functional Failure
0 Emergency/UrgentMaintenance
I Refurbishment
0 Project Repairs/Maintenance
Planned Maintenance 0 Preventive Maintenance
0 Periodic Maintenance
o Performance/Usage-based Maintenance
Inspections
Calibration
Condition-based Maintenance
OOO
Blueprint - Corrective Maintenance:
This document describes the SAP Enterprise Asset Management conguration and design for the DEWA
Transmission
Power Corrective Maintenance Process.
The design is the outcome of the:
v As-Is Discovery
v To-Be Requirement analysis for Enterprise Asset Management
0 Blueprint Workshops
0 L2 Training
Condential DEWA_SAP_WAVE-3_Transmission_EAM_BIueprint_Corrective Maintenence_Final_V1 .1
KPIT Vesta Q
The following topics, which are part of the Corrective Maintenance Process, will be dened in separate
specic Blueprint
documents:
0 Multi Resource Scheduling (MRS)
0 Work Clearance Management (WCM)
0 Reporting
Scope of work related to Corrective Maintenance (as per written contractual agreement between DEWA
and KPIT) is as
follows:
v Business Blueprint
0 Conguration
I Testing
0 Training
I Reports
0 Interfaces
0 Forms
0 Enhancements
0 Data Conversion
0 Document Management
Condential DEWA_SAP_WAVE~3_Transmission_EAM_Blueprint_Con'ective Maintenence_Final_Vl 41
(TP-EAM~03) Page 10 of 77
{pig l _;" \
.~.....;-3;:e.... KPIT vesra ,
7. Module Overview
SAP Enterprise Asset Management (EAM) enables organizations in capital-intensive industries to
manage all phases of
the asset life cycle. For physical assets, a large part of these coordinated activities consist of
Maintenance Activities. The
following gure presents the Maintenance Process from a SAP Object perspective.
Figure 7-1-SAP EAM Object Overview
Tscrnczl Otqectzf F-E511"-(E
THSRLBI
. F flf 5|
Wot
Demlr
Cahgslmkj
Notification Order
Corrective Maintenance Orders are identied by a Notication.
Preventive Maintenance Orders are triggered by a Preventive Maintenance Plan. A Condition-based
Maintenance Plan is
connected to Measurement and Counter readings. Both the Notication and Order are connected to the
Functional
Location and the Technical Object (Equipment) at which the Maintenance Activity is performed.
The EAM module provides one integrated system for all Maintenance related data which includes
Assets, Work load,
Work Center availability, Work Clearance Management, Work Permits and Materials Management.
Condential DEWA_SAP_WAVE-3Transmission_EAM_Blueprint_Corrective Maintenence_Final_V1.l
(TPEAM03) Page ll of 77
I<=-IT vesra id
8. Assumptions
The following assumptions are considered for this implementation:
0 Materials Management was previously implemented in SAP and fully utilized by each DEWA Division.
The
Logistics Plant is already in place.
I Finance and Controlling Modules were previously implemented in SAP and fully utilized by each DEWA
Division to control and assist with nancial reporting.
I For the relevant Equipment, Asset Accounting has been implemented in SAP.
Condential DEWA_SAP_WAVE-3_Transmission_EAM_B1ueprint_Corrective Maintenence_Final_Vl .1
Krrl-r Vesta W ,,,_,.t..,.u,..a..l..

9. Glossary
Following are the key technical tenns used in the document:
Term
Description
Notication
Document used to identify the need for some fonn of Maintenance intervention e.g.
Inspection or Repair. It is also the place to capture Maintenance history related to
inspection & repairs (Condition Reports).
Work Order
Document used to plan work activities and resources.. Material and Service
procurement requirements are originated from Work Order. Labor work plans are the
basis for scheduling work. Actual labor hours are captured by Work Order. Used to
plan costs and track actual expenditures
| Work Order Operation
Sub level within a Work Order where tasks / activities are planned. All resource plans
(labor, service and materials) are created at the operation level.
Operational Account
Assignment (OAA)
Operational Account assignment allows to use the Operation of a Plant Maintenance
Order as an Account Assignment Object. This permits the detailed planning, capture
and reporting of costs at the Order operation level. Normal Order costs are posted at
Order header level. The operations have their own settlement rules enabling more
accurate cost updating of multiple assets maintained using a single Order.
Control Key
Controls how an operation in SAP is processed in terms of planning, scheduling,
procurement and time capture (connnation).
Work Center
SAP Object used to manage and schedule resources used in Maintenance execution.
Specic employee records as stored in HR module can be assigned.
System Status
SAP dened statuses, which both control processing and provide information
User Status
Company dened Statuses used to meet the specic control and authorization
requirements of the business.
Cost Center
This Entity in a controlling area representing a unique, limited area in which costs may
arise or responsibility for costs may rest. The division into cost areas may be perfonned
on the basis of various considerations, including activities, responsibility, physical
location, etc.
Activity Type
The activity type divides the specic activities produced in a cost center according to
how costs are to be distributed. One or more activities may be allocated to a cost center.
Generally, activities are stated in man-hours, production hours, machinery hours, or
number of produced entities.
Work Clearance
Management (WCM)
Work Clearance Management is the SAP model to control and monitor the safety
measures and is used within Maintenance Order
Technical Completion
Technical Conrmation is the Status given to Order once all work dened in
Maintenance Order is completed and Order is ready for settlement.
Business Completion
Business Completion is the Status given to an Order when the Order is fully settled
and no more Goods movements or Financial postings are required.
Time Confirmation
Time Conrmation means booking the actual execution time against each Operation
and Work Center.
Condential DEWA_SAP_WAVE3_Transmission_EAM_Blueprint_C0rrective Maintenence_Final_Vl.l
(TPEAM-03) Page I3 of 77
J. . _ t
1<=-IT v-=5 E17 Q
Term I Description
Order Settlement The Process used to transfer the cost that arises from processing an Order is
transferred from Maintenance Order to cost receiver in the case of Refurbishment it
would be to the Material itself.
Condential DEWA_SAP_WAVE-3_Transmission_EAM_Blueprint_Corrective Maimenence_Final_Vl .1
KPIT Vesta W J
10. Blueprint Meetings
The following users have attended the business blueprints meetings and contributed to the nal
solution documented in
this document.
Phase
Date Attendees
Quick Summary
Notication
01-07-2014 Core Team
1 1-08-2014 EAM Team
Introduction to Work Management
and denition of the To-Be
Notication Process based on the As-
ls situation.
Work
Order
1 1-08-2014 Core Team
26-08-2014 EAM Team
Denition of the To-Be Work Order
Process based on the As-Is situation.
' JMS
16-07-2013 EAM Team
Operations Team
Overview of the As-Is JMS system.
Scheduling
08-O9-2014 Core Team
ll-09-2014 EAM Team
Introduction to Scheduling and
denition of the To-Be Scheduling
Process based on the As-Is situation.
Condential DEWA_SAl_WAVE-3_Transmission_EAM_Blueprint_Corrective Maintenence_Final_Vl.] (TP-
EAM-03) Page 15 of 77
.~':i'_\..;_~Q ,, /
KID T Vesta 1 ~
11. Business Process: Corrective Maintenance
Corrective Maintenance encompasses all activities that are performed after a fault or problem emerges
in a system or
operation, with the goal of restoring and sustaining the mctionality of the system. In some cases, it can
be impossible to
predict or prevent a failure, making this type of maintenance the only option. In other situations
Corrective Maintenance
can be dened as preferred Maintenance Strategy above Preventive Maintenance.
The Corrective Maintenance process is initiated when a fault or malfunction occurs. The fault may be
initiated by the
SCADA system or manually identied by the operators or by Maintenance personnel. Corrective
maintenance can be
subdivided into "immediate corrective maintenance" (in which work starts immediately after a failure)
and "deferred
corrective maintenance" (in which work is delayed in confonnance to a given set of maintenance rules).
The Corrective Maintenance process follows the activities of the general Maintenance Work
Management process, which
consist of the following steps, commonly referred to IPSECA:
0 Identify
0 Plan
0 Schedule
0 Execute
0 Complete
Q Analyze
The gure below visually presents the utilization of SAP Objects in the different stages of the Work
Management process
of Corrective Maintenance. The utilization of two main SAP Objects are distinct:
l. Notication ~ coloured in green
2. Order coloured in blue
3. Pennits colured in orange
Figure 11.1-Work Management and SAP Objects
"Wont Managsnent
Identity Plan Schedule Execute Complete
A"__
wen owe: -:a:ee
- W041)" .,
- ieveore
wall Om! -\Jem0mer 1-c"mmL ,"TDRy
Qllblo
opammza
Ooembni
LT , - won: Omar
EE,
E
Condential DEWA_SAP_WAVE-3_Transmission_EAM_Blueprint_Corrective Maintenence__FinaI_V1.1
(TP-EAM-03) Page l6 of 77
re n Ii
TIVIECIJI1.
is Ill
omq
_;~< _ .. H /P
KPIT vem EI-C7 J
11.1 Corrective Notication
The Notication serves as both the starting point and the ending point of the Work Management cycle
for Corrective
Maintenance. The Notication has two purposes:
Identification
All defects and abnormal events are identied and reported in SAP by a
SAP Notication. The Notication requests the specic maintenance
department to perform a Maintenance task and holds the necessary
information to effectively and efficiently prioritize the Maintenance work.
This mandatory information includes:
0 Description of the exceptional technical condition or problem
0 The object or asset
0 Priority and required start/end dates
0 The person who reported the problem
0 Responsible Planner Group
0 Work Center to perform the work
0 The responsible Maintenance Department to perform the work
0 Breakdown Indicator if required
Complete and Analyze
After the work is executed, the detailed work history is added to the
Notication in the Complete stage of the Work Management process. The
6 history can be used for (Failure) reporting and analysis.
Analyze
Important reporting elds include:
0 Malfunction/Breakdown
0 Start and End time of Down time
0 Actual Repair Duration (MTTR) for Parent Functional Failures
0 RCM Catalogs
o Object Parts involved
o Failure Mode
Failure Cause
Performed Maintenance Activities
5.
Complete
OO
Set Notication Status Complete
The Maintenance Notication needs to be put in the Complete Status as
soon as possible, after the work has been completed. Notications cannot
be edited while in the Complete Status. The Notication completion can
be reversed back to a Status of Notication in Process".
The following elds are the primary elds found on the Maintenance Notication:
Condential DEWA_SAP_WAVE3_Transmission_EAM_Blueprint_C0rrective Maintenence_FinalfV1 .1
(TP-EAM-03) Page l7 of 77
.<; . ~-
KPH" vesra he
Figure 11.1.1-Notzcatinn Fields
> Date I time I reported by
Notification > De$|iPti"
> Object: Functional location
Equipment
Assembly
Material serial number
> Location data
> Breakdown I availability
N H. t. Damage location
is itgngca '0" > Damage
_ Cause of damage
. .. > Activity
Actwmes > Execution factors
Dates
Tasks Task description

11.2 Corrective Work Order
When Corrective Maintenance work has been identied, the Notication provides the basis for the work
Order. The Work
Order is used to Plan, Schedule and manage the execution of the Maintenance activities and to plan cost
and track actual
expenditures.
The Work Order has the following functions:
Condential DEWA_SAP_WAVE~3_Transmission_EAM_Blueprint_C0rrective Maintenence_Final_Vl.l
(TPEAM-03) Page 18 of 77
KPIT Vesta J
Plan
The Tasks/Activities are planned within a Work Order Operation. All
resource plans (Labor, Services and Materials) are created at the
Operation level.
0 lnternal\ External labor
\/ Work is planned for a Work Center
\/ The Planned Activity Type rate is used to calculate the planed
costs (Hrs*AED)
~/ The Control Key denes that the work is for internal or extemal
processing
0 Stock Material/Non-stock Material
~/ Material request originates from a Work Order
/ Stock item can be reserved
A Purchase Requisition can be created for Non-stock items
Either a Purchase Requisition or Reservation can be created
~ Tools
\/ The resources required to perform the job tasks are identied and
planned on the Work Order.
0 In the planning step, the Work Clearance Management Objects
are planned and linked to the Work Order. The WCM design
details are presented in a separate Blueprint document.
\\
Schedule
Scheduling relates to when the planned activities are to be carried out. It
involves the setting of a time table for carrying out the work and
analyzing work demand with respect to resource availability, taking the
availability of spares and materials into account. The Work Order
Operations form the key component of this sub-process.
The objectives of Scheduling are:
0 It eliminates waiting for spares and resources
0 Assures correct skills to be allocated to tasks
0 Optimizes resources utilization
0 High and Low peaks can be managed
In order to reach these objectives it is necessary to Plan and Schedule
work in advance. A weekly plan is created and adjusted on a day-to-day
basis to gather on the actual resource availability, Outage schedules,
Emergency work, Equipment availability and Backlog. The Scheduling
process is dened in a separate Multi Resource Scheduling Blueprint
document.
Condential DEWA_SAP_WAVE-3_Transmission_EAM_Blueprint_Corrective Maintenence_FinaI_Vl .1
1<:==1T vesta E7 .)
Execute Work
This process step covers the execution of maintenance work to ensure that
it is carried out safely, efciently and effectively to specication.
0 It is the stage where, having received the package of work
instructions and technical information associated with the
Maintenance Orders, the work crews actually do the work.
~ Requirements/Expectations
/ Jobs are executed to plan.
~/ Shop Papers will be provided with specication of work &
for feedback purposes.
\/ Minimal delays in execution of work.
/ Compliance with safe working instructions &/or procedures.
/ Work completed to specication
I Deviations that occur during execution must be reported to the
Maintenance Scheduler and/or Planner. The mentioned deviations
must be analyzed and whatever additional Resources and/or
Materials/ Spares required to complete the job; must be requested.
Complete
The feedback of information is crucial for updating both PM Notications
and PM Work Orders to ensure that accurate historical data is captured for
Technical Objects. This includes both Labor and Materials used in tasks.
This feedback must be captured accurately on a daily basis to ensure that
the data on-hand is reliable and valuable in the decision making process.
Record Completion Conrmation
A completion conrmation documents the actual status of the processing
of Operations and Sub-operations for a Maintenance or Service Order. A
conrmation holds:
0 Work Center and the employees who performed the Operation
v When the work was started and when it was completed
0 The actual hours worked/spent on Operations.
Q Actual intemal/extemal Service and Material costs
I What Materials were used
0 Whether and where pieces of Equipment were dismantled from,
or installed at Functional Locations
0 The extent to which the Order has been processed
1 Which technical data should be retained
0 What Measurement or Counter readings were entered for the
Technical Objects during or after execution
S.
Complete
Conrm Job Completion Business Transaction
Conrm Completion of the Job includes setting the System Status of the
Maintenance Order to Technically Completed and the Notication
System Status to Completed. The Maintenance Order should be
Technically Completed as soon as the work has been completed. Once
the Maintenance Order is Technically Completed:
I the System Status TECO is set for the Maintenance Order
0 the Maintenance Order cannot be updated
0 Outstanding Purchase Requisitions will be agged for deletion
Condential DEWA_SAP_WAVE-3_Tll'lSmiSSiOn_EAM_BlUpfln$_COIT8C!lV Maintenence_Final_Vl .l
KPIT Vesta J
0 Outstanding store Reservations will be cleared
~ Outstanding labor (Work Center) capacity scheduled for the
Maintenance Order will be cleared
0 the Maintenance Order can still receive costs (i.e. goods
issues/receipts/invoices can still be posted)
Settle Work Order Cost
The Work Order cost will be settled by means of a batch job running at
frequencies determined and set up in SAP by the EAM/CO team in
accordance with DEWA guidelines.
The following elds are the primary elds found on the maintenance Order:
Figure 11.2.1- Work Order Fields
Order type, dates, plant, main object,
Order header priority, description
Equipment (assembly)
- Object list Functional locations
Maintenance notications
- Work center, control key, description,
operation planned time, activity type, salary details
_ _ Material, quantity, unit of_ measure,
i Matenal ||s'l storage location, batch, item category,
availability
Production
resourcesltools
Settlement rule
Costs
_ (estimated / planned I actual)
Condential DEWA_SAP_WAVE-3_Transmission_EAM_Blueprint_Corrective Maintenence_Final_V1 .1
KP!-r vesta -J
11.3 Operational Account Assignment and Inspection Rounds
11.3.1 Operational Account Assignment (OAA)
Operation Account Assignment (OAA) allows the use of the Operation in a Plant Maintenance Order as
an Account
Assignment Object. This permits the detailed planning, capture and reporting of costs at the Order
Operation level.
Normally, Order costs are posted at Order Header level. The Operations have their own Settlement
Rules enabling more
accurate cost updating of multiple Technical Objects maintained using a single Work Order.
Figure 11.3.1-Plan/Actual cost denition of regular Orders and Operational level cost Orders
existing header costed orders Opefliml |9Ve| 5ti"9
header ,,f,,:j,,,, header
Inventory
management
I8: .
operation procurement p|:|3:cm| operation
(matenali-services)
order n
order no. + opera!

Q
operation G laczzgim operation
postings
H1
II
operation glmeh p|:':7:;im i operation
con rma on ' ' "
COSISZ
plan Sub-operation
Operation Account Assignment offers you the following business benets:
Improved asset valuation due to more granular job costing
Enhanced regulatory reporting capability
Plan/Actual cost reporting on Operation level
This naturally supplements the usage of Inspection Rounds in which each Operation can be assigned to a
different
Technical Object and every object can be associated with different Cost Centers as introduced in the
following
section.
The operational level costing functionality is activated on specic Order Types.
Condential DEWA_SAP_WAVE-3_Transmission_EAM_Blueprint_C0rrective Maintenence_Final_Vl.l (TP-
KPIT Vesta J
11.3.2 Inspections Rounds Functionality
The activation of the Inspection Rounds functionality makes it possible to assign a different Reference
Technical Object
to each Operation. The added value of the functionality is wider than the maintenance activity
inspection. Inspection
Round functionality in SAP can provide advantages for the maintenance of Task Lists and Orders, among
others, the
following repetitive activities:
0 Lubrication Rounds
0 Taking regular meter readings on Measurement Points or Counters
0 Visual Inspection
An inspection task list travels through a set of Objects. For example, walking through a section and
inspecting a set of
related Assets in that section. The Tasks in an inspection list:
0 Are sorted, so that the workers can perform the tasks in a predened or optimal sequence
0 Are linked to a Technical Object (Functional Location, Equipment) and optionally to an Assembly
0 Point to the Measuring Points, Documents, the lubricants, and other tools, such as Test Equipment,
that are used
for each task
~ Are performed on a periodic basis (daily, weekly) or on an event basis (before/after a change of the
Plant or
Operation mode)
0 Have to be available on mobile devices, as well as the reporting and Conrmation of the tasks
Basic Concept of Inspection Rounds:
0 The Inspection Rounds functionality extents the function of PM Work Order Operations
0 Planning is done based on Task Lists and Maintenance Plans
0 Additional elds for Functional Locations and Equipment on the Task List and Work Order for each
Operation
0 Multiple Measuring Points can be assigned to each Operation
The added functionality of the Inspection Round Business Function is visualized below in yellow:
Figure I I. 3.2.1 -Inspection Round Operations
Header (Task usmnonr Order) Assignments D Operations
Operation 10 I Dultnptlnm I wqiggnt I Functlonalloelnnn I Equipment I
5--
Operailon an I Uemlplton I wwreemer I Functional vocation I EIt'-IlP=W\'
Remark: The Measuring Point assigned as
PRT has to be dened as Measuring Point _
for the Technical Object of the Operation. 5
The Inspection Rounds functionality is activated for the entire client, the functionality is then available
in the Operations
of every Order Type.
Condential DEWA_SAP_WAVE-3_Transmission_EAM_Blueprint_Con'ective Maintenence_Final_Vl .l
(TP-EAMO3) Page 23 of 77
KPIT vesta J
12. Business Process Flow Diagram
12.1 Process: Corrective Maintenance Notication
The DEWA Transmission Notication Business Process is presented below. The green block visualizes the
identication
of corrective Maintenance, while the red block visualizes the process capturing of technical information.
Figure 12.1-Processfor Corrective Maintenance Notication
DEWA Tranmission Power ~ Corrective Maintenance Notification
II
a tart ngger: 0
AI SCADA
j Tngizfection ) Create
< . Notification
Obse rvation
._1
\/
Assign
NO Notification
Centra
P anner
0 6 _ 0 _ @i,e
or my Ve .V.ahdi Ye Valid N I investigation
: - arteme . ~ ot|cat|o arrantyi o . y
. U, ., es
NO
- N 9 Q Corrective
6 _ Yes Wor low to order:
ompletton of contractor After Order Created? N - New
CANCELLED manne,
Notification No Apmov Q Yes
O,-k is v Corrective
Q Department's Ye Qidefi
R onsib y? R95-""9
.
YES
_ - ' ' N Completion of Q
_ _ _ _ Notification
_ Feedback Update
Capturing Notification
Department P anner
Team Leader?
Schedu er Schedu er
Condential DEWA_SAP_WAVE-3_Transmission_EAM_Blueprint_Corrective Maintenence_Final_Vl .1
I<I=-'11" Vesta W J
12.1.1 Process Steps: Corrective Maintenance Notication
Table 12.1 . I-Process Steps for Corrective Maintenance Notification
Process Steps (List all SAP Steps) - Corrective Maintenance Notication
Step Type Number Step Role Transaction
Start / 1 Identication of a problem or defect. All External
Trigger Triggered by an Observation, Inspection, Email, SCADA
alami, measurement value or Mobile device.
Create Notification.
The following Notication information is required to clearly
identify the problem or malfunction
- Observed problem Description
- The affected Reference Object:
Functional Location and/or Equipment
- Priority
Action 2 - Breakdown indicator All [W21
Notication Problem code
- NOD Observed by
- Notication Date
The Notication can be created by different paths and
interfaces:
- Manually input in the SAP GUI
- Manual input on a Mobile Device
- Automated through SCADA
Assign Notication
The Central planner validates all new and resubmitted requests
and assigns them to the responsible department by selecting the IW22
Action 3 correct Equipment, Planner group and Work center. Central
Planner IWQ3
The System status Waiting for information can be used when
additional information from Observer is required before further
processing of the Notication
Interface: Manual in the SAP GUI.
' The SAP Syclo mobile solution and the SCADA interface are dened in separate Blueprint documents.
Condential DEWA_SAl_WAVE-3_Transmission__EAM_B1ueprint_Corrective Maintenence_Final_Vl.l
Keir v-ma E57 .1

Step Type Number Step Role Transaction
Decision
4
For my department?
The planner processes all Notications for his planner group
and validates if the Notication is the responsibility of his
department.
No User Status is set to Resubn1itted. To step 3.
Department IW22
Yes User Status is set to Accepted To step 5. Planner lW28
The System Status Waiting for information can be used when
additional information from NOD Observer is required before
further processing of the Notication
Interface: SAP GUI.
Decision
5 work request is not valid:
Valid Notication?
The planner denes if the observed Notication requires
corrective work. For instance it can be the case that problem is
previously corrected by a corrective or preventive Order. If the Depamnnnt IW22
Planner IW28
No (Set User Status = Cancelled) Go to step 6.
Yes go to step 8.
Interface: SAP GUI.
Action
6
Completion of Cancelled Notification
The planner adds a clear justication why the Notication is
=1H<=11@d- Department IW22
- Set User Status = Cancel Planner Iwzg
- System Status = Notication Complete
Interface: SAP GUI.
End
7 End of process
Decision
8 automatic message when an under warranty Equipment is linked
Valid Warranty?
The planner evaluates if the Asset is currently under Warranty
based on the Warranty information on the Equipment Master.
To support the Planner in this process the system provides an Dena,-nnent IW22
to an Notication or Order. Planner IW28
Yes Go to step 9.
No Go to step 10.
Condential
DEWA_SAP_WAVE3ATransmissicn_EAM_Blueprint_Corrective Maintenence_Final_Vl .1 (TP-EAM-03)
Page 26 of 77
KPIT Vesta W
,.J_JOL4D
V
Ihbnnc rmgltuotm
wl-41-A-H'=-141
manor-lg r
Step Type
Number
Step
Role
Transaction
Workow
9
Workow of Notification information to contractor after
planner approval
Workflow is initially triggered to the Department Planner.
If approved by the Planner, the Workow Task is released by
the Planner. This results in the Contractor who receives an email
with the Notication information.
Department
Planner
External
Decision
10
Site Investigation Required?
If the planner has not enough information to plan the Corrective
Work, he can assign a site investigation to collect additional
infonnation.
Yes Go To step 11. User status add the status Site Visit
No Go to Decision step 12.
Interface: SAP GUI.
Department
Plann
I
IW22
IW28
Process
Reference
ll
Corrective Order: New
The planner starts the Corrective Order process by creating a
new Order linked to the Notication.
Interface: SAP GUI.
Department
Planner
IW22
IW2 8
Decision
12
Order Created?
The planner denes if there is already an Order linked to the
Notication.
Yes Go to step 11
No Go to step 13
Interface: SAP GUI.
Department
Plann
61'
IW22
IW28
Process
Reference
13
Corrective Order: Resume:
Corrective Order Process and reume to Block 4 in the
Corrective Order Process.
The corrective Order process is resumed to plan and realize
additional corrective tasks on the existing work Order.
Department
Plann
$1
IW22
IW28
The feedback capturing of a Notication happens after the related Order went through the Order
process stages of
Planning, Scheduling and Execution. The technical details found in the execution phase are captured in
the Catalogs of the
Notication. There are multiple process responsibility possibilities:
1. The Team Leader captures the failure infonnation he observed in the eld on a hardcopy form and he
enters the
data in SAP when he is back at the ofce.
Condential DEWA_SAP_WAVE-3_Transmission_EAM_Blueprint_Cor-rective Maintenence_Final_Vl .l
KPIT Vesta w J
2. The Team Leader captures the failure information he observed in the eld on a hardcopy form and
the data is
insert into SAP by the Planner/Scheduler.
3. The Team Leader carries a Mobile device in the eld, which he uses to directly load the feedback data,
the Order
Conrmations and possibly new Notications for follow~up work into SAP.
l-low the process responsibilities are assigned can vary between different Departments, based on their
workload and exact
organization.
Table 12.1.1-Process Steps for Corrective Maintenance Notication Continued...
Process Steps (List all SAP Steps) - Corrective maintenance Notication Feedback Capturing
Step Type Number Step
Role
Transaction
Stam 14 Feedback capturing
The feedback capturing process is triggered after the
Trigger realization phase of the Order.
Team leader /
Scheduler
IW22
IW28
Update Notication
1. Update malfunction Tab.
Action 15 2. Update technical failure information in catalog tab.
The Notication can be updated by different paths and
interfaces:
Manually input in the SAP GUI
Team leader /
Scheduler
IW22
IW28
Outstanding Work Required?
Decide if there is additional work for the same problem
required.
Yes Additional Work for the same problem is required.
These tasks will be captured on the same Notication and
Order as previous work. Put the user status to Reassigned
Decision 16 and go to step 17.
No- The observed problem is solved. Go to step 18.
For unrelated problems observed in the eld a new
Notication needs be created.
interfaces:
a
Scheduler
IW22
IW28
Condential DEWA_SAP_WAVE-3_Transmission_EAM_Blueprint_Corrective Maintenence_Final_Vl 41
Kerr vesta E17 J

Process Steps (List all SAP Steps) - Conective maintenance Notication Feedback Capturing
Step Type Number Step
Role
Transaction
Work is my departments responsibility?
After a site visit conrmation, follow-up work may be
assigned to the correct Department.
Yes Go to step 13: resume Order planning process
No Change Functional Location and/or Equipment when
Decision 17 required. The system will automatically propose to update the
Planner group and Work Center information based on the
Master Data maintained on the new Functional Location
and/or Equipment. Set User Status to Resubmit. Go to step
3.
interfaces:
Manually input in the SAP GUI
Manual input on a Mobile Device
Department
planner
IW22
IW28
Completion of Notication
Close the Notication. Notication System Status is
Notification Closed.
re
If a reference Notication for another department is c ated,
then the scheduler must assure that this reference Notication
is closed before the main Notication is closed.
Action 1 8
interfaces:
Scheduler
IW22
IW28
End 19 End
Scheduler
Extemal
KPIT Vesta
12.2 Process: Corrective Maintenance Work Order
Figure 12.2-Processzr Corrective Maintenance Work Order
DEWA Transmission Power - Corrective Maintenance Work Order
Start ,Cre=|e Plan lnlemal
Order: New M'""a" Work
Order (TP01)
Q mrrra 0 . w , ulage/Cauti Nun-WCM G
. Matenas van . .
Serv|ce N N , N Permn/Workequest N Flinnlng Releaseorder
. Reqmred? Requvred? .
qmr. Requ|red7
Yes Ves yes
@
Cmpletllvon of 6
Order
Department P anner
R/PO PTW RQ Yes Q Q
Schedu er
N
@ Q Q Sen/Ice @
_ he En @ Entry Update and
Replanning ves_ Ampwme Yes acceplin Technical
Required? _ . ce Completion of
""e Order
Team Leader / Scheclu er
moi
Q Q Q uticatlon
mt: Enter Feedback
WCM e'"" N ' I Execution Conrmation apturln
Yes Q Q WCM
Exec utlon
' rooesse
E
F'nanoe/
Accounfn
' Set\l:m9rll of
Order
Condential DEWA_SAP_WAVE-3_Transmissi0n_EAM_B1ueprint_C0rrective Maintenence_Final_V1.1
KPIT Vesta W J
12.2.1 Process Steps: Corrective Maintenance Work Order
Table 12.2. -Process Stepsfor Corrective Maintenance Order
Process Steps (List all SAP Steps) - Corrective Maintenance Work Order
Step
Type
Number
Step
Role
Transaction
Start /
l Trigger
1
Order New
The start point of the Order process triggered from a
Notication.
Department
Planner
IW3l
Action
2
Create Maintenance Order (TP01)
Input the general Order header data that does not default
from the Notication:
1. Maintenance Activity Type
2. System condition
Interface: SAP GUI
Department
Planner
IW31
Start /
Trigger
3
Order Resume
Start point for previously created Orders which require the
planning of additional work after the rst work execution.
Interface: SAP GUI
Department
Planner
IW32
IW38
Action
4
Plan Internal Work
Create Operations for the Maintenance tasks which
W1
performed by internal labour.
If support work of another Department for the same
Notication is required, then add an Operation to the
Work Order with the Work Center of the other
Department.
'll be
lf it is a big task then a Reference Notication needs to be
created for the other Departments work. The relevan
Department Planner must update the Reference
Noticiation data to match his requirements.
Interface: SAP GUI
I
Department
Planner
IW3l
IW32
IW38
Condential DEWA_SAP_WAVE3_Transmission_EAM_Blueprint_Co\-rective Maintenence_Final_Vl .1
KPIT vesta J
Step Number
Type
Step
Role
Transaction
Decision 5
External Service Required?
Identify if extemal Services are required.
Yes Go to block 6.
No Go to block 8.
Interface: SAP GUI
Department
Planner
1W3]
IW32
IW38
Process
Reference 6
PR/PO Process
Start the Purchase Requisition or Purchase Order process
for the external Service.
The PR/PO Process is previously dened in SAP Wave 2.
Interface: SAP GUI
Department
P1anner/
Buyer
External
Process
Reference 7
PTW Process
Note: Permit to Work (PTW) process is covered in DMS.
Department
Planner
Extemal
Decision 8
Materials Required?
Identify if materials are required for the operations.
Yes (Go to MRQ process to Reserve/Order the Materials
Go to Step 9.
No Go to step 10.
Interface: SAP GUI
Department
Planner
IW3l
IW32
IW38
Process 9
Reference
MRQ Process
Order/Reserve the required materials at the Material
Warehouse.
The MRQ process is previously dened in SAP Wave 2.
Integration with PM is dened by creating
reservations/PR from the workOrder.
Interface: SAP GUI
Department
Planner/
Warehouse
IW32/
IW38
ZWMMRQ_A
PPR
Decision 10
PRTs Required?
Decide if Tools are required to perform the Maintenance
Tasks?
Yes Go to block 11.
No Go to block 12.
Interface: SAP GUI
Department
Planner
External
Condential DEWA_SAP_WAVE-3_Transmission_EAM_Blueprint_Corrective Maintenence_Final_Vl.l (TP-
KPIT vesra E7
t_r4=vLm A-an-H'=i4A
Dbitbztrmlumm mot-xx;
Proces Steps (List all SAP Steps) - Corrective Maintenance Work Order
Step
Type
Number Step
Role
Transaction
Action
Plan PRTs
ll Plan the required PRTs for each Order Operation.
Interface: SAP GUI
Department
Planner
IW31
IW32
IW38
Decision
12
Outage/Caution Permit/Work Request Required?
When the Equipment needs to be out of operation for the
planned maintenance, then an Outage needs to be aligned
with the Operations Department.
Yes Go to block 12.
No Go to block 13.
Interface: SAP GUI
Department
Planner
IW31
IW32
IW38
Process
Reference
13
WCM Process
The WCM process is dened in the separate WCM
Blueprint document.
Interface: SAP GUI
Department
Planner/
Operations
External
Process
Reference
14
N on-WCM Planning
Interface: SAP GUI
Department
Planner/
Operations
Extemal
Action
Release Order
When the Order is planned the Planner Releases the Order
to release the Purchase Requisitions and Material
Reservations.
15 System Status = Released
User Status = Planned
When all Materials, external Services and Permits are
available then set User Status = To Be Scheduled".
Interface: SAP GUI
Department
Planner
IW32
IW38
Process
Reference
MRS Scheduling
Set User Status = Scheduled
16 Note: Process is dened in separate MRS Blueprint
document.
Interface: SAP GUI
Scheduler
External
Condential
DEWA_SAP_WAVE-3_Transmission_EAM_Blueprint_Corrective Maintenence_Final_Vl .1 (TP-EAM
-03) Page 33 of 77
KI=7IT Vesta
t_.-4===L_y=s-I-am-mien _ )
mm Lortrcngllllalm mm-n,
Step
Type
Number
Step
Role
Transaction
Decision
I7
Replanning Required?
Yes Go to step 12 (Set User Status = Replan).
No Go to step 18.
Interface: SAP GUI
Scheduler
IW32
IW38
Decision
18
WCM Related?
Yes Go to step 19.
No ~ Go to step 21.
Scheduler /
Team Leader
External
Process
Reference
l9
Daily WCM Plan
Operations
Extemal
Process
Reference
20
WCM Execution Processes
Operations /
Team Leader
Extemal
Predene
d Process
21
Job Execution
Team
Leader/Field
Staff
External
Action
22
Enter Confirmation
After overall Completion System Status = Finally
Conrmed.
Interface: SAP GUI or Mobile.
Team
Leader/
Scheduler
IW 41
IW48
Process
Reference
23
Notication Feedback Capturing
Interface: SAP GUI
Scheduler
IW22
IW28
Decision
24
Service Entry Acceptance Required?
Yes Go to step 25.
N0 Go to step 26.
Scheduler
IW32
Process
Reference
25
Service Entry Acceptance
The Service Entry acceptance process is previously
dened in SAP Wave 2.
Interface: SAP GUI
Scheduler
ML81N
Condential DEWA_SAP_WAVE-3_Transmission_EAM_Bluepr-int_Corrective Maintenence_Final_V1 .1
\'l:_;>."i~_-;<$ Kg]-f Vesta r_,_pv>Ltnrl-=.w-will J

..,\r~.r-.~-rrrrrr-< lnhmrioetrmynuineranmxy
Step
Type
Number Step
Role
Transaction
Action
Update and Technical Completion of Order
System Status = Technically Completed
User Status = Complete
Interface: SAP GUI or Mobile.
26
Scheduler
IW32
IW38
Action
Settlement of Order
Interface: SAP GUI
27
Finance
K088
KOSG
Action
Business Completion of Order
26 System Status = Closed
User Status = Closed
Interface: SAP GUI
Department
Planner
C099
IW32
Batch Job
End
27 End
Department
Planner
External
12.3 Process: Non-WCM Planning
Figure I 2.3-Process for Non- WCM Planning
Department P anner
DEWA Transmission Power Non>WCM Maintenance Planning Process
i Q Q Resume
Prepare Annual Prevennve o Prepare Monthly G purer Q|_|( preVemi,,,/
_ and Corrective Maintenance for Preventive and maven; work Carmve
Next Year (NcneWCM) to Prepare M Correctlve N . for the Refurbishment]
onthl .
Man-Power and Budgets etc. Mamtenanze for oeparnmem Project
rovide Variant Var Corrective an Next Month (Non- Planner R1,,
Preventive Wark wcm)
anner
Centra P
Annual
mbine Plans Received 9 DOf|y|i(e w|[
Based on Variant "em Q Departmentannerslo
different Devarlmels in Anv Wor Align Work Orders Created
for same Assell Asset Ye By different Departments
Gwvn For Cenwl for same Asse!/ Asset
Reporting . .
1
K;n- Vesta _,_4Jl!994L!)-5135-3+3
,<|;|),\|'\a<n Hi 1'\ g llbmbtlrtitqllotnrhintnrdg
2.3.1 Process Steps: Non-WCM Planning
Process Steps (List all SAP Steps) Non-WCM Planning
Step
Type
Number Step
Role
Transaction
Start /
Trigger
Prepare Annual Preventive and Corrective
Maintenance for Next Year (N on-WCM) to
Man-Power and Budgets etc.
grouped together.
Maintenance Plan dates in the future.
created for each Department.
Interface: SAP GUI
Prepare
For Corrective work, Orders will be created and can be
1 For Preventive work, some Orders will have been created
while others will need to be simulated based on the
A variant for Corrective and Preventive work can be
Department
Planner
IW38
IP24
IP31
IA16
Action
for same Asset / Asset Group For Central R
in order to consolidate maintenance activities.
Interface: SAP GUI
Combine Plans Received from different Departments
eporting
The Central Planner can group together work that can be
2 combined between the different Departments based on the
variants provided against the same Assets or Asset Groups
Central
Planner
IW38
IP24
IP31
IAl 6
Action
Maintenance for Next Month (N on-WCM)
Interface: SAP GUI
Prepare Monthly Preventive and Corrective
3 Corrective and Preventive Work Orders will be created
and can be grouped together for each Department.
Department
Planner
IW38
Decision
4
Can Any Work Be Combined?
Identify if any work between the different Dep
can be combined.
Yes Go to block 5.
No Go to block 6.
Interface: SAP GUI
&l'1Xl'lCl'l[S
Central
Planner
IW38
C
ondential
DEWA_SAP_WAVE-3_Transmission_EAM_Blueprinl_Cor-rective Maintenence_Final_V1 .1 (TP-EAM-03)
Page 36 of 77
\3>:*~e-<> KPIT Vesta W o4="L&B9l-u-A-H11-in J

Process Steps (List all SAP Steps) Non-WCM Planning
Step
Type
Number
Step
Role
Transaction
Action
5
Coordinate with Department Planners to Align Work
Orders Created By different Departments for same
Asset / Asset Group
Central Planner is to coordinate with the Department
Planner where it is applicable to group Orders together
fore the same Assets or Asset Groups in order to
consolidate maintenance activities.
Interface: SAP GUI
Central
Planner
IW38
IW32
Process
Reference
6
Filter Out Relevant Work for the Department Planner
Where Work Orders have been grouped together by the
Central Planner, the Department Planner will lter out the
Work Orders specic his/her relevant Planner Group.
Interface: SAP GUI
Department
Planner
IW38
Process
Reference
7
Resume Preventive / Corrective (Refurbishment) /
Project Orders
The applicable Work Management process is resumed.
Interface: SAP GUI
Department
Planner
External
Condential DEWA_SAP_WAVE-3_Transmission_EAM_Blueprint_Coi-rective Maintenence_Final_Vl .1
Q..>."(~::<'> ](p:1T Vesta tt=~_t-=9 up-_~~=1t=

t-it.-.-.t-at-,1; g Ihbntbeumitqllawrhxhalg '
13. Business Process Design Details and Information
This chapter provides an overview of the detailed design decisions, the SAP Conguration settings and
where necessary a
more detailed description of specic topics.
13.1 Corrective Notication
This paragraph provides a description of the detailed design decisions and the SAP Conguration
settings of the
Corrective Notication Type in SAP. Furthennore, a detailed overview of the SAP RCM Catalogs is
presented.
13.1.1 Notication Design Details
0 Notication Type T1-Corrective Maintenance is used for all Corrective DEWA Transmission Power
Notications.
0 Normal Corrective Work, Emergencies, Real-time NODs and Abnormal events will be identied by T1
Notications.
- Notications will be categorized in two ways:
I Corrective Notications
~ Real-time NODs
The Notication Prole for T1-Notications will contain the following Priorities:
0 Corrective Notications and Realtime NODs:
0 High
o Medium
o Low
Note: For Real-time NODs, the response time allowed depends on the following:
0 NOD Category
0 Nature of Defect
O Responsible Department
Lead times are required for each Priority and Department in order to manage their response times and
SLAs.
Lead times and automated basic/start end date population, based on the Priority, will be congured.
Transmisison Power utilizes different SLAs for each Department and separate SLAs for Outage and Non-
outage
work. Furthermore, these SLAs change frequently.
Breakdovtm Notication are identied by the Breakdown checkbox in Order to calculate the MTTF and
MTTR,
the malfunction start and end time of Notications need to be populated for breakdowns.
0 The Notication Code Group and Code is mandatory .
0 The NOD Observed by eld is mandatory for each Notication.
Catalog Group and Codes
I The Notication Code group needs to differentiate between :
General Categories:
o Environment, Heallth & Safety
o Technical
Housekeeping
Refurbishment
OO
KPIT Vesta w
0
O
RTO Categories (only created by Operations Department):
O
O
OOO
Critical Alarms (Workow Auto email from SAP to predened list)
Transmission Trip (Workow send Auto email from SAP to predened list)
Generation Trip (Workow Auto email from SAP to predened list)
Dubal Trip (Use External Customer Functional Location)
Emergency Outage
The Notication Code species the identied problem or malfunction
For each Code Group, the following set of Catalog Types need to be dened.
O
O
O00
Object Parts
Damage
Cause of Damage
Activities
Tasks
Workows
The following Workow requirements are identied by the Core Team:
v Workow to Contractors to notify of Corrective work under Warranty.
0 Workow to notify the person who created the Notication when their Notication is rejected.
0 Critical Alarms (Workow Auto email from SAP to predened list)
0 Transmission Trip (Workow send Auto email from SAP to predened list)
I Generation Trip (Workow Auto email from SAP to predened list)
The identication of assigned work in SAP is done through running list reports. The need and exact
requirements for
these workows will be specied in the Realization phase.
Mobile
High Priority Notications created on a Mobile device is required to be directly pushed to the SAP
system instead of the
nonnal synchronizations after manually pressing the Synchronize button.
Linear Data
0 Notications which hold a Linear Reference Object by default get the Linear Data from the Reference
Object.
~ The exact location of each Notication needs to be maintained in the Notication Location Tab.
13.1.2 Conguration
Notication Type and Number Range
The Notication Type is a mandatory eld that needs to be specied on every Notication.
The Notication Type denes:
~ Different screen elements and elds
0 Priority Prole
0 Link to an Order Type
Condential DEWA_SAP_WAVE-3_Transmission_EAM_Blueprint_Con'ective Maintenence_Final_Vl .l
vesra W -.)
0 Status Prole
In SAP, all Corrective Maintenance will be captured in a Notication with the Notication Type:
Table 13.1.1.1-Corrective Maintenance Notication Type
Code i Description
T1 I Transmission Corrective Maintenance
The Breakdown Indicator can be used to make an aggregation between Breakdown Notications and
non-Breakdown
Notications.
All Transmission Departments will utilize the Notication type Tl for both NODs and Abnormal Events.
This decision
implies that all Departments are required share a Priority Prole in which a set of target response times
are dened.
The Notication Type Tl is assigned to the existing number range for PM Notications.
Table 12.1.2.2-Notication Type T1 Number Range
Notication Type i Number Range From: I Number Range To:
T1-TP Corrective Maintenance I 10000000 | 99999999
Notication Status Management
The Status codes in SAP are used to route the Notication through the dened business process. The
current Status of a
Notication shows which processing stage the Notication has reached and which steps have yet to be
completed.
A Notication can have the following two types of Statuses:
l. System Status
System Statuses are set by SAP when you execute certain functions for a Notication. For example,
when you print a
Notication, the system sets the status Notication Printed (NOPT). The System Status tells you that a
business
transaction was carried out for the Notication. The System Statuses for Notications are predened in
the SAP System
and cannot be changed.
2. User Status
Apart from having the System status, SAP has given the option of using User Statuses for Notications.
User Status are
dened by the user to support their business process.
The User Status can be used to control SAP Business transactions. Usually, a Notication must have a
certain Status
before you can process it further. A system message will inform the users about this restriction. For
example, the
conversion of Notications into Orders and the completion of Notication can be controlled based on
the User Status.
Condential DEWA_SAP_WAVE-3_Tra.nsmission_EAM_Blueprint_Corrective Maintenence_Final_Vl .l
Vesta s_4:L-load-u-I1->U-sl J
i-1\lK\\ll\IlYll>l\ _ muqunemszqnumomuruiq
Security can be controlled by User Status codes, so that only designated groups have the ability to
set/remove certain
Status codes.
Table 13.1.2.3-Corrective Notication User Status Prole
Code Description
TP_NOT|F DEWA Transmission Notif Status
The following set of User Statuses are dened for the Status Prole TP_NOTIF.
Figure 14.1.2.4-Corrective Notication User Statuses
User Status
Stat... Status Short Text Lon.
SITV
WFIH
5 INII
10 RESU
15 ASSN
CANE
ACCP
30 REES
|~.\ ru
u-I:
Site Visit
Waiting For Information
Initial
Resubmit
Assigned
Cancel
Accepted
Reassign
Inic.
ll
lv/l
.
'l
35 com Complete 5 1
The User Status Waiting for Information and Site Visit do not have a Status number. It is an
additional Status which
can be agged in addition to the other Statuses.
Priorities
A set of Priority Codes is assigned to each Notication Type. An initial Priority can be dened for each set
of Priority
codes. The Priority can be changed during the review of a Notication. The Priority has the following
functions:
I Prioritize Notications
0 Dene Target Response time for Notications
0 Transfer Priority to Work Orders
Table 15.1.2.5-Priority Prole for Corrective Notications
Priority Prole
Code i Description
T1 I PM Priorities
The following Priorities are dened for T1 PM Priorities:
Condential DEWA_SAP_WAVE-3_Transmission_EAM_Blueprint_Con'ective Maintenence_Final_Vl.l
(TPEAM-O3) Page4l of 77
KI=""' Vem \J
Table 16.1.2.6-Prioritiesfur Corrective Notications
Screen layout and Fields
For Notication Type T1-TP Corrective Notication
Table 17.1.2. 7-Corrective Notifications Tabs
Tab Number I Tab Header
,_.
I Header Data
l\J
I Malfunction Data
Lo)
I Document/Links
-lk
I Location/Linear Data
LII
I Catalogs
O\
I Tasks
I
I
I
Tabl : Header data
Mandatory and Optional Fields to be used in the Notication Header tab.
Table 18.1.2.8-Corrective Notications Header Tab
Field tional or Mandatory I
Notication Type
Short Description
Description
Order
An Order can be linked directly to the Notication.
66E
Table 19.1.2. 9-Corrective Notification Reference Objects
@oE
Field
Functional loc.
Equipment
Assembly
tional or Mandatory
Table 110. 1.2. I0-Corrective Notication Categories
Field I Optional or Mandatory
Coding I M
Longtext I O
Table I1 1.1.2.11-Corrective Notification Responsibility Fields
SE5
"U
tional or Mandatory
Planner Group
Main WorkCtr
I Field
I
Condential DEWA_SAP_WAVE~3_Transmission_EAM_Blueprint_Correetive M
aintenence_Final_Vl .1 (TP-EAM-03) Page 42 of 77
~t'K ..
KPIT Vesta
NOD Observed by
E
I Reported by
E
I Notif. Date
E
Table 1I2.1.2.12-Corrective Notication Dates and Priority
Field
E
U
tional or Mandatory
Priority
E
Required Stan
E
Required End
E
Breakdown
E
Note: Based on the selected Priority the Required start and End data are automatically populated
Tab 2: Malfunction data
Table 113.1.2il3-Corrective Notification Malfunction Data
|O
Malfunction Start
Malfunction End
Breakdown
Breakdown Duration
|0
10
lo
The Breakdown Duration is automatically calculated from the Malfunction Start and End date when a
Breakdovwi is
indicated.
Table I I 4.1.2.14-Corrective Notication System Eects
Field
Z
"5
tional or Mandatory
Funct. Loc. affected
E
Equipment affected
E
Effect
E
The Functional Location and Equipment effected are by default populated by the reference Ob_]6Cl
dened on the Header
1" ab.
Table 115.1.2. I5-Corrective Notication System Availability
I Field
Z
U
tional or Mandatory
Avail.bef.Malfunction
E
Cond.bef.malinctn
E
Avail.aft.Malfunction
5
Cond.aft.malfunctn
E
Availafter task
E
Cond.after Task
E
Tab 3: Document/Links
The Document/Link tab provides the opportunity to link DMS documents to the Notication. A set of
Documents can be
linked, for each document the following elds need to be lled in.
Condential DEWA_SAP_WAVE-3_Ti'ansmissionVEAM_Blueprint_Corrective Maintenence_Final_Vl .1
__.--3" ', , .
\_P>f'~<_> Z 1 ot_m l_|)_m.5|.ub
i.~iti~.\.@<~.. lg] I \. K I Vesta KiDw\:hi:tgl|1hbr1hAru|!g
Table 11 6.1.2.16-Corrective Notification Document Links
Field
S
O
tional or Mandatory
Document Type
E
Document
E
Document Part
E
Version
E
Description
E
Status
5
Hierarchy
E
Rev. Level
E
Tab 4: Location/Linear Data
The Location/Linear data is utilized for two functions, rst it references the default location of the asset
to be published 0
the Notication. The Location/Linear Data Tab is defaulted from the Equipment Master Data of the
linked Equipment.
Table 11 7.1.2.1 7-Corrective Notication Location Data
Field
3
U
tional or Mandatory
MaintPlant
Z
Location
E
Room
E
Plant Section
S
ABC Indicator
E
Son Field
E
Secondly, the Linear data can be used to capture the exact location of the Notication for Linear Assets
The following
linear data elds are available:
Table 118.1.2. 18-Corrective Notification Linear Data
Field
3
U
tional or Mandatory
Start Point
O
End Point
O
Length
O
Unit of Measure
O
St. Marker
O
End Marker
E
Dist. St. Marker
5
Dist. End Marker
E
Offsets
E
Tab 5: Catalogs
The catalogs tab is divided into three Sub-tabs:
Condential DEWA_SAP_WAVE-3_Ti'ansmission_EAMBlueprint_Corrective Maintenence_Final_V1 I
(TP-EAM-()3) Page 44 of 77
KPIT Vesta
I Object Parts/Damage
0 Causes
0 Activities
Object Parts/Damage Tab
For each entered Object part/Damage:
Table 119. 1.2.19-Corrective Notification Catalog Data Object Parts/Damage
Field
3
U
tional or Mandatory
Object part
E
Damage Code
E
Text
E
Assembly
E
Number of defects I
E
Cause Tab
For each entered Cause:
Table I20.1.2.20-Corrective Notication Catalog Data Cause
Cause Code I O
Cause Text I O
Activities
For each entered Activity:
Table I21. 1.2.21-Corrective Notication Catalog Data Activities
Activity Code I O
Activity Text I O
Effect on the system
Denes the effect of the malfunction on the operation of the selected equipment or functional location.
The following
effects are dened during the workshops:
Table 122.1 .2.22-Corrective Notification System Effects
Code I Description
A I Parent Functional Failure
B I Parent Potential Failure
C | No Effect on Parent
System Availability
Condential DEWA_SAP_WAVE-34Transmission_EAM_Blueprint_Corrective Maintenence_Final_Vl .1
1<i=1-r v-ma E'I'7 J

The system availability window denes the system condition and availability before the malfunction,
after the
malfunction, and after the corrective tasks. The possible system conditions are predened by SAP.
Table 123.1.2.23-Corrective Notification System Conditions
System Condition
erational
n Limited Oeration
ut of Order
13.1.3 Notication Catalogs
Notication RCM Catalog Proles
Catalog Proles are a combination of Code Groups and Codes used by SAP to store the technical history
of a Notication
SAP uses Catalogs to standardize technical history allowing for Failure Analysis reporting
They can be specic to a type of asset (e.g. pump, motor, transformer)
Catalog Proles can be assigned to individual FLOC/Equipments
A default generic catalog prole can be assigned to each Notication Type. If the Functional Location or
Equipment has been assigned a Catalog prole it will overwrite the default Catalog Prole from the
Notication
Type. Alternatively a Catalog Prole can be manually selected on Each Individual Notication.
A Catalog can exist of the following set of Catalog Types:
o Object parts Denes the object on which the failure is observed
o Damage Denes the damaged observed on the object part.
Cause of Damage Denes the cause of the damage.
Activities Denes the activities performed during the Corrective Work.
Tasks Denes an follow-up activity that still needs to be performed, the task can be
assigned to responsible employee and the status Task is required to be managed.
Catalog Types, assigned to a Catalog can be subdivided into Code Groups. A code group holds a set of
codes which serve
as the actual attribute coding.
OOO
The consistent use of the failure and cause codes provides a convenient method of getting statistics
about equipment
failures and breakdowns. They aid your ability to effectively identify trends and problems. If the failure
rate is above
average, it may be worthwhile proactively replacing parts or shortening the PM interval. Knowing the
failure rate for a
failure code and the failure causes can help in doing the following:
0 Optimize RCM tasks and intervals
~ Improve failure response
0 Improve work practices
(TPEAM~03) Page 46 of 77
i<=-IT vem E17 J
Figure I2-4.1.3. I-Corrective Notification Catalogs
1
~ ~ i am
i " 7: '"" El Dbyect part Object parts Cmmg
l Type
B: BALCO1 motor
9? MuByE' I I l e:l:am.co2 battery
battery ce <_ M
battery charger
UMIIYIO WIN! WMUDIII m 1
"..T" -rat"-" II! 22:22: zazaz.
_ _ ,, ,, ,_ _ _ _ _, _ _ _ _ El BALCOS Field equipments
vw
N.-
Dening Catalog Codes
Without doubt, effective and accurate code lists are required for identifying trends but deciding what
selection choices to
place on such pick lists is no trivial matter. Too few codes and they would not support the level of data
analysis desired or
the data will be meaningless. Equally, if there are too many options, technicians tend to suffer from
choice overload and
the default will become either the Miscellaneous or Other option, which will again render the data
meaningless. Code
Groups & Codes should be dened with global naming convention with some standard technique so that
it can be used by
the company across locations. The Catalog codes should tie into the Object Parts, Failure Codes and
preventive tasks dened
in the current DEWA Transmission Power RCM practices. DEWA Transmission Power is currently in the
process of
dening their different Catalogs.
Condential DEWA_SAP_WAVE-3_Transmission4EAM_Blueprint_Corrective Maintenence_FinalAVl .1
I<I=I"r Vesta J
13.2 Work Order
This paragraph provides a description of the detailed design decisions and the SAP Conguration
settings of the
Corrective Order type in SAP.
13.2.1 Design Details Information
Order Type
I DEWA Transmission Power will utilize the Order type TP0l-Corrective Maintenance for all Conective
Maintenance Work.
I The System Condition is a mandatory eld for all TP01 Orders to assure a clear distinction between
Outage and
non-Outage Orders.
I Maintenance Activity Types on Work Orders are used to indicate more accurately what the
maintenance activity
is about and to group Orders in Cost Reports. DEWA Tranmission Power will not utilize Maintenance
Activity
types because Maintenance Activites of the different categories (Inspection, lubrication, condition
monitoring,
cleaning etc.) are maintained in a common RCM tasklist and as a result can be combined in a single
Preventive
Maintenance Order. To keep the reporting for Corrective Maintenance and Preventive Maintenance
alligned
Maintenance Activity types are not maintenained for both. To provide the visibility of the differnet
activities cost
will be reported at operation/task level.
I For TPOl Orders it is mandatory to have a settlement rule dened and a Fund Management Fund
assignment
before Order release. The Settlement Rule and the Fund Management Assignment will be automatically
made
based on the Cost center of the Reference Object.
Activity Type and Work Centers
I Activity Planning is a SAP CO Function.
I A Work Centre may perfonn different activities which are captured on Plant Maintenance Orders at
different
activities.
I The activity planning should be done annually for the following scal year. The Work Centre will not be
able
to do conrmations for the labour unless the activity planning has been done for its cost centre.
I In Order to be able to perform activity planning, the activity type master data should be in place.
Activity Type
describes the activities that are performed by a Work Centre.
I The Activity types and the costing impact have been previously dened during the SAP Wave2
implementation.
Activity types are dened based on employee grade level.
PM Order Costing
I PM Orders are costing objects
I As the Maintenance Order moves through the planning process, the planned costs for labour, materials
and
services are derived automatically by the system as follows:
I DEWA Transmission Power plans and executes Maintenance work in teams. The team constitutes of
multiple
employees with different grades. Cost planning calculation will be based on an average Activity type for
the
Work Centre. Actual labour cost will be calculated based on individual conmiations with the employees
Activity type or grade level.
I The average Activity for each Work Center is dened with the following methodology:
KPIT Vesta J
1. Dene the number of employees assigned to each rate in the Workcenter.
2. For each grade calculate the product of the number of employees times the hourly rate of the
grade.
3. Sum the in previous step calculated product of each grade and divide by the total number of
employees in the workcenter. The result of this calculation is the average hourly rate of the
Workcenter.
4. Choice the Activity type with the hourly rate that has a minimum deviation from the calculated
average hourly rate of the Workcenter.
DEWA Transmission requested an enhancement to automate the denition of Work Center Acitivity
types
when the HR assigments of Employees to Workcenter changes.
0 The Cost Centre is assigned to the Work Centre and the Activity type is defaulted on the Work Centre.
0 DEWA Transmission Power requires the plan and actual cost of travel time. An operation will be
created for
travel time. This operation is also utilised in the scheduling process.
0 The Operations of a Plant Maintenance Order serve as the Account Assignment Object to allow:
o Improved asset valuation due to more granular job costing.
o Plan-actual cost reporting on operation level.
v Patrolling and inspection rounds require to dene technical objects on operational level instead of
Order
header level.
o Improved asset valuation due to more granular job costing
o Enhanced regulatory reporting capability
Warranty Management When Creating Maintenance Orders
If a warranty exists for the failed asset identied in the maintenance Order, the need exists to recognise
and action warranty
claims as appropriate.
0 Warranties will be maintained on the equipment master by selecting the warranty start and end dates.
0 The detail warranty documents will be attached to the Equipment or Functional Location
0 When an active warranty exists a warning message will appear during the creation of the Notication
and Order.
I Warranty information is always available in the Equipment Master for further reference.
Plan/Capture Resources & Tools Required
0 Required resources to perform the tasks must be identied and planned.
0 If a Task List is used to plan the maintenance Order, then conrm the copied task details.
Labor Hours
o Time estimates with the required Operation Work Centre is entered for each Operation.
I The system compares the labour capacity requirement for the Operation against the capacity dened
for the
Work Centre and will issue a message if there is a capacity overload.
KP/T vesta E17 J

Materials
0 These are planned from the component allocation screen within the Maintenance Order.
0 Material required for the job can be selected from the Bill of Material for the Order reference object
(functional
location, equipment), if one exists, or they can be selected from the Material Master File for catalogued
items
for both Stock and Non-Stock items.
Production Resources and Tools (e.g. Cranes, Measuring Equipment, Tools)
0 Production Resources/Tools (PRTs) functionality in SAP is used for this purpose.
0 Individual PRT s can be represented as material or pieces of equipment in SAP and are assigned to the
Operations of Maintenance Orders and Task Lists.
~ PRTs can be reserved and availability can be monitored in MRS.
I If the plan/actual job costs of PRTs need to be registered, than the PRTs need to also be registered as
Wot
Centers.
Documents
0 Production Resources/Tools (PRTs) functionality in SAP is also used for documents.
0 All documents associated with the Maintenance Order can be dened as PRTs and assigned to the
Operations
of Maintenance Orders and Task Lists.
I The link to the actual document is established via the Document Management System that contains the
document type (e.g. MS Word, Excel, Drawing, Picture, etc.) and its location.
Permits
DEWA Transmission Power Maintenance requires a Permit for a subset of the Maintenance Activities,
these
permits are issued by the Operation department. The integation between Work Orders used to
plan/identify those
permits and the WCM Objects for permits is described in the WCM Blueprint. The following pennits are
identied.
I Outage Permit
0 Caution Permit
0 Work Request
Conrmation
A conrmation documents the processing status of Orders, operations, sub operations and individual
capacities.
0 The control key is a default value which denes how an operation should be processed.
o Operations performed by internal labor are assigned the control key PM01.
o External Operations are assigned the control key PM02.
o Extemal services are assigned the control key PM03.
0 Conrmations are required for Operation performed by Internal Labour.
0 Individual and Collective time connnations are possible. In Order to provide an accurate overview of
Actual
Costs individual Time Conrmation with the individual Activity Type of each employee are required.
0 For Extemal Operations) and External Services connnations are possible but not required.
0 The following information need to be populated during the Notication:
o Labor hours
KPIT Vesta J
o Measurement and Counter Readings
o Technical Conrmation on the Notication.
0 Conrmation of Linear Data allows to record the processing status of a Maintenance Order
0 Conrmation of Material Movement is not required for DEWA Transmission Power, because all
Materials
are withdraum against Reservations only.
Q When Costing of PRTs is required than the PRT needs to be represented by a Work Center, a separate
operation for the PRT needs to be conrmed.
Form Requirements
0 A mapping between the currently used Notice of Defect paper, the SAP elds and the DEWA
Distribution
Shop paper has been discussed. DEWA Tramnission Power will dene a nal layout during the realization
phase.
I The SAP standard to producing Shop Papers is achieved via SAP FOYITIS and Technical Development.
Each
Shop Paper that is dened for use in lant Maintenance needs to he developed and thereafter assigned
for use
on the various PM Orders dened. Job Cards contain all of the necessary Information to successfully
complete
a maintenance task.
0 For DEWA Transmission Power Internal and External shop papers are identied as required.
Shop Paper Layouts
Knowing exactly what should appear on the Job-card cannot be listed at this point, as this is dened only
during the System
Realisation Phase however the following points are currently noted;
0 Planned Durations should appear on the J ob-Card
n The Notication Date should appear on the printed Document
v Variables to be added:
0 PR / PO No.
0 Reservation No.
I Operations
I PRTs
I Packages where applicable
O Measuring Point where applicable
0 Dates: Schedule start & nish date for each Operation
0 Planned hours
0 Maintenance Plan no. + next schedule date
0 Task List (Group & Group Counter)
0 Materials requirements
0 Catalogs will appear on the Job-Card
0 Object Lists will be used and the Objects listed in the PM Order Object List should be printed on the
Job-Card
showing the associated Functional Location and Equipment Data.
0 Printing will be required for all Control Keys used on the PM Work Order
o Printing will be required for all Work Centers used on the PM Work Order
(TP-EAM-03) Page S1 of 77
_Jn _ r , ' _
KPIT vesra M J
The following Shop Papers are available in the standard system:
Control Ticket
The operation control ticket gives the maintenance foreman responsible for the job a complete
overview of the maintenance
Order. It also contains details all the objects to be maintained as well as required pennits.
Job Ticket
The job ticket, which accompanies the Order, provides the manual worker carrying out the task with a
complete overview
of the job.
Pick List
The pick list informs the warehouse clerk which materials have been dispatched for each operation in
the Order. This will
not be used in Plant Maintenance.
Material Issue Slip
Material issue slips authorise the manual worker to issue the materials required for the Order from the
warehouse. A separate
material issue slip can be printed for each material component but DEWA have decided that a material
issue slip from the
receiver will not be required when material is collected. Material will be issued against a reservation
number and the receiver
will sign for the materials on MM documentation produced at delivery.
Time Ticket
The time ticket is a means of recording work times (actual labour hours) for the Order.
The number of time tickets specied for each manual worker involved in an Order is printed out for each
operation. The
manual Worker enters the time that he needed to carry out the operation. DEWA needs to make a
decision whether this will
be required or if another paper form will be used to capture this information.
Completion Conrmation Ticket
The workers enter on the completion conrmation ticket the relevant completion conrmation data for
each operation, if
they themselves do not have authorisation to use the system. The entries on the tickets are then
entered by the data
capture clerk centrally into the system.
Condential DEWA_SAP_WAVE-3_Transmission_EAM_Blueprint_CoiTective Maintenence_Final_Vl .1
(TP-EAM~O3) Page 52 of 77
Vesta J
13.2.2 Conguration
Order Type
Based on the DEWA Transmission Power requirements, one Corrective Maintenance Order Type will be
created:
Table I25.2.2.1-Corrective Maintenance Order Type
l Order Type I Description i Application
TP01 Transmission Corrective Maintenance Use for all Corrective Maintenance request
derived from a PM Notication.
Differentiates between various
maintenance activities.
Order Type TP01 is linked to planning plant 1200: DEWA Transmission Power
Planning Indicator
The Planning indicator is simply a default radio button set per PM Order Type through which a Work
Order is identied
as a Planned Job or and Unplanned job and is used purely for reporting.
Table 1Z6.2.2.2-Corrective Maintenance Order Planning Indicator
Order Type I Planning Indicator (Default)
TP01 I Unplanned
Notication and Order Integration
Table I 2 7.2.2. 3-Corrective Maintenance Notication & Order Integration
Notication Order Notication Long text
Type Type
Tl | TP01 | X X
Orders created from Tl Notications are populated with the TP01 Order Type. The system automatically
copies the long
text of the Notication Header as the long text for the Order Header when an Order is generated from a
Notication.
Control Key
The Control Key denes how an operation is processed. DEWA Transmission utilizes the following
control keys, which
are previously implemented in SAP WAVE 2.
KFWT Vesta
Table I28.2.2.4-Corrective Maintenance Order Control Keys
Existing Description Outcome for Procurement
Ctrl Key
PM01 I Intemal Operation I No impact on Procurement
PM02 i Extemal Operation I P-Req / PO / Followed by Goods receipt
PM03 i External Service i P-Req / PO / Followed by Service Acceptance
PMOI is the default control key for TPO1 Order Operations
Work Order Status Prole
Figure 1292.2. I-Corrective Maintenance Order User Statuses
t User Status
Stat... Status Lon... Init.
WFCP
WFMI
WFUU
WFSE
5 It-III
10 PLND
,l5 IBSC
20 SCHD
25 RSCH
'30 RPLH
35 COMP
40 CLSD
i '1
, I,
=J
Vi
i1
I
lwl
Work Order Priorities
A set of Priority Codes is assigned to each Order Type An initial Priority can be dened for each set of
Priority codes
The Priority can be changed during the review of the Order The priority has the following functions
~ Prioritize Orders
I Dene Target Response time for Orders
Table 130.2.2. 5-Corrective Maintenance Order Priority Prole
PM Priorities
Code Description
T1 I
The Notication Priorities will be defaulted to the Corrective Order Type
Condential DEWA_SAP_WAVE 3_Transm1ssion_EAM_Bluepr1nt_Corrective Maintenence_Final_Vl 1
Priority Prole
1<=-IT vase E J
Table 1312.2. 6-Corrective Mai
ntenance Order Pr
iorities
Relative Start
Date for
TasklNotification
in Days
Priority
Type
Text
Relative End
Date for
TaskINotification
in Days
Priority Text
RESU
REDU
Description
PM Immediate
1 Week
High-C
U
U
High - Corrective
PM Immediate
2 Weeks
Medium-C
U
U
Medium - Correctine
PM Immediate
One Month
Low-C
U
U
Low-Corrective
PM Immediate
24 Hrs
H-SG-OP-SND-O
CEX
U
U
Switchgear Operation
Trouble Due to SCADA &
outage can be extended
PM Immediate
Same outage day
H-SG-OP-SND-O
NEX
D
D
Trouble Due to SCADA &
outage can't be extended
PM Immediate
8 Hrs
H-SG-OP-TEM
H
H
Trouble Due to field problem
related to TEM
PM within 3 days
within 21 days
TPD
MDFR-COMMS-
D
D
DFR not communicating
with master station related to
TPD
PM within 24 Hrs
within 3 days
H-DFR-FLT-SS-
TPD
D
D
DFR not working at site
related to TPD
PM within 24 Hrs
within 30 days
M-TCC-FLT-SND
D
D
TCC device defected &
related to SCADA
PM within 24 Hrs
within 14 days
M-TCOM-FLT-
EM-SND
D
D
Telecommunication Defvices
Failure durining
Emergencies related to
SCADA
PM Immediate
within 24 Hrs
H-SCADA-FLT-
AOP-SND
D
D
SCADA Equipmet Defective
& affecting the Operation
PM within 3 days
within 14 days
M-SCADA-FLT-
NOP-SND
D
D
SCADA Equipmet Defective
& not affecting the Operation
'PM
I
Immediate
with 24 Hrs
H-SS-|NVLD-
STAT-SND
D
D
Invaled SS status due to
SCADA
PM within 24 Hrs
within 56 days
M-AVR-FLT-TEM
D
D
AVR Defected related to
TEM
PM Immediate
within 8 Hrs
H-FDR-U R-
ALRM-TEM
H
H
Defected Urgent Alarm
related to TEM
PM within 24 Hrs
within 3 days
H-DC-MAJOR-
FLT-TPD
D
D
Major DC Equipment Failure
related to TPD
PM within 24 Hrs
within 21 days
M-DC~M|NOR-
FLT-TPD
D
D
Minor DC Equipment Failure
related to TPD
PM within 24 Hrs
within 3 days
H-N O-MES-
SCADA-SND
D
D
Measurment (voltage,
current & frequency) not
updating in Spectrum related
to SCADA
Condential DEWA_SAPAWAVE-3_Transmission_EAM_B1ueprint_C0rrective Maintenence_Final_Vl
.1 (TP-EAM-03) Page ss of 77
KPIT Vesta
PM within 3 days
within 28 days
M-M|SMES
SCADA-SND
E37
u-41 OL4->9 Lu-A-i <1-I-.11
new nourntqn ILIMI4 llhnrlg ~
Mismatch Measurment (MW,
MVAR, voltage, current ,
frequency & Energy meter)
not updating in Spectrum
related to SCADA
PM within 24 Hrs
within 3 days
H-SGSTAT-
ONOFF-SND
Inconsistent Switchgear
on/off status related to
SCADA
PM within 24 Hrs
within 3 days
H-MS-BAYNO-
MIS-SND
SCADA bay number in
Master station not matched
with eld related to SCADA
PM within 24 Hrs
within 3 days
H-ENGMTRFLT-
TPD
ENG feeder energy meter
defected related to TPD
PM within 24 Hrs
within 14 days
M-MTR-FLTTPD
Energy meter defected
related to TPD
PM within 24 Hrs
within 24 Hrs
HMS-GEN-EMS-
FLTSND
Defects related to
Generation EMS
applications related to
SCADA Master Station
PM within 24 Hrs
within 3 days
MCO-GEN-EMS-
FLT-SND
Defects related to
Generation EMS
SCADA Contractor
PM within 24 Hrs
within 3 days
HM S-EMS-FLT-
SND
Defects related to
Transmission EMS
SCADA Master Station
PM within 24 Hrs
within 7 days
M-TCOM-EMS-
FLTSND
Defects related to
Transmission EMS
applications related
toTECOM SCADA
PM within 24 Hrs
within 3 days
H-CHAT-HVAC-
TCM
Chattering HVAC alarms
related to TCM
PM within 24 Hrs
within 3 days
H-CHAT-F PS-
TEM
Chattering Fire Protection
Alarms related to TEM
PM within 24 Hrs
within 7 days
M-CHATDC-TPD
Chattering DC & charger
Alarms related to TPD
PM within 24 Hrs
within 3 days
H-CHAT-SCADA-
SND
Chattering SCADA system
Alarms related to SCADA
No target response time will be applicable for Order Priorities.
Work Order System Condition
Figure 132.2.2.2-Corrective Maintenance Order System Conditions
C TP_Outage
P VTP_i'l0n-outage
Default Units of Measure for Planning Plant 1200
The default Unit of Measure for Work Orders should be set as Hours (HR).
Condential DEWA_SAP_WAVE3_Transmission_EAM_Blueprint_C0n'ec1ive Maintenence_Final_Vl .1
(TP-EAM-03) Page 56 ot77
KPIT vem E17 J

Time for settlement rule
For TP01 Orders it is mandatory to have a settlement rule dened before Order Release.
Mandatory and Optional Fields for Order Header
Table I 3 3.2.2. 7-Corrective Maintenance Order Header Fields
Field | Optional or Mandatory
Description M
PlannerGrP ' M
Main Workcenter | M
PMActctType | O
SystConditi0n
Priority
BSC Start
BSC End
Functional Location
Equipment
Assembly
EEEEEEE
Condential DEWA_SAl_WAVE-3_Transmission_EAM_Blueprint_Corrective Maintenenee_Final_Vl .1
(TPEAM-O3) Page 57 of 77
-~ .
K:-IT v-ma E17 J
14. Process Issues (As-Is)
Process Issues (As-Is)
As-Is
I DEWA Transmission Power Corrective Maintenance can be triggered by the following sources:
0 (SCADA) System Alarms
o Outcome of inspection or patrolling work
Observations by eld workers or operators
Observations by contractors
O0
In JMS, two types of corrective works are distinct:
o Notice of defect (NOD) Observation of defect
0 Abnormal event (SCADA) System Alarm trigger
The As-Is process consists of the following generic steps for the different Departments:
1. The observed defects and alarms are communicated to the TCC or TO coordinator. The TCC or TO
coordinator:
o Creates a Work Request in JMS, with status New
o Denes a priority to the work request
o Assigns the Work request to the concemed department, the concerned coordinator receives an auto
email
Notication.
0 For some departments NODs identied inside the department, for instance from an inspection, are
directly created by the Department Coordinator and do not involve the TCC or TO coordinator.
2. The concemed Department coordinator:
o Denes if the NOD is under the assigned department
No Send the NOD back to the concemed department with feedback
Yes Update the NOD status to In progresses and assign to relevant section
3. An Engineer of the relevant section evaluates the following information and creates an action plan:
o ls the Asset under Wan"anty? if Yes Work will be perfonned by contractor
o Is Outage required? Yes- Create outage request and obtain approval by TOP Manager.
o Required documents: test report, Method statement, Risk Assessment, Drawings, list of vehicles and
manpower, Permit to work.
4. The work request is assigned a Field supervisor and schedules the work request.
5. After work execution the Field Engineer submits a report to the coordinator.
6. The coordinator updates the cause & corrective action taken in JMS and denes the status as
Attended. An
auto Email Notication is send to concemed department.
7. The concemed deparment veries the completion and updates the status to Completed.
As-Is Process Issues
0 JMS support the identication and feedback capturing step of the Work Management cycle. The
system
does not support the work planning and scheduling step of the Work Management Cycle.
0 No Work Management system which integrates between work demand, Material and Resources (HR)
availability, Work Clearance Management (Outages, Caution Pennits, Work Permits) and Finance.
0 The Maintenance Analysis cannot be performed on Asset cost and Asset Material usage.
~ No insight into the reasons of work request no being executed inside the SLA related time span. Which
makes it difcult to optimize the processes.
Consequence:
_<";>_-;.<+ _ 4 ._ "
0 Material and tool availability status is not available during planning before the actual work starts on
site.
I Costs are not booked to specic Assets, and as a consequence the costs of each Asset over the life-
cycle of
that Asset is not clear.
0 It requires huge manual effort to prepare the Yearly Maintenance Plan.
0 It requires large manual effort to prepare the Operational and Management reports.
0 Tracking of Cost, Failures etc, is not properly reected on Plant, Equipment, Plant Section or
Department-
wrse.
No plan/actual report available for costs/materials to optimize the planning of RCM Tasks
' ii. ~'; /1 , I

KPIT Vesta
15. Process Requirements
Process Requirements
0 One common Corrective Maintenance process followed by all Departments.
1 One Maintenance System to manage each phase of the work management cycle and provide visibility
into
the entire Maintenance process.
I Integrate the Maintenance Process with:
o Work Clearance Management (Outage, Caution Permit, Work Permit)
o Material Management
o Financial Systems
0 Internal resource availability
o Management of external Services
0 Corrective Maintenance history in terms of Failure information and cost linked to each asset over the
entire
life cycle of the Asset.
0 Insight in the plan/ actual difference in terms of hours and costs for Corrective Work.
I Failure reporting for each Asset/ asset type on the following KPls:
o Number of failures ( potential failure/ functional failure)
o Failure costs
0 Breakdown time
o Repair time
Reporting aggregation on
o Manufacturer
o Model number
Damage
Object Code
Preventive Tasks
System effect
0 System availability
0 Mobile devices shall facilitate the Work Assignment to Field Staff which allows for real time updates
and
makes all Asset and Order information available out in the eld.
Mobile devices shall facilitate the Work feedback from Field Staff on Conrmations and Activity
Reports.
This results in real time progress information, exact mapping of ofine time due to Maintenance/failures
and
a higher quality of Conrmation information.
OOOO
Condential DEWA_SAPgWAVE-3_Transmission_EAM_Blueprint_Corrective Maintenence_Final_Vl .1
"'57:. K -< S 1
J.,._.;:_?;f.3.. K PIT Vesta E
16. Guiding Principles
Guiding Principles
Notication Guiding Principles:
It is important that SAP Notications are utilized for the identication and reporting of all defects and
malfunctions.
A Notication forms the core of technical maintenance history.
Notications should be properly managed and closed as soon as the tasks are completed.
Notications must be populated with all the applicable master data and feedback.
Work Order Guiding Principles:
Work Orders will be used for planning and scheduling of all Maintenance Tasks.
Work Orders need to be attached to the lowest level of child-equipments possible to assure an accurate
Work and cost history.
Work Orders must be used to plan and consume all resources, spares, material and services
Conrmations will post actual times, costs and material usage to the Work Orders.
Work Orders must be managed and closed in time.
General Guiding Principles:
Clear roles and responsibilities must exist to ensure that the system is fully utilized.
Consistent and accurate reporting will highlight process short falls.
Processes must continuously be assessed and improved.
17 Process Assumptions
/
Process Assumptions
Transmission Power will ensure that Master Data is maintained according to Business Rules and create
centralized govemance across the different Departments.
Each Department will have multiple dedicated Maintenance Planners, Schedulers and Data Capturers.
A Maintenance Change Advisory Board (CAB) is established to manage future SAP related conguration
changes/developments.
The process of Extemal Service Procurement through SAP MM purchasing is previously implemented
and
currently used for all extemal services. The Purchase Requisitions and purchase Orders created in this
process will be linked to the Work Orders to reect the history and costs of external service for each
asset.
DEWA Activity Types and Activity Type rates for Cost Centers have been previously implemented in SAP
WAVE 2 and are maintained by the Finance Department. These existing Activity Types will be extended
and the Activity Types rates will be maintained for TP Cost Centers.
Condential DEWA_SAP_WAVE-3_Transmission_EAM_Blueprint_Corrective Maintenence_Final_Vl.l
KPIT Vesta A r.::::;::;-;.,:.<::

0 The Cost Center Structure is previously implemented in SAP Wave2 and is currently utilized in the
nancial
modules.
0 Costs on the PM Orders will be settled using an Automatic Background Job the frequency of the
settlement
is dened by Finance.
Q A Report of all Cost settlement Errors will be produced at the Finance Ofce who Wlll be responsible
to
communicate and resolve any errors with the appropriate persons.
18. Process Terminology
Process Terminology
Description
EAM
Enterprise Asset Management
GUI
Graphical User Interface
PM
Plant Maintenance
PRT
Production Resource tool
MM
Material Management
HR
Human Resources
FI
Finance
CO
Controlling
PR
Purchase Requisition
PO
Purchase Order
PTW
Permit To work
MRQ
Material Requisition
WCM
Work Clearance Management
MRS
Multi Resource Scheduling
TECO
Technical Completion of Work Orders
SLA
Service Level Agreement
GRV
Goods Receipt Voucher
Condential DEWA_SAP_WAVE-3_Transmission_EAM_Blueprint_Corrective Maintenence_F1nal_Vl l
(TPEAM-03) Page 62 ot 77
<13>f'~ KI=IT' Vesta

V \\l\1l\
<;
J
19 Process Results and Benets
Process Results and Benets
General Results and benets.
One integrated system for all Maintenance related data, processes and Departments which integrates
the
following objects in the Work Management process:
o Assets
o Work Orders and Notication linked to Assets
HR information and Employee availability
Material Management
External Service Procurements
Work clearance Management and Permits
OOOO
One common Work Management Process enables DEWA Transmission Power to use:
o Utilization of common Reports for all Departments and Sections
0 Overall Business Process Transparency
Increase of Control and Consistency
Improve Operational Inefciencies
OO
Work Management Benets:
I
Required elds like the Maintenance Work Center Responsible, Planner Group, Plant Section, Location,
Cost
Center etc. are populated automatically in the Notication and Order from the reference Technical
Object.
This minimizes the workload and the chance of errors.
Material Reservation for Order can be automatically created on the release of an Order and thereafter if
any
new Material is added in the Order.
Order logs for warning & errors related to Material Availability, Costs, Release etc., at different stages of
Order can be analyzed.
The status of Material availability will be available during the Order Planning and Scheduling process
before
the actual work starts on site.
The availability of PRTs is visible during the Order scheduling stage before the actual work starts at site.
Standard Service Masters can be created for Extemal Services in the Order and hence will save time. In
case
of Outline Agreements or Contracts, the required services can be copied from the Contract. Hence the
contractor job will be linked to maintenance Order for which he has provided services.
Loading of different maintenance work centers will be known before placing the Order, hence more
realistic
Planning and Scheduling of work.
Orders on Linear Assets can be seen graphically with all the details like Description, Status, Technical
Object,
Notications, Permits, Materials, Goods Movements, Operations, Conrmations and costs along the
length
of the Linear Assets.
Mobile devices shall facilitate the Work Assignment to Field Staff which allows for real time updates and
makes all Asset and Order information available to the necessary people on site.
Mobile devices shall facilitate the Work feedback from eld staff on Conrmations and Activity Reports.
This facilitates:
o Real time work progress information
o Exact start and end times of maintenance work on Assets are captured for Orders and can be used to
determine the unavailability due to Maintenance Work.
0 Improved quality of technical and Conrmation feedback.
KPIT vesra J
Asset Performance advantages
1 Detailed history of every Asset in terms of technical ndings, causes, tasks, breakdown, materials and
costs.
This infonnation serves as input to optimize the RCM tasks and frequencies.
0 Automatic planning of Time-based and Condition-based RCM tasks is possible in Order to improve
Eqgpment availability.
20. RICEFW Summary
Interface
Role Usage
Information Required
Funct Spec
Comp?
SCADA
Plant
Maintenance
Automatic trigger of Corrective Notications in
SAP in the event of SCADA alarm.
Further information is captured in the SCADA
integration Blueprint.
No
Conversion
Role Usage
F unct Spec
Comp?
Open NODs and
Historical Asset
Performance
Plant
Maintenance
Any open work that needs to be managed after
cutover and the asset history in terms of failures,
abnormalities, major alarms & available cost data
N/A
Enhancements
Role Usage
Funct Spec
Comp?
Mass change of Order
User status
Plant
Maintenance
Detail Functional & Technical Specication during
Realization phase.
No
Notication Priority
Plant
Maintenance
Show full priority description, based on real time
denitions
No
Mass upload of work
Orders
Plant
Maintenance
Realization phase.
No
Material Management
Plant
Maintenance
System should not allow to delete the component or
change the quantity in maintenance Order once it is
issued from Stores.
Once MRQ approval has been provided, user should
not be able to change the quantity.
No.
Automated update of
Work Center Average
Activity type rate
based on I-IR changes.
Plant
Maintenance/
HR
An enhancement is requested to make the update of
Average Work Centre Activity Types automated
based on changes in the HR Module data of
Employees.
No
Maintenance Order
TECO.
Plant
Maintenance
During the TECO of Order, system should check for
any open PO and should not allow TECO without
closure of the same.
No
This is not in line
with best practice
and is highly
Condential DEWA_SAP_WAVE-3_Transmission_EAM_Bluepr-int_Corrective Maintenence_Final_Vl .1
(TP~EAM-03) Page 64 of 77
"::<>j;-Q go _ r
KPIT vase :..:a.:;.::.... J
recommended;
practically it is
not possible to
nish the job
without receiving
the required
Material /
Services.
Validation of Priorities
Plant
Maintenance
Vaildation of Priorities based on Category selection.
Only certain Notication Categories can be used in
conjunction with certain Priorities. If incorrect
combination is selected, system will issue an error
message.
No
Forms
I
Role Usage
Funct Spec
Comp?
Shop papers for
Notications/Orders:
-Internal service
-External service
Plant
Maintenance
Realization phase.
No
Workow
Role Usage
Funct Spec
Comp?
Material Management
Plant
Maintenance
l. Detail Functional & Technical Specication
during Realization phase.
2. Linking to the Purchasing Approvals
(including civil outsourcing contracts),
which are already developed and in use in
the current SAP Wave 2 system.
No
Approval of Capacity
request from other
Department.
Plant
Maintenance
Approval from a Work Center when another
Department requests their capacity.
No.
Notication
Plant
Maintenance
l. Workflow to Contractors to notify of
Corrective work under Warranty.
2. Workflow to notify the person who created
the Notication when their Notication is
rejected.
3. Critical Alanns (Workow Auto email from
SAP to predened list)
4. Transmission Trip (Workow send Auto
email from SAP to predened list)
5. Generation Trip (Workow Auto email
from SAP to predened list)
No
Condential DEWA_SA
P_WAVE-3_Transmission_EAMABlueprint_Corrective Maintenencc_Final_Vl .1 (TP-EAM-03) Page 65 of
77
tiI1H->~'-willW71 Dtbulbchukqlwummahnrlg *
21. Reports
21.1 SAP Standard Reports
Reports (Management Information System) are crucial in helping a Maintenance organizations to
evaluate its success and
progress toward long-term Maintenance organization goals. It also helps an organization to monitor
progress by providing
an insight of performance over time.
There are three types of reports which can be utilized in SAP EAM module to evaluate the Maintenance
Performance of
organizations:
0 Transactional Reports (e.g. Standard List Edit Reports)
o SAP Standard Transaction Reports
0 SAP Custom Transactional Reports
0 Maintenance Information System Reports
0 SAP Standard Maintenance information system reports (PMIS)
o SAP Custom Maintenance Reports
Q Customized / Business Intelligence Reports (BI Reports)
The following Standard Analyses (PMIS) reports will be available from the system for the Corrective
Maintenance
Process:
Standard SAP Report
Transaction Code
Location evaluations based on the location of the technical
object.
MCI l
Planning evaluations based on the planner group.
MCI2
Object Class ~ evaluations on the basis of the technical object
class.
MCI3
Manufacturer evaluations based on the manufacturer of the
technical object.
MCI4
Damage Analysis evaluations based on the Notication type,
damage, cause of damage.
MCl5
Object Statistics ~ statistics of the technical object.
MCI6
Breakdown Statistics MTTIUMTBR
MCI7
Note: Will be replaced by custom
MTTR/MTTF Report for Transmission.
Cost Evaluation evaluations based on Order type, planned costs,
actual costs, material costs and labour costs.
MCI8
Note: Although the PMIS reports are still available, they are often regarded as conventional and have to
some extent been
replaced by newer List Edit and Bl Reports.
Condential DEWA_SAPgWAVE3_Transmission_EAM_Blueprint_Corrective Maintenence_Final_Vl.l
/-< t
\_>>-t..<> t
I<I="' Vem
The following Reporting Requirements are identied for the DEWA Transmission Power Corrective
Maintenance
Process.
Standard SAP Report
Transaction Code
List editing of maintenance Notications in change mode
lW28
List editing of maintenance Notications in display mode
IW29
List editing of Tasks in change mode
IW66
List editing of Tasks display mode
IW67
List editing of Items (failure codes)
IW68
I
l List editing of items change mode
IW64
List editing of items change Display mode
IW65
List editing of maintenance Orders in change mode
IW38
List editing of maintenance Orders in display mode
IW39
Display Orders and operations
IW49N
Change Orders and operations
IW3 7N
Display Actual Conrmation
IW43
Display conrmations
IW44
Display List of Conrmations
IW47
Display Measurement Document
IKl3
List Display of Measurement Documents
IKI7
Display Document Flow
IWl2
List Display of Operations
IW49
Multi-Level List Display of Notications
lW30
Multi-Level List Display of Orders
lW40
List Editing-Display ltems (Damage Analysis such as Trip
analysis)
IW69
List Editing-Display Activity
IW65
Display Order Group
KOH3
Condential DEWA_SAP_WAVE-3_Transmission_EAM_Blueprint_Corrective Maintenence_Final_V1 1
(TP EAM 03) Page 67 of 77
<i.>>:<
<3
Vesta
E17
t,-4: vl-4: =l-4.4-A-Wu!
llmaillachtntqlllldll ilrnrlg
Standard SAP Report
Transaction Code
Display Component List
| IW3L
List of Goods Movements for Order
I IW3M
MTTR / MTTF for Equipment
MC] B
MTTR / MTTF for Functional Location
MCJ C
21.2 Report Requirements
The exact Report requirements are specied in a separate reporting Blueprint. The following high level
requirements are
identied during the Corrective Maintenance Workshops.
S = Standard SAP Report
C = Custom Report
Sl. No
Report
Name
Report
Description
Purpose of
the Report
Frequency
Type
Severity
BBP3/
Sl
Notication
Report /
KPls
Status Report
for
maintenance
requests and
abnormal
events
Management
of
Notications
Daily
Operational
Critical
BBP3/
S2
Orders
Status repon
for
Maintenance
Orders
Management
of Orders
Daily
Operational
Critical
BBP3/
S3
Order
Compliance
Compliance to
schedule
Compliance
SLA report
Weekly/Monthly
Analytical
Critical
BBP3/
S4
Backlog
Order Backlog
overview
Overview of
the Backlog
Daily Weekly
Monthly
Operational /
Analytical /
Planning
Critical
BBP3/
S5
Plan versus
Actual
Order Plan
versus actual
for man-hours,
Costs and
Tasks
Optimize the
plan values
for tasks
Monthly/Y early
Analytical
Critical
Condential DEWA_SAP_WAVE-3_Transmission_EAM_Blueprint_C0rrective Maintenence_Final_Vl .l
(TPEAM-O3) Page 68 of 77
KPIT Vesta W J
BBP3/ MM
C1
Order Material
status
Tracking
Report
required to
integrate
Work Orders
and Material
Status
Monthly/Y early
Analytical
Critical
BBP3/ Failure report
S6
Notication
Failure
reporting
Failure mode
reporting
Monthly/Y early
Analytical
Critical
BBP3/ Linear
C2 Failures
Linear
characteristics
Notication
# of failures
per KM per
manufacturer
(linear
descriptive
characteristic)
*Not the
history of
linear
characteristics
is required
Monthly/Yearly
Analytical
BBP3/ Asset
C3 Availability
report
Notication
Asset
availability
Asset
availability
Monthly/Y early
Analytical
Critical
BBP3/C4 Asset
Lifecycle
Report
Asset lifecycle
Cost Reporting
Track Asset
Lifecycle
Costs
Monthly/Y early
Analytical
Critical
BBP3/C4 MTTR/MTTF
Report
MTTR/MTTF
Report
Tracking of
Failures and
Reliability
Ad Hoc
Operational /
Analytical
Critical
21.3 Management Reports & Dashboards
Sl. No Reportl
Dashboard
Name
Report /
Dashboard
Description
Purpose of
the Report /
Dashboard
Frequency
Type Severity
repair time
report
BBP3/Dl MonthlyAsset Monthly Asset
repair time
report
On asset level
the count of
activities +
total
time(wrench
time)
Monthly
Analytical Critical
BBP3/D2 Corrective
Follow Up
from PM
Report
Corrective
Follow Up
work from PM
Report via
document flow
This report
will highlight
the
effectiveness
of the current
Monthly
Analytical Critical
Condential DEWA_SAP_WAVE~3_Transmission_EAM_Blueprint_Corrective Maintenence_Final_Vl .l
KPIT vesta -N)

preventative
maintenance
lan
Note: Additional Reports/Dashboards will be covered in the Reporting Blueprint based on the As-ls
Dashboards.
21.4 Reports, Management Reports & Dashboards FIT GAP
0 Will be covered in the separate Reporting BBP.
22. Data Consideration
The following data must be in place to ensure that these processes will function properly:
Plant Maintenance
o Functional Locations
0 Equipment including PRTs.
Asset Initial values
Catalogs
Partners
Work centers
Materials
Work Center Activity Types
Cost Centers
Permits
Outsourcing Contract
Asset Historical Performance
OOOOOOOOOO
Condential DEWA_SAP_WAVE-3_Transmission_EAM_Blueprint_Corrective Maintencnce_Final_Vl 41
Q2
zfl
41>
23. Organizational Impact
H O KI=lT Vesta J
Impact As Is
To Be
Management of
Malfunctions/Failures
Operation monitors NODs
Maintenance responsible for Notication
Management. Combined responsibility
between Central and Department Planner.
One Role in some Departments
and separate Roles, possibly
different persons, in other
Departments
Distinction between Planning and
Scheduling
A distinction between the Planning and
Scheduling Role will be made, these
separate Roles will possibly be executed by
one person for some Departments and by
different persons for other Departments.
Currently there is no clear distinction
between Schedulers and Planners.
Centralized Planning No Centralized Planning
It is has been decided to move to a more
Centralized Planning approach.
Cost are not administrated on
Assets.
Administration of Maintenance and
Cost data on Asset level
The effort to manage and maintain all data
in SAP, might require more
administrative/planning personal.
Summary of Changes
Notications in SAP.
some of the Departments.
0 The Central and Department Planner are responsible for the Management of open
Malfunction/Failure
0 A distinction between the Planning and Scheduling role will be made in all Departments, these
separate roles
will possibly be different persons. Currently there is no clear distinction between Schedulers and
Plarmers in
~ A Central Planner is responsible to align the maintenance work between the different Transmission
Departments and Operations Department. The Central Planner is also responsible for the efcient
assignment
of Notications to the responsible Department in addition to managing Master Data.
I Communication between the Maintenance and Operation Departments in relation to Outage and
Permits
planning will happen through SAP WCM with a direct link to SAP Work Orders.
0 DEWA Transmission Power requirements is to monitor and track Asset Perfonnance, Failures,
Maintenance
History and Cost information on Asset Level (Parent/Child). Currently, parts of this information for e. g.
costs, are managed on higher aggregation level such as on Cost Center level. The effort to manage and
maintain all data on this lower level of detail in the SAP system might require more
administrative/planning
personal. This requirement is often underestimated by organizations.
KPIT Vesta _ <1

24. Process Decision Records
Date
Decision
16-07-2014
SAP will replace JMS for DEWA Transmission Power.
l 6-07-2014
DEWA Transmission will utilize one Corrective Maintenance Process for all Departments. This
process will be supported in SAP by one Corrective Maintenance Notication and one Corrective
Maintenance Order.
20-10-2014
DEWA Transmission Work Centers consist of a group of employees with different Grades. For
Order Cost Planning, a default average Rate will be dened for each Work Center. Actual costs
are calculated based on the exact Connnation made by each employee at their specic
Grade/Activity Rate.
07-01-2015
Operational Account Assignment is required to provide plan/actual cost comparison on task
level.
O7-01-2015
A Central Planner is responsible to align the maintenance work between the different
Transmission Departments and Operations Department. The Central Planner is also responsible
for the efcient assignment of Notications to the responsible Department in addition to
managing & administering Master Data.
12-02-2015
DEWA Transmisison Power will use a common set of priorities: High, Medium, Low for all
Preventive and Corrective Maintenance Tasks.
Real-time Priorities will be specic for the Category identied by Management as per the
attached list.
Condential DEWA_SAP_WAVE-3_Transmissi0n_EAM_Blueprint_Corrective Maintenence_Final_Vl.l (TP-
Kprr Vesta W
25. Integration Test Requirements
Integration Test Requirement
Data to use/test
Fund Management
v Work Order
Finance Integration
0 Maintenance Orders
0 Cost centers
I Activity Types
0 Funds Management
0 GL Accounts
~ Cost elements
0 WBS Element
I Finance Asset Processes
0 Acquisition
0 Sell
0 Scrap
c Disposal
0 Refurbishment
Equipment and Assets
Materials Management Stock Material
Reservation
Maintenance Orders
User may not add Components to an approved MRQ. Instead
user needs to create an additional Reservation if additional
quantity is required.
Materials Management Non Stock Material
Purchasing
Maintenance Orders/Contracts
Materials Management Services and standing
Contracts.
Maintenance Orders/Contracts
Materials Management A Retum to stores
Maintenance Orders
Materials Management - Refurbishment
Refurbishment Orders
Warranty Process
Plant Maintenance Orders/Finance/Materials Management
Workow
Purchasing approvals
Work Permits
Work Order
Functional Locations
Finance Activity Planning
Activity planning for Work Center Cost Centers
Mobile Syclo Integration
Notication
Work Order
SCADA Integration
Notication Creation
WCM
WCA and Order Integration
Condential DEWA_SAP_WAVE-3_Transmission_EAM_Blueprint_Correetive Maintenence_Final_Vl .1
\_,-219L449 A-2)-A->614!
Ihhb\UDti:1ntgl\lloLv1.lr0\l\j
,
a
7
<35"? Q Kprr Vesta W re-"e~=-~+=
llblibclttitglulotovlklhnllq
MRS | Work Order and WCM integration
DMS ] Task list, Order, Notication
Oil Lab Processing | Oil Sampling & Testing
Preventive Maintenance I Preventive Maintenance
26. Issues
N 0. Issue Description Resolution/Status
N/A
27. Next Steps/Actions
Task
Owner
Target Date
Complete
Date
Address all RICEFW items listed in the RICEFW
Summary.
All
To be conrmed
During
Realization
Denition of a Cutover Strategy:
0 Open Corrective work from RCM Tasks in
progress
I Open NODs
Open Commitments
Wave 3 Team/
Transmission Power
To be Conrmed
Life Cycle Costing (LCC) documentation to be
conrmed.
EAM Team
To be Conrmed
Historical Data reporting approach to be nalized
as pan of Cutover Strategy.
DEWA IT
To be Conrmed
Detailed report discussions (As~|s & To-Be)
All
To be connned
During
Reporting
BBP
Workshops
:'?_ __
1<=~T vem E177 J
28. References
Related Documentation Document #
DEWA_SAP_WAVE- 1
3_TP_OCM_Planning_and_Scheduling_Processes_05 1 120 14_v0.3
NOD_GQP-52Flowchart 2
NOD_GQP~S2
flowchartvsd
Management of NODs 3
Management of
NODs.vsd
4
PTW process
PTW Process.pdf
Procedure for attending alarms Rev2 5
Proced u re for
attending alarms-Rs
Work center HR Activity and Rate 6
Work center HR
| Activity and Rate.xls:
TP Maintenance Planning Flowchart (WAVE3) 7
TP maintenance
planning 14Jan 15.
TP Notication Management Flowchart (WAVE3) 8
Notification_ 14 Jan
lS.vsdx
N0ticati0n_15Feb2015.xlsx 9
Notification_15Feb
20154x|sx
Condential DEWA_SAP_WAVE-3_Transmission_EAM_B1ueprim_C0rrective Maintenence_Final*Vl .l
W
ik
Vesta gr-4:0-absal-u-14453-91 x
=-~.,~.\< \\A ~ = -. Qbolbclrliglulakortlovlg
29. Functional Gaps
The following gaps are being identied:
Gap | Description
G0]
Annual Planning on Designation not possible due to Work Center denition at Team
level.
30. Roles
Role
Description
Z_TPEAM_GEN:
General User
Display Master Data/Create Notications/Display Orders
Z_TPEAM_MAN:
Manager
Create Notications/Display Orders/ Display Master Data] Display MRS
Z_TPAM_TML:
Team Leader
Display:
v All Master Data
I Orders
0 MRS
Create/Change/Display:
0 Notications
Z_TPEAM_CPL:
Central Planner
All Master Data
Notications
Orders
Task Lists
Plans
~ Items
Display:
0 MRS
Z_TPEAM_PLN:
Depamnent
Planner
Task Lists
Plans
Items
Notications
Q Orders
Display:
0 All Master Data
I MRS
Z_TPEAM_PLA:
Planning Assistant
0 Notications
Condential DEWA_SAP_WAVE-3_Transmissi0n_EAM_Blueprint_Con'ective Maintenence_Final_Vl .l
J
KPIT Vesta w J
~ Orders
Display:
0 All Master Data
Z_TPEAM_ScD; Create/Change/Display:
Scheduler 0 Notications
0 Orders
0 MRS
Display:
0 All Master Data
Z7TpEAM_SUp; Create/Change/Display:
Super 0 Notications
User/Administrator I Orders
O MRS
0 All Master Data
Naming conventions for the above mentioned Roles will be dened in accordance with the current
DEWA Authorization
Roles.
31. Risk
Following risks are envisioned based on interactions with business & PMO and based on past experience
of System
Integration Team members.
Risk l Description I
R01 DEWA Transmission Power requirements is to monitor & collect asset performance,
Administrative/planning Maintenance history and Cost infonnation on Asset Level (parent/child),
currently
personnel requirement parts of this information for e. g. costs, are managed on higher aggregation level
such
as on Cost Center level.
The effort to manage and maintain all data on this lower level of detail in the SAP
system might require more administrative/planning personal. This requirement is often
underestimated by organizations.
Note: These risks are added to DARI for further follow up.
32. Additional Information
| N/A |
n
=-i 1-1.. - ___ i____ '_ _ ___
4
,3
1)
Mi M UN E
_ rt
V
at
EN."
___w>3_
M___E89__ as __
g|S_5l___:
/ Na
V HVW win yd
p\\
I/_
___H__
UUYQN
mM____
__U__% ___O_N__M_E SN
S5
t ' JV
X WR \ _ Q
if \
E
___N__
C El:
__u__<
Es
algal:
\ k I \;v
iv [W N iv
\ K I _Iv
_\__
_
Q>
f_ EIMN
___m__e_
___v______e___
m__|_>_<m|L____
.1
EM
P
H>
U__E_m
___>3_
_Q>=__g2__ __U___gm__ms_ Utes
____|_2<u'g__
V. 1 \\1"
HM
$\_\
_f
3,
f_ El"
E>8_
_g_H_2__8_ Emsgmz 0;
m|_2<m|__:
Mi wiux xx UV
_ I YQHF
m>
tE|wN
___>$_
maa B35 __
N|_>_<m|__I
mE__N___
___ _g__>_ __q_
___> g EB_a__8
__2___ ____
_____=__Eg an
Q an
_ m_g__&<

FreeOCR Notes

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

FreeOCR Notes

Uploaded by

Copyright:

Available Formats

FreeOCR notes

1<=-IT vwa Eff?

/<=-I-r v-ma E7157 J

Krrl-r Vesta W ,,,_,.t..,.u,..a..l..

Tasks Task description

order no. + opera!

Keir v-ma E57 .1

Kerr vesta E17 J

\'l:_;>."i~_-;<$ Kg]-f Vesta r_,_pv>Ltnrl-=.w-will J

\3>:*~e-<> KPIT Vesta W o4="L&B9l-u-A-H11-in J

Q..>."(~::<'> ](p:1T Vesta tt=~_t-=9 up-_~~=1t=

1<i=1-r v-ma E'I'7 J

KP/T vesta E17 J

KPIT vem E17 J

' ii. ~'; /1 , I

KPIT Vesta A r.::::;::;-;.,:.<::

<13>f'~ KI=IT' Vesta

KPIT vesta -N)

KPIT Vesta _ <1

You might also like