Annex 4A-8d

PAGE 1 OF 3

DETAILED FUNCTIONAL REQUIREMENTS OF TRANSMISISON OMC This appendix clarifies the functional perimeters of the OMC and of the NMS (umbrella Network Management System for Transmission).
Application Functionalities Required in BIDDER OMC Functionalities of OPERATOR NMS Interfaces Required From OMC to NMS

End-to-end graphical
view by Bidder of network hierarchy until module configuration Detailed status of the NE (every fault alarms even non-service affecting, no Performance Alarms displayed) Enable user to navigate through the network (until NE configuration) and display selected details using a Graphical User Interface (GUI)

Retrieve NE configuration
from OMC Create topological maps of the network in form of hierarchical graphs Display current status of the NE depicted on the map (Fault Alarms affecting service, Performance Alarms) Enable user to navigate through the network and display selected details using a Graphical User Interface (GUI)

Network
hierarchy including network topological, network logical hierarchy

Network Topology

Raw alarms viewing

Fault Management

and alerting (without filtering) Trouble shooting in regional managers if possible directly in the system NE resynchronization Testing of NE after trouble shooting Alarm data storage Remark: the escalation process to field maintenance and Bidder is carried out manually

Alarm reception from OMCs Alarms viewing, isolation and

grouping (using network topology) Route cause analysis (correlation) Alarms prioritization based on service affecting Provide help menus with trouble shooting procedures Trouble tickets (TT) creation based upon alarms and customer trouble reports Trouble ticketing notification to Regional Manager Statistical problem resolution performance reporting Reset functionality Push alarms to Map Info after correlation Optional: resynchronization with OMC

Text/ASCII
alarms data format including: alarm type alarm name alarm severity NE ID alarm start time Rerouting data (NE configuration, to ways communication)

Annex 4A-8d
PAGE 2 OF 3

Application

Functionalities Required in BIDDER OMC

Functionalities of OPERATOR NMS

Interfaces Required From OMC to NMS

Calculation of NE
performance data: Availability Utilization Error Bit Rate Signal loss Throughput power Presentation of performance data: NE performance End-to-end Network performance for networks which are Bidder specific.

Automatic collection and processing

of operational data from OMC End-to-end performance calculation (same indicators as OMCs) Per-section performance calculation (same indicators as OMCs) E1 performance calculation (same indicators as OMCs) : leased lines per Bidder Performance threshold definition Network surveillance: periodic network performance calculation Bidders KPI follow-up for future SLAs Establish performance based alarms: Generating alarms (based upon thresholds) which are sent to Alarm Management Push performance reports to MapInfo for NE planning

Replication of all
performance data generated in the OMC to the NMS: NE performance Network performance (if available) Data required: Intervals Error Bits Signal strength Throughput power ....

Performance Management

Database of Inventory Management

detailed configuration of network and NE(logical network and physical configuration)

Retrieve periodically actual

configuration data from OMC and overwrite Inventory Data Synchronization check of data with OMC End-to-end configuration of network sections until E1:

Periodic retrieval
of NE configuration from OMCs: NE ID logical network configuration resources used (timeslots allocation) ports configuration tributary cards configuration frequency used equipment type capacity Bidder

Annex 4A-8d
PAGE 3 OF 3

Application

Functionalities Required in BIDDER OMC

Functionalities of OPERATOR NMS No

Interfaces Required From OMC to NMS

Modify network and NE Configuration Management

configuration : Automatic network configuration based on NE configuration Initialize equipment Set-up and execute actions Configuration templates for easy set-up of NE Radio Protection switching Hot Standby switching Download of configuration file to NE Clock synchronization Frequency definition Carry out trouble shooting of NE when requiring only software modification Test network performance after NE reconfiguration due to trouble shooting, or network optimization

At this point, no
interface required as the configuration of NE is carried out in the OMCs itself