CMS Doc ID SOP-1867 SOP Title Condition Monitoring Online Surveillance

Date Issued 12/6/2022 Directorate UOD Sub Team UOM

Security Restricted Page No 6 Version 2.0

Document Authorisation
Document Owner: Nasser Al Toqi Document Custodian: Al Waleed Document Author: Ahmed Al
UOM Sha'Aily UOM5 Mamari UOM51
Toqi, Nasser UOM Sha'Aily, Al Waleed UOM5 Mamari, Ahmed UOM514

Date : 07-05-2023 10:58 AM Date : 29-06-2022 1:47 PM Date : 01-05-2023 8:05 AM

Printed copies are UNCONTROLLED

Number of People Involved: 6  Total Lead Time: 8 Hours

Special Procedure
Instructions and Explanations Key Point Images
Requirements Overview

1. Assign team
1.1 Supervisor to assign team members
members to check to check machines in online systems
all machines in their respective areas of
connected to responsibilities.
online systems
1.2 Supervisor to establish frequency of
UOM51x online system screening such as
daily checks for traffic lights or
Cycle Time: 20min
alarms and weekly screening for
trending or in-depth analysis.
 2. Access the 2.1 Go to PDO Landing-Page.
online systems 2.2 Access the PCAD Portal.
and check its 2.3 Enter the credentials.
healthiness. 2.4 Select the Area and station.
UOM511x 2.5 Select the server.
2.6 Enter the credentials to access the
Cycle Time: 30min
server.
daily & 2hrs
weekly 2.7 Open the online system.
2.8 Check if all tags are communicating
properly.
 3.1 Utilize the On-line monitoring
3. Screen vibration
systems to screen daily for traffic
and performance
data and check light or alarms of all the critical
machines machine conditions.
condition. 3.2 If alarms found during daily
UOM511x
screening, do in-depth analysis and
gather data for further investigation
Cycle Time: 30min 3.3 Weekly screening or in-depth Figure 1 Online Monitoring System
daily & 2hrs
analysis of all critical machines to
weekly
find abnormalities in the trends and
impending failures.
4.1 Inquire from the station operator (by
4. Get additional phone) any urgent issues (P1) and
information from
site or help from
ask additional information like
expert. process parameters and any
abnormalities or check in
UOM511x
SmartConnect.
Cycle Time: 30 4.2 Conduct site visit if required for
min additional information. Consult the
supervisor if required to support
analysis.

5. Prepare
5.1 Prepare diagnostic report with
diagnostic report findings and recommendations to
rectify impending failure.
UOM511x
5.2 Wherever is applicable, prepare a
Cycle Time: 120 performance analysis report and
min highlight significant issues (if
SmartConnect or Nibras is available).
5.3 Consult the supervisor or in team
discussions for technical comments
and approval of the analysis report.

Figure 2 Diagnostic Report

6. Issue Report
6.1 Issue the diagnostic report to the
and Raise concerned operation and
Notifications in maintenance teams.
SAP system 6.2 Raise notification in SAP with
UOM511x description and recommendation as
described in the diagnostic report.
Cycle Time: 60 6.3 Highlight deficiency and required
min
correction into the Weekly highlights
report.
6.4 Condition Monitoring Supervisor and
Diagnostic Engineer to take action if
the defective machine requires
continuous close monitoring.

Figure 3 SAP Notification

  Pre-Checks
Key Point Images
Things to Do Before Starting the Process

Check the health of the on-line system and connections

with the server.

Contact Operations team and station operator for any

machine’s health issues and if any diagnosis required.

Screen the machines health in the system continuously

on daily and weekly basis.

 Tools and Materials

Things You Need Before Step Key Point Images

Starting the Process

Performance analysis
reports and previous reports.

Computer connected to the

on-line system and having the
software.

Save the historic data.

People Key Point Images

Who Is Required to Be Notified

 Supervisor + Journey manager

Operations (station operator)

Maintenance team involved.

 Key Learnings; Performance Points 

Key Point Images
What Have We Learned That We Should Share

 Professional communication with all parties involved in

the process.
 Solve the problems as a teamwork and communicate
success.
 It is important to do the follow up of the reported potential
failures and discuss the next actions taken to make effective
use of the data collected and analysed.
 It is important to do performance and health analyses for
the machines connected with the on-line systems and report
any development ahead.