7/30/2019 Functional Requirement of Transmission

1/3

Annex 4A-8d

PAGE 1 OF 3

DETAILED FUNCTIONAL REQUIREMENTS

OF TRANSMISISON OMC

This appendix clarifies the functional perimeters of the OMC and ofthe NMS (umbrella Network Management System forTransmission).

Application Functionalities Required

in BIDDER OMC

Functionalities of OPERATOR

NMS

Interfaces Required

From OMC to NMS

NetworkTopology

End-to-end graphicalview by Bidder ofnetwork hierarchy until

module configuration Detailed status of the

NE (every fault alarmseven non-serviceaffecting, noPerformance Alarmsdisplayed)

Enable user tonavigate through thenetwork (until NEconfiguration) anddisplay selecteddetails using a

Graphical UserInterface (GUI)

Retrieve NE configurationfrom OMC

Create topological maps of the

network in form of hierarchicalgraphs

Display current status of theNE depicted on the map (FaultAlarms affecting service,Performance Alarms)

Enable user to navigatethrough the network anddisplay selected details usinga Graphical User Interface(GUI)

Networkhierarchyincluding network

topological,network logicalhierarchy

FaultManagement

Raw alarms viewingand alerting (withoutfiltering)

Trouble shooting inregional managers ifpossible directly in thesystem

NE resynchronization

Testing of NE aftertrouble shooting

Alarm data storage

Remark: the escalationprocess to fieldmaintenance andBidder is carried outmanually

Alarm reception from OMCs

Alarms viewing, isolation andgrouping (using networktopology)

Route cause analysis(correlation)

Alarms prioritization based onservice affecting

Provide help menus withtrouble shooting procedures

Trouble tickets (TT) creationbased upon alarms andcustomer trouble reports

Trouble ticketing notification toRegional Manager

Statistical problem resolutionperformance reporting

Reset functionality

Push alarms to Map Info aftercorrelation

Optional: resynchronization

with OMC

Text/ASCIIalarms dataformat including:

alarm type

alarm name

alarm severity

NE ID

alarm start time

Rerouting data

(NE configuration,to wayscommunication)

7/30/2019 Functional Requirement of Transmission

2/3

Annex 4A-8d

PAGE 2 OF 3

Application Functionalities

Required in BIDDER

OMC

Functionalities of OPERATOR NMS Interfaces Required

From OMC to NMS

PerformanceManagement

Calculation of NEperformance data:

Availability

Utilization

Error Bit Rate

Signal loss

Throughput power

Presentation ofperformance data:

NE performance

End-to-endNetworkperformance fornetworks which areBidder specific.

Automatic collection and processingof operational data from OMC

End-to-end performance calculation(same indicators as OMCs)

Per-section performance calculation(same indicators as OMCs)

E1 performance calculation (sameindicators as OMCs) :

leased lines

per Bidder

Performance threshold definition

Network surveillance:

periodic network performancecalculation

Bidders KPI follow-up for future SLAs

Establish performance based alarms:

Generating alarms (based uponthresholds) which are sent to AlarmManagement

Push performance reports to Map-Info for NE planning

Replication of allperformance datagenerated in theOMC to the NMS:

NE performance

Networkperformance (ifavailable)

Data required:

Intervals

Error Bits

Signal strength

Throughputpower

....

InventoryManagement

Database ofdetailedconfiguration ofnetwork andNE(logical networkand physicalconfiguration)

Retrieve periodically actualconfiguration data from OMC andoverwrite Inventory Data

Synchronization check of data withOMC

End-to-end configuration of networksections until E1:

Periodic retrievalof NEconfiguration fromOMCs:

NE ID

logical networkconfiguration

resources used(timeslots

allocation) ports

configuration

tributary cardsconfiguration

frequency used

equipment type

capacity

Bidder

7/30/2019 Functional Requirement of Transmission

3/3

Annex 4A-8d

PAGE 3 OF 3

Application Functionalities Required in

BIDDER OMC

Functionalities of

OPERATOR NMS

Interfaces Required

From OMC to NMS

ConfigurationManagement

Modify network and NEconfiguration :

Automatic networkconfiguration based on NEconfiguration

Initialize equipment

Set-up and execute actions

Configuration templates foreasy set-up of NE

Radio Protection switching

Hot Standby switching

Download of configurationfile to NE

Clock synchronization

Frequency definition

Carry out trouble shootingof NE when requiring onlysoftware modification

Test network performanceafter NE reconfiguration dueto trouble shooting, ornetwork optimization

No At this point, nointerface requiredas theconfiguration ofNE is carried outin the OMCs itself