Telekom Malaysia EMS DC Power System

Doc No:
UTP-1/ST/TF03/BATTERYAND-RECTIFIER
Revision No: 2
Doc Title:
Acceptance Test Protocol for EMS
DC POWER SYSTEM
ACCEPTANCE TEST PROTOCOL
FOR EMS
Prepared By :
Prepared By:
Mohd Falaah Abd Manap

System Technology
ND Wholesale
Telekom Malaysia
Reviewed By:
Reviewed By:
Norizan Melan
System Technology
ND Wholesale
Telekom Malaysia
Approved By:
Approved By:
Zulkarnain Husain
System Technology
ND Wholesale
Telekom Malaysia

(February 2009)
Page : 1
Doc No:
Revision No: 2
Doc Title:
TABLE OF CONTENTS
OBJECTIVE.............................................................................................................3
SCOPE..................................................................................................................... 3
PHYSICAL VERIFICATION.....................................................................................3
SOFTWARE VERSION VERIFICATION..................................................................4
TEST REQUIREMENT.............................................................................................5
TEST ITEM............................................................................................................ 12
SUMMARY OF EMS DC POWER SYSTEM TEST..............................................101
TEST MEMBERS.................................................................................................104
AGREED BY TEST MEMBER.............................................................................105

(February 2009)
Page : 2
Doc No:
Revision No: 2
Doc Title:
OBJECTIVE
This document describes the detailed procedures for the acceptance test of the
MSAN EMS.
1 SCOPE
1.1
1.2
The scope of this test procedures shall include the following items:
i.
Acceptance Memorandum
ii.
Physical verification of all equipment
iii.
Software verification of all equipment
iv.
System tests, as outlined in the test requirement provided by Telekom

Malaysia.
This ATP shall be applied to the following:

i.
EMS software
ii.
Database software
2 PHYSICAL VERIFICATION
2.1
Server / Client:
Item
Description
Condition
(OK/Faulty)
Operating System
CPU
Installed RAM
Internal HDD
DAT (DDS)
CD-ROM Drive
Graphic Display
Ethernet Card

(February 2009)
Page : 3
Doc No:
Revision No: 2
Doc Title:
3 SOFTWARE VERSION VERIFICATION
No
Hardware
Name
Software Name
Release /
Version no
License
1
2
3
4
5
6
7
8
9

(February 2009)
Page : 4
Doc No:
Revision No: 2
Doc Title:
TEST REQUIREMENT
NO
1
Test
Description
Database back-up and

restoration
1.1
Data purging
To verify that the system is able to auto-purge out of

date information e.g alarm, audit trails logs.
1.2
NE configuration backup/restore
To verify the system is able to backup the NE

configuration manually and schedule
Fault Management
2.1
Housekeeping Alarms
2.1.1
Monitor rack temperature
To simulate the alarm and verify that the EMS is able

to monitor the rack temperature and generate alarm
should the temperature threshold is increased.
2.1.2
Monitor fan status
To verify that the EMS is able to monitor the fan status
2.1.3
Monitor humidity
To verify that the EMS is able to monitor the humidity

level in the DSLAM
2.1.4
Monitor rectifier
To verify that the EMS is able to monitor the rectifier

status
2.1.5
Monitor battery on load
To verify that the EMS is able to monitor the battery

status

(February 2009)
Page : 5
Doc No:
Revision No: 2
Doc Title:
2.2
Alarm display at EMS
2.2.1
Active alarm display at EMS
To simulate an alarm and verify that the alarm received at

the EMS have the following items:
a) Severity of alarms
b) Received date and time for each alarm
c) Alarm description
d) Alarm type
e) Alarm location (specific location of alarm that has
occurred)
f)
2.2.2
Historical
EMS
alarm
display
at
NE location the area name in which the NE is

located
To simulate an alarm and verify that the alarm received at

the EMS have the following items:
a) Severity of alarms
b) Received date and time for each alarm
c) Restored date and time for each alarm
d) Alarm description
e) Alarm type
f)
Alarm location (specific location of alarm that has

occurred)
g) NE location the area name in which the NE is

located
2.2.3
Severity of alarms
To verify that the EMS is able to distinguishly display the

severity of alarms, such as critical, major, minor
2.2.4
Alarm alert
To verify that the EMS will have a visual and audible alert
upon receiving alarms
2.3
Alarm/ event data handling
2.3.1
Acknowledgement of alarms

(February 2009)
To verify that the

acknowledge alarms.
EMS
allows
the
operator
Page : 6
to
Doc No:
Revision No: 2
Doc Title:

(February 2009)
Page : 7
Doc No:
Revision No: 2
Doc Title:
2.3.2
Inserting
input
acknowledgement
2.3.3
Alarm filtering
To verify that the EMS allows the operator to filter and

selectively display the filtered alarms according to the
filtering options.
2.3.3
Alarm masking
To verify that the EMS is able to mask or hide the

unwanted alarms
2.3.4
Polling time configuration
To verify that the EMS allows configuration of polling time

between EMS and NE
2.3.5
Severity setting
To verify that the EMS is able to modify the representation

of alarms according to severity (i.e. change the colour
and the severity of each alarm)
2.3.6
Alarm escalation
To verify that the EMS is able to escalate alarms received

via email and log the sending date and time of escalation.
2.4
Reporting
management
2.4.1
for
on
To verify that the operator is able to input remarks,

username, date and time of acknowledgement
fault
Exporting of reports
To verify that the EMS is able to export the reports to

other format, particularly Excel, Word and HTML form.
2.4.2
Creation of template reports
To verify that the EMS is able to allow the operator to

design report templates
2.4.3
Graphical representation
fault management reports
of
To verify that the EMS is able to generate and print

graphical representation of fault management report
2.4.4
Statistical representation
fault management reports
of

statistical representation of fault management report
(tabulation)
event

fault/event occurrences report representation, such as NE
location versus alarm type for particular date and time
2.4.5
Generation of fault/
occurrences report

(February 2009)
Page : 8
Doc No:
Revision No: 2
Doc Title:
Performance Monitoring
4.1
Performance
Report
Management
4.1.1
Scheduling of performance
management report
4.2
Performance
Report
4.2.1
Generation of performance
monitoring report
To verify that the EMS is able to establish a schedule for

reporting performance data. An example of this is by
selecting the date and time for the performance
monitoring.
Management
To verify that the EMS is able to display and print
(monthly, weekly, daily, 15 minutes, 24 hours)
performance report including:
a) Date vs performance data
b) NE location vs performance data for a particular
time
4.2.2
Exporting
report
of
performance
4.2.3
Web
based
performance
report generation and printing
3.3
SYSTEM TOPOLOGY
3.3.1
Creation, deletion and edition

of performance threshold
3.4
PM data handling
3.4.1
Creation, deletion and edition

of performance report

(February 2009)
To verify that the EMS is able to export report to Excel

and Word.
To verify that the EMS can generate and print web based
performance report
EMS software must have a topology which a few level.
To verify that EMS allows the operator to create, update

and delete customizable performance threshold profiles
for the physical link that is monitored.
Page : 9
Doc No:
Revision No: 2
Doc Title:
Configuration Management
4.1
Discovery of Network Element
4.1.1
Add/Remove and edit NE
To verify that the EMS is able to add, delete and edit NE.
4.1.2
Checking loss of connectivity

between NE and EMS
To verify that the EMS is able to check the loss of

connectivity between the NE and EMS
To verify that the EMS is able to re-synchronize the
database with the current state of the NE upon discovery
4.1.3
Auto discovery of NE
4.2
Display of Network Elements
4.2.1
Display NE according to
graphical area
4.3
Software Upgrade
4.3.1
Remote software upgrade
To verify that the EMS can perform auto discovery of the

network elements and automatically draw the graphics of
bay, shelf and slot configuration, once the NE is autodiscovered.
To verify that the EMS is able to display the NE according

to geographical area
To verify that the EMS shall be able to:

a) Remotely upgrade the managed NE to new
software release.
b) Indicate status of upgrading, including mismatch
of data, checklist of items indicating successful
upgrade
c) Upgrade the software without interruption in
services provided to subscriber and operations of
NE
4.4
Date and Time Administration
4.4.1
Setting and changing

managed NE

(February 2009)
To verify the EMS can set and change .the managed NE

date and time.
Page : 10
Doc No:
Revision No: 2
Doc Title:

(February 2009)
Page : 11
Doc No:
Revision No: 2
Doc Title:
Security Management
5.1
Assignment of users
5.2
Creation, addition and deletion To verify that the EMS supports creation (user information
of users
and password), deletion and modification of users.
5.3
Change password function
To verify that SA can change user password for security
5.4
Display of active user
To verify that the system can display current list of active

user.
5.5
Force user logout
To verify that the system can release/terminate of active

user
5.6
Modification of user profiles
To verify that the EMS supports modification of user

profiles.
To verify that the EMS is able to assign at lease three

categories of users, namely System Administrator,
Operation and Maintenance, NOC user
The user profile shall include the user ID, name,

telephone number, division, address, description, NE
function menu controlled, NE location controlled and
customer controlled.
5.7
Access right of users (function

menu)
To verify that the EMS supports user access right in terms

of function menu
5.8
Access right of users

(geographical area of interest)
To verify that the EMS supports user access right in terms

of geographical area of interest
5.9
Audit trail
To verify that the EMS supports audit trail, including the

following items:
a) Date/ time
b) Activities - Add/delete NE,
- Enable/disable port
- Add/delete user
- Port configuration changes
- User login/ logout
c) NE/ Port related to the activity
d) User name
e) Client / workstation entered

(February 2009)
Page : 12
Doc No:
Revision No: 2
Doc Title:
f)
5.10
Stress test

(February 2009)
User command entered
To verify that the system can handle sudden burst of

information processing load (receiving sudden flow
maximum alarms at a very short period of time) to the
server and client software
Page : 13
Doc No:
Revision No: 2
Doc Title:
TEST ITEM
5.1
DATABASE BACK-UP AND RESTORATION

1.0 Database back-up and restoration
1.1 Data purging
TEST OBJECTIVE:
PRE-REQUISITE:
To verify that the system is able to auto-purge

out of date information a.g. alarm, audit trail
logs.
none
PROCEDURES
Run dbbackup.exe, login with Admin user, connect to database which historical alarms are stored
from system setting tab, then go to Delete tab, click Delete history tables to delete database
according to the setting.
Expected Result:
Actual Result
The dated data will be deleted.

(February 2009)
Page : 14
Doc No:
Revision No: 2
Doc Title:
ACCEPTABLE
NOT ACCEPTABLE
Name:
Div:
Signature:
Date:
Name:
Div:
Signature:
Date:
Name:
Div:
Signature:
VERIFIED BY TM:
VERIFIED BY
SUPPLIER:

(February 2009)
Date:
Page : 15
Doc No:
Revision No: 2
Doc Title:
1.2 NE restoration back-up/restore
TEST OBJECTIVE:
PRE-REQUISITE:
To verify the system is able to back-up the NE

configuration manually and schedule.
NE information has been created.
PROCEDURES
NE configuration information is stored into an ACCESS database file, we only need to backup/restore the ACCESS database file to back-up/restore NE configuration
Expected Result:
Actual Result
Backup Database after NE configured

The configuration information can be restored.

(February 2009)
Page : 16
Doc No:
Revision No: 2
Doc Title:
1.2 NE restoration back-up/restore

ACCEPTABLE
NOT ACCEPTABLE
VERIFIED BY TM:
VERIFIED BY
SUPPLIER:
Name:
Div:
Signature:
Date:
Name:
Div:
Signature:
Date:
Name:
Div:
Signature:

(February 2009)
Date:
Page : 17
Doc No:
Revision No: 2
Doc Title:
5.2
FAULT MANAGEMENT
2.0 FAULT MANAGEMENT
2.1 Housekeeping Alarms
2.1.1 Monitor rack temperature
TEST OBJECTIVE:
PRE-REQUISITE:
To simulate the alarm and verify that the EMS is

able to monitor the rack temperature and
generate alarm should the temperature
threshold is increased.
Temperature sensor is provided
PROCEDURES
Open the Integrated Client (run container.exe),go to the detailed page of environment device from
Navigate Window, temperature will be display
Change the threshold of temperature, the alarm will be displayed.

(February 2009)
Page : 18
Doc No:
Revision No: 2
Doc Title:
2.1.1 Monitor rack temperature

Expected Result:
Actual Result
The NE environment temperature will be display

on the EMS
ACCEPTABLE
NOT ACCEPTABLE
Name:
Div:
Signature:
Date:
Name:
Div:
Signature:
Date:
Name:
Div:
Signature:
VERIFIED BY TM:
VERIFIED BY
SUPPLIER:

(February 2009)
Date:
Page : 19
Doc No:
Revision No: 2
Doc Title:

(February 2009)
Page : 20
Doc No:
Revision No: 2
Doc Title:

2.1.2 Monitor fan status
TEST OBJECTIVE:
PRE-REQUISITE:
To verify that the EMS is able to monitor the fan

status
Only used for ZXDU3000 system
PROCEDURES
Open the Integrated Client (run container.exe), go to the detailed page of Switching Power Supply
from the Navigate Window, the fan state of the rectifier will be displayed
Expected Result:
Actual Result
Fan state of the rectifier will be displayed on the

EMS

(February 2009)
Page : 21
Doc No:
Revision No: 2
Doc Title:
2.1.2 Monitor fan status
ACCEPTABLE
NOT ACCEPTABLE
VERIFIED BY TM:
VERIFIED BY
SUPPLIER:
Name:
Div:
Signature:
Date:
Name:
Div:
Signature:
Date:
Name:
Div:
Signature:

(February 2009)
Date:
Page : 22
Doc No:
Revision No: 2
Doc Title:

2.1.3 Monitor humidity
TEST OBJECTIVE:
PRE-REQUISITE:
To verify that the EMS is able to monitor the

humidity level in the DSLAM
Humidity sensor has been installed.
PROCEDURES
Open the Integrated Client (run container.exe), go to the detailed page of environment device from
Navigate Window, humidity will be display

(February 2009)
Page : 23
Doc No:
Revision No: 2
Doc Title:

Expected Result:

Actual Result
Environment humidity will be displayed on EMS
ACCEPTABLE
NOT ACCEPTABLE

(February 2009)
Page : 24
Doc No:
Revision No: 2
Doc Title:

VERIFIED BY TM:
VERIFIED BY
SUPPLIER:
Name:
Div:
Signature:
Date:
Name:
Div:
Signature:
Date:
Name:
Div:
Signature:

TEST OBJECTIVE:
Date:
2.1.4 Monitor rectifier

PRE-REQUISITE:

rectifier status

(February 2009)
Page : 25
Doc No:
Revision No: 2
Doc Title:

PROCEDURES
device from the Navigate Window, the state of the rectifier will be displayed
Expected Result:
Actual Result
The rectifier status will be displayed
ACCEPTABLE
NOT ACCEPTABLE
(February 2009)
Page : 26
Doc No:
Revision No: 2
Doc Title:
Name:
Div:
Signature:
Date:
Name:
Div:
Signature:
Date:
Name:
Div:
Signature:
VERIFIED BY TM:
VERIFIED BY
SUPPLIER:

(February 2009)
Date:
Page : 27
Doc No:
Revision No: 2
Doc Title:

2.1.5 Monitor battery on load
TEST OBJECTIVE:
PRE-REQUISITE:

battery status
rectifier has been connected with battery and

load
PROCEDURES
from the Navigate Window, the state of the battery on load will be displayed
Expected Result:
Actual Result
The battery charging mode, current and battery

voltage will be displayed on EMS.

(February 2009)
Page : 28
Doc No:
Revision No: 2
Doc Title:
2.1.5 Monitor battery on load
ACCEPTABLE
NOT ACCEPTABLE
Name:
Div:
Signature:
Date:
Name:
Div:
Signature:
Date:
Name:
Div:
Signature:
VERIFIED BY TM:
VERIFIED BY
SUPPLIER:

(February 2009)
Date:
Page : 29
Doc No:
Revision No: 2
Doc Title:

2.2 Alarm display at EMS
2.2.1 Active alarm display at EMS
TEST OBJECTIVE:
PRE-REQUISITE:
To simulate an alarm and verify that the alarm

received at the EMS have the following items:
NE-EMS communicate OK
g) Severity of alarms
h) Received date and time for each alarm
i)
Alarm type and description
j)
Alarm location (specific location of alarm

that has occurred)
k) NE location the area name in which

the NE is located
PROCEDURES
Open the Integrated Client (run container.exe), open the Alarm View window from the toolbar, and
then simulate an alarm, this alarm will be displayed on Active Alarm window automatically.

(February 2009)
Page : 30
Doc No:
Revision No: 2
Doc Title:
2.2.1 Active alarm display at EMS

Expected Result:
Actual Result
Alarm information including the site name, alarm

description alarm time, receive time and alarm
severity, and so on.
ACCEPTABLE
NOT ACCEPTABLE
VERIFIED BY TM:
VERIFIED BY
SUPPLIER:
Name:
Div:
Signature:
Date:
Name:
Div:
Signature:
Date:
Name:
Div:
Signature:

(February 2009)
Date:
Page : 31
Doc No:
Revision No: 2
Doc Title:

2.2.2 Historical Alarm display at EMS
TEST OBJECTIVE:
PRE-REQUISITE:
To simulate an alarm and verify that the alarm

received at the EMS have the following items:
none
l)
Severity of alarms
m) Received date and time for each alarm

n) Alarm type and description
o) Alarm location (specific location of alarm
that has occurred)
p) NE location the area name in which
the NE is located
PROCEDURES
Open the report Client (run report.exe),click open clip from toolbar, according to query condition to
query historical alarm from Alarm Manage function

(February 2009)
Page : 32
Doc No:
Revision No: 2
Doc Title:
2.2.2 Historical Alarm display at EMS

Expected Result:
Actual Result
The history alarm information including: site

name alarm time, received time, alarm
description, alarm severity and so on.
ACCEPTABLE
NOT ACCEPTABLE
VERIFIED BY TM:
VERIFIED BY
SUPPLIER:
Name:
Div:
Signature:
Date:
Name:
Div:
Signature:
Date:
Name:
Div:
Signature:

(February 2009)
Date:
Page : 33
Doc No:
Revision No: 2
Doc Title:

2.2.3 Severity of alarms
TEST OBJECTIVE:
PRE-REQUISITE:
To verify that the EMS is able to distinguish

display the severity of alarms, such as critical,
major, minor
none
PROCEDURES
Open the Integrated Client (run container.exe), open Alarm View window from the toolbar; the
description of alarm included severity of alarm on this window and also different severity of alarm is
distinguished with different foreground color.

(February 2009)
Page : 34
Doc No:
Revision No: 2
Doc Title:

Expected Result:
Actual Result
alarm severity has three levels: Critical ,major

and minor, different severity of alarm can be
distinguish display.
ACCEPTABLE
NOT ACCEPTABLE
VERIFIED BY TM:
Name:
Div:
Signature:
Date:
Name:
Div:
Signature:
Date:

(February 2009)
Page : 35
Doc No:
Revision No: 2
Doc Title:

VERIFIED BY
SUPPLIER:
Name:
Div:

Signature:
Date:
2.2.4 Alarm alert
TEST OBJECTIVE:
PRE-REQUISITE:
To verify that the EMS will have a visual and

audible alert upon receiving alarms.
NE has sent out the alarm to the EMS, AlarmBox or speaker is installed at supervision center
PROCEDURES
Open the Integrated Client (run container.exe), make sure the driver of Alarm-Box or speaker has
been installed and started rightly.

(February 2009)
Page : 36
Doc No:
Revision No: 2
Doc Title:

Expected Result:
2.2.4 Alarm alert

Actual Result
When alarm sent to the EMS

1) The EMS will pop up the real time alarm
window. All alarms will be show with red
background color (it can be set optionally).
2) The alarm voice will heard from the speaker
or Alarm-Box
ACCEPTABLE
NOT ACCEPTABLE

(February 2009)
Page : 37
Doc No:
Revision No: 2
Doc Title:
2.2.4 Alarm alert

Name:
Div:
Signature:
Date:
Name:
Div:
Signature:
Date:
Name:
Div:
Signature:
VERIFIED BY TM:
VERIFIED BY
SUPPLIER:

2.2 Alarm/Event data handling
TEST OBJECTIVE:
Date:
2.3.1 Acknowledgement of alarms

PRE-REQUISITE:
To verify that the EMS allows the operator to

acknowledge alarms.
PROCEDURES
On the Integrated Client, open Alarm View window, click Affirm on command column

(February 2009)
Page : 38
Doc No:
Revision No: 2
Doc Title:

Expected Result:

Actual Result
Alarm could be acknowledged.
ACCEPTABLE
NOT ACCEPTABLE

(February 2009)
Page : 39
Doc No:
Revision No: 2
Doc Title:

Name:
Div:
Signature:
Date:
Name:
Div:
Signature:
Date:
Name:
Div:
Signature:
VERIFIED BY TM:
VERIFIED BY
SUPPLIER:

TEST OBJECTIVE:
Date:
2.3.2 Inserting input on acknowledgement

PRE-REQUISITE:
To verify that the operator is able to input

remarks, username, date and time of
acknowledgement

(February 2009)
Page : 40
Doc No:
Revision No: 2
Doc Title:

PROCEDURES
It is stored automatically after alarm is acknowledged.
Expected Result:
Actual Result
ACCEPTABLE
NOT ACCEPTABLE

(February 2009)
Page : 41
Doc No:
Revision No: 2
Doc Title:
Name:
Div:
Signature:
Date:
Name:
Div:
Signature:
Date:
Name:
Div:
Signature:
VERIFIED BY TM:
VERIFIED BY
SUPPLIER:

(February 2009)
Date:
Page : 42
Doc No:
Revision No: 2
Doc Title:

TEST OBJECTIVE:
2.3.3 Alarm filtering

PRE-REQUISITE:
To verify that the EMS allows the operator to

filter and selectively display the filtered alarms
according to the filtering options.
PROCEDURES
Open Integrated client (run container.exe), open Alarm view from toolbar, and click Configure to set
the filtering options of alarms

(February 2009)
Page : 43
Doc No:
Revision No: 2
Doc Title:

Expected Result:
Actual Result
Alarm can be filtered and selectively display

according to the filtering options.
ACCEPTABLE
NOT ACCEPTABLE
Name:
Div:
Signature:
Date:
Name:
Div:
Signature:
Date:
VERIFIED BY TM:

(February 2009)
Page : 44
Doc No:
Revision No: 2
Doc Title:

VERIFIED BY
SUPPLIER:
Name:
Div:

TEST OBJECTIVE:
Signature:
Date:
2.3.4 Alarm masking

PRE-REQUISITE:
To verify that the EMS is able to mask or hide

the unwanted alarms
(February 2009)
Page : 45
Doc No:
Revision No: 2
Doc Title:

2.3.4 Alarm masking
PROCEDURES
Open the Integrated Client (run container.exe), open the detailed page of device, right-click on the
alarm name which will be filtered, and select alarm mask
Expected Result:
Actual Result
Alarms can be masked or hided.
ACCEPTABLE
NOT ACCEPTABLE
(February 2009)
Page : 46
Doc No:
Revision No: 2
Doc Title:
2.3.4 Alarm masking
Name:
Div:
Signature:
Date:
Name:
Div:
Signature:
Date:
Name:
Div:
Signature:
VERIFIED BY TM:
VERIFIED BY
SUPPLIER:

(February 2009)
Date:
Page : 47
Doc No:
Revision No: 2
Doc Title:

2.3.5 Polling time configuration
TEST OBJECTIVE:
PRE-REQUISITE:
To verify that the EMS allows configuration of

polling time between EMS and NE
none
PROCEDURES
Run cfgpro.exe ,connect to DB, enter common user, click other config tables, select
SCANBUS table, change the value of scan interval or scan time for each SCANBUS

(February 2009)
Page : 48
Doc No:
Revision No: 2
Doc Title:

Expected Result:

Actual Result
The interval time can be set.
ACCEPTABLE
NOT ACCEPTABLE

(February 2009)
Page : 49
Doc No:
Revision No: 2
Doc Title:

VERIFIED BY TM:
VERIFIED BY
SUPPLIER:
Name:
Div:
Signature:
Date:
Name:
Div:
Signature:
Date:
Name:
Div:
Signature:

2.3.6 Severity setting
TEST OBJECTIVE:
PRE-REQUISITE:
To verify that the EMS is able to modify the

representation of alarms according to severity
(i.e change the colour and the severity of each
None

(February 2009)
Date:
Page : 50
Doc No:
Revision No: 2
Doc Title:

alarm)
PROCEDURES
Open the Integrated Client (run container.exe), open the detailed page of device, right-click on the
alarm name whichs severity will be changed, and select Property, then change the alarm level
Expected Result:
Actual Result
System could set level of alarm, alarm voice and

the color of alarm background.
ACCEPTABLE
(February 2009)
Page : 51
Doc No:
Revision No: 2
Doc Title:
NOT ACCEPTABLE
Name:
Div:
Signature:
Date:
Name:
Div:
Signature:
Date:
Name:
Div:
Signature:
VERIFIED BY TM:
VERIFIED BY
SUPPLIER:

(February 2009)
Date:
Page : 52
Doc No:
Revision No: 2
Doc Title:

2.3.7 Alarm Escalation
TEST OBJECTIVE:
PRE-REQUISITE:
To verify that the EMS is able to escalate alarms

received via email and log the sending date and
time of escalation.
Need SMS module.
PROCEDURES
1.Connect SMS module with client PC
2. configured SMS module drivers.

(February 2009)
Page : 53
Doc No:
Revision No: 2
Doc Title:

Expected Result:

Actual Result
Able to escalate alarms via SMS and Email.

(February 2009)
Page : 54
Doc No:
Revision No: 2
Doc Title:
ACCEPTABLE
NOT ACCEPTABLE
Name:
Div:
Signature:
Date:
Name:
Div:
Signature:
Date:
Name:
Div:
Signature:
VERIFIED BY TM:
VERIFIED BY
SUPPLIER:

(February 2009)
Date:
Page : 55
Doc No:
Revision No: 2
Doc Title:

2.4 Reporting for fault management
2.4.1 Exporting of reports
TEST OBJECTIVE:
PRE-REQUISITE:
To verify that the EMS is able to export the

reports to other format, particularly Excel, Word
and HTML form.
None
PROCEDURES
Open the report client (run report.exe)
Export the history performance and alarm data to Excel, TXT or HTML form

(February 2009)
Page : 56
Doc No:
Revision No: 2
Doc Title:

Expected Result:
Actual Result
Data record can be exported to Excel, TXT and

HTML form
Excel, TXT, HTM

(February 2009)
Page : 57
Doc No:
Revision No: 2
Doc Title:
ACCEPTABLE
NOT ACCEPTABLE
VERIFIED BY TM:
VERIFIED BY
SUPPLIER:
Name:
Div:
Signature:
Date:
Name:
Div:
Signature:
Date:
Name:
Div:
Signature:

(February 2009)
Date:
Page : 58
Doc No:
Revision No: 2
Doc Title:

TEST OBJECTIVE:
2.4.2 Creation of template reports

PRE-REQUISITE:
To verify that the EMS is able to allow the

operator to design report templates.
PROCEDURES
Run report.exe, click Customize from menu, select sites and device from pop-up windows, then
save the new type of template.
Expected Result:
Actual Result
New type of template.
ACCEPTABLE

(February 2009)
Page : 59
Doc No:
Revision No: 2
Doc Title:
2.4.2 Creation of template reports
NOT ACCEPTABLE
Name:
Div:
Signature:
Date:
Name:
Div:
Signature:
Date:
Name:
Div:
Signature:
VERIFIED BY TM:
VERIFIED BY
SUPPLIER:

(February 2009)
Date:
Page : 60
Doc No:
Revision No: 2
Doc Title:

2.4.3 Graphical representation

management report
TEST OBJECTIVE:
PRE-REQUISITE:
of
To verify that the EMS is able to generate and

print
graphical
representation
of
fault
management report
PROCEDURES
1.Run report.exe, Open the alarm curve from Alarm Detail clip
2.Run the Alarm Curve function of Alarm Curve
3. Select one alarm and time span on the new window, and click Query button.
Expected Result:
Actual Result
EMS is able to generate and print graphical

representation of fault management report.
ACCEPTABLE
NOT ACCEPTABLE
Name:
Div:
Signature:
Date:
Name:
Div:
Signature:
Date:
Name:
Div:
Signature:
VERIFIED BY TM:
VERIFIED BY
SUPPLIER:

(February 2009)
Date:
Page : 61
fault
Doc No:
Revision No: 2
Doc Title:

2.4.4 Statistical representation

management report
TEST OBJECTIVE:
PRE-REQUISITE:
of

print
statistical
representation
of
fault
management report (tabulation)
PROCEDURES
1.Run report.exe, Open Alarm Detail from Alarm Manage
2.Run the function of Device Alarm Detail
3. click Query button to query the report according to the setting

(February 2009)
Page : 62
fault
Doc No:
Revision No: 2
Doc Title:


management report
Expected Result:
Actual Result
of
EMS is able to generate and print statistical

representation of fault management report
(tabulation).
ACCEPTABLE
NOT ACCEPTABLE
VERIFIED BY TM:
Name:
Div:
Signature:
Date:
Name:
Div:
Signature:
Date:

(February 2009)
Page : 63
fault
Doc No:
Revision No: 2
Doc Title:

management report

VERIFIED BY
SUPPLIER:
Name:
Div:
Signature:
of
fault
Date:
2.4.5 Generation of fault/event occurrences

report
TEST OBJECTIVE:
PRE-REQUISITE:

print
fault/event
occurrences
report
representation, such as NE location versus
alarm type for particular date and time.
PROCEDURES
Run the report.exe, query history data record according to particular date and time.
Print the history data record
(February 2009)
Page : 64
Doc No:
Revision No: 2
Doc Title:


report
Expected Result:
Actual Result
History data record can be print.
ACCEPTABLE
NOT ACCEPTABLE
Name:
Div:
Signature:
Date:
Name:
Div:
Signature:
Date:
VERIFIED BY TM:

(February 2009)
Page : 65
Doc No:
Revision No: 2
Doc Title:

report

VERIFIED BY
SUPPLIER:
5.3
Name:
Div:
Signature:
Date:
PERFORMANCE MONITORING
3.0 Performance Monitoring

3.1 Performance Management Report
3.1.1 Scheduling of performance management

report
TEST OBJECTIVE:
PRE-REQUISITE:
To verify that the EMS is able to establish a

schedule for reporting performance data. An
EMS is running on the windows operating

system.

(February 2009)
Page : 66
Doc No:
Revision No: 2
Doc Title:

example of this is by selecting the date and time
for the performance monitoring.

report
History Data has been stored
PROCEDURES
1) Run report.exe
2) Query the history data according to selecting the alarm starting date( time ) and ending date
(time) or the NE name , equipment etc
3) Observe the result of query
Expected Result:
Actual Result
The reporting subsystem output the

performance report according to the query
conditions.
ACCEPTABLE
NOT ACCEPTABLE

(February 2009)
Page : 67
Doc No:
Revision No: 2
Doc Title:

report

Name:
Div:
Signature:
Date:
Name:
Div:
Signature:
Date:
Name:
Div:
Signature:
VERIFIED BY TM:
VERIFIED BY
SUPPLIER:

(February 2009)
Date:
Page : 68
Doc No:
Revision No: 2
Doc Title:

3.2 Performance Monitoring Report
3.2.1 Generation of performance monitoring

report
TEST OBJECTIVE:
PRE-REQUISITE:
To verify that the EMS is able to display and

print (monthly, daily, 15 minutes, 24 hours)
performance report including:
History Data has been stored

Printer has been connected.
c) Date vs performance data

b) NE location vs performance data for a
particular time
PROCEDURES
1) Run report.exe, Query history data according to day and the station.
2) Observe the result of query
3) Print the result of query

(February 2009)
Page : 69
Doc No:
Revision No: 2
Doc Title:
3.2.1 Generation of performance monitoring

report

Expected Result:
Actual Result
1) The reporting subsystem output the

performance report of the date, day, and
station.
2) The report subsystem can support the printer.
ACCEPTABLE
NOT ACCEPTABLE
Name:
Div:
Signature:
Date:
Name:
Div:
Signature:
Date:
Name:
Div:
Signature:
VERIFIED BY TM:
VERIFIED BY
SUPPLIER:

(February 2009)
Date:
Page : 70
Doc No:
Revision No: 2
Doc Title:

3.2.2 Exporting of performance report
TEST OBJECTIVE:
PRE-REQUISITE:
To verify that the EMS is able to export report to

Excel and Word.
None
PROCEDURES
1) Open the report subsystem at the EMS
2) Query the history data according to the condition
3) Export the history data to the Excel format file

(February 2009)
Page : 71
Doc No:
Revision No: 2
Doc Title:

Expected Result:

Actual Result
Excel report file will be built.

(February 2009)
Page : 72
Doc No:
Revision No: 2
Doc Title:
ACCEPTABLE
NOT ACCEPTABLE
VERIFIED BY TM:
VERIFIED BY
SUPPLIER:
Name:
Div:
Signature:
Date:
Name:
Div:
Signature:
Date:
Name:
Div:
Signature:

(February 2009)
Date:
Page : 73
Doc No:
Revision No: 2
Doc Title:

3.2.3
Web based
generation and printing
TEST OBJECTIVE:
PRE-REQUISITE:
To verify that the EMS can generate and print

web based performance report
None
performance
PROCEDURES
Expected Result:
Actual Result
ACCEPTABLE
(February 2009)
Page : 74
report
Doc No:
Revision No: 2
Doc Title:
3.2.3
Web based
performance
NOT ACCEPTABLE
Name:
Div:
Signature:
Date:
Name:
Div:
Signature:
Date:
Name:
Div:
Signature:
VERIFIED BY TM:
VERIFIED BY
SUPPLIER:

(February 2009)
Date:
Page : 75
report
Doc No:
Revision No: 2
Doc Title:
3.0 Performance Report

3.3 SYSTEM TOPOLOGY
3.3.1 Creation, deletion and edition of SYSTEM

topology
TEST OBJECTIVE:
PRE-REQUISITE:
EMS software must have a topology which a few

level
None

(February 2009)
Page : 76
Doc No:
Revision No: 2
Doc Title:

3.3 SYSTEM TOPOLOGY

topology
PROCEDURES
Open Integrated Client(run container.exe)
Enter design mode, make 4 pages to display 4 level of topology respectively,
Expected Result:
Actual Result
System topology can be created deleted and

edited.
ACCEPTABLE
NOT ACCEPTABLE

(February 2009)
Page : 77
Doc No:
Revision No: 2
Doc Title:

topology
3.3 SYSTEM TOPOLOGY
Name:
Div:
Signature:
Date:
Name:
Div:
Signature:
Date:
Name:
Div:
Signature:
VERIFIED BY TM:
VERIFIED BY
SUPPLIER:

(February 2009)
Date:
Page : 78
Doc No:
Revision No: 2
Doc Title:

3.4 PM data handling
3.4.1 Creation, deletion

performance report
TEST OBJECTIVE:
PRE-REQUISITE:
To verify that EMS allows the operator to create,

update and delete customizable performance
threshold profiles for the physical link that is
monitored.
None
and
edition
PROCEDURES
Expected Result:
Actual Result
ACCEPTABLE
NOT ACCEPTABLE
Name:
Div:
Signature:
Date:
Name:
Div:
Signature:
Date:
Name:
Div:
Signature:
VERIFIED BY TM:
VERIFIED BY
SUPPLIER:

(February 2009)
Date:
Page : 79
of
Doc No:
Revision No: 2
Doc Title:
5.4
CONFIGURATION MANAGEMENT
4.0 Configuration Management

4.1 Discovery of Network Element
4.1.1 Add/Remove and edit NE
TEST OBJECTIVE:
PRE-REQUISITE:
To verify that the EMS is able to add, delete and

edit NE
None
PROCEDURES
1) Open the configuring subsystem at the EMS( run cfgpro.exe)
2) Configure the database of NE ( for example ,add , delete and modify the monitored equipment)
3) Connect the modified database for the monitor subsystem at the EMS
4) Restart Integrated client(container.exe) and pre-processor( FrontPC.exe)
5) Observe the modified station name and equipment etc

(February 2009)
Page : 80
Doc No:
Revision No: 2
Doc Title:
4.1.1 Add/Remove and edit NE

Expected Result:
Actual Result
The station and device could be added, deleted

and modified.
ACCEPTABLE
NOT ACCEPTABLE
VERIFIED BY TM:
VERIFIED BY
SUPPLIER:
Name:
Div:
Signature:
Date:
Name:
Div:
Signature:
Date:
Name:
Div:
Signature:

(February 2009)
Date:
Page : 81
Doc No:
Revision No: 2
Doc Title:

4.1.2 Checking loss of connectivity between NE

and EMS
TEST OBJECTIVE:
PRE-REQUISITE:
To verify that the EMS is able to check the loss

of connectivity between the NE and EMS
NE-EMS communicate OK
To verify that the EMS is able to re-synchronize

the database with the current state of the NE
upon discovery
PROCEDURES
1) Open Integrated Client(run container.exe)
2) Manual break the communicate( for example, put the NE equipment power off) between NE
and EMS
3) Observe the communicate status at the monitor subsystem
4) Recover the communicate ( for example ,put the NE equipment power on)
5) Observe the communicate status at the monitor subsystem

(February 2009)
Page : 82
Doc No:
Revision No: 2
Doc Title:

4.1.2 Checking loss of connectivity between NE

and EMS
Expected Result:
Actual Result
It can be displayed the NE communication

status ON EMS.
ACCEPTABLE
NOT ACCEPTABLE
VERIFIED BY TM:
VERIFIED BY
SUPPLIER:
Name:
Div:
Signature:
Date:
Name:
Div:
Signature:
Date:
Name:
Div:
Signature:

(February 2009)
Date:
Page : 83
Doc No:
Revision No: 2
Doc Title:
4.1.3 Auto discovery of NE
4.1 Discovery of network elements

TEST OBJECTIVE:
To verify that the EMS can perform
discovery of the network elements
automatically draw the graphics of bay,
and slot configuration, once the NE is
discovered.
PRE-REQUISITE:
auto
and
shelf
auto-
New NE should be configure in EMS first
PROCEDURES
Expected Result:
Actual Result
New site can be discovered automatically

(February 2009)
Page : 84
Doc No:
Revision No: 2
Doc Title:
4.1.3 Auto discovery of NE
4.1 Discovery of network elements
ACCEPTABLE
NOT ACCEPTABLE
VERIFIED BY TM:
VERIFIED BY
SUPPLIER:
Name:
Div:
Signature:
Date:
Name:
Div:
Signature:
Date:
Name:
Div:
Signature:

(February 2009)
Date:
Page : 85
Doc No:
Revision No: 2
Doc Title:

4.2 Display of Network Elements
4.2.1 Display NE according to graphical area
TEST OBJECTIVE:
PRE-REQUISITE:
To verify that the EMS is able to display the NE

according to geographical area
electronic map file has been used
PROCEDURES
1) open Integrated client( run container.exe),
2) Entering Design mode
3) configure the electronic map, set site location on the map
Expected Result:
Actual Result
Displaying the site icon on the map in the

monitoring subsystem.

(February 2009)
Page : 86
Doc No:
Revision No: 2
Doc Title:
4.2.1 Display NE according to graphical area
4.2 Display of Network Elements
ACCEPTABLE
NOT ACCEPTABLE
VERIFIED BY TM:
VERIFIED BY
SUPPLIER:
Name:
Div:
Signature:
Date:
Name:
Div:
Signature:
Date:
Name:
Div:
Signature:

(February 2009)
Date:
Page : 87
Doc No:
Revision No: 2
Doc Title:

4.3 Software Upgrade
TEST OBJECTIVE:
4.3.1 Remote software upgrade

PRE-REQUISITE:
To verify that the EMS shall be able to:

a) Remotely upgrade the managed NE to
new software release.
b) Indicate status of upgrading, including
mismatch of data, checklist of items
indicating successful upgrade
Upgrade the software without interruption in
services provided to subscriber and operations
of NE
PROCEDURES

(February 2009)
Page : 88
Doc No:
Revision No: 2
Doc Title:
4.3.1 Remote software upgrade
4.3 Software Upgrade

Expected Result:
Actual Result
Will be tested during implementation.
ACCEPTABLE
NOT ACCEPTABLE
VERIFIED BY TM:
VERIFIED BY
SUPPLIER:
Name:
Div:
Signature:
Date:
Name:
Div:
Signature:
Date:
Name:
Div:
Signature:

(February 2009)
Date:
Page : 89
Doc No:
Revision No: 2
Doc Title:

4.4 Date and Time Administration
4.4.1 Setting and changing managed NE
TEST OBJECTIVE:
PRE-REQUISITE:
To verify the EMS can set and change .the

managed NE date and time.
None
PROCEDURES

(February 2009)
Page : 90
Doc No:
Revision No: 2
Doc Title:

Expected Result:
Actual Result
ACCEPTABLE
NOT ACCEPTABLE
VERIFIED BY TM:
Name:

(February 2009)
Div:
Signature:
Date:
Page : 91
Doc No:
Revision No: 2
Doc Title:
VERIFIED BY
SUPPLIER:
5.5
Name:
Div:
Signature:
Name:
Div:
Signature:
Date:
Date:
SECURITY MANAGEMENT
5.0 Security Management
5.1 Assignment of users
TEST OBJECTIVE:
PRE-REQUISITE:
To verify that the EMS is able to assign at lease

three categories of users, namely System
Administrator, Operation and Maintenance,
NOC user
None

(February 2009)
Page : 92
Doc No:
Revision No: 2
Doc Title:
PROCEDURES
1) Open Integrated Client (run container.exe)
2) click the menu of Operator, then select Operator Manage
3) Add user and configure the users property
Expected Result:
Actual Result
3 level security of super user, administrator and

maintenance.
ACCEPTABLE
NOT ACCEPTABLE

(February 2009)
Page : 93
Doc No:
Revision No: 2
Doc Title:
Name:
Div:
Signature:
Date:
Name:
Div:
Signature:
Date:
Name:
Div:
Signature:
VERIFIED BY TM:
VERIFIED BY
SUPPLIER:
5.2 Creation, addition and deletion of users
TEST OBJECTIVE:
PRE-REQUISITE:
To verify that the EMS supports creation (user

information and password), deletion and
modification of users.
None

(February 2009)
Date:
Page : 94
Doc No:
Revision No: 2
Doc Title:
PROCEDURES
1) Open Integrated Client by super user
3) Add, delete and modify the user information and password and right
4) Observe whether the configured different user can login in the system
Expected Result:
Actual Result
Only the super user can add, delete and modify

the user information and password.
Only Admin can add, delete, modify user
ACCEPTABLE
NOT ACCEPTABLE

(February 2009)
Page : 95
Doc No:
Revision No: 2
Doc Title:
Name:
Div:
Signature:
Date:
Name:
Div:
Signature:
Date:
Name:
Div:
Signature:
VERIFIED BY TM:
VERIFIED BY
SUPPLIER:

(February 2009)
Date:
Page : 96
Doc No:
Revision No: 2
Doc Title:
5.3 Change password function
TEST OBJECTIVE:
PRE-REQUISITE:
To verify that SA can change user password for

security
None
PROCEDURES
1) Open Integrated Client by super user
3) Modify the users password
4) Observe whether the user can login in the system with the new password and can not login in
the system with the old password any more.
Expected Result:
Actual Result
The users password will be changed.

(February 2009)
Page : 97
Doc No:
Revision No: 2
Doc Title:
5.3 Change password function

ACCEPTABLE
NOT ACCEPTABLE
VERIFIED BY TM:
VERIFIED BY
SUPPLIER:
Name:
Div:
Signature:
Date:
Name:
Div:
Signature:
Date:
Name:
Div:
Signature:

(February 2009)
Date:
Page : 98
Doc No:
Revision No: 2
Doc Title:
5.4 Display of active user
TEST OBJECTIVE:
PRE-REQUISITE:
To verify that the system can display current list

of active user.
PROCEDURES
The list of active user displaying is no available, but the monitor system can display the login in
user
1) Open the monitor subsystem at the EMS
2) The user login in
3) The user ID etc can be display ed at the status-bar of Integrated Consol software
Expected Result:
Actual Result
ACCEPTABLE
NOT ACCEPTABLE
Name:
Div:
Signature:
Date:
Name:
Div:
Signature:
Date:
Name:
Div:
Signature:
VERIFIED BY TM:
VERIFIED BY
SUPPLIER:

(February 2009)
Date:
Page : 99
Doc No:
Revision No: 2
Doc Title:
5.5 Force user logout
TEST OBJECTIVE:
PRE-REQUISITE:
To verify that the system can release/terminate

of active user
PROCEDURES
not available( only modify right for the active user . After the active user login out itself, login in
again ,the user have the new modified right)
Expected Result:
Actual Result
ACCEPTABLE
NOT ACCEPTABLE
Name:
Div:
Signature:
Date:
Name:
Div:
Signature:
Date:
Name:
Div:
Signature:
VERIFIED BY TM:
VERIFIED BY
SUPPLIER:

(February 2009)
Date:
Page : 100
Doc No:
Revision No: 2
Doc Title:
5.0 Security management
5.6 Modification of user profiles
TEST OBJECTIVE:
PRE-REQUISITE:
To verify that the EMS supports modification of

user profiles.
None
The user profile shall include the user ID, name,

telephone
number,
division,
address,
description, NE location controlled and customer
controlled.
PROCEDURES
3) Add, delete and modify the user information
4) The configured user login in

(February 2009)
Page : 101
Doc No:
Revision No: 2
Doc Title:
5.6 Modification of user profiles
Expected Result:
Actual Result
the information including: user ID, user name,

telephone no, security level .
ACCEPTABLE
NOT ACCEPTABLE
VERIFIED BY TM:
VERIFIED BY
SUPPLIER:
Name:
Div:
Signature:
Date:
Name:
Div:
Signature:
Date:
Name:
Div:
Signature:

(February 2009)
Date:
Page : 102
Doc No:
Revision No: 2
Doc Title:
5.7 Access right of users (function menu)
TEST OBJECTIVE:
PRE-REQUISITE:
To verify that the EMS supports user access

right in terms of function menu
None
PROCEDURES
3) Modify the user control right
4) Observe the user whether it control the equipment according to configuring right

(February 2009)
Page : 103
Doc No:
Revision No: 2
Doc Title:
5.7 Access right of users (function menu)
Expected Result:
Actual Result
The user right in terms of function menu will be

changed on Integrated Client.
ACCEPTABLE
NOT ACCEPTABLE
VERIFIED BY TM:
VERIFIED BY
SUPPLIER:
Name:
Div:
Signature:
Date:
Name:
Div:
Signature:
Date:
Name:
Div:
Signature:

(February 2009)
Date:
Page : 104
Doc No:
Revision No: 2
Doc Title:

(February 2009)
Page : 105
Doc No:
Revision No: 2
Doc Title:
5.8 Access right of users (geographical area of

interest)
TEST OBJECTIVE:
PRE-REQUISITE:
To verify that the EMS supports user access

right in terms of geographical area of interest
PROCEDURES
1) Open Integrated Client (run container.exe).
2) Open the page of NE of interest or detailed page of device of interest
3) Right click on it and select set it as favorite page on the popup menu
4) open Navigate window from toolbar, then select favorite page from list,
Expected Result:
Actual Result
Geographical area of interest could be set.
ACCEPTABLE
(February 2009)
Page : 106
Doc No:
Revision No: 2
Doc Title:
5.8 Access right of users (geographical area of

interest)
NOT ACCEPTABLE
Name:
Div:
Signature:
Date:
Name:
Div:
Signature:
Date:
Name:
Div:
Signature:
VERIFIED BY TM:
VERIFIED BY
SUPPLIER:

(February 2009)
Date:
Page : 107
Doc No:
Revision No: 2
Doc Title:
5.9 Audit Trail
TEST OBJECTIVE:
PRE-REQUISITE:
To verify that the EMS supports audit trail,

including the following items:
a) Date/ time
b) Activities -
Add/delete NE,
Enable/disable port
Add/delete user
Port configuration changes
User login/ logout
c) NE/ Port related to the activity

d) User name
e) Client / workstation entered
f) User command entered
PROCEDURES
1.Run report.exe, Open the Maintain Manage clip From Device Maintain clip
2. Query out the record according to the requirement

(February 2009)
Page : 108
Doc No:
Revision No: 2
Doc Title:
5.9 Audit Trail
Expected Result:
Actual Result
EMS supports audit trail.
ACCEPTABLE
NOT ACCEPTABLE
VERIFIED BY TM:
VERIFIED BY
SUPPLIER:
Name:
Div:
Signature:
Date:
Name:
Div:
Signature:
Date:
Name:
Div:
Signature:

(February 2009)
Date:
Page : 109
Doc No:
Revision No: 2
Doc Title:
5.10 Stress test
TEST OBJECTIVE:
PRE-REQUISITE:
To verify that the system can handle sudden

burst of information processing load (receiving
sudden flow maximum alarms at a very short
period of time) to the server and client software
None
PROCEDURES
1) Open the monitor subsystem at the EMS
2) Manually make any alarm for different NE at the same time
3) Observe whether the alarm have loss and error

(February 2009)
Page : 110
Doc No:
Revision No: 2
Doc Title:
5.10 Stress test
Expected Result:
Actual Result
No breakdown happen to EMS
ACCEPTABLE
NOT ACCEPTABLE
VERIFIED BY TM:
VERIFIED BY
SUPPLIER:
Name:
Div:
Signature:
Date:
Name:
Div:
Signature:
Date:
Name:
Div:
Signature:

(February 2009)
Date:
Page : 111
Doc No:
Revision No: 2
Doc Title:
6 SUMMARY OF EMS DC POWER SYSTEM TEST

(February 2009)
Page : 112
Doc No:
Revision No: 2
Doc Title:
No
Test Item
Description
1.
1.1
Database back-up
2.
1.2
Database restoration
3.
1.3
Data purging
4.
1.4
NE configuration backup/restore
5.
2.1.1
Monitor
temperature
6.
2.1.2
Monitor fan status
7.
2.1.3
Monitor humidity
8.
2.1.4
Monitor rectifier
9.
2.1.5
Monitor battery on
load
10.
2.2.1
Active alarm display at

EMS
11.
2.2.2
Historical
display at EMS
12.
2.2.3
Severity of alarms
13.
2.2.4
Alarm alert
14.
2.3.1
Acknowledgement
alarms

(February 2009)
Pass/Fail/Pending
rack
alarm
of
Page : 113
Doc No:
Revision No: 2
Doc Title:
No
Test Item
Description
15.
2.3.2
Inserting input on
acknowledgement
16.
2.3.3
Alarm filtering
17.
2.3.3
Alarm masking
18.
2.3.4
Polling time configuration
19.
2.3.5
Severity setting
20.
2.3.6
Alarm escalation
21.
2.4.1
Pass/Fail/Pending
Exporting of reports
22.
2.4.2
Creation of template reports
23.
2.4.3
Graphical representation of fault

management reports
24.
2.4.4
Statistical representation of fault

management reports
25.
2.4.5
Generation of fault/
occurrences report
event
26.
3.1.1
Scheduling of performance
management report
27.
3.2.1
Generation of
monitoring report
28.
3.2.2
Exporting of performance report
29.
3.2.3
Web based performance report


(February 2009)
performance
Page : 114
Doc No:
Revision No: 2
Doc Title:
30.
3.3.1
Creation, deletion and edition of

performance threshold
31.
3.4.1
Creation, deletion and edition of

performance report
32.
4.2.1
Display NE according to
graphical area
33.
4.3.1
Remote software upgrade
34.
4.4.1
Setting and changing managed

NE
35.
5.1
Assignment of users
36.
5.2
Creation, addition and deletion

of users
37.
5.3
Change password function
38.
5.4
Display of active user
39.
5.5
Force user logout
40.
5.6
Modification of user profiles
41.
5.7
Access right of users (function

menu)
42.
5.8
Access right of users

(geographical area of interest)
43.
5.9
Audit trail
44.
5.10
Stress test

(February 2009)
Page : 115
Doc No:
Revision No: 2
Doc Title:
TEST MEMBERS
No
Name
Designation
MOHD FALAAH ABD MANAP
ASSISTANT MANAGER
MOHD NASIR MUNAWIR
ASSISTANT MANAGER
A.HALIM SAMAD
ASSISTANT MANAGER
SYED ABDUL KADIR SYED MOHD
ASSISTANT MANAGER
KHAIRUL ANWAR LUKMAN
ASSISTANT MANAGER
SYAHRIL NIZAR MOHD NASIR
ASSISTANT MANAGER
7
8
9
10
11
12
13
14
15

(February 2009)
Page : 116
Doc No:
Revision No: 2
Doc Title:
AGREED BY TEST MEMBER
MOHD FALAAH ABD MANAP

ASSISTANT MANAGER
SYSTEM TECHNOLOGY
MOHD NASIR MUNAWIR

ASSISTANT MANAGER
TMFS
A.HALIM SAMAD
ASSOCIATE SENIOR RESEARCHER
TM R&D
SYED ABDUL KADIR SYED MOHD

ASSISTANT MANAGER
TMFS
KHAIRUL ANWAR LUKMAN

ASSISTANT MANAGER
ANOC
SYAHRIL NIZAR MOHD NASIR

ASSISTANT MANAGER
BSQM RNO

(February 2009)
Page : 117

Telekom Malaysia EMS DC Power System

Uploaded by

Copyright:

Available Formats

Telekom Malaysia EMS DC Power System

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Telekom Malaysia EMS DC Power System

Uploaded by

Copyright:

Available Formats

Doc No:

Mohd Falaah Abd Manap

Acceptance Test Protocol for EMS

SOFTWARE VERSION VERIFICATION..................................................................4

SUMMARY OF EMS DC POWER SYSTEM TEST..............................................101

AGREED BY TEST MEMBER.............................................................................105

Acceptance Test Protocol for EMS

Physical verification of all equipment

Software verification of all equipment

System tests, as outlined in the test requirement provided by Telekom

This ATP shall be applied to the following:

Acceptance Test Protocol for EMS

3 SOFTWARE VERSION VERIFICATION

Acceptance Test Protocol for EMS

Database back-up and

To verify that the system is able to auto-purge out of

To verify the system is able to backup the NE

Monitor rack temperature

To simulate the alarm and verify that the EMS is able

Monitor fan status

To verify that the EMS is able to monitor the fan status

To verify that the EMS is able to monitor the humidity

To verify that the EMS is able to monitor the rectifier

Monitor battery on load

To verify that the EMS is able to monitor the battery

Acceptance Test Protocol for EMS

Alarm display at EMS

Active alarm display at EMS

To simulate an alarm and verify that the alarm received at

NE location the area name in which the NE is

To simulate an alarm and verify that the alarm received at

Alarm location (specific location of alarm that has

g) NE location the area name in which the NE is

To verify that the EMS is able to distinguishly display the

Alarm/ event data handling

Acceptance Test Protocol for EMS

To verify that the

Acceptance Test Protocol for EMS

To verify that the EMS allows the operator to filter and

To verify that the EMS is able to mask or hide the

Polling time configuration

To verify that the EMS allows configuration of polling time

To verify that the EMS is able to modify the representation

To verify that the EMS is able to escalate alarms received

To verify that the operator is able to input remarks,

To verify that the EMS is able to export the reports to

Creation of template reports

To verify that the EMS is able to allow the operator to

To verify that the EMS is able to generate and print

To verify that the EMS is able to generate and print

To verify that the EMS is able to generate and print

Acceptance Test Protocol for EMS

To verify that the EMS is able to establish a schedule for

Creation, deletion and edition

Creation, deletion and edition

Acceptance Test Protocol for EMS

To verify that the EMS is able to export report to Excel

EMS software must have a topology which a few level.

To verify that EMS allows the operator to create, update