E - Guard USMS V1.67 Training Manual - IPowerConfig

ZTE E_guard USMS V1.
67 Training
Manual iPowerConfig
Objectives:
To understand the functions of ZTE E_guard USMS V1.67

iPowerConfig;
To understand the basic configuration of ZTE E_guard USMS

V1.67 iPowerConfig;
To comprehend the batch editing tool of ZTE E_guard USMS
V1.67 iPowerConfig;
To master authority settings of ZTE E_guard USMS V1.67

iPowerConfig;
Reference Manuals:
ZTE E_guard USMS Unified Site Management System V1.67
Operation Manual
Target Readers:
System maintenance personnel;
Engineering outsourcing personnel
Contents
Chapter 1 Overview........................................................................................................................1
1.1 Introduction............................................................................................................................1
1.2 Operating Principle................................................................................................................2
1.3 Installation Environment........................................................................................................3
1.3.1 Hardware Environment................................................................................................3
1.3.2 Software Environment..................................................................................................3
1.4 Glossaries..............................................................................................................................3
Chapter 2 Installation and Use......................................................................................................5
2.1 Installation.............................................................................................................................5
2.1.1 Installation Preparation................................................................................................5
2.1.2 Installation Steps..........................................................................................................5
2.2 Use of the iPowerConfig........................................................................................................8
2.2.1 Login.............................................................................................................................9
2.2.2 Site Configuration.......................................................................................................12
2.2.3 Batch Modifying..........................................................................................................23
2.2.4 Synchronizing Level 2 (LSC) and Level-3 (CSC) Supervision Center.......................23
2.2.5 Alarm Scheme............................................................................................................23
2.2.6 Adding User and Setting Authority.............................................................................23
2.2.7 Managing Basic Information.......................................................................................23
2.2.8 Video Integration Configuration Scheme...................................................................23
Chapter 1 Overview
Knowledge Points:
To introduce the functions of the iPowerConfig;
To briefly describe the operating environment of the iPowerConfig.
1.1 Introduction
The iPowerConfig software is a subsystem of E_guard USMS V1.67 system.
It is responsible for adding and configuring devices of NMS and field
supervision units, as well as authority settings of the entire system. It is the
core to ensure the normal running of the entire system.
The location of it in the entire system is as shown in Figure 1.1 -1
ZTE E_guard USMS V1.67 Training Manual - iPowerConfig
Figu
re 1.1-1
System Architecture
Chapter 1 Overview
1.2 Operating Principle

Through the operation of user, the iPowerConfig writes the actual site
configuration information at field into the database ZXM10_CFG. Each
node reads the added information from the iPowerConfig. They build a
perfect power environment supervision system together.
1.3 Installation Environment

1.3.1 Hardware Environment
Recommended configuration:
CPU main frequency: Pentium 4 CPU 3.00GHz
Memory: 1GB
Hard disk: 80GB
1.3.2 Software Environment

Operating system: Windows XP sp2 or later, Windows 2003 or later;
Software environment: .NET FrameWork2.0
vcredist_x86_CHS
1.4 Glossaries
System Template: refers to the database base template managed by the
company, which is saved in base database and must not be changed by the
field.
Field template: refers to the device template derived from the System
Template by user according to actual situation.
Chapter 2 Installation and Use

Knowledge Points:
To introduce the installation of iPowerConfig;
To introduce the operation and site configuration of iPowerConfig;
2.1 Installation
2.1.1 Installation Preparation
These programs must be already installed before installing the iPowerConfig
console: dotnet2fx, WindowsInstaller3.1, sqlncli_CHS, vcredist_x86_CHS.
2.1.2 Installation Steps

1.
Double-click ZXM10-iPowerConfig and click Nest.
Figure 2.1-2 Setup Wizard
2.
Select an installation path, click Next.
Figure 2.1-3 Select Installation Path
3.
Click Install to start installation.
Figure 2.1-4 Start Installation
4.
Click Finish to complete the installation.
Figure 2.1-5 Complete Installation
2.2 Use of the iPowerConfig

Before performing database configuration, we need to plan the networking,
IP, LSC ID, region, site/end office ID, and wiring diagram. Then we need to
carry out as per the following process:
1.
Import system template and make field template according to actual

demand;
2.
Add supervision network;
3.
Add network management equipment under supervision center:

SQL2005
database,
iNodeServer,
iPowerStore,
iPowerManager,
iPowerReport, Safeguard console, iPowerBackup, iPowerClient, and

iPowerScada, and add computer host and add its proper IP in
configuration variable.
4.
Add bus under front PC (image module should be added with safeguard
bus in the safeguard console);
5.
Add site;
6.
Add supervision unit;
7.
Add FSU detail: select scan bus and protocol DLL, etc;
8.
Configure supervision channel of supervision unit (EISU needs to

change the channel type, while MISU does not)
9.
Configure virtual expression of door contact, water sensor, mains off,

etc. For EISU, virtual expressions of temperature, voltage and other
channels can be configured by EISU configuration program. While
MISU cannot do this, these expressions need to be added on the
iPowerConfig console.
10. Add device: power equipment, environment device & access control
device, sensors, and audio/video device.
11. Configure four-level alarm scheme and storage scheme.
12. Configure tele-control enabling expression and control success
expression, such as, air-conditioning, turn-off, rectifier module on/off,
etc.
13. Configure site template and copy sites with same configurations.
2.2.1 Login
Click Start > Programs > ZTE E_guard USMS > iPowerConfig >
iPowerConfig or double-click iPowerConfig.exe under the installation
directory to start the iPowerConfig program. The Login window is as shown
in Figure 2.2 -6 .
Figure 2.2-6 Login Window
User Name: name of user added in iPowerConfig console, default is

admin;
Password: password of user when added, default is admin;
Before login the iPowerConfig console, please test database connection and
configure IP of iPowerAuthority Console.
2.2.1.1 Setting Database Connection
This is to set the database to be accessed.
10
Figure 2.2-7 Enter IP of Database Server
Server Name: IP address of server where the actual database is located,

127.0.0.1 for local;
Database Name: zxm10_cfg;
Login Name: default is sa;
Password: default is zxm10;
Click Test button to test the connection.
2.2.1.2 Setting Authority Connection
This is to set the IP of iPowerAuthority server.
11
Figure 2.2-8 Enter IP of iPowerAuthority Console
Enter IP address of the iPowerAuthority. If run in local machine, keep it as

127.0.0.1.
Click Test to test the connection.
2.2.2 Site Configuration

The following site information need to be configured in simulation at field:
Table 2.2-1 EISU Template Site

Supervi
Device
sion
Type
Device Name
Actual access
channel
Unit
Channel
configured
Remark
in
Bus
Information
NMS
Camera
Fixed
brick
To
camera
1#
channel of
encoder
EISU
Encoder
Standard 5016
Power
YD2010
COM2
equipme
nt
1#
\
intelligent
port
Gree
intelligent
COM3
air-conditioner
2 # intelligent
port
12
127.0.0.1,10
001

ZXDU68
COM4
switching power
3#
intelligent
Board channel
port
supply
Environ
Temperature
Channel 1
ment
equipme
1
Infrared sensor
Channel 9
nt
Board channel
9
Smoke sensor
Smoke
Board channel
Correlate
dedicated
13
a control
channel
channel
DO3
Door contact
Channel 10
Board channel
10
Water sensor
Channel 11
Board channel
11
Access
Access controller
Equipm
Door dedicated
Access port
channel
ent
Table 2.2-2 MISU Template Site

Supervisi
Device
on Unit
Type
Device Name
Actual
Channel
access
configured
channel
MISU
Camera
Fixed
brick
Remark
Bus
Information
in NMS
\
camera
To
2#
channel
of
encoder
Encoder
Standard
7#
5016
Power
YD2010
COM2
equipment
intelligent
port
Gree
13#
intelligent air-
intelligent
conditioner
port
ZXDU68
Environme
COM3
COM4
19#
switching
intelligent
power supply
port
Temperature
AI1
AI1
13
127.0.0.1,1231

nt
Infrared
DI1
DI1
equipment
sensor
Smoke sensor
DI2
DI2
Water sensor
DI3
DI3
Door contact
DI3
DI3
Correlate
a control
channel
DO1
Access
Access
Door
Access port
Equipment
controller
dedicated
channel
When configuring specific site information, please pay close attention to the
differences between configuring EISU and MISU.
2.2.2.1 Configure a Basic Site
2.2.2.1.1 Importing System Template
This is to import the system base data template made by R&D.
Figure 2.2-9 Import System Template
2.2.2.1.2 Making Field (Device) Template
14
This is to make field template which is used for database configuration.

Click Utility Management > Template Management Tool > Add Template
to open the Device Template interface, as shown in Figure 2.2 -11 ;
Figure 2.2-10 Click Add Template
Select the desired semaphore to make field template.
15
Figure 2.2-11 Device Template Window
Site level can be the default level selected by the system automatically.
2.2.2.1.1 Adding Supervision Network
This is to add a supervision network, i.e. LSC or CSC supervision center.
Configure Supervision Center > Center and Region List > Add
Supervision Center to open the Add Supervision Center dialog, as shown
in Figure 2.2 -12 .
16
Figure 2.2-12 Create Supervision Network
IsCSC: 1 for level-3 supervision center (CSC), 0 for level-2 supervision

center;
LSC ID: 1 for level-3 supervision network, any number between 2~64 for
level-2 supervision network;
LSC Name: the name of the supervision network to be created, use (region
+ supervision network) mode;
Click OK to confirm.
2.2.2.1.2 Adding Region
This is to add region information.
Click Supervision Center > Center and Region List > ** Supervision
network, click Add Region to open the Add Region dialog, as shown
in Figure 2.2 -13 .
17
Figure 2.2-13 Add Region
Add region information according to actual regions at field, mainly for

classification management and display of sites.
For example, if there are Nanshan, Luohu, and Futian in Shenzhen (LSC),
then add these three regions for convenient site management to Shenzhen
LSC.
Region ID: set ID of region, range from 1 ~254, ID under a same LSC
should be unique;
Region Name: name of the region;
Up Region ID: If region nested, select the superior region of it.
Note: When adding supervision center, the system adds the network
management equipments needed for building NMS system automatically.
2.2.2.1.3 Adding Other Network Management Equipments
This is to add network management equipments other than the default ones
added by the system automatically.
network > Supervision Center > Network Management Equipment, click
18
Add Network Management Equipment to open the Add NMS Device

dialog, as shown in Figure 2.2 -14 .
Figure 2.2-14 Add NMS Device
Add these NMS devices: iPowerClient, iPowerScada, Safeguard,

iPowerSync (only in V1.6 NMS level-3 networking), iPowerDiesel Adapter
and (Only when diesel generator scheduling system is used).
Device ID: generated by the system;
User Device ID: Not required;
Device Type: Type of NMS device;
Launch Time: generated by the system;
Device Module: select the template used by the device;
Device Name: Device name defined by user;
Host IP: Enter the IP address of the computer where the network
management software is installed.
19
After added, they are displayed as below
Figure 2.2-15 Network Management Equipments Added
Site Device is generated by the system automatically when adding site, do

not have to change it. The purpose is to manage the supervision center as a
device.
The Device ID at the left of each device is the basis of registration of node in
building NMS system.
Note
How many iPowerScadas and iPowerClients should be added depends on
the actual quantity.
2.2.2.1.4 Adding Computer Device

This is to add computers of the field.
network > Supervision Center > Computer, click Add Computer to open
the Add Computer Device dialog, as shown in Figure 2.2 -16 .
20
Figure 2.2-16 Add Computer Device
Device ID: generated by the system;

User Device ID: Not required;
Device Type: Type of computer device;
Launch Time: generated by the system;
Device Template: select the template used by the device;
Device Name: Device name defined by user;
Host IP: Enter the actual IP address of the computer host
Add all work stations and servers used in the NMS system, for monitoring
the operation conditions of them on the iPowerManager.
Note:
If computer host has dual NIC, here setting as 127.0.0.1 is OK.
21
2.2.2.1.5 Adding Bus Information

This is module scanning bus and door scan bus information.
Click Supervision Center > Center and Region List > **Supervision
network > Supervision Center > **iPowerScada, click Add Scan Bus to
open the Add Scan Bus dialog, as shown in Figure 2.2 -17 .
After adding all NMS devices, we need to add module scan bus and door
scan bus information (if access equipment exists) of iPowerScada. There
are two cases for configuring scan bus according to the manner of working
of iPowerScada.
iPowerScada serves as client;
iPowerScada serves as server.
Communication DLL for these two working modes are different and the bus
parameters are also different.
1. First of all, we introduce the scan bus configuration when iPowerScada
works as client.
Figure 2.2-17 iPowerScada as Client
Scan Bus Type: the type of bus, generally select common scan bus;
22
Scan Bus Name: name of scan bus;

Comm Param: parameters of scan bus;
Comm DLL: dynamic link library used by the bus scanning;
Scan Time: time internal of scanning information, just keep default value;
Enter scan bus name and click Generate Parameters to go to the
Configure Scan Bus Parameters window, as shown in Figure 2.2 -18 .
If use EISU, the port of scan bus is fixed as 12315; if use MISU, the port of
bus should be configured according to actual port assignment. Here we
support it is 3000.
Figure 2.2-18 Enter Scan Bus Parameters (use EISU)
IP Address: IP address of site;

Port: Port for bus communication;
Wait Time: waiting time for bus scanning;
Comm DLL: use NetScanClnt.dll when iPowerScada works as client;
The bus parameter configuration when using MISU is the same as EISU.
The steps of adding door scan bus information is the same as adding scan
bus information, except for port selection.
23
Figure 2.2-19 Add Door scan bus
The port of bus is the port number for access control communication. If use
EISU, default is 13215.
2. Second, we introduce the scan bus configuration when iPowerScada
works as server.
24
Figure 2.2-20 iPowerScada as Server
Comm Param: parameters of bus;
Configure Scan Bus Parameters window, click TCP Server tab, as shown
in Figure 2.2 -21 .
If use MISU, type in the MAC address of MISU in the MAC Address field.
25
Figure 2.2-21 Use MISU Supervision Unit
If use EISU, type in the global ID of EISU and go to EISU configuration

program.
Figure 2.2-22 Use EISU Supervision Unit
26
Figure 2.2-23 Enter Global ID
Select NetServerEISU.dll in Comm DLL for EISU and NetServer.dll for

MISU;
Meanwhile, we need to set the server IP of bottom supervision unit as the IP
of the iPowerScada where the site belongs to, as shown in Figure 2.2 -24 .
Figure 2.2-24 Enter Server (iPowerScada) IP
2.2.2.1.6 Adding Site Information

This is to add the information of site.
Click Site Device > Site List > **Supervision network > **iPowerScada,
click Add Site to open the Add Site dialog, as shown in Figure 2.2 -25 .
Enter site ID and site name, select site type, region, and networking mode,
and click OK to confirm.
27
Figure 2.2-25 Add Site
Site ID: the ID assigned when planning, must be unique under a same LSC,
under 8000.
Site Name: The name of the site to be added, use (region + site name);
Site Type: Select the type of site, for convenient of statistical management;
User Site ID: Not required;
Networking Mode: Select corresponding networking mode;
Region: Select the region where the site belongs to;
State: After site information is configured, a running state shall be selected.
2.2.2.1.7 Adding Supervision Unit
This is to add supervision unit, such as MISU, EISU, PMU, GSU, and BMU,
and to configure the supervision channels like name, virtual expression, etc.
of supervision unit.
Click Site Device > Site List > **Supervision network > **iPowerScada >
**Site > Supervision Unit, click Add Supervision Unit to open the Add
FSU dialog, as shown in Figure 2.2 -25 .
28
It is recommended to add supervision unit from system template, as shown

in Figure 2.2 -26 .
Figure 2.2-26 Add FSU (MISU)
The configuration of EISU is the same, except that the device type and
template are different. Select EISU, as shown in Figure 2.2 -27
Figure 2.2-27 Use EISU
Device Type: the type of supervision unit;

Device Template: the template used by the supervision unit;
Device Name: name of the supervision name;
After supervision unit is added, we need to associate the bus information for
supervision unit.
29
**Site > Supervision Unit > MISU > FSU Detail Info, click Add FSU Detail
Information to open the FSU Detail Info dialog, as shown in Figure 2.2
-28 .
Figure 2.2-28 FSU Detail Info
Scanbus ID: the bus used by the supervision unit;

Address: the DIP address of supervision unit, generally use 1;
Protocol DLL: protocol used by the supervision unit;
Different supervision units use different protocol DLLs. MISU uses
ParserMisu90.dll, and EISU uses ParserEISU.dll. The protocol DLLs used
by other supervision units are listed in Table 2.2 -3 .
Table 2.2-3 Protocol DLLs for Supervision Units

Protocol DLL
ParserEisu.dll
PaserGsu.dll
Description
EISU protocol parser DLL
GSU protocol parser DLL
30

PaserMisu90.dll
MISU protocol parser DLL
PaserPcu.dll
PCU protocol parser DLL
PaserDoor.dll
Door access protocol parser DLL
ProtocolEisu80.dll
ProtocolZXDU300V30.wso
ProtocolEisu.wso
Not used yet

Power protocol central parser DLL
EISU protocol central parser DLL
ProtocolMisu25.dll
Not used yet
ProtocolMisu44.dll
Not used yet
The method of configuring supervision channels of different supervision

units, like MISU and EISU, is different, as described as below:
Supervision unit is MISU
AI, DI, AO, and DO of MISU are not universal, they are configured as below:
(1).Configuring temperature virtual expression
MISU does not do preprocessing to telemeter data at the bottom, so
computed expression is required to be configured in NMS.
** Site > Supervision Unit > MISU > Channel, double-click the channel to
be modified.
Figure 2.2-29 Configure Temperature Computing Expression
The following items need to be configured:
31
Channel Type: select the proper data type of this channel;

Formula Type: select the formula type of the appropriate expression of this
channel;
Select 1 if calculating the variables of its own channels only. Click
Generate Expression to open the Formula Builder interface, as shown
in Figure 2.2 -30 .
Figure 2.2-30 Formula Builder
For specific slope and offset of expression, please set as per the actual
parameters of sensor.
After the temperature express is configured, the result is displayed as shown
in Figure 2.2 -31 .
32
Figure 2.2-31 Temperature Expression Added
Configuring expression for infrared sensor, vibration sensor, and water

sensor
For infrared, vibration, and water sensors, the original values need to be
negated to reflect the actual values. We take infrared sensor as an example
to introduce.
**Site > Supervision Unit > MISU > Channel, double-click the channel to
be modified.
Figure 2.2-32 Configure Infrared Computing Expression
33
Select the actually accessed tele-signal channel, and click Generate

Expression to open the Formula Builder.
Figure 2.2-33 Formula Builder
Figure 2.2-34 Infrared Expression Added
(3) Configuring smoke sensor reset

**Site > Supervision Unit > MISU > Channel, double-click the channel to
be modified.
34
Figure 2.2-35 Configure Smoke Sensor Reset

Channel Name: type in a name recognizable name, like smoke reset;
DO Output Type: select the appropriate output type of DO, smoke is pulse
output;
Channel Type: select the proper data type of this channel;
Pulse Width: set the width of pulse, smoke reset uses pulse type, with width
2000ms;
Formula Type: select the type of the appropriate expression of this channel;
Supervision unit is EISU

Channel 1-12 of EISU are universal, channel 13 is dedicated smoke
channel. They are configured as below:
(1).Configuring temperature
Temperature of EISU has been preprocessed at the bottom, so virtual
expression is not required to be configured in NMS. We only need to change
the name of the appropriate channel for easy management.
35
** Site > Supervision Unit > EISU > Channel, double-click the channel to
be modified.
Figure 2.2-36 Set Channel Name of Temperature
Configuring expression for infrared, vibration and water sensors

Basically it is similar to MISU, except for channel selection and the needs of
selecting channel type or EISU universal channels. We take infrared sensor
as an example to introduce.
**Site > Supervision Unit > EISU > Channel, double-click the channel to
be modified.
36
Figure 2.2-37 Configure Infrared Expression
Select the corresponding channel and change channel type to DI. The
generation of expression is same as that of MISU. Please pay attention to
the corresponding channel of the expression variable.
Figure 2.2-38 Results Displayed
(3) Configuring smoke sensor reset

**Site > Supervision Unit > EISU > Channel, double-click the channel to
be modified.
37
Figure 2.2-39 Configure Smoke Reset
2.2.2.1.8 Configuring Power Equipment

This is to add power device, like air-conditioner, rectifier and so on.
Use MISU
**Site > Power Device, click Add Power Device to open the Add Power
Device dialog, as shown in Figure 2.2 -40 .
38
Figure 2.2-40 Add Power Device
FSU Device ID: select the FSU, i.e. supervision unit that the device belongs
to.
MISU Device Index: select the intelligent index number of the device;
Device Type: select the type of the device;
The method of adding ZXDU68 power supply and Gree intelligent airconditioner is the same as adding YD2010, except for the device template.
ZXDU68 is a kind of rectifier power distribution equipment; Gree intelligent
air-conditioner is a kind of common air-conditioner equipment.
Use EISU
The method of configuration when using EISU is the same as the method
when using MISU. Just select EISU for FSU device ID and the EISU Device
Index is accumulated, which is different from MISU. Refer to configuration
table for details.
2.2.2.1.9 Configuring Environment Device
This is to add various environment devices like identification, environment,
and others.
Adding Device
39
**Site > Environment Device, click Add Environment Device to open the
Add Environment Device dialog, as shown in Figure 2.2 -41 .
Figure 2.2-41 Add ENV Device
Add environment device when using MISU is the same as that of EISU,
except for selecting FSU.
Environment device is not intelligent device, set 0 in MISU Device Index
field.
Correlating and changing corresponding variables
(1) Telemeter
This is to set the properties of telemeter.
**Site > Environment > Telemeter, double-click the channel to be modified.
40
Figure 2.2-42 Modify Telemeter
Monitoring Data Name: name of monitoring name, just keep the default;
FSU Device: the FSU device where the monitoring data belongs to,
generally keep it default.
Valid Upper Limit: the maximum value for valid monitoring data;
Valid Lower Limit: the minimum value for valid monitoring data;
FSU Channel ID: the monitoring points of this monitoring data of the
correlated supervision unit i.e. correlated supervision channel.
Precision: decimal places of the value of monitoring data;
Severity: the significance level of the monitoring data;
Limit Bandwidth: default;
Rangeability threshold: default;
Last Value: default.
Select the corresponding supervision channel of supervision unit and set
proper decimal places.
41
Figure 2.2-43 Set corresponding Telesignal of telemeter
The following item needs be configured:

Delay Time: the delay time for reporting alarm, set according to requirements
at field;
Click Alarm Mask Exception to set the mask expression for the
corresponding alarm of the telesignal.
42
Figure 2.2-44 Set Alarm Mask Expression for Telemeter
Click Validity Expression to set the validity expression of the telesignal.
43
Figure 2.2-45 Set Validity Expression for Telemeter
The above settings for telemeter must be configured according to actual

requirements at field.
For monitoring data not required can be deleted.
44
Figure 2.2-46 Delete Unnecessary Monitoring Data
Telesignal
**Site > Environment > Telesignal, double-click the channel to be modified.
45
Figure 2.2-47 Modify Telesignal

correlated supervision unit i.e. correlated supervision channel.
Generally, Alarm Mask and Other Info do not have to be configured, or
configure them as per actual situation.
Teleadjust
Teleadjust is not required for environment equipments.
Telecontrol
**Site > Environment > Telecontrol, double-click the channel to be
modified.
46
Figure 2.2-48 Set Smoke Sensor Reset
The following item needs to be configured:

correlated supervision unit, select the channel for smoke sensor reset.
2.2.2.1.10 Adding Door Device
This is to add door device and correlate it with appropriate door scan bus
information.
**Site > Door, click Add Door to open the Add Door Device dialog, as shown
in Figure 2.2 -49 .
47
Figure 2.2-49 Add Door Device
Correlate scan bus information for door device:

**Site > Door > FSU Detail Info, click Add FSU Detail Information to open
the FSU Detail Info dialog.
48
Figure 2.2-50 Correlate Door Scanbus
Select the scan bus corresponding to the site, and the protocol DLL
ParserDoor.dll and click OK.
2.2.2.1.11 Copy Site
This is to add site information quickly by setting template site and copying it.
Click Site Device > Site List > **Level-2 Supervision center >
**iPowerScada, right-click an already configured site and click Set as
Template to set the site a template site, as shown in below:
49
Figure 2.2-51 Set as Template
Right-click the template site with icon
, click Copy Site:
Figure 2.2-52 Copy Site
50
Right-click the iPowerScada into which the site will be added and select
Paste Site on the right-click menu:
Figure 2.2-53 Paste Site
The Copy Site dialog appears, as shown in Figure 2.2 -54
Figure 2.2-54 Copy Site Dialog
51
Site ID: the assigned number of site;

Site Name: the name of the site;
Region: select the region the site is located;
Scan Bus ID: correlate the scan bus that this site is using;
2.2.2.1.12 Changing Running State
This is to change the running state of site, so as to display the site on the
iPowerClient console.
To display the devices under a site on the iPowerClient console, the State of
the site must be changed to Running.
Click Site Device > Site List > **Level-2 Supervision center >
**iPowerScada, right-click and click Edit Site to open the Modify Site
dialog:
Figure 2.2-55 Change Running State
2.2.2.2 Configuring Image Acquisition Module

This is to use image acquisition module to acquire and store pictures from
site.
52
If image acquisition is required for site, the following configurations must be

conducted, there are two cases: MISU+PMU and EISU+ camera.
1. Use MISU+PMU:
PMU is used for supporting image acquisition.
Add safeguard image bus in safeguard console as follows:
Click Supervision Center > Center and Region List > **Supervision
Center > SafeGuard > ScanBus, click Add Scan Bus to open the Scan
Bus dialog, as shown in Figure 2.2 -56 .
Figure 2.2-56 Add Safeguard Scan Bus
Scan Bus Name: name of safeguard scan bus;

Bus Param: communication parameters of safeguard scan bus, generally
using IP + Port, for external port of low-end PMU, default is 12315.
It is not recommended to connect more than 500 picture manager units.
Add PMU device in supervision unit:
**Site > Supervision Unit, click Add Supervision Unit, as shown in Figure
2.2 -57 .
53
Figure 2.2-57 Add PMU Device
Correlate safeguard bus:

**Site > PMU > FSU Detail Info, click Add FSU Detail Information, as
shown in Figure 2.2 -58 .
54
Figure 2.2-58 Correlate Safeguard Bus
Bus ID: select the scan bus used by the PMU in transmitting picture;
MAC Address: MAC address of low-end PMU.
Add camera:
**Site > Video Device, click Add Video Device, as shown in Figure 2.2
-59 .
55
Figure 2.2-59 Add Camera
Select PMU in FSU Device ID field.

iPowerScada scan bus employs the mode of TCP server:
56
Figure 2.2-60 Connect Image +MISU
Comm Param: parameters of scan bus;
Configure Scan Bus Parameters window. Click TCP Server tab, enter the
MAC address of MISU.
57
Figure 2.2-61 Supervision Unit is MISU
2. EISU+ Camera
When EISU is used at the bottom, it is required to add safeguard bus,
safeguard EISU device, and camera.
The method of adding safeguard bus and camera is the same as that when
using MISU, except for selecting EISU Door instead of PMU. The port of
safeguard bus needs to be the one for low-end EISU security console
parameters. Default is 12615, as shown in Figure 2.2 -62 .
Figure 2.2-62 Set Security Console Port
Add safeguard EISU device as follows:

**Site >Supervision Unit, click Add Supervision Unit, as shown in Figure
2.2 -63 .
58
Figure 2.2-63 Add Safeguard EISU
Correlate safeguard bus:

EISU Door > FSU Detail Info, click Add FSU Detail Information, as shown
in Figure 2.2 -64 .
Figure 2.2-64 Correlate Safeguard Bus
59
Bus ID: select the scan bus used for communication of EISU Door;
Device Unique Address: the global unique number of the EISU door in this
site, as shown in Figure 2.2 -65
Figure 2.2-65 Set Global ID
Add camera:
**Site > Video Device, click Add Video Device, as shown in Figure 2.2
-66 .
Select EISU Door in FSU Device ID field.
2.2.3 Batch Modifying

2.2.3.1 Batch Modifying Monitoring Data
This is to set virtual expression of monitoring data by batch.
60
Click Utility management > Monitory Data Batch Modifying Tool:

If the expression for controlling rectifier on or off needs to be modified by
batch, we can do it as per the following steps:
Figure 2.2-67 Batch Modifying Telecontrol Expression
Select the site, and check the Successful Control Expression check box,
click Generate Expression to open the Generate Expression window, as
shown in Figure 2.2 -68 .
61
Figure 2.2-68 Generate Expression
Set the successful control expression:
62
Figure 2.2-69 Set Successful Control Expression
After complete settings, click OK.
63
Figure 2.2-70 Update
Batch modifying of other expressions is similar.

2.2.3.2 Batch Modifying Monitory Point
This is to set virtual expression of monitory point by batch.
Click Utility management > Batch Modify Monitory Point, the following
window appears:
The expression of mains supply failure needs to be modified by batch at
field, and whether the AI2 mains supply voltage is below 100V needs to be
judged through the DI channel 50 of MISU.
64
Figure 2.2-71 Set Mains Supply Failure Expression
Since mains supply failure is judged through the value of other channel, so it
is a level-2 formula.
Select Two-level formula and click Generate Expression to open the
Formula Builder window, as shown in Figure 2.2 -72 .
65
Figure 2.2-72 Set Mains Supply Failure Expression by Batch
After settings completed, click Update.
66
Figure 2.2-73 Update Mains Supply Failure Expression
2.2.4 Synchronizing Level 2 (LSC) and Level-3 (CSC) Supervision Center

2.2.4.1 Setting Database Connection Information
This is to synchronizing the data between level-2 and level-3 databases.
Click Utility Management > Database Synchronization Tool to go to the
synchronization main window; level-2 and 3 databases can be refreshed
mutually. Here is the data refresh from level-2 supervision center to level-3.
When building level-3 network, changes for level-2 center need to be
refreshed into level-3 center, as below:
Figure 2.2-74 Set Level-3 Database Information
67
Set correct level-3 database information and click Test to check if

connection is normal.
2.2.4.2 Synchronizing by System Difference
Figure 2.2-75 Refresh Level-2/3 Database by System Difference
When the first time refreshing level-2/3 database, only one change record is
displayed here, just click Import All.
2.2.4.3 Synchronizing by Customized
This is to synchronize the contents selected by users.
Click By Customized tab, select the contents to be synchronized, click
Import.
68
Figure 2.2-76 Refresh Level-2/3 Database by Customized
2.2.4.4 Synchronizing Basic Information

This is to synchronize some basic information, like four-level alarm scheme,
storage strategy, and so on.
Figure 2.2-77 Synchronize Basic Information
Click Basic Information tab, select the items to be synchronized and click
Synchronize button.
69
2.2.5 Alarm Scheme

2.2.5.1 Four-level Alarm Scheme
This is to change the scheme of how alarm is generated on the
iPowerScada.
Click Alarm and Storage Management > Four Level Alarm Scheme to go
to the alarm scheme main window:
Figure 2.2-78 Four-Level Alarm Scheme
Click Add to open the add four-level alarm scheme window.

When monitoring data is telemeter:
70
Figure 2.2-79 Add - Telemeter
Note:
1.
The currently added alarm scheme is under the selected supervision

center.
2.
Telemeter must be set up with upper and lower limits and the upper limit
must be greater than the lower limit. But it is unnecessary to set alarm
level. Telesignal, however, must be set up with alarm level, but upper &
lower limits are not necessary.
3.
When adding telemeter (the State Data Type is less than 1000.)
scheme, state data type, explanation value, alarm delay, alarm clear
delay, and Delta value must be set.
4.
Each monitoring data type can correspond with only one state type.
However, each state type can correspond with multiple state types.
5.
Alarm Delay, Alarm Clear Delay, and Delta can only be positive
number.
When monitoring data is telemeter:
71
Figure 2.2-80 Add - Telesignal
Note:
Double-click a data row or select it and click Modify to open a dialog box.
When Monitoring Type is tele-signal (above 1000), the dialog is as shown
in figure below:
72
Figure 2.2-81 Four Level Alarm Scheme Tele-signal
Click OK, the configured data is saved into database. When

Monitoring Type is telemeter (under 1000), alarm upper & lower
limits must be set, and the upper limit must be greater than alarm
lower limit.
73
Figure 2.2-82 Four Level Alarm Scheme Tele-meter
Click OK, the configured data is saved into database.

To delete, select one or more data rows, and click Delete, the
Warning dialog appears, as shown in Figure 2.2 -83 :
Figure 2.2-83 Warning
Click OK to delete the selected data, click Cancel to cancel.

2.2.5.2 Special Four Level Alarm Scheme
This is to set special alarm scheme to monitoring data in special situations.
Click Special Four Level Alarm Scheme tab, as shown in Figure 2.2 -84 :
74
Figure 2.2-84 Special Four Level Alarm Scheme
Select one data; click Edit to open the Detail of Special Four Level
Alarm Scheme window. When Monitoring Data Type is telesignal
(above 1000), the alarm severity level must be selected, as shown in
Figure 2.2 -85 :
Figure 2.2-85 Detail of Special Four Level Alarm Scheme
75
To delete, select one or more data rows, click Delete on the title bar,
the following Warning dialog will appears:
Figure 2.2-86 Warning
Click OK to delete the selected data, click Cancel to cancel.
2.2.6 Adding User and Setting Authority

This is to set the authority of user for login which node(s), region(s), and/or
what type(s) of device(s).
Note: User belongs to a user group and has the system function authority of
role.
2.2.6.1 Adding Department
This function is used to create a department for managing users.
Click User Management > User Authority Configuration Scheme >
Department > ** Supervision Network, click Add Department.
76
Figure 2.2-87 Add Department
2.2.6.2 Adding Role

This function is to create role and allocate system functions for the role.
Click User Management > User Authority Configuration Scheme > Role
> ** Supervision Network, click Add Role.
77
Figure 2.2-88 Add Role
Select the role that you added just now to assign appropriate authority
information to it, as below:
Figure 2.2-89 Configure Authority for Role
78
2.2.6.3 Adding User Group

This function is to add user group information.
Figure 2.2-90 Add User Group
2.2.6.4 Adding User

This is to add user information.
Click the user group to which you want to add user, click Add User
Information, input the user information according to actual situation and
assign a role for the user, click OK.
79
Figure 2.2-91
2.2.6.5 Adding Site and Device Monitoring Authority

This is to configure appropriate monitoring authority information over site(s)
and device(s) for user group.
Select the desired user group and configure special site authority, normal
site authority and device type authority for the group.
Figure 2.2-92 Configure Site and Device Authority
80
Special Site Authority: can be exactly the authority scheme of individual

site.
Normal Site Authority: Site authority scheme by site type and region.
Device Type Authority: Device monitority authority by device type.
2.2.7 Managing Basic Information

2.2.7.1 Adding/Modifying Site Type
This is to add/modify the type according to requirements of customer.
Click Basic Info Management > Site Type, click Add Site Type.
Figure 2.2-93 Add Site Type
Enter a site type and click OK.

2.2.7.2 Adding Site Level
This is to add/modify the level of site according to requirements of
customers.
Click Basic Info Management > Site Level, click Add Site Level.
81
Figure 2.2-94 Adding Site Level
Enter a site level name and click OK.

2.2.7.3 Modifying Alarm Color
This is to change the color of the four-level alarms displayed in the network
management system.
Click Basic Info Management > Alarm Severity, select the severity level to
be changed, double-click and change the color of it.
82
Figure 2.2-95 Change Color of Alarm Severity
2.2.8 Video Integration Configuration Scheme

In the video integration system, safeguard sub-system consists of safeguard
data center and safeguard client. Video Integration Configuration scheme of
iPowerConfig console is a tool for device configuration and data
synchronization in video integration. Therefore, the Video Integration
Configuration tool should have the following functions:
Adding, modifying, and deleting video related devices;
Updating video devices configuration of multimedia center unit I1000;
Correlating DI and devices
2.2.8.1 Preparation
Before running the Video Integration Configuration scheme, the following
preparation must be done:
1.
System templates of video devices, such as small platform system

template, encoder template, decoder template, camera template, etc.
have been applied successfully.
2.
The applied templates have been imported into database by using the
iPowerConfig. See Importing System Device Template for details.
83
3.
Field templates have been configured accordingly based on the

template management tool.
In the next sections, we mainly introduce the third step: how to make field
template for vide device and what should be paid attention.
2.2.8.1.1 Making Field Template for Small Platform Device
Small platform device is NMS device. Suppose system template of video
device has been applied successfully and has been imported into database.
Start the iPowerConfig console, click Utility Management > Template
Management Tool, select NMS > Small Platform Server in the Device
Template Tree, as shown in figure below:
Figure 2.2-96 Select Small Platform Server
Click Add Template open the Device Template dialog, as shown in figure
below:
84
Figure 2.2-97 Device Template
The left pane lists the system template(s) that you imported into database
using the iPowerConfig. Select one, and input a name for the field template,
and enter remarks, as shown in figure below:
Figure 2.2-98 Enter Field Template Name
Click OK, the field template of small platform device has been made.
85
Note: the five-teles (telemeter, telesignal, teleadjust, telecontrol, and

teleconfig), especially teleconfig must be selected and must not be missed
when making small platform field template. Default is all selected, do not
deselect them).
2.2.8.1.2 Making Field Template for Encoder
Encoder device is video device. So click Video Device > Encoder in the
Device Template Tree, as shown in figure below:
Figure 2.2-99 Select Encoder
Click Add Template to open the dialog. Select the system template to be
used from the left pane, type in the name of the field template and input
remark. Select DI and DO in Telesignal and Teleadjust. Click OK, the
encoder field template has been made.
2.2.8.1.3 Making Field Template for Decoder
The steps for making decoder field template is the similar to encoder.
Note: all configuration variables must be selected when making decoder field
template.
2.2.8.1.4 Making Field Template for Camera
The steps for making camera field template are the similar to encoder.
86
Note: all configuration variables must be selected when making camera field
template.
2.2.8.2 Video Device Management Module
2.2.8.2.1 Configuring Small Platform Device
A small platform server must be configured first before using video
integration system. In NMS system, small platform server device is NMS
equipment. So configuring small platform server is the same as configuring
other NMS equipments, such as, iPowerClient, safeguard console, etc., Start
the iPowerConfig and click Supervision Center > Network Management
Equipment > Add Network Management Equipment to open the Add
NMS Device dialog, as shown in figure below:
Figure 2.2-100 Add NMS Device
Enter proper information and click OK, a small platform server has been
added.
To modify small platform record, select the small platform record in
supervision center and click Modify to open the dialog and change it.
To delete small platform record, select the small platform record in
supervision center and click Delete to delete it.
87
Then we need to configure correct IP address, port number, user name, and
password for the small platform. If not configure these, error may occur
when synchronizing data into video server.
First of all, select the small platform that we just added from the supervision
center node, and click Teleconfig from the right part of the window, as
shown in figure below:
Figure 2.2-101 Teleconfig
We can see that there are 4 rows in the Teleconfig list; they are IP address,
port, user Name and password. Given that these information of the small
platform server are 10.72.13.30, 8000, admin, and 888888 respectively,
Now we need to change these items to the correct ones. First, double-click
the IP Address row to open the Modify Teleconfig dialog and input correct
address, as shown in figure below:
88
Figure 2.2-102 Modify Teleconfig
Click OK to confirm. Then we need to repeat the above steps to change the
port, user name and password.
Click Utility Management> Video Integration Configuration Tool to check
the small platform devices under the current supervision center, as shown in
figure below:
Figure 2.2-103 Check the Configured Small Platform Device
We can see that the small platform device we added just now is displayed in
the Device List.
89
2.2.8.2.2 Configuring Encoder

After small platform server is configured, we need to configure video
devices.
First of all, we need to configure an encoder device. Click Platform tab at
the bottom left corner of the window, click a small platform node, click
Encoder tab on the right, and click Add Encoder to open the Select Site
dialog, as shown in figure below. This dialog will not appear if add encoder
or decoder in Site Type or Region tab.
Figure 2.2-104 Select Site
Select a site and click OK to open the Add Encoder dialog, as shown in
figure below:
90
Figure 2.2-105 Add Encoder
Input relevant information and click OK to confirm.

To modify encoder record, select the encoder record to be changed and click
Modify to open the dialog and change it.
To delete encoder record, select the encoder record that you want to delete
and click Delete to delete it.
2.2.8.2.3 Configuring Camera
After encoder is configured, if camera is required to be configured under the
encoder, select the encoder device under which that you want to configure
camera, click Add Camera to open the Add Camera dialog and enter
appropriate values, as shown in figure below:
91
Note: Access Channel cannot be repeated under a same encoder. For

example, if a camera is configured with Access Channel 1, then other
cameras cannot be configured as 1 any more.
Click OK to confirm:
To modify camera record, select the camera record to be changed and click
To delete camera record, select the camera record that you want to delete
2.2.8.2.4 Configuring Decoder
After small platform server is configured, if decoder device is required to be
configured, select the small platform device node under which that you want
configure decoder, click Decoder tab on the right, click Add Decoder to
open the Select Site dialog, as shown in figure below:
92
Figure 2.2-107 Select Site
Click OK to open the Add Decoder dialog, as shown in figure below:
Figure 2.2-108 Add Decoder
Click OK, the decoder just added can be seen in the right list, as shown in
figure below:
93
To modify decoder record, select the decoder record to be changed and click
To delete decoder record, select the decoder record that you want to delete
2.2.8.3 Correlating DI and Camera
This function is to correlate DI and cameras within the same site. One DI can
be correlated with more than one camera. Select the DI under a device, for
example, DI under an encoder, as shown in figure below:
Figure 2.2-109 Select DI
Double-click the record to open the Modify Telesignal dialog, as shown in

figure below:
94
Figure 2.2-110 Modify Telesignal
Click Alarm Linkage tab, as shown in figure below:
Figure 2.2-111 Alarm Linkage
95
Double-click the camera to be linked, the Default Position column of this

camera can be edited, input a legal number (positive integer from 0 to 255),
as shown in figure below:
Figure 2.2-112 Set Default Position
Move the mouse cursor away and click OK, the value of the camera which is
to be linked to the DI is set. Open it again; it is displayed as shown in figure
below:
Figure 2.2-113 DI Linked
If the check box is checked, it means the corresponding DI is linked with the
camera.
96
To change the value of camera linked to DI, double-click it and change the
value, then click OK to confirm. To delete the value, deselect the check box
before DI, and click OK to confirm.
2.2.8.4 Video Device Synchronization Module
Video device synchronization module is mainly used to synchronize the
video devices configured in NMS into video small platform server. There are
two main synchronization methods. One method is to synchronize by
platform, that is, synchronize devices of platform into video database by
whole. The other method is to synchronize based on difference. This method
is similar to differential synchronization function in Level-2/3 synchronization
tool in NMS.
Note: when using the video device synchronization module, the IP address,
port number, user name and password of small platform must be ensured
correct. Otherwise, error may occur. Refer to Configuring Small Platform
Device for configuring small platform.
2.2.8.4.1 Platform Synchronization
This is to synchronize devices at NMS into video database by whole. To do
this, delete devices at video side first, then synchronize all the devices at
NMS to the video side.
Select a small platform device, right-click
Synchronization, as shown in figure below:
97
and
select
Platform
Figure 2.2-114 Platform Synchronization
The process bar appears, as shown in figure below:
Figure 2.2-115 Process of Synchronization
If synchronization failed, relevant error message will appear.

2.2.8.4.2 Synchronization Based on Difference
This is to synchronize the changes on devices at the NMS side into video
server. The main window is as shown in figure below:
98
Figure 2.2-116 Synchronization based on Difference
Select the small platform to be synchronized, click OK, the lower part of the
window lists the different data records; select the record(s) to be
synchronized from the list, as shown in figure below. It is recommended to
test the connection of the small platform by selecting the platform from the
video device management module and clicking Test.
99
Figure 2.2-117 Select Items to be Synchronized
Click Synchronization, the system starts synchronizing the selected data,

as shown in figure below:
100
Figure 2.2-118 Synchronization is Process
There is a progress bar at the bottom of the window. Operation Status

column tells you whether the data is synchronized successfully. If yes, it
displays in green. If no, it displays in red.
2.2.8.5 Other Functions
2.2.8.5.1 Copying Video Device ID
This function is to convert device ID of NMS device into that of video device
and save in memory. As shown in figure below, select video device, rightclick and select Copy Video Device ID. This function only works with video
device, encoder, decoder, and camera.
101
Figure 2.2-119 Copy Video Device ID
Click Quick Start at the right part of the window, select Notepad, right-click
and select Paste to paste the video device ID, as shown in figure below:
Figure 2.2-120 Video Device ID Copied
2.2.8.5.2 Copying Site ID

This function is similar to Copying Video Device ID. The only difference is
that this is to copy the site ID of video device.
102
2.2.8.5.3 Topological Graph

This is to display the topological structure of video devices in graph. At
present, only encoders are displayed in the graph.
Select an encoder in the Device List, right-click and select Topological
Graph, as shown in figure below:
represents encoder device, and
represents decoder device.
Figure 2.2-121 Select Topological Graph
The following window which shows the topological graph of video devices
appears:
103
Figure 2.2-122 Topological Graph of Video Devices
Click the down arrow at the upper right corner of the window to adjust
the size of the graph.
2.2.8.5.4 Testing Small Platform Connection
This is mainly to test the connection of small platform. It is available only
when small platform node is selected.
Configure correct user name, password, port, and IP address for the small
platform device, click the small platform node, right-click and select Test
Platform Connection, as shown in figure below:
104
Figure 2.2-123 Test Platform Connection
If connection is made successfully, the following Prompt box appears:
Figure 2.2-124 Successful Connection
If small platform device configuration (IP address, port, user name and
password) is not correct or the small platform server itself is not connected,
the following Prompt box will appear:
105
Figure 2.2-125 Connection Failure
It means that the current small platform server is disconnected.
106
Appendix A Abbreviations
Abbreviations
Full Name
CMU
Control Monitor Unit
CSC
Centralized Supervision Center
EMU
Environment Monitor Unit
MISU
Multiple Integrative Supervision Unit
ODBC
Open Database Connectivity
PC
Personal Computer
SC
Supervision Center
SM
Supervision Module
SU
Supervision Unit
TCP
Transfer Control Protocol
107

E - Guard USMS V1.67 Training Manual - IPowerConfig

Enviado por

Dados do documento

Título original

Direitos autorais

Formatos disponíveis

Compartilhar este documento

Compartilhar ou incorporar documento

Opções de compartilhamento

Você considera este documento útil?

Este conteúdo é inapropriado?

Direitos autorais:

Formatos disponíveis

E - Guard USMS V1.67 Training Manual - IPowerConfig

Enviado por

Direitos autorais:

Formatos disponíveis

ZTE E_guard USMS V1.

To understand the functions of ZTE E_guard USMS V1.67

To understand the basic configuration of ZTE E_guard USMS

To master authority settings of ZTE E_guard USMS V1.67

System maintenance personnel;

Engineering outsourcing personnel

ZTE E_guard USMS V1.67 Training Manual - iPowerConfig

1.2 Operating Principle

1.3 Installation Environment

1.3.2 Software Environment

Chapter 2 Installation and Use

2.1.2 Installation Steps

Double-click ZXM10-iPowerConfig and click Nest.

Figure 2.1-2 Setup Wizard

ZTE E_guard USMS V1.67 Training Manual - iPowerConfig

Select an installation path, click Next.

Figure 2.1-3 Select Installation Path

Click Install to start installation.

Chapter 2 Installation and Use

Figure 2.1-4 Start Installation

Click Finish to complete the installation.

ZTE E_guard USMS V1.67 Training Manual - iPowerConfig

Figure 2.1-5 Complete Installation

2.2 Use of the iPowerConfig

Import system template and make field template according to actual

Add supervision network;

Add network management equipment under supervision center:

iPowerReport, Safeguard console, iPowerBackup, iPowerClient, and

Chapter 2 Installation and Use

Add supervision unit;

Configure supervision channel of supervision unit (EISU needs to

Configure virtual expression of door contact, water sensor, mains off,

ZTE E_guard USMS V1.67 Training Manual - iPowerConfig

Figure 2.2-6 Login Window

User Name: name of user added in iPowerConfig console, default is

Chapter 2 Installation and Use

Figure 2.2-7 Enter IP of Database Server

Server Name: IP address of server where the actual database is located,

ZTE E_guard USMS V1.67 Training Manual - iPowerConfig

Figure 2.2-8 Enter IP of iPowerAuthority Console

Enter IP address of the iPowerAuthority. If run in local machine, keep it as

2.2.2 Site Configuration

Table 2.2-1 EISU Template Site

Chapter 2 Installation and Use

Table 2.2-2 MISU Template Site

ZTE E_guard USMS V1.67 Training Manual - iPowerConfig

Figure 2.2-9 Import System Template

2.2.2.1.2 Making Field (Device) Template

Chapter 2 Installation and Use

This is to make field template which is used for database configuration.

Figure 2.2-10 Click Add Template

Select the desired semaphore to make field template.

ZTE E_guard USMS V1.67 Training Manual - iPowerConfig

Figure 2.2-11 Device Template Window

Chapter 2 Installation and Use

Figure 2.2-12 Create Supervision Network

IsCSC: 1 for level-3 supervision center (CSC), 0 for level-2 supervision

ZTE E_guard USMS V1.67 Training Manual - iPowerConfig

Figure 2.2-13 Add Region

Add region information according to actual regions at field, mainly for

Chapter 2 Installation and Use

Add Network Management Equipment to open the Add NMS Device

Figure 2.2-14 Add NMS Device