Neral Maintenance v0.7

Project Aarohan
200.1.03.04
BBP_Plant Maintenance_General Maintenance
Version: 0.5 7 (Signed off version to be 1.0)
200.1.03.04
V0.57 Classification: Internal Page 1 of 27
CHANGE HISTORY
Date Author Role Version Description
22/10/2021 Mohammed Ashif Consultant 0.1 Draft
25/10/2021 Mohammed Ashif Consultant 0.2 Updated the Process description
01/11/2021 Mohammed Ashif Consultant 0.3 Inclusion of KDS in BBP
08/11/2021 Mohammed Ashif Consultant 0.4 Separation of Permit system from this BBP
Addition of Cost settlement process in TO-
27/12/2021 Mohammed Ashif Consultant 0.5
BE section
Updated Planning & scheduling related
30/12/2021 Mohammed Ashif Consultant 0.6
sections and final review from CTM
18/04/2022 Mohammed Ashif Consultant 0.7 OEM Audit recommendations incorporated
SUPPORTING DOCUMENTS
Date Document Title Document Reference
22/10/2021 Inventory application REF-PM-08-V00
22/10/2021 Inventory Usage Application REF-PM-16-V00
22/10/2021 Work permit system with checklist and approval workflow PM-MKTG-12-V00
22/10/2021 History card of the equipment PM-MKTG-13-V00
22/10/2021 Part list inventory management (Warehouse) PM-MKTG-14-V00
22/10/2021 CP Maintenance PM-LAM-08-V00
22/10/2021 OFC Maintenance PM-LAM-09-V00
22/10/2021 Pipeline Maintenance PM-LAM-10-V00
22/10/2021 Work permit system with checklist and approval workflow PM-LAM-15-V00
22/10/2021 History card of the Pipeline sections PM-LAM-16-V00
22/10/2021 Part list inventory management (Warehouse) PM-LAM-18-V00
22/10/2021 ROW Maintenance PM-LAM-11-V00
200.1.03.04
REVIEW & SIGN-OFF
Name (Mr/Ms) Role Signature and Date

Prepared by
Mohammed Ashif Consultant
Reviewer – Accenture Module Lead

Abhishek Kumar Team Lead
Sridhar Mandadi SME
Sujeet Kulkarni SME
Reviewer - Business Core Team

Binoy D TheruvanBinoy T Core Team Member
Bhupendra Kumar Core Team Member
Gopal Mishra Core Team Member
SandeepKumar Dharampal Core Team Member
Amit Rathore Core Team Member
Approver - Business Core Team Module Lead
Binoy D TheruvanBinoy T Process Owner
200.1.03.04
Table of Contents
1. GLOSSARY............................................................................................................................................ 5
2. OVERVIEW............................................................................................................................................. 6
2.1. Business Event............................................................................................................................ 6
2.2. Assumptions and Dependencies...............................................................................................7
2.3. Visio Legend................................................................................................................................ 7
3. TO-BE PROCESS................................................................................................................................... 8
3.1. To be Process – Process Name / Description...........................................................................8
3.1.1. Process Description: (Brief Process sections and explanation)..........................................8
3.1.2. Process flow (Visio – Activity flow):.....................................................................................12
3.1.3. Process Steps:....................................................................................................................... 14
3.1.4. Process Variation (Brief description if there are more than one variation of processes as
per business units / Geographies etc.)..............................................................................................15
3.2. To be Process – Process Name / Description.........................................................................15
3.2.1. Process Description: (Brief Process sections and explanation)........................................16
3.2.2. Process flow (Visio – Activity flow):.....................................................................................16
3.2.3. Process Steps:....................................................................................................................... 16
3.2.4. Process Variation (Brief description if there are more than one variation of processes as
per business units / Geographies etc.)..............................................................................................16
4. IMPROVEMENT AREAS....................................................................................................................... 17
5. SAP REPORTS..................................................................................................................................... 17
6. GAP ANALYSIS.................................................................................................................................... 17
7. DOCUMENT ATTACHMENTS.............................................................................................................. 18
8. KEY CONSIDERATIONS...................................................................................................................... 18
8.1. Locations / SBUs where this Business Process is performed...............................................18
8.2. Integration Points...................................................................................................................... 19
8.3. Cut Over / Deployment Considerations...................................................................................19
8.4. Batch Processing...................................................................................................................... 19
8.5. Roles & Authorization............................................................................................................... 20
9. BUSINESS IMPACT.............................................................................................................................. 20
9.1. Key Policies/Operational Decisions.........................................................................................20
9.2. Key Changes for Adoption to Standard...................................................................................20
10. TEST SCENARIOS............................................................................................................................... 21
11. TRANSACTION LIST (S4 AND FIORI).................................................................................................21
12. ANNEXURE.......................................................................................................................................... 21
200.1.03.04
1. Glossary
Term Definition
HPCL Hindustan Petroleum Corporation Limited
PM Plant Maintenance
MM Materials Management
HR Human Resource
FICO Financial Accounting and Controlling
KDS Key Data Structure
BBP Business Blueprint
AMC Annual Maintenance Contract
SES Service Entry Sheet
WCM Work Clearance Management
PTW Permit To Work
WAP Work Approval
WCA Work Clearance Application
WCD Work Clearance Document
PR Purchase Requisition
PO Purchase Order
WO Maintenance Work Order
MTP Maintenance Planning
TECO Technically Completed
NOCO Notification Completed
WCD Work Clearance Document
GR Goods Receipt
MIGO Goods Movement Transaction code in SAP
WOCO Work Completed
MDM Master Data Management
MIT Material Issue Ticket
MIR Material Issue Request
WC Maintenance Work center
RCFA Root Cause and Failure Analysis
FMEA Failure mode effect analysis
MTTR Mean Time to Repair
MTBF Mean Time between Failure
PRT Production Resource Tools
WRICEF Workflow, Reports, Interface, Conversions, Enhancement and Forms
200.1.03.04
2. Overview
2.1. Business Event
Business Event
Please list the Sub-Process and Process for which this event is associated. Also, provide a few sentences defining the basic
functions supported by this business event.
Module: L1 Plant Maintenance
Process: L2 General Maintenance
Sub-
L3 ---
Process
Applicable Corporate Lubes Refineries Supply Operations and Distribution
Businesses Retail LPG Direct Sales Aviation Pipelines Gas Other Functions
Process:
This document covers the process related to General Maintenance
• Notification creation
• WO creation
Business • WCM Process for Permits
Process • Reservation and Issue of materials
Overview: • Reservation and Issue of Garage tools
• Issue and return of stock tools from tool room
• Activity and time confirmation in WO
• Technical completion (TECO)
• Settlement & Closure
200.1.03.04
2.2. Assumptions and Dependencies
Key Assumptions
Document key assumptions related to the business process.
No
Assumption Description
.
01 Order Type & Notification Types are maintained along with appropriate priorities
02 All external procurements and material handling will be covered in MM Module.
03 Stock items will be issued against the reservation number.
04 A separate document is available on Master data
05 Separate document is available for Work Permit System
Key Dependencies & Master Data Consideration

Document key dependencies related to the business process as well as third party systems.
No
Dependency Description
.
01 All required Material master data should be available in the system
All required PM master data like Work Center, Equipment, Function Location, etc. should be available in the
02
system
03 Required HR master data should be available in the system.
2.3. Visio Legend
200.1.03.04
200.1.03.04
3. TO-BE PROCESS
Process Description: (Overall Document level Process brief Description / Coverage)
3.1. To be Process – Process Name / Description
PROCESS CHARACTERISTICS
Process Trigger Maintenance Request (Notification)
Process Input Maintenance Details
Process Output General Maintenance Order
Process Owner Maintenance Department
Process Volumes ---
Process Frequencies ---
3.1.1. Process Description: (Brief Process sections and explanation)
Introduction on General Maintenance:
General Maintenance process will cover day to day jobs / activities viz. Housekeeping, Grass Cutting, Gardening,
Issue of Consumables, loading / unloading of materials, etc. at work stations / locations. Maintenance jobs which
are not falling in any of the defined maintenance processes viz. Corrective, Preventive, Breakdown, etc. can be
covered through General Maintenance work order.
General maintenance process has the below key transactional data for recording the maintenance details:
1) Maintenance Notification
2) Maintenance Order
Maintenance Notification:
The Maintenance request is raised through a maintenance notification.
Figure 1 : Notification Screen in SAP - Header and Item level

200.1.03.04
While creating a maintenance notification, basic information like Problem description, Equipment / Functional
location details, Priority, Object part (if known at this stage), etc. can be filled in.
While closing a maintenance notification, further information like the Damage information against the Object part,
Cause of damage, Remedy details (if applicable) can be filled which can be used for FMEA analysis in future
stages.
Maintenance Notifications are converted to Maintenance Order by the maintenance planner for executing the
maintenance job. However, there could be maintenance activities, which do not warrant any significant resource
utilization. Such activities can be performed through a notification and no maintenance orders need to be created.
After the notification is processed, it can directly be closed.
Maintenance Order:
Maintenance Order are usually created by the planner with reference to a maintenance notification. Direct
maintenance order can also be created which will create the maintenance notification automatically in the
background. Direct maintenance order is usually created if the maintenance request is from the maintenance
team.
Figure 2: Order Screen in SAP - Header and Item level

Maintenance order can capture information like planned and actual dates, list of activities to be performed, Person
responsible for each activity, Spares and services required for maintenance, Planned and Actual Cost for
Maintenance, etc. A single maintenance order can be linked to multiple maintenance notifications.
Maintenance order will help to capture the expenses carried out on individual equipment, functional location, and
at plant level. Maintenance details are digitally recorded which can be used as a reference for future maintenance
order.
General Maintenance Process:
(Reference to Work permit in the below visio diagrams is only for representation purpose. A separate BBP will be
presented for Work Permit, LOTO and their integration with Work Orders)
200.1.03.04
Figure 3: Maintenance Process flow
Figure 4: Permit Process Flow (Without LOTO process)
200.1.03.04
Figure 5: Permit Process Flow (With LOTO process)
1) Notification and Order Creation
General Maintenance process may start with a Notification or a work order. Applicability of either or both of them
depends on the following: -
 If Operations intends to intimate Maintenance about a job they may create a notification. The Operation
manager will release the notification validating and confirming the need of maintenance.
 Upon receiving released notification, if the Maintenance Planner determines that the job requires planning
of resources then a general work order will be created from the Notification.
 If the Maintenance planner is of the view that completing the aforesaid job doesn’t involve significant
resource consumption, the same can be closed through Notification only. In this case, no Work Order will
be created. The planner will update the Notification for FMEA, no cost will be captured for the job.
 If the Maintenance Planner creates a General work order on his own for a job then a Notification will also
be created automatically in the background by the system which will capture FMEA on closure of work
order.
2) Planning of WO
A WO is created by Maintenance Planner from Notification released by Operations Planner or independent of it.
Planning Activities can be carried in a WO by a Maintenance Planner or Executor either before or after Release
depending upon authorization of user.
200.1.03.04
Planning activities consist of, attachment of task lists, Planning of Labor resources, Planning of Work centers,
Stock item reservation, Tools and Tackles reservation, Reservation of Production Resource Tools (PRT: like
crane, forklifts, etc.), RPO creation, PR preparation. PR and RPO related activities are done in MM module and
WO no. is entered for reference.
3) Request for Work Permits
A WO is ready for execution of tasks after it is released. A Permit and LOTO can be obtained by executor against
the WO.
4) Issuance of Tools / Garage Equipment’s
Garage Tools: Utilization of HPCL owned Crane, Forklifts, heavy vehicle etc. for work order operation is done
through PRT application in SAP. A crane is reserved for a specific duration under a WO operation. Garage In-
charge runs the report and get to know about all the reservations for allotment.
Tools: Tool reservation process is like warehouse material reservation/Issuance process in which a tool is
reserved for a WO operation which generates an MIT/MIR (reservation no in SAP). Person carrying the MIT is
issued the tool for usage in maintenance activities. It is returned after completion of work. Tool Room In-charge
makes entry in SAP for return against the return reservation no.
5) Issue of Materials for WO
Materials required for WO will be drawn from stores with reference to order no. / reservation no. For non-stock
Material, GRN is created in MM module with WO reference.
6) Closure of Permits
After completion of tasks, work permits and LOTO closure is carried out by executor.
7) Confirmation of maintenance activities
WO time confirmation is an activity done by executor to confirm the completion of task. Time confirmation can be
either partial confirmation (Sys. Status PCNF) or full confirmation (Sys. Status CNF). WO Confirmation
(CNF/PCNF) is mandatory for Technical completion (TECO) of WO.WO time confirmation is done by executor
after completion of a task or all the tasks in a WO to record the total time taken. Final Time confirmation (Full
Confirmation) is prohibited in case of any open Work permit or LOTO against the WO.
8) SES entry for booking external services:
Service Entry sheet will be created for entering consumption of external services with WO reference no.
9) Update Technical Findings and Technical Completion of WO
Any technical findings such as damages/defects and causes (if applicable) will be maintained in maintenance
notification / WO for equipment history. All the activities requested in the notification will be completed and will be
updated in the notification. Once technical findings are updated, the order will be Technically Completed (TECO)
by concerned person and simultaneously Notification Completion (NOCO) will also be updated in the system
against the notification created
10) Cost Settlement and Business Completion of WO (FI/CO)
Cost of any financial transaction related to a work order remains at Work order itself until settlement is not caried
out. The cost recorded in WO is settled against a cost center through settlement process. The Cost settlement will
be done as per the settlement rule defined in the WO which is defaulted from Equipment / Functional Location’s
cost center, the same can also be modified in WO. Cost Settlement process is executed by FICO and can be
carried out at any stage after the release of WO. Once all the cost in WO is settled to a cost center and WO is in
TECO status, the order can be moved to business completion status which signifies that the WO is fully closed,
and no further transactions are possible against the WO.Cost of any financial transaction related to a work order
remains at Work order itself until settlement is not caried out. The cost recorded in WO is settled against a cost
center through settlement process. The Cost settlement will be done as per the settlement rule defined in the WO
which is defaulted from Equipment / Functional Location’s cost center, the same can also be modified in WO.
Cost Settlement process is executed by Finance & Costing team and can be carried out at any stage after the
200.1.03.04
release of WO. Once all the cost in WO is settled to a cost center and WO is in TECO status, the order can be
moved to business completion status which signifies that the WO is fully closed, and no further transactions are
possible against the WO.
Workflow Process
Workflow process is driven by Work center (WC), Planner group (PG) and Person responsible. Depending upon
the inputs provided in WC, PG and Person responsible fields, WO will be made available in Dashboard based
inbox. A WO will go through the following stages sequentially.
1. Created & Release (approved)
2. Work in progress (optional)
3. Work Confirmation / Completed
4. Certification by Operations (optional)
5. Technical Closure
6. Cost settlement and Final Closure
Above stages of WO will have HPCL specific statuses (User Status) and SAP standard system statuses in
combination to map the existing practices.
Major Key Data Structure / Master Data
Following Data structure will be created to suit HPCL Processes.
1. Notification Type & its number rangers
2. Order Type & its number ranges
3. Activity type (To further classify the type of general work)
4. User Status
5. Planner Group
6. Work center
7. Functional location Master
8. Equipment Master (with Linear details if applicable)
9. Catalog Profile (for recording the RCFA codes), etc.
KDS document will include the details on the above KDS points.
General WO relevant standard reports can be accessed with below transaction codes:
Sl. No SAP Transaction code Report Description
01 IW38 / IW39 Order Report
02 IW28 / IW29 Notification Report
03 IW37N / IW49N Order Operation Report
04 IW69 Equipment History Card
05 MCI2 Manufacturer Analysis
06 MCI4 Planner Group Analysis
07 MCI8 Cost Analysis
Business Benefits
 Monitoring of General maintenance process starting from creation of notification to closure of
maintenance process.
200.1.03.04
 Permit Process is integrated with WO.
 Effective monitoring of maintenance KPI’s.
 Readily available warranty information while creating a work order
 Maintenance expense can be tracked at equipment / functional location level
 Duplication of maintenance activity is avoided.
 Enables systematic recording of historical data pertaining to equipment(s).
 Optimized Inventory of spares.
 Enhanced reporting’s of maintenance works through SAP Plant Maintenance Information System
 Well Integrated with MM / FI-CO modules
 Well Integrated Document Management System
 Digitalized knowledge management
 Overall maintenance information is online and thus paperless environment can be achieved.
 Enhanced user experience and mobility through FIORI Apps
200.1.03.04
3.1.2. Process flow (Visio – Activity flow):
200.1.03.04
3.1.3. Process Steps:
SAP Process Steps with Role / Executioner of the step

Proposed Business Process Description
Document future To-Be process based on system requirements. Note which tasks are system vs. manual
transaction. Also, cross-reference the number of each task to the number of steps in the process flow
diagram.
SAP
No. Activity / Task Name Activity / Task Description Transaction Role
/ Non-SAP
Notification
Create Maintenance Report the equipment maintenance request
10 IW21 Requestor/
Request Notification through Notification in SAP
Operations
In this step, the maintenance request can be

20 Release Notification reviewed by the Operation manager and decision IW22 Operations Manager
on creating General WO can be taken
Create General Maintenance Order with

Create a reference to Maintenance Request Notification IW22 / IW31
30 Maintenance Planner
Maintenance Order and select appropriate PM Activity type in WO. / IW34
Attach any relevant document if required.
Plan Operations
(Maintenance In this step User can plan maintenance activities,
Activities), resources resources & external services, Tools / Tackles,
40 IW32 Maintenance Planner
& external service Garage equipment if required, to execute the
requirements in the general maintenance.
order
In this step, the Order is getting released for

50 Release Order IW32 Maintenance Planner
execution.
Request the permit using the customized work

permit system in SAP. Below actions can be
Customized Work done in Work permit system: Maintenance
60 IW32
Permit System 1) Approval / Rejection Work Permit Executor
2) Lockout / Tagout of Equipment’s
3) Renewal of work permit
In this Step - required materials/spares/tools &
Issue tackles are drawn from the store, against the
materials/spares/tools reservation number generated through the
70 MIGO Stores
tackles against the maintenance order. PRT booked in WO
order reservation operation will be allotted for WO by Garage In-
charge.
Maintenance
80 Execute Job at Site Work is executed at the site. Non-SAP
Executor
200.1.03.04
Record the Maintenance activities performed
IW41 / IW42
Confirmation of WO (confirmation of WO operations). Enter the Actual Maintenance
90 / IW44 /
Operations Hours (Optional) for executing the work. Executor
IW45
Confirmation can be revoked (if required).
Create Service Entry Sheet (SES) for the

external services. The details of resources Maintenance
100 SES Entry ML81N
provided by the external service is recorded in Executor
the Service Entry Sheet (SES).
Update Technical In these steps, technical findings, like details and

Maintenance
110 Findings & Complete causes of the maintenance request (if IW22
Executor
Tasks in Notification applicable), are updated in the Notification.
Once all the operations are performed Technical

Completion of Order (TECO) is done.
With the Technical confirmation of the order,
Technical Completion Maintenance
120 Completion of Notification (NOCO) is done IW32
of Order Executor
automatically if complete notification checkbox is
checked during TECO. TECO can be revoked (if
required).
The cost recorded in WO is transferred to cost

130 Settlement of WO KO88 Finance / Costing
center as per the settlement rule in WO
Business Completion After full settlement of cost from WO to cost

140 IW32 Finance / Costing
of WO center, WO can be fully closed
3.1.4. Process Variation (Brief description if there are more than one variation of
processes as per business units / Geographies etc.)
NA
3.2. To be Process – Process Name / Description
PROCESS CHARACTERISTICS
Process Trigger ---
Process Input ---
Process Output ---
Process Owner ---
Process Volumes ---
Process Frequencies ---
3.2.1. Process Description: (Brief Process sections and explanation)

NA
200.1.03.04
3.2.2. Process flow (Visio – Activity flow):
NA
3.2.3. Process Steps:
NA
SAP Process Steps with Role / Executioner of the step
Proposed Business Process Description

Document future To-Be process based on system requirements. Note which tasks are system vs.
manual transaction. Also cross-reference the number of each task to the number of steps in the process
flow diagram.
SAP
Transaction /
No Activity / Task
Activity / Task Description Non-SAP (Other Role
. Name
system or
Manual)
10 --- --- --- ---
3.2.4. Process Variation (Brief description if there are more than one variation of
processes as per business units / Geographies etc.)
NA
200.1.03.04
4. IMPROVEMENT AREAS
Expectations with the new SAP system

Define key business scenario specific improvement areas expectation in the To Be processes discussed above. Avoid writing
generic requirements here. Also document to be process step reference If improvement is captured as a specific step in process flow
above
Sl. Improvement / Expectations Mitigation To Be Step No Remark
No (Yes/ No) Process
Section No
01 Equipment level cost analysis Yes 3.1.1 NA NA
and other reporting’s
02 Integration with MM / FI / EHS Yes 3.1.1 NA NA
module
03 Integration of Work Permit in Yes 3.1.3 60 NA
WO
04 Integration of Document Yes 3.1.1 NA NA
Management System
05 Extraction of reports as per Yes 3.1.1 NA NA
selected time period, Schedule
Frequency, location, equipment,
RCA etc.
06 Option to enter Root Cause Yes 3.1.3 110 NA
Analysis details and generate
reports
07 Maintenance Dashboard Yes 3.1.1 NA NA
Showing pending actions for
users
5. SAP REPORTS
Sl. HPCL Reporting requirement SAP Report Description Gap between
No Transaction HPCL
code requirement
and Standard
SAP Report
(Gaps
identified here
should be
added in
section 6)
01 Expense Main Nature of Expense --- --- GAP
02 Expense Section IW38 Order Report ---
03 Expense Workorder Activity MCI8 Cost Analysis ---
04 Job received by a section during a period & Jobs IW38 Order Report ---
Completed by a Section
05 List Job Cards Released IW38 Order Report ---
06 Material Issue Ticket MB24 Reservation List ---
07 Garage Tools Reservation --- --- GAP
08 Material Issued on WO Tilltill Date MB51 Material Document List ---
09 Material Availability by Workorder IWBK Material Availability ---
Information
200.1.03.04
10 Workorder Failure Report IW69 Notification Item ---
11 Workorder Inbox Forfor a Section IW38 Order report ---
12 Work Orders Scheduled on a day IW38 Order report ---
13 Work Order Expenditure Details IW38 Order report ---
14 Expense Workorder Details MCI8 Cost Analysis ---
15 MAXARC WO print details report IW37N Order Operation Report ---
16 MAXARC Expenditure Details MCI8 Cost Analysis ---
17 Work Order Generated Yesterday IW38 Order report ---
18 Report on Stocked tool usage in WO --- --- GAP
19 --- IW28 / IW29 Notification Report ---
18
20 --- IW37N / IW49N Order Operation Report ---
19
21 --- MCI7 / MCJB / MTTR / MTBR Report ---
20 MCJC
22 --- MCI2 Manufacturer Analysis ---
21
23 --- MCI4 Planner Group Analysis ---
22
200.1.03.04
6. GAP ANALYSIS
Identify Gaps w.r.t To Be Processes
Record development objects. Specify their Ref. To-Be Steps, Recommendations (Not in Standard, Process Changed – Change
management required, Development Required) and Status of recommendation. Also cross-reference the number of each task to the
number of steps in the process flow diagram.
Status Type of
Recommendation
(Proposed / Development
Ref. To-be (Custom
Description (if reuse W/ R / I / C/ E /
Sr.
item, include high
Section(s) Ref. To-be Development / Agreed with
No. Step(s) Third party F
level changes) core team /
solution /
workaround
Agreed with
SAP)
Maintenance
Dashboard for E
Custom Agreed with Core
01 Filtering User Specific 3.1.1 ---
Development Team
Transaction
Processing
Restrict TECO 3.1.1 --- Custom Agreed with Core
02 without WO Development Team E
Confirmation
3.1.1 --- Custom Agreed with Core
03 PRT Custom Report Development Team R
Order & Permit 3.1.1 --- Custom Agreed with Core

04 Development Team F
Forms
WO Report based on --- --- Custom Agreed with Core
05 Development Team E/R
nature of expense
Report on Stocked 3.1.1 --- Custom Agreed with Core
06 Development Team R
tool usage in WO
Equipment BOM --- --- Custom Agreed with Core
07 availability in stock Development Team R
report
Technical Object field --- --- Custom Agreed with Core
to be made Development Team
08 E
mandatory in
Notification and WO
7. DOCUMENT ATTACHMENTS
Sr. No Activity/Task No., Name (ref Document Doc type (pdf, xls, Expected Doc size
with visio) description acad, jpg, mp4…) in MB
1 Upload of drawings during Equipment drawing Pdf, acad, jpg, etc. 5MB
creation of WO
2 Upload of attachments in WO for WO attachment Pdf, acad, jpg, etc. 5MB
maintenance
200.1.03.04
8. Key Considerations
8.1. Locations / SBUs where this Business Process is performed
BUSINESS UNITS / LOCATIONS

Location Country Function Number of Users Point of Contact
All locations India All functions All users
8.2. Integration Points
Integration Points
Document list of all integration areas discussed in the document. This shall include integrations with other SAP module and
non-sap applications
Ref Process ID / Integration Point SAP / Non-SAP Data Object Owner of the
BBP Document Component integration process
200.1.05.03 Stock Item SAP --- MM
Replenishment
200.1.05.04 Purchase Requisition SAP --- MM
Process
200.1.05.06 Purchase Order Process SAP --- MM
200.1.05.07 Good Receipt & SES SAP --- MM
Receipt
RBAR (Revenue Budget SAP --- FI/CO
Appropriation Request)
200.9.02.07 Work Order Cost SAP --- CO
Settlement
200.1.03.04
8.3. Cut Over / Deployment Considerations
Cut Over / Deployment Considerations
Document any Cut-over considerations (particularly dependencies / third party systems) corresponding to the business
process. Specify the action required.
No
Description Action Required
.
It is recommended to close existing
01 Migration of open WO open orders to reduce volume of
open orders
02 Equipment Failure History NA
03 Reservations, Issues related to Open WO NA
8.4. Batch Processing

Batch Processing
Document batch considerations (particularly performance, job dependencies) corresponding to the business process. Specify
the priority (M = Mandatory, O = Optional) required.
No Dependencie
Description Priority
. s
01 NA NA NA
8.5. Roles & Authorization
Roles & Authorization

Document security considerations (particularly ring-fencing requirements) corresponding to the business process. Specify the
priority (M = Mandatory, O = Optional) required.
No. Description Priority

01 Operations M
02 Operations Manager M
03 Maintenance Planner M
04 Maintenance Executor M
05 Store Executive M
06 Finance / Costing M
9. Business Impact
200.1.03.04
Highlight Business Impact of Changes from Current Practices
Please provide a high-level summary (or list of) current practices related to this processing event. Highlight/focus on practices
that are no longer followed or changed as a consequence of the To-Be process. The document identified impacts to the
business. Specify impact category (OG = Organization, OP = Operation, CU = Customer, JO = Job, AP = Applications, OT =
Others) the level of impact (H = High, M = Medium, L = Low), Process Change from current practice (Deleted / Changed /
Added)
Impact Impact Deleted / Changed /

No. Description
Category Level Added
01 Strengthening of safe work practices OP M Changed
02 Standardization of processes OP M Added
9.1. Key Policies/Operational Decisions

NA
9.2. Key Changes for Adoption to Standard
NA
200.1.03.04
10. Test Scenarios
Test Scenarios
Document Test scenarios corresponding to the business process. (Test scenarios may get added or merged /changed as project
progresses)
No
Unit Test Scenario Description
.
01 General Notification Create / Change / Display
02 General WO Create / Change / Display
03 Reservation of stock material / Tools & tackles
04 Posting of service entry sheet with reference to work order
05 Confirmation of WO
06 TECO & CLSD of WO
No
Integration Test Scenario Description
.
01 Goods Issue / Goods Receipt of spares / consumables with ref. to Reservation no. / WO no.
02 Settlement of work order as part of monthly activities for finance and costing
11. Transaction List (S4 and Fiori)
Sl. SAP Fiori APP Standard / Custom Description

No Transaction Name Fiori App
code including
custom Fiori
Apps
1 IW21 Create Maint. Create Maint. Request
Request
2 IW28 Manage Notif. Manage Notif. List
List
3 IW38 Manage Order Manage Order List
List
4 IW41 Confirm Jobs Confirm Jobs
5 IW44 Create Mass Create Mass Time Confirmation
Time
Confirmation
1 IW21 IW21 Standard Create PM Notification - General

2 IW22 IW22 Standard Change PM Notification
200.1.03.04
Display PM Notification, Display PM
3 IW23 IW23 Standard
Notification (IW23)
4 IW31 IW31 Standard Create Maintenance Order, Create Order
5 IW32 IW32 Standard Change Maintenance Order
Display Maintenance Order, Display PM
6 IW33 IW33 Standard
Order (IW33)
7 IW34 IW34 Standard PM Order for PM Notification
8 IW36 IW36 Standard Create PM Sub-Order
9 IW38 IW38 Standard Change PM Orders
10 IW39 IW39 Standard Display PM orders
11 IW41 IW41 Standard Enter PM Order Confirmation
12 IW42 IW42 Standard Overall Completion Confirmation
13 IW44 IW44 Standard PM Order Collective Confirmation
14 IW45 IW45 Standard Cancel PM Order Confirmation
15 IW29 F2071 Standard Find Maintenance Notification
16 IW28 W0004 Standard Manage Notification List
17 IW49N IW49N Standard Display Orders and Operations
Display Material Availability (IWBK),
18 IWBK IWBK Standard
Material availability information
12. Annexure
Improvements / Solution for Pain Points reported mentioned in the below document attachment
200.1.03.04

Neral Maintenance v0.7

Uploaded by

Document Information

Original Title

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

Neral Maintenance v0.7

Uploaded by

Copyright:

Available Formats

Project Aarohan

BBP_Plant Maintenance_General Maintenance

Version: 0.5 7 (Signed off version to be 1.0)

22/10/2021 Mohammed Ashif Consultant 0.1 Draft

25/10/2021 Mohammed Ashif Consultant 0.2 Updated the Process description

01/11/2021 Mohammed Ashif Consultant 0.3 Inclusion of KDS in BBP

Date Document Title Document Reference

22/10/2021 Inventory application REF-PM-08-V00

22/10/2021 Inventory Usage Application REF-PM-16-V00

22/10/2021 History card of the equipment PM-MKTG-13-V00

22/10/2021 Part list inventory management (Warehouse) PM-MKTG-14-V00

22/10/2021 CP Maintenance PM-LAM-08-V00

22/10/2021 OFC Maintenance PM-LAM-09-V00

22/10/2021 Pipeline Maintenance PM-LAM-10-V00

22/10/2021 History card of the Pipeline sections PM-LAM-16-V00

22/10/2021 Part list inventory management (Warehouse) PM-LAM-18-V00

22/10/2021 ROW Maintenance PM-LAM-11-V00

Name (Mr/Ms) Role Signature and Date

Reviewer – Accenture Module Lead

Reviewer - Business Core Team

Approver - Business Core Team Module Lead

Binoy D TheruvanBinoy T Process Owner

Key Dependencies & Master Data Consideration

2.3. Visio Legend

Process Description: (Overall Document level Process brief Description / Coverage)

3.1. To be Process – Process Name / Description

3.1.1. Process Description: (Brief Process sections and explanation)

Introduction on General Maintenance:

Figure 1 : Notification Screen in SAP - Header and Item level

Figure 2: Order Screen in SAP - Header and Item level

Figure 4: Permit Process Flow (Without LOTO process)

SAP Process Steps with Role / Executioner of the step

In this step, the maintenance request can be

Create General Maintenance Order with

In this step, the Order is getting released for

Request the permit using the customized work

Create Service Entry Sheet (SES) for the

Update Technical In these steps, technical findings, like details and

Once all the operations are performed Technical

The cost recorded in WO is transferred to cost

Business Completion After full settlement of cost from WO to cost

3.2. To be Process – Process Name / Description

3.2.1. Process Description: (Brief Process sections and explanation)

Proposed Business Process Description

10 --- --- --- ---

Expectations with the new SAP system

Order & Permit 3.1.1 --- Custom Agreed with Core

BUSINESS UNITS / LOCATIONS

8.2. Integration Points

03 Reservations, Issues related to Open WO NA

8.4. Batch Processing

8.5. Roles & Authorization

Roles & Authorization

No. Description Priority

Impact Impact Deleted / Changed /

02 Standardization of processes OP M Added

9.1. Key Policies/Operational Decisions

01 General Notification Create / Change / Display

02 General WO Create / Change / Display

03 Reservation of stock material / Tools & tackles

04 Posting of service entry sheet with reference to work order

06 TECO & CLSD of WO

11. Transaction List (S4 and Fiori)