Overview
Meter Reading Executive performs automated meter reading functions for electric utility
companies. It implements those functions as dictated by the utility
industry, using resources provided by the NTMC
core components.
MREX organizes its data as follows: MREX maintains global parameters and a
list of meters. Automated meter
reading can be scheduled globally, while manual reading can be done globally, or
individually by meter.
MREX also maintains a list of user defined schedules.
These are collections of meter parameters shared between meters.
Multiple meters can be assigned the same schedule. All those meters share
all parameters in that schedule. Two kinds of schedules are available: monthly
and daily. The former list activities for each day of the month by
specifying a daily schedule for each day of the month, while the latter specify
meter reading activities for a given day of the month. Meters are associated
with monthly schedules.
Three kinds of meter reading are supported: latest dial reads, billing reads,
and data downloads. While the first two kinds essentially record dial readings
throughout the system, the latter records energy consumption, as recorded by
meters, and stored by remote units, every few minutes, as specified by the
operator. The detailed data is downloaded once per day and stored in RUEX RURDR
files, and can be used to study detailed energy consumption profiles.
Database
Each of the above items must be defined by the operator. This is a one time
process, most of which is done at the time of system installation. Subsequently
definitions usually get added or modified only when new devices are added to the
system, or when system changes are taken into account, such as changes in remote
unit model being used (new meter or RTU model, etc). Definition of each
item comes in several steps.
- First, a new database entry is made. This creates a record corresponding
to the item to be managed. For example, to import new meter data one
must define a new meter database entry. At that time, the
item is said to be off-line.
- In case of meters, a mapping onto appropriate I/O points
in RUEX needs to be made. A meter must be mapped onto an
appropriate counter (when
KYZ pulses are expected) or analog
point (when analog readings are available) in RUEX so
MREX knows where to find new demand figures when they come in.
- Next, the new item has to be 'put on-line'. MREX does not 'know' about the
new item until this step is performed. At that time MREX verifies the type,
location, and integrity of the database entry. If all tests are passed MREX creates a manager of appropriate type. (For those familiar with modern
software engineering jargon, MREX creates an object of appropriate class.)
From that time on MREX 'knows' about that item and maintains it by calling
functions exposed by the manager. At that point the item is said to be on-line.
Please click here to see how to
implement this.
Data Processing
Data processing is done by both, RUEX and MREX. The former does data
acquisition, handles pulse counter roll-overs, and computes intra-day time
stamps for downloaded energy consumption data based on assigned data recording
interval. MREX computes dial readings based on incoming pulse counter data,
and operator entered meter parameters. MREX also handles dial reading
roll-overs and dial reading calibrations.
Please click here to see how to implement this.
Data Recording
All meter dial readings are saved in standard RUEX NTMCRDR
files. Each meter reading dial value is stored, as well as the nature of the
reading (latest, billing, calibration).
MREX relies on RUEX to do RURDR
of all pulse counters associated with the meters. The downloaded pulses are
rescaled and stored as power consumption numbers into standard RUEX RURDR
files.
All of the above information can be reviewed, studied, or exported at any
time by using using MCDA.
Please click here to see how to implement this.
Data Archiving
All data recording files and event logs fill up after a while, and must be
archived to a separate location, either on the same computer, or elsewhere on
the LAN. This is done manually by
the operator who executes archiving commands. Two kinds of information get
archived: data recorded from remote units, and event logs. MREX does not
back up archived data recording files stored elsewhere on the computer (for
example, on a ZIP disk), or the LAN.
It is the user's responsibility to back those files up after each archiving
operation.
Please click here to see how to implement this.
Meter Reading
Three kinds of meter reading are supported: latest dial reads, billing reads,
and data downloads.
In the case of latest dial reads, remote units monitoring the meters get
polled for the latest pulse counter values. Dial readings are then computed
and saved in the database.
Billing reads are essentially latest dial reads. In addition, the dial
readings also get stored in another part of the database which does not change
until the next billing read. These values are available for data exports to
the billing department.
Data downloads are discussed in the next section.
Please click here to see how to implement this.
Meter Data Downloads
Meter data downloads are downloads of RURDR
data performed by remote units
at meter sites. Pulse count values are recorded by remote units at a regular,
operator specified interval, and stored. The data is downloaded to the master
computer once per day. The numbers get converted to energy consumed during the
previous interval, and stored in RUEX RURDR data recording files. The data can
then be studied using MCDA,
or exported for further study using other tools. Detailed energy consumption
profiles, and demand profiles can thus be obtained for every meter.
Please click here to see how to implement this.
Billing Data Exports
For any automated meter reading system it is not only important how to read
meters, but also how to export the collected data in the format useful to the
billing department. MREX provides facilities for scanning historic records of
some, or all meters, and placing the results into a file which can be read the
local billing program. Export file format customizations are available and
expected. Scanning historic data not only provides meter dial readings, but
also reading averages, information on reading extrema, etc.
Please click here to see how to implement this.
| 