B T E C O R P O R A T I O N

loyalsockvillemobΔίκτυα και Επικοινωνίες

27 Οκτ 2013 (πριν από 4 χρόνια και 17 μέρες)

134 εμφανίσεις




3 5 MA P L E P L A CE,

HUNTI NG TO N
, NY 1 1 7 4 3
US A

P HONE: 6 3 1
-
6 7 3
-
8 3 3 9,

FA X: 6 3 1
-
6 7 3
-
8 1 8 6

I NTERNET: WWW.BTECEN
TR A L.C OM

E
-
MA I L: S UP P ORT@BTECEN
TRA L
.CO M

NTMC Specification


Page
1

NTMC
®

2005
Specification




1

Contents


1

CONTENTS
................................
................................
................................
................................
..........................

1

2

REVISIONS
................................
................................
................................
................................
..........................

3

3

INTRODUCT
ION

................................
................................
................................
................................
..............

3

4

PLATFORM
................................
................................
................................
................................
.........................

4

5

ARCHITECTURE
................................
................................
................................
................................
..............

4

5.1

C
LIENT
/

S
ERVER
M
ODEL
................................
................................
................................
...........................

4

5.2

S
YSTEM
M
ODULARITY

................................
................................
................................
...............................

5

5.3

S
OFTWARE
D
ESIGN

................................
................................
................................
................................
.....

6

6

APPLICATIONS

................................
................................
................................
................................
................

6

6.1

SCADA

................................
................................
................................
................................
........................

6

6.2

L
OAD
M
ANAGEMENT
................................
................................
................................
................................
..

6

6.3

C
APACITOR
C
ONTROL

................................
................................
................................
................................

7

6.4

AMR

................................
................................
................................
................................
.............................

7

6.5

R
EMOTE
A
CCESS AND
N
OTIFICATION

................................
................................
................................
......

7

7

SHARED SERVICES

................................
................................
................................
................................
........

7

7.1

D
ATABASE
M
ANAGEMENT

................................
................................
................................
........................

7

7.2

E
VENT
L
OGGING

................................
................................
................................
................................
.........

8

7.3

S
ECURITY

................................
................................
................................
................................
.....................

8

7.3.1

User Groups

................................
................................
................................
................................
...........

9

7.3.2

Users
................................
................................
................................
................................
........................

9

7.4

D
ATA
R
ECORDING
................................
................................
................................
................................
.......

9

8

CORE COMPONENTS

................................
................................
................................
................................
..
10

8.1

M
ASTER
C
ONTROLLER
E
XECUTIVE
(MCEX)

................................
................................
.......................

10

8.1.1

System Star
tup / Shutdown

................................
................................
................................
................
10

8.1.2

System Component Monitoring
................................
................................
................................
.........
11

8.2

I
NPUT
/

O
UTPUT
E
XECUTIVE
(IOEX)

................................
................................
................................
.....

11

8.2.1

Physical Layer

................................
................................
................................
................................
.....
11

8.2.1.1

Serial (RS 232 and RS 485)
................................
................................
................................
....

13

8.2.1.2

Ethernet

................................
................................
................................
................................
......

14

8.2.2

Application Layer / Protocols

................................
................................
................................
...........
15

8.2.2.1

COM/DCOM
................................
................................
................................
...............................

17

8.2.2.2

Web Services
................................
................................
................................
.............................

17

8.2.2.3

DNP 3.0

................................
................................
................................
................................
......

17




3 5 MA P L E P L A CE,

HUNTI NG TO N
, NY 1 1 7 4 3
US A

P HONE: 6 3 1
-
6 7 3
-
8 3 3 9,

FA X: 6 3 1
-
6 7 3
-
8 1 8 6

I NTERNET: WWW.BTECEN
TR A L.C OM

E
-
MA I L: S UP P ORT@BTECEN
TRA L
.CO M

NTMC Specification


Page
2

8.2.2.4

MODBUS
................................
................................
................................
................................
....

19

8.2.2.5

Comverge

................................
................................
................................
................................
...

19

8.2.2.6

Telescada

................................
................................
................................
................................
...

20

8.2.2.7

BTE
................................
................................
................................
................................
..............

20

8.2.2.8

NPPD

................................
................................
................................
................................
..........

20

8.3

R
EMOTE
U
NIT
E
XECUTIVE
(RUEX)
................................
................................
................................
.......

21

8.3.1

Component Architecture

................................
................................
................................
....................
21

8.3.2

Domain
s

................................
................................
................................
................................
................
23

8.3.3

Remote Units

................................
................................
................................
................................
........
25

8.3.4

I/O (Data) Points
................................
................................
................................
................................
.
34

8.3.4.1

An
alog Points
................................
................................
................................
.............................

35

8.3.4.2

Counters

................................
................................
................................
................................
.....

35

8.3.4.3

Status Points
................................
................................
................................
..............................

35

8.3.
4.4

Control Points

................................
................................
................................
............................

35

8.3.4.4.1

Latching Control Points
................................
................................
................................
.......

35

8.3.4.4.2

Timed Control Points
................................
................................
................................
...........

35

8.3.4.4.3

Momentary Control Points
................................
................................
................................
..

36

8.3.4.5

I/O Point Parameters

................................
................................
................................
................

36

8.3.5

One Line Diagrams
................................
................................
................................
.............................
43

8.3.5.1

Display Panels

................................
................................
................................
...........................

43

8.3.5.2

Display Elements

................................
................................
................................
......................

44

8.3.6

Data P
rocessing (Evaluators)
................................
................................
................................
...........
51

8.3.7

Communication Routing

................................
................................
................................
....................
52

8.3.8

Remote Unit Polling

................................
................................
................................
...........................
52

8.3.9

Timed Switch Management
................................
................................
................................
................
54

8.3.10

Control Code Dispatching

................................
................................
................................
...........
54

8.3.11

Data Downloads

................................
................................
................................
............................
55

8.3.12

System Backup

................................
................................
................................
................................
55

8.3.13

External Commands

................................
................................
................................
......................
55

8.4

M
ASTER
C
ONTROLLER
E
DI
TOR
(MCED)

................................
................................
..............................

56

8.5

M
ASTER
C
ONTROLLER
E
VENT
V
IEWER
(MCEV)

................................
................................
................

56

8.6

M
ASTER
C
ONTROLLER
S
ECURITY
A
DMINISTRATOR
(MCSA)

................................
...........................

57

8.7

M
ASTER
C
ONTROLLER
D
ATA
A
NALYZER
(MCDA)
................................
................................
............

57

8.7.1

Data Tables

................................
................................
................................
................................
..........
59

8.7.2

Graph
s
................................
................................
................................
................................
...................
60

8.7.3

Reports

................................
................................
................................
................................
..................
60

9

APPLICATION MODULES

................................
................................
................................
.........................
60

9.1

L
OAD
M
ANAGEME
NT
E
XECUTIVE
(LMEX)
................................
................................
..........................

60

9.1.1

Component Architecture

................................
................................
................................
....................
61

9.1.2

Global Parameters
................................
................................
................................
..............................
61

9.1.3

Metering Points

................................
................................
................................
................................
...
66

9.1.4

Demand Inputs
................................
................................
................................
................................
.....
68

9.1.5

Load Points

................................
................................
................................
................................
..........
70

9.1.6

Schedules

................................
................................
................................
................................
..............
72

9.1.7

Management Algorithms

................................
................................
................................
....................
74

9.1.7.1

Peak Shaving
................................
................................
................................
.............................

74

9.1.7.1.1

One
-
Way Load Management
................................
................................
.............................

74

9.1.7.1.2

Two
-
Way Load Management
................................
................................
.............................

76

9.1.7.1.3

Acti ve Cycl
e Demand Correction

................................
................................
......................

77




3 5 MA P L E P L A CE,

HUNTI NG TO N
, NY 1 1 7 4 3
US A

P HONE: 6 3 1
-
6 7 3
-
8 3 3 9,

FA X: 6 3 1
-
6 7 3
-
8 1 8 6

I NTERNET: WWW.BTECEN
TR A L.C OM

E
-
MA I L: S UP P ORT@BTECEN
TRA L
.CO M

NTMC Specification


Page
3

9.1.7.2

Load Rotation

................................
................................
................................
............................

78

9.1.7.3

Load State Reinserting
................................
................................
................................
.............

78

9.1.7.4

Strategy Management

................................
................................
................................
..............

80

9.2

C
APACITOR
C
ONTROL
E
XECUTIVE
(CCEX)

................................
................................
.........................

80

9.2.1

Component Architecture

................................
................................
................................
....................
81

9.2.2

Global Parameters
................................
................................
................................
..............................
81

9.2.3

Substations

................................
................................
................................
................................
...........
84

9.2.4

Feeders
................................
................................
................................
................................
..................
85

9.2.5

Capacitors

................................
................................
................................
................................
............
87

9.2.6

Schedules

................................
................................
................................
................................
..............
88

9.2.7

Management Algorithms

................................
................................
................................
....................
89

9.2.7.1

Control Parameter Management

................................
................................
................................
..

89

9.2.7.2

Capacitor Bank State Reinserting

................................
................................
................................

90

9.3

M
ETER
R
EADING
E
XECUTIVE
(MREX)

................................
................................
................................
.

90

9.3.1

Component Architecture

................................
................................
................................
....................
91

9.3.2

Global Parameters
................................
................................
................................
..............................
91

9.3.3

Meters
................................
................................
................................
................................
....................
93

9.3.4

Monthly Schedules

................................
................................
................................
..............................
95

9.3.5

Daily Schedules

................................
................................
................................
................................
...
95

9.3.6

Input Data Types

................................
................................
................................
................................
.
96

9.3.6.1

KYZ Pulses

................................
................................
................................
................................
..

97

9.3.6.2

Dial Readings
................................
................................
................................
...............................

97

9.3.7

Types of Meter Reading

................................
................................
................................
.....................
97

9.3.7.1

Meter Calibration
................................
................................
................................
.........................

97

9.3.7.2

Latest Reading

................................
................................
................................
.............................

97

9.3.7.3

Billing Reads

................................
................................
................................
...............................

98

9.3.7.4

Data Downloads
................................
................................
................................
...........................

98

9.3.8

Billing Data Exports

................................
................................
................................
...........................
98

9.4

R
EMOTE
C
LIENT

................................
................................
................................
................................
........

98

9.5

W
EB
L
INK
................................
................................
................................
................................
....................

99

9.5.1

Functions

................................
................................
................................
................................
..............
99

9.5.1.1

Publishing of Objects on the Web

................................
................................
..........................

99

9.5.1.2

Access to NTMC via the Web

................................
................................
................................
.

99

9.5.1.3

NTMC Event Notifications
................................
................................
................................
........

99

9.5.1.4

Programmatic Access to NTMC

................................
................................
...........................

100

9.5.2

Architecture
................................
................................
................................
................................
.......

100

9.5.3

Security

................................
................................
................................
................................
..............

102

9.5.4

Configuration Parameters

................................
................................
................................
..............

102


2

Revisions


2005.1
1
-

Peter Battelino
, BTE Corporation
, September 2
9
, 2005.


3

Introduction





3 5 MA P L E P L A CE,

HUNTI NG TO N
, NY 1 1 7 4 3
US A

P HONE: 6 3 1
-
6 7 3
-
8 3 3 9,

FA X: 6 3 1
-
6 7 3
-
8 1 8 6

I NTERNET: WWW.BTECEN
TR A L.C OM

E
-
MA I L: S UP P ORT@BTECEN
TRA L
.CO M

NTMC Specification


Page
4

NTMC
®
2005 (from here on NTMC) i
s a master controller software suite
used to
automate and optimize electric energy distribution. It is intended
for use
primarily
by




S
maller
electric

utility companies wishing to do SCADA, load
management, capacitor control, and / or AMR;



By all electric utility companies wishing to do substation monitoring and
control, using NTMC as a data concentrator communicating with
larger,
higher level SCADA sys
tems


This document gives a broad outline of NTMC architecture, capabilities and
functionality.


4

Platform


NTMC

runs on IBM PC compatible computers running Microsoft Windows XP /
2000 Professional operating systems.
Minimum recommended system
requirements:




Intel Pentium 4 (or equivalent) processor



256 MB of RAM



I GB of hard disk space



19”
high resolution monitor


These are minimum requirements


actual systems usually include higher
capacity machine, another computer as a backup target, and a UPS.


5

Archite
cture


5.1

Client / Server

Model


All NTMC components are structured to
us
e
the so called
client / server m
odel as
shown below.





3 5 MA P L E P L A CE,

HUNTI NG TO N
, NY 1 1 7 4 3
US A

P HONE: 6 3 1
-
6 7 3
-
8 3 3 9,

FA X: 6 3 1
-
6 7 3
-
8 1 8 6

I NTERNET: WWW.BTECEN
TR A L.C OM

E
-
MA I L: S UP P ORT@BTECEN
TRA L
.CO M

NTMC Specification


Page
5




The client / server pair shown on the right is meant to represent a component
running on one machine

located in the control room. The additional client on the
left is meant to represent any other user of the system located anywhere else, be
it in the next office, at home, or anywhere else in the world.


5.2

System Modularity


NTMC
is modular


it
consists of

core components

and
application specific
modules
.
The core components perform all basic SCADA functions
. They also
serve as an operating system for higher level application specific modules.




SERVER

CLIENT

CLIENT

CORE

MODULE

MODULE




3 5 MA P L E P L A CE,

HUNTI NG TO N
, NY 1 1 7 4 3
US A

P HONE: 6 3 1
-
6 7 3
-
8 3 3 9,

FA X: 6 3 1
-
6 7 3
-
8 1 8 6

I NTERNET: WWW.BTECEN
TR A L.C OM

E
-
MA I L: S UP P ORT@BTECEN
TRA L
.CO M

NTMC Specification


Page
6

Apart from reducing complexity of

each component, this architecture also
simplifies overall product maintenance and further development.


5.3

Software Design


The Object Oriented Paradigm
(OOP) is

used throughout

the source code. The
latter
is

written
and maintained
using




T
he latest technolo
gy
programming languages
:

o

C#

o

C++



The latest
Microsoft
software development

tools and technologies:

o

Visual Studio
.Net

o

.Net Framework

o

.Net Web Services

o

Asp.Net

o

COM/DCOM


Source code
revision control and documentation are
maintained
at all times.



6

Applicat
ions


At the highest level NTMC provides the following functions:


6.1

SCADA


SCADA
f
unctions are performed by the core component

Remote Unit Executive
(RUEX


see Section
8.3
).


6.2

Load Management


Load management fun
ctions are performed by the application module Load
Management Executive (LMEX


see Section
9.1
).





3 5 MA P L E P L A CE,

HUNTI NG TO N
, NY 1 1 7 4 3
US A

P HONE: 6 3 1
-
6 7 3
-
8 3 3 9,

FA X: 6 3 1
-
6 7 3
-
8 1 8 6

I NTERNET: WWW.BTECEN
TR A L.C OM

E
-
MA I L: S UP P ORT@BTECEN
TRA L
.CO M

NTMC Specification


Page
7

6.3

Capacitor Control


Capacitor control

functions are performed by the application module
Capacitor

Control

Execut
ive (
CC
EX


see Section

9.2
).


6.4

AMR


Automated meter reading
functions are performed by the application module
Meter Reading

Executive (
MR
EX


see Section

9.3
).


6.5

Remote Access and Notification


Remot
e access and notification functions are performed by




Remote Client (see Section
9.4
), and



WebLink (see Section
9.5
).


7

Shared Services


These services are integrated in
, and shared by
all core comp
onents

and

all
application specific modules.


7.1

Database M
anagement


For purposes of reliability, speed, and cost control BTE has developed its own
database engine. It is used to store and manage most of NTMC information. This
includes all
system configurati
on files, as well as all remote
unit

databases. The
files are encrypted when necessary. File format is not proprietary; it can be
o
btained upon request.


Database manager comes with an editor
(MCED)
which is one of the core
components
described

in Section
8.4
.





3 5 MA P L E P L A CE,

HUNTI NG TO N
, NY 1 1 7 4 3
US A

P HONE: 6 3 1
-
6 7 3
-
8 3 3 9,

FA X: 6 3 1
-
6 7 3
-
8 1 8 6

I NTERNET: WWW.BTECEN
TR A L.C OM

E
-
MA I L: S UP P ORT@BTECEN
TRA L
.CO M

NTMC Specification


Page
8

7.2

Event Logging


Every NTMC component, core or application
module

comes with an integrated
event logger. Every important event is written down into a log file. Every
component has its own event log file. Eve
ry entry in a log file, describing one
system event, comes in the following sections:




Subsystem



identifies which part of the NTMC system generated the
event log



Procedure



identifies the procedure within above subsystem which
generated the event log



Ev
ent Type



describes event level

o

Log



a regular event log entry

o

Alarm



log entry of an event requiring operator attention

o

Error



log entry of an event caused by software malfunction.
These entries are rare but when they do occur the customers are
asked
to contact BTE which, in turn, investigates the event and
correct the possible software malfunction.



Date



Event date



Time


Event time down to one second resolution



Entry


The actual body (text) of the event log



Group Number


Entry group number, used t
o group entries which are
parts of the same ‘larger’ event, or an error stack



Entry Number


Entry number


used for debugging purposes



Source File


identifies source code source file which produced the entry
-

used for debugging purposes



Line Number


li
sts the line number of the source code within the above
source file where event was generated
-

used for debugging purposes


Event log manager comes with a viewer
(MCEV)
which is one of the core
components listed
in Section
8.5
.


7.3

Security


In addition to operating system security (one has to log on to a correct Windows
account) NTMC has its own native security system. In order to use an NTMC
component an operator needs to first sign on to it. His / her account cr
edentials
determine which parts of the system he can see, and which operations she is



3 5 MA P L E P L A CE,

HUNTI NG TO N
, NY 1 1 7 4 3
US A

P HONE: 6 3 1
-
6 7 3
-
8 3 3 9,

FA X: 6 3 1
-
6 7 3
-
8 1 8 6

I NTERNET: WWW.BTECEN
TR A L.C OM

E
-
MA I L: S UP P ORT@BTECEN
TRA L
.CO M

NTMC Specification


Page
9

allowed to perform. Those credentials are enforced everywhere: on
a
control
room computer, on Remote Client machines, and users’ computers elsewhere on
the internet
runni
ng

standard web browsers.


Security database consists of User Groups and Users.


7.3.1

User Groups


Groups are used to define
privileges

for group members (Users). Each group
lists the following permissions for each of the 33 NTMC object classes:




Access (overal
l On/Off for the class)



Create / Delete



Configure



Read RTD (Run Time Data)



Execute



Generate Reports



Archive Data


7.3.2

Users


Each User account consists of username and password (credentials used to log
on to the system), as well as association with one of the
User Groups. The latter
defines user account privileges. Every account also contains user first and last
names, those are used in all event log entries associated with user actions on the
system.


Security manager comes with a security database editor
(MCS
A)
which is one of
the core components listed
in Section
8.6
.


7.4

Data Recording


All data coming into the system can be recorded into data recording files. There
are two data recording files available for each I/O

point (for definition of I/O point
see section

8.3.4
).

One is for data recorded via standard polling procedures, and
the other is data downloaded from devices capable of their own data recording.




3 5 MA P L E P L A CE,

HUNTI NG TO N
, NY 1 1 7 4 3
US A

P HONE: 6 3 1
-
6 7 3
-
8 3 3 9,

FA X: 6 3 1
-
6 7 3
-
8 1 8 6

I NTERNET: WWW.BTECEN
TR A L.C OM

E
-
MA I L: S UP P ORT@BTECEN
TRA L
.CO M

NTMC Specification


Page
10


Each of the d
ata entries consists of the following sections:




Date



Time


To one second resolution



Value



entry value



Flags


a register containing bits specifying data type dependent
attributes such as billing period (peak / off peak), Operation Mode (auto /
manual)
, Operation (ON/OFF), and Source of Operation (identifying
NTMC component).


As these files fill up they are archived to another location, usually somewhere on
a LAN. Archiving can be manually initiated, or programmed to happen on a
regular basis.


Data re
cording manager comes with a data viewing and analysis program
(MCDA) which is one of the core components described
in Section
8.7
.


8

Core Components


As mentioned in section
5.2

the core components perform not only SCADA
functions, but also provide all basic services to the entire control system. This
means that all functionality listed in this section is also available to all application
modules

(section
9
).


8.1

Master Controller Executive

(MCEX)


MCEX provides system startup, shutdown, and centralized high level system
monitoring facilities.

8.1.1

System Startup / Shutdown


NTMC consists of several components running simultaneously,

communicating
with each other and the outside world.
MCEX is used to start up and shut down
all installed components in correct order.





3 5 MA P L E P L A CE,

HUNTI NG TO N
, NY 1 1 7 4 3
US A

P HONE: 6 3 1
-
6 7 3
-
8 3 3 9,

FA X: 6 3 1
-
6 7 3
-
8 1 8 6

I NTERNET: WWW.BTECEN
TR A L.C OM

E
-
MA I L: S UP P ORT@BTECEN
TRA L
.CO M

NTMC Specification


Page
11

8.1.2

System Component Monitoring


MCEX displays the status

(ON / OFF)
,
mode (OK / ALARM)
and location (host
computer) of eac
h component comprising the NTMC system.


8.2

Input / Output Executive (IOEX)


IOEX is responsible for NTMC communications.

Each communications channel
consists of two
independently configurable

layers to reduce complexity, and to
provide larger number of

avail
able choices.
The two layers are
Physical Layer

and
Application Layer
.


There are no software imposed limits on the number communications channels
IOEX can run at any one time, or which communications protocol any one
channel is running. All channels run i
ndependently and asynchronously.


To define a communications channel one first creates a physical layer interface,
then an appropriate application layer interface, matches them together in a pair,
and assigned a name to the so formed channel. IOEX then man
ages the channel
independently of all other channels.


8.2.1

Physical Layer


This layer virtualizes NTMC‘s interaction with the outside world.
Parameters
common to all physical layer clients and servers:


PARAMETER

DESCRIPTION

Channel Id

Channel identifier, use
d for communications channel
identification purposes.

Connect T.O.
(ms)

Connect time out, specified in milliseconds. If client is
unable to connect to server in the given time,
operation fails and the failure is logged in the event
log file.

Wait T.O. (m
s)

Wait time out, specified in milliseconds. If client, once
connected,


is unable to receive a reply from the
server in the given time, operation fails and the failure



3 5 MA P L E P L A CE,

HUNTI NG TO N
, NY 1 1 7 4 3
US A

P HONE: 6 3 1
-
6 7 3
-
8 3 3 9,

FA X: 6 3 1
-
6 7 3
-
8 1 8 6

I NTERNET: WWW.BTECEN
TR A L.C OM

E
-
MA I L: S UP P ORT@BTECEN
TRA L
.CO M

NTMC Specification


Page
12

is logged in the event log file.

Input FIFO
Records

Size of input 'First In First Out'

buffer, in records. Used
for buffering incoming message. Number should be
increased for busy channels.

Input Record
Width

Input FIFO buffer width, in bytes. Determines
maximum allowed incoming message length.

Output FIFO
Records

Size of output 'First In

First Out' buffer, in records.
Used for buffering outgoing message. Number should
be increased for busy channels.

Output Record
Width

Output FIFO buffer width, in bytes. Determines
maximum allowed outgoing message length.

Input Recording

When
Enabled

al
l incoming messages get recorded in
the
Recording Input File
. This parameter should be
Disabled

except during system debugging (see
parameter below).

Recording Input
File

Incoming message recording file id (see above
parameter).

Input File
Records

Capaci
ty of
Recording Input File,

in records. File is a
FIFO, oldest messages get overwritten when file is
full.

Input File Record
Width

Incoming message recording file record width, in
bytes. Determines maximum allowed incoming
message length.

Output Recordin
g

When
Enabled

all outgoing messages get recorded in
the
Recording Output File
. This parameter should be
Disabled

except during system debugging (see
parameter below).

Recording Output
File

Outgoing message recording file id (see above
parameter).

Output

File
Records

Capacity of
Recording Output File,

in records. File is a
FIFO, oldest messages get overwritten when file is
full.

Output File
Record Width

Outgoing message recording file record width, in
bytes. Determines maximum allowed outgoing
message le
ngth.

Message Format

Format in which input and output messages are



3 5 MA P L E P L A CE,

HUNTI NG TO N
, NY 1 1 7 4 3
US A

P HONE: 6 3 1
-
6 7 3
-
8 3 3 9,

FA X: 6 3 1
-
6 7 3
-
8 1 8 6

I NTERNET: WWW.BTECEN
TR A L.C OM

E
-
MA I L: S UP P ORT@BTECEN
TRA L
.CO M

NTMC Specification


Page
13

recorded. When set to
ASCII
, messages are recorded
as simple ASCII characters. When set to
Binary
,
numeric value of each byte is recorded in
hexadecimal notation.



The following interfac
es are available


8.2.1.1

Serial (RS 232 and RS 485)


One can connect to external devices as well as
dedicated and
dialup modems
via this interface.

Additional parameters used to configure serial clients and
servers:


PARAMETER

DESCRIPTION

Port Id

Serial port ide
ntifier.


Must be of the form COMn,
where n = 1, 2, 3, ...


Baud Rate

Specifies communications channel speed, in bits /
second.

Data bits

Number of data bits used in communications over this
channel.

Stop Bits

Number of stop bits used in communications
over this
channel.

Parity

Parity (error checking) used in communications over
this channel.



Additional parameters used to configure serial clients with dialup modems:


PARAMETER

DESCRIPTION

Port Id

Serial port identifier.


Must be of the form COMn,
wh
ere n = 1, 2, 3, ...


Modem
Initialization
String

String sent to the modem on above port when NTMC
is restarted.




3 5 MA P L E P L A CE,

HUNTI NG TO N
, NY 1 1 7 4 3
US A

P HONE: 6 3 1
-
6 7 3
-
8 3 3 9,

FA X: 6 3 1
-
6 7 3
-
8 1 8 6

I NTERNET: WWW.BTECEN
TR A L.C OM

E
-
MA I L: S UP P ORT@BTECEN
TRA L
.CO M

NTMC Specification


Page
14

Modem Connect
String

String sent to the modem when dialing the telephone
number. The latter is appended to the Connect String
when dialing th
e number.

Modem
Disconnect String

String sent to the modem when 'hanging up' the
phone.

Baud Rate

Specifies communications channel speed, in bits /
second.

Data bits

Number of data bits used in communications over this
channel.

Stop Bits

Number of stop

bits used in communications over this
channel.

Parity

Parity (error checking) used in communications over
this channel.


8.2.1.2

Ethernet


Network (LAN and internet) communications go over this interface.
Windows
Sockets

interface is used because of overwhelmin
g popularity of TCP/IP
protocol.
Named Pipes

interface is also available so older network protocols
(such as IPX/SPX or NetBEUI) can be used.


Additional parameters used to configure Windows Socket clients and servers:


PARAMETER

DESCRIPTION

Windows
Socke
ts Major
Version

Major version number of Windows Sockets library
IOEX is to initialize and use for communications.

Windows
Sockets Minor
Version

Minor version number of Windows Sockets library
IOEX is to initialize and use for communications.

Port Number

TCP/IP port number to be used for communications.

Server Address

Windows Sockets clients only use this address to
connect appropriate server.

Address Type

Parameter specifies how above address is specified.
Possible choices are
NetBios

Name

(address mus
t be



3 5 MA P L E P L A CE,

HUNTI NG TO N
, NY 1 1 7 4 3
US A

P HONE: 6 3 1
-
6 7 3
-
8 3 3 9,

FA X: 6 3 1
-
6 7 3
-
8 1 8 6

I NTERNET: WWW.BTECEN
TR A L.C OM

E
-
MA I L: S UP P ORT@BTECEN
TRA L
.CO M

NTMC Specification


Page
15

server network name), URL (address must be server
universal resource locator, such as
http://www.btecentral.com
),
IPv4 Address

(address
must be server IP version 4 32 bit address, such as
123.456.789.001), and

IPv6 Address

(address must
be server IP version 6 128 bit address).



Additional parameters used to configure Named Pipe clients and servers:


PARAMETER

DESCRIPTION

Pipe Name

Named pipe identifier. Must be unique within the host
computer.


Identifier mu
st conform to standard named
pipe naming conventions.



8.2.2

Application Layer

/ Protocols


In most cases this layer sits on top of the physical layer.
Exceptions are
COM/DCOM and Web Services interfaces listed below.


The layer hosts communications protocol u
sed by users of the channel, and
provides the standard interface for NTMC device drivers so they can
communicate with external devices. Depending on complexity of the protocol,
this layer may have further internal layers (such as DNP data link, transport,
and
application layers),
or a single layer.


Parameters common to all application layer clients:


PARAMETER

DESCRIPTION

Channel Id

Channel identifier, used for application channel
identification purposes. This identifier shows up in
RUEX remote unit
Remote Client Id

parameter choice
list when selecting remote unit communications link.

Comm. Client
File Id

Specifies File id which identifies communicati
ons
channel


used by this application client.

Application Id

Specifies application type / communications protocol



3 5 MA P L E P L A CE,

HUNTI NG TO N
, NY 1 1 7 4 3
US A

P HONE: 6 3 1
-
6 7 3
-
8 3 3 9,

FA X: 6 3 1
-
6 7 3
-
8 1 8 6

I NTERNET: WWW.BTECEN
TR A L.C OM

E
-
MA I L: S UP P ORT@BTECEN
TRA L
.CO M

NTMC Specification


Page
16

used over this channel.

Destination
Address (or
NONE)

Parameter specifies addressing within a common
communications channel. Example: teleph
one
number.

Connect On Init

When
Enabled
, IOEX connects the client to the server
at channel initialization time, i.e. when IOEX starts up.
When
Disabled
, communications channel is initialized,
however connection with the server is not attempted.

Disconne
ct on
Idle (sec, 0 =
disabled)

Parameter specifies the number of seconds of
channel inactivity before connection with the server is
terminated. The value of 0 disables this function.

Disconnect on
Read Failure

When
Enabled

IOEX disconnects the channel on
server query failure. The feature is turned off when
this parameter is
Disabled
.

Channel Flushing

Communications channel is flushed, and FIFOs reset
periodically when this parameter is
Enabled
. This
cleans up chatter on noisy lines.
Caution
: This
paramete
r must be
Disabled

on all channels expecting
unsolicited (quiescent) messages.



Parameters common to all application layer servers:


PARAMETER

DESCRIPTION

Channel Id

Channel identifier, used for application channel
identification purposes. When this ser
ver is to be
paired with an application client, both client and server
must have the same Id.

Comm. Client
File Id

Specifies File id which identifies communications
channel


used by this application server. When this
server is to be paired with an applica
tion client, both
client and server must have the same Comm. Client
File Id.




The following protocols / interfaces are supported.





3 5 MA P L E P L A CE,

HUNTI NG TO N
, NY 1 1 7 4 3
US A

P HONE: 6 3 1
-
6 7 3
-
8 3 3 9,

FA X: 6 3 1
-
6 7 3
-
8 1 8 6

I NTERNET: WWW.BTECEN
TR A L.C OM

E
-
MA I L: S UP P ORT@BTECEN
TRA L
.CO M

NTMC Specification


Page
17

8.2.2.1

COM/DCOM


Microsoft Distributed Component Object Model interface is an older mechanism
for communications between processe
s running on one or several machines.
NTMC uses it to communicate with external (foreign) SCADA
systems.


8.2.2.2

Web Service
s


Microsoft Web Services is one of the latest technologies for communications
between computers over the internet. BTE hosts a web service

on its own
internet server so NTMC systems can be accessed via the internet by human
users, other NTMC systems, or other SCADA systems.


8.2.2.3

DNP 3.0


Probably the most popular protocol used in the utility industry these days. All
three DNP layers are fully co
nfigurable with no software imposed size limitations.
Client and server sides are supported, so
each channel can act as an
independent client (master) or server (slave). This enables IOEX, and thus
NTMC to be a DNP client and server at the same time and ca
n act as a data
concentrator.

Most major hardware (RTUs, switches, IEDs, meters, etc)
manufacturers support DNP.


Additional parameters used to configure DNP clients:


PARAMETER

DESCRIPTION

Resident on
Master Station

Possible choices are
Yes

(this station

is a DNP client),
and


No

(this station is a DNP server).

Station Address

Specifies this station address in the DNP network.

Data Link
Confirmations

Possible choices are
Enabled

(data link layer
confirmations are enabled), and
Disabled

(data link
layer
confirmations are disabled).


Data Link Retries
(on Error))

Parameter specifies number of times data link layer
must retry communicating when errors occur.

Data Link Status
Specifies how often (in milliseconds) data link is t
o



3 5 MA P L E P L A CE,

HUNTI NG TO N
, NY 1 1 7 4 3
US A

P HONE: 6 3 1
-
6 7 3
-
8 3 3 9,

FA X: 6 3 1
-
6 7 3
-
8 1 8 6

I NTERNET: WWW.BTECEN
TR A L.C OM

E
-
MA I L: S UP P ORT@BTECEN
TRA L
.CO M

NTMC Specification


Page
18

Polling Period
(ms, 0 = off)

query the other station when the latter is reporting
busy. The value of
0

disabled this function.

Data Link Delay
Between
Transmissions
(ms)

Specifies how many milliseconds are to transpire
between outgoing messages. This parameter can be
used to pace c
ommunications when dealing with
slower devices, and when confirmations are turned
off.


Data Link Busy
Station Timeout
Period (ms)

Specifies how long data link is to wait (polling for
status) for a busy station to report ready.


Data Link Forces
DFC = 0
(User
Link Available)

Parameter should be set to No in normal
circumstances. It can be set to Yes when debugging
the system.

Application Layer
Fragment Size
Limit (bytes)

Parameter specifies maximum size of application
layer fragment the station is allowe
d to transmit.

Application Layer
Retries (on Error)

Parameter specifies number of times application layer
must retry communicating when errors occur.

Application Layer
Confirmations

Possible choices are
Enabled

(application


layer
confirmations are enabl
ed), and
Disabled

(application
layer confirmations are disabled).


Application Layer
Time Out Period

Specifies how long application layer is to wait for a
station to respond.


Additional parameters used to configure DNP
servers
:


PARAMETER

DESCRIPTION

R
esident on
Master Station

Possible choices are
Yes

(this station is a DNP client),
and


No

(this station is a DNP server).

Station Address

Specifies this station address in the DNP network.

Data Link
Confirmations

Possible choices are
Enabled

(data link
layer
confirmations are enabled), and
Disabled

(data link
layer confirmations are disabled).


Data Link Retries
(on Error))

Parameter specifies number of times data link layer
must retry communicating when errors occur.




3 5 MA P L E P L A CE,

HUNTI NG TO N
, NY 1 1 7 4 3
US A

P HONE: 6 3 1
-
6 7 3
-
8 3 3 9,

FA X: 6 3 1
-
6 7 3
-
8 1 8 6

I NTERNET: WWW.BTECEN
TR A L.C OM

E
-
MA I L: S UP P ORT@BTECEN
TRA L
.CO M

NTMC Specification


Page
19

Data Link Status
Polling Period
(m
s, 0 = off)

Specifies how often (in milliseconds) data link is to
query the other station when the latter is reporting
busy. The value of
0

disabled this function.

Data Link Delay
Between
Transmissions
(ms)

Specifies how many milliseconds are to transpire

between outgoing messages. This parameter can be
used to pace communications when dealing with
slower devices, and when confirmations are turned
off.


Data Link Busy
Station Timeout
Period (ms)

Specifies how long data link is to wait (polling for
status)

for a busy station to report ready.


Data Link Forces
DFC = 0 (User
Link Available)

Parameter should be set to No in normal
circumstances. It can be set to Yes when debugging
the system.

Application Layer
Fragment Size
Limit (bytes)

Parameter specifies
maximum size of application
layer fragment the station is allowed to transmit.

Application Layer
Retries (on Error)

Parameter specifies number of times application layer
must retry communicating when errors occur.

Application Layer
Confirmations

Possible

choices are
Enabled

(application


layer
confirmations are enabled), and
Disabled

(application
layer confirmations are disabled).


Application Layer
Time Out Period

Specifies how long application layer is to wait for a
station to respond.



8.2.2.4

MODBUS


This
older industry standard protocol is also fully supported and configurable.
Simpler than DNP, it is suitable for systems with smaller number of
independently addressable external devices.

Most major hardware (RTUs,
switches, IEDs, meters, etc) manufacturers

support MODBUS.


8.2.2.5

Comverge





3 5 MA P L E P L A CE,

HUNTI NG TO N
, NY 1 1 7 4 3
US A

P HONE: 6 3 1
-
6 7 3
-
8 3 3 9,

FA X: 6 3 1
-
6 7 3
-
8 1 8 6

I NTERNET: WWW.BTECEN
TR A L.C OM

E
-
MA I L: S UP P ORT@BTECEN
TRA L
.CO M

NTMC Specification


Page
20

Comverge Inc. protocol for communications with Comverge load management
switches via Comverge RTS radio interface.
This is a proprietary protocol, owned
by Comverge Inc. Although fully implemented BTE needs permission from
Comve
rge to use this protocol on a case by case basis.

Due to the nondisclosure
agreement between BTE and Comverge BTE is not allowed to disclose any
information pertaining to Comverge protocol.


8.2.2.6

Telescada


ACS Telescada Inc. proprietary
protocol

is
used to sup
port their CCU7C radio
interface, their full line of ARS series RTUs and several types of load
management switches and pagers made by GE, Motorola, and Scientific Atlanta.


Additional parameters used to configure
Telescada clients:


PARAMETER

DESCRIPTION

Baud Rate

Specifies communications channel speed, in bits /
second. Parameter does not control the speed. The
value is used by
Telescada

clients in calculations of
internal timing parameters.

CCU Board
Number

Telescada

CCU7C

can have two boards. This
parameter identifies the board used by this channel.

CCU Board
Channel Number

Telescada

CCU7C

boards can have two ports. This
parameter identifies the port used by this channel.

Function Tone
(Hz)

Tone frequency used by
CCU7C

when controllin
g
radio transmitters.


8.2.2.7

BTE


BTE Corporation protocol
is used for

communications between the various
NTMC components.
Documentation is available upon request.


8.2.2.8

NPPD





3 5 MA P L E P L A CE,

HUNTI NG TO N
, NY 1 1 7 4 3
US A

P HONE: 6 3 1
-
6 7 3
-
8 3 3 9,

FA X: 6 3 1
-
6 7 3
-
8 1 8 6

I NTERNET: WWW.BTECEN
TR A L.C OM

E
-
MA I L: S UP P ORT@BTECEN
TRA L
.CO M

NTMC Specification


Page
21

Nebraska Public Power District protocol is used by NPPD to disseminate load
management wai
ver messages to member utilities within the state of Nebraska.
Protocol documentation is available upon request.


Additional parameters used to configure NPPD Servers:


PARAMETER

DESCRIPTION

Waiver Message
Execution

NTMC accepts load management waiver mes
sages
from NPPD when this parameter is set to
Enabled
.
Waiver messages are ignored when the parameter is
set to
Disabled
.

Emergency
Message
Execution

NTMC accepts emergency load management
messages from NPPD when this parameter is set to
Enabled
. Emergenc
y messages are ignored when the
parameter is set to
Disabled
.

Group
Designation

Parameter value defined NPPD customer group
designation. NPPD messages are ignored unless they
contain matching group designation.

Zone Designation

Parameter value defined NP
PD customer zone
designation. NPPD messages are ignored unless they
contain matching zone designation.

District
Designation

Parameter value defined NPPD customer district
designation. NPPD messages are ignored unless they
contain matching district designa
tion.

Modem Answers
on Ring #

The value specifies how many rings the modem must
receive in order to answer the call.



8.3

Remote Unit Executive (RUEX)


RUEX is the ‘centerpiece’ of NTMC core in that it performs most of the
automated SCADA functions
.



8.3.1

Compo
nent Architecture





3 5 MA P L E P L A CE,

HUNTI NG TO N
, NY 1 1 7 4 3
US A

P HONE: 6 3 1
-
6 7 3
-
8 3 3 9,

FA X: 6 3 1
-
6 7 3
-
8 1 8 6

I NTERNET: WWW.BTECEN
TR A L.C OM

E
-
MA I L: S UP P ORT@BTECEN
TRA L
.CO M

NTMC Specification


Page
22

RUEX database is divided into a collection of operator defined domains, and
each domain holds a collection of remote units (devices).

Each of the remote
units is a collection if I/O (data) points.


Each level of above hierarchy is indivi
dually configurable. RUEX configuration
affects itself and all objects below (domains, remote units, etc). Each domain
configuration affects itself, and objects below. Each remote unit configuration
affects its own functioning and I/O points within. And fi
nally, Each I/O point can
also be individually configured.


In addition to the above hierarchy, there additional databases for managing one
line diagrams, data evaluation facilities, and message routing facilities described
later in this section.


Also, t
here are a number of high level, global settings and functions that affect
the whole component. Global parameters are listed in the following table:


PARAMETER

DESCRIPTION

Manager Status

Enables or disables all RUEX activities. When
enabled, any enabled s
ub processes are allowed to
execute. When disabled no automatic activities are
allowed to execute.

Export File
Directory

Specifies the directory where RUEX reports get
deposited. This can be a directory on a local hard
disk, or a network drive.

Alarms

Ca
n be
Enabled

or
Disabled
. When
Enabled

visual
and audio alarms are generated in addition to alarm
log entries when error conditions occur. When
Disabled
, log entries are generated only.

Midnight RU
Clock
Synchronization

Midnight remote units clock synchro
nization with
master time executes nightly when enabled.

OS Time
Monitoring

Operating system time is monitored when enabled.
When operating system clock is reset discontinuously,
a log entry is generated, and application modules
ignore data from the first

poll following the detected
time shift.

RURDR File
Specifies the directory where RUEX
RURDR

files get



3 5 MA P L E P L A CE,

HUNTI NG TO N
, NY 1 1 7 4 3
US A

P HONE: 6 3 1
-
6 7 3
-
8 3 3 9,

FA X: 6 3 1
-
6 7 3
-
8 1 8 6

I NTERNET: WWW.BTECEN
TR A L.C OM

E
-
MA I L: S UP P ORT@BTECEN
TRA L
.CO M

NTMC Specification


Page
23

Backup Directory

archived. This can be a directory on a local hard disk,
o
r a network drive.

NTMCRDR File
Backup Directory

Specifies the directory where RUEX
NTMCRDR

files
get archived. This can be a directory on a local hard
disk, or a network driv
e.

Auto
-

Archiving
(Data and Event
Log Files)

Specifies if data recording files and event log file are
to be archived automatically, and how often. Possible
options are
Disabled
,
Daily
,
Weekly
, and
Monthly
.



8.3.2

Domains


Domains are collections of remote u
nits. A domain not only serves as a folder for
remote units (the latter can be segregated based on function, geographic
location, etc.), but also as a collection of parameters which affect all remote units
within the domain. Also, commands issued on domai
n level affect all remote units
within that domain. For example, one can poll all meters by pressing the ‘Poll’
button on the domain “Meters’ window, without polling all substation RTUs as
well.


Each domain can be represented by two windows, one showing r
emote units
within the domain in graphical form, and the other as a listing in tabular form.


Domain parameters:


PARAMETER

DESCRIPTION

Domain Id

Displays the domain id. This is a read only parameter,
it can not be changed. The identifier is selected by t
he
operator at the time of domain creation.

Manager Status

Enables or disables all domain activities. When
enabled, any enabled sub processes associated with
this domain are allowed to execute. When disabled no
automatic activities associated with the dom
ain are
allowed to execute.

Polling

Enables or disables domain associated automatic
polling activities. When disabled, manual polling still
works.




3 5 MA P L E P L A CE,

HUNTI NG TO N
, NY 1 1 7 4 3
US A

P HONE: 6 3 1
-
6 7 3
-
8 3 3 9,

FA X: 6 3 1
-
6 7 3
-
8 1 8 6

I NTERNET: WWW.BTECEN
TR A L.C OM

E
-
MA I L: S UP P ORT@BTECEN
TRA L
.CO M

NTMC Specification


Page
24

Evaluation
Priority (0 =
highest)

Specifies evaluation priority of
I/O points

under this
domain during each point evaluation cycle.

Timed Switch
Manager

Enables or disables timed switch manager activities.

Timed Switch
Manager Period

Specifies how often timed switch manager execut
es,
in seconds.

Timed Switch
Update Period
Cushion

Specifies the number of seconds to subtract from
each timed switch timeout period. This cushioning
assures that switches get refreshed on time even
when RUEX is very busy and timed switch manager
executio
n is delayed.

Control Point
Operation
Logging

Specifies which control point operations are recorded
in RUEX event log file. The following options are
available: All
-

Every control code is recorded; State
Changes Only
-

Only control codes which cause stat
e
change (On

Off and Off

On) are recorded; None
-

recording is disabled. Note that this parameter does
not affect
NTMCRDR

control point activity recording.
The latter always re
cords control point state changes
only.

Control Point
Operation
Repeating
(times)

Specifies the number of times control code is to be
repeated each time control point is controlled by
RUEX. The value of 0 means control code is not
repeated, i.e. one contr
ol code only is sent out.

Failed Poll
Repeating
(times)

Specifies maximum number of times
remote unit

poll
gets to be repeated when poll fails. The value of 0
means remote
unit gets polled once only.

Delay Between
Polls (ms)

Specifies amount of time, in milliseconds, between
successive polls. The value of this parameter depends
on the communications medium used. This same
delay is also used by control code dispatcher for
pa
cing of outgoing control codes.

Data Recording
Interval (Minutes)

Specifies
RURDR

interval, in minutes, to be
programmed into remote units when data recording is
enabled.

RU Li
st Display
Specifies remote unit list display method, when



3 5 MA P L E P L A CE,

HUNTI NG TO N
, NY 1 1 7 4 3
US A

P HONE: 6 3 1
-
6 7 3
-
8 3 3 9,

FA X: 6 3 1
-
6 7 3
-
8 1 8 6

I NTERNET: WWW.BTECEN
TR A L.C OM

E
-
MA I L: S UP P ORT@BTECEN
TRA L
.CO M

NTMC Specification


Page
25

Method

domain list view window is displayed. The value
RU
Data

should be used when domain contains RTUs or
multiple relay switches. In this case remote unit
relevant data gets to be displayed. The
value
First
CTP Data

is used when domain contains single relay
switches. In this case first (and only) control point
relevant information is displayed.

RU Id Displays
(On 2D Listings)

Specifies if remote unit identifiers are to be displayed
in 2D domain v
iew windows. This may be turned off
when domains contain many remote units.

Hidden RUs /
Points

When set to
Hide
, hidden remote units and I/O points
are not displayed. When set to
Show
, all remote units
and points are displayed.

RU Comm. Lines
Drawing

Sp
ecifies if remote unit communications lines get to
be shown in 2D domain view windows. This may be
turned off when domains contain many remote units.



8.3.3

Remote Units


Each remote unit is the lowest individually addressable entity which NTMC can
talk to.
Th
e number of parameters involved depends on the type of device
remote unit represents.
It can be something as simple as a switch, something as
complicated as another SCADA system, or anything in between (RTU, meter,
PLC, IED, etc.).

Each remote unit can be

displayed by one or more windows as needed
depending on the number of I/O points within.

Parameters used to configure
all remote units
:


PARAMETER

DESCRIPTION

<Manufacturer><Model
/ Protocol><Unit Type>

Parameter value is remote unit id. The identifier
i
s selected by the operator at the time of remote
unit creation. Parameter name specifies
manufacturer name, unit model /
communications protocol, and unit type. For



3 5 MA P L E P L A CE,

HUNTI NG TO N
, NY 1 1 7 4 3
US A

P HONE: 6 3 1
-
6 7 3
-
8 3 3 9,

FA X: 6 3 1
-
6 7 3
-
8 1 8 6

I NTERNET: WWW.BTECEN
TR A L.C OM

E
-
MA I L: S UP P ORT@BTECEN
TRA L
.CO M

NTMC Specification


Page
26

example,
Telescada

ARS16P RTU
, or
GE
REMS 101/102
Switch.

Manager Status

Enables or disables all remote unit activities.
When
Enabled
, any enabled sub processes
associated with this remote unit are allowed to
execute. When
Disabled

no automatic activities
associated with this unit are allowed to execute.

Communications
Protocol

Specifies which communications protocol RUEX
is to use to communicate with remote unit. Not
all choices may be available. Possible choices
are
NONE

(no communications),
Native

(manufacturer's own protocol),
<Specific
Protocol>

(on
e or more of the standard
protocols, such as DNP 3.0, MODBUS, etc).

External Client Id

Specifies communications channel and protocol
RUEX must use to communicate with this unit.
The allowed choices are presented in a pull
-
down menu, and come from the choi
ces
configured into
IOEX

by the operator.

Evaluation Priority (0 =
highest)

Specifies evaluation priority of
I/O points

under
this remote unit during each point evaluation
cycle.

Display Status

Specifies whether this remote unit is to be
displayed in domain windows. When
Enabled
,
the unit is always displayed. When
Disabled
,
the
unit is hidden when domain parameter
Hidden
RUs / Points

is set to
Hide.




In above table, External Client
Id specifies

communica
tion channel defined in
IOEX (section
8.2
) to be used to communicate with the remote unit


Additional parameters used to configure
2
-
way remote units
:


PARAMETER

DESCRIPTION

Polling

Specifies whether this unit
is to be polled
automatically by RUEX. When
Enabled

RUEX polls



3 5 MA P L E P L A CE,

HUNTI NG TO N
, NY 1 1 7 4 3
US A

P HONE: 6 3 1
-
6 7 3
-
8 3 3 9,

FA X: 6 3 1
-
6 7 3
-
8 1 8 6

I NTERNET: WWW.BTECEN
TR A L.C OM

E
-
MA I L: S UP P ORT@BTECEN
TRA L
.CO M

NTMC Specification


Page
27

this unit automatically. When
Disabled
, RUEX ignores
this unit, but manual polling is still possible.

Polling Period
(System Periods)

Parameter specifies how often this unit is to be polled
wh
en polled automatically by RUEX. The period is in
multiples of
currently active RUEX polling period.

Minimum Polling
P
eriod (Seconds)

Specifies minimum interval, in seconds, between
automatic polls of this unit. This restriction may have
to be imposed on slow counting pulse inputs in order
to avoid bad calculation results derived from poor
statistics. Manual polls are sti
ll permitted during
blackout period, however numeric data received
during that period (analog points and counters) does
not get entered into database.




Additional parameters used to configure
DNP 3.0 capable remote units
:


PARAMETER

DESCRIPTION

Polling

Method

Specifies polling method to be used. Possible choices
are
Standard

(standard RUEX polling algorithm which
asks for data for defined I/O points only), and

By
Classes

(polling by DNP object classes).

Static Polling
Period (0 =
Disabled)

Specifies ho
w often RUEX is to poll remote unit for
static (DNP class 0) data objects. The value of 0
means never, the value of 1 means every poll, the
value of 2 means every other poll, etc. This parameter
is ignored when parameter 'Polling Method' is set
to

Standard
.

Class 1 Period (0
= Disabled)

Specifies how often RUEX is to poll remote unit for
events (DNP class 1 data objects). The value of 0
means never, the value of 1 means every poll, the
value of 2 means every other poll, etc. This parameter
is ignored when
parameter 'Polling Method' is set
to

Standard
.

Class 2 Period (0
= Disabled)

Specifies how often RUEX is to poll remote unit for
events (DNP class 2 data objects). The value of 0
means never, the value of 1 means every poll, the



3 5 MA P L E P L A CE,

HUNTI NG TO N
, NY 1 1 7 4 3
US A

P HONE: 6 3 1
-
6 7 3
-
8 3 3 9,

FA X: 6 3 1
-
6 7 3
-
8 1 8 6

I NTERNET: WWW.BTECEN
TR A L.C OM

E
-
MA I L: S UP P ORT@BTECEN
TRA L
.CO M

NTMC Specification


Page
28

value of 2 means every oth
er poll, etc. This parameter
is ignored when parameter 'Polling Method' is set
to

Standard
.

Class 3 Period (0
= Disabled)

Specifies how often RUEX is to poll remote unit for
events (DNP class 3 data objects). The value of 0
means never, the value of 1 mea
ns every poll, the
value of 2 means every other poll, etc. This parameter
is ignored when parameter 'Polling Method' is set
to

Standard
.

Station Address

Specifies remote unit DNP address.

Object Prefix
Code

Specifies the DNP Object Prefix Code to be used

in
replies and unsolicited messages. This parameter is
used only when RUEX acts as a DNP slave station
(server). Parameter is ignored when RUEX acts as a
DNP master station (client).

Range Specifier
Code

Specifies the DNP Range Specifier Code to be used
in replies and unsolicited messages. This parameter is
used only when RUEX acts as a DNP slave station
(server). Parameter is ignored when RUEX acts as a
DNP master station (client).

Undefined I/O
Point Data
Processing

Specifies how RUEX is to behave when

data is
received, but is addressed to an undefined I/O point.
Possible values are
NONE (Ignore)
, and
Log and
Alarm
. In the latter case RUEX generates an event log
entry for every data received for which I/O point was
not defined, also recording I/O point'
s address.

Unsolicited
Report Recipient

Specifies if remote unit is recipient of unsolicited
reports. If set to yes, RUEX sends unsolicited reports
to remote unit when data change. This parameter is
used only when RUEX acts as a DNP slave station
(server)
. Parameter is ignored when RUEX acts as a
DNP master station (client).



Additional parameters used to configure
MODBUS capable remote units
:





3 5 MA P L E P L A CE,

HUNTI NG TO N
, NY 1 1 7 4 3
US A

P HONE: 6 3 1
-
6 7 3
-
8 3 3 9,

FA X: 6 3 1
-
6 7 3
-
8 1 8 6

I NTERNET: WWW.BTECEN
TR A L.C OM

E
-
MA I L: S UP P ORT@BTECEN
TRA L
.CO M

NTMC Specification


Page
29

PARAMETER

DESCRIPTION

RTU


Address

Specifies the unit's MODBUS RTU address.



Additional parameters used to c
onfigure
General Electric 16 bit PLCs
:


PARAMETER

DESCRIPTION

PLC Address

Numerical address identifying the PLC.

Register Address
(Status Reads)

Numerical address of the PLC register used for
reading status bits. NTMC
status point

addresses are
interpreted as bit identifiers in the register specified by
this parameter. All other types of
I/O poi
nts

addresses
are interpreted as register addresses within the PLC.



Additional parameters used to configure
Baritek WSR 4400 RTUs
:


PARAMETER

DESCRIPTION

Register Address
(Control Writes)

Address of a 16 bit register, assigned by
Baritek Inc.
,
for up to 16 control outputs.


Push To Talk
Delay (ms)

Delay after the transceiver is keyed before sending
data. This is to allow the master transceiver to go
from transmit to receive mode. The value of this
parameter gets

uploaded when programming the
remote unit. The default is 250 ms.

Counter 0 Pre
-
scale Value

Pre
-
scale factor for KYZ pulses on digital inputs 0 and
1. For example, if the value is set to 6, the pulse
counter will be slowed down by a factor of 6. The
valu
e of this parameter gets uploaded when
programming the remote unit. Default value is 1.

Counter 1 Pre
-
scale Value

Pre
-
scale factor for KYZ pulses on digital inputs 2 and
3. For example, if the value is set to 6, the pulse
counter will be slowed down by a
factor of 6. The
value of this parameter gets uploaded when
programming the remote unit. Default value is 1.





3 5 MA P L E P L A CE,

HUNTI NG TO N
, NY 1 1 7 4 3
US A

P HONE: 6 3 1
-
6 7 3
-
8 3 3 9,

FA X: 6 3 1
-
6 7 3
-
8 1 8 6

I NTERNET: WWW.BTECEN
TR A L.C OM

E
-
MA I L: S UP P ORT@BTECEN
TRA L
.CO M

NTMC Specification


Page
30


Additional parameters used to configure
General Electric kV2 meters
:


PARAMETER

DESCRIPTION

Load Interval
Delay (ms)

Delay, in milliseconds, be
tween them time when
NTMC loads the data logger interval selector register,
and the time when NTMC reads the interval data (time
stamps and load profiling channels) from the unit's
MODBUS board.


Last Downloaded
Interval

Number of last data logger interva
l (1
-

2880)
downloaded from meter's MODBUS board. The
number can be set back in case older data needs to
be re
-
downloaded.

Interval Period
(Minutes)

Data logger interval period programmed into the
meter. The value of this parameter is copied from the
met
er and set at the time when NTMC RURDR is
enabled. NTMC does not enable the data logger,
because the MODBUS board does not support that
feature. Meter's data logger must be enabled using
GE's MeterMate software.



Parameters common to all
Telescada RTUs
:


PARAMETER

DESCRIPTION

RTU Address

Specifies address used by RUEX to communicate
with the RTU.

Group Address
Usage

Specifies if parameter RTU Group Address is defined,
and is allowed to be used by RUEX for
communication with groups of RTUs. Parameter mus
t
be
Enabled

for this to happen.

RTU Group
Address

Specifies group address used by RUEX to
communicate with the RTU. All RTUs set up with the
same group address receive and process messages
containing this address. Parameter
Group Address
Usage

must be
En
abled

for RUEX to use this
address.




3 5 MA P L E P L A CE,

HUNTI NG TO N
, NY 1 1 7 4 3
US A

P HONE: 6 3 1
-
6 7 3
-
8 3 3 9,

FA X: 6 3 1
-
6 7 3
-
8 1 8 6

I NTERNET: WWW.BTECEN
TR A L.C OM

E
-
MA I L: S UP P ORT@BTECEN
TRA L
.CO M

NTMC Specification


Page
31

Route Id

Specifies Route identifier to be used when direct
communication with remote unit is not possible. When
the value is set to NONE, RUEX communicates with