Preventive Maintenance Process_Ver4.2

NSN Preventive Maintenance Process V-4.2 D440773926-4.2

Internal Use Only Nokia Siemens Networks Page 1, Total 46

Preventive Maintenance Process

Process and Quality

Delivery India Region

(Applicable to both SDU and Non-SDU Circles)

Nokia Siemens Networks



Preventive Maintenance Process Document Author Subhakanta Panda Manager Process Support -MS

India [email protected]

Vikas Kukreja Head Process & Quality

Document Contributor(s)

[email protected] K Siva Kumar Manager- Process and Quality Mukesh Prabhakar

[email protected] Manager- Process and Quality

Rajesh Divakaran [email protected]

Manager- Process and Quality Himanshu Verma

[email protected] Manager- Process and Quality

Priti Jain [email protected]

Engineer- Process and Quality Kemy Rishi

[email protected] Engineer- Process and Quality

Sanjeev Sharma

[email protected]

Manager- Process and Quality

Ethiraj Venkesh

[email protected] Business Ops Manager- GNSC, Chennai

Subhakanta Panda

[email protected]

Manager Process Support -MS India [email protected]

Sachin Grover Maxis Account

Sivasankara Kumar

[email protected]

COM, Vodafone GNSC Chennai

Krishna Palaniswamy

[email protected]

VHA, GNSC Chennai Devinder Pal Singh

[email protected] GNSC Noida

Sunil Taparia [email protected]

COM, TTSL GNSC Noida Malla Nageswara

[email protected] GNSC Noida

Ronak Kaji [email protected]

Manager National Core Pivush Trivedi

[email protected] GNSC – Chennai – VF- Tx

Kamal Mehta [email protected]

GNSC – Noida – TTSL- Tx Rahul Sagar

[email protected] GNSC – Noida – Maxis -Tx

Chetan Gandhikar [email protected]

GNSC –Noida – Bharti -Tx Srinivas Rao

[email protected] GNSC –Chennai –VF - MSS

Senthil Kumar [email protected]

GNSC –Chennai –Idea - NSS Bhuwan Pandey

[email protected] GNSC – Noida – Maxis - NSS

Parthiv Shah [email protected]

GNSC – Noida – Bharti - NSS Gaurav saraf

[email protected] GNSC – Noida – TTSL - NSS

Rohit Sayal [email protected]

GNSC – Noida- Bharti - NSS Santhosh. S

[email protected] GNSC Chennai –VF- BSS

Nithin Baranwal [email protected]

GNSC Noida –Maxis- BSS Vishal Kumar

[email protected] GNSC Noida –Bharti- BSS

Yatish Singhal. C [email protected]

GNSC Noida – TTSL- BSS Atul Singhal

[email protected] National IN VAS Team

Shreyansh Panchal [email protected]

National Core Team Phani Kumar

[email protected] National IN VAS Team

Zeenia Sharma [email protected]

National IN VAS Team Ujjwal Bagchi

[email protected] Core Network Planner

Document Approver

[email protected]

Vikas Kukreja Head – Performance & Process, MS India

Document Release Authority

[email protected]

Amit Dhingra Head Global Services, India Region [email protected]

mailto:[email protected]�





DOCUMENT HISTORY DATE NAME VERSION CONTENTS OF CHANGE

16.03.09 Vikas Kukreja Version 1.0 Release of First Version 15.06.10 Vikas Kukreja Version 1.1 Release of Second Version

18.08.10 Puneet Singh Version 1.2 Release of Third Version including New Procedures & complete Process layout change

31.10.10 Puneet Singh Version 1.3 Release of 4th Version including New PrM Template, Severity & Approval Matrix in PrM Activities, New Calender and modification in Responsibility Matrix

12.11.10 Puneet Singh Version 2.0 Non Version 30.11.10 Puneet Singh Version 3.0 Version with Inventory & Spare validation

13.05.11 Puneet Singh Version 3.1

Inclusions : (1) Health Check & Preventive Maintenance of Router/Firewall & STP. (2) Node-B PrM is also modified

21.07.11 Subhakanta Panda Version 3.2

3rd

18.10.11

party responsibility for out of NSN scope equipments, responsibility of switch over, pre checklist of STP redundancy check and document on redundancy procedure and method attached.

Subhakanta Panda Version 4.0

Detailed Redundancy check procedure Health check of erlangs utilization,CGR utilization,STM utilization,License utilization of MGW added in HC & monthly PrM PrM Calendar-Tracker is modified. Frequency of diagnose of computer units of RNC,MGW,MSS added/modified PrM for infra equipments modified.

28.12.11 Subhakanta Panda Version 4.1

Health check for new generation nodes (SGSN/ GGSN/ NTP/DNS/RADIUS). MSS,MGW and HLR redundancy check frequency has changed from 3months to 6 months. Frequency of Prm for BTS sites has changed to six months. Prm checklist for BSC included Schedule for Prm/HC updated(new generation node included) Approval Matrix for Prm/HC updated(new generation node included) Redundancy for Open MSS included.

15.02.12 Subhakanta Panda Version 4.2 Recommendation is to stop preventive/periodic maintenance for all diagnosis, switch over and redundancy check activities of MSS/MGW /HLR.



1 Introduction ........................................................................................................... TABLE OF CONTENTS

7

1.1 Purpose .......................................................................................................................... 7

1.2 Scope .............................................................................................................................. 7

1.3 Key Points ...................................................................................................................... 7

1.4 Key Interfaces ................................................................................................................ 7

1.5 Process Change Control .............................................................................................. 8

1.6 Process Definitions ....................................................................................................... 8

1.6.1 Automatic Maintenance .......................................................................................... 8

1.6.2 Health Checks ......................................................................................................... 8

1.6.3 Preventive Maintenance ......................................................................................... 9

1.6.4 Category of PrM & Health Check (Non-Service & Service Affecting) ..................... 9

1.6.5 Severity of PrM & Health Check Activities (Major & Minor type) .......................... 10

1.6.6 PrM for Infra equipments ...................................................................................... 10

2 Preventive Maintenance Process Work Flow .................................................... 12

2.1 Process Work Flow ..................................................................................................... 12

2.2 Role Mapping of SDU and Non-SDU circles ............................................................. 12

2.3 Process Overview ....................................................................................................... 12

2.3.1 Explanation of Process Work Flow ....................................................................... 13

3 Process Description ............................................................................................ 14

3.1 Preventive Maintenance (PrM) Life cycle ................................................................. 14

3.1.1 Scheduling of PrM ................................................................................................. 14

3.1.2 Performing PrM activities ...................................................................................... 14

3.1.3 Reporting PrM Tasks ............................................................................................ 15

3.1.4 Closure of the Preventive Maintenance tasks ...................................................... 15

3.2 Preservation of PrM Reports ...................................................................................... 15

3.3 Roles and Responsibilities for PrM & health Checks activity ................................ 15

3.4 Schedule for Health Check and Preventive Maintenance activities ...................... 16

4 Preventive maintenance via PrM Form (Manual Process) ................................ 17

4.1 Scheduling ................................................................................................................... 18

4.2 Performing ................................................................................................................... 18

4.3 Reporting ..................................................................................................................... 20

4.4 Closing ......................................................................................................................... 21

5 Preventive Maintenance via PT4 Tool (applicable to PT4 rolled out circles) .. 21

5.1 Scheduling ................................................................................................................... 21

5.2 Performing ................................................................................................................... 21



5.2.1 PRM TASK Flow diagram in PT4 for Circle team: (not ready yet) ....................... 22

5.2.2 PrM Task Status flow in PT4 ................................................................................. 23

5.3 Reporting ..................................................................................................................... 23

5.4 Closing ......................................................................................................................... 24

6 Health Check and Preventive Maintenance Responsibility Matrix (SOR)........ 24

6.1 SOR for Health Check of HLR .................................................................................... 24

6.1.1 Health check of HLR ............................................................................................. 24

6.1.2 Preventive Maintenance of HLR ........................................................................... 25

6.2 SOR for Health Checks and PrM of MSS-GCS and GMSC ...................................... 25

6.2.1 Health Check of MSS-GCS & GMSC ................................................................... 25

6.2.2 Preventive Maintenance of MSS-GCS & GMSC .................................................. 26

6.3 SOR for Health Checks & PrM of MGW ..................................................................... 26

6.3.1 Health Check of MGW .......................................................................................... 26

6.3.2 Preventive Maintenance of MGW ......................................................................... 27

6.4 SOR for Health Checkup of Router ........................................................................... 28

6.4.1 Health Check of Routers ....................................................................................... 28

6.5 SOR for Health Checks of Firewalls: ......................................................................... 29

6.5.1 Health Check of Firewalls ..................................................................................... 29

6.6 SOR for Health Checks of BSS .................................................................................. 30

6.6.1 Health Check of BSC ............................................................................................ 30

6.6.2 Preventive Maintenance of BSC ........................................................................... 31

6.7 SOR for Health Checks of RNC .................................................................................. 32

6.7.1 Health Check of RNC ............................................................................................ 32

6.7.2 Preventive Maintenance of RNC........................................................................... 33

6.8 SOR for Preventive Maintenance of Node B ............................................................ 33

6.8.1 Preventive Maintenance of Node B ...................................................................... 33

6.9 SOR for Health Checks of Ericsson Charging System ........................................... 34

6.9.1 Health Check of Ericsson Charging System ......................................................... 34

6.10 SOR for Health Checks of Comverse RTBS ............................................................. 35

6.10.1 Daily Health Check of Comverse RTBS ............................................................... 35

6.11 SOR for Health Checks of NSN IN@vantage ............................................................ 36

6.11.1 Health Check of NSN IN@vantage ....................................................................... 36

6.12 SOR for Health Checks of CMD Nodes ..................................................................... 36

6.12.1 Health Check of CMD Nodes ................................................................................ 36

6.13 SOR for Health Checks of NBG Nodes ..................................................................... 37

6.13.1 Health Check of NBG Nodes ................................................................................ 37

6.14 SOR for Health Checks of SMSC Nodes ................................................................... 38

6.14.1 Health Check of SMSC Nodes. ............................................................................. 38



6.15 SOR for Health Checks of MMSC Nodes .................................................................. 39

6.15.1 Health Check of MMSC Nodes ............................................................................. 39

6.16 SOR for Health Checks of Transmission Equipment .............................................. 39

6.16.1 Health Check of Transmission .............................................................................. 39

6.17 Preventive maintenance of OMC Computer units: .................................................. 40

6.18 SOR for Health Check for SGSN ................................................................................ 40

6.18.1 Health Check of SGSN ......................................................................................... 40

6.19 SOR for Health Check for FING(GGSN) .................................................................... 41

6.19.1 Health Check of FING(GGSN) .............................................................................. 41

6.20 SOR for Health Check for DNS .................................................................................. 41

6.20.1 Health Check of DNS ............................................................................................ 41

6.21 SOR for Health Check for NTP ................................................................................... 42

6.21.1 Health Check of NTP ............................................................................................ 42

6.22 SOR for Health Check for Radius .............................................................................. 42

6.22.1 Health Check of Radius ........................................................................................ 42

6.23 Preventive Maintenance for BTS/Node B & TX-MW ................................................. 42

7 Process KPI’s ...................................................................................................... 43

7.1 Process KPI Reports ................................................................................................... 43

8 Nomenclature ...................................................................................................... 44

8.1 Circle IDs ..................................................................................................................... 44

8.2 Customer IDs ............................................................................................................... 45

8.3 Node ID ......................................................................................................................... 45

8.4 Date ID .......................................................................................................................... 46

9 Glossary ............................................................................................................... 46



1 Introduction

1.1 Purpose The purpose of this document is to define the Process for carrying out the Preventive Maintenance

activities by identifying and resolving the problems and known errors before they become the network faults which may affect the Network service.

In order to carry out the Preventive Maintenance successfully, appropriate Preventive Maintenance routines are to be defined with responsibilities and procedures to be followed.

This process document is applicable for both SDU and Non-SDU circles.

1.2 Scope The Scope consists of carrying out the regular Preventive Maintenance & Health Check activities of, BSC, RNC, SGSN, GGSN, CMD, IN VAS, Node-B & BTS, TX-Transmission equipments and Infrastructure elements in order to eliminate or minimize the possibility of failure/outages of this Network Element in day to day operations. Preventive Maintenance consists of:

• Scheduling and carrying out preventive maintenance of Network Element as per PrM Process.

• Routine Health check of Network elements as per planned schedule by GNSC/GNOC Team.

1.3 Key Points

Node wise Daily, Weekly, Monthly Health Check activities & their results are to be published by GNSC-FM team on the GNSC Web Portal

GNSC-FM team will publish & share Node wise Weekly, Monthly & quarterly Health Check activities with Circle team via Network Calendar.

Circle team will publish & share Node wise for core elements and site wise for BTS elements Monthly, Quarterly & half-yearly etc. PrM activities with GNSC-FM team via email.

Cluster/ Node wise Field Preventive maintenance (PrM) schedule are to be published by the Cluster Heads/Function Managers/JFLM Managers on the monthly/half yearly basis in advance through PrM Calendar-Tracker.

For PrM Task (Preventive Maintenance Task –On Site), access of PT4 tool is required for all relevant teams. Although manual PrM form must be used until PrM module is ready in PT4 tool.

All Service affecting/or Non Service Affecting PrM & Health Check activities must be executed as per PrM Process.

Before doing the preventive maintenance activity, engineer should take clearance from GNSC AM/ GNSC CM team/Planned activity tracker and after completing the preventive maintenance activity, engineer must inform GNSC AM team.

1.4 Key Interfaces

The Key interfaces for the Preventive Maintenance activities are:

GNSC FM/Core & TX Team: Responsible for most of the Health Check (HC) activities which are done remotely.



Circle Team

1.5 Process Change Control

: Responsible for most of the Preventive Maintenance (on Site) activities which require physical site/ switch visit.

The process will be changed only by the National Process and Quality Team. All suggestions and feedback should be sent to the Document Author.

1.6 Process Definitions

1.6.1 Automatic Maintenance

Automatic Maintenance by the System is done on the integrated network elements and handles all the fault situations and User-initiated configuration management requests within the Hardware and Software of the System. The Automatic Maintenance activities are as below.

1.6.1.1 Supervision of System

a) Detecting the fault in the System by continuously performing the checks b) Sending the fault signal to Alarm System once the fault is detected.

1.6.1.2 Alarm System

a) Identifying the faulty unit by processing the alarm events, b) keeping the alarm into OMU and informing the User and c) Activating the Recovery System.

1.6.1.3 Recovery System

a) Changing the faulty unit state to test (TE) b) Sending the fault localization request to Diagnostic system.

1.6.1.4 Diagnostic System

a) Test the faulty unit to localize the fault and b) Reporting the faulty PIU to the User.

Usually the above activities can be performed remotely except the replacement of hardware if involved. These steps identifies an event or an occurrence that may be classified as an Emergency.

1.6.2 Health Checks

Health Check Activities are done remotely by GNSC FM Team/ or by Circle Team (those nodes which are not migrated to GNSC) for all respective Nodes. For all catagories (service affecting/Non-Service affecting) & Severity (major/minor) of Health Check activities will be done as per PrM process. Most of the Health checks should be carried out on Daily basis in the beginning of every shift to ensure the quality and the state of the Network that it has not been deteriorated. These health checks can performed in regular frequencies like Daily, Weekly & Monthly.

• Daily Health Checks Examples are:

- Service affecting Alarms Status check. - Radio Network Status check. - Working status of functional units in SCN check - Working status check of computer unit

• Weekly Health Checks examples are:

- Updating alarm database - Back up charging files - Check the status of Online charging file



1.6.3 Preventive Maintenance

Preventive maintenance is aimed for prevention of breakdowns and failures. The primary goal of preventive maintenance is to prevent the failure of equipment before it actually occurs. It is designed to preserve and enhance equipment reliability by taking preventive action before they actually fail. These activities are done on-site by Circle teams/ IP vendor and need to perform through proper PrM Form.

• Examples of Preventive maintenance activities are:

- General cleaning of the MTU - Checking Earth resistance and Earth voltage (Before and after monsoon).(checking will be done by infra provider) - Checking VSWR of Feeders as and when required on Node B. - Voltage checks - Cleaning of FDU

All of these activities can be performed only after raising the PrM form either via Manual method (i.e. by submitting PrM Form) or through PT4 tool. Circle Operations need to perform PrM activities via manual method until National Process & Tools team asked circles to start it via PT4 Tool. Both Circle & GNSC/GNOC team need to share their Schedule (Via PrM Calendar-Tracker) with each other every month.

1.6.4 Category of PrM & Health Check (Non-Service & Service Affecting)

Health Checks and Preventive Maintenance activities are categorized in 2 parts: • Non-Service affecting (NSA) or • Service affecting (SA)

1.6.4.1 Non-Service affecting (NSA): Maintenance activity that do not affect the service. Examples are:

• Checking the Network Time. • Checking Blocked alarms. • Charging file backup using DXDAT format

The approved PrM form is required to execute the PrM activities only not for Health Check.

1.6.4.2 Service affecting including May Service affecting (SA): Maintenance activity that affect the Network Service. Before performing any Preventive Maintenance activities, it should be assessed that whether the Service will be interrupted, If so, then such PrM activities have to be executed only after the PrM Form is approved along with proper Risk Assessment. The service affecting tasks are classified as:

• Protection Check for IDU/ODU (MW 1+1) • BSC/Critical node redundant power supply availability • Checking VSWR on Node B/BTS • Battery drain check

All these Service affecting activities needs to have proper planning involved with proper communication in order to keep the GNSC and other stake holders informed . Hence such task should be carried out during the low traffic period. Sometime it may be necessary to prevent (block) the unnecessary alarms being generated from certain network elements towards GNSC during this task.

All Service affecting/May Service affecting PrM Task must be performed during maintenance window defined as per Customer Guidelines



Following points need to be considered carefully before execution: 1. If the task requires a System Restart, it is to be ensured that the measurements are stopped

because a Restart may alter the measurement results. 2. The Service affecting task of Software Upgrades is divided into different groups as shown

below according to delivery mode: • Installation of release-level Upgrade. • Installation of Change Notes • Installation of Feature-level Update • Installation of Technical Note

The Service affecting activity of Hardware Upgrades may be required due to a Software Upgrade. Before carrying out the Service affecting Preventive Maintenance tasks, it is necessary to have a safe copy in order to backup software for the Network element. Safe copying means taking a copy of the Backup(BU) software build either to Fallback(FB) software build on Disk or to any other medium like DAT (for BSC2i) or Magneto-Optical (MO) Disk (for BSC3i or Upgraded BSC2i). For more details please refer Backup & Restore Process.

1.6.5 Severity of PrM & Health Check Activities (Major & Minor type)

1.6.5.1 Major PrM

- SMSC/MMSC

: PrM Activities for All Core Nodes as well as BSC & RNC are defined as Major severity. This may/may not be of Service Affecting activities. For Example: Backup of nodes (Refer B&R Process), Setting of Summer/Winter time fall. This will include:

- SGSN/GGSN - CMD/NBG Node - IN VAS Elements ( Ericsson/RTBS or NSN In@vantage Charging System) - RNC/BSC - New PACO Nodes (FING, FINS, FISN, PCRF) - HLR ( One NDS, DX HLR, NT HLR) - BTS Sites with greater than 6 dependancy

1.6.5.2 Minor PrM

- BTSE

: All PrM & Health Check activities for Node-B/BTS/Tx-MW/ATM Link will be treated as minor type PrM. Although they are service affecting yet are very mild in nature and can be carried out in defined routine services. This will include:

- Node-B - MW Equipment (Link with less than 6 sites dependancy) - Other TX Equipment - TX- HUB Sites

1.6.6 PrM for Infra equipments

Any activity for which Customer or 3rd Party is responsible, then it is out of NSN scope. Third party is responsible for preventive maintenance and health check of equipments under taken by them.The battery drain test is usually carried out by IP Vendor quarterly. Even though it is 3rd

party vendor equipment, for preventive maintenance of infra equipments of core nodes, BSC and RNC nodes, NSN circle has to fill the PrM form, take NSN internal appovals and inform to all stake holders (such as GNSC etc..). Individual PrM form has to be filled up for each activity and proper NSN internal approval for each individual PrM is required, especially for infra related preventive maintenance.



The PrM activity will be done by 3rd

As a part of day to day preventive maintenance of switch location, the site technician must check the voltage,temperature,UPS load and alarms of infra equipments every hour and maintain the record in the register.The record should be strictly verified by the switch manager.

party vendor ( supplier) Engineer/Technician under NSN Engineer’s supervision.

Do’s and Dont’s of battery drain test:

1) The activity planning always to be done in MW between 0000hrs to 0430hrs 2) Common Mail will be sent to Customer, NSN, & GNSC regarding the activity 3) For battery bank testing, battery will never be dis-connected from power plant 4) All testing will be done through controller in power plant 5) It will be defined as 4 hours or 47.5 volts ( whichever early) in power plant as maximum

duration for activating battery plant source in the power plant 6) Individual cell readings must be taken before battery backup check 7) To tighten all the battery cell connections if found loose before the preventive maintenance

activity using proper torque tool 8) After the threshold of 4 hours / 47.5 volts reached, power plant will automatically de-activate

battery bank as the power source 9) Charging will start automatically after EB source becomes the source 10) In no scenario, battery bank will be removed from power plant for testing, because, in that case

manual error can be there while re-connecting the same to power plant such as revered polarity of connection

11) In no scenario, this will be performed outside MW.

The check list of CORE node infra is given below:



2 Preventive Maintenance Process Work Flow

2.1 Process Work Flow Preventive Maintenance Process work flow is as follows:-

Preventive Maintenance Process

Circ

le C

ore

Ops

/SD

EC

ircle

Hea

d/C

TL/ M

anag

er

Team

Lea

d/

GN

SC

FM

Identify NE for Health Check

as per Schedule

Visit the site for PrM activity

of the Node

Are the results satisfactory?

Approve PrMT for Health Checkup

Perform PrM task physically as per

checklist

Yes

NoYes

No

No

Yes

Is it Service Affecting?

Carry out the Health Checks

Analyze the Health checks

Results

Are the results satisfactory?

Create PrM Task for

remote Health Check

Open a Trouble Resolution Ticket

in PT4

Resource Trouble Management Process

Fill PrM Form

Approve PrM Task

Check schedule in

PrM Calander

Upload the results in the Web Portal

Start EndCheck the

schedule of the Health Check

Intimate GNSC AM of

the completion of the PrM

Task

If new alarms found in node during PrM?

Update PrMT in PT4 and

close the PrM Form

No

Upload the PrM results on web

Portal & Report to 1Up Manager

Yes

Close PrM form

Are the spares needed?

Inventory & Spare Management Process

No

YesPlan the site visit for PrM

task

Inform GNSC AM of the

scheduled PrM Task

2.2 Role Mapping of SDU and Non-SDU circles

SDU Non-SDU Circle SDU Head Circle Head

Cluster SDU Head CTL SDE FLM/JFLM

Function Manager Function Manager

2.3 Process Overview

In PrM process, the originator from GNSC or Circle Team will create the PrM task via PrM Form (or through PT4 once it is available) for all Service Affecting/May service affecting PrM and health check activities and for non-service affecting PrM activities only and will get the approval from the authorized approver. Once the PrM Task is approved it will be assign to the executor for the execution.



2.3.1 Explanation of Process Work Flow

GNSC-FM:

GNSC-FM, who is responsible for most of Health Check activities, will check the schedule in Calendar (created & published by GNSC FM Team lead in every month start). The team will identify NE as per schedule. If the activity is:

• Service affecting

•

: FM team must create PrM request for remote Health Check and get an approval from the Circle / Cluster Head as per the Approval matrix. Executor will carry out the health check activity. FM team will analyze the health checks result and if found satisfactory, they will close the PrM form & will publish the Health Check Results on GNSC web portal. Non Service affecting

In any of above cases, even, if the results are found un-satisfactory, then also the results will be uploaded on the Web Portal. But at the same time a Trouble Resolution Ticket will be opened in PT4 and Resource Trouble management Process will be followed thereafter.

: FM Team will carry out the routine Health check activities, for which approval is not mandatory. The Team will analyze the health check results & will publish the same on GNSC web portal

Circle Core Ops/ SDE/ FLM:

Circle Operations team will check out the scheduled PrM activity in the Calendar (created & published by respective Cluster Head/ Functional Head in every month start) and will plan the site visits. The Circle Team will perform following activities:

• Creation of PrM request via PT4/or via manual form: The concerned SDE/ FLM/ CORE Ops/ Team Lead will create the PrM request (fill PrM Form) for preventive maintenance activity and will get it approved from his concerned Team Lead / Cluster Head/ Function Manager/ Circle Head and from Customer (if its service affecting) as per approval matrix in Sec 3.4.

• Interact with I&SPM Process: For availability of Spares, tools and the material required for that specific activity.

• Executor will take clearance from GNSC-AM and CM Team before starting the activity

• Executor will perform the activity and if the end results are found satisfactory then he will inform the GNSC-AM about the completion of the PrM activity.

• Interact with Resource Trouble Management Process: Executor should ensure that GNSC-AM will check the alarms for that relevant node. Executor will leave the site only when he will get clearce from GNSC that every thing is fine after maintenence. Meanwhile, If GNSC-AM finds any alarm on site after completion, then they will refer it to the FM team who will open a Trouble ticket (TTA) in PT4 and will follow the Resource Trouble Management (FM) Process until the issue is resolved.

• SDE/ FLM/Core Ops will update & close the PrM Form and finally return the tools/spare or unused material to SPM Lead.

• Cluster Ops Team will finally update the PrM Calendar and their respective tracker and the results will get uploaded in the web portal.



3 Process Description

3.1 Preventive Maintenance (PrM) Life cycle

This process goes through the following four stages:

3.1.1 Scheduling of PrM

Node wise Preventive maintenance schedules to be published & shared by the Cluster / Functional Head on the monthly basis via PrM Calendar and must be circulated to the SDE/ FLM/ Core Engineer.

Many times PrM Activities can be pre-pone and post-pone due to certain reasons. These activities can be defined and distinguished as under:

Pre-pone:

In this case he must notify GNSC-FM and AM team first, before doing his activity. Also he must refer his TT no as a reason to pre-pone this activity.

When a SDE/ FLM is already on-site (Remote/Rural types) to attend a new fault. He will rectify the fault first & then will complete his PrM Activity by doing Pre-Schedule of that PrM Task. In that case he doesn’t need to come again to do the same PrM for the same site in later stage (i.e. after 1-2 weeks time).

Post-pone:

Although the planned PrM activities need to be performed as per fixed & planned schedule, yet there is a level of flexibility in order to control Operational Expenditure. In any of the case, the difference between 1st & 2nd PrM should not vary more/or less than 2 weeks for Quarterly PrM and for half-yearly it should not vary/deviate more/ or less than 1 month. This means if a PrM is performed on site XYZ on15 May 10, then the next half-yearly PrM (which is planned on 15 Nov) can be done on any day between 15 Oct to 15 Dec provided it has valid justification. However depending on geographical conditions the Prm activities can be preponed upto 2 months.

When the node have got some major changes planned Or it is in embargo stage where all the major activities on-site are frozen.

So, if any activity is rescheduled due to any of the reasons stated above, then the new dates has to be clearly specified in the PrM Calendar.

3.1.2 Performing PrM activities

Approved PrM requests needs to be acknowledged by the SDE/ FLM/ Core Engineer, who will confirm it with the GNSC before visiting the field and will perform the task.

The SDE/ FLM/ Core Engineer will perform the PrM activity according to the correct checklist. He will perform the Preventive maintenance task and fill the checklist accordingly.

The SDE/ FLM/ Core Engineer will cross verify the network Inventory after completing the PrM Task. This is mandatory action must be done as per NSN Guidelines. This will ensure the correctness of Network Inventory & control Operational Expenditure.

The SDE/ FLM/ Core Engineer must also update all stakeholders (his Cluster lead, Logistic Manager & GNSC Team) about all of his PrM tasks where his activity have interacted with existing processes like Spare Management/ Network Change Management or Backup & Restore Management. The interaction of the Process with other processes such as Inventory



and Spare Management, Resource Trouble Management and Network Change Management has been described in the Process Work flow.

3.1.3 Reporting PrM Tasks

PrM Task needs to be reported to GNSC/Circle once it is done. The SDE/ FLM will inform the GNSC-AM team to get permission to leave the site.

3.1.4 Closure of the Preventive Maintenance tasks

PrM Task needs to be closed by GNSC/Circle Team once it is done. They will update the PrM Form including log of complete action.

SDE/ FLM/ Core Engineer must update his excel for the exact date of PrM of a particular site and send the report back to the Cluster/ Functional Head at the end of the month.

3.2 Preservation of PrM Reports

At the end of every month certain PrM and Health check reports are generated and these reports have to be properly preserved for future reference and also to be produced before the Customer if asked.

All the PrM forms and the Calendars must be preserved for at least 1 Year for future reference & auditing purpose. Also the filled checklist forms have to be preserved along with the PrM forms and Calendars.

3.3 Roles and Responsibilities for PrM & health Checks activity

ROLE RESPONSIBILITY

GNSC-FM Team

Schedule and perform DAILY/WEEKLY/MONTHLY/ PRE-FESTIVAL/ ANNUAL Health checks.

Create PrM request (manually or via PT4) for all Service affecting activities based upon Health Check Scheduled like MONTHLY/ PRE-FESTIVAL/ ANNUAL

Analyze the Daily/Weekly/Monthly Health check results.

Upload the results on Web Portal.

Open the Trouble Ticket(TT) in PT4 and follow Trouble Resolution Management (FM) Process, if results are not satisfactory

All software versions management should be done as per NSN Product/Care guidelines. Also Reconciliation need to be done quarterly for the same.

Circle Core Ops/ SDE/ FLM

Checks the PrM scheduled in shared Calendar and plan the site visit.

Create PrM request, get approval, take clearance from GNSC-AM & CM team and conduct the PrM Task for all Service affecting activities.

All hardware versions management should be done as per NSN Product/Care guidelines. Also Reconciliation needs to be done quarterly for the same.



Notify GNSC-AM team about completion of PrM task, and leave the site only after clearance from the GNSC-AM team. Update & Close the PrM Task & Calendar. Finally send the completed PrM form back to Functional head for updating his PrM Tracker.

CTL/ Team Lead/ Manager

Prepare the PrM schedule, shared the calendar, Create PrM Task, get approval and update the PrM tracker

Circle Head Approve the PrM form

3.4 Schedule for Health Check and Preventive Maintenance activities

Preventive Maintenance and Health Check Schedule

Sr no. NE Type Daily HC

Weekly HC

Monthly HC

Pre-festival

HC Monthly

PrM

Quarterly routine

PrM

Half-yearly PrM

Pre Monsoon PrM

Yearly PrM

1 BTS

2 MW and TX Equipment

3 Node B 4 Routers 5 Firewalls 6 BSC 7 RNC

8

Ericsson Charging System

9 Comverse RTBS

10 NSN IN@vantae

11 NBG The Pre-Festival Health Checks are not mandatory, but good to conduct for major festivals. As we have to do the BTS PrM half yearly, suggest to do one in pre monsoon and the other one after six month. Process recomondation is to do the BTS PrM half yearly but if circles have a different agreement with customer then please follow the customer agreement.

Approval Matrix for Health Check and Preventive Maintenance

The Health Check and onsite Preventive Maintenance activities can be grouped as Daily, Monthly, Quarterly, Half-yearly and Pre-festival. These activities can be of Major or Minor severity. PrM Task has to be approved accordingly by the Team Lead/ Functional head or the Circle head based on its severity & Customer impact..

However,NSA Routine Health Checks doesn’t require any approval.



The approval matrix per Node element can therefore be defined as:

PrM _Approval Matrix Sr. No NE Type PrM Schedule Severity of

Activity Type Approver

1 BSC Half-Yearly

Major SA

Functional Head, Circle Head & Customer

(optional)

Pre-Festival NSA Functional Head/ Team Lead/ CTL

2 RNC Half-Yearly

Major SA

Functional Head, Circle Head & Customer

(optional)

Pre-Festival NSA Functional Head/ Team Lead/ CTL

3 Ericsson Charging System

Weekly Major NSA Functional Head/ Team

Lead/ CTL Monthly

4 Comverse RTBS

Weekly Major NSA Functional Head/ Team Lead/ CTL Monthly

5 CMD Weekly Major NSA Functional Head/ Team Lead/ CTL Pre-Festival

6 NBG Weekly

Major NSA Functional Head/ Team Lead/ CTL Pre-Festival

Pre-Festival

7 Transmission Equipment Pre-Festival Minor May

SA Functional Head/ Team

Lead/ CTL

8 BTS

Half-Yearly Minor NSA Functional Head/ Team Lead/ CTL

Half-Yearly Major SA Functional Head, Circle

Head & Customer (optional)

9 Microwave/TX Equipment

Half-yearly Minor NSA Functional Head/ Team Lead/ CTL

Half-yearly Major SA Functional Head, Circle


10 Node B

Quarterly Minor NSA Functional Head/ Team Lead/ CTL

Half-yearly Major SA Functional Head, Circle


Half-Yearly Preventive Maintenance for BTS & Node-B is service affecting for Sector not for the whole site. Sector wise outage duration must be mentioned in PrM Form very clearly for activity like VSWR measurement.

Customer approval for All service affecting/ May service affecting PrM activities are

required as per Customer Guideline/Instruction.

4 Preventive maintenance via PrM Form (Manual Process)

The Preventive Maintenance Process is to be carried out manually via PrM form until PrM module in PT4 Tool is ready to start. The Process life cycle will be same as described in section 3.1 to 3.4 with some additional responsibilities.



MONTHPlanned

date NETWORK

NODE

Site ID (INDUS ID/ Other IP ID)

Severity of Activity

Category of activity

Name of the Activity

Activity start time

Activity end time

Executor Name

PrM Form No.

Execution Date

Activity Actual

start time

Activity Actual

end time

Executor Remarks

Submission Date

Submitted To Status

DATE (if rescheduled

)

Reason for reschedule

RESCHEDULING STATUSPrM CALENDAR PrM TRACKER

PrM Calendar-Tracker for Jan-Mar 2011

4.1 Scheduling

The Process starts with scheduling which is need to be defined in PrM Calendar. Both Circle & GNSC/GNOC team needs to share their Schedule via PrM Calendar with each other. GNSC-FM team and the Circle Team will publish & share Node wise Weekly, Monthly & Bi-yearly Health Check activities with each other via Network Calendar. The Calendar has to be published every month by the Team lead/ Cluster Head and a record of rescheduled activities are also to be kept. The Calendar has to be shared with the Customer and approval has to be taken before publishing the Calendar if the Customer guidelines states.

The network Calendar with tracker will have the fields as shown below. The activity schedule and the executor details must to be specified clearly. The scheduler has to indicate that whether the Health Check/ PrM activity is Service Affecting. If it's Non-service/ service affecting PrM or Service affective HC then prior approval is required for PrM request. If GNSC/ Circle ops couldn’t be able to perform the PrM/ Health Check on time, due to some major issues, then they should specify the Rescheduled date & Reason for that activity.

4.2 Performing

Once the schedule is planned and shared by GNSC-FM and the Circle Team, the next step is to execute it i.e. to perform the Health Checks/ PrM activity.

The PrM executor (SDE/ FLM/ Core Engineer) will inform to GNSC-AM/FM/CM Team(if required) with his PrM Form No. before starting the activity to get clearance to work. GNSC AM team will ensure that there is no major alarm for that site/Node.

The PrM form has dropdowns for Type (i.e. Service affecting and Non-service Affecting) and the Severity (i.e. Major and Minor) which is to be carefully filled as per defined in Responsibility Matrix (section 6) & In case of service affecting activities, a proper approval has to be taken as per Approval Matrix.(defined in Section 3.3) from Team Lead/ Functional Head + Circle Head + Customer ( if required as per customer guidelines) . Approvers Name along with their Contact number and Email IDs is to be filled in the PrM Form.

Each form has a unique PrM form number. A consistent nomenclature is to be followed in filling the PrM Form number.

Nomenclature for the PrM Form Number:

The PrM Form number will be a 16 digit unique number of the form: CPWWWWWWNI_YYMMDD

Where:

C: One letter ID for the Circle

P: One letter ID for the Customer

WWWWWW: The 6 Characters can be used for Node ID. In case all 5 digits are similar, we can use the last 2-3 digit to make the node unique.



NI: Where N indicates Routine ((M-Monthly, Q-Quarterly, H-Half Yearly, P-Pre/Post Festival) & I indicates frequency (1-2-3 or 4) of Preventive maintenance schedule of that NE.

YYMMDD: Year/ Month/ Date

For example: PrM Form number: QB MG5365 Q1_100912 indicates First Quarterly PrM of BTS- MG5365 of customer Bharti for Rest of Maharashtra.

Other PrM Details must be carefully filled in the Form given below. Following points need to be taken care of:

Affected party information need to be clearly defined. All the parties & team which are getting affected for this PrM must be notified prior to this activity.

After Work Detail Information section, Work Results must be filled & at the end of this sheet there is a Status Tab which must be clearly specified whether PrM Activity is successful or not. This can be selected from the radio Button

Reason for rescheduling of the Task due to any reason must be specified clearly. Next Date, Time also required to be filled.



Here is the sample of the PrM form:

The SDE/ FLM/ Core Engineer will perform the PrM Task according to the correct checklist. He will perform the Preventive maintenance task and fill the checklist accordingly. In last he will also cross verify the network Inventory & Site+ Data, after completing the PrM Task. This will ensure the correctness of Network Inventory & control Operational Expenditure.

4.3 Reporting

Health check Reporting by GNSC/GNOC-FM Team

o GNSC FM Team is responsible for the Max. Health Check activities and so generate

the health check report based upon the outcome of the health check results. The report will be uploaded on the web portal.

Generation of Health Check Reports



o The health check reports so created shall be stored for the period of one quarter. And their respective backup needs to be stored as per Backup & Restore Process.

Record Keeping of the Health Check Reports

At the end of every month a monthly report has to be generated :

Monthly Report Generation and Preservation

At the end of every month, FM Manager will prepare and share a monthly tracker showing the status of all health check activities performed for that account to Circle head and functional managers.

Health check Reporting :

PrM Reporting :

At the end of every month, a monthly tracker has to be generated and shared by functional head with circle head, GNSC COM & P&Q Team for all PrM activity performed in that month.

This report will contain the list of activities being done including all rescheduled ones. (and has to be submit to the Customer if asked)

Note: All the PrM forms, checklists, Calendars and Trackers must be preserved for at least for 1 Year for future reference & auditing purpose

4.4 Closing

The Process ends with the Closing of the PrM request. Once SDE/ FLM/ Core Engineer have completed their PrM Task, they will intimate it to GNSC-AM to get clearance to leave the site. Finally he will close his PrM Form along with the status & will submit it to his Functional head.

5 Preventive Maintenance via PT4 Tool (applicable to PT4 rolled out circles)

Once the PT4 tool for Preventive maintenance comes into action, the Circle Operations and the GNSC has to perform all the Preventive Maintenance activities/ Health Checks via the PT4 tool only.

For PrM Task, all Originators/Executors should use the PT4 tool.

5.1 Scheduling

All the PrM tasks will be scheduled and shared via Calendar as explained in the Process without PT4. The format of the Calendar will remain the same as followed with the manual process without PT4.

5.2 Performing

The executor of the activity has to create a PrM request through the PT4 tool. All the PrM activities need to be performed via PT4 tool. The concerned SDE/ FLM/ Team Lead will create the PrM request in PT4 and follow the Task Flow as shown below.



5.2.1 PRM TASK Flow diagram in PT4 for Circle team: (not ready yet)

START

Assigned to SDE/ FLM

Perform the activity

Update the PrM Task

RejectApprove

Cluster head for approval

Inform to GNSC-AM

Team

PrM Task created by SDE/ FLM

PrM Task created & approved by Manager/

Team lead

PREVENTIVE MAINTAINANCE TASK FLOW IN PT4

There are two ways of creating the PrM Task in Circle:

1. Via Functional Manager or

2. Via SDE/ FLM/ Switch Engineer.

PrM Task created by Manager: - The functional Head/Manager/lead create the PrM Task, approve and will assign it to the concerned SDE/ FLM who will inform the GNSC-AM before performing the PrM Task. Once the PrM Task is performed successfully then he will update the PRM Task accordingly & will inform again to GNSC-AM team to get permission to leave the site.

PrM Task created by SDE/ FLM/ SE

•

: If the PrM Task is created by the SDE/ FLM/ , then he has to get the approval from the concerned Cluster Head /Manager who can further reject or approve it accordingly. There are two scenarios:

Rejected

•

: If it is rejected by the Cluster Head/Manager then it will go back to the originator i.e. SDE/ FLM who created that PrM Task and he will again submit it after making the necessary changes suggested to him as per the rejection. Or

Approved If it is approved then the assigned SDE/ FLM will perform that PrM Task after informing to the GNSC and will update it accordingly after completing the PrM Task.



5.2.2 PrM Task Status flow in PT4

Cluster Lead/ Functional head will create the Schedule in PrM Calendar & will share it with GNSC & Other team. Then either him or the originator will create the PrM Task in PT4 as per plan/schedule in the Calendar. He will plan it, get it authorized if its service affecting in nature. Assign it to the concerned assignee, who will acknowledge it and will execute the PrM Task after informing the GNSC-AM Team. The assignee will perform the PrM Task according to the correct checklist. He will perform the Preventive maintenance task and fill the checklist accordingly. He will also cross verify the network Inventory after completing the PrM Task. This will ensure the correctness of Network Inventory & control Operational Expenditure.

Once PrM Task is done satisfactory then again he will inform the GNSC-AM to get approval to leave the site. Finally he will update and will be closed the PrM Task in PT4 with comments and finding or punch points from the executor.

5.3 Reporting

At the end of every month a consolidated report has to be generated to be produced in front of the Circle Head by Functional heads (Cluster Head). All these reports & Evidences will be generated and preserved in the PT4 tool. These reports will contain complete list of Tasks being performed by the executor. All the PrM forms will be preserved for future reference.



5.4 Closing

Once SDE/ FLM has completed his PrM Task, he will update the same in PT4 tool including log of complete action/ or ask SPOC in Circle Operations to update his PrM Task on his behalf if he is unable to access PT4 tool.

6 Health Check and Preventive Maintenance Responsibility Matrix (SOR)

6.1 SOR for Health Check of HLR

SA: Service Affecting NSA: Non-service Affecting

6.1.1 Health check of HLR

Health Check of HLR Sr. No. FORM DESCRIPTION Frequency Category Responsibility 1 Element Details Daily NSA GNSC- FM Team 2 Command calendar tasks Daily NSA GNSC- FM Team 3 Display the blocked alarm details Daily NSA GNSC- FM Team 4 All units states Daily NSA GNSC- FM Team 5 Disk units Daily NSA GNSC- FM Team 6 Synchronization state Daily NSA GNSC- FM Team 7 Check for link state in UA-INS Daily NSA GNSC- FM Team 8 Link load Daily NSA GNSC- FM Team 9 Link set data Daily NSA GNSC- FM Team

10 Route set data handling Daily NSA GNSC- FM Team 11 SCCP state handling Daily NSA GNSC- FM Team 12 GT analysis Daily NSA GNSC- FM Team 13 GSM measurement Daily NSA GNSC- FM Team 14 Linkage data Daily NSA GNSC- FM Team 15 NSAP_data Daily NSA GNSC- FM Team

16 License capacity utilization for those features loaded in the system(UCAP) Daily NSA GNSC- FM Team

17

License capacity utilization should be less than 80%. Daily NSA GNSC- FM Team

18 HLR subscriber handling Daily NSA GNSC- FM Team 19 Subscribers in AUC Daily NSA GNSC- FM Team 20 Active alarms in HLR Daily NSA GNSC- FM Team 21 Disk Handling Daily NSA GNSC- FM Team 22 Measurement files Daily NSA GNSC- FM Team 23 Alarm history Daily NSA GNSC- FM Team 24 Processor load Daily NSA GNSC- FM Team 25 Unit Load Sharing Pre Festival NSA GNSC FM Team 26 Number of Signaling links in link set Pre Festival NSA GNSC FM Team

27 Licenses should be Checked in MSS / HLR / MGW Pre Festival NSA GNSC FM Team

28 Signaling Link Load Verification Pre Festival NSA GNSC FM Team 29 Signaling Link Load Verification Pre Festival NSA GNSC FM Team 30 Processor load Pre Festival NSA GNSC FM Team 31 Active alarms MSC Pre Festival NSA GNSC FM Team 32 Alarm history Pre Festival NSA GNSC FM Team

Note : Point 25 to 28 activities; Perform 7 Days before the Commencement of any festival.



6.1.2 Preventive Maintenance of HLR

Preventive Maintenance of HLR Sr. No. FORM DESCRIPTION Frequency Category Responsibility

1

Check for proper working of External Power supplies and their Alarm systems. Monthly NSA CIRCLE Core Ops

2

Check for proper working of Environmental equipments like Fans, Air conditioning etc and their Alarm systems. Monthly NSA CIRCLE Core Ops

6.2 SOR for Health Checks and PrM of MSS-GCS and GMSC

6.2.1 Health Check of MSS-GCS & GMSC

Health Check of MSS-GCS & GMSC Sr. No. FORM DESCRIPTION Frequency Category Responsibility 1 Element details Daily NSA GNSC-FM Team 2 Command calendar tasks Daily NSA GNSC-FM Team 3 Display blocked alarm details Daily NSA GNSC-FM Team 4 All units states Daily NSA GNSC-FM Team 5 Disk units Daily NSA GNSC-FM Team 6 Synchronization state Daily NSA GNSC- FM Team 7 C7 link states Daily NSA GNSC- FM Team 8 Link load Daily NSA GNSC- FM Team 9 Link set data Daily NSA GNSC- FM Team

10 Route set data handling Daily NSA GNSC- FM Team 11 SCCP state handling Daily NSA GNSC- FM Team 12 GT analysis Daily NSA GNSC- FM Team 13 Circuit group Daily NSA GNSC- FM Team 14 Circuit states in CGR Daily NSA GNSC- FM Team 15 MGW data Daily NSA GNSC- FM Team

16

SIGU-ISU communication status (To ensure Status of State estabilshment of both Primary & Sec is ACT. Daily NSA GNSC- FM Team

17

Active alarms in MSC (Act on the alarm based on severity/impact.) Daily NSA GNSC- FM Team

18

Alarm history (Verify the disturbance and critical alarms) Daily NSA GNSC- FM Team

19 Measurement files Daily NSA GNSC- FM Team 20 Charging files Daily NSA GNSC- FM Team 21 Disk handling Daily NSA GNSC- FM Team 22 Subscribers in VLR Daily NSA GNSC- FM Team 23 BS controller data Daily NSA GNSC- FM Team 24 Association set Daily NSA GNSC- FM Team

25 Check and match the HMS/Boot version between memory and disk. Daily NSA GNSC-FM Team



26 Processor load Daily NSA GNSC- FM Team

27 Unit Load Sharing Pre Festival NSA GNSC-FM TEAM

28 Number of Signaling links in link set Pre Festival N7 SA GNSC-FM TEAM

29 Licenses should be Checked in MSS / HLR / MGW

Pre Festival NSA GNSC-FM TEAM

30 Signaling Link Load Verification Pre Festival NSA GNSC-FM TEAM

31 Matching the Circuits definitions in BSS,MGW & MSS

Pre Festival NSA GNSC-FM TEAM

32 CIRCUIT STATES IN CGR Pre Festival NSA GNSC-FM TEAM

33 Signaling Link Load Verification Pre Festival NSA GNSC-FM TEAM

34 PROCESSOR LOAD Pre Festival NSA GNSC-FM TEAM

35 Clear Code Pre Festival NSA GNSC-FM TEAM

36 VLR Capacity Utilization Pre Festival NSA GNSC-FM TEAM

37 Active alarms in MSC Pre

Festival NSA GNSC-FM TEAM

38 Alarm history Pre

Festival NSA GNSC-FM TEAM

Note : Point 31 to 35 activities , Perform in 7 Days before the Commencement any festival

6.2.2 Preventive Maintenance of MSS-GCS & GMSC

Preventive Maintenance of GCS & GMSC Sr. No. FORM DESCRIPTION Frequency Category Responsibility

1

Audit Trail of Digit analysis (checking NLD/ISD/Local/Short codes and their routing) Monthly NSA

CIRCLE and Core Planning Team

2 Check for proper working of External Power supplies and their Alarm systems. Monthly NSA CIRCLE Core Ops

3

Check for proper working of Environmental equipments like Fans, Air-conditioning etc and their Alarm systems. Monthly NSA CIRCLE Core Ops

4

Check the number of circuits added in each VMGW. .(The information must be shared with Circle Planning Team for verification as per planning guidelines) Monthly NSA


6.3 SOR for Health Checks & PrM of MGW

6.3.1 Health Check of MGW

Health Check of MGW Sr. No. FORM DESCRIPTION Frequency Category Responsibility

1 ELEMENT DETAILS Daily NSA GNSC-FM Team 2 COMMAND CALENDER TASKS Daily NSA GNSC-FM Team



3 BLOCKED ALARMS Daily NSA GNSC-FM Team 4 ALL UNITS STATES Daily NSA GNSC-FM Team 5 DISK UNITS Daily NSA GNSC-FM Team 6 SYNCHRONIZATION STATE Daily NSA GNSC-FM Team 7 C7 LINK STATES Daily NSA GNSC-FM Team 8 LINK LOAD Daily NSA GNSC-FM Team 9 LINK SET DATA Daily NSA GNSC-FM Team 10 ROUTE SET DATA HANDLING Daily NSA GNSC-FM Team

11

CIRCUIT STATES IN CGR (Action need to taken for those Circuit in faulty states) Daily NSA GNSC-FM Team

12 ASSOCIATION SET Daily NSA GNSC-FM Team 13 VIRTUAL MGW DATA Daily NSA GNSC-FM Team 14 ACTIVE ALARMS IN MGW Daily NSA GNSC-FM Team 15 ALARM HISTORY Daily NSA GNSC-FM Team 16 MEASUREMENT FILES Daily NSA GNSC-FM Team 17 DISK HANDLING Daily NSA GNSC-FM Team 18 PROCESSOR LOAD Daily NSA GNSC-FM Team

19 Check and match the HMS/Boot version between memory and disk. Daily NSA GNSC-FM Team

20 Erlangs Utilization (Equipped erlangs and active erlangs) Daily NSA GNSC-FM Team

21 Unit Load Sharing Pre festival NSA GNSC-FM TEAM

22 Circuits per ISU / SIGU Pre festival NSA GNSC-FM TEAM

23 Number of Signaling links in link set Pre festival NSA GNSC-FM TEAM

24 Licenses should be Checked in MSS / HLR / MGW Pre festival NSA

GNSC-FM TEAM

25 Signaling Link Load Verification Pre festival NSA GNSC-FM TEAM

26 PROCESSOR LOAD Pre festival NSA GNSC-FM TEAM

27 ACTIVE ALARMS IN MSC Pre festival NSA GNSC-FM TEAM

28 ALARM HISTORY Pre festival NSA GNSC-FM

TEAM Note : Point 20 to 24 activities , Perform in 7 Days before the Commencement any festival

6.3.2 Preventive Maintenance of MGW

Preventive Maintenance of MGW Sr. No. FORM DESCRIPTION Frequency Category Responsibility

1 Check for proper working of External Power supplies and their Alarm systems if remote. Monthly NSA CIRCLE Core Ops

2

Check for proper working of Environmental equipments like Fans, Air conditioning etc and their Alarm systems if remote. Monthly NSA CIRCLE Core Ops

3

Check the number of circuits added in each VMGW.(The information must be shared with Circle Planning Team for verification as per planning guidelines) Monthly NSA


4 Check the Erlangs utilization, CGR utilization and STM utilization Monthly NSA




5 Check the License utilization in MGW Monthly NSA CIRCLE and Core

Planning Team

6.4 SOR for Health Checkup of Router

6.4.1 Health Check of Routers

Health Check for Routers Sr.No. Form Description Expected Results

Frequency Category Responsibility

1 Checking Version Information

Display the output of Release version Daily NSA GNSC

2 Checking current configuration (DRAM)

Display the output of Running Configuration Daily NSA GNSC

3

To check startup configuration (NVRAM)

Display the output of Startup Configuration Daily NSA GNSC

4

To check all logs that the router has in its memory Display the Logs Daily NSA GNSC

5

To check All Interfaces on the Router

Display the output of all Interfaces Daily NSA GNSC

6

Checking the interface status of interface e0 Display interface on e0 Daily NSA GNSC

7 Checking type of serial cable on s0

Display the serial cable type Daily NSA GNSC

8

Check the status of current routing protocols and dynamic routing protocol.

Display current routing protocols Daily NSA GNSC

9 Check the IP Routing Table Display IP routing table Daily NSA GNSC

10 Display access lists

Display access lists, this includes the number of displayed matches Daily NSA GNSC

11 To check Uptime Display the Up time of the router Daily NSA GNSC

12 To check log buffer Display the Logging Information Daily NSA GNSC

13 To check time sync status with NTP Display the ntp status Daily NSA GNSC

14 To check memory status

Display the Memory Status Daily NSA GNSC

15 To check power status

Display the Power Status Daily NSA GNSC

16 To check CPU utilization

Display the CPU Utilization Daily NSA GNSC

17 To Check Active Alarms

Display the Status of Active Alarm Daily NSA GNSC

18

To Check the current router time and time since

Display the current router time and time since Daily NSA GNSC



19 To check LED status on router front panel

Display the LED status on router front panel Daily NSA GNSC

20

To Check the status of interfaces configured in Router,

Display the status of interfaces configured in Router. Daily NSA GNSC

21 To Check the hardware details

Display the status of hardware details Daily NSA GNSC

22

To Check the Power, Fan and Temperature status at Router chassis

Display the status of Power, Fan and Temperature at Router chassis Daily NSA GNSC

23

To check PIC status should be online in command output

Display the status of PIC in Chassis Daily NSA GNSC

24

To Check All configured BGP peer should be UP

Display the status of All configured BGP peer Daily NSA GNSC

25 To Check the CPU of Routing Engine

Display the status of Routing Engine Daily NSA GNSC

26 Display port channel list

Display the list of Port channel in Router Daily NSA GNSC

27

To Check the Port Channel Status between different link where the routers are deployed in 1+1 configuration

Display the port channel status in different link b/w SGSN-GGSN, GGSN-Firewall, Router-Firewall, Firewall-Router, Router-ISP Router, Router-MPLS Daily NSA GNSC

28 Checking of air filter

Cleaning or replacement of air filter as and when required

Fortnightly NSA Circle core ops

SA: Service Affecting NSA: Non-service Affecting

6.5 SOR for Health Checks of Firewalls:

6.5.1 Health Check of Firewalls

Health Check for Firewall Sr.No. Form Description Expected Results

Frequency Category Responsibility

1 To check Uptime To see the uptime of the

firewall Daily NSA GNSC-FM

Team

2 To check CPU

utilization To see the CPU

utilization of the firewall Daily NSA GNSC-FM

Team

3 To check memory

utilization To see the Memory of

the firewall Daily NSA GNSC-FM

Team

4 To check interface

status To see the all interface

status in firewall Daily NSA GNSC-FM

Team

5 To check chassis

status To see the all Chassis


Team

6 To check FW

Master/Backup status To see the Firewall

status Master/Backup Daily NSA GNSC-FM

Team



7 To check sync status

with NTP To see the all Firewall Sysn. status with NTP Daily NSA

GNSC-FM Team

8 To check default v

router To Check the default

router Daily NSA GNSC-FM

Team

9 To check routes To Check the default

routes Daily NSA GNSC-FM

Team

10 To check zones

created To Check the zone


Team

11 To check addresses To Check the address


Team

12 To check policy To Check the policy


Team

13 To get the config. To take a Backup of

firewall Daily NSA GNSC-FM

Team

14 To Get the Firewall

Info To get a firewall

information Daily NSA GNSC-FM

Team

6.6 SOR for Health Checks of BSS

6.6.1 Health Check of BSC

Health Check for BSC Sr. No. FORM DESCRIPTION Frequency Category Responsibility 1 COMMAND CALENDER TASKS Daily NSA GNSC- FM Team 2 BSC & BTS BLOCKED ALARMS Daily NSA GNSC- FM Team 3 COMP UNITS STATES Daily NSA GNSC- FM Team 4 COMP UNITS STATES IN NO-WO STATE Daily NSA GNSC- FM Team 5 GPRS LINK STATUS Daily NSA GNSC- FM Team 6 SS7 SIGNALING LINK STATUS Daily NSA GNSC- FM Team 7 TCSM & CGR STATUS Daily NSA GNSC- FM Team 8 DISK UNITS Daily NSA GNSC- FM Team 9 SYNCHRONIZATION STATE Daily NSA GNSC- FM Team 10 ACTIVE ALARMS IN BSC Daily NSA GNSC- FM Team 11 MEASUREMENT FILES Daily NSA GNSC- FM Team 12 OSCILLATOR CONTROL VALUE Daily NSA GNSC- FM Team

13 BSC SYNCH INPUT ET CHECK Daily NSA GNSC- FM Team &

Circle

14 Status of DAP distribution to be checked in all BCSU. Daily NSA GNSC- FM Team

15 X.25 STATE Daily NSA GNSC- FM Team

16 TRX Lapd distribution status to be checked in all BCSU. Fortnightly NSA GNSC- FM Team

17 All BSC units Working Status Pre-Festival NSA GNSC-FM TEAM

18 Major & Critical Alarms to be verified Pre-Festival NSA GNSC-FM TEAM

19 All the SYNC inputs are connected and clocks units ok

Pre-Festival NSA

GNSC-FM TEAM/ Support from Circle

Team

20 All BCF Synch settings / DAC values based on alarms to be checked

Pre-Festival NSA GNSC-FM TEAM

21 All computer / sig unit CPU utilization & signaling load observation

Pre-Festival NSA GNSC-FM TEAM

22 Verification of all transcoders, circuits & its Pre- NSA GNSC-FM TEAM



LAPD Festival

23 Checking the status of all Gb links Pre-Festival NSA GNSC-FM TEAM

24 Checking the status of TRX'S AND TS'S Pre-Festival NSA GNSC-FM TEAM

25 The LAPD of the BCCH TRX is 32 Kbps if the LU or Paging is high for specific BTS

Pre-Festival NSA Circle - Team

26 MBCCH /MBCCB defined and optimum SDCCH’s are defined per sector


27 Optimize the time slots defined for GPRS/EDGE on BTS


28 Proper distribution between AMR and Non-AMR CGR’s/ TCSM’s


29 SIGNALLING link STATE Pre-Festival NSA GNSC-FM TEAM

30 X.25 state Pre-Festival NSA GNSC-FM TEAM

31 BSC external alarm ok Pre-Festival NSA

GNSC-FM TEAM & Circle - Team both

32 BSC/Critical node redundant power supply availability

Pre-Festival NSA

GNSC-FM TEAM & Circle - Team both

33 VDU working at the BSC location with One cable for service terminal made available


34 Equal Distribution of CCS7 and LAPD signaling links

Pre-Festival NSA

GNSC-FM TEAM & Planning team

35 Path protection Testing for Ater, Gb and X.25 Pre-Festival NSA Circle - Team

36 HWAT Toggle switch position Pre-Festival May be SA Circle - Team

37 Availability of Critical Spares at site Pre-Festival NSA Circle - Team

6.6.2 Preventive Maintenance of BSC

Preventive Maintenance of BSC Sr. No. FORM DESCRIPTION Frequency Category Responsibility 1 Diagnose computer units Half Yearly NSA GNSC-FM TEAM

2 Check for proper working of External Power supplies and their Alarm systems if remote. Monthly NSA Circle Ops Team

3

Check for proper working of Environmental equipments like Fans, Air-conditioning etc and their Alarm systems if remote. Monthly NSA Circle Ops Team

4 Soft Switch over of computer units Half Yearly

May be Service Affecting GNSC-FM TEAM



6.7 SOR for Health Checks of RNC

6.7.1 Health Check of RNC

Health Check of RNC Sr. No. FORM DESCRIPTION Frequency Category Responsibility 1 Check active alarms Daily NSA GNSC- FM Team 2 Check past critical alarms for last 24 hrs Daily NSA GNSC- FM Team 3 Blocked alarms Daily NSA GNSC- FM Team 4 Check functional states of each unit Daily NSA GNSC- FM Team

5 Check the working state of I/O devices disk units Daily NSA

GNSC FM Team and Circle Ops Team

6 C7 LINK STATES Daily NSA GNSC FM Team 7 Speech circuits and circuit group Daily NSA GNSC FM Team 8 Check the state of ATM Interface Daily NSA GNSC FM Team 9 Check the state of TCP/IP ATM Interface Daily NSA GNSC FM Team

10 Check the host reach ability(Pinging) Daily NSA GNSC FM Team

11 Check current radio alarms from RNC Transmission view. Daily NSA GNSC FM Team

12 Element details Daily NSA GNSC FM Team 13 Command calendar tasks Daily NSA GNSC FM Team 14 Synchronization state Daily NSA GNSC FM Team 15 Link load Daily NSA GNSC FM Team 16 Link set data Daily NSA GNSC FM Team

17

Route set states need to be observe for both NA0 and NA1.Verify in the output “CONG” for no congestion in that route. Daily NSA GNSC FM Team

18 The state of ASSOCIATION SET(it must be ASP-ACTIVE) Daily NSA GNSC FM Team

19 Measurement files Daily NSA GNSC FM Team

20 Disk handling Daily NSA

GNSC FM Team and Circle Ops Team

21 Processor Load Daily NSA GNSC FM Team 22 Checking blocked alarms Weekly NSA GNSC FM Team 23 Checking the maintenance mode Weekly NSA GNSC FM Team 24 Cleaning up alarm acknowledgement Weekly NSA GNSC FM Team 25 Updating the alarm database Weekly NSA GNSC FM Team 26 Checking the network time Weekly NSA GNSC FM Team 27 C7 Link states Pre Festival NSA GNSC FM Team 28 Number of Signaling links in link set Pre Festival NSA GNSC FM Team

29 Licenses should be Checked in MSS / HLR / MGW/RNC Pre Festival NSA GNSC FM Team

30 Signaling Link Load Verification Pre Festival NSA GNSC FM Team 31 Processor Load Pre Festival NSA GNSC FM Team

32 Active alarms in MSC(Act on the alarm based on severity impact) Pre Festival NSA GNSC FM Team

33 Alarm history Pre Festival NSA GNSC FM Team Note : Point 27 to 32 , Performed in 7 Days before the Commencement any festival



6.7.2 Preventive Maintenance of RNC

Preventive Maintenance of RNC Sr. No. FORM DESCRIPTION Frequency Category Responsibility

1 Check for proper working of External Power supplies and their Alarm systems if remote. Monthly NSA

Circle Ops Team

2

Check for proper working of Environmental equipments like Fans, Air-conditioning etc and their Alarm systems if remote. Monthly NSA

Circle Ops Team

3 License verification and validation Monthly NSA Circle Ops Team

4 Check and verify for the availability of the latest s/w Monthly NSA

Circle Ops Team

5 Diagnose of computer units Half yearly NSA GNSC FM Team

6.8 SOR for Preventive Maintenance of Node B

6.8.1 Preventive Maintenance of Node B

Preventive Maintenance of Node B Sr. No. FORM DESCRIPTION Frequency Category Responsibility 1 Check H/W status/ Alarms Quarterly NSA GNSC_FM Team 2 Check License status/ Alarms Quarterly NSA GNSC_FM Team 3 Fetch BTS Log Files Quarterly NSA GNSC-FM Team 4 BTS Performance Monitoring Quarterly NSA GNSC-FM Team 5 Check BER test Quarterly NSA Circle Ops Team &

support from GNSC FM Team

6 Check BTS Clock Quarterly NSA GNSC-FM Team 7 WCDMA Loop Test Quarterly NSA GNSC FM Team and

Circle Ops Team 8 Check Physical Layer, IUB ,ATM , IP

Configurations Quarterly NSA GNSC FM Team and

support from Circle Ops Team

9 NTP Server Status Quarterly NSA GNSC FM Team and Circle Ops Team

10 Check EAC States Quarterly NSA GNSC FM Team 11 Update the Logbook Half Yearly NSA Circle Ops Team 12 Checkup for proper antenna connections, cables

and connectors Half Yearly NSA Circle Ops Team

13 Visual checking for lightning arrestor Half Yearly NSA Circle Ops Team 14 Check the connector seals Half Yearly NSA Circle Ops Team

15 Measure Earth resistance values of the pits for BTS, Tower before and after monsoon Half Yearly NSA IP vendor

16 Measure Voltage between earth and neutral before and after monsoon Half Yearly NSA Circle Ops Team

17 Check for Node B power(as and when required) Half Yearly NSA Circle Ops Team

18 Check VSWR and Return Loss(as and when required) Half Yearly SA Circle Ops Team

19 Check Antenna azimuth and tilts Half Yearly NSA Circle Ops Team

20 Test the external alarms( if applicable) Half Yearly NSA GNSC FM Team and Circle Ops Team

21 Check for proper working of external power Half Yearly NSA Circle Ops Team



supplies such as critical load verification and their alarm systems.

22

Check for proper working of environmental equipments like Fans, air-conditioning etc. and their alarm systems. Half Yearly NSA Circle Ops Team

23 Check voltage and current from battery, rectifier and invertors power supply Half Yearly NSA Circle Ops Team

24 Check for any obstruction coming up in the radiation area Half Yearly NSA Circle Ops Team

25 Clear the dust inside the racks Half Yearly NSA Circle Ops Team 26 Check the aviation lamps functioning Half Yearly NSA IP Vendor 27 Check the functioning of DG sets Half Yearly NSA IP Vendor

28 Checking of equipment room Half Yearly NSA IP Vendor/Circle Ops Team

6.9 SOR for Health Checks of Ericsson Charging System

6.9.1 Health Check of Ericsson Charging System

Health Check of Ericsson Charging System Sr. No, FORM DESCRIPTION Frequency Category Responsibility 1 Check root mailbox Daily NSA Circle IN Ops Team 2 Check System Error messages Daily NSA Circle IN Ops Team 3 Check Load of Machine Daily NSA Circle IN Ops Team

4 Check Zone synchronization Daily NSA Circle IN Ops Team 5 Check FDS Log Files Daily NSA Circle IN Ops Team 6 Check Event Log Files Daily NSA Circle IN Ops Team

7 Check for CORBA-locks Daily NSA Circle IN Ops Team 8 Checking the Input CDR Files Daily NSA Circle IN Ops Team 9 Checking the Output CDR Files Daily NSA Circle IN Ops Team 10 Checking the Scheduled Job CDR Files Daily NSA Circle IN Ops Team 11 Check TT Monitor Log File Daily NSA Circle IN Ops Team 12 Checking the Sybase Error Logs Daily NSA Circle IN Ops Team 13 Disk Mirroring Status Daily NSA Circle IN Ops Team

14 Check status Daily NSA Circle IN Ops Team 15 Check alarms Daily NSA Circle IN Ops Team 16 Check hanging files Daily NSA Circle IN Ops Team 17 Check event log for errors and warnings Daily NSA Circle IN Ops Team

18 Check scheduler for failed activities and load status Daily NSA Circle IN Ops Team

19 Check table spaces Daily NSA Circle IN Ops Team 20 Check file system state Daily NSA Circle IN Ops Team 21 Check disk alarms Daily NSA Circle IN Ops Team 22 Check Processors Status Daily NSA Circle IN Ops Team 23 Check disk space Daily NSA Circle IN Ops Team 24 Check the IO Status Daily NSA Circle IN Ops Team 25 Check the Processor Load Daily NSA Circle IN Ops Team 26 Check disk space Weekly NSA Circle IN Ops Team 27 Remove Old tasks in AIR Weekly NSA Circle IN Ops Team



28 Remove old task in VS Weekly NSA Circle IN Ops Team 29 Remove old report files Weekly NSA Circle IN Ops Team 30 Remove old statistics files Weekly NSA Circle IN Ops Team 31 Check SS7 Log Weekly NSA Circle IN Ops Team 32 Check the SDP database Weekly NSA Circle IN Ops Team 33 Check time synchronization Weekly NSA Circle IN Ops Team 34 Deleting old Sybase Logs Weekly NSA Circle IN Ops Team 35 Check FDS Log Files Monthly NSA Circle IN Ops Team 36 Check Event Log Files Monthly NSA Circle IN Ops Team 37 Display system diagnostic information Monthly NSA Circle IN Ops Team 38 Check TT Monitor Log File Monthly NSA Circle IN Ops Team

6.10 SOR for Health Checks of Comverse RTBS

6.10.1 Daily Health Check of Comverse RTBS

Health Check of Comverse RTBS Sr. No, FORM DESCRIPTION Frequency Category Responsibility 1 Checking Disk Usage Daily NSA Circle IN Ops Team

2 Checking CPU & Memory Usage Daily NSA Circle IN Ops Team 3 Check Event and Alarm files Daily NSA Circle IN Ops Team 4 Checking Link Status Daily NSA Circle IN Ops Team 5 Checking Kern and Daemon files Daily NSA Circle IN Ops Team 6 Check BHCA Growth Daily NSA Circle IN Ops Team 7 Checking Log Files Daily NSA Circle IN Ops Team 8 NTP Synchronization Daily NSA Circle IN Ops Team 9 Checking the CDR transfer Logs Daily NSA Circle IN Ops Team 10 Version Check on SLU’s Daily NSA Circle IN Ops Team 11 Checking COP Alarms Daily NSA Circle IN Ops Team 12 Check disk space Daily NSA Circle IN Ops Team 13 Check CPU Usage Daily NSA Circle IN Ops Team 14 Checking Alert and Core Log Files Daily NSA Circle IN Ops Team 15 Checking Cop Loggers on SDP Daily NSA Circle IN Ops Team

16

Checking Log Files(Login to the SDP as oracle8 and go to the directory oracle/admin/sdpx/bdump)

Daily NSA Circle IN Ops Team

17 NTP Synchronization Daily NSA Circle IN Ops Team 18 Checking any faulty disk Daily NSA Circle IN Ops Team 19 Checking moshell Alarms Daily NSA Circle IN Ops Team 20 Checking Alert Log Files Daily NSA Circle IN Ops Team 21 Checking CPU Usage Daily NSA Circle IN Ops Team 22 Checking any faulty disks Daily NSA Circle IN Ops Team 23 Check the disk Usage Daily NSA Circle IN Ops Team 24 Memory Usage Daily NSA Circle IN Ops Team 25 Signaling link stability Daily NSA Circle IN Ops Team 26 Check IAP Daily NSA Circle IN Ops Team 27 Check the Disk Usage Daily NSA Circle IN Ops Team 28 Check for the Latest Commands Daily NSA Circle IN Ops Team 29 Check all the processes Daily NSA Circle IN Ops Team 30 Check Trunk and Port status Daily NSA Circle IN Ops Team

31 Check Portmon utility for alarms and Trunk status

Daily NSA Circle IN Ops Team



32 Checking Disk Usage Weekly NSA Circle IN Ops Team 33 Check disk space Weekly NSA Circle IN Ops Team 34 Check CPU Usage Weekly NSA Circle IN Ops Team 35 Checking Alert and Core Log Files Weekly NSA Circle IN Ops Team 36 Checking Cop Loggers on SDP Weekly NSA Circle IN Ops Team 37 Checking Log Files Weekly NSA Circle IN Ops Team 38 NTP Synchronization Weekly NSA Circle IN Ops Team 39 Checking any faulty disk Weekly NSA Circle IN Ops Team 40 Checking CPU Usage Weekly NSA Circle IN Ops Team 41 Checking any faulty disks Weekly NSA Circle IN Ops Team 42 Checking Kern and Daemon files Monthly NSA Circle IN Ops Team 43 Checking Log Files Monthly NSA Circle IN Ops Team

44 Checking Alert and Core Log Files Monthly NSA Circle IN Ops Team 45 Checking Cop Loggers on SDP Monthly NSA Circle IN Ops Team

46 NTP Synchronization Monthly NSA Circle IN Ops Team

47 Checking any faulty disk Monthly NSA Circle IN Ops Team 48 Checking Alert Log Files Monthly NSA Circle IN Ops Team 49 Checking any faulty disks Monthly NSA Circle IN Ops Team 50 Check the Disk Usage Monthly NSA Circle IN Ops Team

6.11 SOR for Health Checks of NSN IN@vantage

6.11.1 Health Check of NSN IN@vantage

Health Check of NSN IN@vantage S.No. FORM DESCRIPTION Frequency Category Responsibility

1 Check Message File Daily NSA Circle IN Ops Team 2 Check Hardware Defeats Daily NSA Circle IN Ops Team 3 Check RMS Resource Daily NSA Circle IN Ops Team 4 Check Network Status Daily NSA Circle IN Ops Team 5 Check Disk Space Daily NSA Circle IN Ops Team 6 Check number of active CPUs Daily NSA Circle IN Ops Team 7 Check Mirror Disks Status Daily NSA Circle IN Ops Team 8 Check Oracle Process Daily NSA Circle IN Ops Team 9 Check RTP SEP Applications Daily NSA Circle IN Ops Team 10 To Check Performance Daily NSA Circle IN Ops Team 11 To Check @commander Applications Daily NSA Circle IN Ops Team

6.12 SOR for Health Checks of CMD Nodes

6.12.1 Health Check of CMD Nodes

Health Check of CMD Nodes Sr. No, Form Description Frequency Category Responsibility

1 Monitor alarms with the Alarm CLI command line tool. Daily NSA Circle Core Ops

2 Check the Veritas Status Daily NSA Circle Core Ops 3 Check the status of the Cluster node. Daily NSA Circle Core Ops 4 Check the statuses of the service groups Daily NSA Circle Core Ops



5 Check the statuses of the resources Daily NSA Circle Core Ops 6 Check the License Details Daily NSA Circle Core Ops

7 Check the connectivity between the Flexi-Isn and CMD Daily NSA Circle Core Ops

8 Check the connectivity between CMD and IN Daily NSA Circle Core Ops

9 Verify Connectivity for IACC Diameter Mediation Workflow Daily NSA Circle Core Ops

10 Verify collection of GTP’ packets and writing raw-data files Daily NSA Circle Core Ops

11

Verify NICD3.0 output format for SGSN S-CDR and FlexISN3.2 G-CDR / SA-CDR processing for postpaid subscriber Daily NSA Circle Core Ops

12 Find out the discarded CDR Daily NSA Circle Core Ops 13 To see the load of CPU Daily NSA Circle Core Ops 14 Find out the routing of network node Daily NSA Circle Core Ops 15 To check the Disk Space Available Daily NSA Circle Core Ops 16 To see the summary of network connections Daily NSA Circle Core Ops 17 Check the EC log for any errors. Daily NSA Circle Core Ops

18 Check inbox directory for FING / FISN. Report if Raw CDR files are accumulating in the directory. Daily NSA Circle Core Ops

19 Check for sucessful Backup. Report if backup is not happening in the system. Daily NSA Circle Core Ops

20 Check DCCA logs for 4999 count from IN. Daily NSA Circle Core Ops

21 Checking System Logs and report in case of any error. Daily NSA Circle Core Ops

22 Hardware Visual check, Report in case of any amber or red light in the hardware. Daily NSA Circle Core Ops

23 Environmental Check

NSA Circle Core Ops

24 Monitor critical alarms with the Alarm CLI command line tool. Pre festival NSA Circle Core Ops

25 Check the Vreitas Status Pre festival NSA Circle Core Ops 26 Check the License Details Pre festival NSA Circle Core Ops 27 To see the load of CPU Pre festival NSA Circle Core Ops 28 To check the Disk Space Available Pre festival NSA Circle Core Ops

6.13 SOR for Health Checks of NBG Nodes

6.13.1 Health Check of NBG Nodes

Health check of NBG Nodes Sr. No. Form Description Frequency Category Responsibility 1 To find out the current host Daily NSA Circle Core Ops 2 To Check Licenses of NBG Daily NSA Circle Core Ops 3 To see the summary of Network Daily NSA Circle Core Ops 4 Find out the routing of network node Daily NSA Circle Core Ops 5 To see the load of CPU Daily NSA Circle Core Ops 6 To check the Nodes connectivity Daily NSA Circle Core Ops

7 Check all the h/w and LAN interfaces on which NBG connected Daily NSA Circle Core Ops

8 To see the total amount of free & Used Physical Memory Daily NSA Circle Core Ops

9 To check the Disk Space Available Daily NSA Circle Core Ops

10 Find out the virtual memory & statistics of network node. Daily NSA Circle Core Ops



11 To check detail status of application server Daily NSA Circle Core Ops 12 To check status of individual Application Blade Daily NSA Circle Core Ops 13 To Check all Oracle instances are up Daily NSA Circle Core Ops 14 Check Oracle Process Daily NSA Circle Core Ops 15 To check the status of IBM Management Daily NSA Circle Core Ops

16 To access the TR/CDR logs of NBG for a particular time stamp Daily NSA Circle Core Ops

17 To display the events in the NBG Daily NSA Circle Core Ops

18

Display all Browsing Gateway severe logs between 31 March 2005, midnight and 1 April 2005, 23.59.59 on screen Daily NSA Circle Core Ops

19 To print the statistics of NBG like TPS used etc Daily NSA Circle Core Ops 20 To display all configuration files Daily NSA Circle Core Ops 21 To check the connectivity of Internet sites Daily NSA Circle Core Ops 22 To check the connectivity of Internet sites Pre festival NSA Circle Core Ops

23 Check all the h/w and LAN interfaces on which NBG connected Pre festival NSA Circle Core Ops

24 Check Oracle Process Pre festival NSA Circle Core Ops 25 Check the License Details Pre festival NSA Circle Core Ops 26 To see the load of CPU Pre festival NSA Circle Core Ops 27 To check the Availability of Disk Space Pre festival NSA Circle Core Ops

6.14 SOR for Health Checks of SMSC Nodes

6.14.1 Health Check of SMSC Nodes.

Health Check of SMSC Nodes

S.No. Form Description Frequency Category Responsibility

Expected execution

time 1 To Check SMS Center system logs Daily NSA Circle Core Ops NA 2 To check the SMS Centre Event Logs Daily NSA Circle Core Ops NA

3 To check the SMS Centre message queue size Daily NSA Circle Core Ops NA

4 To check the cache size and application states for AT traffic Daily NSA Circle Core Ops NA

5

To check SMS Centre load and traffic if Nokia Network Data Warehouse (NDW) tool is used Daily NSA Circle Core Ops NA

6 Checking the SMS Center release version Daily NSA Circle Core Ops NA

7 Checking the SMS Center change delivery information Daily NSA Circle Core Ops NA

8 Signaling Link Load Verification Pre festival NSA Circle Core Ops Immediate 9 Processor Load Pre festival NSA Circle Core Ops Immediate 10 Disk Utilization & I-Node Utilization Pre festival NSA Circle Core Ops Immediate 11 CPU Idle Percentage Pre festival NSA Circle Core Ops Immediate



6.15 SOR for Health Checks of MMSC Nodes

6.15.1 Health Check of MMSC Nodes

Health Check of MMSC Nodes Sr. No. Form Description Frequency Category Responsibility

1 Overview of the system CPU Load and memory usage Daily NSA Circle Core Ops

2 Overview of the system CPU Load and memory usage over a period of time Daily NSA Circle Core Ops

3 File systems/ Disk Usage Daily NSA Circle Core Ops 4 Busiest Processes Daily NSA Circle Core Ops 5 Zombies Daily NSA Circle Core Ops 6 Check for routing configuration Daily NSA Circle Core Ops 7 Interfaces Check Daily NSA Circle Core Ops 8 Monitor Application Processes for MMSC Daily NSA Circle Core Ops 9 Monitor Application Processes for NEMS Daily NSA Circle Core Ops 10 Monitor Application Processes for NPS Daily NSA Circle Core Ops 11 Monitor Current Traffic Daily NSA Circle Core Ops 12 Monitor Previous 24Hrs Traffic Daily NSA Circle Core Ops

13

Monitor MMSC Alarms to verify that no Runtime Errors or Critical alarms are being generated Daily NSA Circle Core Ops

14 Overview of the system CPU Load and memory usage Pre festival NSA Circle Core Ops

15 File systems/Disk Usage Monitor Pre festival NSA Circle Core Ops 16 Application Processes for MMSC Pre festival NSA Circle Core Ops 17 Monitor Previous 24Hrs Traffic Pre festival NSA Circle Core Ops 18 Monitor Current Traffic Pre festival NSA Circle Core Ops

6.16 SOR for Health Checks of Transmission Equipment

6.16.1 Health Check of Transmission

Health Check of TX Sr. No. FORM DESCRIPTION Frequency Category Responsibility 1 Tellabs 8660 Daily NSA GNSC-FM TX TEAM 2 Tellabs INM 8000 Daily NSA GNSC-FM TX TEAM

3 Utilization of Transmission Network Pre festival NSA GNSC-FM TX TEAM/ Circle

Ops Team(as applicable)

4 Equipment capacity Pre festival NSA GNSC-FM TX TEAM/ Circle


5 ECI NMS hard disk utilization Pre festival NSA GNSC-FM TX TEAM/Circle Ops Team(as applicable)

6 ECI EMS hard disk utilization Pre festival NSA GNSC-FM TX TEAM/ Circle


7 Ensuring the status of standby cards Pre festival NSA GNSC-FM TX TEAM

8 Network Synchronization and Clock Source Pre festival NSA GNSC-FM TX TEAM

9 Rx Level Report Daily NSA GNSC-FM TX TEAM 10 NE Visibility Check-Q1 Integration Daily NSA GNSC-FM TX TEAM



Status

11 Protection Check for IDU/ODU (MW 1+1) Half Yearly SA

Circle Team and support from GNSC-FM TX TEAM

12 SDH ring protection check Half Yearly SA Circle Team and support from

GNSC-FM TX TEAM

13 Prm of Tellabs 8660 (Protection check of MSP/ELP/CDC) Half Yearly SA

Circle Team and support from GNSC-FM TX TEAM

** Where the operation/equipment visibility is not with GNSC for transmission in that case the responsibility is with Circle Ops team.

6.17 Preventive maintenance of OMC Computer units:

Preventive Maintenance of OMC Computer units Sr. No. FORM DESCRIPTION Frequency Category Responsibility 1 Delete Temp Internet Files Daily NSA Circle Ops Team 2 Delete Temp Windows Files Daily NSA Circle Ops Team 3 Run Virus Scan Weekly NSA Circle Ops Team

4 Windows Update When updates are

available SA Circle Ops Team

5 Antivirus Update When updates are

available NSA Circle Ops Team 6 Check for Updates to Java Weekly NSA Circle Ops Team 7 Run Disk Cleanup Monthly NSA Circle Ops Team

8 Run Scan Disk/Check Disk Monthly May be service

affecting Circle Ops Team

9 Run Disk Defragmenter Monthly May be service

affecting Circle Ops Team 10 Check for Updates to Adobe Reader Monthly NSA Circle Ops Team 11

Clean Computer, Mouse, Keyboard & Monitor Yearly NSA Circle Ops Team

6.18 SOR for Health Check for SGSN

6.18.1 Health Check of SGSN

Sr. No. FORM DESCRIPTION Frequency

Non Service Affecting-NSA / Service Affecting-SA Responsibility

1 ELEMENT DETAILS Daily NSA GNSC- FM Team 2 Active Alarms Daily NSA GNSC- FM Team 3 Alarms History Daily NSA GNSC- FM Team 4 ALL UNITS STATES Daily NSA GNSC- FM Team 5 Interface Status Daily NSA GNSC- FM Team 6 APN Daily NSA GNSC- FM Team 7 Command Logs Daily NSA GNSC- FM Team 8 Static routes Daily NSA GNSC- FM Team



9 Network Interface Daily NSA GNSC- FM Team 10 BVCI Status Daily NSA GNSC- FM Team 11 SYNCHRONIZATION Daily NSA GNSC- FM Team 12 SUBSYSTEM STATES Daily NSA GNSC- FM Team 13 GT ANALYSIS Daily NSA GNSC- FM Team 14 MEASUREMENT FILES Daily NSA GNSC- FM Team 15 MEASUREMENT FILES RATIO Daily NSA GNSC- FM Team 16 SUBSCRIBERS IN SMMU Daily NSA GNSC- FM Team 17 SUBSCRIBERS IN PAPU Daily NSA GNSC- FM Team 18 SUBSCRIBER PLMNWISE Daily NSA GNSC- FM Team 19 ASSOCIATION SET DATA Daily NSA GNSC- FM Team 20 CHARGING Daily NSA GNSC- FM Team 21 CDR STATUS Daily NSA GNSC- FM Team 22 LICENCE STATUS Daily NSA GNSC- FM Team 23 SIGNALLING LINK STATUS Daily NSA GNSC- FM Team 24 SW PACKAGES Daily NSA GNSC- FM Team

6.19 SOR for Health Check for FING(GGSN)

6.19.1 Health Check of FING(GGSN)

Sr. No. FORM DESCRIPTION Frequency Non Service Affecting-NSA /

Service Affecting-SA Responsibility 1 Time Status Daily NSA GNSC- FM Team 2 Disk Space Daily NSA GNSC- FM Team 3 Memory Utilization Daily NSA GNSC- FM Team 4 ALL UNITS STATES Daily NSA GNSC- FM Team 5 NTP Status Daily NSA GNSC- FM Team 6 Alarm Count Daily NSA GNSC- FM Team 7 Functionality Check Daily NSA GNSC- FM Team 8 Static routes Daily NSA GNSC- FM Team 9 Object Status Daily NSA GNSC- FM Team 10 Node Status Daily NSA GNSC- FM Team

6.20 SOR for Health Check for DNS

6.20.1 Health Check of DNS

Health Check for DNS Sr.No. Form Description Frequency Category Responsibility

1 Check CPU Utilization Daily NSA GNSC 2 Check Memory Utilization Daily NSA GNSC 3 Check Disk Utilization Daily NSA GNSC 4 Check Process Utilization Daily NSA GNSC 5 Check for routing configuration Daily NSA GNSC

6 Check for Active / Historical

Alarms Daily NSA GNSC

7 Check ping test for SGSN PAPU

IP's from CG Ga Interface Daily NSA GNSC

8 Check for DNS Application

status.Local APN Daily NSA GNSC 9 DNS Query for Natl Opr. Daily NSA GNSC

10 DNS Query for InterNatl Opr Daily NSA GNSC



6.21 SOR for Health Check for NTP

6.21.1 Health Check of NTP

Health Check for NTP Sr.No. Form Description Frequency Category Responsibility

1 To check Uptime Daily NSA GNSC 2 To Check the memory Status Daily NSA GNSC

3 To Check the Network --> LAN1

Status Daily NSA GNSC 4 To check GPS Antenna Status Daily NSA GNSC

5 To check Check System peer

mode Daily NSA GNSC 6 To check NTP Stratum Daily NSA GNSC 7 To check Alarms Status Daily NSA GNSC

8

ping (client Ips eg:SGSN,GGSN,6509 -1,6509-2,

FW ) Daily NSA GNSC 9 DNS Query for Natl Opr. Daily NSA GNSC

6.22 SOR for Health Check for Radius

6.22.1 Health Check of Radius

Health Check for Radius Sr.No. Form Description Frequency Category Responsibility

1 Check Disk Space Daily NSA GNSC 2 Check Process Daily NSA GNSC 3 Check latest accounting file Daily NSA GNSC 4 Check svrlogs. Daily NSA GNSC 5 Accounting Threads Daily NSA GNSC 6 Accounting Threads Daily NSA GNSC 7 Accounting Threads Daily NSA GNSC

6.23 Preventive Maintenance for BTS/Node B & TX-MW Preventive Maintenance for all Node-B/BTS & MW equipments is done at following schedules • Quarterly Routine Preventive Maintenance: (• Half-yearly Preventive Maintenance: (

As attached in attachment folder) As attached in attachment folder

)

• Pre monsoon Checklist : • Post monsoon Checklist

(As attached in attachment folder )

• Half-Yearly Infra Preventive Maintenance: Where Infra is in scope of NSN like few sites in Bharti and Idea Bihar Circle.

(As attached in attachment folder)

(As attached in attachment folder). In addition for TTSL the Infra provider details have to be collected and validated in the enclose template. (As attached in attachment folder

.



The Quarterly routine preventive maintenance activities are non-service affecting whereas the half-yearly Preventive Maintenance activities can be service affecting and therefore need proper approval as mentioned in section 3.5. All the points in the Quarterly Routine Preventive Maintenance are included in the Half-Yearly Preventive Maintenance. So in half a year, both quarterly routine checklist and half-Yearly checklist should be filled up once. All PrM activity schedule must be prepared either by Cluster Head which must be circulated to all concerned SDE/ FLMs and hence must be shared with GNSC FM Team. The SDE/ FLM must keep his schedule up- to-date & keep all stake holders updated with the progress.

7 Process KPI’s This report will contain all the list of Tasks being done including all rescheduled ones. All the PrM forms, the checklists and the Calendars must also be preserved for future reference. All the SDE/ FLMs/ Core engineers will submit their forms to the Cluster Heads and Cluster Heads will provide the information to the customer in turn. At the end of every month a report has to be generated which is to be produced in front of the customer by the Cluster Head.

S.No. KPI Formula

1 % of PRM TASK Created as per

Schedule

Total No. of PrM Task Created * 100 Total No. of PrM Task Scheduled

2 % of PRM TASK Executed within SLA

Total PrM Task Created-PRM TASK not executed within SLA * 100 Total No. of PrM Task Scheduled

3 % of PRM TASK pending as per

schedule

No. of PrM Task Pending * 100 Total No. of PrM Task Created

4 % of PRM TASK closed within SLA

Total No. of closed within SLA * 100 Total No. of PrM Task Created

7.1 Process KPI Reports Reports can be generated in excel for all PrM Task pending and completed Node wise with period or date range mentioned. The report should include, node, date of PrM completion, Executor of the PrM, list of punch points, action on each punch point. There will be separate report for BTS and Core nodes. There should be a provision to download a report for upcoming PrM schedules too for proper planning of resources.



Monthly PrM Process KPI Report (Sample)

Sr. No. Node Type Tot

al Scheduled / Planned

PrM Form

Created

PrM Executed within

SLA

PrM Closed within SLA

PrM Cancelled/

Not Executed

PrM Pending

1 MSC 4 2 2 2 2 0 0 2 GMSC 2 1 1 1 1 0 0 3 MGW 2 1 1 1 1 0 0 4 IN System 2 1 1 1 1 0 0 5 CMD Node 1 1 1 1 1 0 0 6 NGB Node 1 1 1 1 1 0 0 7 SMSC 1 1 1 1 1 0 0 8 MMSC 1 1 1 1 1 0 0 9 BSC 20 10 10 10 10 0 0

10 RNC 10 4 4 4 4 0 0 11 Node-B 200 70 70 60 60 10 10

12 BTS 1000 700 700 670 670 30 30

Monthly PrM Process KPI Report

Sr. No. Node Type

PrM TASK Created as per

Schedule

PrM TASK executed within

SLA

PrM TASK pending as per

Schedule

PrM TASK closed within

SLA

1 MSC 100% 100% 0% 100% 2 GMSC 100% 100% 0% 100% 3 MGW 100% 100% 0% 100% 4 IN System 100% 100% 0% 100% 5 CMD Node 100% 100% 0% 100% 6 NGB Node 100% 100% 0% 100% 7 SMSC 100% 100% 0% 100% 8 MMSC 100% 100% 0% 100% 9 BSC 100% 100% 0% 100%

10 RNC 100% 100% 0% 100% 11 Node-B 100% 86% 14% 86% 12 BTS 100% 96% 4% 96%

8 Nomenclature

8.1 Circle IDs

Circle ID (1 Character)

Circle Circle ID Andhra Pradesh A Bihar & Jharkhand B Chennai C



Delhi D Kerala E Assam F Gujarat G Haryana H Madhya Pradesh I Jammu & Kashmir J Karnataka K UP-E L Mumbai M North East N Orissa O Punjab P R o Maharashtra Q Rajasthan R Himachal Pradesh S R o Tamil Nadu T UP-W U R o West Bengal W Kolkata Y

8.2 Customer IDs

Customer Customer ID Bharti B Vodafone V Maxis M TTSL T IDEA I Videocon D Uninor U

8.3 Node ID

Network Node ID (1Character) Network Node Node ID

HLR HLRXXX MSC/ MSS MSSXXX GMSC/ GCS GCSXXX MGW/ GMGW MGWXXX SGSN GSSNXX GGSN GGSNXX Routers RTRSXX Firewalls FIRWXX STP STPXXX OSS OSSXXX BSC BSXXXX BTS XXXXXX CDS CDSXXX RNC RNCXXX



Node B NBXXXX SMSC SMSCXX MMSC MMSCXX Comverse IN COMIXX Ericsson IN ERINXX NSN IN@Vantage INVXXX Telcordia IN TCRDXX

XXXX Numeric Digits

8.4 Date ID Date: DDMYY

Where DD Date (01 to 31) MM Month – JAN to DEC as 01 to 12 YY Year (Last 2 digits of Year)

9 Glossary A-BIS A-BIS Protocol AIS Alarm Indication Signal ATM Asynchronous Transfer Mode AUC Authentication Centre BERT Bit Error Rate Test BSC Base Station Controller BSDATA BSS Database BTS Base Transceiver Station CLAB Clock and Alarm Buffer CR Change Request DAT Digital Audio Tape DCC Data Communication Channel DCN Data Communication Network EB Electricity Board EIR Equipment Identity Register EMS Element Management System EQUIPM Equipment Database ET Exchange Termination (E1 Card) FDU Fibre Distribution Unit GNSC Global Network Solution Centre (GNOC) NCM Network Change Management SDE/ FLM Service Delivery Engineer Service Delivery Unit TTA Trouble Ticket Administration TRM(FM) Trouble Résolution Management Process

Documents

Preventive Maintenance Process_Ver4.2