3. Why NOC?
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.
3
4. Why NOC?
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.
4
5. Why NOC?
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
•
•
•
•
5
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
7. Why NOC?
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
7
8. Why NOC?
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.
8
9. Why NOC?
TMN Hierarchy
Business Management Layer
BML
SML
Service Management Layer
NML
Network Management Layer
EML
Element Management Layer
NEL
Network Element Layer
9
11. How NOC will help PTCL in
achieving its targets?
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
11
13. Networks – Some basic concepts
Network Element (NE)?
Element Manager System (EMS)?
Network Management Systems (NMS)?
A cluster of NMSs
Examples in Transmission and Switching Domains
13
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 Faults
Performance events
• The alarms contains information (alarm attributes) regarding:
Begin time, End time, Rack, Shelf, Slot, Port etc
14
15. Alarms and their classifications
Classifications of Alarms?
• Severity
Critical Alarms
Major Alarms
Minor Alarms
Warnings
• Type:
Equipment Alarms
Communications Alarms
Environment Alarms
QoS Alarms
Security Alarms
15
16. Alarms – Some Concepts
• 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)
16
20. Alarm collection Processes
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
20
22. PTCL network - Classification
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 network
Core
network (Transits )
Access network (RLUs)
22
23. PTCL network - Classification
– WLL network
Core
network (MSCs)
Access network (BTSs)
– Signaling network
– Synchronization network
– NGN network
– IN network
– IP network (PIE)
– Multimedia and Broad Band network
– DXX network
23
25. Vendors in PTCL Network
•
DXX
•
•
•
•
•
•
• Switching
Transmission
Switching
Access
NGN
WLL
Signaling
• PIE (CA Spectrum)
25
• DXX
•
•
•
•
•
•
•
•
• PIE
• WLL
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)
26
