Table of content

PROCESS DEFINITION DOCUMENT –

MAINTENANCE PROCESSING

Dibakar Thakur
IBM INDIA PVT. LTD.  
 Project UNIFY

1 Document Control Information............................................................................................2

1.1 Document Details.......................................................................................................... 2
1.2 Revision Log.................................................................................................................. 2
1.3 Distribution List............................................................................................................. 2
1.4 Scope of this Document.................................................................................................2
1.5 Process Owners and Users.............................................................................................2
2 Master Scenario................................................................................................................ 3
3 Process Coverage...............................................................................................................3
4 Best Practices.................................................................................................................... 3
5 Proposed Solution.............................................................................................................. 4
5.1 Master Data.................................................................................................................. 4
5.2 Process Flow Diagram & Description...............................................................................4
5.2.1 Asset/Equipment Installation.................................................................................................4
5.2.2 Manage Asset/Equipment..................................................................................................... 5
5.2.3 Breakdown Maintenance....................................................................................................... 6
5.2.4 Preventive Maintenance........................................................................................................ 8
5.2.5 Calibration of Test Equipment............................................................................................... 9
5.2.6 Spares Management........................................................................................................... 10
5.3 WRICEF Objects........................................................................................................... 11
5.4 Automation Plan......................................................................................................... 11
6 Gaps.............................................................................................................................. 12
7 Future Roadmap.............................................................................................................. 12
8 Sign-off........................................................................................................................... 13

Process Definition Document Page 1 of 15

 Project UNIFY

1 Document Control Information

1.1 Document Details

Customer
Cyient Ltd
Name
Document
Name 4.3_Maintenance Processing _V2.0

Project Name Project UNIFY

1.2 Revision Log

Revision Change Description Author E-mail Release

Number Date
1.0 Initial Dibakar Thakur dibthaku@in.ibm.com 02.07.2018
2.0 Updated Dibakar Thakur dibthaku@in.ibm.com 08.08.2018

1.3 Distribution List

Sr. Name E-mail
No.
1 Core Team Members: Shrinivas.Govinda@cyient.com
Shrinivas Govinda Wadiraj.Kulkarni@cyient.com
Wadiraj Kulkarni
2 Business Process Owner:
Suchitra.Royroth@cyient.com
Suchitra Royroth
3 Project Manager:
Ramakrishnav.potluri@cyient.com
Ramakrishna Potluri
4
IBM Project Team:
Rakesh_tripathy@in.ibm.com
Rakesh Tripathy

1.4 Scope of this Document

The objective & scope of this document is to describe the process flows as configured in SAP as against the
activities conducted at Plant Maintenance at Cyient Manufacturing plants. The processes listed in this document
apply to asset maintenance activities carried out by Maintenance team process, which will include spare parts
management and calibration of test equipment.

1.5 Process Owners and Users

This is for use of the entire Cyient group.

Process Definition Document Page 2 of 15

 Project UNIFY

2 Master Scenario

Master Scenario Plan to Manufacture (P2M) - Maintenance Processing

3 Process Coverage
Process Coverage  Asset/Equipment Installation
 Manage Asset/Equipment
 Breakdown Maintenance
 Preventive Maintenance
 Calibration of Test Equipment
 Spares Management

4 Best Practices
Best Practices SAP S4/HANA best practices for Plant Maintenance applicable for Cyient manufacturing plants are
mainly as below -
 Breakdown Maintenance – validate the equipment and create Notification to capture initial
breakdown information and then create Maintenance Order, plan labor and material cost,
release the Order and print out the Order copy; Time confirmation and goods movement to
post actual cost to Order; update Notification with breakdown information and TECO the
Order; settle the cost from the Order to Equipment Cost Center and finally business
completion of the Order.
 Preventive Maintenance – Create Task List and Maintenance Plan with right maintenance
strategy avoiding of creation of multiple plans of the same Equipment. Deadline monitoring of
the Plans to create and auto-release the Preventive Maintenance Order. Labor and materials
planned in Task list will come to order automatically, reduces the planning time of the
Maintenance planner. Book time confirmation and goods movement and TECO the Order.
settle the cost from the Order to Equipment Cost Center and finally business completion of the
Order
In addition to the above, Test Equipment Calibration, Spares management, Corrective
maintenance, maintenance cost analysis, Breakdown analysis etc are recommended as part of Sap
S4/HANA best practices.

Process Definition Document Page 3 of 15

 Project UNIFY

5 Proposed Solution
Proposed Solution The below is Proposed Solution with 1. Master Data 2. Process flow diagrams & description 3.
WRICEF objects included in the solution and Automation plan if any

5.1 Master Data

Below master data are primarily important for carrying out all the maintenance process detailed under section 5.2

 Functional Location
 Equipment
 Work Centre
 Material
 Maintenance Task List
 Maintenance Plan
 Document Info Record
 Master Inspection Characteristics

5.2 Process Flow Diagram & Description

In this section, the following processes will be described:

 Asset/Equipment Installation
 Manage Asset/Equipment
 Breakdown Maintenance
 Preventive Maintenance
 Calibration of Test Equipment
 Spares Management

5.2.1 Asset/Equipment Installation

 This process of new asset or equipment installation is referred to the Statutory Maintenance
Format “MNT-F-08 Installation Qualification Report”. When a new asset is procured by Finance
team, the asset master will be created for that and it is sent to Maintenance team to install that
asset.
 Maintenance planner will create an Equipment master data with all the manufacturer details
along with warranty date information and link the asset no. with mentioning start date.
Equipment master holds the information of manufacturer details and location details of where
the equipment will be located.
 Maintenance planner will create a Notification of in SAP for the equipment to be installed. A
new Notification type (viz Z2) will be configured as maintenance request for this.
 He will create a Maintenance Work Order from that Notification to execute the actual work. A
new Work Order type (viz ZM01) will be configured.
 A blank Installation Qualification Document should be attached to the notification using
Document Management System (DMS). A new Document type (viz ZPM) will be configured. The
Installation Qualification document contains all pre and post installation checks by Maintenance
and other departments.
 After the notification is created, the Maintenance planner will add 5 tasks to the Notification for
each responsible department – Maintenance, Production, Process Engineering, Quality & EOHS.
He will assign the task to the respective “User Responsible” which will trigger a workflow
message to the respective User to inform them that a new task is created to do the Installation
check by their department. The user needs to log in to SAP S4/HANA to access the Notification

Process Definition Document Page 4 of 15

 Project UNIFY
Task. And he will enter all the checking notes and comments in the Task long text section and
finally complete the task.
 The Maintenance technician can book the material component to the Work order if it is required
for installation. And Goods issue will be done from the Store accordingly.
 After all tasks are completed in SAP by all the users from the all the respective departments,
maintenance technician will book the time for the Installation Work. He will capture all the
Object & Activity codes in the Notification, he will get the Installation Qualification document
signed by each responsible department and attach it to the Notification for audit and history
purpose.
 He will do the Technical Completion (TECO) of the Work order and complete the Notification.
The respective User of all the departments will be provided the SAP transaction access to
process and complete the Notification Task.
 Finance will do the Settlement of the Work Order cost to Equipment Cost center and finally
Business Completion of Work Order will be done.
 In future, when the equipment will be scrapped or out-of-function, a user- status as “Scrapped”
can be updated to the equipment and maintenance team will inform the Finance team to de-
registrar the corresponding asset master for that equipment.

Asset/Equipment Installation process

Finance

New Asset
Installation request

Create New Like Asset to the Create Maintenance Create and Release Add Tasks to
Equipment Master Equipment Master Notification Maintenance Order Notification
IE01 IE02 IW21 IW21, IW31 IW22

Order
Output

Assign Task to User

Sign the IQ document and Process & complete all Tasks Responsible of Maintenance,
Workflow messages to
attach to Notification by all departments Production, Quality & EOHS
departments
CV01N, IW22 IW22, IQS2 departments
IW32
Maintenance

Time Confirmation of Technical Completion of Settle the Actual Cost of Business Completion of
Maintenance Order Maintenance Order Maintenance Order Maintenance Order
IW41, IW42 IW42, IW32 KO88 IW32

Non SAP Steps

Standard SAP SAP Development
(Manual Business
Process Steps (WRICEF)
Process Step)

5.2.2 Manage Asset/Equipment

 Once the new Equipment is created from section 5.2.1, it will be also installed to a Functional Location.
The equipment will have a user-status set as “In Use”. There will be another user status as “Not In-use” or
“Scrapped” and it will be set to the equipment master when it will retire from functioning. This way it will
provide a better tracking of the equipment of whether it is functioning or not. Standard SAP report
transaction codes like IH08 are available to find the list of equipment or machines. This process refers to
Maintenance format – “MNT-F-01 List of machinery” used in DLM manufacturing plants.
 For Critical Equipment, ABC indicator should be maintained where A - is Critical, B - Semi-Critical and C
-Non-critical. Same can be done for Critical Spare Materials also. Standard SAP report transaction IH08

Process Definition Document Page 5 of 15

 Project UNIFY
will provide the list of Critical Equipment. This process refers to Maintenance format – “MNT-F-07 Critical
Spares List” used in DLM manufacturing plants.
 For Scrap Equipment list, the equipment master will be updated with a user status as ‘Scrapped”. The
standard SAP transaction codes are available to track the Scrap equipment list. This process refers to
Maintenance format – “MNT-F-11 Scrap List” used in DLM manufacturing plants.
 Soft copy of manual/drawings can be attached to the equipment master using Document Management
System (DMS); new document type ZPM will be used to create a Document Info Record (DIR) to attach
the manual/drawings to the equipment. During preventive or breakdown maintenance, technician can
open the manual from the equipment and execute the maintenance work. If the Manual is updated or
revised, a new version of DIR can be created and attached to the equipment. In the new version, revision
details can be updated in the DIR long text. To see the list manuals, standard SAP transaction code CV04N
can be used. This process refers to Maintenance format – “MNT-F-09 List of Machine Manuals” used in
DLM manufacturing plants.

5.2.3 Breakdown Maintenance

Breakdown maintenance consists of the actions taken to restore a failed system to operational status. This usually
involves replacing or repairing the component that is responsible for the failure of the overall system. The
objective of breakdown maintenance is to restore the system to satisfactory operation within the shortest
possible time. The production process gets interrupted by the machine failure.

Breakdown maintenance process in Cyient DLM plants are classified as below:

5.2.3.1 Breakdown Maintenance by Internal Resource

 While any machine or equipment gets any break down or malfunction problem the operator will inform
the maintenance team. Maintenance planner will raise a notification (viz notification type Z1 –
breakdown maintenance) in SAP S4/HANA system for that equipment. He will maintain the priority
information by which they need to resolve the malfunction. Manual or drawings can be added to the
Notification Document data section. If the equipment is under warranty, system will give a pop-up
message saying that the equipment is under warranty.
 The planner will create a Work Order (viz Work Order type ZM01 – breakdown maintenance) from that
notification and add operation details. He can book spare material component to the Work order if
needed. He will release the Work order and then take print out of the Work order shop paper and hand
over to the technician.
 The Store person will do Goods Issue to the technician. The technician will finish the breakdown
maintenance activity and book time confirmation in SAP S4/HANA system. Also he will add all the Activity
code, damage code and break down duration.
 He will do the Technical completion of the Work order and Notification. Standard SAP report
transactions code are available to analyse the breakdown history of the Equipment.
 After technical completion, Work Order cost will be settled to equipment cost centre. Business
completion of the Work Order will be done subsequently.
 The breakdown maintenance process is referred to Maintenance formats used in Cyient DLM
manufacturing plants – “MNT-F-02 Breakdown Maintenance and Complaint Log Sheet” & “MNT-F-05
Machine History Card” & MNT-F-16 Breakdown History Tracker.

Process Definition Document Page 6 of 15

 Project UNIFY
Breakdown Maintenance Process

Create Breakdown Check Equipment Create Breakdown Release Breakdown

Add Component
Notification Warranty period Maintenance Order Maintenance order
IW32
IE01 IW21 IW21, IW31 IW32

Order
Output

Update Activity Code, Damage

Goods Issue from Store
Update Breakdown Hours Code & cause Code in Book Time confirmation
MIGO, IW42
IW22 Notification IW41
IW42
Maintenance

Technical Completion of Work Settle the Cost of the Work Business Completion of Work
Analyse Breakdown history of
Order (TECO) Order Order
equipment
IW42, IW32 KO88 IW32

Non SAP Steps

Standard SAP SAP Development
(Manual Business
Process Steps (WRICEF)
Process Step)

5.2.3.2 Breakdown Maintenance by External Vendor

 If the breakdown maintenance needs to be done by any external vendor, the maintenance technician will
create a Notification (Z1 type) for the equipment
 He will create a Maintenance Work order (ZM01 type) from that. He will add an external operation (using
external Control Key - PM02) and release the work order. System will create a Purchase Requisition
automatically for that external work.
 Maintenance Planner will convert the Purchase requisition to Purchase Order upon approval. Once the
Purchase Order will be sent to the External vendor, they will come to Site and do the breakdown
maintenance.
 Maintenance technician will confirm and accept the service and do the Technical Completion (TECO) of
the Work order. Also he will update the breakdown hours and activity and damage codes in the
notification during time completing the Notification. Maintenance Work Order will be updated with the
actual cost charged by the external vendor.
 After technical completion, Work Order cost will be settled to equipment cost centre. Business
completion of the Work Order will be done subsequently.

5.2.3.3 Replacement of Equipment (Contingency Plan)

 While any critical equipment gets breakdown and the maintenance team needs to replace the similar
type of equipment, they will create a Notification (Z1 type) for the damaged equipment and create a
Work Order (ZM01 type).
 All the similar type of critical equipment will be assigned to a certain Class (Equipment class type – 002).
Maintenance technician can search the similar active equipment in “In-Use” status in SAP S4/HANA
system by standard report transaction code using the Class of that equipment. The technician will choose
the right equipment and replace the damaged one by it in site.
 He will update the Notification long text with the replacement equipment details and book the time
confirmation along with the damage code and activity code.
 He will do the technical completion of the Work order and Notification. This process is referred to
Maintenance format – “MNT-F-14 – Contingency Plan” used in Cyient DLM Plants.

Process Definition Document Page 7 of 15

 Project UNIFY
5.2.4 Preventive Maintenance
 Preventive maintenance processing is the practice of replacing components or subsystems before they
fail in order to promote continuous system operation. Main goal is to assure the reliability of the object
(within defined limits) during the inspection interval. The schedule for preventive maintenance is based
on observation of past system behaviour, component wear-out mechanisms and knowledge of which
components are vital to continued system operation. Ensuring a high availability of objects in the long
term is an important part of plant maintenance. Preventive or Planned maintenance is used to avoid
system breakdowns or the breakdown of other objects, which - in addition to the repair costs - often
result in much higher costs subsequently owing to production breakdown.
 Prerequisite for the process preventive maintenance processing is the creation of a Maintenance plan. It
describes when a maintenance task should be performed and on which functional location or equipment
(several objects are possible for a tour for example).
 Each maintenance item of a Maintenance plan has to be linked to a Task list. The Task list contains a
detailed description of what has to be done and who (work centre) should do it. A planned time for the
required tasks should be entered as well. It may have all task instruction maintained in operation long
text or attached document (using PRT).
 It is also possible to assign required parts, to plan procurement of external services & materials and to
attach documents (in forms of production resource tools) to the task list. Maintenance Plans can be single
cycle, time based strategy or performance based. If it is strategy based, the Task list should have the
same strategy maintained. One Time based Strategy may have different frequency cycles. Hence the
Same Equipment having same maintenance plan with different frequencies (weekly check, monthly
check, yearly check etc). Also preventive maintenance can be classified in Maintenance plan by using
different Maintenance Activity Types (viz Overhaul, Inspection, Oil Clean-up, Servicing etc.).
 The Maintenance plan is the basis for the scheduling of preventive maintenance tasks in SAP. Depending
on the requirements daily or weekly batch jobs (called deadline monitoring) should be set up in the
production environment to perform the scheduling of the maintenance tasks during the night. When the
plan date is reached the Work Order are automatically created and released according to the scheduling
period.
 Each day the maintenance department (e.g. the maintenance planner) reviews the work list. Once Work
order is created and released, planner will take print out of the Work order and the technician will carry
out the job. If any spare component (stock item) is needed, can be withdrawn from Store.
 If the Spare is a non-stock item, then it can be booked to the Work Order and a Purchase Requisition will
be created automatically. After getting all the approval the Purchase Order will be created from the
Purchase Requisition and sent to the Vendor.
 Once the Vendor supplies the material, the Store will do the Good Receipt. Finally the technician will
book the time confirmation and update with notification with necessary findings; if needed technician
can create a follow-on Work Maintenance order also if there is further maintenance work to be done;
then he will do the technical completion of the Work order.
 After technical completion, Work Order cost will be settled to equipment cost centre. Business
completion of the Work Order will be done subsequently.
 There are standard SAP reporting transaction codes available of Maintenance Plans. This Preventive
Maintenance process is referred to Maintenance format – “MNT-F-10 PM Calendar” & “MNT-F-03
Preventive Maintenance record” used in Cyient DLM Plants.
 For Preventive Maintenance of Electrostatic device (ESD), Task List for ESD checklist should be created
and Maintenance plan with right cycle frequency should be created. And the plans will be scheduled by
deadline monitoring of daily batch job in SAP S4/HANA system to create Preventive maintenance Work
Order. This process is referred to Maintenance format –“MNT-F-06 ESD Checklist” used in Cyient DLM
Plants.
 Similarly for Preventive Maintenance of Feeder and Earth-Pit, Task list and Maintenance plans should be
created with right cycle frequencies and the plans will be scheduled by deadline monitoring of daily batch
job in SAP S4/HANA system to create Preventive maintenance Work Order. This process is referred to
Maintenance format – “MNT-F-13 Earth Pit Preventive Maintenance Record” & “MNT-F-15 Feeders
Preventive Maintenance Check list” used in Cyient DLM Plants.
 For routine measurement of Lux Value reading, a Functional Location can be created to map the zone
where the Lux values is to be measure. For taking the measurement reading, measuring Point can be
created to the Functional location. Also Maintenance plan and Task list needs to be created for routine
measurement reading with right cycle frequencies. The plans will be scheduled by deadline monitoring of
daily batch job in SAP S4/HANA system to create Work Order. The Technician will take the Lux value

Process Definition Document Page 8 of 15

 Project UNIFY
reading and update in the measuring point reading during time confirmation process and finally do the
technical completion of the work order. There are standard SPA report transactions are available to view
the lux value reading history. This process is referred to Maintenance format – “MNT-F-17 Lux Value
Measurement Record” used in Cyient DLM Plants.
 Same Preventive Maintenance process will be applicable of different Equipment Categories – like Tools,
Jigs & fixture, Customer Owned Equipment etc. Separate Maintenance Plans and Task list should be
created for them.
 There are some equipment which may need Preventive Maintenance by External AMC agencies. Separate
Maintenance Plans and Task list should be created for them. Task list should have external operation
(using PM02 control key) with external vendor information. Once the maintenance plan will be scheduled
by daily batch job, the Purchase requisition will be created from the Work order automatically. The
Purchase Order will be created from Purchase requisition after the necessary approval and sent to the
AMC agency. The AMC agency will come to site and carry out the preventive maintenance the
Maintenance team will confirm and do the acceptance of the service. Finally the time confirmation is
booked and work order will be technically completed.

Preventive Maintenance Process

Create Maintenance Create Maintenance Release Preventive

Schedule Plan Add Component
Plan Task List Maintenance order
IP10, IP30 IW32
IP01 IA05,IA01,IA11 IW32

Order
Output

Update Activity Code, Damage

Goods Issue from Store
Create Follow-on Work order Code & Cause Code in Book Time confirmation
MIGO, IW42
IW41, IW32 Notification IW42
IW42
Maintenance

Technical Completion of Work Review Document flow of Settle the cost of the Business Completion of the
Order (TECO) Preventive Maintenance Order Maintenance Order Maintenance Order
IW42, IW32 IW32 KO88 IW32

Non SAP Steps

Standard SAP SAP Development
(Manual Business
Process Steps (WRICEF)
Process Step)

5.2.5 Calibration of Test Equipment

 Routine calibration is done on the Test Equipment (which is a separate Equipment category). For the
routine calibration process, Master Inspection characteristics (MIC) will be created along with
Maintenance plan and Task list. Master Inspection Characteristics can be quantitative or qualitative to
capture the results accordingly. It signifies the characteristics of the test Equipment which will be
observed during Calibration inspection and value of the same test recorded.
 Maintenance plan will have calibration cycle frequency and Task list have the instruction details for
doing the calibration activities of the Test Equipment. Calibration Work Order of “ZM04” type will be
created and released in SAP S4/HANA system from the daily Maintenance Plan Scheduling batch job.
 From the Calibration Order, an Inspection Lot will also be created. The calibration technician will do the
result recording on the inspection lot and finally do the Usage Decision as “Accept” or “Reject”. If it is
“Reject”, Test Equipment Status should be updated as “Not for Use”. Finally the Calibration Order will be
technically completed.
 If the Calibration is done by External Vendor, the Maintenance Task list should have an External
Operation (using PM02 control key). Calibration Work order will be created from daily batch of
Maintenance Plan Scheduling. Purchase Requisition will be created automatically from the Work order.

Process Definition Document Page 9 of 15

 Project UNIFY
Purchase Order will be created manually form the Purchase Requisition once it is approved, and then it
will be sent to Vendor. They will come to Site and collect the Test equipment or do the calibration at site
itself. Once they complete the calibration, the Calibration technician will confirm and accept the service
and attach the scan copy of the Calibration certificate provided by the vendor to the Notification via SAP
Document Management System (DMS). And he will also do the result recording and Usage Decision as
per the external vendor’s calibration result and do the Technical Completion of the Calibration Order.

Calibration of Test Equipment Process

Create Master
Create Maintenance Create Maintenance Schedule Maintenance Release
Inspection
Plan for Calibration Task List Plan Calibration Order
Characteristics
IP01 IA05,IA01,IA11 IP10, IP30 IW32
QS22
Order
Output

Attach Calibration Certificate to

Usage Decision Result Recording & valuation Carry out Calibration Task
Notification
QA11, QE51N QE51N IW32
IW22
Maintenance

Time Confirmation & Technical

Review Document flow of Settle the Cost of the Business Completion of the
Completion of Calibration Order
Calibration Order Calibration Order Calibration Order
(TECO)
IW32 KO88 IW32
IW42, IW32

Non SAP Steps

Standard SAP SAP Development
(Manual Business
Process Steps (WRICEF)
Process Step)

5.2.6 Spares Management

 Spare material stock is checked periodically by store person. There are standard SAP S4/HANA
transaction codes are available to monitor the stock. For Spare material, a separate material type will be
created as “ERSA”. Maintenance team will raise a Purchase Requisition to procure the material. Once the
Purchase Requisition will be approved, then Purchase Order will be created and sent to Vendor. After
they supply the material, the Store person will check the quantity against the Purchase Order and do the
Goods receipt of the material. The Stock level will be updated accordingly in SAP S4/HANA system. For
further details of Spares procurement, please refer to PDD process - 3.2_Procure to Pay.
 Non-stock spare material can be booked into Work Order, which will create a Purchase requisition
automatically by SAP system. After necessary approval, the Purchase Order will be created for that
Purchase requisition. Vendor will supply the material to store and store person will do the Goods receipt.
It will not update the stock level, rather it will be consumed for that Work order.

Process Definition Document Page 10 of 15

 Project UNIFY

5.3 WRICEF Objects

 Workflow -
o Trigger Notification Task Workflow to Maintenance, Production, Engineering and Quality Teams
for New Asset Installation, which will enable the respective teams to complete the necessary
Asset Installation checks and approvals before the asset becomes ready for use.

 Reports – Not applicable; all standard SAP reports are available to meet Business requirement.

 Interfaces – Not applicable

 Conversions
o Upload program will be required to load the master data - Functional Location, Equipment, Plan,
Task List, Material master etc.

 Enhancements - Not applicable; all standard SAP process will suffice business requirement excluding the
Workflow and Forms requirement.

 Forms
o Maintenance Work Order Output needs to be developed as per business requirement which will
be confirmed by business.

5.4 Automation Plan

 Currently asset maintenance process are excel-based, carried out manually in all manufacturing plants of
Cyient groups. Analysing Equipment breakdown history, maintaining preventive maintenance calendar,
maintenance cost analysis, availability of critical equipment, calibration of test equipment etc. are all
manually maintained at present in Excel spreadsheet; These all manual process will be automated by the
usage of SAP S4/HANA Plant Maintenance system.

Process Definition Document Page 11 of 15

 Project UNIFY

6 Gaps
Gaps  Currently for new asset/equipment Installation in DLM plants, maintenance team face the
challenge of co-ordinating the installation checks and approval with other departments like –
Production, EOHS, and Engineering etc. They note down the installation check parameters
details manually in the MNT-F-08 Installation Qualification Report which is a MS-Word
document. Business requires an automated approach to co-ordinate all the installation check
and approvals processes.

7 Future Roadmap
Future Roadmap  Automation can be done to use paperless maintenance process by using SAP Works Manager
Application (Syclo). With SAP Works Manager solution, user can use Mobile devices
(Android/IOS) to receive Breakdown Notification & Work Order in their handsets and they can
book material to the job from mobile and book time confirmation and all necessary job
completion details along with breakdown hours; they can attach documents to the job and
finally send back to SAP S4/HANA system. They can also do calibration inspection with the
Mobile solution. Further follow-on job can be created through Mobile if required. The mobile
solution increases the response time to attend the breakdown or any other maintenance work.
All necessary maintenance reports and historical data can be tracked and analysed in Mobile. It
increases data integrity and productivity improvement.

Process Definition Document Page 12 of 15

 Project UNIFY

8 Sign-off

The Document has been signed off by:

Name Designation Signature Date

Shrinivas Govinda Process Owner

Business Owner
Suchitra Royroth

Ramakrishna Potluri Project Manager

Process Definition Document Page 13 of 15