1

2

PTCL National NOC

(Network Operations Center)

3

What is NOC?

•It is Network Operations Center

• It is an apex in TMN hierarchy to view, monitor and control networks.

•It is a tool for managing a network of networks.

Why NOC?

4

What is NOC ?

•NOC rely on a set of Operations Support Systems (OSS) and operations procedures to manage the networks.

•The OSS collects fault and performance data from the Element Management Systems and Network Elements and present them in standardized manner to enable the NOC staff to monitor and manage the networks.

Why NOC?

5

What is NOC ?• NOC is a cross-domain organization managing network across several

business and operations units at PTCL. It manages networks provided by multiple vendors, multiple network technologies in multiple geographic locations. Using a set of standardized processes and tools, regardless of where in the PTCL infrastructure the problem lies, the NOC aims to

• provide up-to-date status of services.• identify and minimize impacts to customers due to service outages.• manage resolution of outages in a timely manner • be a focal point for coordination during major networks related

events

Why NOC?

6

Centralized

Network visibility

Integrated EMSs

Integrated Network Fault Management

Trouble Ticketing

Centralized NOC?

7

Current Operational Challenges

Decentralized Network Management

Reduced visibility of outstanding/critical problems

More time taken to own and record the faults

Manual activity logs

No knowledge base being maintained to track faults

Why NOC?

8

No Trouble Ticketing system

No Automated Escalation process

No Access controls defined for operators

No Centralized Work Orders Platform

Service provisioning to customers is distributed and has inherent delays.

Why NOC?

9

TMN Hierarchy Business Management Layer

Service Management Layer

Network Management Layer

Element Management Layer

Network Element Layer

BML

NML

EML

NEL

SML

Why NOC?

10

NOC provides FCAPS functions for networks– Fault management– Configuration management– Account management– Performance management– Security management

Why NOC?

11

NOC will proactively identify and get resolved the faults in Network through Real time Network Monitoring Network status visibility

Increase network availability Enhanced QOS visibility Centralized Reporting Uniform performance statistics

Optimization of operational and maintenance cost Centralized level of O&M/OSS management Standardized Operational Processes

How NOC will help PTCL in achieving its targets?

12

• Alarm monitoring & management

• Performance management

• Trouble Ticketing (Incident management)

PTCL NOC scope- at Present

13

Network Element (NE)? Element Manager System (EMS)? Network Management Systems (NMS)? A cluster of NMSs Examples in Transmission and Switching Domains

Networks – Some basic concepts

14

Alarms and their classifications

What are Alarms?

• The EMS generates notifications regarding events on N.E.s called alarms.

• The events in a networks can be;Network FaultsPerformance events

• The alarms contains information (alarm attributes) regarding:

Begin time, End time, Rack, Shelf, Slot, Port etc

15

Alarms and their classifications

Classifications of Alarms?• Severity

Critical AlarmsMajor AlarmsMinor AlarmsWarnings

• Type:

Equipment AlarmsCommunications AlarmsEnvironment AlarmsQoS AlarmsSecurity Alarms

16

• Alarm Attributes (Managed object, Raising time, clearing time etc)• Alarms & Clear Alarms• Severity Propagation of Alarms• Similar Alarms(Managed Object, Alarm type, Specific problem, Probable cause)

Alarms – Some Concepts

17

Examples of Alarms

18

Examples of Alarms

19

Examples of Alarms

20

The North Bound Interface (NBI)– This is an interface on EMS with standardized set of protocols for information

interchange with NMS.

The commonly used NBI Protocols– CORBA– ASCII– SNMP– Q3

Alarm collection Processes

21

NOC OSS Capacity

22

The PTCL network is multi functional, multi vendor network, and can be classified as fallows :– Transmission network

Core network (Backbone)Access network (Junction and OFAN)

– Switching networkCore network (Transits )Access network (RLUs)

PTCL network - Classification

23

– WLL networkCore network (MSCs)Access network (BTSs)

– Signaling network– Synchronization network– NGN network– IN network– IP network (PIE)– Multimedia and Broad Band network– DXX network

PTCL network - Classification

24

Network Domains

PIE Network

NGN Network

WLL Network

Transmission Network

TDM Switching Network

Triple play Network

Metro OFAN Network

Signaling Network

DXX Network

IN Network

NOC Center

25

Vendors in PTCL Network

• Transmission• Switching• Access• NGN• WLL• Signaling

• DXX

• DXX

• WLL• PIE (CA Spectrum)

• Switching

• PIE

• Transmission• Switching• Access• NGN• WLL• IN• Triple Play• Synchronization

26

Contract details

The contract for the NOC project (PUR.6-12/2007/1494) was signed on the 14th of December 2007

The contract was signed on Turnkey basis with M/S Huawei

Huawei has subcontracted with HP for the Provisioning of NOC/OSS solution (software/application)

27

Vendor Domain EMS Name NBI EMS number

Transmission Network iManager T2000 CORBA 23

TDM Switching Network iManager N2000 CORBA 1

Access Network iManager N2000 CORBA 7

WLL Network iManager M2000 CORBA 2

Fixed IN Network iManagaer N2100 CORBA 1

MM&BB OVO ASCII 1

Synchronization iManager N2000 CORBA 1

NGN Network iManager N2000 CORBA 1

Transmission Network E300 CORBA 21

Access Network E100 ASCII 10

NGN Network NetNumen N31 CORBA 2

WLL Network NetNumenM31 Corba 1

Tekelac Signaling Network Netboss SNMP 1

Emircom/Cisco PIE Network CA Spectrum ASCII 1

Siemens TDM Switching Network NetManager Corba 4

Tellabs DXX Network Tellabs 8100 ASCII 1

Symbia DXX Network Loop iNMS Corba 1

ZTE

Huawei

NOC – Integration Details

28

Network Domains – EMS Percentage

NGN, 2%

Signaling, 1%

PIE, 1%IN, 1%Synchronization,

1%

Triple Play, 1%

Access, 19%

WLL, 5%

Switching, 25%

DXX, 4%

Transmission, 40%