Ea MS

EnergyAxis Management System Release 7.
6
User Guide TM42-3006D
www.elster.com
EA_MS Release 7.6 User Guide
Contents
Contents
New features in Rel. 7.6 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
Evaluation features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14 EA_MS documents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14 What is the EnergyAxis System? . . . . . . . . . . . . . . . . . . . . . . . . 14 EA_MS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15 EA_LAN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16 Home area network . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17 Standard features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17 Data format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17 Time-of-use metering . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18 Demand metering . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18 A3 ALPHA meters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18 REX and REX2 meters . . . . . . . . . . . . . . . . . . . . . . . . . . . 19 Interval metering . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19 A3 ALPHA meters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19 REX and REX2 meters . . . . . . . . . . . . . . . . . . . . . . . . . . . 19 Outage and restoration . . . . . . . . . . . . . . . . . . . . . . . . . . . 19 Meter data collection and reporting . . . . . . . . . . . . . . . . . . . 20 Reading previous registers . . . . . . . . . . . . . . . . . . . . . . . . 21 Configuration change data . . . . . . . . . . . . . . . . . . . . . . . . 21 Reading and reporting operational information . . . . . . . 21 Network management . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21 Line voltage data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22 Reading and reporting meter data . . . . . . . . . . . . . . . . . 22 Meter configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22 Data export and XML schema . . . . . . . . . . . . . . . . . . . . . 22 Time management in gatekeepers . . . . . . . . . . . . . . . . . . . . 23 Meter events, alarms and logs . . . . . . . . . . . . . . . . . . . . . . . 23 Reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24 Disconnecting and reconnecting service . . . . . . . . . . . . . . . 24 EA_MS data file partitioning . . . . . . . . . . . . . . . . . . . . . . . . . . 24 Web Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24 Other capabilities . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25
Understanding EA_MS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . About meters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . About accounts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . About schedules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . About TOU schedules . . . . . . . . . . . . . . . . . . . . . . . . . . About synchronization schedules . . . . . . . . . . . . . . . . About data sets . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Reading meters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Meter life cycle . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
26 26 28 28 28 29 30 30 33
Contents
Important information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36
Using the system . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .37 Data entry . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .37 Elster data entry restrictions . . . . . . . . . . . . . . . . . . . . . . . .37 Accessing the system . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38 Logging on . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38 About the EA_MS main window . . . . . . . . . . . . . . . . . . . . . . . 39 Changing start up page . . . . . . . . . . . . . . . . . . . . . . . . . . 40 Viewing the Elster website . . . . . . . . . . . . . . . . . . . . . . . . . 41 About the system dashboard . . . . . . . . . . . . . . . . . . . . . . . . . . 41 System activities . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41 Alarm conditions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42 User activities . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44 Using the work status indicator . . . . . . . . . . . . . . . . . . . . . . . 46 Detecting errors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .47 Viewing an activitys information . . . . . . . . . . . . . . . . . 48 Viewing alarm conditions . . . . . . . . . . . . . . . . . . . . . . . . . 48 Using buttons . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48 Searching . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50 Exact matches . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50 Filtered lists . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50 Refreshing the user interface display . . . . . . . . . . . . . . . . . . . . 51 Selecting a date and time . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51 Using time zones . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53 Processing error messages . . . . . . . . . . . . . . . . . . . . . . . . . . 53 Viewing sorted lists . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54 Viewing PDFs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54 Using Help . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55 Configuring EA_MS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60 Configuring event and alarm panels . . . . . . . . . . . . . . . 60 Configuring schedules panels . . . . . . . . . . . . . . . . . . . . . . 61 Configuring EA_MS favorites list . . . . . . . . . . . . . . . . . . . . 61 Logging off . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63
Getting started. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64 Installing meters and devices . . . . . . . . . . . . . . . . . . . . . . . . . 64 Installing a gatekeeper . . . . . . . . . . . . . . . . . . . . . . . . . . . 64 Installing a node device . . . . . . . . . . . . . . . . . . . . . . . . . . 64 Create data sets . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65 Creating schedules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66 Schedule run times . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66 A schedule for billing data . . . . . . . . . . . . . . . . . . . . . . . . 66 A3 ALPHA meters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66 REX/REX2 meters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66 A schedule for synchronizing . . . . . . . . . . . . . . . . . . . . . . 66 A schedule for reading voltage . . . . . . . . . . . . . . . . . . . . 66 Assigning meters and devices to data sets and schedules .67
Electricity metering . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68 Actions and reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68 Retrieving a meter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68 Viewing a meters information . . . . . . . . . . . . . . . . . . . . . . . . . 71 Changing a meters information . . . . . . . . . . . . . . . . . . . . . . .79 Changing schedule assignments . . . . . . . . . . . . . . . . . . . . . 80
Contents
Installing a meter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81 Assigning billing determinants . . . . . . . . . . . . . . . . . . . . . . . . . 81 Assigning a gatekeeper to a synchronization schedule . . . . 81 Removing a billing determinant from a meter . . . . . . . . . . . 82 Changing a meters schedule assignment . . . . . . . . . . . . . . 82 Adding a new meter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85 Adding multiple new meters . . . . . . . . . . . . . . . . . . . . . . . . . 90 Removing a meter from the field . . . . . . . . . . . . . . . . . . . . . . 90 Deleting a meter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 92 Pinging a meter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 93 Performing an on request read of a meter . . . . . . . . . . . . . . 95 Performing a health check on a meter . . . . . . . . . . . . . .104 Reading meter time . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 107 Reading a meters configuration . . . . . . . . . . . . . . . . . . . . . .108 Setting a meters time . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 110 Performing advanced metering functions . . . . . . . . . . . . . . . 111 Performing a special read for billing . . . . . . . . . . . . . . . . . . .120 Connecting a meters service . . . . . . . . . . . . . . . . . . . . . . . . .126 Disconnecting a meters service . . . . . . . . . . . . . . . . . . . . . . .130 Importing a marriage file . . . . . . . . . . . . . . . . . . . . . . . . . . . .134 Importing a CIS file . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .136 Importing a WIC activation file . . . . . . . . . . . . . . . . . . . . . . . . 137 Performing a power status check . . . . . . . . . . . . . . . . . . . . .138 Meter Readings Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .138 Display Meter Readings . . . . . . . . . . . . . . . . . . . . . . . . . . 141 Viewing Load Profile Data . . . . . . . . . . . . . . . . . . . . . . . .148 Meters Not Read Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . .155 Meter Events Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .156 Meter Alarms Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .159 Meter Statuses Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 161 Meter Inventoried Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . .164 Meter Installed Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .166 Meter List Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .168 Component Mismatch Report . . . . . . . . . . . . . . . . . . . . . . . . 170 Meters Disconnected Report . . . . . . . . . . . . . . . . . . . . . . . . . 170
Water metering . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 172 Reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 172 About Water Metering . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 172 Viewing a water meters readings . . . . . . . . . . . . . . . . . . . . . 173 Viewing the unknown water nodes report . . . . . . . . . . . . . . 173 Viewing a gatekeepers water nodes report . . . . . . . . . . . . 175 Viewing a gatekeepers water meters reading history . . . . 177 Viewing the Water Interval Threshold report . . . . . . . . . . . . . 178 Viewing the Water Leak report . . . . . . . . . . . . . . . . . . . . . . . .180
Gas metering. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .183 Reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .183 About gas metering . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .183 Viewing a gas meters readings . . . . . . . . . . . . . . . . . . . . . .184 Viewing the unknown gas nodes report . . . . . . . . . . . . . . . .186 Viewing a gatekeepers gas nodes report . . . . . . . . . . . . . .188
Contents
Viewing a gatekeepers gas meters reading history . . . . . .190
Data Set . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .192 Actions and reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .192 Retrieving a Data Set . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .192 Viewing a list of all data sets . . . . . . . . . . . . . . . . . . . . . . . . .193 Changing data set assignments . . . . . . . . . . . . . . . . . . . . . .194 Creating a data set . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .195 Deleting a data set . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 203
Schedule . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 204 Actions and reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 204 Retrieving a Schedule . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 204 Viewing a list of all schedules . . . . . . . . . . . . . . . . . . . . . . . . 206 Schedule Dashboard . . . . . . . . . . . . . . . . . . . . . . . . . . . 209 View Schedule Information Report . . . . . . . . . . . . . . . . .210 Performance Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . .213 Voltage Reading Performance reports . . . . . . . . . . . . . .221 Using the Schedule Explorer . . . . . . . . . . . . . . . . . . . . . . . . . 232 Resubmitting a Schedule . . . . . . . . . . . . . . . . . . . . . . . . . . . 235 Modifying a Schedule . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 237 Exchanging Schedules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 240 Creating a schedule . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 242 Creating a new schedule . . . . . . . . . . . . . . . . . . . . . . . . 245 Creating a billing schedule for REX meters . . . . . . . . . 249 Creating a synchronization schedule . . . . . . . . . . . . . . 249 Creating a voltage reads schedule . . . . . . . . . . . . . . . . 252 Deleting a schedule . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 252
10 TOU Schedules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Actions and reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . About TOU Schedules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Creating the TOU program . . . . . . . . . . . . . . . . . . . . . . . About non-TOU schedules . . . . . . . . . . . . . . . . . . . . . . . TOU schedules and meter display . . . . . . . . . . . . . . . . Viewing a list of all TOU schedules . . . . . . . . . . . . . . . . . . . Changing TOU schedule assignments . . . . . . . . . . . . . . . . Importing TOU schedules . . . . . . . . . . . . . . . . . . . . . . . . . . . Overwriting the default TOU schedule . . . . . . . . . . . . . Deleting a TOU schedule . . . . . . . . . . . . . . . . . . . . . . . . . . .
254 254 254 254 255 255 256 259 260 263 264
11 Demand response . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 266 Actions and reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 266 About demand response . . . . . . . . . . . . . . . . . . . . . . . . . . . 267 About demand response groups . . . . . . . . . . . . . . . . . 268 Managing home area devices . . . . . . . . . . . . . . . . . . . . . . . 269 Commissioning HADs . . . . . . . . . . . . . . . . . . . . . . . . . . . 270 Decommissioning HADs . . . . . . . . . . . . . . . . . . . . . . . . 270 Adding a new HAD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 270 Creating a Demand Response Group . . . . . . . . . . . . . . 271 Assigning a HAD to a meter . . . . . . . . . . . . . . . . . . . . . . 271 Removing a HAD from a meter . . . . . . . . . . . . . . . . . . . 272 Removing a HAD from a meter using CIS Import . . . . 273 Assigned HAD listing . . . . . . . . . . . . . . . . . . . . . . . . . . . 274
Contents
Unassigned HAD listing . . . . . . . . . . . . . . . . . . . . . . . . . 275 Pricing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 275 Creating a Price . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 276 Modify Pricing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .277 Clear Pricing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 279 Assign Pricing to meter . . . . . . . . . . . . . . . . . . . . . . . . . . 280 HAN Pricing reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . 280
All . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 282 Confirmed . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 282 Unconfirmed . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 283

Messaging . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 283 Creating a message . . . . . . . . . . . . . . . . . . . . . . . . . . . . 283 Cancelling a message . . . . . . . . . . . . . . . . . . . . . . . . . . 286 Messaging reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 287 All . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 289 Delivered . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 289 Undelivered . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 290 Confirmed by User . . . . . . . . . . . . . . . . . . . . . . . . . . . . 290 Unconfirmed by User . . . . . . . . . . . . . . . . . . . . . . . . . .291 Pending Cancel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .291 Controlling HAD devices . . . . . . . . . . . . . . . . . . . . . . . . . . . . .291 Emergency management . . . . . . . . . . . . . . . . . . . . . . . 292 Creating and assigning an EM or LCE event . . . . . . . 292 Cancelling an EM or LCE event . . . . . . . . . . . . . . . . . . 295 Emergency management reports . . . . . . . . . . . . . . . . . 296 Confirmed by Device . . . . . . . . . . . . . . . . . . . . . . . . . . 296 Unconfirmed by Device . . . . . . . . . . . . . . . . . . . . . . . . 297 Overridden By User . . . . . . . . . . . . . . . . . . . . . . . . . . . 297 Home Area Network Events report . . . . . . . . . . . . . . . . . . . 298 Exporting to PDF file . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .301 Exporting to CSV file . . . . . . . . . . . . . . . . . . . . . . . . . . . . 302 Commissioned/Decommissioned reports . . . . . . . . . . . . . 303 Confirmed by Device . . . . . . . . . . . . . . . . . . . . . . . . . . . . 303 Unconfirmed by Device . . . . . . . . . . . . . . . . . . . . . . . . . 305 History by Meter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 306 Legacy support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 307 Creating Elster Pricing . . . . . . . . . . . . . . . . . . . . . . . . . . . 307 Elster Pricing reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . 308 Elster Pricing Configuration report . . . . . . . . . . . . . . . 308 Elster Pricing Synchronization report . . . . . . . . . . . . . 309 Energy conservation . . . . . . . . . . . . . . . . . . . . . . . . . . . . .310 Creating an energy conservation event . . . . . . . . . . .310 Assigning an EC event to a TOU schedule . . . . . . . . .312 Assigning an EC event to a meter . . . . . . . . . . . . . . . .313 Energy conservation event listing . . . . . . . . . . . . . . . . .313 Viewing EC event settings . . . . . . . . . . . . . . . . . . . . . . .313
12 Critical tier overrides . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .315 Actions and reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .315 Critical tier overrides . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .315 Creating a critical tier override . . . . . . . . . . . . . . . . . . . . . . . .315 CTO listing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .316
13 Configuring elements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .318 Supported devices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .318 Actions and reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .318 Adding a configuration profile . . . . . . . . . . . . . . . . . . . . . . . .318 Assign a configuration profile . . . . . . . . . . . . . . . . . . . . . . . . 320
Contents
Removing a configuration profile . . . . . . . . . . . . . . . . . . . . . Reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Viewing all configuration profiles . . . . . . . . . . . . . . . . . Viewing configuration profiles on a meter . . . . . . . . . . Viewing meters on configuration profile . . . . . . . . . . . .
322 323 323 324 324
14 Reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 326 Reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 326 See Also . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 326 Meter Communication Summary Report . . . . . . . . . . . . . . . 327 Gatekeeper LAN Protocol Report . . . . . . . . . . . . . . . . . . . . . .331 Associated Nodes Report for Gatekeeper . . . . . . . . . . . . . . 333 Troubleshooting REX Meters . . . . . . . . . . . . . . . . . . . . . . . . . 337 Synchronization Summary Report . . . . . . . . . . . . . . . . . . . . 342 Node Jumping History Report . . . . . . . . . . . . . . . . . . . . . . . . 345 REX Communication Report . . . . . . . . . . . . . . . . . . . . . . . . . 347 Pending Synchronization Report . . . . . . . . . . . . . . . . . . . . . 350 LAN Information Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .351 LAN Performance Threshold . . . . . . . . . . . . . . . . . . . . . . . . . 355 Network Capacity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 356 User Audit Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 357 CIS Import Audit Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 360 Marriage File Import Audit Report . . . . . . . . . . . . . . . . . . . . 363 Firmware Version Summary report . . . . . . . . . . . . . . . . . . . 366 Firmware Upgrade Job Listing Report . . . . . . . . . . . . . . . . . 367 Firmware Upgrade History Report . . . . . . . . . . . . . . . . . . . . 368 Firmware Upgrade Failure History . . . . . . . . . . . . . . . . . . . . 370 Customizing a report layout . . . . . . . . . . . . . . . . . . . . . . . . . . 371 Using column selection . . . . . . . . . . . . . . . . . . . . . . . . . . 371 Using column data filters . . . . . . . . . . . . . . . . . . . . . . . . 373
15 Administration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Administration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Viewing a list of all users . . . . . . . . . . . . . . . . . . . . . . . . . . . . Changing a Users Information . . . . . . . . . . . . . . . . . . . Adding a new user . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Changing a user password . . . . . . . . . . . . . . . . . . . . . . . . . Viewing your account information . . . . . . . . . . . . . . . . . . . . Editing Your Account . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Deleting a User . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Creating a user based on another users profile . . . . . . . . Security Administrator . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
374 374 374 376 376 383 383 385 386 386 387
16 Network Management. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 388 Optimizing a gatekeepers LAN . . . . . . . . . . . . . . . . . . . . . . 388
A Glossary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 390
Sample Files. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 400 Sample Marriage files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 400 REX meter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 400
Contents
A3 ALPHA node . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 400 REX meter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 400 REX2-EA meter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .401 Water module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .401 Gas module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .401 EA_Repeater . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .401 Sample WIC activation file . . . . . . . . . . . . . . . . . . . . . . . . . . . 402 Example CIS files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 402 Example 1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 402 Example 2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 449 About InHomeDevice object . . . . . . . . . . . . . . . . . . . . . 455 About ProvisionInHomeDevice object . . . . . . . . . . . . . . 455 About ThermostatConfigToMeter object . . . . . . . . . . . . 456
Events and statuses . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Events and statuses . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Common Meter Statuses . . . . . . . . . . . . . . . . . . . . . . . . Common Meter Events . . . . . . . . . . . . . . . . . . . . . . . . . . A3 ALPHA meter events and statuses . . . . . . . . . . . . . . . . . A3 ALPHA Meter Statuses . . . . . . . . . . . . . . . . . . . . . . . A3 ALPHA Meter Events . . . . . . . . . . . . . . . . . . . . . . . . . REX/REX2 meter events and statuses . . . . . . . . . . . . . . . . . REX/REX2 Meter Statuses . . . . . . . . . . . . . . . . . . . . . . . . REX/REX2 Meter Events . . . . . . . . . . . . . . . . . . . . . . . . . EA_Water meter events and statuses . . . . . . . . . . . . . . . . . EA_Water Meter Statuses . . . . . . . . . . . . . . . . . . . . . . . . EA_Water Meter Events . . . . . . . . . . . . . . . . . . . . . . . . . . EA_Gas meter statuses and events . . . . . . . . . . . . . . . . . . . EA_Gas Meter Statuses . . . . . . . . . . . . . . . . . . . . . . . . . EA_Gas Meter Events . . . . . . . . . . . . . . . . . . . . . . . . . . . A3 ALPHA meter with EA_NIC events and statuses . . . . . . A3 ALPHA meter with EA_NIC Statuses . . . . . . . . . . . . . A3 ALPHA meter with EA_NIC Events . . . . . . . . . . . . . . WIC Statuses and Events . . . . . . . . . . . . . . . . . . . . . . . . . . . . WIC Statuses . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . WIC Events . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A3 ALPHA meter and gatekeeper status descriptions . . . . REX/REX2 status descriptions . . . . . . . . . . . . . . . . . . . . . . . .
457 457 458 458 459 459 463 467 467 469 472 472 472 473 473 473 473 473 476 478 478 479 480 489
D Voltage reading statuses . . . . . . . . . . . . . . . . . . . . . . . . . . . . 494
Reading components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 496 Registers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 496 Load Profile . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 497 HTML report of Load Profile . . . . . . . . . . . . . . . . . . . . . . 497 Demand Reset . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 498 Events and Exceptions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 499 Reset A3 Events . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 500 LAN Performance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .501 Reset Communication statistics . . . . . . . . . . . . . . . . . . . . . . 502 Registers from Gatekeeper . . . . . . . . . . . . . . . . . . . . . . . . . . 502 Read and Clear Water Data from Gatekeeper . . . . . . . . . . 503 Read and Clear Gas Data from Gatekeeper . . . . . . . . . . . . 503 Load Profile from Gatekeeper . . . . . . . . . . . . . . . . . . . . . . . . 504 HTML report of Load Profile from Gatekeeper . . . . . . . 504
10
Contents
Clear A3 Statuses . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 505 Clear Sag Statuses . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 505 Load Profile (last 24 hrs) . . . . . . . . . . . . . . . . . . . . . . . . . . . . 506 HTML report of Load Profile (last 24 hours) . . . . . . . . . . 506 Sag Log . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 507 Sag Log Counter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 508 Load Profile (last one week) . . . . . . . . . . . . . . . . . . . . . . . . . 508 HTML report of Load Profile (last one week) . . . . . . . . . 509 ICMP Ping . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 509 Present Values . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .510 Health Check A3 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 511 Health Check ILC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 511 Health Check WIC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .512 ICMP Ping . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .513 ICMP Traceroute . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .513
11
New features in Rel. 7.6
New in Rel. 7.6

Meters supported
EA_Gatekeeper FW v 6.0 - with A3 ALPHA meter-packaged or an AGI-packaged device supports 2048 REX or REX2 meters support 2048 water and gas meters
Note: Total number or end points supported depends on the configuration of LAN meters and EA_LAN Mode configuration.
supports maximum of 750 A3 ALPHA meters with EA_NIC supports up to 16 levels of meters in a gatekeepers EA_LAN in LAN Mode 2 support for A3 ALPHA meter FW v 4.0 with WIC FW v 3.0 supports EA_LAN Mode 2 support for EA_Repeater (please contact Elster for details) REX2 meter FW v 3.0 EA_LAN Mode 2 supports event-only load profile data supports real, apparent, and reactive metering REX meters
Compatibility
While EA_MS is backward compatible with prior versions of the REX meter (1.x, 2.x, etc.), it does require that any gatekeepers be upgraded to firmware v 4.1 or higher. While EA_MS is backward compatible with earlier firmware versions of the A3 ALPHA meter with EA_NIC (FW ver. 1.0) in reading demand and energy data, to support TOU and season changes, A3 ALPHA meters with EA_NIC must be upgraded to FW v 2.0. Contact Elster for additional information.
Demand response
EA_MS 7.6 expands on demand response from MAS 6.0 and 6.2 including: supports the ability enable/disable broadcast functionality in REX and REX2 meters for support of 900 MHz IHDs adding support for commissioning of SEP 1.0 compliant HAN devices adding support for sending ZigBee SEP 1.0 pricing commands extending support for specifying utility enrollment group and randomization parameters for load control commands adding ability to send a message to a list of meters providing broadcast capability for load control, messaging and pricing commands
12
Voltage readings
EA_MS 7.6 supports reading voltage on a schedule basis or via On-Request-Read with the use of a Voltage component. See Chapter 8, Data Set for details. Voltage Read Performance - data elements provide the ability to read voltage from up to 50 meters registered to a EA_Gatekeeper FW 6.0 on a scheduled basis as often as five minute intervals. See Chapter 9, Schedule for details.
LAN Mode
With the release of the EA_Gatekeeper FW v 6.0 or later, a gatekeeper can support up to 16 levels of hops at a data rate of 142 kbps. This expansion of support is provided by LAN Mode 2. Contact EnergyAxis Support for more information.
EA_LAN encryption
With the release of the EA_Gatekeeper FW v 6.0 or later, a gatekeeper can encrypt EA_LAN radio-frequency communications. This feature can be enabled and disabled by the EA_MS Security Administrator. Refer to the EA_MS Installation and Administration Guide for details.
13
Evaluation features
About evaluation features

The following features and functions are evaluation features only. They are included in this release to obtain customer suggestions and recommendations. Evaluation features have not been fully tested for commercial release. A future release will provide fully tested features.
MDM/R integration
To enable meter data management/repository (MDM/R) integration, EA_MS allows time zones in the meter reading data packaged in the EA_MS AMRDEF file to be converted (for example, from GMT to local time). In particular, the time zone conversion of meter reading time stamps packaged in the reading files is subject to user control as described in the EA_MS Installation and Administration Guide. The evaluation feature allows EA_MS to be configured to deliver an AMRDEF file with all time stamps converted to the specified time zone. The DST correction to be applied during the conversion is configured independently (see the EA_MS Installation and Administration Guide).
Note: The default behavior of EA_MS is to package the converted time stamps without a time zone abbreviation.
System Dashboard
To view the System Dashboard, from the Activity Monitor menu, select System Dashboard. Refer to PG42-1025 EnergyAxis Dashboards for details on using the dashboards.
Note: Only System Administrators can view or use the System Dashboard.
14
1. Introduction
Introduction
EA_MS documents
Other documentation for the EnergyAxis Management System (EA_MS) may be found on the EA_MS Documentation CD-ROM. The Documentation CD contains the following documents: EA_MS Installation and Administration Guide EA_MS Backup and Recovery Guide EA_MS JSlinger Administration Guide EA_MS AMRDEF Reference EA_MS Release Notes
Note: To read the above documents you must have Adobe Reader installed. You can download the latest version of Adobe Reader from http://www.adobe.com.
What is the EnergyAxis System?

The EnergyAxis System (Figure 1-1) is designed for residential and commercial and industrial (C&I) metering automation. It is composed of up to three parts: 1. EnergyAxis Management System (EA_MS) 2. One or more gatekeepers and up to 1024 or 20481 of the following meters per gatekeeper: REX, REX2 and gREX meters equipped with the EnergyAxis network interface card (EA_NIC) optional service control switch for remote disconnection/reconnection A3 ALPHA meters with the EA_NIC2 2048 water and gas meters (equipped with EA_Water Module and EA_Gas Module) AGInodes equipped with the EA_NIC 3. Optional home area network (HAN) composed of a REX2 meter with ZigBee communications option board and one or more ZigBee-enabled home area devices (HAD) - for example, programmable thermostat, in-home display, or load control device. Each gatekeeper gathers and stores meter data from its registered meters and manages the 900 MHz RF LAN (EA_LAN). These gatekeepers upload the data to the EnergyAxis Management System (EA_MS) via a public or private WAN either on a scheduled or ondemand basis.
repeaters3 that relay meter data from downstream, or descendant, meters up to the
In standard EA_LAN mode, each REX, REX2 and A3 ALPHA meter with EA_NIC can act as gatekeeper. When a repeaters RF transmission capability is blocked, the gatekeeper
1. EA_Gatekeeper FW 6.0 or later. 2. EA_Gatekeeper FW 6.0 or later supports a maximum of 750 A3 ALPHA meters with EA_NIC. 3. In EA_LAN Mode 2, devices capable of Mode 1 operation only may not register as repeaters in the EA_LAN.
15
1. Introduction
determines that something is wrong and initiates a node scan. The node scan re-builds the LAN and re-routes communication paths thereby bypassing the faulty node. In this manner, the network is called self-healing.
Figure 1-1. EnergyAxis System
EA_MS
The EA_MS is the server (or head-end) component of the EnergyAxis System. EA_MS automates data collection and other processes for devices or elements accessed remotely over public WAN for both C&I and residential applications.
16
1. Introduction
EA_MS supports utility business processes for billing, demand response, revenue protection, customer service, asset management, distribution automation and load management. Additionally, it implements key network management and operational reporting functions for the network of gatekeepers and their wireless network of end-point devices. EA_MS collects element readings on either a schedule or on request using the browserbased user interface. The EA_MS user interface requires Internet Explorer Rel 6.0, 7.0 or 8.0 and Adobe Flash 10.0 so that it can be accessed by authorized personnel on the intranet. The computer monitor should have a minimum screen resolution 1024 x 768. All billing data is read from the meter; this includes interval data channels, consumption, demand, time-of-use registers as well as meter status flags. EA_MS delivers collected data in text files that use an open XML format, AMRDEF (AMR data exchange format). This XML format allows the exchange of data between EA_MS and other enterprise systems (for example, billing and CIS) which can be implemented by in-house IT personnel. Refer to the EA_MS AMR Data Exchange Format Reference for details.
EA_LAN
In the EnergyAxis System, A3 ALPHA meters with gatekeeper modules and EA_Gatekeepers manage and communicate with end-point elements (that is, REX and REX2 meters with EA_NIC, A3 ALPHA meters with EA_NIC, gas and water meters with EA_Water module and EA_Gas module), AGInodes, etc.) through a 900 MHz LAN (EA_LAN). In LAN Mode 2, each gatekeeper is capable of managing a network of up to 2048 electricity and 2048 gas and water meters (the actual number depends on meter densities, meter mix, and enabled capabilities). Additionally, EA_MS reads data and performs operations on these devices through the gatekeepers.4 Since a meter-based gatekeeper itself can be used to meter a site, the data read from the meter can include both data from the meter-based gatekeeper as well as data from any A3 ALPHA, REX, REX2, gREX, A1800 ALPHA, gas and water meters registered to the gatekeeper. EA_MS can also perform pass-through operations (such as service disconnect and connect) and on request reads of meters using the gatekeeper to communicate with specific meters.5 The elements communicate with their registered gatekeeper through the two-way EA_LAN. The gatekeeper, in turn, is responsible for performing the following actions: reading and storing the billing data from each element on a periodic basis reading and storing the load profiling data from a configurable number of elements on a periodic basis reporting the billing and load profiling data back to EA_MS notifying the elements to perform demand resets based on a schedule from EA_MS reading and storing the previous billing period data from elements after a demand reset has occurred notifying the meters to perform season changes based on a schedule from EA_MS reading and storing the previous season data from meters after season changes have occurred6 synchronizing the elements to the system time and TOU day type distributing TOU rate schedules to the REX and REX2 meters reading or sending commands to an individual element on command from EA_MS performing other network maintenance tasks
4. Data is read from the gatekeeper via telephone, RS-232, etc. 5. Except for EA_Water modules Rel. 1.0 meters which can only transmit data to the gatekeeper. 6. REX and REX2 meters only.
17
1. Introduction
Home area network

For demand response, REX2 meters equipped with the ZigBee communication option board can communicate with a variety of home area network (HAN) devices, for example, programmable communicative thermostats (PCTs), load control (LC) devices, and in-home displays.
Modem virtualization
Modem virtualization provides better modem resource management capabilities for the EA_MS environment. It handles the communication resources efficiently, minimizes the total cost by eliminating dedicated and duplicate hardware and software resources. It creates and works on a virtual and shared environment. It is also a scalable solution (up to 4,096 virtual comm ports) for future expansion. EA_MS supports modem virtualization as provided by a Cisco Remote Access Server and the accompanying virtual COM port driver. The supported behavior is as follows: EA_MS allows the periodic line check to be disabled for virtual telephone lines EA_MS allows the periodic modem initialization to be disabled for virtual telephone lines EA_MS opens and closes the serial port as needed for virtual telephone lines. For EA_MS, all telephone lines are either virtual or real.
Note: Combinations of real and virtual lines are not supported. Since combinations of virtual and real lines are not supported, customers using virtualized modems in EA_MS will not be able to support call-in from telephone meters.
Real lines will continue to stay open all the time and have the same behavior as today. For additional information, refer the supporting documentation for the Modem Virtualization software located on the Modem Virtualization CD.
Optimizing the 900 MHz network

The Optimize LAN functionality added in EA_MS allows users the ability to optimize a gatekeeper's local area network registration threshold based on the density of the network to enable registrations at various qualification thresholds.
Support for static IP addresses

EA_MS supports gatekeepers with wireless WAN interface card (W-WIC) CDMA and GPRS, Ethernet WIC (E-WIC) or RS-232 having an assigned static IP address.
Email notification of alarms

EA_MS supports email notification of alarms and events. Using this feature, you can configure EA_MS to email you when such conditions occur. You can also have EA_MS email you when a schedule completes if schedule performance is below or equal to the schedule performance threshold value.
Standard features
Data format
A3 ALPHA meters FW v 2.x with EA_NIC can be programmed to collect data in one of two data formats: short data format returns kWh consumption data, time of use, two userselected tiers of maximum demands and total demand without time stamps
18
1. Introduction
long data format
returns two metered quantities, time of use, all tier cumulative or maximum demands with time stamps, identification information for 2 channels of load profiling, and 2 channels of interval data to the gatekeeper. This format can also includes support for kQ metering and the configuration of power factor as a coincident demand.
Note: This format uses more data that takes longer to read and more memory to store in the gatekeeper. Elster recommends that the long data format be utilized for all applications except those fulfilled using A3D styles (generally energy and demand applications that do not require time of maximum demand).
A3 ALPHA meters FW v 3.x and higher with EA_NICs can be programmed to collect data that returns two metered quantities, time-of-use, all tier cumulative or maximum demands with time stamps, identification information for 2 channels of load profiling, and 2 channels of interval data to the gatekeeper. They can also be programmed to support kQ metering and the configuration of power factor as a coincident demand.
Time-of-use metering
Time-of-use (TOU) rates allow a utility to charge the customer different amounts for energy and demand usage at different times of day and different times of year. When TOU is performed in the meter, the meter contains a TOU schedule that defines how energy and demand should be reported to support these charges. The TOU schedule includes definitions of different day types (such as weekday, weekend, special dates, and switch times) in different seasons, and when seasons change. It also includes holiday definitions.
A3 ALPHA meters
Using Elster Metercat software, you can program A3 ALPHA meters (whether or not they are gatekeepers) to support TOU metering. Once the meter has been programmed for TOU, EA_MS will retrieve the time-of-use data from the meter through the gatekeeper.
Note: A3 ALPHA meters are not assigned to TOU schedules in EA_MS. Gatekeepers automatically read the TOU data from registered meters.
Refer to the Metercat User Guide for details on programming an A3 ALPHA meter for TOU metering.
REX and REX2 meters

EA_MS allows you to import a TOU program that was created in Elsters Metercat software. Once the TOU program is created in Metercat, export the program to a PED file (program exchange document). Import the PED file into EA_MS. Once the TOU program has been imported into EA_MS, the new TOU schedule is available for assigning REX and REX2 meters and synchronizing to gatekeepers. The system enables users to setup schedules for synchronizing of TOU schedules, and other information on a periodic basis. For example, an imported TOU program is defined with demand_1 as total demand and demand_2 as rate A demand. All REX and REX2 meters that are programmed to support total demand and rate A demand are then assigned to the TOU schedule. See Chapter 10, TOU Schedules for additional information.
Demand metering
A3 ALPHA meters
EA_MS can support the full set of demand metering capabilities for A3 ALPHA meters. A3 ALPHA meters (with EA_NIC) may be programmed to either collect two demand values plus total demand or all tiered demands with time stamps (this format also enables support for coincident demand).
19
1. Introduction
REX and REX2 meters

REX meters may be programmed to collect two demand values (Total and one tier - TierA, Tier B, Tier C, or Tier D); REX2 meters may be programmed to collect three demand values (Total, and two tiers - Tier A, Tier B, Tier C, or Tier D). The marriage file for the meter will detail the demand values and EA_MS will show the demand values in the reading file.
Total demand for REX meters

Total demand for REX meters is calculated as follows: For REX meters with FW version 1.x, EA_MS calculates and reports Total value as the sum of the tiers. For REX meters with FW version 2.x, EA_MS reports the Total value that is calculated in the REX meter. For REX2 meters, EA_MS reports the Total value that is calculated in the REX2 meter.
Note: Depending on the number of significant digits after the decimal, the sum of individual tiers (as displayed in EA_MS) may not equal the Total usage (as calculated by the REX meter).
Interval metering
For the initial schedule execution in EA_MS 6.0 or higher, reading LP through a EA_Gatekeeper FW 4.0 or higher, EA_MS uses the optimized LP retrieval mechanism to request LP data for all meters. On resubmits, or for On Request Reads of LP from the gatekeeper, EA_MS uses the one-ata-time method. This means that if the initial reading failed, or if individual meters failed (because there was no new data for them, for example), on the resubmit, the old mechanism would be used to get the data one meter at a time.
A3 ALPHA meters
EA_MS can support the full set of interval metering capabilities for A3 ALPHA meters with internal telephone modem (Rev. 3) [ITM3] and gatekeepers. A3 ALPHA meters with EA_NICs may be programmed to support up to two channels of interval metering. Although the meter may be configured for load profile, the gatekeeper will not retrieve load profile data by default. Interval metering is turned on through EA_MS by assigning the meter to a data set that includes load profile as a data component. Once interval metering is turned on, the gatekeeper and EA_MS will collect one or both channels, depending on meter configuration.
REX and REX2 meters

All REX meters come from the factory with the ability to perform interval metering of kWh data. The REX2 meter can measure two channels of interval data. The gatekeeper and EA_MS will start recording this data only if interval metering is turned on through EA_MS by scheduling the REX and REX2 meter for collection of interval data through a data set that contains the load profile data component (see Creating a data set on page 195 for details).
Outage and restoration

REX2 meters and A3 ALPHA meters with EA_NICs (FW 3.0 and FW 4.0) have the capacity to broadcast a last gasp outage notification. This ability is dependent on the supercapacitor charge on the EA_NIC and the outage status of any repeaters in receiving range. The repeaters relay the outage notification up to their registered gatekeepers which then reports the outage notices to EA_MS. EA_MS can be configured to relay these outage notices to an outage management system or other system.
20
1. Introduction
Figure 1-2.
When power is restored, the system works in the manner for restoration notification without the dependence on the supercapacitor charge.
Meter data collection and reporting

EA_MS allows users to collect metered data either on a scheduled basis or on request. Scheduled reads can be set up to read data at almost any frequency (monthly, weekly, daily, etc.) that is required by an upstream application. From a data collection and reporting perspective, EA_MS allows the following: request data for a specific REX or REX2 meter regardless of whether the original read request was initiated to the REX or REX2 meter or the gatekeeper request data for a specific water meter despite the fact that the original read request for water data was initiated to a gatekeeper request data for a meter over a time range that spans both on request reads and scheduled reads view a summary of the load profile information for a specific meter and only view intervals if needed view and retrieve data for individual meters in a scheduled reading file one at a time view and retrieve data for individual water meters in a scheduled reading file by gatekeeper view meter readings, schedule readings and schedule executions ordered by most recent first Operational information on the state of the network and meters (including meter status information) is read during every communication session with the gatekeeper and the most recent values are stored in the EA_MS database for the purposes of tracking and reporting.
21
1. Introduction
Reading previous registers

Previous registers are read under the following circumstances: Conditions must be met for data to be read Data read Previous Season Previous Period Billing read (scheduled or on request) Y1 Y2 On request read Y Y Data collection read N N
1. Only if REX meter or A3 ALPHA meter with EA_NIC is on a TOU rate and a season change occurred since last billing read. For EA_Gatekeepers in A3 ALPHA meters, season change data is read with every billing read. 2. Meter is on a demand rate or a TOU-demand rate.
Configuration change data

Whenever a REX meters TOU schedule assignment or its configuration has changed, a snapshot of the current period data is copied to configuration change data and is later read by the meters gatekeeper. Additionally, the configuration change data is read on the next billing schedule and during on request reads. Configuration change data is retrieved by EA_MS when the gatekeeper is read.
Reading and reporting operational information

EA_MS stores the most recent values for reporting purposes. By default, only abnormal statuses that correspond to Meter Health and Tamper Alert alarms (that is, alarms that potentially affect billing data) are reported in the AMRDEF XML file and online. All the other statuses and warnings are available through EA_MS reports and can also generate events when values are abnormal. Most meter statuses can be configured to trigger alarm notifications for abnormal values. Additionally, important events such as outages, restorations, meter health, etc. can be configured for alarm notification to the system administrator (Activity Monitor > Alarm Conditions7).
Note: If needed, all statuses can be read and reported in the AMRDEF file via a system configuration change. Elster does not recommend this configuration for normal system operation.
Outage and restoration information may be sent to an external system using the MultiSpeak outage detection (OD) Web Service interface. See the EA_MS Installation and Administration Guide for more details. Using the Power Status Check command (see Performing a power status check on page 138) the user can determine the status of a meter: Powered On Powered Off
Note: Meters would be reported as Off when A3 ALPHA meters and REX2 meters with last gasp capability notify the gatekeeper of an outage.
No-response - meter was pinged but there was no response Indeterminate - meter could not be pinged /communicated to (perhaps a repeater is out)
Network management
There are several reports for helping in network management. You can view this information in the LAN Information Report. The history of LAN performance for a specific meter is available in the REX Communication Report. On request reads of LAN 7. Refer to the EA_MS Installation and Administration Guide for details on configuring Alarm Notification.
22
1. Introduction
performance data from the gatekeeper can be used to read and report the most recent performance information online (for example, number of attempts, number of successes, % success, etc.). Additionally, the LAN Performance Threshold report shows the communication threshold information for the 900 MHz LAN. The Network Capacity report provides an indication of how loaded the EA_LAN is, and how gatekeepers are configured in terms of memory allocation one-way meters, etc. The information provided can be used in determining gatekeeper placement and configuration as well as meter configuration to ensure network efficiency. Additionally, with the availability of the EA_MS GIS option, some of the information available for meters (such as, level of the element in the graph, etc.) can be geographically represented. Information displayed includes meter location, number of hops to a gatekeeper, outages, and communication problems.
Line voltage data

EA_MS reads and records line voltage data for electricity meters. The line voltage is the root mean squared (RMS) of the per phase voltage at the time of meter reading.
Reading and reporting meter data

An on request read of a gatekeeper will show all the data retrieved in that communication session, including all requested gatekeeper register data for registered REX. REX2, and A3 ALPHA meter with EA_NIC and gas and water meters as requested. Likewise, viewing the Meter Readings Report for a previous read of the gatekeeper will display all meter data retrieved from the gatekeeper.
Meter configuration
For the gatekeeper in an A3 ALPHA meter, EA_MS reads the configuration from the meter during the first communication session and any time EA_MS detects a program change. Typical configuration parameters read from the meter include the following: the quantities the meter is programmed to measure how quantities are mapped to channels within the meter meter multipliers firmware revision number daylight saving flag length of interval data and demand intervals Each time it reads a gatekeeper, EA_MS also reads the meters last programmed date, verifying that the date has not changed since the last time it communicated with the meter. If the last programmed date has changed, EA_MS reads the meters configuration information to determine if anything has changed. Every time EA_MS reads an A3 ALPHA meter, it reads the meters clock to verify that the time in the meter is correct. See Time management in gatekeepers on page 23 for information on how a meters clock is synchronized to the system time when necessary. For REX and REX2 meters and A3 ALPHA meters with EA_NICs, EA_MS determines their configurations, either from the manufacturers marriage file (see Importing a marriage file on page 134) or based on the gatekeeper to which the meter is registered.
Data export and XML schema

Data collected by EA_MS (includes scheduled meter reads and on request reads) is published in XML format files. The complete description of the XML schema is given in the EA_MS AMR Data Exchange
Format Reference.
23
1. Introduction
Time management in gatekeepers

Note: This feature is only available for A3 ALPHA meters as gatekeepers.
EA_MS provides complete time management by reading meter configuration and time synchronizing meters.
Time synchronization in A3 ALPHA meters

Whenever EA_MS communicates with an A3 ALPHA meter, it also reads the meters clock, reads its daylight saving time (DST) observance, and compares it to the servers clock. Based on user-defined parameters, the server may: determine the meters clock is within allowable limits determine the meters clock is off and correct the meters time determine the meters clock is significantly off (that is, requiring a field visit) and not correct the meters time All time synchronization messages are included in the event section of the reading report (see Meter Readings Report on page 138). For meter time synchronization to be accurate, the server clock must be synchronized with a national time standard. Refer to the EA_MS Installation and Administration Guide for details on time synchronization.
Multiple time zones and DST

In general, meters can have their clocks set to local time zones and may or may not observe DST. However, REX meters use the same time zone and have the same DST observance as the gatekeeper to which they are registered. Times provided in XML files are in Greenwich Mean Time (GMT). The time translation is computed by using the meters time zone entered by the user and DST information stored in the meter.
Meter events, alarms and logs

EA_MS includes support for alarms, events and other status conditions that are reported by a meter. Refer to the EA_MS Installation and Administration Guide for detailed information on configuring alarm notification.
Note: Refer to the manufacturers meter technical manual for details on the events, errors, warnings, and alarms supported by a particular meter.
EA_MS provides the ability for System Administrators and Meter Services profile users to be notified of exception conditions, registrations, health issues, outages, and restorations including meter restorations reported by the gatekeeper either when they are detected and interpreted by the system (by interpreting change in value). This is available via the flashing icon on the top right of the browser or by selecting Activity Monitor > Alarm Conditions.
Note: Users with lower privileges have varying rights to view alarms but cannot acknowledge or clear them. See Chapter 15, Administration for details.
The system also provides the ability to report on events and alarms that occurred over a time range, either by meter or by category (but not both at the same time). You can also query for statuses by status type or category. See Appendix C, Events and statuses for details of events, alarms, and statuses reported to EA_MS. See Chapter 5, Electricity metering for details on the various reports for events, alarms, and statuses.
24
1. Introduction
Reports
EA_MS provides numerous reports to help manage and operate the system. Standard browser features such as Print, Send To (via email) and Save As are available. See Chapter 14, Reports for details.
Disconnecting and reconnecting service

EA_MS supports a service disconnect/reconnect function for operating the service control switch on REX and REX2 meters (see Connecting a meters service on page 126 and Disconnecting a meters service on page 130 for details). The disconnect/connect command is sent to the REX and REX2 meter through the gatekeeper. The response is checked to make sure the meter did not reject the command, but the state of the switch is not verified. A subsequent command is sent to the meter to retrieve statuses after the operation. These statuses are returned in the AMRDEF file produced by the switch operation in the Disconnect category. An on request read of current period TOU values for the meter is performed after the switch command and these values are returned to the user interface. This reading is not treated like a special billing read in EA_MS. Disconnect/reconnect support includes: user actions specific for disconnecting and reconnecting service (see Connecting a meters service on page 126 and Disconnecting a meters service on page 130) available to Billing and CIS Services profile users and do not require advanced privileges CIS import for automating connect/disconnect operations improved interpretation of statuses and error messages before and after the operation of the service control switch
EA_MS data file partitioning

EA_MS generated AMRDEF billing/non-billing schedule data files can become very big in size. For customers that have all meters on a single schedule to be read daily, the billing file size could be over 1 GB. For these types of schedules it takes a long time for EA_MS to produce the final AMRDEF file. By using EA_MS data file partitioning, MDFP, meter reading data is available as gatekeepers are read instead of waiting for all meters to be read before any data is available. This speeds up the utility billing process cycle. Also, by providing partitioned files of meter readings, the user interface can display meter readings data faster.
Web Services
EA_MS includes a SOAP-compliant XML-based protocol that provides a clear and easy to use interface with EA_MS. This feature allows using standard tools available in different frameworks such as .NET, Java Axis, etc. to perform tasks such as the following: provisioning of meters reading meters demand reset outage detection
25
1. Introduction
There are two Web Services that are installed with EA_MS: MAS and OD: MAS Elsters proprietary interface that accesses most of our Web Services functionality.
MultiSpeak Web Services: OD Elsters MultiSpeak compliant interface that accesses EA_MS outage detection functionality.
Refer to the EA_MS Web Services Interface Reference (PG42-1014) for details on using Web Services. Refer to the EA_MS Installation and Administration Guide for details on configuring Web Services.
Other capabilities
Some other important capabilities supported by the system include: browser notification to the system administrator for specific meter events and alarms such as A3 ALPHA meter power outages, restorations, meter registrations and unregistrations, etc. a system dashboard tracks important system events, alarms and schedule completions since the user's last logoff on a prior day on request or scheduled synchronizing of REX meter time-of-use programming and other collection configuration data to gatekeepers exchange action allows switching meters between schedules or TOU schedules and between data sets LDAP-enabled to allow enterprise network logon IDs usage for access to EA_MS
26
2. Understanding EA_MS
Understanding EA_MS
As a EA_MS user, you will be responsible for performing a variety of activities associated with managing meters, accounts, schedules, and data sets. To perform these activities, you must understand the basic concepts required for effectively managing these business entities as they are represented in the system. This chapter discusses the relationship between meters, accounts, schedules, and data sets. You will also gain an understanding of how EA_MS retrieves and stores meter data by tracking the life cycle of a meter.
About meters
A meter is a device that measures a service (for example, electricity, gas, water, or energy). An electricity meter is capable of measuring a variety of data components (for example, consumption, demand, interval data, and TOU) depending upon the meter type and the programmed configuration of the meter. Other meters, such as gas or water meters, may provide other types of information, like leak detection, in addition to the metered quantity. After adding a new meter to EA_MS, you specify the schedule and data set to be associated with the meter. This three-way association determines when a meter is read and what data is collected.
Figure 2-1. Three-way Association (MeterScheduleData Set)

Removing a meter from a data set or from a schedule breaks the three-way association, so the meter has to be reassigned not only to a data set but also to a schedule to read the collected data.
27
Supported elements
EA_MS supports the following Elster elements:
A3 ALPHA meter gatekeeper and EA_Gatekeeper Element A3 ALPHA meter Firmware ver. 4.2 3.6 3.3 Firmware ver. Element EA_Gatekeeper Firmware ver.
WAN Comm options ITM3 modem Serial (ACB option board) Ethernet WIC (E-WIC) Wireless WIC (W-WIC)
LAN Comm options Gatekeeper module (ILC)
Firmware ver. 6.2 6.1 6.0 5.2 5.1 5.0 4.2 4.1
3.x 3.x 1.4 1.3 1.0 - 1.2 2.x 1.2 & 1.3
ACB option board 3rd Party Public radio modem 3rd Party Private radio modem
A3 ALPHA meter WAN Comm options ITM3 modem Ethernet WIC (ACB option board) Serial (ACB option board) 3.x 3.x C12.22 C12.21 Modbus DNP 3.0 DL/T 645 CDMA (C12.22) GPRS (C12.22) C12.21 Modbus DNP 3.0 DL/T 645 Firmware ver. Protocol
Wireless WIC
1.4 1.3 1.0 - 1.2 2.x 1.2 & 1.3
ACB option board
RS-232 3rd Party Public radio modem 3rd Party Private radio modem
Element REX meter
Firmware ver. 3.0 2.x 1.x
LAN Comm options 900 MHz RF radio
Firmware ver.
28
Element REX2 meter HW ver. 2.0
Firmware ver. 3.0, 3.1 2.x 1.x 4.0 3.1 3.1 3.0
LAN Comm options EA_NIC
Firmware ver. 3.0 2.7, 2.6 2.5 2.5 3.0 2.7 2.6 2.3 2.0 1.0 2.0 1.0
A3 ALPHA meter1
EA_NIC (ILN)
Water meter Gas meter AGInode

1. Either short or long data format.
EA_Water module EA_Gas module
About accounts
An account represents the customer responsible for paying the bill for the metered service (consists of an account name and an account number). EA_MS allows the option to use this information as meter attributes to make it easier to search for meters.
Note: EA_MS is not the system of record for this information.
About schedules
EA_MS allows for the following types of schedules: not for billing for billing for synchronization of gatekeepers with EA_MS for voltage reads A schedule specifies when readings from a meter are to be retrieved (using recurring dates or nonrecurring dates) and made available for billing. See Chapter 9, Schedule for detailed information. EA_MS also allows synchronization schedules for synchronizing information to gatekeepers (for example, changed TOU schedules, changed meter TOU schedule assignments). These schedules execute periodically at such a time that they do not cross midnight. In addition, they also set up gatekeepers to collect load profile from REX meters.
About TOU schedules

A TOU schedule defines switch times for various rate tiers for different day types during different seasons throughout the year. EA_MS supports up to eight TOU schedules (including non-TOU rates) that can be used by the utility for TOU metering. EA_MS allows you to import TOU schedules from programs (*.ped files) exported from Elsters Metercat software (release 1.6 or later). Once a TOU schedule is imported and assigned to REX meters, EA_MS synchronizes the TOU schedule and meter assignments to the EA_Gatekeepers, which in turn synchronizes the applicable switch times to each REX meter on a TOU schedule. See Chapter 10, TOU Schedules for detailed information.
29
About synchronization schedules

EA_MS uses synchronization schedules to synchronize information between EA_MS and the gatekeepers (for example, new or changed TOU schedules, billing information, HAD assignments, etc.). See Creating a synchronization schedule on page 249 for detailed information.
Note: Synchronization schedules are for gatekeepers only. EA_MS will not allow other meter types to be assigned to synchronization schedules.
Information that is synchronized to the gatekeeper consists of: New or changed TOU schedules Changed or new TOU schedule to REX/REX2 electricity meter assignments Changed or new billing dates Changed or new billing schedule to REX/REX2/A3ILN meter assignments EA_LAN node cleanup needed in old gatekeeper after registration change Change voltage reading configuration parameters Enable/disable LP collection for electricity meter in gatekeeper Enable/disable voltage reading collection for electricity meter in gatekeeper Configure critical tier override operation in gatekeeper Poll for OTA (over-the-air) upgrade status during OTA job Pending OTA image for registered meters on a gatekeeper Pending cancellations of OTA jobs Request version information for meters that are out of date Pending EA_LAN Mode 2 enable/disable commands Pending EA_LAN security commands (ACL, WAN seed, encryption, etc.) Pending check-in profile to WIC assignments Additionally, certain events in EA_MS require a synchronization of information with the gatekeeper (either on-request or by a synchronization schedule). These events include: creation/deletion/modification of TOU schedules any changes of meter assignments to TOU schedules changing the default TOU schedule assigning REX meters and A3 ALPHA meters with EA_NICs to a LP collection schedule assigning REX meters and A3 ALPHA meters with EA_NICs to a data set that contains demand reset for the purpose of billing assigning/changing the billing schedule for a REX meter and A3 ALPHA meters with EA_NICs creation, certain modifications (such as changing billing dates) or deletion of a billing schedule addition of a new gatekeeper to the system discovery of a new REX meter or a new A3 ALPHA meter with EA_NIC in the field or a jump by a REX meter from one gatekeeper to another Caution: All these changes (particularly when user-initiated) should be thought of as remote programming or configuration changes to underlying meters and, as such, must be handled with the same care as any other user-initiated programming and configuration changes to a meter.
30
About data sets

A data set specifies the data component types (such as, registers, events and exceptions, etc.) associated with a meter. Data sets are associated with a meter and a schedule. See Chapter 8, Data Set for detailed information. Additionally, as a part of its network monitoring, management and reporting, during every communication session with a gatekeeper, EA_MS reads network registration information. Data sets are not meter type specific. Consequently, there is no verification of whether an individual component type can be supported by a specific REX or A3 ALPHA meter. As the user, you are responsible for matching a meters programmed capabilities with the appropriate component types. EA_MS will report an error if the entire data set is invalid for a specific meter. Additionally, EA_MS includes a Component Mismatch Report that generates a report of all meters which are assigned to data sets that contain components that they cannot support.
Reading meters
To support meter data management, EA_MS reads and delivers the following data from meters: register billing data interval data voltage events and meter statuses
Reading register billing data

The register billing data supported by EA_MS include the following: consumption (kWh) demand (kW) (maximum, cumulative, and coincident) timeofuse (TOU) consumption TOU demand (maximum, cumulative, and coincident) usage (water meters only) voltage1 outage count1 demand reset count1
Note: REX meters do not support cumulative demand. Note: Only water meters support usage.
Although A3 ALPHA meters are modeled as REX meters in EA_MS and generally work like a REX meter, there are some inherent differences because of the metering capabilities of each meter type. For instance, because the A3 ALPHA meter has the capability to meter Total, the View meter form will display this along with two other demands. For the A3 ALPHA meter, the demand configuration displayed is based on what was detected when the meter was read, not the marriage file (which only shows two demands). REX meters have the ability to meter two demand quantities and REX2 meters can support three demand quantities. A3 ALPHA meters can meter Total demand along with two other demand quantities. Marriage files for both meter types only contain two entries for demand configuration. From EA_MS perspective, A3 ALPHA meters show Total and the
1. A3 ALPHA meters and REX2 meters with EA_NIC.
31
two demand quantities from the marriage file (or from an actual meter read). From EA_MS perspective, a REX meter shows the two demands from the marriage file (or from an actual meter read) and a REX2 meter shows the three demands. For example, a user sets up a TOU schedule with Total and Tier A demand values in EA_MS. A REX meter assigned to this TOU schedule has Total as demand 1 and Tier A as demand 2. Any additional meters must have Total as demand 1 to be assigned to this TOU schedule. For A3 ALPHA meters, the user will always see Total as first demand listed in View Meter and think that they should be able to associate the TOU schedule to that A3 ALPHA meter. However, they cannot assign the TOU schedule even though EA_MS View Meter shows Total as first demand. Maximum demand is the highest demand measured in a time period. The maximum demand is usually associated with the billing period, which is often 30 days (for example, the maximum demand occurred between 5:00 and 5:15 PM on November 25, 2005 for the November billing cycle). Cumulative maximum demand is determined by adding the present billing period maximum demand to the cumulative maximum demand each time the data is collected and demand is reset. Typically a meter is programmed to provide either cumulative maximum demand or continuous cumulative maximum demand, but not both. EA_MS reads both the maximum demand and cumulative maximum demand values from the meter. Coincident demand refers to a demand value that occurs at the same time as another demand reaches its peak value. For example, an electric utility may want to record the kVAR demand at the time of a maximum kW demand (Figure 2-2). Similarly, coincident power factor refers to a power factor that occurs at the same time as a demand value reaches its peak value. For example, an electric utility may want to record the average power factor at the time of a maximum kVAR demand (Figure 2-2). Coincident values are only available on reactive meter types (A3R and A3K). The number of coincident values that may be captured by the A3 ALPHA meter depends on whether or not the advanced metering option (-A) is enabled (disabled - two coincident values; enabled - four coincident values).
32
Figure 2-2. Metercat - configuring coincident values

Note: EA_MS does not support continuous cumulative maximum demand.
A demand reset is the action of resetting the accumulated demand count to zero. This is typically done at the end of each billing period, as well as at a season change for TOU. Many meters provide a demand reset count, which is the number of demand resets since the meter was last programmed. The meter may also provide the demand reset date and the date and time of the last demand reset action. Demand resets may also be recorded in the meters log. EA_MS can perform a demand reset on a meter (as part of a schedule or an on request read) as well as read the meters demand reset count and date/time of last demand reset, if supported by the meter. For the billing period that contains a season change, EA_MS reads and exports two sets of TOU data for billing for meters on TOU rates - previous season and current season.
Demand resets and meter types

A demand reset on an A3 ALPHA meter in a gatekeeper or an A3 ALPHA meter with an internal telephone modem results in the following actions: 1. Perform demand reset. 2. Return current data to EA_MS (labeled current). 3. Return incremented demand reset count. A demand reset on an A3 ALPHA meter with EA_NIC or a REX meter results in the following actions: 1. Perform demand reset. 2. Copy current data to previous data register. 3. Take snapshot of previous data.
33
4. Return previous data to EA_MS (labeled previous).
Note: The demand reset counter is only returned for current data, therefore, the counter is not returned with REX meter or A3 ALPHA meter with EA_NIC previous data.
Reading load profile data

EA_MS can read all LP channels programmed in the REX meter. Interval length and unit of measures can be read as part of a configuration read or from the marriage file. For A3 ALPHA meters with EA_NICs, EA_MS can read LP data for one or two metered quantities, based on how the meter is programmed. To read LP data from a gatekeeper, the meter must be assigned to a schedule that reads the Load Profile from Gatekeeper data component. See Chapter 8, Data Set and Changing a meters schedule assignment on page 82 for details. To optimize communication time, scheduled reads of interval data will only read those intervals in the meter that have not yet been read by EA_MS. On request reads of interval data for non-REX meters provide the option to either read data over a specific time range or to read those intervals that have not yet been read. For REX meters, EA_MS reads all data available in the gatekeeper.
Note: The limited storage available in the gatekeeper requires special consideration especially when using load profile data for billing. Note: During scheduled readings of LP data for A3 ALPHA meters with EA_NICs with two channels of LP, the number of intervals could differ for the two channels. Note: When reading an A3 ALPHA meter with Metercat, the diagnostic reading for LP will show a timestamp of 24:00 and a date stamp of the previous day. EA_MS shows this time as 00:00 with a date stamp of the current day. Note: When reading an A3 ALPHA meter with Metercat the Spring daylight saving time (DST) change shows a timestamp of 02:00 with the DST flag set ON. EA_MS shows the interval timestamp as 03:00 with the DST flag set ON. Additionally, the gatekeeper shows a timestamp of 02:00.
Reading instrumentation values

EA_MS delivers instantaneous instrumentation values as part of register data. For A3 ALPHA meters and gatekeepers, instrumentation values reported are an instantaneous snapshot of current period per phase voltages, currents, phase angles, and line frequency. For REX meters and A3 ALPHA meters with EA_NICs configured for short data format, these values may contain voltages for one or more of the following: current, previous period, and previous season. For A3 ALPHA meters with EA_NICs configured for long data format, the values are current period per phase voltage.
Meter life cycle

The meter life cycle in EA_MS can be illustrated in terms of a series of stages that map to effects of real-world business processes. While different actions can be thought of as changing the stage the meter is in at a given time, they do not prohibit the user from changing the order (where it makes sense) in which they do these operations to better fit their business processes. For instance, a user could set up a meter with schedules and data sets long before it is installed in the field if that process is consistent with the utilitys standard operating procedure. The figure below illustrates the effect of user actions on the meter life cycle.
34
Figure 2-3. Meter Life Cycle

Meter stages are determined by the following actions: 1. Purchase Meter and enter into Inventory A meter begins its life cycle when a company purchases and enters it into the companys meter management system as inventory. For A3 ALPHA meters, to indicate this purchase in EA_MS, you use the Meter > New action to enter the meter information (for example, meter serial number, meter type, etc.) into the EA_MS database. For A3 ALPHA meters with EA_NICs, REX meters, gas meters, and water meters (LAN meters), you use the Import Marriage File action to import multiple meter information. For LAN meters, once the marriage file has been imported, you could assign a name as well as collection parameters using the Meter > New action. When you have defined the meter, it enters the Inventoried stage in its life cycle. 2. Install Meter After a meter is inventoried, you may receive a Meter Installation Service Order requesting that the meter be installed (or informing you that the meter has been installed) at a customers location. You use the Meter > Modify activity to update the meter installation information (for example, regulatory agency, installation date and time, etc.) or the Meter > New action if the meter has not been entered in the system.
Note: A LAN meter for which EA_MS has only marriage file information is not considered to be in the system since the meter does not have a name associated with it.
35
Alternatively, a meter may be reported as installed from the field (either via gatekeeper call in for newly registered meters or an on request read from the system or a scheduled read). If the meters marriage file information is available in the system (for LAN meters) or if the meter has been added to the system and the installation date is empty, the meters installation date is set and the meter is marked as installed. That is, if you can read the meter in the field it is obviously installed. Under such circumstances, when a REX or water meter has not been named yet (through an Meter > New action) and all the system has is the marriage file information for that meter, the customers serial number is used as a proxy for the meter name. (Users can subsequently, update the name using Meter > Modify if needed).
Note: The installation date is the critical field that is used by the system to determine whether the meter is installed in the field.
You may need to enter the meters communication information. Remote communication between EA_MS and the meter may or may not be available at the time the meter is installed either because the remote communication with the meter is not required for this installation or because the communication link is not yet ready. For REX meters, you can use the Meter > Import CIS File action to import the installation information for multiple meters. The meter now enters the Installed stage in its life cycle. When a meter is installed it can be associated with the appropriate account. You would use the Meter > Modify activity (or Import CIS File) to make this association. 3. Initiate Data Collection When a meter is installed, you must specify the components to be collected by the system and the frequency with which to collect it. To specify this data in EA_MS, you would use one of the following actions: Meter > Assign/Remove Schedules, Meter > Modify, Schedule > New, Schedule > Modify depending on your business processes. The meter then enters the Readable & Billable stage in its life cycle. Note that in EA_MS, a meter cannot be assigned to a billing schedule using the Meter > Assign/Remove Schedules command. Users should use the Meter > New or Modify or the Schedule > Modify commands to set up these assignments.
Note: Meters cannot be assigned to a non-billing schedule using the Schedule > Modify command. Note: Water meters cannot be directly read from EA_MS and therefore do not support schedule and data set associations. In effect, water meters are readable upon installation, provided gatekeepers are configured to receive water meter broadcasts and are in the vicinity.
4. Stop Data Collection When a meter is removed from a schedule (using Meter > Assign/Remove Schedules or Schedule > Modify) and there are no other schedule associations, the meter returns to the Installed stage. Additionally, collection of load profile data by a gatekeeper for a meter can also be stopped by removing the meter from any data sets that involve LP data collection (Load Profile or Load Profile from Gatekeeper). 5. Remove Meter When the meter is uninstalled (that is, removed from its physical location) and returned to inventory, you must change the meters information in the database to show this change by using the Meter > Remove action to set the removal date on the meter to a valid value. For meters that will be taken out for any extended period, users can also optionally take the meter out of any billing, data collection and TOU schedules at this time. For REX meters, this action will cause them to be tagged for automatic unregistration from gatekeeper. When a meter is uninstalled, it returns to the Inventoried stage.
Note: Elster recommends that, even though you can enter a meters Field Removal Date without removing its schedules and data sets, you remove a meters schedule and data set associations before entering the Field Removal Date.
36
For REX meters that have been removed EA_MS will queue the meter for unregistration and subsequently send a command to its gatekeeper to unregister the meter.
Note: Removed meters will not be included in schedule executions and in various reports.
6. Retire Meter Once a meter has been uninstalled and returned to the inventoried stage, it may be either re-installed at a new physical location using Meter > Modify or retired/ destroyed and deleted from inventory using the Meter > Delete action. When a meter is deleted from EA_MS, it enters the Terminated stage in its life cycle. All usage and performance data associated with the meter are retained in the database until they are either cleaned manually or by a system administrator using the Purge Utility (see the EA_MS Installation and Administration Guide for details on using the Purge Utility).
Note: Elster recommends waiting for 24 hours after the meter was removed from EA_MS before it is deleted, so EA_MS can remove its association with its gatekeeper.
Important information
Please note the following information: A3 ALPHA meters as gatekeepers must have Comm Mode set as call out (see Meter > New); call in is not supported for gatekeepers EA_MS will not allow an EA_LAN meter (REX, A3 ALPHA meter, gas or water meter) to be added by using the Meter > New action without first importing the appropriate marriage file using Meter > Import Marriage File all meter reading data is stored on the server in XML files
37
3. Using the system
Using the system
Before you begin using the system, take a few moments to review the concepts contained in this and the preceding chapter. In this chapter, you will learn some basic techniques for using the EA_MS user interface. These techniques may be familiar to you already (for example, using the Search feature) but others are unique to this system (for example, using the Activity Monitor).
Note: To see all data entry fields you should set your monitors resolution to at least 1152 x 864 pixels. Note: In EA_MS, Name is used variously for Meter Name, Schedule Name, or Data Set Name. To differentiate these entities, this guide will use the specific entity name.
Data entry
When entering data in EA_MS forms, special characters cannot be used. Special characters include: ~, !, @, #, $, ^, &, *, (, ), <, >, ?,. Additionally, Elster recommends that you not use | (pipe), \ (back slash), and / (forward slash) in identification numbers because they are reserved characters for most operating system. Additionally, EA_MS does not support the use of non-English characters such as characters with accents or umlauts (, , , , etc.).
Elster data entry restrictions

Default rule: Alphanumeric +=_:%Meter names: Alphanumeric _-% File names: Alphanumeric . _ - <space> User names: Alphanumeric @$-._ Email addresses: Alphanumeric @.-%
38
3. Using the system
Accessing the system

EA_MS comes installed with one default system administrator user logon amrsysadmin (initial password is amrsysadmin). If multiple utility personnel share system administration responsibilities, this logon must be shared between them. Warning: EA_MS will force you to change the amrsysadmin password during the first time you access the system. See Changing a user password on page 383 for details.
All other user IDs are set up by the amrsysadmin (see Adding a new user on page 376 for details on creating a new user ID). Before you begin using EA_MS, you must have a logon name and password. Access to the system is restricted by user access levels. See your system administrator for a logon name and password. To access EA_MS: 1. From the Windows Start menu, select Programs > Internet Explorer. 2. In the browsers Address bar type: http://<ServerName>/mas where <ServerName> is the name of the server where EA_MS is installed. Contact your IS department if you do not know the server name. 3. Press Enter. 4. The EA_MS logon screen should appear.
Note: If the logon screen fails to appear contact your system administrator.
Logging on
Note: You should only have one browser window to EA_MS open at any one time. Note: Only one user should be logged in with a particular User Name.
To log on to EA_MS: 1. Type your User Name.
39
3. Using the system
Figure 3-1. Logon screen

2. Type your Password. 3. Click Submit. The EA_MS main window displays with the System Dashboard showing. Caution: Although EA_MS allows the use of the Back and Forward buttons, there may still be certain reports where they do not work as expected. (message: Warning: Page has Expired, or it causes the report to get submitted again). These issues, while an inconvenience, do not have any major side effects. Elster plans to resolve this issue in a future release. Until then, Elster recommends returning to the report using the Activity Monitor (select User Activities and select the desired report from the displayed list). See User activities on page 44 for details.
About the EA_MS main window

The EA_MS main window is composed of three areas: the menu bar the navigation bar the body area
41
3. Using the system
Alarms (same as Activity Monitor > Alarm Conditions) - opens Alarm Conditions page; blinks red (shown at right) when the system detects a new alarm condition (such as health problems) at the meter
Body area
The body area displays data entry forms, reports, and information requested using the menu bar commands.
Viewing the Elster website

To view the Elster website, click on the Elster logo at the top left of the EA_MS browser window.
About the system dashboard

The System Dashboard summarizes information about what is happening (or has happened) in the system. This view provides a single consolidated view that makes it easy to monitor large systems and provides a quick overview without having to navigate through many reports. The System Dashboard itself consists of the pages: System activities- activities executed or monitored by the system User activities (formerly known as the Activity Monitor) - activities executed by the user through the browser interface System Dashboard - displays graphical representation of schedule executions, schedules grid, WAN statistics, and LAN metrics [evaluation feature] Alarm conditions - displays a listing of alarm conditions detected by the system
System activities
The System Activities page displays a series of panels that provide the user an overview of the current state of the system (including completed and running schedules, as well as schedules queued up to run). To view system activities: From the Activity Monitor menu, select System Activities.
42
3. Using the system
Figure 3-4. System Dashboard - System Activities

The System Activities page displays the following information: Event Summary panel and Outstanding Alarms panel - summarizes major events that have occurred since a users last logout time (from a prior day1) to the current time-for each category that a user has configured to monitor (for example, job function related events). These are configurable in each users profile (based on security profile) see Configuring event and alarm panels on page 60. Clicking on an event category listed in the Event Summary panel displays the Meter Events Report for the selected category between the time the user logged off on a prior day and the current time. This ensures that users can keep track of events that occurred over a weekend or overnight. Clicking on an alarm listed in the Outstanding Alarms panel displays an Alarm Conditions report for the selected alarm condition (Figure 3-5) between the time the user logged off on a prior day and the current time. This ensures that users can keep track of alarms that occurred over a weekend or overnight. Access to detailed alarm reports may be restricted by user's security profile: System Administrators and Meter Services have full access to acknowledge and clear alarms. If another user acknowledges the alarms, the Unacknowledged counter decreases at the next Dashboard refresh time. Reports Only users are only allowed to view summary information. Billing and CIS users can view alarm details but cannot acknowledge or clear them.
Alarm conditions
To view Alarm Conditions, from the Activity Monitor menu, select Alarm Conditions.
1. Prior day logout ensures that the session inactivity logout does not cause the users dashboard view to react.
43
3. Using the system
Figure 3-5. Viewing outstanding alarms

Schedules: Completed Runs - shows schedules that ran between the users last logout time and the current time. This panel provides easy access to schedule performance, summary of execution and links to schedule readings: Clicking a Performance value opens a Performance Report for the selected schedule (Figure 3-6). Schedules - Running panel lists schedules that are currently running.
Note: The percent success for schedules that are currently running serves as a progress indicator. This percentage is updated as meters are read by the system.
Schedules - Upcoming Runs panel lists schedules that are expected to execute in the future (the default setting is one day but this can be configured for each user). See Configuring schedules panels on page 61.
44
3. Using the system
Figure 3-6. Schedule Performance
User activities
EA_MS is a multi-user, multi-threaded, multi-tasking application. This allows you to submit an activity for execution and then immediately proceed to the next independent activity without waiting for the earlier activity to complete (for example, you can define meters one right after another). An activity could be either an action (such as, Modify Meter) or a creation of a report (such as, Associated Nodes). While you continue on to the next activity, the server executes your submissions and will post the status of your activities to the User Activities window. Warning: Do not submit multiple actions for the same entity or proceed to dependent activities before the completion of prior activities on the same objects. Wait until the request completes before submitting another request. For example, when creating a new meter, wait for the meter to be successfully created before attempting to assign the meter to a schedule.
User Activities is a listing of all the activities that you have initiated in the system (including
report generation). It is set up to wrap around after a certain number of pre-configured entries (currently 100) across all users. In general users can see only their activities. The only exception is amrsysadmin, who can see all the activities in the system.
45
3. Using the system
Figure 3-7. User Activities

An activity is created as soon as a user opens a form to perform the activity. Since it takes up space in the Activity Monitor list, Elster recommends that users clean up any Waiting on User activities periodically by selecting the activity and clicking Cancel. The table below describes the information shown on the Activity Monitor. Each of these can be used to sort the list of activities in the Activity Monitor. The default sort order is based on submitted time in reverse chronological order. Note that activities that have not been submitted do not have a submitted time, therefore these activities show up in random order at the top of the list. Item radio button Initiator NW (Noteworthy) Description Status Description Allows you to select the activity in the list (for use with the Activity Monitors buttons). See Using buttons on page 48. Logon ID of the user executing the activity. Displays the work status indicator icon. See Using the work status indicator on page 46. The activity executed. Shows a message indicating the activity Status, Workitem Number, Information messages, warning messages, error messages, and, occasionally, Exception Details. The date and time that the activity was submitted for execution. Clicking column heading allows for sorting by date and time (ascending or descending order).
Submitted
46
3. Using the system
Item Elapsed
Description The length of time between the submission of the activity and the completion.
Using the work status indicator

Workitem status form
After the server completes a command, a page displays the requested information (for example, Performance Report) and also includes the Workitem Status form indicating the status of the command execution (for example, Succeeded).
Figure 3-8. Workitem Status form

The Work Status Indicator icon changes as the status of an activity changes (that is, working or completed). The possible working states of the Work Status Indicator are: waiting for user input
waiting on the system
executing the activity
activity completed successfully
activity failed
47
3. Using the system
After EA_MS completes an activity, the system displays a message and includes one of the following message type symbols for the Work Status Indicator: information warning
error
Detecting errors
The system indicates problems or errors with your work activities when the Work Status Indicator changes from to .
Figure 3-9. Activity error

When this occurs, click Activity Monitor > User Activities to view the System Dashboard User Activities window that lists the status of all of your activities for the current session. The Warning indicator appears in the NW column and the Error Message describing the error appears in the Status column. You can click on the Exception Details hyperlink to view additional information on the problem.
Figure 3-10. Exception Details information

To correct a data entry error, select the activity from the Activity Monitor list and click the Copy button. A copy of the activity with the original data appears allowing you to enter the correct information and re-submit the activity. If you have determined that the error is correctable: 1. Click the radio button to select the workitem. 2. Click Copy. The form for the selected activity displays. 3. Enter the corrected information.
48
3. Using the system
4. Click Submit to complete the action.
Viewing an activitys information

You may view the results for a listed activity by selecting the desired activity (Description column) from the User activities list. System administrators can see every users activities; other users can only see their own activities. You can click on the activitys Description to view the results of the selected workitem. System administrators can view the information (Administrator > Users > View All > Display Information on User) on the Initiator by selecting the user logon ID for the desired activity from the User activities list.
Viewing alarm conditions

If EA_MS is configured for alarm notification (refer to the EA_MS Installation and Administration Guide for details on configuring alarm notification) and you have Meter Services Security privileges, you can view configured alarms online using Activity Monitor > Alarm Conditions.
Note: Because of the auto-refresh nature of this report and because of the potentially sensitive nature of information, only the EA_MS system administrator and users with the Meter Services Security privilege are allowed full access to this report.
Figure 3-11. Activity Monitor - Alarm Conditions
Using buttons
Workitem actions tool bar
The Workitem Actions tool bar display below an action form.
Note: Some forms do not display the entire tool bar.
Figure 3-12. Workitem Actions toolbar
49
3. Using the system
Cancel
You can cancel the display of a workitem by selecting the item radio button from the Workitem Actions list of the Activity Monitor and clicking the Cancel button on the Workitem Actions tool bar. If you have already submitted the workitem, it will execute as usual. The cancellation just means that you will not see any further results in the browser window. After the completing the cancellation, the Activity Monitor show the activitys Status as Cancelled.
Create
You can open a new, blank form for a selected activity in the Activity Monitor list by clicking the Create button on the Workitem Actions tool bar.
Copy
You may copy the data entered for a listed activity by selecting the desired activity from the Activity Monitor list and clicking the Copy button on the Workitem Actions tool bar. The window displays with the data you entered previously already entered in the data fields. This button enables you to correct data entry mistakes and then re-submit the activity for execution.
Note: Not all of the forms fields are filled in.
Delete
You may delete an activity from the Activity Monitor list by selecting an activity and clicking the Delete button on the Workitem Actions tool bar. This enables you to clear out your Activity Monitor window as you perform additional activities and correct mistakes.
User actions tool bar

The Administration > Users > View All and View My Account reports displays the User Actions tool bar.
Note: The View All action is available for system administrators only.
Figure 3-13. User Actions toolbar

Edit
Note: This action is available to all users.
Each user may change the default settings on his user account by first clicking the radio button for the item to select it and then clicking the Edit button on the User Actions tool bar. An Edit form displays allowing you to make the necessary changes. After making your changes, click Submit to complete the action.
Copy
Note: This action is available for system administrators only.
System administrators may create a new user based upon an existing user by first clicking the radio button for the user to select it and then clicking the Copy button on the User Actions tool bar. Edit the new user form as needed (for example, change the user name, etc.) and click Submit to complete the action.
Create
50
3. Using the system
System administrators can open a new, blank form for creating a new user by first clicking the radio button for the user to select it and then clicking the Create button on the User Actions tool bar. Enter the required information as needed and click Submit to complete the action.
Delete
System administrators may delete a user from the list by first clicking the radio button for the user to select it and then clicking the Delete button on the User Actions tool bar.
Searching
EA_MS provides a search capability that enables you to select a particular item for a report by viewing a listing of items (for example, when adding a meter to a schedule). See the following topics for specific information: Retrieving a meter on page 68 Retrieving a Schedule on page 204 Retrieving a Data Set on page 192 To search for an item like a meter: 1. When you select an action that requires a specific meter the Search button appears at the top of the form. 2. You can click Search now. Or Enter search criteria to narrow the search and click Search.
Note: The search criteria is not case sensitive. Note: You can use % or * as a wildcard. You can use beginning and trailing wild cards to perform starts-with and contains searches. For example, entering a Meter Name of %Col% result in a list of all meters whose names contain Col.
EA_MS starts narrowing the list as you type the search criteria. 3. Select the needed item from the displayed listing. The selected item is selected and the activity is submitted.
Exact matches
You do not have to use the search option if you know the exact name of the entity you want. For instance, when viewing a meter, if you know the exact name of the meter, you can type the exact name in the Meter Name field and click Submit. The View Meter Report displays without having to select the specific meter from a list.
Filtered lists
To aid you in locating the correct meter and the appropriate meter type, EA_MS filters the available list of meters based on whether the action or report is supported for that meter type. In addition EA_MS will also limit these lists based on certain business process-related conditions. For instance, since a meter cannot be on more than one billing schedule, EA_MS will only display meters that are not on a billing schedule when you are assigning meters to a billing schedule. The table below summarizes the filtering behavior in this release. Activity Billing schedules Meter types displayed
51
3. Using the system
Activity Action > Schedule > New Action > Schedule > Modify Synchronization schedules Action > Schedule > New Action > Schedule > Modify
Meter types displayed only meters that are not currently assigned to a billing schedule
only EA_Gatekeepers that are not currently assigned to a synchronization schedule
Refreshing the user interface display

Occasionally you may wish to refresh the data of a report (for example, View All Schedules).
Note: Clicking the browsers Refresh button, will not refresh the contents of a report. Clicking the Refresh button opens the System Dashboard at the specified default page. See Changing start up page on page 40 for detailed information on configuring the default page.
To refresh the displayed data: 1. Right click in the report body. 2. Select Refresh. The report data is updated.
Selecting a date and time

For some of the activities and reports, you are required to enter a date and time either as input information or part of a query criteria. To enter a date and time: to select the desired date and time. Click on the Display Calendar button Usually, the display defaults to now. For some reports, the default time may be midnight. Click on the Clear Date/Time button to clear the current date and time, if the date and time to be selected is substantially different from the default.
Note: The Date and Time defaults to your user profile time zone and displays an hourly offset (the -05 in the example below) to Greenwich Mean Time (GMT) depending upon the Time Zone you selected (which, unless changed explicitly, is the same as the user profile time zone).
Caution: Validation rules on date and times (in the future, in the past etc.) are context sensitive and depend on the specific action or report.
52
3. Using the system
Figure 3-14. Selecting a date and time
Figure 3-15. Selecting a date

The table below describes the features of the Calendar dialog. Item Description Allows you to select a specific month.
Allows you to select a specific year.
Moves the calendar back one year from the current month.
Moves the calendar back one month.
Sets the calendar to the current date and time.
53
3. Using the system
Item
Description Advances the calendar one month.
Advances the calendar one year from the current month.
Time Time Zone
Allows you to specify the HH:MM:SS and AM or PM. Allows you to select the Time Zone. Click to select the specified date and time.
To enter dates and times using the calendar perform the following procedure: 1. Click on the buttons to select the appropriate Month and the appropriate Year. 2. Select the Date from the displayed month. 3. Enter the proper Time in the text box. 4. Click Select to return to the main activity window with the specified date and time.
Using time zones

In EA_MS, time zones are represented in Windows format (for example (GMT - 05:00) Eastern Time (US and Canada)). The various business entities use the time zone in the following manner: meter data (the actual readings) are displayed in meter local time zone with DST adjusted2 (see Actions > Meter > New) schedule data and reports (executions, performance, etc.) use the schedule time zone of the schedule (see Actions > Schedule > New)
Note: Schedule execution times will be automatically adjusted to DST (that is, the schedule will run at 2:00 am EST and 2:00 am EDT).
all other reports show up in the users time zone (see Administration > Users > New) certain specific date-times on each of the reports that are used to indicate when the server performed a specific task show up in the server's time zone. For instance, the Report Generated On time stamp and the time stamps on some of the detailed workitems under the user audit report will use the servers time zone. Hence, if the server is running in GMT, these will show up as such.
Processing error messages

If any required information is missing when an activity is submitted to the server, the system displays an error message that notes what data or information is required to complete the activity. To correct the error, enter the correct required data and click Submit. The figure below shows an example of an error message.
2. Assuming the meter observes DST.
54
3. Using the system
Figure 3-16. Sample error message
Viewing sorted lists

In the various reports you can click on a column header to sort the listing in ascending or descending order. For example, in the View Schedules Report, clicking on the Performance column header sorts the list of schedules by their performance percentage. A small up or down arrow indicates which column the list is sorted by and whether it is sorted in ascending or descending order.
Figure 3-17. Viewing a sorted list - performance
Viewing PDFs
EA_MS allows you to view reports in Adobe Reader PDF file. You must have Adobe Reader installed (you can download the Reader installation file at http://www.adobe.com/ products/acrobat/). To view a report in a PDF file: click the PDF icon on the report page -
55
3. Using the system
Using Help
The Help menu provides access to the EA_MS User Guide and to EA_MS version and contact information.
Viewing the User Guide online

To access online help: From the Help menu, select User Guide. The EA_MS Help window opens displaying the online help with the Contents pane showing on the left.
Figure 3-18. Contents panel

The table below describes the items shown on the online help. Item Move back a page. Description
Move forward a page.
56
3. Using the system
Item
Description Synchronizes the Contents pane to the page currently being displayed.
Prints the current page.
Using the Contents pane

To view the contents of the user manual, select a topic from the table of contents.
Figure 3-19. Using the table of contents

Using the Index pane
To search the online help index, click the Index tab and select the initial letter for the word or slide the scroll bar down to view the indexed items.
57
3. Using the system
Figure 3-20. Index pane

Using the Search pane
To search the online help, click the Search tab and type the search word or phrase in the text box and click Go!. The search results are displayed by rank in the list frame. Select an item and the selected page displays with the word or phrase highlighted.
58
3. Using the system
Figure 3-21. Search pane

Using the Favorites pane
To search the online help, click the Search tab and type the search word or phrase in the text box and click Go!. The search results are displayed by rank in the list frame. Select an item and the selected page displays with the word or phrase highlighted. To add topics to your Favorites: 1. From the Contents pane, select the desired topic. 2. Select the Favorites pane. The select topic heading is displayed in the Favorite text box.
59
3. Using the system
Figure 3-22. Favorites pane

3. Click Add to add the selected topic to your Favorites. The topic is added to your Favorites list.
Figure 3-23. Favorites list
60
3. Using the system
Viewing EA_MS version and contact information

To access information about EA_MS: From the Help menu, select About EA_MS. The About EA_MS form displays the version and contact information.
Figure 3-24. Version Information

To email EnergyAxis Technical Support: click on the email link on the About EnergyAxis Management System
Configuring EA_MS
Configuring event and alarm panels
To configure the Event and Alarm panels: 1. Click Configure link appearing after the Event Summary title. Or From the Favorites menu, select Edit Favorites. Or From the Administration menu, select Users > View My Account > Edit button.
61
3. Using the system
Figure 3-25.
The Edit Your Account form displays. 2. Select the Dashboard page. 3. For Monitored Event Categories, select those categories you wish to view on the Dashboard. See Appendix C, Events and statuses for details on events and alarms. 4. Click Submit.
Configuring schedules panels

To configure Schedules panels: 1. Click Configure link appearing after the appropriate Schedules title. Or From the Favorites menu, select Edit Favorites. Or From the Administration menu, select Users > View My Account > Edit button. The Edit Your Account form displays. 2. Select the Dashboard page. 3. Enter the number of Days to Look Ahead (range of 1 - 30).
Note: Days to Look Ahead goes to the midnight (00:00:00) of that day. The information is not in 24-hour increments.
Configuring EA_MS favorites list

EA_MS allows you to configure a Favorites list of frequently used activities. To configure your favorites: 1. From the Favorites menu, select Edit Favorites. 2. Select the Dashboard page.
62
3. Using the system
Figure 3-26. Configuring EA_MS favorites

3. From the Favorites check list, select the actions you frequently perform. 4. From the Monitored Event Categories list, check the categories you wish to monitor: Service PQM Network Firmware Upgrade Tamper Alert Audit Log Power Quality Voltage Monitoring Full Power Outage/Restoration Meter Health Miscellaneous
Note: See Appendix C, Events and statuses for details on events and alarms.
5. For the Upcoming Schedules, enter the number of days to look ahead (range of 1 30). 6. For Dashboard Preferences, select the page to be viewed by default: System activities User activities
63
3. Using the system
Logging off
To log off from EA_MS, use the Log Off option from the main menu. Although EA_MS has a built in security mechanism to log off user sessions after a period of inactivity (a configurable period based on the company's security policies), every user is responsible for logging off after completing their work. The Activity Monitor reports have an auto-refresh setting that ensures that users see the very latest information available from EA_MS. However, there is no way that EA_MS can differentiate between user-initiated activity and auto-refresh activity. As a result, if the monitor is left on an Activity Monitor report, the users session will appear to be always active (and therefore never logged off automatically). Warning: To prevent unauthorized use of EA_MS, system administrators are expected to follow sound security procedures and log off as soon as they have completed their work.
64
4. Getting started
Getting started
To begin setting up EA_MS, you need to perform the following activities to correctly set up EA_MS for reading and collecting data: 1. Installing meters and devices. 2. Create data sets. 3. Creating schedules. 4. Assigning meters and devices to data sets and schedules.
Installing meters and devices

You need to add your meters and devices to the EA_MS database before you can begin collecting data. When you purchased meters from Elster, you received marriage (for REX and REX2 meters) and WIC activation files for use with EA_MS.
Installing a gatekeeper
To add a gatekeeper to EA_MS: 1. Receive the gatekeeper from Elster and place into inventory. 2. If the gatekeeper is WIC-enabled, import the Activation file emailed by Elster. See CIS Import Audit Report on page 360 for details on verifying the import results. The gatekeeper is inventoried. 3. Install the gatekeeper in the field. 4. Use Meter > New to set the devices installation date and time and enter any required meter, billing and installation information. Check to Overwrite Meter if exists only if you think that this meter may already be in the system. Be sure to enter the correct communication information such as comm media, and comm number, etc. Be sure to check the Meter Type is Gatekeeper Latitude/Longitude data are used to generate shape files for use with GIS (geographical information systems). The gatekeeper is installed.
Installing a node device

To install a REX, REX2, A3 ALPHA, EA_Repeater, water, gas, or AGInode device: 1. Receive the device from Elster and place into inventory. 2. Import the marriage file emailed by Elster. See Marriage File Import Audit Report on page 363 for details on verifying the import results. The device is inventoried. 3. Install the device in the field.
65
4. Getting started
4. If the device registers with a gatekeeper before being entered into EA_MS, EA_MS automatically adds the device into EA_MS with the devices serial number as the Meter Name. 5. Use Meter > New to set the devices installation date and time and enter any required meter, billing and installation information. Check to Overwrite Meter if exists only if you think that this meter may already be in the system. Latitude/Longitude data are used to generate shape files for use with GIS (geographical information systems). Be sure to check the Meter Type is correct: EA_MS Meter Type REX EAGas EAWater A3_ILN A3 The device is installed. Elster Product REX, REX2, EA_Repeater, AGInode EA_Gas module on gas meter EA_Water module on water meter A3 ALPHA meter with EA_NIC A3 ALPHA meter with WAN comm (WIC, RS-232, ITM3, etc.)
Create data sets

Before you can create any schedules to begin reading meter data, you need to create the data sets (Data Set > New) that define the meter data EA_MS will be reading from the gatekeepers and devices. Elster recommends, at a minimum, creating a data set for each device type using the listed components: Device type Gatekeeper Data components Registers Load Profile Events and Exceptions LAN Performance Reset Communication Statistics Read Water Data from Gatekeeper Read Gas Data from Gatekeeper Demand Reset Registers from Gatekeeper Load Profile from Gatekeeper Demand Reset
node device: REX2 meter A3_ILN EAGas EAWater
Depending on the information you need to properly manage and operate your system, you may have additionaly data sets defined.
66
4. Getting started
Creating schedules
EA_MS provides the following schedule types: billing non-billing synchronize voltage reads
Schedule run times

A typical EA_MS installation uses the following strategies for reading the various data types and performing demand resets: Gatekeeper reads demand reset registers load profile voltage Timing at midnight - 00:00 (billing or season change) every 4 hours - 1:00, 5:00, 9:00, 13:00, 17:00, 21:00 every 6 hours - 2:00, 8:00, 14:00, 20:00 every 15 minutes
A schedule for billing data

A billing schedule operates differently for A3 ALPHA meters and REX/REX2 meters.
A3 ALPHA meters
1. EA_MS synchronizes the gatekeeper with the next billing date. 2. On the billing date, the gatekeeper reads the current period data. 3. The gatekeeper performs a demand reset. The current period data is used for billing purposes.
REX/REX2 meters
1. EA_MS synchronizes the gatekeeper with the next billing date. 2. On the day before the billing date, the gatekeeper arms the REX meter for a demand reset to occur. 3. At midnight the REX meter performs a demand reset and copies the current period data to previous period. 4. The gatekeeper reads the previous period data from the REX meter during the first reading after midnight. The previous period data is used for billing purposes.
A schedule for synchronizing

You will need to create one schedule for synchronizing the gatekeepers in the system. See Creating a synchronization schedule on page 249 for details.
A schedule for reading voltage

If EA_MS and your gatekeepers have been configured to read voltage data, you may create one or more schedules for reading voltage. See Creating a voltage reads schedule on page 252 for more information.
67
4. Getting started
Assigning meters and devices to data sets and schedules

Once you have your meters and devices installed and your data sets and schedules defined, you need to use Actions > Meter > Modify to edit the selected meters Billing Details to assign the meters and devices to a Billing Data Set, a Billing Schedule, and for gatekeepers, a Synchronize Schedule. Once you have completed the steps outlined in this chapter, your system should be reading and collecting meter and device data and saving the date to an AMRDEF file on the system.
68
5. Electricity metering
Electricity metering
Actions and reports

Depending on the users security profile, the Actions menu allows you to access the following meter actions: View Meter Report New Modify Assign/Remove to Schedules Remove Delete Ping On Request Read Read Time Read Configuration Grouped Operations Power Status Check Set Meter Time Advanced Metering Functions Special Read for Billing
Import Marriage File Import CIS File Import WIC Activation File Connect Service Disconnect Service
All EA_MS users can access operational reports. The Reports menu allows you to create the following meter reports: Meter List Report View Meter Report Meter Readings Report Display Meter Readings Meter Inventoried Report Meter Installed Report Meters Not Read Report Meter Events Report Meter Alarms Report Meter Statuses Report Component Mismatch Report Meters Disconnected Report
See Chapter 14, Reports and Chapter 6, Water metering for additional reports related to meters.
Retrieving a meter
For the following activities you will need to retrieve a meter from the EA_MS database: View Meter Report Modify Assign/Remove to Schedules New Remove Delete On Request Read Read Time Read Configuration Set Meter Time Advanced Metering Functions Special Read for Billing
69
To retrieve a meter: 1. From the Actions menu, select Meter and the activity. The Retrieve a Meter form displays.
Note: Initially, the Search Criteria and Dates criteria sections appear collapsed. Click to expand a section to enter search criteria.
Figure 5-1. Retrieving a meter

2. Enter one of the parameters on which to base the search Meter Name Account No. Serial Number Narrow the meter name search by using the Search for: all meters meters with service disconnect switch (REX, REX2, and A2 ALPHA meters) A3 ALPHA meters EA_Gatekeepers REX meters EA_Water meters EA_Gas meters A3 ILN (A3 ALPHA meters with ILN)
70
Account Name Site ID Comm Media Comm Mode Schedule Name Data Set Name TOU Schedule (REX meters only)
Installation From and To date
Removal From and To date
Note: The search criteria is not case sensitive. Note: You can use % or * as a wildcard>. You can use beginning and trailing wild cards to perform starts-with and contains searches. For example, entering a Meter Name of %66% result in a list of all meters whose names contain 66. Note: The list of Search for can be filtered by meter type and the search pattern entered. For example, selecting REX meters and entering a Meter Name wildcard search %77%, displays all REX meters with Meter Name containing 77. Note: Elster does not recommend using a search pattern that consists of wildcards only. For large system installations the returned results would be too large to easily select a meter.
3. Click Search. The Search Results display.

4. Click the desired meter from the listing to select.
71
Note: The list of meters can only display up to 200 meters. If the desired meter is not displayed you will need to further narrow your search (for example, by adding another character to the search string).
Once the meter has been selected and user has submitted the request, the Please Wait graphic displays on the top while the form is being loaded. Do not select a meter from the list and then click Submit before the form has had a chance to load. The activitys form displays with the selected meters information.
Viewing a meters information

The View action displays a report of the selected meters information including the following: Characteristics (all meter types) Meter Name Serial Number Firmware Device Types REX Firmware Version Radio Firmware Version A3 Firmware Version LAN OB Version A3 Firmware Revision LAN OB Revision LAN Encryption Enabled LAN Mode 2 Enabled Meter Type /Descriptor Description Characteristics (gatekeepers) Billing Password3 Unrestricted Password3 Last Programmed Site Characteristics (all meter types) Observing DST (Yes/No) Meter Time Zone Comm Media Comm Number3 Comm Mode Device Number3 SDP ID (Site ID) EA_LAN Elements (all 900 MHz meters) LAN ID Gatekeeper (Lan Level:) Last Registered Site Location Field Install Date Field Removal Date (if applicable) Operating Territory Latitude Longitude Comm Template3 Direction (meter) CT Ratio VT Ratio Associated Nodes (hyperlink to Associated Nodes Report for Gatekeeper report) Last Connected (Last Connect Time) Meter Model LP Interval Max Days for LP Demand Interval Demand Subinterval Last Changed On (date/time) Disconnectable1 Service Disconnect Status2
1. Only meters with service disconnect switch. 2. Listed as Unknown for meters without service disconnect switch. 3. Gatekeepers only.
Billing Characteristics Account No. Account Name TOU Schedule
72
Collection Information Data Set Name Schedule Name (hyperlink to View Schedule Information Report) Billing Synchronization Schedule
Metered Quantities Billing Registers LP Channels Usage1
1. Water meters.
Marriage File Information (all 900 MHz devices) LAN Utility ID Manufacturer Serial Number Customer Serial Number Style Number Marriage File Information - REX Meter Load Profile Divisor Metered Quantity Demand Forgiveness Time Kh Demand Threshold Marriage File Information - A3 ALPHA meter with EA_NIC Factory Ke ILN Firmware Version ILN Firmware Revision Firmware Version (A3 ALPHA) Firmware Revision (A3 ALPHA) Owner Name Service Disconnect Tripped When Demand Threshold Exceeded Demand Threshold Penalty Firmware Version Firmware Revision Owner Name
Marriage File Information - Water Meter Load Profile Divisor Multiplier Manufacturer Module Serial Number Customer Module Serial Number Marriage File Information - Gas Meter Gas Meter Serial Number Gas Meter Model Lan ID LAN Utility ID Gas Module Serial Number Gas Module Style Number Snapshot Time Module Mode Multiplier Digits Displayed Gas Company ID Customer Serial Number Predivisor Pressure Compensation Numerator Pressure Compensation Denominator Interval Data Divisor Interval Length Unit of Measure Firmware Version Firmware Revision GPS Latitude GPS Longitude Metered Quantity Style Number Digits Displayed Load Profile Interval Water Company Id Firmware Version Firmware Revision
Note: For one-way nodes, such as water modules, the Gatekeeper field displays the gatekeeper that reported the most recent data for this device.
To view a meters information: 1. From the Actions menu, select Meter > View.
73
2. Search for the meter. 3. Select the meter. The View Meter form displays the meters information.
Note: Data collection schedules in the Collection Information section are hyperlinked to View Schedule Information Report on page 210. Note: All date and date-time fields on this report show up in the users profile time zone. Note: For EA_Gatekeeper in A3 ALPHA meters, any synchronization schedules that the meter is assigned to will show up under the section Collection Information as it would under any other schedule. However, the Data Set column will not be populated. Note: For LAN meters, time zone and daylight saving time (DST) observance information is not available until the meter registers to an gatekeeper (since the meter obtains this information from its gatekeeper).
4. Click on the Additional Information bar to view the marriage file information for the REX or A3 ALPHA node meter.
Note: The Characteristics section collapses when viewing the Additional Information section. To return to the Characteristics section, click the Characteristics bar.
74
Figure 5-3. Viewing a gatekeeper
75
Figure 5-4. Viewing a REX meter
76
Figure 5-5. Viewing an A3 ALPHA with EA_NIC

Note: The Gatekeeper field for a water meter lists the most recent gatekeeper to report data for the specified water meter. Note: Collection information will not be available for water meters since water meters cannot be explicitly scheduled for data collection. Only gatekeepers can be scheduled for the collection of water meter data.
77
Figure 5-6. Viewing a water meter
79
Changing a meters information

The Modify action allows you to perform the following meter operations: modify required and optional attributes of the meter set a meter as installed by specifying a valid installation date or modify an installation date set by the system (based on meter discovery) to a user-specified date overwrite a meter's name (that may have been defaulted to serial number after meter discovery) easily assign billing schedule, data set, and account, change assignments or remove them to support business processes for new meter installations, change outs, customer move ins and customer move outs assign a gatekeeper to its synchronization schedule assign a REX meter to a TOU schedule To modify a meters information in the EA_MS database: 1. From the Actions menu, select Meter > Modify. 2. Search for the meter. 3. Select the meter. The Modify Meter form displays the meters information. 4. Edit the information as needed. You can change the following settings: Required Information Meter Name Billing Details Account No. Account Name Site ID Site Location Billing Schedule Billing Data Set TOU schedule Id (for REX meters only) Installation Details Description Field Install Date Operating Territory (LAN meters and gatekeeper) Latitude Longitude Direction (meter) Comm Media Comm Mode
A3 ALPHA meter and EA_Gatekeeper specific items Billing Password Unrestricted Password Synchronization schedule (gatekeeper only) Time Zone Comm Number Comm Template
Figure 5-8. Modify Meter - Required Information (gatekeeper)
80
Figure 5-9. Modify Meter - Billing Information
Figure 5-10. Modify Meter - Installation Details

5. Click Submit to complete the change.
Changing schedule assignments

To change a meters assigned schedules: 1. Elster recommends you use the actions detailed in the following table to obtain the desired result. Desired Result Billing Schedule Add meter to billing schedule Modify billing assignment Remove meter from billing schedule Non-billing Schedule Add meter to non-billing schedule Actions > Schedule > Creating a schedule Actions > Schedule > Modify Actions > Meter > New Actions > Meter > Modify Actions > Meter > Modify Actions > Schedule > Modify Actions > Meter > Assign/Remove to Schedules Actions > Schedule > Modify Use Action
81
Desired Result Billing Schedule Modify non-billing schedule assignment Remove meter from non-billing schedule
Use Action
Actions > Meter > Assign/Remove to Schedules Actions > Schedule > Modify Actions > Meter > Assign/Remove to Schedules Actions > Schedule > Modify
2. Once the appropriate form is displayed, continue with the desired action.
Installing a meter
To indicate that a meter has been installed in the field: 1. From the Actions menu, select Meter > Modify. 2. Select the Installation Details page. 3. Enter the Field Install Date. 4. Click Submit to complete the change.
Note: The meter enters the Installed stage in its life cycle. See Meter life cycle on page 33.
Assigning billing determinants

Schedules and data sets determine when meter data is collected and what data is collected. To assign meter to a schedule or data set: 1. From the Actions menu, select Meter > Modify. 2. Select the Billing Details page. Caution: Elster recommends you review current schedule assignments using the View Meter Report before making any changes to billing determinates.
3. Select the Billing Schedules Schedule Name. 4. Select the Billing Data Sets Data Set Name. 5. For REX meters, select a TOU Schedule (if needed) 6. Click Submit to complete the change.
Note: The meter returns to the Billable & Readable stage in its life cycle. See Meter life cycle on page 33.
Assigning a gatekeeper to a synchronization schedule

Synchronization schedules are used to periodically synchronize to the EA_LAN any changes to the population of meters - information such as new TOU schedules, meter assignments to TOU schedules, meter display configuration, turning on LP collection and so forth. To assign a gatekeeper to a synchronization schedule: 1. From the Actions menu, select Meter > Modify (for the gatekeeper). 2. Select the Billing Details page. 3. Select the Synchronization Schedule's Schedule Name. 4. Click Submit to complete the change.
82
Removing a billing determinant from a meter

To remove a data set from a meter (for example, when you wish to delete a data set): 1. From the Actions menu, select Meter > Assign/Remove to Schedules. Or To remove many meters, from the Actions menu, select Schedule > Modifying a Schedule. 2. Check the Schedule Name-Data Set assignment. 3. Click Remove Selected. 4. Click Submit to complete the change.
Note: The meter returns to the Installed stage in its life cycle. See Meter life cycle on page 33. Note: Both the data set and the billing schedule assignments are removed at the same time.
Changing a meters schedule assignment

The Assign/Remove Schedules action allows you to assign or remove meters from schedules (when to collect) and data sets (what to collect). Multiple assignments and removals can be done in a single operation. To prevent unintended changes you cannot assign meters to a billing schedule or a synchronization schedule (however, removals are allowed).
Note: You can also make assignments and removals using either the Meter > New or the Meter > Modify actions.
Typical business processes that would use this function include: removing all collection parameters prior to a meter change out or retirement setting data collection requirements for purposes other than billing (for example, reading LAN performance to monitor the underlying network) or when frequency of data collection required is greater than that of the normal billing schedule (for example, daily reads of load profile (LP) for load survey)
Note: Water meters communicate only up to EA_MS (that is they cannot receive information from EA_MS) therefore they cannot be assigned to schedules. Note: For electricity meters in the EnergyAxis System, Elster recommends that each node meter be scheduled to read either REX Registers from Gatekeeper or Load Profile from Gatekeeper. Scheduling gatekeepers to read REX Registers from Gatekeeper will cause data to be read and exported to AMRDEF twice.
Some data components should not be set up on multiple schedules. Load profile, for instance, should be read from the meter on a single schedule only based on the needs of the application that needs the data more frequently than others. This minimizes the performance impact of reading LP data; EA_MS reads LP data on schedules in increments from where the previous scheduled read left off. In EA_MS, the application ensures that a user cannot assign the same meter to multiple schedules for collecting LP data.
To assign or remove a meter from one or more schedules: 1. From the Actions menu, select Meter > Assign/Remove Schedules. 2. Search for the meter.
83
3. Select the meter. The Assign/Remove Schedule to/from Meter form displays the meters information.
Figure 5-11. Assign/Remove Schedule

4. To remove a meter from a schedule: a. Check the Schedule Name to be removed. b. Click Remove Selected to remove the meter from the selected schedule. Caution: Elster recommends you review current schedule assignments using the View Meter Report before making any changes to billing determinates.
The schedule name is removed from the meters information.
84
Figure 5-12. Remove meter from schedule

c. Click Submit to complete the activity. 5. To add a meter to a schedule: a. Click Add. b. Search for the appropriate Schedule Name. c. Select the Schedule Name from the list.
Note: You can add more than one schedule at a time.

d. Select a Data Set from the drop list for each schedule specified.
Note: EA_MS allows you to assign data sets if at least one of the components in the data set is supported by the meter. See Component Mismatch Report on page 170 for details on mismatched components.
85
Figure 5-13. Assigning a Meter to a Schedule

e. Click Submit to complete the action.
Adding a new meter

The New action allows you to add the following types of meters to EA_MS: EA_Gatekeeper: A3 ALPHA meter-based enclosure-based node meters: A3 ALPHA meters with the EA_NIC REX and REX2 meters equipped with the EA_NIC water meters equipped with EA_Water module gas meters equipped with EA_Gas module EA_Repeater EA_MS allows a REX meter, EA_Repeater, gas meter, water meter or an A3 ALPHA meter to be added through using Meter > New only after the appropriate marriage file has been imported (using Meter > Import Marriage File). The system considers a meter that has been imported in a marriage file as being in inventory and not yet added to the system. Once your have imported the marriage file, you can proceed to add the meter to EA_MS. When defining a new gatekeeper with a WIC (WAN interface card) and ILC option board, you must use the following settings: Comm Media = IP address for option board Comm Mode = gatekeepers should be defined as call out only Comm Number = IP address with port number: static - standard IP address format, example: 192.168.1.1:4660 dynamic - DNS (domain name system) name format, example: www.elster.com:4660
86
Comm Template: IP Ethernet WIC GPRS WIC 1xRTT WIC
Note: If you use DNS name format, EA_MS will attempt to resolve the name into a standard IP address at the start of communications with the gatekeeper. If the DNS format cannot be resolved to a standard IP address, EA_MS will return an error message.
To add a new meter to EA_MS: 1. From the Actions menu, select Meter > New. 2. Select the appropriate Meter Type from the drop list: a. A3 - A3 ALPHA meters b. REX - for REX meters, REX2 meters and EA_Repeaters c. A3_ILN - for A3 ALPHA nodes d. EAWater - for water meters e. EAGas - for gas meters f. Gatekeeper Depending on the meter type selected, the Add New Meter form will change to reflect the parameters applicable to that type of meter.
Figure 5-14. Adding a new meter - gatekeeper
Figure 5-15. Adding a new meter - REX meter

3. Enter the Required Information: a. Enter the Meter Name (must be unique). b. Enter the meters Serial Number. c. Enter the meters Billing Password (A3 ALPHA meters and gatekeepers). d. Enter the meters Unrestricted Password (A3 ALPHA meters and gatekeepers).
87
4. Select to Overwrite Meter if exists to overwrite the meter information if the meter already exists in the system.
Note: This option is useful any time that the user is not sure whether the meter has already been added to the system. For example, if a REX meter gets discovered and added to the system before the paperwork from the work order comes back, users can use Add New Meter with Overwrite without having to know whether it is already in the system or not.
5. Select the Billing Details page.
Figure 5-16. Adding a new meter - gatekeeper billing information
Figure 5-17. Adding a new meter - REX meter billing information
Figure 5-18. Adding a new meter - A3 ALPHA node billing information
88
Figure 5-19. Adding a new meter - water meter billing information

a. Enter the Account No. b. Enter the Site ID. c. Enter the Account Name. d. Enter the Site Location. e. For electricity meters, select the Billing Schedules Schedule Name.
Note: EA_Repeaters need to be on a schedule so that EA_MS receives status information from the device. Note: Water meters communicate only up to EA_MS (that is they cannot receive information from EA_MS) therefore they cannot be assigned to schedules.
f. For electricity meters, select a Billing Data Sets Data Set Name. g. If the meter is a gatekeeper, select a Synchronization Schedule. h. If the new meter is a REX meter, select the TOU Schedule.
Note: At this point, you can submit the new meter to EA_MS. Once the new REX meter is in EA_MS, you can perform an On Request Read to have EA_MS set the installation details. If you are adding a new A3 ALPHA meter or gatekeeper, you must complete the Installation Details communication information before you can perform an On Request Read.
6. Select the Installation Details page.
Figure 5-20. Adding a new meter - gatekeeper installation information
89
Figure 5-21. Adding a new meter - node installation information

a. Enter the Description. b. Enter the Field Install Date. c. Select the Meter Time Zone. d. If the meter is communicative: 1) Select the Operating Territory. 2) If the meter is an A3 ALPHA meter: Select the Comm Media (for gatekeepers: telephone, IP, 900 MHz, Ethernet WIC, GPRS WIC, and 1xRTT WIC [CDMA WIC]).
Note: EA_MS automatically assigns REX, water and node meters to 900 MHz Comm Media. Note: EA_MS does not check for correct configuration of Comm Template and Comm Media when the meter is added to EA_MS. Incorrect selections will appear as communication errors when the gatekeeper is first read by EA_MS.
Select the Comm Mode.
Note: A3 ALPHA gatekeepers should be defined as call out only.

Enter the Comm Number (for gatekeepers - telephone number or IP address in standard IP format with port number, example 192.168.1.1:4660) Select the Comm Template (for gatekeepers - std_phone for telephone or std_ip for standard IP. Enter the Device Number (for A3 ALPHA meters only). 7. If available, enter the Latitude and Longitude.
Note: Latitude and Longitude are required for geographical information system (GIS) management of EA_MS if the GIS option is available.
8. Select a Direction (meter) from the drop list. 9. Click Submit to complete the addition. EA_MS automatically adds a REX meter, water meter, or A3 ALPHA node (with the serial number as the meter name) and marks it as installed the first time it is reported by a gatekeeper (or you can use Meter > New). This minimizes user input and ensures that EA_MS reflects, as closely as possible, the state of the underlying network. This does create some ambiguity as to how you should add a meter - if the paperwork comes back before the gatekeeper calls in, use the Meter > New action; if the paperwork comes back after the gatekeeper calls in, use Meter > Modify action. Alternatively, you can consistently use the Meter > New option with the Overwrite if it Exists checked and the application will either create a new meter entry or update if it already exists in the database.
90
Adding multiple new meters

The Import Marriage File action allows you to automate the setting up of meters in EA_MS and to handle larger numbers than a user can normally be expected to enter from the user interface. To perform a batch creation of new meters: 1. Use Meter > Import Marriage File (containing the list of meters received from Elster with their factory configuration) to import the marriage file for the new meters. 2. Install the meters in the field. 3. Add XML snippets to a CIS file as the paperwork arrives for the individual meters. Alternatively, the paperwork may be completed in the CIS system and have the CIS system create an XML file of meters, installation details and billing details to be imported into the EA_MS system. 4. Use Meter > Importing a CIS file to create, install, and configure billing for the list of meters.
Removing a meter from the field

This action is used to indicate that a meter has been removed from the field (and can be installed at a new location):
Note: The meter returns to the Inventoried stage in its life cycle. See Meter life cycle on page 33.
To remove a meter from the field: 1. From the Actions menu, select Meter > Remove. 2. Retrieve the meter. 3. Select the meter to be removed from the listing.
Figure 5-22. Removing a Meter
91
4. Click Submit to retrieve the meter. The Remove Meter form displays.
Figure 5-23. Removing a meter

5. Enter the Field Removal Date. 6. If the meter is to be permanently removed from the current location, select to Remove Meter from All Schedules and TOU programs.
Note: Selecting Remove Meter from All Schedules and TOU programs will not remove the meter from the account or clear latitude and longitude. Use Meter > Modify to remove these parameters.
7. Click Submit to complete the action. For REX meters and A3 ALPHA meters, this action will also flag the meter for unregistration from the gatekeeper to which it is registered. The unregistration actually occurs at the next execution of synchronization schedule. This is done to ensure that there is enough time for the system to collect data for the meter from its gatekeeper prior to the unregistration. Unregistration process will also trigger a read of the latest available data for that meter from its gatekeeper. If the meter remains on the schedule, this data will be packaged to the next billing and/or LP schedule file.
Note: Current register and voltage data are not read as part of the unregistration process.
When combined with the fact that the system is likely to rediscover the meter (and reinstall it) if it is out in the field, some inconsistencies in data in the period prior to the unregistration may occur. For example, when a gatekeeper is removed while a schedule (whether billing or synchronization) is currently running, the gatekeeper is successfully read and consequently reinstalled. To prevent such inconsistencies, Elster recommends that utilities follow the business processes listed below: For temporary removals (that is, where the meter will go back in the same location in a matter of hours or a day), do not remove the meter from EA_MS. This will ensure that all associations are kept and the system will continue as though the removal did not occur. If the removal is an extended one (that is, where the utility swaps out the meter, brings it back to the shop for maintenance and perhaps re-deploys the meter at a different site at a later time), always remove the meter from the field prior to
92
removing from EA_MS. Once a meter has been removed from EA_MS, allow at least 23 business days (specifically one execution of a synchronization schedule) prior to physically reinstalling the meter in the field.
Note: Because water meters are not assigned to schedules, the Remove action has no effect on water meters. Note: For meters that are removed, EA_MS will not attempt to read them during the schedule even if they are still associated with the schedule.
Deleting a meter
This action allows you to delete a meter from EA_MS. However, if a meter is installed in the field (that is, has a valid installation date) it must be removed (using Action > Meter > Remove) before it can be deleted from the system. Deleting a meter removes it completely from the system along with all its associations (including any node-gatekeeper associations). You will not be able to access any of the meter reports for the deleted meter. However, schedule reports will work. Caution: If you intend to mark a meter as removed from the field, you should use Meter > Modify to enter a valid Field Removal Date.
Note: Deleted REX meters will not be automatically unregistered by EA_MS. Elster recommends that you wait for the next synchronization schedule after removal before deleting the meter otherwise the meter will remain in the gatekeeper as registered and will show up in EA_MS as an unknown node.
To delete a meter from EA_MS: 1. From the Actions menu, select Meter > Delete. 2. Retrieve the meter.
93
3. Select the meter to be deleted from the listing. The Delete Meter form displays the selected meters information.
Figure 5-25. Deleting a meter

Warning: This command cannot be undone.
4. Click Submit to complete the action.
Pinging a meter
To assist in troubleshooting EA_LAN communications to a meter, EA_MS allows you to ping a specific REX2 FW 3.0 meter. To ping a REX2 meter: 1. From the Actions menu, select Meter > Ping. 2. Retrieve the meter.

3. Select the meter to be pinged.
94
Figure 5-27. Meter ping results report

The Ping Meter Results report displays detailing the following information: Item Device Name Device Type Network Hop Level Response Received Indicator Total Ping Time (ms) Description Indicates the EA_MS name for the selected meter. Indicates the type of meter pinged.
Note: EA_MS Rel. 7.0 supports REX meters only.

Indicates the number of hops from the gatekeeper to the specified meter. Indicates a response was received by the meter. Indicates the total elapsed time (in milliseconds) between the execution of the Ping command to the receipt of the response by EA_MS. Indicates the distance between two meters in the path. Indicates the received signal strength indicator (RSSI) on that particular link on the response (as heard by the meter on the lower level of the link). Indicates the received signal strength indicator (RSSI) for the on that particular link on the response (as heard by the meter on the lower level of the like) Indicates the received signal strength indicator (RSSI) on that link on the request (as heard by the meter on the higher level of the link).
Inbound Link Distance (meters) Inbound Link RSSI (dBm)
Outbound Link Distance (meters)
Outbound Link RSSI (dBm)
95
Performing an on request read of a meter

This action allows you to perform a direct reading from the meter. Typically this action would be used for troubleshooting or for any purpose that requires a quick check of the meter reading.
Note: Water meters cannot be read on request. You need to perform an on request read of one or more gatekeepers to retrieve Water Registers from Gatekeeper to view meter data for a particular water meter. Note: For special reads (that is, off-cycle reads) of billing data from the meter, use Special Read for Billing.
On Request Read allows you to read not only fixed, standard data components (such as Registers and LP) but also user-defined data sets that the meter is scheduled to collect. The list of standard data components displayed on the user interface is dependent on the specific meter type as well as what EA_MS supports in this release for that meter type. See About data sets on page 30 for details on supported data components by meter type.
Note: Every time EA_MS communicates with an A3 ALPHA meter, it verifies the meters time and will synchronize it if the time is outside configured limits. Every time EA_MS communicates with the ILC1 of a gatekeeper, it verifies its network status.
To perform a read of a meter: 1. From the Actions menu, select Meter > On Request Read. 2. Retrieve the meter.

3. Select the meter to be read. The Read Meter form displays the meters information. 4. Check the Data Components to be read.
96
Component Clear A3 Sag Statuses Clear A3 Statuses Clear Profile Data in Gatekeeper Clear meter statuses
Description Clears sag statuses in A3 ALPHA meter. Clears statuses in A3 ALPHA meter. Cleares gatekeepers profile data. Clears REX meter statuses: No Voltage Detected with Disconnect Closed Demand Threshold Exceeded Load Side Voltage Present (Latched value) Load Side Voltage Present Phase A Low Potential Phase C Low Potential Voltage above maximum threshold Voltage below minimum theshold Demand limiting operations exceeded Tilt warning Reverse energy warning Invalid access warning Configuration table write warning Performs an unscheduled demand reset in the meter. Disables broadcast of usage data to 900MHz EA network in home displays by REX version 4.1, REX2 meters. Enables broadcast of usage data to 900MHz EA network in home displays by REX version 4.1, REX2 meters. Reads meters event log. Reads the following events and alarms from A3 ALPHA meters with EA_NIC: PQ Events All outage events Meter alarms Tamper alarms This component only reads new events since the last reading of the event or exception log. See A3 ALPHA meter event types. Reads exceptions from the Gatekeepers ILC.
Demand Reset Disable EnergyAxis Broadcast
Enable EnergyAxis Broadcast
Endpoint Event Log Events and Exceptions (A3 ALPHA meter and Gatekeeper only)
97
Component Health Check A3
Description This is a short session with the A3 ALPHA meter or Gatekeeper that verifies the following: WAN link is operational and the meter responds to EA_MS requests (WAN health) meter serial number matches what EA_MS expects (checks provisioning errors) EA_MS could authenticate with the meter (checks provisioning errors) EA_MS could encrypt/decrypt communications (is supported and enabled, checks provisioning and configuration errors) comm. address (IP addr/port or phone number) is valid and the device ID (for multidrop installations) is correct the meter configuration has been updated by Metercat and re-reads configuration tables if so meter status and reports errors Reads any new events from the event log Checks and synchronizes the meter clock if necessary This component does a quick session with only the Gatekeeper module/ILC of the gatekeeper (not the meter itself) and does the following: verifies that the module firmware version is compatible with EA_MS verifies that EA_MS can authenticate with the module checks for health errors in the module This component does a quick session with only the WIC of the Gatekeeper or A3 ALPHA meter to verify: EA_MS can communicate with the WIC board encryption and authentication (if enabled) are functioning properly there are no health problems reported by the WIC board Performs an ICMP ping to an A3 ALPHA meter or Gatekeeper WIC device's comm. address. In many cases this only pings the WAN modem. Performs an ICMP traceroute to an A3 ALPHA meters or Gatekeepers WIC device's comm. address. An event is generated if the route has changed from the last time it was read. Reads new entries in the audit log of the Gatekeeper module/ILC board in a gatekeeper. Forces a registered meter to unregister from its gatekeeper. Reads selected gatekeepers performance data including statistics, node registration information, time slice (for gatekeeper), etc. By default, only the statistics are displayed on the reading report.
Health Check ILC
Health Check WIC
ICMP Ping
ICMP Traceroute
ILC Audit Log LAN Message to Force a Meter to Unregister LAN Performance (gatekeeper only)
98
Component Load Profile (gatekeeper, A3 ALPHA meter, and REX meters)
Description Reads the selected gatekeepers or A3 ALPHA or REX meters load profile data directly from the meter (that is, a call is made to the meter). The system also calculates and displays a summary view of LP data for each channel. By default only summary information is displayed; however detailed interval data can be viewed from the user interface, if specified.
Note: Elster recommends using either Load Profile (last 24 hours) or Load Profile (last One week) to collect LP data. Note: When selected for REX or A3 ALPHA with EA_NIC meters, a call will be made to the gatekeeper and all available LP data from the meter to the last completed interval will be read.
Load Profile (last 24 hours) REX, REX2, A3 ALPHA with EA_NIC (reads the data from the endpoint meter directly over the EA_LAN using the gatekeeper).
Note: Elster recommends using either Load Profile (last 24 hours) or Load Profile (last One Week) to collect LP data.
Load Profile (last One Week) REX, REX2, A3 ALPHA with EA_NIC (reads the data from the endpoint meter directly over the EA_LAN using the gatekeeper).
Note: For REX meters reading 15 min LP data, the full last week of LP data may not be returned to EA_MS. Note: Elster recommends using either Load Profile (last 24 hours) or Load Profile (last One week) to collect LP data.
Load Profile from Gatekeeper (REX meter and A3 ALPHA meter with EA_NIC) Reads load profile data for the selected REX meter or A3 ALPHA meter with EA_NIC from the meters registered gatekeeper.
Note: Elster recommends using either Load Profile (last 24 hours) or Load Profile (last One week) to collect LP data. Note: This component is displayed in the data component list on the on request read form only if the REX meter or A3 ALPHA meter with EA_NIC is assigned to a data set containing this component.
Outage and Restoration Events from Endpoint Outage and Restoration Events from Gatekeeper Present Values Reads the present demand values (that is, the current demand value in this demand interval) and a set of present instrumentation values from the gatekeeper or A3 ALPHA meter.
99
Component Read Gas Data from Gatekeeper (gatekeeper)
Description Reads usage and status data from the specified gatekeeper.
Note: During a scheduled read the gas data is cleared after a successful read. Note: The Gas Registers from Gatekeeper component is required for on request and scheduled reads of gas meter data.
Read Water Data from Gatekeeper (gatekeeper) Reads usage and status data from the specified gatekeeper.
Note: During a scheduled read the water data is cleared after a successful read. Note: The Water Registers from Gatekeeper component is required for on request and scheduled reads of water meter data.
Read home area network status Reads status and events from home area devices. Event types are: Load Control Event (future) Display Message Event (future) Commissioning Status Event Decommissioning Status Event Energy Conservation Event Time of Use Event (including CTO events) Home Area Network Event Reads the selected meters data registers including current, previous period1, previous season1, meter statuses, voltage, reset count, outage count, instrumentation values, etc. For REX meters, EA_MS calls the gatekeeper to which the REX meter is registered and then the gatekeeper communicates over the LAN with the specified REX meter.
Registers (gatekeeper, A3 ALPHA meter, and REX meters)
Note: Although all statuses in the current table are read, by default only abnormal statuses that are a change from previous values are reported in the file and on the user interface.
Registers from Gatekeeper (gatekeeper, A3 ALPHA meter, and REX meters) Reads REX meters and A3 ALPHA nodes data registers from the associated gatekeeper, including: current period previous period previous season configuration change snapshots meter statuses instrumentation values voltages outage count If a REX meter is selected, this component returns data for the specified REX meter from the gatekeeper. If a gatekeeper is selected, EA_MS returns the above data for every REX meter registered to the gatekeeper. Reset A3 EVents Reset Communication statistics Reset ILC Events Clears (resets) events and statuses in the gatekeeper module/ILC board on a gatekeeper.
100
Component Sag Log (A3 ALPHA meter and Gatekeeper only) Sag Log Counter (A3 ALPHA meter and Gatekeeper only) Start Node Scan Test A3 Battery Voltage Unregister from Gatekeeper Voltage <Data Set Name>
1. Gatekeepers.
Description Reads new sag log entries from the gatekeeper or A3 ALPHA meter. Reads the sag log counter values from the gatekeeper or A3 ALPHA meter.
Reads three days of voltage data from REX2 meters FW 2.0 or higher. List of data sets defined in EA_MS based on selected meter type.
Note: Billing data sets (that is, data sets that include a demand reset as a component) appear only in the list of Advanced Metering Functions. Elster recommends using Special Read for Billing for reading billing data sets. Note: The list of available data components displayed for on request read actions (such as, On Request Read and Advanced Metering Functions) is limited by what the meter type supports. Note: Selecting a Registers data component for a REX meter results in a call to the gatekeeper to which the REX meter is registered then the gatekeeper reads the REX meter. Selecting a REX Registers from Gatekeeper results in a call to the gatekeeper to retrieve data already collected from the specified REX meter (that is, will not retrieve the data that is still in the REX meter but has not been read by the gatekeeper). Note: When selecting a Load Profile data component, you must specify a date and time range. If no time range is selected for the A3 ALPHA meter, only LP data stored since the last read will be collected. See Reading load profile data on page 33.
5. Select the From and To dates and times (applies to load profile data only and not to other data components) for the A3 ALPHA meter.
Note: These dates and times are optional parameters. If you leave these fields blank, EA_MS will return interval data from the last execution of an on request read. To minimize confusion, Elster recommends that you specify the date range for which you want data. Also note that for REX meters, an on request read of LP data will always return all the LP data stored in the gatekeeper for that meter because EA_MS does not support the selection of specific LP ranges.
101
Figure 5-29. Reading a meter on demand

Note: This command initiates a call to the selected meter.
6. Click Submit to initiate the call to the meter to read the selected information.
Note: If the meter is currently being read (for example, a scheduled read) EA_MS will return with the following message - Failed - meter busy will appear to not dial the meters phone number. Note: On request readings are stored in XML files on the server.
The Reading Summary form displays the data report of the read meter.
102
Figure 5-30. On request read results - gatekeeper reading summary

7. Select the Reading Details tab to view details on all meters read. The Reading Details report displays the data read from the meter. All reading data time stamps and any other information coming from the meter is displayed in meter local time with adjustment for DST (if meter is programmed to observe DST). In addition, the report also displays an event if the meters time was synchronized during the session or if the REX meter has been discovered as well as some status information. See Meter Readings Report on page 138 for details on the report.
Figure 5-31.
8. Select a data component from the drop list to view the meters data for the selected component.
Figure 5-32. Choosing a data component
103
104
Performing a health check on a meter

To check the health of a meter: 1. From the Action menu, select Meter > On Request Read. 2. Search for the appropriate meter (A3 ALPHA meter with EA_NIC, A3 ALPHA meter with WIC, or Gatekeeper). 3. Select the meter from the listing. 4. From the Component Type, select one of the following, as appropriate:
105
Health Check A3 - checks the health of the meter Health Check ILC - checks the health of the EA_Gatekeeper module used to manage the EA_LAN and the elements Health Check WIC - checks the health of the WIC (for example, ethernet WIC, 1xRTT/CDMA WIC, or GPRS/GSM WIC). 5. Click Submit. The meter reading reports the health of the WIC.
Figure 5-33. Health Check - ethernet WIC summary
Figure 5-34. Health Check - ethernet WIC reading details
106
Figure 5-35. Health Check - ILC/Gatekeeper summary
Figure 5-36. Health Check - ILC/Gatekeeper reading details
Figure 5-37. Health Check - A3 ALPHA meter summary
Figure 5-38. Health Check - A3 ALPHA meter reading details
107
Reading meter time

Note: This action is available for A3 ALPHA meters and gatekeepers only. The search list of meters is filtered to exclude REX, REX2, and water meters, and A3 ALPHA nodes.
While EA_MS reads the meters time every time the system communicates with the meter, you can use this action to read a meters time on demand and compare it to the server time.

To read a meters time: 1. From the Actions menu, select Meter > Read Time. 2. Retrieve the meter. 3. Select the meter to be read. The Read Time for Meter form displays the meters information, meter time (in meter local time), server time (in meter local time) and whether the meter is currently observing DST.
Note: Every time EA_MS communicates with an A3 ALPHA meter or an A3 ALPHA gatekeeper, it verifies the meters time and will synchronize it if the time is greater than the configured minimum limit and less than the maximum limit.
Figure 5-39. Reading meter time

4. Click Submit to initiate the call to the meter to read the time. The Read Time for Meter form displays the meters time.
Figure 5-40. Meter Read Time results
108
Reading a meters configuration

Note: This action is available for A3 ALPHA meters and gatekeepers only. The search list of meters is filtered to exclude REX meters, water meters, and A3 ALPHA nodes.
For A3 ALPHA meters and gatekeepers, EA_MS will always read the configuration during the first communication session and will check whether the configuration has changed on all subsequent communication sessions. For REX meters, most relevant configuration information is obtained from the marriage file (see Importing a marriage file on page 134). This action allows you to read a meters configuration on demand (for checking whether the meter can support data requirements or for troubleshooting meter problems). To read a meters configuration: 1. From the Actions menu, select Meter > Read Configuration. 2. Retrieve the meter. 3. Select the meter to be read. The Read Configuration for Meter form displays the meters information.
Figure 5-41. Read Configuration

4. Click Submit to initiate a call to the meter to read the configuration. The View Meter report displays the meters information. See Viewing a meters information on page 71 for details on the information displayed in this report.
109
110
Setting a meters time

Note: This action is available for A3 ALPHA meters and Gatekeepers only. The search list of meters is filtered to exclude REX meters, water meters, and A3 ALPHA nodes.
This action allows you to adjust (that is, synchronize) a meters time to the servers time. You would use this action to adjust a meters time when EA_MS cannot automatically perform the adjustment, for example, if EA_MS communicates with the meter and the time difference is greater than the configured limit.
Note: Every time EA_MS communicates with an A3 ALPHA meter or an A3 ALPHA gatekeeper, it verifies the meters time and will synchronize it if the time is greater than the configured minimum limit and less than the maximum limit.
This action is independent of the normal time synchronization rules governing automatic meter time synchronization by EA_MS (for example, EA_MS limits and LP boundary restrictions). Warning: This action cannot reset a meters time across a date or midnight boundary (for example, from 23:59:10 to 00:01:05). If the meter time is outside the date boundary, it will be adjusted forward to 23:59:59 or backward to 00:00:01 depending on the adjustment needed to synchronize the meters time to the servers time.
Note: To set a meters date you must reprogram the meter using the Program task of Metercat, Elsters meter support software.
To set a meters time: 1. From the Actions menu, select Meter > Set Meter Time. 2. Retrieve the meter. 3. Select the meter to be set. The Set Time for Meter form displays the meters information.
Figure 5-42. Setting a meters time

4. Click Submit to initiate a call to the meter to set the time. The Set Time for Meter form displays the meter time (in meter local time) at the beginning of the communication session (prior to the time adjustment), the server time (in meter local time) at the beginning of the communication session, and whether the meter is currently observing DST.
111
Figure 5-43. Meter Time set
Performing advanced metering functions

Note: This action should be available only to users authorized to perform demand resets on meters. In the security model currently implemented in the system, this includes meter shop personnel and system administrators. The security profiles for normal customer service representatives and CIS personnel or users of system reports do not allow access to this function.
The Advanced Metering Functions action allows you to read data as well as perform demand reset, reset event and exception logs, perform an on request synchronize gatekeepers with EA_MS [formerly download], reset LAN performance statistics and optimize LAN in the A3 ALPHA gatekeeper. This action is primarily intended as a troubleshooting mechanism.
Note: Water meters communicate only up to EA_MS (that is they cannot receive information from EA_MS) therefore they cannot be read directly. You must read the meter by selecting the component, Water Registers from Gatekeeper. Note: To perform special billing reads that include demand resets use the Meter > Special Read for Billing. Note: Every time EA_MS communicates with an A3 ALPHA meter or an A3 ALPHA gatekeeper, it verifies the meters time and will synchronize it if the time is greater than the configured minimum limit and less than the maximum limit.
To read a meter and perform a demand reset (or to reset event logs and LAN performance statistics): 1. From the Actions menu, select Meter > Advanced Metering Functions. The On Request Read - Advanced - Meter form displays allowing you to select a meter based on the meter, account number, account name, site ID, etc. 2. Retrieve the meter. 3. Select the meter to be set. The On Request Read - Advanced form displays the meters information.
112
Figure 5-44. On Request Read - Advanced form (gatekeeper)

4. Check the Data Components to be read. . Component Clear A3 Sag Statuses Clear A3 Statuses Clear Profile Data in Gatekeeper Clear meter statuses Description Clears sag statuses in A3 ALPHA meter. Clears statuses in A3 ALPHA meter. Cleares gatekeepers profile data. Clears REX meter statuses: No Voltage Detected with Disconnect Closed Demand Threshold Exceeded Load Side Voltage Present (Latched value) Load Side Voltage Present Phase A Low Potential Phase C Low Potential Voltage above maximum threshold Voltage below minimum theshold Demand limiting operations exceeded Tilt warning Reverse energy warning Invalid access warning Configuration table write warning Performs an unscheduled demand reset in the meter.
Demand Reset
113
Component Disable EnergyAxis Broadcast
Description Disables broadcast of usage data to 900MHz EA network in home displays by REX version 4.1, REX2 meters. Enables broadcast of usage data to 900MHz EA network in home displays by REX version 4.1, REX2 meters. Reads meters event log. Reads the following events and alarms from A3 ALPHA meters with EA_NIC: PQ Events All outage events Meter alarms Tamper alarms This component only reads new events since the last reading of the event or exception log. See A3 ALPHA meter event types. Reads exceptions from the Gatekeepers ILC. This is a short session with the A3 ALPHA meter or Gatekeeper that verifies the following: WAN link is operational and the meter responds to EA_MS requests (WAN health) meter serial number matches what EA_MS expects (checks provisioning errors) EA_MS could authenticate with the meter (checks provisioning errors) EA_MS could encrypt/decrypt communications (is supported and enabled, checks provisioning and configuration errors) comm. address (IP addr/port or phone number) is valid and the device ID (for multidrop installations) is correct the meter configuration has been updated by Metercat and re-reads configuration tables if so meter status and reports errors Reads any new events from the event log Checks and synchronizes the meter clock if necessary This component does a quick session with only the Gatekeeper module/ILC of the gatekeeper (not the meter itself) and does the following: verifies that the module firmware version is compatible with EA_MS verifies that EA_MS can authenticate with the module checks for health errors in the module This component does a quick session with only the WIC of the Gatekeeper or A3 ALPHA meter to verify: EA_MS can communicate with the WIC board encryption and authentication (if enabled) are functioning properly there are no health problems reported by the WIC board Performs an ICMP ping to an A3 ALPHA meter or Gatekeeper WIC device's comm. address. In many cases this only pings the WAN modem.
Enable EnergyAxis Broadcast
Endpoint Event Log Events and Exceptions (A3 ALPHA meter and Gatekeeper only)
Health Check A3
Health Check ILC
Health Check WIC
ICMP Ping
114
Component ICMP Traceroute
Description Performs an ICMP traceroute to an A3 ALPHA meters or Gatekeepers WIC device's comm. address. An event is generated if the route has changed from the last time it was read. Reads new entries in the audit log of the Gatekeeper module/ILC board in a gatekeeper. Forces a registered meter to unregister from its gatekeeper. Reads selected gatekeepers performance data including statistics, node registration information, time slice (for gatekeeper), etc. By default, only the statistics are displayed on the reading report. Reads the selected gatekeepers or A3 ALPHA or REX meters load profile data directly from the meter (that is, a call is made to the meter). The system also calculates and displays a summary view of LP data for each channel. By default only summary information is displayed; however detailed interval data can be viewed from the user interface, if specified.
ILC Audit Log LAN Message to Force a Meter to Unregister LAN Performance (gatekeeper only)
Load Profile (gatekeeper, A3 ALPHA meter, and REX meters)
Note: Elster recommends using either Load Profile (last 24 hours) or Load Profile (last One week) to collect LP data. Note: When selected for REX or A3 ALPHA with EA_NIC meters, a call will be made to the gatekeeper and all available LP data from the meter to the last completed interval will be read.
Load Profile (last 24 hours) REX, REX2, A3 ALPHA with EA_NIC (reads the data from the endpoint meter directly over the EA_LAN using the gatekeeper).
Note: Elster recommends using either Load Profile (last 24 hours) or Load Profile (last One Week) to collect LP data.
Load Profile (last One Week) REX, REX2, A3 ALPHA with EA_NIC (reads the data from the endpoint meter directly over the EA_LAN using the gatekeeper).
Note: For REX meters reading 15 min LP data, the full last week of LP data may not be returned to EA_MS. Note: Elster recommends using either Load Profile (last 24 hours) or Load Profile (last One week) to collect LP data.
Load Profile from Gatekeeper (REX meter and A3 ALPHA meter with EA_NIC) Reads load profile data for the selected REX meter or A3 ALPHA meter with EA_NIC from the meters registered gatekeeper.
Note: Elster recommends using either Load Profile (last 24 hours) or Load Profile (last One week) to collect LP data. Note: This component is displayed in the data component list on the on request read form only if the REX meter or A3 ALPHA meter with EA_NIC is assigned to a data set containing this component.
115
Component Outage and Restoration Events from Endpoint Outage and Restoration Events from Gatekeeper Present Values
Description
Reads the present demand values (that is, the current demand value in this demand interval) and a set of present instrumentation values from the gatekeeper or A3 ALPHA meter. Reads usage and status data from the specified gatekeeper.
Read Gas Data from Gatekeeper (gatekeeper)
Note: During a scheduled read the gas data is cleared after a successful read. Note: The Gas Registers from Gatekeeper component is required for on request and scheduled reads of gas meter data.
Read Water Data from Gatekeeper (gatekeeper) Reads usage and status data from the specified gatekeeper.
Note: During a scheduled read the water data is cleared after a successful read. Note: The Water Registers from Gatekeeper component is required for on request and scheduled reads of water meter data.
Read home area network status Reads status and events from home area devices. Event types are: Load Control Event (future) Display Message Event (future) Commissioning Status Event Decommissioning Status Event Energy Conservation Event Time of Use Event (including CTO events) Home Area Network Event Reads the selected meters data registers including current, previous period1, previous season1, meter statuses, voltage, reset count, outage count, instrumentation values, etc. For REX meters, EA_MS calls the gatekeeper to which the REX meter is registered and then the gatekeeper communicates over the LAN with the specified REX meter.
Registers (gatekeeper, A3 ALPHA meter, and REX meters)
Note: Although all statuses in the current table are read, by default only abnormal statuses that are a change from previous values are reported in the file and on the user interface.
116
Component Registers from Gatekeeper (gatekeeper, A3 ALPHA meter, and REX meters)
Description Reads REX meters and A3 ALPHA nodes data registers from the associated gatekeeper, including: current period previous period previous season configuration change snapshots meter statuses instrumentation values voltages outage count If a REX meter is selected, this component returns data for the specified REX meter from the gatekeeper. If a gatekeeper is selected, EA_MS returns the above data for every REX meter registered to the gatekeeper.
Reset A3 EVents Reset Communication statistics Reset ILC Events Sag Log (A3 ALPHA meter and Gatekeeper only) Sag Log Counter (A3 ALPHA meter and Gatekeeper only) Start Node Scan Test A3 Battery Voltage Unregister from Gatekeeper Voltage <Data Set Name>
1. Gatekeepers.
Clears (resets) events and statuses in the gatekeeper module/ILC board on a gatekeeper. Reads new sag log entries from the gatekeeper or A3 ALPHA meter. Reads the sag log counter values from the gatekeeper or A3 ALPHA meter.
Reads three days of voltage data from REX2 meters FW 2.0 or higher. List of data sets defined in EA_MS based on selected meter type.
The list of available data components displayed for on request read actions (such as, On Request Read and Advanced Metering Functions) is limited by what the meter type supports.
Note: Selecting a Registers data component for a REX meter results in a call to the gatekeeper to which the REX meter is registered then the gatekeeper reads the REX meter. Selecting a REX Registers from Gatekeeper results in a call to the gatekeeper to retrieve data already collected from the specified REX meter (that is, will not retrieve the data that is still in the REX meter but has not been read by the gatekeeper). Note: For the A3 ALPHA meter, when selecting a Load Profile data component, you must specify a date and time range. If no time range is selected only LP data stored since the last read will be collected. See Reading load profile data on page 33.
5. Select the From and To dates and times (applies only for load profile data) for the A3 ALPHA meter.
117
Note: These dates and times are optional parameters. If you leave these fields blank, EA_MS will return interval data since the last execution of an on request read or all available data for REX meters. To minimize confusion, Elster recommends that you specify the date range for which you want data.
Figure 5-45. On Request Read - Advanced form (REX)

6. Click Submit to initiate a call to the meter for the reading.
Note: On request readings are stored in files on the server.

The Meter Readings Listing Report form displays the reading results.
118
Figure 5-46. On Request Read - Advanced - reading summary (REX)

The Reading Summary report details the following information: Item Communication Session On File Created On Meter Type Account Number Source Name Description The date and time (meter local time) the meter was called. The date and time (GMT) the reading file was created. The Meter Type. The Account No. The Meter Name for the gatekeeper from which the data was read.
119
Figure 5-47. On Request Read - Advanced - reading details (gatekeeper)

The following table describes the information detailed in the Data Report for a gatekeeper: Item Event Data Description Lists events with the date and time of discovery and any additional relevant information (for example, event start date and time). Lists the name, category, and value for statuses read from the meter. The quality flags (A3 ALPHA meter quality flags or REX meter quality flags) active in the meter. The Meter Time; Server Time; Observes DST (Yes/No). Consumption, TOU, Demand, LAN Performance, Instrumentation Values, Outage Count Summary, Statuses, etc.
Statuses Global Quality Flags Clock Requested Data
120
Figure 5-48. On Request Read - Advanced - reading details (REX meter)

7. Click on a Data Report in the list to expand the data report. 8. Select a data component from the drop list to view the meters data for the selected component. The following table describes the information detailed in the Data Report for a meter: Item Event Data Description Lists events with the date and time of discovery and any additional relevant information (for example, event start date and time). Lists the name, category, and value for statuses read from the meter. The quality flags (A3 ALPHA meter quality flags or REX meter quality flags) active in the meter. Consumption, TOU, Demand, LAN Performance, Instrumentation Values, etc.
Statuses Global Quality Flags Requested Data
Performing a special read for billing

Note: To perform this action, the selected meter must have an associated data set (with a demand reset) and a billing schedule. Note: Elster recommends using this action on electricity meters only.
121
This action allows you to perform a special billing read associated with customer move ins, customer move outs, service disconnect/reconnect. Billing data is collected and a demand reset is performed if the meter is on a demand rate (that is, has a demand reset as part of its billing data set). When using this action, the data is returned to the users browser for online viewing and an XML file is created and saved to the file location specified in the meters assigned billing schedule. EA_MS treats this action similar to a scheduled billing read. If LP is part of the customers billing determinants, then the internal pointer that the system uses to keep track of the last interval read from the meter on a scheduled read will get incremented so that the next execution of the schedule will pick up from where the special read left off. In addition, if the meter is on a demand rate (i.e. has demand reset as part of billing data set), the special billing read will also read and package previous period and previous season data (if there was a season change since the last billing read) in the billing schedule directory.
Note: If the meter is assigned to a TOU schedule but it does not have a demand reset, EA_MS will not package previous data.
To read a meter for billing: 1. From the Actions menu, select Meter > Special Read for Billing. 2. Retrieve the meter. 3. Select the meter to be read. The Read Meter form displays the meters information. 4. Check the Data Set to be read.
Note: To read other meter information (such as events, LAN performance, etc.) use On Request Read. To reset demand, performance statistics or event logs, use Advanced Metering Functions.
Figure 5-49. Special Read for Billing - gatekeeper

Note: This command initiates a call to the selected meter to read the billing data and usually triggers a demand reset.
If the data set includes a demand reset as part of the data components (see Viewing a list of all data sets on page 193 for information on viewing a data sets properties), a demand reset will be performed. This function can be made available to users who are not (under normal circumstances) allowed to do a demand reset to the meter but are required to do initial and final reads to fulfill their job function. In the current implementation
122
customer service representatives and CIS personnel who are not allowed to do independent demand resets can execute this action and perform a reset that is coordinated with the special read. 5. Click Submit to initiate a call to the meter for the reading. The Read Meter for Billing form displays the reading results. 6. Select a data component from the drop list to view the meters data for the selected component.
Figure 5-50. Special Read for Billing results - reading summary
123
124
125
The following table describes the information displayed in the Read Meter for Billing results report: Item Meter Data Reset Count Data Event Data Description UOM, Direction (meter), Measurement Period, Tier, Time stamp, Meter Reading. UOM, Time stamp, and Meter Reading. The REX/REX2 Meter Events or A3 ALPHA Meter Events, Discovered At date/time, and Additional Information (for example, start date and time).
126
Connecting a meters service
Use authorized utility safety procedures before closing the switch to restore electrical service. The consumer should be ready to receive power when the reconnect service command is implemented. Property damage, personal injury or death can result if safety precautions have not been followed and proper consumer contact established.
EA_MS supports connecting service to the following meters: REX meters with service disconnect switch REX2 meters with service disconnect switch AGI RLC polyphase interrupter connected to one of the following: A3 ALPHA meters FW 4.0 with EA_NIC A3 ALPHA meters FW 4.0 with Elster WIC To connect a meters service: 1. From the Actions menu, select Meter > Connect Service. 2. Retrieve the meter.
Note: EA_MS displays only those meters that have the service disconnect switch (that is, meter type is REX-D or A3 ALPHA meters).
Figure 5-51. Connecting Service

Note: This command initiates a call to the selected meter. Note: EA_MS does not prevent executing a Connect Service action if the meters current status is connected. The action will call the meter, verify its status and return the result (that is, the action fails, the meter is connected).
3. Click Submit to initiate a call to the meter to execute the command. EA_MS performs the following actions. a. Reads statuses and determines if the action can be safely performed. b. Connects power. c. Reads statuses and determines if the action was successful.
127
d. Reads register data. The Connect Service at Site form displays the reading results. The Statuses section shows the state of the action in the Service category (see REX/REX2 Meter Statuses) after the action execution.
Figure 5-52. Connect Service - reading summary
128
129
Figure 5-53. Connect Service - reading details
Connect Error and Warning Messages

Pre-check Messages
Error: Communication error on initial status check. Operation terminated. Error: Disconnect switch is already open. Operation terminated. Error: Disconnect switch state change is pending. Setting switch state to unknown. Operation terminated. Error: Initial status check indicates the disconnect switch is open with load voltage present. Setting switch state to unknown. Operation terminated. Error: Disconnect switch is currently open. Error: Disconnect switch is currently closed. Error: Initial status check indicates the disconnect switch is closed with no load voltage present. Setting switch state to unknown. Operation terminated. Error: Disconnect switch is charging.: Time remaining - xx Error: Disconnect switch IS_DISCON_SWITCH_CLOSED_NO_VOLT flag is set. Error: Communication error attempting to operate switch. Setting switch state to unknown. Operation terminated.
Post-check Messages
Error: Communication error attempting to verify switch operation. Setting switch state to unknown. Operation terminated. Error: Disconnect switch is not charging after operation. Setting switch state to unknown. Operation terminated. Error: Disconnect switch state change is pending. Setting switch state to unknown. Operation terminated. Error: Final status check indicates the disconnect switch is open with load voltage present. Setting switch state to unknown. Operation terminated. Error: Disconnect switch is currently closed. Error: Final status check indicates the disconnect switch is closed with no load voltage present. Setting switch state to unknown. Operation terminated. Warning: Register data not read from the meter.
Troubleshooting Connecting Service

Load Voltage Present
If the action returns with an error Disconnect switch is currently open with load voltage present. Proceed as follows: 1. Send a technician to the site to verify that it is safe to connect service to the meter. 2. If is safe to connect, perform a remote demand reset on the meter (Advanced Metering Functions > Demand Reset). 3. Retry the Connect Service action.
130
Unsafe to Turn on Power

If EA_MS is unable to read the meters statuses before attempting to close the service disconnect switch, EA_MS will return an error Could not verify that it is safe to turn on power. Proceed as follows: 1. Perform a remote demand reset on the meter (Advanced Metering Functions > Demand Reset). 2. Retry the Connect Service action.
Capacitor Charging
If EA_MS is unable to connect the meter because the disconnect switch capacitor is still charging, EA_MS will return an error and indicate the time remaining for the capacitor to charge. Retry the action after the capacitor has charged.
Disconnecting a meters service

EA_MS supports connecting service to the following meters: REX meters with service disconnect switch REX2 meters with service disconnect switch AGI RLC polyphase interrupter connected to one of the following: A3 ALPHA meters FW 4.0 with EA_NIC A3 ALPHA meters FW 4.0 with Elster WIC To disconnect a REX or A3 ALPHA meters service: 1. From the Actions menu, select Meter > Disconnect Service. 2. Retrieve the meter.
Note: EA_MS displays only those REX meters that have the service disconnect switch (that is, meter type is REX / REX-D or A3 ALPHA meters). Note: EA_MS does not prevent executing a Disconnect Service action if the meters current status is disconnected. The action will call the meter, verify its status and return the result (that is, the action fails, the meter is disconnected).
Figure 5-54. Disconnecting Service

3. Click Submit to initiate a call to the meter to execute the command.
131
EA_MS performs the following actions. a. Reads statuses and determines if the action can be safely performed. b. Disconnect power. c. Read statuses and determines if the action was successful. d. Read register data. The Disconnect Service form displays the reading results. The Statuses section shows the state of the action in the Service category (see REX/REX2 Meter Statuses on page 467).
Note: The Open Pending flag may appear as true. This status is only valid if the Change Pending flag is also true. If Change Pending flag is false, you may disregard the Open Pending flag.
Figure 5-55. Disconnect Service - reading summary
132
133
Figure 5-56. Disconnect Service - reading details
Disconnect Errors and Warnings

Pre-check Messages
Error: Communication error on initial status check. Operation terminated. Error: Disconnect switch is already closed. Operation terminated. Error: Disconnect switch state change is pending. Setting switch state to unknown. Operation terminated. Error: Initial status check indicates the disconnect switch is open with load voltage present. Setting switch state to unknown. Operation terminated. Error: Initial status check indicates the disconnect switch is closed with no load voltage present. Setting switch state to unknown. Operation terminated. Error: Disconnect switch is charging.: Time remaining - xx Warning: Disconnect switch LATCHED_IS_LD_SIDE_VOLT_PRESENT flag is set. Error: Communication error attempting to operate switch. Setting switch state to unknown. Operation terminated.
Post-check Messages
Error: Communication error attempting to verify switch operation. Setting switch state to unknown. Operation terminated.
134
Error: Disconnect switch is not charging after operation. Setting switch state to unknown. Operation terminated. Error: Disconnect switch state change is pending. Setting switch state to unknown. Operation terminated. Error: Final status check indicates the disconnect switch is open with load voltage present. Setting switch state to unknown. Operation terminated. Error: Disconnect switch is currently open. Error: Final status check indicates the disconnect switch is closed with no load voltage present. Setting switch state to unknown. Operation terminated. Warning: Register data not read from the meter.
Troubleshooting Disconnecting Service

Failed to Read Statuses
After the service disconnect switch has been opened (that is, service has been shut off), EA_MS reads the statuses of the disconnected meter. However, if EA_MS is unable to read the statuses, it will return a warning Could not verify successful operation of disconnect switch.
Load Voltage Present after Disconnect

If the meter indicates that load voltage is present after the disconnect, this could mean that the household has a backup generator.
Capacitor Charging
If EA_MS is unable to disconnect the meter because the disconnect switch capacitor is still charging, EA_MS will return an error and indicate the time remaining for the capacitor to charge. Retry the action after the capacitor has charged.
Importing a marriage file

A marriage file is distributed with each shipment of REX meters, EA_Repeaters, A3 ALPHA nodes, gas or water modules. These files list meters or EnergyAxis modules that have been shipped to a utility by Elster. Caution: The marriage files for EA_Water modules, EA_Gas modules, A3 ALPHA nodes, and REX meters are different from each other. You cannot merge the files into one file for importing. Attempting to do so will result in a failed import.
Typical information in the marriage file includes the manufacturers serial number, customer serial number, LAN ID, Utility ID (ensures that a REX meter only communicates with a gatekeeper with the same Utility ID), and meter configuration information (that is, supported data components, default display parameters and other configuration information). Most of these parameters are required for EA_MS to communicate with the meter, understand what it supports and interpret the data read from the meter. A marriage file is generated by the meter manufacturer and is emailed to the designated person at the utility. Meter shop personnel must import this file into EA_MS before the meter is deployed in the field or is added to the system using Meter > New. Every meter imported through the marriage file is considered as inventoried until it is installed in the field and either discovered by the system or provided with a valid name and marked as installed through user input. Additionally, if a gatekeeper reports a newly registered node (that is, a REX meter or A3 ALPHA node) for which EA_MS does not have a marriage file entry, the meter will be reported as an unknown node (see Unknown REX Meters Report on page 338) and the system will not execute any other actions on this meter.
135
Once the marriage file has been imported EA_MS can identify a meter by its LAN ID. Caution: EA_MS will not allow a REX meter, an EA_Repeater or an A3 ALPHA node to be added through using Meter > New without first importing the marriage file.
See Sample Marriage files on page 400 for an example of a REX meter marriage file. To import a meters marriage file: 1. From the Actions menu, select Meter > Import Marriage File. The Import Marriage File form displays. 2. Browse for the marriage file.
Figure 5-57. Importing a marriage file

Note: The marriage file can be located in any folder on your local computer or in a shared network folder that is accessible from the local computer.
3. Click Submit to import the marriage file. The results of the action are displayed and are saved to a temporary XML file.
Figure 5-58. Importing marriage file - results

Note: EA_MS will not allow a marriage file to be imported more that once. Re-importing the same marriage file will import only those meters that have been deleted from EA_MS since the prior importation. Note: If any of the meters failed to import, the Import action will indicate failure. Note: EA_MS does not save the imported marriage file.
The Marriage File Audit report provides details on which meters were successfully added and which meters failed to import. See Marriage File Import Audit Report on page 363 for details.
136
Importing a CIS file

After new meters have been installed in the field and their paperwork has been recorded in CIS (customer information system), the CIS system should periodically create a CIS file, following AMR Data Exchange Format (AMRDEF) requirements, to allow the easy setup of new meters in EA_MS. Importing the CIS file into EA_MS allows you to do the following: import new meters assign meters to billing schedules assign meters to TOU schedules modify meters remove meters delete meters perform on request meter reads for a large number of meters disconnect and reconnect REX meters (with service control switch) A CIS file can be created using the EA_MS AMRDEF Reference. See Example CIS files on page 402 for an example of CIS import objects. To import a CIS file: 1. From the Actions menu, select Meter > Import CIS File. The Import CIS File form displays.
Figure 5-59. Importing CIS file

2. Browse for the CIS file.
Note: The CIS file can be located in any folder on your local computer or in a shared network folder that is accessible from the local computer.
3. Click Submit to import the CIS file. The results of the action are displayed and are saved to an XML file.
137
Figure 5-60. Importing CIS file - results

For additional details on features related to CIS imports and integration, please refer to the EA_MS AMRDEF Reference. See CIS Import Audit Report on page 360 for details on all CIS import actions.
Importing a WIC activation file

A gatekeepers WAN interface card (WIC) activation file is distributed with each shipment of gatekeepers. This file details important communications settings for each gatekeepers WIC. Prior to installing a gatekeeper in the field, you must import the WIC activation file. See Sample WIC activation file on page 402. 1. From the Actions menu, select Meter > Import WIC Activation File. The Import WIC activation File form displays.
Figure 5-61. Importing a WIC activation file

2. Browse for the WIC activation file.
Note: The WIC activation file can be located in any folder on your local computer or in a shared network folder that is accessible from the local computer.
3. Click Submit to import the WIC activation file. The results of the action are displayed and are saved to a temporary XML file.
138
Performing a power status check

As part of EnergyAxis System power outage and restoration monitoring, EA_MS allows you to perform a power status check on a group of meters. The group of meters can be registered to multiple gatekeepers. To perform a power status check: 1. From the Actions menu, select Meter > Grouped Operations > Power Status Check. The Power Status Check form displays.
Figure 5-62. Power Status Check form

2. Click Add. 3. Using the Search dialog, select meters to be included in the Power Status Check schedule. 4. Click Submit. 5. To view the results Reports > Meter > Statuses and do a report by choosing the Status category of Power Status Check. This report shows the result of power status check, that is, a list of meters showing which one was powered on or off.
Meter Readings Report

This action allows you to view meter readings returned after an on request read (such as, On Request Read and Advanced Metering Functions) or a scheduled read. EA_MS is a data collection system rather than a data management system. This has several implications that you should be aware of: collected data is stored in files rather than the database: you can generate a report for the selected meter corresponding to each file you cannot see a consolidated view of the data that goes across multiple communication sessions (that is, scheduled reading with one or more resubmits) while data read from the meter is available in the system for later use (until it is purged): each data file corresponds to the type of the read request performed (that is, On Request Read, Special Read for Billing, Advanced Metering Functions, or scheduled, etc.) users are provided a meter-level view of the data and can view readings that span different types of read requests (on request, scheduled, from gatekeeper etc.). In particular, users do not have to know the gatekeeper or query by gatekeeper in order to view the meter data for a REX meter. To view a report of on request readings of a specific meter: 1. From the Reports menu, select Meter > Readings. 2. Select the proper meter type from the Search for drop list.
139
3. Enter the From and To dates and times. 4. Click Search for a listing of meters by Meter Name.
Figure 5-63. Meter Readings report form

5. Select the meter from the search list. Or Click Submit if the exact meter name is entered. EA_MS displays a listing of on request reading files for the selected meter and the specified time period.
Note: Reading files have a time stamp that represents the approximate time that the meter was read. Reading files are displayed sorted most recent first on Reading Date Time (which is approximated by date time of file creation in the users time zone). Note: Reading data is stored in AMRDEF XML files on the server.
140
Figure 5-64. Meter Readings report - gatekeeper
Figure 5-65. Meter Readings report - REX meter
141
Figure 5-66. Meter Readings report - water meter

The following table describes the information displayed in the Meter Readings Listing report: Item File name Reading Date/Time Schedule Name Description The path and file name for the XML reading file. The approximate date and time of the reading. The Schedule Name a hyperlink to the View Schedule Information Report) that created the indicated file. A value of None indicates an on request reading or a special reading for billing.
6. Click a Filename to view a report of the reading data.
Note: The Reading File contents depend on the Schedule type (data component, etc.).
The Display Meter Readings report displays the readings for the selected meter.
Display Meter Readings

The Display Meter Readings report displays the Reading Summary and Reading Details.
142
Figure 5-67. Reading File contents - gatekeeper - reading summary

Meter Statuses link opens the Meter Statuses report. See Meter Statuses Report on page 161 for details.
143
Figure 5-68. Reading File contents - gatekeeper - reading details

Note: In the REX meter, previous period and previous season data are time stamped at midnight (00:00) because that is when the demand reset occurs (on the night before the billing date). However, current period data is time stamped with the date and time of the last successful read by the gatekeeper which could be before midnight. Therefore a situation could occur where the current period data time stamp is older than the previous period data time stamp. The next successful read of the REX meter will update the current period data time stamp to after midnight. Additionally, if a REX meter failed to perform a demand reset at midnight (00:00), the gatekeeper will initiate the reset at the time of the reading (for example, at 01:00). The previous data will still be time stamped at midnight.
144
Figure 5-69. Reading File contents - REX meter - reading summary
Figure 5-70. Reading File contents - REX meter - reading details
Figure 5-71. Reading File contents - water meter - reading summary
145
Figure 5-72. Reading File contents - water meter - reading details
Figure 5-73. Reading File contents - A3 ALPHA node - reading summary
146
Figure 5-74. Reading File contents - A3 ALPHA node - reading details
147
Note: Reading data and any other time stamps from the meter are shown in meter local time with DST adjustment (if applicable).
148
The following table describes the information detailed in the Meter Readings Listing report: Item Meter Type Description Account Number Site Source Name Clock Statuses The Meter Type. The Description. The Account No. The Site ID. The gatekeeper that the meter is assigned to (that is, the gatekeeper that provided the readings). The Meter Time; Server Time; Observes DST (Yes/No). The Name, Category, and Value for the A3 ALPHA Meter Statuses, A3 ALPHA meter with EA_NIC Statuses, and REX/ REX2 Meter Statuses. UOM, Direction (meter), Measurement Period, Tier, Time stamp, Meter Reading. UOM, Direction (meter), Measurement Period, Tier, Time stamp, Meter Reading. Counter for number of demand resets in the meter Lists events that occurred in the meter. Name (whether voltage, current, phase angle, or line frequency), Phase (A, B, or C), Value, and Timestamp. Number of outage event counted since the previous reading (includes the previous count value). Value and Previous Value for reverse energy measurement. Description
Consumption Data Max Demand Data Demand Reset Count Data Event Data Instrumentation Values Outage Count Summary Reverse Energy Summary
Viewing Load Profile Data

To view load profile (LP) data: 1. From the Meter Readings Report select a file name for a schedule that collects load profile. The Reading Properties report displays.
149
Figure 5-75. Reading File - Load Profile
150
Figure 5-76. Reading File - Load Profile - reading details

The following table describes the information detailed in the Display Meter Readings report: Item Communication Session On File Created On Meter Type Serial # Description Account Number Site Number of LP channels Interval length Start Time End Time Description The date and time the communication session was initiated. The date and time the schedule reading file was created. The Meter Type. The Serial Number. The Description. The Account No. The Site ID. The number of load profile channels the meter is programmed to collect. The interval length in minutes. The date (YYYY-MM-dd format) and time ((HH:mm:ss format) the readings started. The date (YYYY-MM-dd format) and time ((HH:mm:ss format) the readings ended.
151
Item Pulse Multiplier UOM Direction (metered quantity) Channel Summation Event Data
Description The Pulse Divisor (combined value of pulse divisor and Ke). The UOM for the indicated channel. Indicates whether the indicated measurement is for Delivered or Received energy. Indicates the channel number. Indicates the summation of the energy values for the indicated channel between the start and end times. Indicates the recent event, the time stamp of the event, and any additional information (if available). See Events and statuses on page 457. The Meter Time; Server Time; Observes DST (Yes/No). Name (per phase instrumentation reading), Phase, Value, Timestamp. Indicates the last outage count prior to this reading date and time.
Clock1 Instrumentation Values Outage Count Summary1
1. A3 ALPHA meters and gatekeepers only.
2. Select one of the report types for the Load Profile Summary: a. Excel - displays a new browser window with the load profile data in an Excel spreadsheet that can be saved as an Excel file (*.xls) (Figure 5-77)
Note: Depending on your Internet Explorer security settings you may see a message that the Excel report is suspicious. This is the default behavior of Internet Explorer. Please select to continue to view the file. Note: The Excel file will indicate the interval statuses using color coded indicators.
b. HTML - displays the load profile data in the current browser window (Figure 5-78 and Figure 5-79)
Note: The HTML file will indicate the interval statuses using color coded indicators (see Figure 5-79 for an example).
c. XML - displays a new browser window with the load profile data in an XML file format (Figure 5-80)
Note: Load profile data is detailed by interval period and by channel.
152
Figure 5-77. Load Profile - Excel file
153
Figure 5-78. Load Profile - HTML file
154
Figure 5-79. Load Profile - HTML example with interval statuses
155
Figure 5-80. Load Profile - XML file
Meters Not Read Report

This report allows you to create a list of meters that have not been read since a specified date and time. Use this report in the following scenarios: to identify meters that have been installed in the field but have not been read from since then, either because no attempt was made or it was expected to read but did not to identify any meters that were expected but have not been read since a specified date and time (identify any communication failures, RF holes, etc.) For example, if the system is setup to read REX meter data from gatekeepers every day at 2:00 AM, you may run this report daily at 8:00 AM with the From date and time set to 00:00 AM of the current day and identify which meters have readings older than the time stamp specified (that is, whose scheduled 2:00 AM reading did not occur). 1. From the Reports menu, select Meter > Not Read. The Meters Not Read form displays. 2. Enter the From date and time (usually a time before the last expected schedule read);
156
Or Check to use the Installation Date (Field Install Date).
Figure 5-81. Meters Not Read form

3. Click Submit to create the report. The Meters Not Read report displays those meters that have not been read since the selected date and time.
Note: This report is sorted by meter type allowing users to easily identify gatekeeperrelated issues.
Figure 5-82. Meters Not Read report

The Meters Not Read report lists the Meter Name, Serial Number, Meter Type/ Description, LAN ID, Installation Date/Time, Registration Date/Time and Last Read Date/Time. 4. Click a Meter Name to view the meter. The View Meter report displays the selected meters information (see Viewing a meters information on page 71 for an example).
Meter Events Report

To view a report of meter events by meter name or by event category (but not both at the same time): 1. From the Reports menu, select Meter > Events.
157
2. From the Meter Events drop list select one of the following: a. Select the Event Category from the drop list: Miscellaneous Tamper Alert Full Power Outage/ Restoration Meter Health Service Firmware Upgrade Power Quality Audit Log Voltage Reading Network PQM
b. Event Type - to view all instances of a particular event (see Events and statuses on page 457). c. Meter Name - to view events for a particular meter. d. Search for - to filter the list of meters by Meter Type.
Figure 5-83. Meter Events Report form

3. If you selected Meter Name, enter the particular meter or Search for the meter name.
158
Figure 5-84. Meter Events Report (by meter name)

4. If you selected Category, select the Category. 5. Select the Type (A3 ALPHA Meter Events, A3 ALPHA meter with EA_NIC Events, REX/ REX2 Meter Events, EA_Water Meter Statuses, or EA_Gas Meter Events). 6. Select the From and To date and time. 7. Click Submit to create the report.
159
Figure 5-85. Meter Events Report by Category (all meters)

The table below describes the information displayed by the Meter Events Report. Item Account Number Meter Name Serial Number Event Category Event Type Additional Information Description The Account No. of the meter. The Meter Name (a hyperlink to View Meter Report) The meters Serial Number. Indicates the category for the particular event. Indicates the event name. Indicates additional information regarding the particular event; may include one or more of the following: magnitude value angle value LAN threshold value LCD event code other importance information Indicates the beginning date and time for the event. Indicates the date and time the server detected the event.
Started Detected
Meter Alarms Report

This report allows you to list those events that have been defined as alarms in EA_MS.
160
To view a report of meter alarms by meter name: 1. From the Reports menu, select Meter > Alarms. 2. From the Search for drop list, select a meter type. 3. Enter the Meter Name. Or Use a wildcard (% or *) with or without a character string. 4. Search for - to filter the list of meters by Meter Type. 5. Select the From and To date and time.
Figure 5-86. Meter Alarms Report form

6. Click Submit to create the report.
161
Figure 5-87. Meter Alarms Report
Meter Statuses Report

To view a report of meter statuses by meter name: 1. From the Reports menu, select Meter > Statuses. 2. Select the Status Category from the drop list: Service Tamper Alert Meter Health Miscellaneous Power Quality General Communications Security LAN Performance REX Network Meter Communication Power Status Check
3. Select the Status Name from the drop list (see Events and statuses on page 457). 4. Enter the Meter Name. Or Use a wildcard (% or *) with or without a character string. 5. Select a Meter Type from the Search for drop list. 6. Select the From and To date and time.
162
Figure 5-88. Meter Statuses Report form

163
Figure 5-89. Meter Statuses Report (by category)
164
Figure 5-90. Meter Statuses Report (meters with disconnect)

EA_MS reads and reports the following disconnect statuses for REX meters with each meter read: Disconnect Relay Open Is Load Side Voltage Present No Voltage with Disconnect Switch Closed By default, the most recent values will be reported on the Meter Status Report for those meters. Also, EA_MS generates the following new events: No Voltage Detected with Disconnect Closed Meter Reports Load Side Voltage Detected With Disconnected Service
Meter Inventoried Report

This report allows you to view a list of all meters that are currently inventoried (that is, according to EA_MS, the listed meters have not been installed in the field). Inventoried meters are defined by the system as those that do not have a valid installation date. For REX meters this action reports the following meters:
165
meters whose marriage file has been imported and do not have a valid installation date meters that have not been added to EA_MS with a valid installation date (Meter > New) meters that have not been reported by a gatekeeper meters that have been removed (Meter > Remove) A REX meter for which marriage file is not imported and is reported by a gatekeeper will be reported as an unknown node (see Unknown REX Meters Report on page 338). From the Reports menu, select Meter > Inventoried. The Meters Inventoried form displays all meters that are at the inventoried stage. See Meter life cycle on page 33 for details on meter life cycle.
IF Marriage File was:
AND REX or node meter has an Install Date Yes
AND REX or node meter is registered to gatekeeper Yes
The REX meter or node meter appears in report: Meter Installed Report Registered REX Meters Report1
Imported
Yes No No
No Yes2 No Yes
Meter Installed Report Orphaned REX Meter Report Registered REX Meters Report1 Meter Inventoried Report Unknown REX Meters Report
Not Imported
No
1. Only if meter is not on a schedule for data collection. 2. When the A3 ALPHA gatekeeper notifies EA_MS that a new node has registered, EA_MS sets the installation date.
The Meters Inventoried Report is divided into a Summary tab that indicates the total number of inventoried meters (by meter type) and a Meters Inventoried tab that lists each Meter Name, Meter Type, Serial Number and LAN ID.
Figure 5-91. Meters Inventoried Report - summary
166
Figure 5-92. Meters Inventoried Report
Meter Installed Report

This report allows you to view a list of meters that are currently installed (that is, according to EA_MS, the listed meters have valid installation dates but whose removal dates are not set) in the field. You would use this report to identify meters that have been installed in the field in the recent past (that is, within that last 23 days). For REX meters this action reports the following meters: meters from marriage file import meter added through Meter > New and provided a valid installation date meter registered to a gatekeeper and is discovered by the system either via a gatekeeper call-in or a read of the gatekeeper (which will automatically set an installation date for the meter) A REX meter for which marriage file is not imported and is reported by a gatekeeper will be reported as an unknown node (see Unknown REX Meters Report on page 338). To view a report of meters that have been installed: 1. From the Reports menu, select Meter > Installed. 2. Enter the From date. Caution: Elster strongly recommends you use a recent From date and time. EA_MS does not limit the From date and time you can enter. Consequently, depending on the specified From date and time, this report could list all the meters in EA_MS.
Figure 5-93. Meters Installed form

167
The Meters Installed form displays all meters that are at the installed stage. See Meter life cycle on page 33 for details on meter life cycle.
Figure 5-94. Meters Installed Report

The table below explains the format of the Meters Installed report. Item Meter Name Type/Descriptor Serial Number LAN ID Installation Date Registration Date Last Read Date Description The Meter Name and is a hyperlink to View Meter Report. The Meter Type. The meters Serial Number. The LAN ID for the REX meter. The date and time the meter was installed or registered by a gatekeeper. For REX meters, the date and time the meter registered with an EA_Gatekeeper. The date and time the meter was last read whether using a schedule or On Request Read, Advanced Metering Functions, or Special Read for Billing.
4. Click a Meter Name to view the meter. The View Meter form displays the selected meters information.
168
Meter List Report

Using the Meter List report, you can search for and view a list of meters in the system that meet a specific set of criteria. From the Meter List report you can access a variety of other reports.
Figure 5-95. Navigating meter reports

To view the Meter List report: 1. From the Reports menu, select Meter > Listing. 2. Enter one of the parameters on which to base the search Meter Name Meter Type Serial Number Account No. Account Name Site ID Comm Media Comm Mode Installation From and To date Removal From and To date Schedule Name Data Set Name TOU Schedule (REX meters only)
Note: You can use a search pattern (% and * are wildcards) in the text box. Note: Elster does not recommend using a search pattern that consists of wildcards only. For large system installations the returned results would be too large to easily select a meter. Note: The Meter List Report includes only meters that were added using Meter > New or that were discovered by a gatekeeper.
169
Figure 5-96. Listing Meters Report form

3. Enter the Installation or Removal From and To dates and times (if applicable). 4. Click Submit to create the report. The Meter List Report displays.
Figure 5-97. Meter List Report
170
The table below describes the information displayed by the Meter List report. Item Meter Name Meter Type/Descriptor Account Number Account Name Site ID Installation Date Field Removal Date Comm Media Comm Mode Comm Number or LAN ID Serial Number Description The Meter Name (a hyperlink to View Meter Report) The Meter Type of the meter. The Account No. of the meter. The Account Name of the meter. The Site ID. The installation date and time. The Field Removal Date (if applicable) of the meter. The Comm Media of the meter. The Comm Mode of the meter. The Comm Number for the A3 ALPHA meter or the LAN ID for REX meters. The meters Serial Number.
Component Mismatch Report

The Component Mismatch Report allows you to view a report of meters whose supported components do not fully match the assigned data set. To view a list of meters with component mismatched: From the Actions menu, select Reports > Meter > Component Mismatch. A report of component mismatches displays.
Figure 5-98. Component Mismatch report

Note: EA_MS allows you to assign data sets if at least one of the components in the data set is supported by the meter.
Meters Disconnected Report

The Meters Disconnected Report allows you to view a report of REX meters whose service disconnect switch is open (that is, the meter has been disconnected from service). To view a list of disconnected meters: From the Actions menu, select Reports > Meter > Disconnected. A report listing all disconnected REX meters displays.
171
Figure 5-99. Meters Disconnected Report
172
6. Water metering
Water metering
Reports
All EA_MS users can access operational reports. The Reports menu allows you to create the following water meter reports: View Meter Report Unknown Water Nodes Report Gatekeeper Water Nodes Report Water Meter Read History Report Water Interval Threshold Report Water Leak Report
About Water Metering

EA_MS supports water meter data collection from water meters equipped with the EnergyAxis Water Module. Modules transmit meter register readings, load profile data, and local status and warnings over the same 900 MHz RF network used for electricity metering communications. From the EA_MS perspective, the water meter is similar to a REX electricity meter in that it can be added and manipulated in EA_MS in the same manner as a REX meter. EA_MS reads water meter data from the 900 MHz network via a gatekeeper. However, a water meter differs from a REX meter in that the EA_Water module transmits its meter data periodically to reduce battery usage. When the modules are active, they fully participate in the EA_LAN (although they do not act as repeaters) by evaluating the best communications path and developing a LAN communications table. The modules also receive network timing from their parent device and can be given additional data by the network. The unit, when operating, is a full twoway device and member of the EA_LAN. EA_Water modules also do not use EA_MS schedules or data components and cannot register with gatekeepers and for these reasons, a gatekeeper-only data component, Water Registers from Gatekeeper, is used to collect water meter register and load profile data from the network (see Creating a data set on page 195). On request reads of gatekeepers for this data component will read and package all available water data from the gatekeeper.
Note: To enable the collection of water meter data in the LAN, the gatekeepers in the network must be configured to store the water register and load profile data transmissions received from the modules. Contact EnergyAxis Support for assistance in configuring gatekeepers for water meter support. Note: No configuration changes are required for the repeaters relaying water meter data to the gatekeeper.
Existing EA_MS reports support electricity meters and the water meter where the current functionality is applicable to both. In addition, water meter reports allow for management and monitoring of water meters in EA_MS.
173
6. Water metering
Viewing a water meters readings

The most recently read water meter data (received from the gatekeeper) can be viewed in the Readings report. To view a water meters readings: 1. From the Reports menu, select Meter > Readings. 2. Select EAWater as Meter Type. 3. Select a reading filename.
Figure 6-1. Reading File contents - water meter
Viewing the unknown water nodes report

A water meter that is discovered by a gatekeeper (that is, installed in the field) before its marriage file has been imported is called an unknown water meter. The Unknown Water Nodes Report lists the following information for each unknown water meter: the discovering gatekeeper the most recent date and time it was considered unknown LAN ID
Note: EA_MS cannot report unknown meters for gatekeepers that have not been communicated with at least one time (for example, newly installed gatekeepers).
To view a report of unknown water meters: 1. From the Reports menu, select Water > Unknown Water Nodes. The Unknown Water Node Report form displays. 2. Enter the From and To date and time. 3. Enter any parameters specific to the search. Or Enter a wildcard string (like % or *) to view a report on all meters, serial numbers, account numbers. 4. Click Search.
174
6. Water metering
Figure 6-2. Unknown Water Nodes Report form

5. Select the desired gatekeeper. The Unknown Water Nodes Report displays.
Figure 6-3. Unknown Water Nodes Report
175
6. Water metering
The table below describes the information displayed by the Unknown Water Nodes Report. Item Gatekeeper Name Discovered At Unknown LAN ID Description The Meter Name for the A3 ALPHA gatekeeper (hyperlink to View Meter report). The date and time the unknown water node was discovered by EA_MS. The LAN ID for the unknown water node.
Viewing a gatekeepers water nodes report

The Gatekeeper Water Nodes Report displays a listing of water nodes associated with a specified gatekeeper. To view a report of a gatekeepers associated water meters: 1. From the Reports menu, select Water > Gatekeeper Water Nodes. The Gatekeeper Water Node Report form displays. 2. Enter any parameters specific to the meter search and click Search. 3. Select the desired gatekeeper.
Figure 6-4. Gatekeeper Water Nodes Report form

The Gatekeeper Water Nodes Report displays.
176
6. Water metering
Figure 6-5. Gatekeeper Water Nodes Report

The table below describes the information displayed by the Gatekeeper Water Nodes Report. Item for each A3 ALPHA gatekeeper Gatekeeper Name Last Connect Date LAN Last Optimized Last Changed # of Nodes # of Repeaters The Meter Name for the EA_Gatekeeper (hyperlink to View Meter report). The date and time the gatekeepers data readings were last read by EA_MS. The date and time the gatekeeper was last optimized (see Optimizing a gatekeepers LAN on page 388). Date and time of the last programming change. The number of meters registered to the gatekeeper. The number of registered meters functioning as repeaters (that is, relaying downstream meter data up to the gatekeeper). The number of water meter readings currently stored in the gatekeeper. The meter configuration of the gatekeeper. See Meter configuration on page 22 for details. Description
# of One-Way Nodes Gatekeeper Configuration for each water meter Meter Name Type/Descriptor
The Meter Name for the water meter (hyperlink to View Meter report). The Meter Type of the meter.
177
6. Water metering
Item LAN ID Serial Number Installation Date Last Read Date
Description The LAN ID for the water node. The meters Serial Number. The installation date and time. The date and time the meters register readings were last read.
Viewing a gatekeepers water meters reading history

The Water Meter Read History Report displays the reading dates and times for a listing of water nodes associated with a specified gatekeeper. To view a report of associated water meters: 1. From the Reports menu, select Water > Water Meter Read History. The Water Meter Communications Report form displays. 2. Enter the From and To date and time. 3. Enter any parameters specific to the meter search and click Search. A listing of all meters meeting the search criteria displays.
Figure 6-6. Water Meter Communications Report form

4. Select the desired gatekeeper. The Water Meter Read History Report displays.
178
6. Water metering
Figure 6-7. Water Meter Read History Report

The table below describes the information displayed by the Water Meter Read History Report. Item Date Range Node Name Gatekeeper Name Read Time Description The From and To dates and times for which the report was generated. The Meter Name for the water meter. The Meter Name for the A3 ALPHA gatekeeper (hyperlink to View Meter report). The date and time water meter data was received by the gatekeeper.
Viewing the Water Interval Threshold report

The Water Interval Threshold Report displays all interval data where usage is found to exceed an hourly usage threshold. The system-wide usage threshold is defined in the windows registry (see the EA_MS Installation and Administration Guide for details). As interval data is read from the gatekeeper, EA_MS will flag with an event any reported interval that exceeds the threshold for later presentation in the Water Interval Threshold Report. To view a report of excessive hourly usage: 1. From the Reports menu, select Water > Water Interval Threshold. The Water Interval Threshold Report form displays.
179
6. Water metering
Figure 6-8. Water Interval Threshold report form

2. Enter the From and To date and time. 3. Enter any parameters specific to the search. Or Enter a wildcard string (like % or *) to view a report on all meters, serial numbers, account numbers. 4. Click Search. 5. Select the desired water node. The Water Interval Threshold Report displays.
180
6. Water metering
Figure 6-9. Water Interval Threshold report

The table below describes the information displayed by the Water Interval Threshold Report. Item Node Name Serial Number Account ID Magnitude Threshold Time Description The Meter Name for the water meter (hyperlink to View Meter report). Serial number of the water meter. Account ID of the water meter. Magnitude of the interval exceeding the hourly usage threshold. Hourly usage threshold. The date and time of the interval exceeding the hourly usage threshold.
Viewing the Water Leak report

Each EA_Water module can be programmed to monitor the meter for potential leaks. Individual account settings are available to define the number of zero-consumption intervals over a time period ("leak window") monitored at the meter: if consumption does not fall below zero (per the meter's registration) for the specified number of intervals ("zero intervals"), then the module sets the leak flag. The water leak report uses the modules that
181
6. Water metering
have their leak flag set. Not only are the units with suspected leaks reported, the Water Leak Report also the Water Leak Report presents the minimum non-zero usage recorded in the available interval data for a water node as the possible magnitude of a suspected leak condition, as indicated by a leak status reported with the water register read. The time stamp of the reported status is set to that of the corresponding minimum usage interval. The report is event-based and depends on Leak Suspected events generated in response to Leak Suspected statuses reported by EA_MS. To view a report of suspected leaks: 1. From the Reports menu, select Water > Water Leak. The Water Leak Report form displays.
Figure 6-10. Suspected Water Leak report form

2. Enter the From and To date and time. 3. Enter any parameters specific to the search. Or Enter a wildcard string (like % or *) to view a report on all meters, serial numbers, account numbers. 4. Click Search. 5. Select the desired water node. The Water Leak Report displays.
182
6. Water metering
Figure 6-11. Suspected Water Leak report

The table below describes the information displayed by the Water Leak Report. Item Node Name Serial Number Account Id Magnitude Time Description The Meter Name for the water meter (hyperlink to View Meter report). Serial number of the water meter. Account Id of the water meter. Magnitude of the suspected leak. The date and time of the suspected leak.
183
7. Gas metering
Gas metering
Reports
All EA_MS users can access operational reports. The Reports menu allows you to create the following gas meter reports: View Meter Report Unknown Gas Nodes Gatekeeper Gas Nodes Gas Meter Read History
About gas metering

EA_MS supports gas meter data collection from gas meters equipped with the EA_Gas module. Modules transmit meter register readings, load profile data, and local status and warnings over the same 900 MHz RF network used for electricity metering communications. From the EA_MS perspective, the gas meter is similar to a REX electricity meter in that it can be added and manipulated in EA_MS in the same manner as a REX meter. EA_MS reads gas meter data from the 900 MHz network via a gatekeeper. The EA_Gas module develops a list of preferred EA_LAN repeaters and communicates only with the best communication repeater. The main difference between REX meters and EA_Gas modules are that EA_Gas modules do not register with a gatekeeper and they are not active on the EA_LAN at all times. When the modules are active, they fully participate in the EA_LAN (although they do not act as repeaters) by evaluating the best communications path and developing a LAN communications table. The modules also receive network timing from their parent device and can be given additional data by the network. The unit, when operating, is a full twoway device and member of the EA_LAN. EA_Gas modules also do not use EA_MS schedules or data components and cannot register with gatekeepers and for these reasons, a gatekeeper-only data component, Gas Registers from Gatekeeper, is used to collect water meter register and load profile data from the network (see Creating a data set on page 195). On request reads of gatekeepers for this data component will read and package all available gas data from the gatekeeper.
Note: To enable the collection of gas meter data in the LAN, the gatekeepers in the network must be configured to store the one-way register and load profile data transmissions received from the gas modules. Contact EnergyAxisSupport for assistance in configuring gatekeepers for gas meter support. Note: No configuration changes are required for the repeaters relaying gas meter data to the gatekeeper.
Existing EA_MS reports support electricity meters and the gas meter where the current functionality is applicable to both. In addition, gas meter reports allow for management and monitoring of gas meters in EA_MS.
184
7. Gas metering
Viewing a gas meters readings

The most recently read gas meter data (from the gatekeeper) can be viewed in the Readings report. To view a gas meters readings: 1. From the Reports menu, select Meter > Readings 2. Select EAGas as Meter Type 3. Select a reading filename.
Figure 7-1. Reading File contents - gas meter

Selecting the Reading Details tab shows the Data Report for the selected meter.
185
7. Gas metering
Selecting to view Load Profile in HTML, opens the Meter Readings Listing Report.
Clicking Meter Statuses opens the Meter Statuses Report.
186
7. Gas metering
Viewing the unknown gas nodes report

A gas meter that is discovered by a gatekeeper (that is, installed in the field) before its marriage file has been imported is called an unknown gas meter. The Unknown Gas Nodes Report lists the following information for each unknown gas meter: the discovering gatekeeper the most recent date and time it was considered unknown LAN ID
To view a report of unknown gas meters: 1. From the Reports menu, select Gas > Unknown Gas Nodes. The Unknown Gas Node Report form displays. 2. Enter the From and To date and time. 3. Enter any parameters specific to the search. Or Enter a wildcard string (like % or *) to view a report on all meters, serial numbers, account numbers. 4. To select a specific gatekeeper, click Search and select the desired gatekeeper. Or Click Submit to view a report for all gatekeepers.
187
7. Gas metering
Figure 7-2. Unknown Gas Nodes Report form

The Unknown Gas Nodes Report displays.
Figure 7-3. Unknown Gas Nodes Report

The table below describes the information displayed by the Unknown Gas Nodes Report. Item Gatekeeper Name Description The Meter Name for the EA_Gatekeeper (hyperlink to View Meter report).
188
7. Gas metering
Item Discovered At Unknown LAN ID
Description The date and time the unknown gas node was discovered by EA_MS. The LAN ID for the unknown gas node.
Viewing a gatekeepers gas nodes report

The Gatekeeper Gas Nodes Report displays a listing of gas nodes associated with a specified gatekeeper. To view a report of a gatekeepers associated gas meters: 1. From the Reports menu, select Gas > Gatekeeper Gas Nodes. The Gatekeeper Gas Node Report form displays. 2. Enter any parameters specific to the meter search and click Search. 3. Select the desired gatekeeper.
Figure 7-4. Gatekeeper Gas Nodes Report form

The Gatekeeper Gas Nodes Report displays.
189
7. Gas metering
Figure 7-5. Gatekeeper Gas Nodes Report

The table below describes the information displayed by the Gatekeeper Gas Nodes Report. Item for each A3 ALPHA gatekeeper Gatekeeper Name Last Connect Date LAN Last Optimized Last Changed # of Nodes # of Repeaters The number of meters registered to the gatekeeper. The number of registered meters functioning as repeaters (that is, relaying downstream meter data up to the gatekeeper). The number of water and gas meter readings currently stored in the gatekeeper. The meter configuration of the gatekeeper. See Meter configuration on page 22 for details. The Meter Name for the EA_Gatekeeper (hyperlink to View Meter report). The date and time the gatekeepers data readings were last read by EA_MS. The date and time the gatekeeper was last optimized (see Optimizing a gatekeepers LAN on page 388). Description
# of One-Way Nodes Gatekeeper Configuration for each gas meter Meter Name Type/Descriptor LAN ID Serial Number
The Meter Name for the has meter (hyperlink to View Meter report). The Meter Type of the meter. The LAN ID for the gas node. The meters Serial Number.
190
7. Gas metering
Item Installation Date Last Read Date
Description The installation date and time. The date and time the meters register readings were last read.
Viewing a gatekeepers gas meters reading history

The Gas Meter Read History Report displays the reading dates and times for a listing of gas nodes associated with a specified gatekeeper. To view a report of associated gas meters: 1. From the Reports menu, select Gas > Gas Meter Read History. The Gas Meter Communications Report form displays. 2. Enter the From and To date and time. 3. Enter any parameters specific to the meter search and click Search. A listing of all meters meeting the search criteria displays.
Figure 7-6. Gas Meter Communications Report form

4. Select the desired gatekeeper. The Water Gas Read History Report displays.
191
7. Gas metering
Figure 7-7. Gas Meter Read History Report

The table below describes the information displayed by the Gas Meter Read History Report. Item Date Range Node Name Gatekeeper Name Read Time Description The From and To dates and times for which the report was generated. The Meter Name for the water meter. The Meter Name for the EA_Gatekeeper (hyperlink to View Meter report). The date and time water meter data was received by the gatekeeper.
192
8. Data Set
Data Set
Data sets are used to specify a group of data components that are to be collected from the meter on a scheduled basis. These could be billing determinants or data for other purposes such as load survey, monitoring system performance, etc.
Actions and reports

TheEA_MS menu allows you to access the following data set actions and report: Actions New Delete Exchange Reports View All
Retrieving a Data Set

For the following activities you will need to retrieve a data set from the EA_MS database: Exchange Delete To retrieve a data set: 1. From the Actions menu, select Data Set and the activity. The Retrieve a Data Set form displays.
Figure 8-1. Retrieving a data set

2. Enter the Data Set Name Or Enter a search pattern (% and * are wildcards) in the text box.
Note: The search criteria is not case sensitive.
193
8. Data Set
Note: You can use % or * as a wildcard>. You can use beginning and trailing wild cards to perform starts-with and contains searches. For example, entering a Data Set Name of %LP% result in a list of all data sets whose names contain LP. Note: Elster does not recommend using a search pattern that consists of wildcards only. For large system installations the returned results would be too large to easily select a data set.
3. Click Search. The Search Results displays a list of specified data sets.
Figure 8-2. Retrieving a data set

4. Click to select the desired data set from the listing. The activitys form displays with the relevant data set information.
Viewing a list of all data sets

To view a listing of all data sets: From the Actions menu, select Data Set > View All. The Data Sets report displays a listing of all data sets in alphabetical order followed by their components.
194
8. Data Set
Figure 8-3. View All data sets
Changing data set assignments

Note: This action is available for evaluation only. Use of this operation on production data / installation of the system is not recommended at this point in time.
This action allows you to switch one or more meters from one data set to another. To exchange data sets in one or more meters: 1. From the Actions menu, select Data Set > Exchange. 2. Click Search to select the Current Data Set (that meters should be switched from). 3. Click Search to select the Current Data Set (that meters should be switched to). 4. Select one of the following: a. Show all Meter-Schedule Assignments - allows user to switch all instances where this data set is in use across multiple schedules. b. Show only Meter-Billing Schedule Assignments - allows user to switch all meters that are on this data set for billing c. Show only Meter-specified Schedule Assignments and select a Schedule for Filtering - allows user to switch all meters that are on this data set on a specified schedule 5. Select all meters that will be changed to the new data set.
195
8. Data Set
Figure 8-4. Exchange Data Set form

6. Click Submit to initiate the exchange. All the meters selected will be switched to the new data set but will be kept on the same schedules.
Note: Exchanging data sets could result in synchronization at the next execution of a synchronization schedule.
Creating a data set

You can define data sets with any combination of data components regardless of intended meter type. When a data set is defined, EA_MS does not know the meter types the data set may be assocated with, therefore, it is your responsibility to determine the proper composition of a new data set. To save processing time (for example, when assigning a large numbers of meters to a schedule and data set), EA_MS does not perform full validation of meter support of individual data components when a meter is assigned to a schedule and data set. It only checks to make sure that there is at least one component in the data set that can be supported by the meter type. Consequently, if you request a data component that is not supported by the meter type, EA_MS may return no data for that component for that meter type. Users can review the list of meters which have unsupported components using Reports > Meter > Component Mismatch Report. To add a new data set: 1. From the Actions menu, select Data Set > New. The Define a Data Set form displays a blank form. 2. Enter the Data Set Name.
Note: Component names are reserved by the system therefore you cannot name a data set a component name (for example, you cannot create a data set named Registers or Load Profile).
3. Enter a Description. 4. Select the Data Components to be collected.
196
8. Data Set
The table below describes the mapping of user selectable data components to low level components within the system.
Table 8-1. Data components

Category Energy and Demand Data Component Registers Low-level Data Component Consumption (current and previous period and seasons) Max demand (current and previous period and seasons) Demand Reset count Meter Type A3 ALPHA meter, Gatekeeper and REX meter See Registers on page 496. See Warning below for REX meters and A3 ALPHA meters. For REX meters, MAS calls the Gatekeeper to which the REX meter is registered and then the Gatekeeper communicates over the LAN with the specified REX meter.
Note: Although all statuses in the current table are read, by default only abnormal statuses are reported in the file and on the user interface.
Cumulative demand (current and previous period and seasons) Instrumentation Values A3 ALPHA Meter Statuses and A3 ALPHA meter with EA_NIC Statuses REX/REX2 Meter Statuses A3 ALPHA meter with EA_NIC Statuses Voltage Interval Data Load Profile All LP channels from endpoint All unread LP channels from endpoint A3 ALPHA meter and Gatekeeper
REX meter and A3 ALPHA meter
REX meter; A3 ALPHA meter and Gatekeeper The system also calculates and displays a summary view of LP data for each channel. By default only summary information is displayed; however detailed interval data can be viewed from the user interface if specified. See Load Profile on page 497.
Note: Elster does not recommend using the Load Profile data component for REX and A3 ALPHA meters.
Energy and Demand Demand Reset Perform demand reset A3 ALPHA meter, Gatekeeper and REX meter See Demand Reset on page 498. A3 ALPHA meter and Gatekeeper This component only reads new events since the last reading of the event or exception log. See A3 ALPHA Meter Events. See Events and Exceptions on page 499. Gatekeeper A3 ALPHA meter and Gatekeeper See Reset A3 Events on page 500.
Events and Statuses
Events and Exceptions
New PQ Events All outage events Meter alarms Tamper alarms Exceptions from ILC (LAN controller)
Events and Statuses
Reset A3 Events
Reset Event Log
197
8. Data Set

Category Events and Statuses Data Component LAN Performance Low-level Data Component ILC read comm statistics Gatekeeper network information Gatekeeper Gatekeeper Reads selected Gatekeepers performance data including statistics, node registration information, time slice (for Gatekeeper), etc. By default, only the statistics are displayed on the reading report. See LAN Performance on page 501. Gatekeeper See Reset Communication statistics on page 502. Gatekeeper, A3 ALPHA meter, A3 ALPHA meter with EA_NIC and REX meter Reads associated REX meters data registers including current, previous period, previous season and configuration change snapshots, REX/REX2 Meter Statuses, voltages, outage count for all registered nodes to specified Gatekeeper. If a REX meter is selected, this component returns data for the specified REX meter from the Gatekeeper. If a Gatekeeper is selected, EA_MS returns the above data for every REX meter registered to the gatekeeper. See Registers from Gatekeeper on page 502. Gatekeeper See Read and Clear Water Data from Gatekeeper on page 503. Gatekeeper See Read and Clear Gas Data from Gatekeeper on page 503. REX and REX2 meters and A3 ALPHA meter See Load Profile from Gatekeeper on page 504. REX2 meters Meter Type
Events and Statuses
Reset Communication statistics Registers from Gatekeeper
Reset communication statistics
Energy and Demand
Consumption (current and previous period and seasons) Max demand (current and previous period and seasons) Node Statuses (Gatekeeper/ILC and node)
Water Data
Read Water Data from Gatekeeper Read Gas Data from Gatekeeper Load Profile from Gatekeeper Read home area network status
Usage Statuses Usage Statuses All LP channels All new LP channels Read today's home area network events from the meter. Read yesterdays home area network events from the meter.
Gas Data
Interval Data
HAN
198
8. Data Set

Category Events and Statuses Data Component Clear meter statuses Low-level Data Component Clear (reset) meter statuses. The following statuse are cleared: No Voltage Detected with Disconnect Closed Demand Threshold Exceeded Load Side Voltage Present (Latched value) Load Side Voltage Present Phase A Low Potential Phase C Low Potential Voltage above maximum threshold Voltage below minimum theshold Demand limiting operations exceeded Tilt warning Reverse energy warning Invalid access warning Configuration table write warning Per-phase voltage, in volts. Enables broadcast of usage data to 900MHz EA network in-home displays. Disables broadcast of usage data to 900MHz EA network in-home displays. Reads new entries in the audit log of the ILC board in a Gatekeeper. Read the last 24 hours worth of LP data (all channels) from the meter. REX2 meters Meter Type
PQM HAN
Voltage Enable EnergyAxis Broadcast Disable EnergyAxis Broadcast ILC audit log
REX, REX2, A3 ALPHA Node REX version 4.1, REX2 meters
HAN
REX version 4.1, REX2 meters
Gatekeeper REX, REX2, A3 ALPHA Node (reads the data from the endpoint meter directly over the EA_LAN using the Gatekeeper). See Load Profile (last 24 hrs) on page 506. See Clear A3 Statuses on page 505. See Clear Sag Statuses on page 505.
Interval Data
Load Profile (last 24 hrs)
Clear A3 Statuses PQM PQM PQM Interval Data Clear Sag Statuses Sag Log Sag Log Counter Load Profile (last One Week) Reads new sag log entries from the meter. Reads the sag log counter values from the meter. Reads the last 7 days' worth of LP data (all channels) from the meter including missing LP data.
A3 ALPHA, Gatekeeper See Sag Log on page 507 WIC connected A3 ALPHA and Gatekeeper See Sag Log Counter on page 508. REX, REX2, A3 ALPHA Node (reads the data from the endpoint meter directly over the EA_LAN using the Gatekeeper). See Load Profile (last one week) on page 508. REX2 version 3.0 and higher (reads the endpoint meter directly using the EA_LAN)
Events and Statuses
Outage and Restoration Events from Endpoint
Reads all available outage and restoration events from a REX2 meter configured (at the Elster factory) to perform event only profiling.
199
8. Data Set

Category Events and Statuses Data Component Outage and Restoration Events from Gatekeeper Low-level Data Component Reads new outage and restoration events from a REX2 meter configured (at the Elster factory) to perform event only profiling. Only new data since the last read is returned. Clears (resets) events and statuses in the ILC board on a Gatekeeper. Reads new EA_LAN endpoint events from Gatekeeper. Reads the present instrumentation values from the meter. Reads the new PQM Log entries. Reads PQM Counter This is a short session with the A3 ALPHA meter or gatekeeper that verifies the following: WAN link is operational and the meter rseponds to EA_MS requests (WAN health) meter serial number matches what EA_MS expects (checks provisioning errors) EA_MS could authenticate with the meter (checks provisioning errors) EA_MS could encrypt/decrypt communi-cations (is supported and enabled, checks provisioning and configuration errors) comm. address (IP addr/port or phone number) is valid and the device ID (for multidrop installations) is correct the meter configuration has been updated by Metercat and rereads configuration tables meter status and reports errors Reads any new events from the event log Checks and synchronizes the meter clock if necessary Meter Type REX2 version 3.0 and higher
Events and Statuses
Reset ILC Events
Gatekeeper
PQM
Present Values
A3 ALPHA, Gatekeeper See Present Values on page 510.
Diagnostic
Health Check A3
A3 ALPHA, Gatekeeper See Health Check A3 on page 511.
Diagnostic
Health Check ILC
Performs a comm session with the Gatekeeper ILC (not the meter) to make sure of See Health Check ILC on page 511. the following: verifies that the ILC firmware version is compatible with EA_MS verifies that EA_MS can authenticate with the ILC checks for health errors in the ILC
200
8. Data Set

Category Diagnostic Data Component Health Check WIC Low-level Data Component Meter Type
A3 ALPHA or Gatekeeper with a WIC board Performs a comm session with the WIC to make sure of the following: See Health Check WIC on page 512. EA_MS can communicate with the WIC board encryption and authentication (if enabled) are functioning properly there are no health problems reported by the WIC board Performs an ICMP ping to the device's comm address. In many cases this only pings the WAN modem. The component succeeds if the ping was successful and fails if it was unsuccessful. Performs an ICMP traceroute to the devices comm address. The component succeeds if the route was completed. An event is generated if the route has changed from the last time it was read. Unregister EA_LAN Device Clear Node Interval Data from Gatekeeper EA_LAN Message to Unregister Node Start EA_LAN Node Scan at Gatekeeper Clear and Reload Cached A3 Configuration Data Clear and Reload Cached Gatekeeper Module Configuration Data Reset Gatekeeper Interval Data Pointer Update Gatekeeper Interval Data Pointer to Now Clear A3 Meter Statuses Clear Sag Log Statuses Clear PQM Statuses Clear Gatekeeper Module Statuses A3 ALPHA with TCP/IP connection, Gatekeeper with TCP/IP connection See ICMP Ping on page 509.
Diagnostic
ICMP Ping
Diagnostic
ICMP Traceroute
A3 ALPHA, Gatekeeper See ICMP Traceroute on page 513.
Maintenance Maintenance Maintenance Maintenance Maintenance Maintenance
Maintenance Maintenance Maintenance Maintenance Maintenance Maintenance
Note: Certain components that provide information (such as node statuses, LAN performance) about the state of the network will be read in every communication session even though they may not be reported upstream. Note: For electricity meters in the EnergyAxis network, Elster recommends that each node meter be scheduled to read either Registers from Gatekeeper or Load Profile from Gatekeeper. Scheduling REX meters, A3 ALPHA meters with EA_NIC, and gatekeepers to read Registers from Gatekeeper and Load Profile from Gatekeeper will cause data to be read and exported to AMRDEF twice.
201
8. Data Set
Warning:
Normal data collection for REX meters should use the REX Registers from Gatekeepers component which will return the latest data available for the REX meter in the gatekeeper. In most cases, this read will be within four hours of the execution time of the schedule. Elster recommends that you do not setup REX meters on data sets with
Registers as a component. The Registers component requires

communication with the individual meter through its gatekeeper to get the data. This is likely to result in long communication times. If used for REX meters, the Registers component should be used only for on request reads. Similarly, normal load profile data collection should use Load Profile from Gatekeeper for REX meters and A3 ALPHA nodes. Attempting to reading Load Profile component for REX and A3 ALPHA nodes will result in an error message. The Load Profile data component can be used for on request reading of LP data from gatekeepers and A3 ALPHA meters.
203
8. Data Set
Deleting a data set

To delete a data set that has no associated meters (see Changing a meters information on page 79 for details on changing a meters data components): 1. From the Actions menu, select Data Set > Delete. 2. Search for the data set. 3. Select the data set. The Remove Data Set form displays the data set information.
Figure 8-6. Delete Data set

Note: EA_MS will not allow you delete a data set that is currently in use on schedules and meters because the same data set may be in use on meters in multiple schedules and the potential impact of such an operation could be significant.
4. Click Submit to delete the selected data set. The Remove Data Set form displays the action results.
204
9. Schedule
Schedule
Actions and reports

The Actions menu allows you access to the following schedule actions: Actions Exchange New Delete Resubmit Modify Reports View All Explorer
The Reports menu allows you create to the following schedule reports: View All Explorer Additional reports available from the Schedule > View All report: View Schedule Information Report Meter List Report Performance Report Voltage Reading Performance reports Schedule Execution Summary Report
Retrieving a Schedule
For the following activities you will need to retrieve a schedule from the EA_MS database: Resubmit Modify To retrieve a schedule: 1. From the Actions menu, select Schedule and the activity. The Retrieve a Schedule form displays. Delete
205
9. Schedule
Figure 9-1. Retrieving a schedule

2. Enter the Schedule Name. Or Enter a search pattern (% and * are wildcards) in the text box.
Note: The search criteria is not case sensitive. Note: You can use % or * as a wildcard. You can use beginning and trailing wild cards to perform starts-with and contains searches. For example, entering a Schedule Name of %bill% result in a list of all meters whose names contain bill. Note: Elster does not recommend using a search pattern that consists of wildcards only. For large system installations the returned results would be too large to easily select a schedule. Note: You should enter the name in the text field or click on a search-returned name. You should not do both since this has the effect of doing two submits. Once you do one or the other, a progress bar displays at the top of the form saying Please Wait while the page is being loaded.
3. Click Search. The Search Results display.
Figure 9-2. Retrieving a schedule
206
9. Schedule
4. Click to select the desired schedule from the listing. The activitys form displays with the relevant schedule information.
Viewing a list of all schedules

The View All report allows you to view a listing of active schedules (schedules with meters assigned) that have been set up in the system. This also includes schedules that are inactive (that is, schedules without meters assigned) or terminated (that is, deleted schedules) but for which the system has information about past executions, performance etc. In addition, it also provides access to additional reports: Meter List Report View Schedule Information Report Schedule Execution Summary Report Performance Report
View Schedules report Schedule List, Inactive Schedules, Terminated Schedules, Schedule Dashboard, Voltage Schedules
Schedule List
# Meters
Voltage Schedules Schedule List
Schedule Name
Performance Performance by - gatekeeper - schedule - by meter - node level
View Schedule Information report
Completed
View Schedule Information
Performance report
Schedule Execution Summary report
Meter Listing report
View Schedule Runs
Meters Read Voltage
Name View Meter report View Schedule Information report View Data Set Information report
Meters Not Read
Figure 9-3. Navigating schedule reports
207
9. Schedule
Note: All date and time information (such as execution times) that is displayed in schedule reports is in the time zone specified during the creation of the schedule (see Schedule > New).
To view a listing of all schedules: From the Actions menu, select Schedule > View All. Or From the Reports menu, select Schedule > View All. The View Schedules Report displays a listing of all schedules.
Note: The percent success for schedules that are currently running serves as a progress indicator. This percentage is updated as meters are read by the system.
Figure 9-4. View Schedules Report - schedule list
208
9. Schedule
Figure 9-5. View Schedules Report - inactive schedules
Figure 9-6. View Schedules Report - terminated schedules

The Terminated Schedules report lists any terminated schedules and their termination date (if any). See Deleting a schedule on page 252 for details on terminating a schedule.
209
9. Schedule
Figure 9-7. View Schedules Report - voltage schedules

The Voltage Schedule report lists voltage schedules currently existing in EA_MS. The table below explains the format of the Schedule List reports. Item Name Description Billing # Meters Description The Schedule Name (a hyperlink to the View Schedule Information Report). A brief Description of the schedule (set by using Schedule > New). A check mark indicates if the schedule is for billing purposes. The number of meters currently assigned to the schedule.
Note: If a meter is marked as removed without removing all its associations (that is, it is still on all collection schedules, TOU schedules, etc.) then it will be included in this count.
Last Execution Next Execution Performance The last date and time the meters assigned to the schedule were read. The next date and time the meters assigned to the schedule are to be read. Indicates the percentage success rate for the last schedule execution including any resubmits (hyperlink to the specified schedules Performance Report and Display Meter Readings report. Allows you to quickly view report of the schedules Execution Summary. Opens the Voltage Reading Performance form for creating Performance reports and the voltages of meters read.
E report button R report button
Schedule Dashboard
Selecting the Schedule Dashboard displays graphical representation of schedule performances.
210
9. Schedule
Figure 9-8. View Schedules Report - schedule dashboard
Item
Description Maximizes the selected pane.
Reduces the selected pane to fit in the dashboard.
Displays a pie chart of the selected information.
Displays a bar chart of the selected information.
Displays a table of the selected information.
View Schedule Information Report

To view a schedules information: Click on the Schedule Name.
211
9. Schedule
Figure 9-9. View Schedule Information Report - periodic schedule
Figure 9-10. View Schedule Information Report - non-periodic schedule
212
9. Schedule
The table below describes the information displayed by the View Schedule Information Report. Item Report Generated On View Schedule Runs Schedule Information Description The server date and time the report was created. Is a hyperlink to Schedule Execution Summary Report. The Schedule Name, Description, Time Zone, File Location, Read Window, % Meters Read at the last execution, Last Execution date/time, # of Meters, Schedule Purpose, and Termination Date. See Creating a schedule on page 242 for details. Clicking on this list will display the Meter List Report that contains the meters currently on this schedule. Note that if a meter is marked as removed without removing all its associations (i.e. it is still on all collection schedules, TOU schedules etc.) then it will be included in this list. The Schedule Dates (periodicity or list of execution dates both past and present).
Meter Listing Report (Current)
Schedule Dates
Meter List Report

The Meter List Report displays the list of meters assigned to specific schedule.
Figure 9-11. Meter List Report
213
9. Schedule
The table below describes the information displayed on the Meter List Report. Item Meters Description The assigned meters Meter Name (hyperlink to View Meter Report), Meter Type, Schedule Name (hyperlink to View Schedule Information Report), Data Set Name (the components being collected for this meter on this schedule) (hyperlink to View All), Account No., Account Name, Site ID, Installation date, Field removal date, Comm Media, Comm Mode, Comm Number, and Serial Number.
Performance Report
The Performance report provides summary data of all executions (initial and resubmitted) for a particular run of a schedule and allows a user to selectively view a listing of Meters Read, Meters Not Read, Errors, Tamper and Stale reads. The report also allows users to search for specific meters (using dynamic search) and their meter data within each execution (rather than display a list of meters read, not read etc.). This allows users to easily find and view a particular meter or group of meters. The Performance Report displays the performance information for the selected schedule.
Figure 9-12. Performance Report

The table below describes the information displayed by the schedule Performance report. Item Report Generated On Description The date and time the report was created.
214
9. Schedule
Item View Schedule Information
Description A hyperlink to View Schedule Information Report. It displays the schedule parameters (such as number of meters) as of the date of execution of the schedule.
Note: The Meter Listing is always current view (that is, it shows the number of meters currently on the schedule). While EA_MS does keep history of executions, EA_MS does not keep a historical view of what specific meters were on a schedule at a particular time in the past.
[Execution Summary] The Execution Type (whether initial, resubmit or overall), last schedule start and stop dates and times, the Number of Active Meters, Expected Reads, Number of Meters Read, Number of Meters Not Read, Actual Reads, Errors/Tampers, and % Success).
Details Select a filter from the drop list to view a listing of meters: Meters Read (total number read) Meters Not Read (total number not read) Stale Reads (total stale readings) Tamper (total number of tamper events) Error (total number of errors) Meters Read The meters read by the schedule with Meter Name, Serial Number, Account No., Account Name, Site ID, Site Location and View Data. Meter Name is a hyperlink to View Meter Report. To see View Data links, select Meters Read for the appropriate execution type (for example, Initial). View Data is a hyperlink to the Display Meter Readings report. The meters not read by the schedule with Meter Name, Serial Number, Account No., Account Name, Site ID, Site Location and Communication (Comm Mode), Error. Meter Name is a hyperlink to View Meter Report.
Meters Not Read list
Note: REX meters and A3 ALPHA nodes will be included in this list only if they are individually scheduled (as against schedule the gatekeeper). In addition, for REX meters this list will also include meters for which data is older than a pre-configured threshold.
Stale Reads The meters that do not have data within the freshness threshold but do have data read with Meter Name, Serial Number, Account No., Account Name, Site ID, Site Location and View Data. Meter Name is a hyperlink to View Meter Report. View Data is a hyperlink to the Display Meter Readings report. The meters that appear to have experienced a tamper event with Meter Name, Serial Number, Account No., Account Name, Site ID, Site Location and View Data. Meter Name is a hyperlink to View Meter Report. View Data is a hyperlink to the Display Meter Readings report.
Tamper
215
9. Schedule
Item Error
Description The meters that appear to have experienced an error event with Meter Name, Serial Number, Account No., Account Name, Site ID, Site Location and View Data. Meter Name is a hyperlink to View Meter Report. View Data is a hyperlink to the Display Meter Readings report.
Figure 9-13. Performance report - meters read
216
9. Schedule
Figure 9-14. Performance report - meters read (resubmit)
217
9. Schedule
Figure 9-15. Performance report - meters not read
218
9. Schedule
Figure 9-16. Performance report - stale reads
219
9. Schedule
Figure 9-17. Performance report - Tamper
220
9. Schedule
Figure 9-18. Performance report - errors
221
9. Schedule
Figure 9-19. Performance report - view data

View Data link opens the Meter Readings report for the selected meter. See Meter Readings Report on page 138 for details.
Note: If the selected instance of the schedule was a resubmitted action, the Execution Summary section would include statistics for both the initial execution and for the resubmitted execution.
Voltage Reading Performance reports

You can view voltage readings by the following: Voltage Reading Performance by gatekeeper Voltage Reading Performance by schedule run Voltage Reading Performance by meter Voltage Reading Performance by node level
Voltage Reading Performance by gatekeeper

1. When you click on the R report button on the Voltage Schedules listing report, the Voltage Reading Performance Report form - Data Elements form displays.
222
9. Schedule
Figure 9-20. Voltage Reading Performance input form

2. Select the From and To dates and times. 3. From the Schedule drop list select the voltage schedule. 4. From the Report Type drop list select to view the data by one of the following: gatekeeper schedule run meter node level 5. Select the Threshold. 6. Click Submit. The report displays in the right pane.
223
9. Schedule
Figure 9-21. Voltage Reading Performance - by gatekeeper

7. In the report pane, select a meter Name. The data for the select meter displays the Meters Read and Meters Not Read tables for the selected meter.
224
9. Schedule
Figure 9-22. Voltage Reading Performance - by schedule run

Selecting a Schedule Run Date displays the Meters Read section where you can view the voltages measured by each meter.
Figure 9-23. Voltage Reading Performance - meters read
225
9. Schedule
Select a Schedule Run with a performance of zero displays Meters Not Read.
Figure 9-24. Voltage Reading Performance - meters not read

Clicking the Chart button displays a bar chart for the selected meters performance.
226
9. Schedule
Figure 9-25. Voltage Reading Performance - bar chart

Clicking the Export to Excel button allows you to open or save the table data as an Excel file.
Figure 9-26. Voltage Reading Performance - Excel file

Clicking the Column Selection button displays a dialog that allows to select which columns of data to display in the table.
227
9. Schedule
Figure 9-27. Voltage Reading Performance - column selection

Clicking the Full Screen button expands the selected table to fit the screen.
Figure 9-28. Voltage Reading Performance - expanded table

Click the Restore button to collapse the full screen table.
Voltage Reading Performance by schedule run

1. When you click on the R report button on the Voltage Schedules listing report, the Voltage Reading Performance - Data Elements form displays. 2. Select the From and To dates and times. 3. From the Schedule drop list select the voltage schedule. 4. From the Report Type drop list select to view the data by Schedule run. 5. Select the Threshold. 6. Click Submit.
228
9. Schedule
The report displays in the right pane.
Figure 9-29. Voltage Reading Performance - schedule run
Item Run Date Performance
Description Indicates the date and time the schedule started. Indicates the percentage of meters or gatekeepers on the schedule that successfully completed (includes resubmits). [Schedule] Run Duration specifies when schedules stop running (this has nothing to do with tolerance). Run Duration applies to hourly and minute frequency period schedules only. Default value for this field is zero (indicates the schedule never stops running). Indicates the Meter Name.
Run Duration
Name Average Read Duration Time Stamp Voltage [ A B C] Node Level
Indicates the voltage measured on the specified phase: A, B or C. Indicates the number of communication hops between the meter and its registered gatekeeper.
229
9. Schedule
Voltage Reading Performance by meter

1. When you click on the R report button on the Voltage Schedules listing report, the Voltage Reading Performance - Data Elements form displays. 2. Select the From and To dates and times. 3. From the Schedule drop list select the meter. 4. From the Report Type drop list select to view the data by Meter. 5. Select the Threshold. 6. Click Submit. The report displays in the right pane.
Figure 9-30. Voltage Reading Performance - by meter

See Appendix D, Voltage reading statuses for details on meter reading statuses.
Voltage Reading Performance by node level

1. When you click on the R report button on the Voltage Schedules listing report, the Voltage Reading Performance - Data Elements form displays. 2. Select the From and To dates and times. 3. From the Schedule drop list select the meter. 4. From the Report Type drop list select to view the data by Node level. 5. Click Submit. The report displays in the right pane showing the node level performance for the selected schedule.
230
9. Schedule
Figure 9-31. Voltage Reading Performance - by node level
Schedule Execution Summary Report

This report displays a summary of the data for a particular schedules specific execution. Information included on the report is meter readings and a listing of meters not read on specified run date. See Viewing a list of all schedules on page 206 for details on accessing this report.
231
9. Schedule
Figure 9-32. Schedule Execution Summary report

The table below describes the information displayed by the Schedule Execution Summary report. Item Report Generated On Schedule Information Description The date and time the report was created. The Schedule Name, Start Date, Description, File Creation Date, Filename, if the run was a Resubmit, Number of Meters, A hyperlink to the View Schedule Information Report. A hyperlink to the Performance Report. The Meter Name (is a hyperlink to Viewing a meters information), Serial Number, Account No., Account Name, Site ID, Site Location.
View Schedule Information View Schedule Performance Meter Readings
232
9. Schedule
Item Meters Not Read
Description Lists the meters that were not read in this schedule - Meter Name, Serial Number, Account No., Account Name, Site ID, Site Location, Communication, and Error (indicates the problem encountered with the reading).
Note: REX meters and A3 ALPHA nodes will be included in this list only if they are individually scheduled (as against schedule the gatekeeper). In addition, for REX meters this list will also include meters for which data is older than a pre-configured threshold. Note: Because water meters cannot be scheduled individually, you can view their data by selecting the corresponding gatekeeper.
Using the Schedule Explorer

The Schedule Explorer allows you to dynamically view a schedules information, executions, and performance information. To use the explorer: 1. From the Actions menu, select Schedule > Explorer. Or From the Reports menu, select Schedule > Explorer. The Schedule Explorer displays. 2. Click the Schedule Name drop list to select the appropriate schedule.
Note: Schedule names are color coded: blue for active, plum for inactive, and red for terminated schedules. Note: Voltage schedules cannot be viewed using the Schedule Explorer.
233
9. Schedule
Figure 9-33. Selecting a schedule

Clicking Information displays the selected schedules information
Figure 9-34. Schedule Explorer - information

Clicking Executions displays the selected schedules executions
Item Name Description
Description Indicates the name for the selected schedule. Indicates the description assigned to the schedule.
234
9. Schedule
Item Time Zone Read Window
Description Indicates the time zone applied to the schedule. Indicates the read window during which the schedule must complete reading its assigned meters. Indicates the percent of assigned meters that were read successfully. Indicates the last date and time the schedule ran. Indicates the number of meters assigned to the schedule. Indicates the purpose of the schedule: Billing Non-billing Synchronization Voltage reads If present, indicates the date and time the schedule was terminated from EA_MS.
Percent Meters Read Last Execution No. of Meters Purpose
Termination Date
Figure 9-35. Schedule Explorer - executions

Clicking Performance displays the selected schedules performance
235
9. Schedule
Item Number Started Completed (Initial) No. Active Meters
Description The number of schedule executions within the specified time frame. Indicates the date and time the schedule started to run. Indicates the date and time the schedule run completed. Indicates the number of active meters (installed) assigned to the schedule.
Note: For synchronization schedule, this number indicates the number of gatekeepers assigned to the schedule.
Expected Reads No. of Resubmits Actual Reads Percent Success Finished (with Resubmit) Indicates the total number of meters expected to be read successfully by the schedule. Indicates the number of resubmits
Figure 9-36. Schedule Explorer - performance
Resubmitting a Schedule
If a schedule is unable to read all of the meters associated with it, you can resubmit the schedule to retrieve the data from all unread meters or you can read unread meters individually (see Performing an on request read of a meter on page 95 and Performing a special read for billing on page 120).
236
9. Schedule
This action can also be used to resubmit a synchronization schedule. However in this case, the system will also synchronize any changes made between the initial execution and resubmit. This implies that: Any new gatekeepers added between the initial execution and resubmit will be marked as requiring synchronizing and will be included in the resubmit. Any changes made that affect existing gatekeepers that were successfully synchronized to in the initial execution will cause that gatekeeper to be included in the resubmit. Examples include addition / deletion of TOU schedules, changing Rex meter assignments to TOU, billing schedules, removing Rex meters, discover of newly installed REX meters, node jumping activity etc.) Any meters that were added to the data collection schedule after the initial execution will be read by a resubmit If a meter failed to be read and has been removed since the initial execution, the meter will not be read in the resubmit. To resubmit a schedule: 1. From the Actions menu, select Schedule > Resubmit. 2. Search for the schedule. 3. Select the schedule. The Resubmit Schedule form displays the schedules information.
Figure 9-37. Resubmitting a schedule

Warning: Resubmitting a schedule calls all meters that were not read. Depending on the number of meters not read, this action could take some time to complete.
Once all of the meters assigned to the schedule have been read, the Resubmit Schedule form displays the results.
237
9. Schedule
Figure 9-38. Resubmit Schedule results

The table below describes the information displayed by the schedule Resubmit report. Item Meter Name Description The meter name of meters unsuccessfully read during prior attempt and is a hyperlink to Meter > Viewing a meters information. The status of the meter read attempt. Is a hyperlink to the schedules Performance Report that was updated by the resubmit action.
Read Status View Latest Performance Report
Modifying a Schedule
This action allows you to change a schedules reading window, description, file location, start time, schedule dates and periodicity. In addition, you can also add or remove meters from the schedule.
Note: Only execution dates in the future can be added or removed.

To change a schedule: 1. From the Actions menu, select Schedule > Modify. 2. Search for the schedule.
238
9. Schedule
Figure 9-39. Selecting a schedule

3. Select the schedule. The Modify Schedule form displays the schedules information.
Figure 9-40. Modifying a schedule

4. Change the appropriate information as needed. 5. Click Submit. The Modify Schedule form displays the status of the action. Note that system will not (that is, it will return an error) allow execution dates in the past to be removed for non-periodic schedules.
239
9. Schedule
Adding or removing meters from Schedule 1. Click on the Assign Meters page.
A listing of all meters currently on the schedule is displayed.
Note: If the schedule has more than 50 meters assigned, the form initially does not display any meters. Click View More to search for a specific meter or a group of meters you wish to change or remove from the schedule.
Figure 9-41. Add/Remove meters from schedule

To change an assigned meters Data Set: 1) Select the Data Set from the meters drop list. 2) Click Submit. To remove meters from the schedule: 1) Check all meters that are to be removed from the schedule. 2) Click Submit. To add meters to the schedule: 1) Click Add. A Search dialog displays allowing you to search for meters that can be added to the schedule. 2) Select the meters to add to the schedule. 3) Select the Data Set Name for each added meter. To remove a meter from the Add New Meters list, check the meter and click Remove.
Note: For synchronization schedules the selection list will only display gatekeepers. For billing schedules, the selection list will only display meters that are not currently on billing schedules.
240
9. Schedule
Figure 9-42. Modifying a schedule - adding meter

4) Click Submit. The Modify Schedule form displays the status of the action.
Note: EA_MS does not allow the same meter to be on multiple schedules for LP data collection. EA_MS will return an error if you attempt to assign any meter to a data set that contains load profile as a component and the meter is already on some other schedule for load profile collection. Note: After modifying a billing schedules next execution date or meter assignments (whether adding or removing), the information needs to be synchronized to the gatekeeper (using Meter > Advanced Meter Functions to perform an on request synchronization).
Exchanging Schedules
This action allows you to switch one or more meters from one schedule to another. To exchange one or more meters to another schedule: 1. From the Actions menu, select Schedule > Exchange. EA_MS displays a list of all schedules.
241
9. Schedule
Figure 9-43. Schedules list

2. Select the appropriate schedule from the list. The Exchange Schedule form displays the schedules assigned meters and their data sets.
Figure 9-44. Exchange Schedule form
242
9. Schedule
3. Check the meters to be moved to the new schedule. 4. Select the New Schedule Name from the drop list. 5. Select the meters to be moved to the new schedule.
Figure 9-45. Selecting meters

6. Click Submit to perform the exchange. The system will switch all the selected meters to the new schedule. If the schedule is used for billing and the meters are on a data set with demand reset (that is, a demand rate), this will also trigger a synchronization to gatekeepers to send the new assignments and the new billing dates for the meters involved in the exchange.
Note: The meter will remain on the same data set in the new schedule.
Creating a schedule
EA_MS supports a variety of reading schedules: billing - Creating a billing schedule for REX meters non-billing synchronize - Creating a synchronization schedule voltage reads - Creating a voltage reads schedule
Demand metering and schedules

REX meters
EA_MS handles demand in the REX meters differently compared to the A3 ALPHA meter. In the A3 ALPHA meter, the current period data is read and then a demand reset occurs. For the REX meter, EA_MS synchronizes its next billing date to the gatekeeper. The day before the billing date, the gatekeeper arms the REX meter (on the midnight before the billing
243
9. Schedule
date) for a demand reset to occur. At midnight the REX meter performs a demand reset and copies the current period data to previous period. During the billing schedule, the gatekeeper reads the REX meter to retrieve the previous period demand for billing. REX meters may be programmed to collect three demand values. The marriage file for the meter will detail the demand values and EA_MS will show the demand values in the reading file. For REX meters, metering demand data works as follows: 1. EA_MS synchronizes to the gatekeeper the next billing date for each meter on the 900 MHz local area network (that is, REX meters and A3 ALPHA nodes) that is on a demand or time of use demand rate. 2. The gatekeeper arms the meter for demand reset at midnight of the day before the billing date. 3. At midnight of the billing date, the REX meter performs a demand reset and copies a snapshot of the billing data, which is later retrieved by the gatekeeper. For example, if the billing date is April 21st, then the gatekeeper will arm the REX meter on April 20 at 00:00. The REX meter performs a demand reset on April 21st at 00:00. Some time after that (say at 01:00), the gatekeeper will read the snapshot data from the meter.
A3 ALPHA meters with EA_NIC

A3 ALPHA meters with EA_NIC configured for short data format may be programmed to collect two demand values plus total demand. The marriage file for the meter will only detail the two demand values; however, EA_MS will show all three demand values in the reading file. A3 ALPHA meters with EA_NIC configured for long data format support two metered quantities, all tier cumulative or maximum demands, identification information for 2 channels of load profiling, and 2 channels of interval data. Additionally, each of the tiered demands may be configured to support coincident demand metering.
Note: A3 ALPHA meters with EA_NIC configured for short data format do not time stamp demand values. If the gatekeeper failed to arm the meter for a billing or season change demand reset, the time stamp of readings may be off by several hours. Sparse network deployments may be particularly vulnerable to this effect.
Caution: A3 ALPHA meters with EA_NIC configured for long data format require more data storage on the gatekeeper and accordingly reduce the maximum number of meters supported by the gatekeeper. Additionally, more data packets are required to read all the data can result in an increased number LAN communication failures.
Load profile and REX meters

EA_MS supports the scheduled and on request reading of load profile (LP) data from REX meters. When creating a schedule to read LP data, you need to take into account the following parameters: the amount of available storage in the gatekeeper the amount of available storage in the REX meter the data collection times
Note: Elster strongly recommends using Load Profile (last 24 hours) or Load Profile (last One Week) for collecting load profile data to reduce burden on the gatekeeper and the network.
Storing load profile data in a gatekeeper

During manufacturing Elster configured the A3 ALPHA gatekeeper with the following two parameters: maximum number of nodes (that can register)
244
9. Schedule
maximum number of LP nodes The table below details the maximum number of days of available LP storage in the gatekeeper based on the two parameters: Max # End Points 1024 / 20481 1024 / 2048 512 512 1024 600 300 Max # LP End Points 150 300 150 300 1024 600 300 # of Days of Storage by LP Interval 15 min 7 3 10 5 1 2 5 30 min 14 7 19 9 1 4 10 60 min 28 14 39 19 3 9 21
1. EA_Gatekeeper FW 6.0 or higher.
Note: A3 ALPHA meters with EA_NIC that are configured to collect two channels of LP (long data format) count as 2 meters in this calculation.
When determining the proper EA_MS schedule configuration for reading load profile from the gatekeeper you must keep in mind the maximum number of day of storage in the gatekeeper. To reduce the risk of losing REX LP data, you need to configure EA_MS to read the gatekeeper before the maximum number of days is exceeded.
Storing load profile data in a REX meter

The table below details the number of hours of load profile data that can be stored in the REX meter (ver. 3.0): LP Interval 15 min 30 min 60 min # of Days of Storage 5 10 20
Gatekeeper LP data collection times

The table below describes when the gatekeeper usually reads load profile data from the REX meters: LP Interval 15 min 30 min 60 min Collection Interval every 4 hours every 6 hours every 12 hours Collection Times 2:00, 6:00, and 10:00 2:00 and 8:00 2:00
When determining the proper EA_MS schedule for reading LP data from a gatekeeper, please keep in mind the above collection times. You will want to read a gatekeeper after it has retrieved data from its registered REX meters.
TOU data and A3 ALPHA meters with EA_NIC

Even though A3 ALPHA meters are not assigned to EA_MS TOU schedules, they still must be programmed with a TOU program using Elsters meter support software, Metercat. Meters must be assigned to a billing schedule that includes a demand reset. As in the REX meter, EA_MS synchronizes the information to the gatekeeper and the gatekeeper will arm the node for the demand reset at midnight on the day before the billing date.
245
9. Schedule
The meter performs the demand reset at midnight (00:00) and copies the current period data to the previous period register. The gatekeeper reads the previous period data during the first reading after midnight. For season changes, use Metercat to program the meter with the season change information. When the season change occurs as programmed, the meter performs a demand reset and copies the current season data to the previous season register. The gatekeeper reads the previous season data the next time it reads the node. During every billing reading with the gatekeeper, EA_MS asks the gatekeeper for previous season data read since the last billing read.
Note: If the A3 ALPHA meters with EA_NIC jumped gatekeepers between a season change and a billing schedule, EA_MS may read previous season data from one gatekeeper and current and previous period data from the other gatekeeper.
Creating a new schedule

To create a new schedule: 1. From the Actions menu, select Schedule > New. The Add New Schedule form displays a blank form.
Figure 9-46. Adding a new schedule - periodic

2. Enter the Schedule Name. 3. Enter the Read Window and select the units (seconds, minutes, hours, or days). Caution: Read windows should not coincide with gatekeeper-REX read schedules.
4. Select the Schedule Type (Periodic or Non-Periodic).
Note: Elster recommends that synchronization schedules be periodic. Note: Voltage Reads must be periodic.
5. Select if the Schedule is used for one of the following: a. not used for billing b. used for billing
Note: EA_MS supports a maximum of 29 billing schedules. Note: For REX meters, the billing date and meter assignments are synchronized to the gatekeeper and the gatekeeper will arm the meter for a demand reset on the midnight before the billing date.
246
9. Schedule
c. used for synchronization d. used for voltage reads 6. Select the Start Time.
Note: If you are creating a synchronization schedule, you must specify the Start Time.
7. Select the Schedule Time Zone. This is the time zone used for interpreting the schedules start (execution) time. For example, if you want to ensure that a schedule always runs at 11:00 PM Pacific time, you should select the Pacific time zone for this schedule.
Note: Voltage Reads do not need the Time Zone set. Note: This setting affects the dates and times listed on schedule reports.
8. Enter the schedule Priority (1 - 64,000) where the higher the number the higher priority.
Note: Schedules in progress will not be pre-empted (interrupted) when a higher priority schedule starts, but no new schedules with a lower priority will start until all schedules with higher priority have been started.
9. Enter the Retry Count (minimum of 1). 10.Enter the Retry Interval (in seconds) [default = 120]. 11. For voltage read schedules, enter the Schedule Run Duration (mins). 12.Select to Enable Auto Resubmit if you want the schedule to automatically resubmit when it fails to read one or more meters on the schedule. If Auto Resubmit is enabled, enter the Max Resubmits. If Auto Resubmit is enabled, enter the Resubmit Frequency. If Auto Resubmit is enabled, enter the Resubmit Threshold (secs). 13.Enter the schedule Description. 14.Enter the schedule File Location. if no location is specified, EA_MS delivers the file to the default folder configured during system installation (usually, X:\EE\dfs\billing_schedules or X:\EE\dfs\non_billing_schedules where X: is the EA_MS installation drive) if a relative path is specified (for example, LAN_data, EA_MS creates a new folder under the default folder location configured during system installation if a full path is specified to an existing folder (for example, C:\my_data), EA_MS ignores the configured default folder location and writes the file to the specified location 15.Depending on the selected schedule type, select the appropriate Schedule Dates (for periodic where the schedule runs every X number of minutes, hours, days, weeks, or months) or Schedule Date (for non-periodic where the schedule runs on specific dates).
Note: For periodic schedule, the schedules specified periodicity must be greater than the Read Window.
247
9. Schedule
Figure 9-47. Adding a new schedule - non-periodic
Figure 9-48. Adding a new schedule - synchronization
248
9. Schedule
Figure 9-49. Adding a new schedule - voltage reads

16.If you are assigning meters to the new schedule select the Assign Meters page. 17. Click Add to select meters to be added to the new schedule.
Note: A meter can belong to only one billing schedule at any given point in time. EA_MS displays a list of meters that are not currently assigned to a billing schedule. It also means that the data collected by the schedule will be delivered to the default path or the File Location specified in the schedule definition. Note: If you are creating a synchronization schedule, EA_MS will only display gatekeepers that are not on a synchronization schedule.
Figure 9-50. Adding meters to a new schedule

Caution: If the schedule is not used for billing and the assigned meters associated data components contain a demand reset, a demand reset will not be performed.
18.Select a Data Set Name from the drop list.
Note: EA_MS allows you to assign data sets if at least one of the components in the data set is supported by the meter. See Component Mismatch Report on page 170 for details on mismatched components.
19.Click Submit to create the new schedule. The Add New Schedule form displays the action results.
249
9. Schedule
Creating a billing schedule for REX meters

When creating a billing schedule for REX meters, you must be mindful of how billing is handled by EA_MS: EA_MS must synchronize the billing schedules to the gatekeepers at least 36 hours before the first billing date in the schedule if the billing schedule runs more than once a month (for example, every two weeks), the billing dates must be at least 48 hours apart. EA_MS cannot reconfigure demand settings in the REX meter. You can assign meters to billing schedules at any time prior to the midnight of the billing date, however, you must ensure the following information has been synchronized to the gatekeeper: the next billing date for the schedule the meter assignment to the billing schedule
Creating a synchronization schedule

When creating a synchronization schedule use the following guidelines: Only one synchronizing schedule should be defined for the entire system. The synchronizing schedule should be setup as a periodic schedule that runs no more than once a day. The synchronizing schedule should run after all billing schedules and all resubmits have been completed (usually at the end of a business day). Assign all gatekeepers to the synchronizing schedule. Meters can be assigned to a synchronizing schedule at any time even on the day before billing as long as you ensure that the information gets synchronized to the gatekeeper prior to midnight of the billing date (using Meter > Advanced Metering Functions to perform an on request synchronization). New TOU and billing schedules must be synchronized to gatekeepers prior to synchronizing the new schedules meter assignments. For billing schedules with a 2-3 day billing cycle, the time factors involved in arming REX meters for demand reset require special attention when creating a synchronizing schedule. For example, a particular meter is on a demand rate and on a billing schedule with the following datesMay 2 and May 5. In order to correctly arm the meter for a demand reset, the synchronizing schedule should run on April 30th and May 3rd after the billing schedules have executed and all resubmits have completed but prior to a midnight crossing (that is, May 1st 00:00 and May 4th 00:00). A normal 20-day billing cycle and a once-a-day or once-every-two-days synchronizing schedule is usually unaffected by these constraints (except for getting the synchronized data that needs to occur at system initialization). In order to assist users in managing the synchronizing process, EA_MS provides the following reports: The Synchronization Summary Report (Reports > Residential Communication > Synchronization Summary) provides a report of information in the system (TOU schedules, billing schedules and gatekeepers) that has changed since the last execution of a synchronizing schedule and consequently requires synchronizing to the gatekeepers. The Associated Nodes Report for Gatekeeper (Reports > Residential Communication > Associated Nodes) indicates if the nodes require synchronizing from EA_MS or if they have synchronizations pending as of the last communication session with the gatekeeper.
250
9. Schedule
Note: Elster recommends that you allow one set of changes to be successfully synchronized prior to making additional changes that require synchronizing (particularly in relation to changes to TOU schedules).
The Pending Synchronization Report (Reports > Residential Communication > Pending Synchronizations) provides a listing of REX meters and A3 ALPHA nodes that hsave not received synchronized information from their registered gatekeeper.
Viewing a synchronizing schedule file

Note: Synchronizing schedule files are located in the non_billing_schedules folder on the EA_MS server. In addition to the standard file header and status information, the synchronizing schedule file may also contain old data (billing and load profile) for meters unregistered during the synchronizing that do not belong to any billing or load profile data collecting schedule.
Additionally, to view the synchronizing schedule files: 1. From the Reports menu, select Meters > Readings. 2. Search and select the appropriate gatekeeper. The Meter Readings Report displays. 3. Select the File Name for the appropriate synchronizing schedule (for example: E:\EE\dfs\non_billing_schedules\mas5_AutoTestSynchronization_01_08_10_2006_20_38_06.xml The Display Meter Readings report displays.
Figure 9-51. Synchronizing schedule file contents - reading summary
251
9. Schedule
Figure 9-52. Synchronizing schedule file contents - reading details

The table below explains the format of the synchronizing schedule file. Item Communication Session On File Created On Meter Type Serial # Description Account Number Site Clock Outage Count Summary Description The date and time the communication session was initiated. The date and time the schedule reading file was created. The Meter Type. The Serial Number. The Description. The Account No. The Site ID. The Meter Time; Server Time; Observes DST (Yes/No). Indicates the last outage count prior to this reading date and time.
252
9. Schedule
Forcing a synchronization to a gatekeeper

To force a synchronization to a gatekeeper: 1. For every gatekeeper, from the Actions menu, select Advanced Metering Functions. The On Request Read - Advanced - Meter form displays 2. Select a gatekeeper based on the meter, account number, account name, site ID, etc. 3. Retrieve the gatekeeper. 4. Select the gatekeeper. The On Request Read - Advanced form displays the gatekeepers information. 5. From the Data Components list, select Synchronize changes with EA_MS. 6. Click Submit. 7. After synchronizing to all gatekeepers, review the Synchronization Summary Report (Reports > Residential Communication > Synchronization Summary) to verify that no gatekeepers have a pending synchronization (that is, they have not received the synchronized data). Also review the Pending Synchronization Report (Reports > Residential Communication > Pending Synchronization Report) for a listing of REX meters that have not received synchronized information from their registered gatekeeper.
Creating a voltage reads schedule

EA_MS provides the ability to schedule reads of voltage data from REX2 meters registered to gatekeeper with module FW 6.0 (30 - 40 REX2 meters maximum) on periodic basis as frequently as every five minutes. EA_MS provides alerts when voltage readings by gatekeepers take longer than a configurable amount of time or when the number of devices registered to a gatekeeper exceeds a configurable threshold which impact the systems ability to read all the data in the allotted time.
Note: REX2 meters can only be on one voltage read schedule. A synchronization to gatekeepers is required before voltage data will be recorded by system.
To read voltage data using EA_MS the system administrator must configure gatekeepers to read meters on a schedule. Refer to the EA_MS Installation and Administration Guide for details on configuring the voltage readings. Once the system administrator has configured EA_MS, create a voltage read schedule by selecting used for voltage reads from the Schedule Types drop list. To view voltage reading performance reports see Voltage Reading Performance reports on page 221.
Deleting a schedule
Note: You can only delete a schedule if there are no meters assigned to it. EA_MS allows users the option of deleting meter assignments at the time that the schedule is being deleted. See Changing a meters schedule assignment on page 82 for details on removing meters from a schedule.
To delete a schedule: 1. From the Actions menu, select Schedule > Delete. 2. Search for the schedule. 3. Select the schedule. 4. Check Remove Meter-Schedule Assignments Before Delete if meters are assigned to the schedule but it still must be deleted. The Delete Schedule form displays the schedules information.
253
9. Schedule
Figure 9-53. Deleting a schedule

5. Check to Remove Meter-Schedule Assignments before deletion. 6. Click Submit to delete the selected schedule. The Delete Schedule form displays the actions results and the schedules termination date is updated.
254
10. TOU Schedules
10
TOU Schedules
Actions and reports

The EA_MS menu allows you to access the following TOU actions and reports: Actions Import/Overwrite Delete Exchange Reports View All View TOU Schedule Report
About TOU Schedules

Note: Only REX or REX2 meters are assigned in EA_MS to TOU schedules. Gatekeepers automatically read all data from A3 ALPHA meters collecting TOU data.
In EA_MS, the REX meter must be assigned to a billing schedule for TOU rates to work properly. In addition, a gatekeeper will not register a REX meter unless it has the REX meters TOU schedule.
Creating the TOU program

To create TOU schedules, you must create a Metercat program containing a Rates component [specifying Switch Times and Day Types] and a Special Dates component). 1. From the Metercat File menu, select New > Program. 2. For Meter Family, select either A1800 ALPHA or A3 ALPHA and click Next. 3. For Meter Type, select D (Demand) or T (Time of Use) and click Next. 4. For Program Type, select Time Of Use and click Next. 5. Enter a unique Program ID number and click Next. 6. Check to use Special Dates and click Finish. 7. For the unnecessary components, select to use the Sample components: Constants Quantities - Metering, Display, Interval Data Configuration Demand Logs Special Features Service Test 8. Configure the Rates component > Switch Times with the Default Rate (off-peak or lowest rate) as Rate C. After a power restoration, the REX meter stores data in Rate C until the correct time and rate from the gatekeeper. 9. Configure the Special Dates component as follows: for a multi-season TOU schedule: season changes must be programmed as recurring dates
255
10. TOU Schedules
must check to Perform demand reset on every season change to ensure reading the previous season data. for a single-season TOU schedule: one season change date must be programmed as a recurring date (for example, Season Change to Winter on Dec 1) unecessary to check Perform demand reset on every season change
Note: Holidays are programmed into the gatekeeper using Metercat. REX meters use the holiday list programmed in the gatekeeper therefore it is unnecessary to add holidays to the Special Dates lists.
10.Save the program and close the program. 11. From the Metercat Tools menu, select Export/Import Program. 12.Select the REX TOU program created above and click Export. 13.Select Program Exchange Docs (*.ped) from the Save as type drop list. 14.Save the file to a known location. 15.Close the Export/Import Program dialog and exit Metercat. 16.In EA_MS import the Metercat TOU PED file into EA_MS using Actions > TOU > Import/Overwrite (see Importing TOU schedules on page 260).
About non-TOU schedules

EA_MS supports up to eight1 TOU and non-TOU schedules for use with REX meters. EA_MS allows two non-TOU schedules. All REX meters are initially assigned to the default nonTOU schedule, Total Energy Only, after their marriage file is imported into EA_MS. Generally this schedule should be the most common/lowest rate so that customers get the benefit of a doubt during any intermittent periods in which the system cannot determine the actual rate in effect (for example, synchronizations have not completed). The Total Energy Only non-TOU schedule does not configure the REX meter to display demand on the meters LCD. A second non-TOU schedule may be created that configures a REX meter to display demand on the LCD.
TOU schedules and meter display

In addition to defining rate changes, TOU schedules also configure the REX meter display. For example, if the REX meter is currently in a TOU schedule, the meters LCD will display the current rate and time. If the meter is assigned to the default non-TOU schedule the meters LCD will not display demand.
Synchronizing TOU schedules

Just as billing schedules must be synchronized at some time before the midnight preceding the billing date, TOU schedules and meter assignments to TOU schedules must be synchronized before the midnight prior to the season change at midnight so that the gatekeeper can arm the REX meters in time to do a demand reset on a season change.
Note: Because of the effects of node jumping and registration, Elster recommends that you wait until the TOU schedule is successfully synchronized to every gatekeeper before assigning any REX meters to the schedule.
Changes to TOU schedules have substantial impact on synchronization schedules, meter configuration, and system behavior and consequently need to be thought through extensively.
Note: Because A3 ALPHA meters with EA_NIC configured for short data format do not time stamp billing and season change data, a situation may occur where a season change occurred after midnight, but the data is time stamped at midnight. Networks that are volatile or sparsely populated may show a high incidence of such situations.
1. This number is a function of the memory available in the gatekeeper.
256
10. TOU Schedules
Viewing a list of all TOU schedules

To view a listing of all TOU schedules: 1. From the Actions menu, select TOU > View All. The TOU Schedule report displays a listing of all TOU schedules defined in EA_MS.
Figure 10-1. TOU Schedule List
Item Name Program Name Program # # Energy Tiers # Demand Tiers # Seasons Last Season Change
Description The TOU Schedule name (hyperlink to View TOU Schedule Information report). The name of the Metercat program imported into EA_MS. The unique identification number for the TOU program (provided by Metercat support software). The number of energy tiers used in the schedule including Total Energy. The number of demand tiers used in the schedule including Total Demand. The total number of seasons defined in the TOU schedule. The date of the last season change.
257
10. TOU Schedules
Item Next Season Change Schedule Created On Default
Description The date of the next scheduled season change. The date and time the TOU schedule was created. If checked, indicates the schedule is the default TOU schedule.
2. Click to select the desired TOU schedule from the listing.
Viewing a TOU schedules information

From the View All The View TOU Schedule Information report displays the selected TOU schedules information including season definitions, day types, and season change dates.
Figure 10-2. View TOU Schedule - schedule summary
258
10. TOU Schedules
Figure 10-3. View TOU Schedule - season definitions
Item Name Program Name Program # # Energy Tiers # Demand Tiers # Seasons Last Season Change Next Season Change Schedule Created On Schedule Terminated On The TOU Schedule name.
Description
The name of the A3 ALPHA meter program imported into EA_MS. The unique identification number for the TOU program (provided by Metercat support software). The number of energy tiers used in the schedule including Total Energy. The number of demand tiers used in the schedule including Total Demand. The total number of seasons defined in the TOU schedule. The date of the last season change. The date of the next scheduled season change. The date and time the TOU schedule was created. If present, indicates the date and time the particular TOU schedule was deleted from EA_MS.
259
10. TOU Schedules
Item # Meters
Description The number of meters that are currently assigned to the particular TOU schedule. The Meter Listing Report lists the meters on the schedule.
Note: In the case of the default TOU schedule, this number does not include meters in inventoried state.
Day Type (season) Seasons Day Type From To Tier Demand The current season and the Day Type settings for the days of the week. The season name and season change date. The day type (weekday, weekend, holiday). The beginning time for the tier definition for the day types. The ending time for the tier definition for the day types. The tier assignment for the tier definition for the day types. If checked, indicates that the tier is a demand tier.
Changing TOU schedule assignments

This action allows you to switch one or more REX meters from one TOU schedule to another.
Note: Before using this action, please verify that the new TOU schedule has been synchronized to all gatekeepers. See Synchronization Summary Report on page 342 for details. Note: While the Associated Nodes Report for Gatekeeper will identify any nodes that are registered to gatekeepers that need synchronizations, nodes that are orphaned but require synchronizations are not identified in any specific report. Elster recommends that you verify that none of the nodes with configuration changes (such as assignment to a new TOU schedule) are in an orphaned state prior to making the next set of configuration changes. Ideally, the utility should troubleshoot and resolve issues with any nodes that show up as orphaned prior to making any configuration changes that affect that node.
To exchange TOU schedules: 1. From the Actions menu, select TOU > Exchange.
Figure 10-4. Exchange a TOU Schedule form
260
10. TOU Schedules
2. Select one of the listed TOU schedules. The Exchange TOU form displays the schedules assigned meters and their data sets.
3. Check the meters to be moved to the new TOU schedule.
Figure 10-5. Exchange TOU Schedule form

4. Select the New Schedule Name. 5. Click Submit to exchange the TOU schedule assignment for the specified meters.
Importing TOU schedules

This action allows you to import (and overwrite if necessary) TOU schedules for REX and REX2 meters. The maximum number of TOU and non-TOU schedules is eight. EA_MS is installed with a default TOU schedule, Total Energy Only.
Note: Although EA_MS supports eight TOU schedules, one schedule is required for exchange purposes.
Caution: Elster recommends that you not make changes to more that one TOU schedule during a single synchronization cycle. Wait for one set of changes to synchronize successfully before making any additional changes. To prevent potential conflicts between TOU schedules, Elster does not recommend using the overwrite setting on TOU schedules that have been synchronized at least once to meters.
Caution:
Note: After deleting a TOU schedule, Elster recommends that you either force a synchronization (see Forcing a synchronization to a gatekeeper on page 252) or wait until the next schedule has synchronized successfully before creating any new TOU schedules.
261
10. TOU Schedules
To import a TOU schedule: 1. Use Metercat support software to create a program with a TOU rate (that is, with the Day Types, Special Dates and Switch Times components).
Note: By default, EA_MS expects that TOU programs with season changes will also arm REX meters for demand reset on season change (that is, Special Dates component > Perform Demand Reset on every Season Change checked). To configure EA_MS so that no demand resets are required at a season change, define the Special Dates component with Perform Demand Reset on every Season Change unchecked. Note: EA_MS requires that TOU programs created in Metercat should include a demand reset at season change and at least one season change date to ensure proper accumulation in the proper tier.
2. Export the new program from Metercat using Tools > Export/Import Program (using the default file type of Program Exchange Document (*.ped)). 3. Use the TOU Extractor tool from Metercat installation CD to output a file that EA_MS can import. 4. In EA_MS, from the Actions menu, select TOU >Import/Overwrite. 5. Check This is a non-TOU Schedule for a TOU schedule that has no switch times for peak and off-peak rates or for configuring the REX meter to display demand.
Note: A non-TOU schedule will take up one of the eight available TOU schedule slots in the gatekeeper.
Figure 10-6. Importing a non-TOU schedule
262
10. TOU Schedules
Figure 10-7. Importing a new TOU schedule

6. For TOU schedules, click Browse to navigate to the location of the File Name for the TOU PED file from Metercat. 7. Enter the Name (TOU Schedule). 8. Select the Operating Territory2. 9. Check to Overwrite TOU if exists.
Note: Elster recommends that you use this setting for only overwriting non-TOU schedules or for overwriting a TOU schedule that has no assigned meters. To change a TOU schedule to which meters are assigned, use TOU > Exchange.
10.Check Default to set this schedule to be the default schedule for all REX meters. 11. Check a maximum of two items to be included in the Demand Configuration meters LCD display (Tier A, Tier B, etc.).
Note: The selected demand display should match with the demand configuration of the REX meters specified in the marriage file.
12.Check if this is a Total Demand TOU schedule. 13.Click Submit to import the new TOU Schedule. The Import TOU Schedule form displays the action results.
Changing the default TOU schedule

To define a new default TOU schedule: 1. Use Actions > TOU > Import/Overwrite giving the TOU schedule a new name. 2. Enter the File Name for the PED file. 3. Select the Operating Territory from the drop list. 4. Check Default. 5. Check the items to be included in the Demand Configuration meters LCD display (Tier A, Tier B, etc.). 2. EA_MS currently supports only one Operating Territory.
263
10. TOU Schedules
6. Check if this is a Total Demand TOU schedule. 7. Click Submit. The previous default schedule becomes a non-default schedule. All meters assigned to the old default schedule (except for inventoried meters) remain on the old schedule.
Overwriting the default TOU schedule

To overwrite the default TOU schedule: 1. Reassign any assigned meters to a different non-default TOU schedule using Actions > TOU > Exchange or Meter > Modify. 2. For each gatekeeper in the system, force a synchronization of this change using Actions > Meter > Advanced Metering Functions and selecting Synchronization to Gatekeeper as the Component Type. 3. After synchronizing to all gatekeepers, review the Synchronization Summary Report (Reports > Residential Communication > Synchronization Summary) to verify that no gatekeepers have a pending synchronization (that is, Requires Synchronization is unchecked). 4. Review the Associated Nodes Report for Gatekeeper (Reports > Residential Communication > Associated Nodes Report) to ensure the node assignments to the non-default TOU schedule is in effect (that is, Requires Synchronization is unchecked). 5. If you change the TOU or billing schedule itself, (new, or modify next billing date) that would show up on the Synchronization Summary Report. 6. If all gatekeepers have received the synchronization, use Actions > TOU > Import/ Overwrite using the original name of the TOU schedule. 7. Check Default. 8. Check Overwrite TOU if exists. 9. Click Submit. 10.Reassign the meters back to the TOU schedule using Actions > TOU > Exchange or Meter > Modify. The original default TOU schedule is replaced with the new default TOU schedule.
Changing TOU schedules

You can use the following procedure to change an existing TOU schedule (if no meters are assigned to it) or to create a new TOU schedule and move all the meters from an existing schedule to the new TOU schedule. To change a TOU schedule: 1. Use Metercat support software to create a new TOU program (that is, with the Day Types, Special Dates and Switch Times components). 2. Export the new program from Metercat using Tools > Export/Import Programs (using the default file type of Program Exchange Document (*.ped)). 3. Import the TOU schedule into EA_MS using Actions > TOU > Import/Overwrite and give the TOU schedule a new Name.
Note: Do not check Overwrite TOU if exists.

4. Synchronize the new TOU schedule to the gatekeepers using one of the following procedures: a. For each gatekeeper, use Actions > Meter > Advanced Metering Functions and selecting the Component Type Synchronization to Gatekeeper. b. Wait for the synchronization schedule to run at its next scheduled time. (This assumes all the gatekeepers are in the synchronization schedule.) 5. Review the Synchronization Summary Report (Reports > Residential Communication > Synchronization Summary) to verify that no gatekeepers have a pending synchronization (that is, they have not received the synchronization).
264
10. TOU Schedules
6. Move the desired meters to the imported TOU schedule using one of the following procedures: a. Individually move each meter using Actions > TOU > Exchange or Meter > Modify. b. Create a CIS file and import it using Actions > Meter > Import CIS File. 7. Wait until all of the gatekeepers and REX meters have received the synchronization. 8. To verify that all gatekeepers have received the synchronized information, check the Schedules Performance Report and verify that the performance was 100%. 9. To verify that the REX meters have received the synchronized information, view the Associated Nodes Report for Gatekeeper (Reports > Residential Communication > Associated Nodes) for each gatekeeper and verify that the Last Modified Date is after the time the Synchronization Schedule ran (to make sure the data is current) and verify that the Pending Synchronization column is not checked for every REX meter. 10.After the new TOU Schedule has been synchronized to all the gatekeepers and REX meters, you may delete the old TOU Schedule from EA_MS using Actions > TOU > Delete if needed.
Note: The deletion needs to be synchronized to all gatekeepers before any new TOU schedules are created. See the procedure above for information about synchronizing to gatekeepers and using the synchronization schedule, and how to verify that all gatekeepers have received the synchronized information.
Deleting a TOU schedule

Caution: Elster recommends deleting a TOU schedule only if the maximum number of eight TOU schedules is about to be exceeded. EA_MS associates a unique identifier to each TOU schedule. If you delete a TOU schedule and then create a new TOU schedule you risk having the new TOU schedule being associated with the old identifier. This could lead to conflicts where two gatekeepers may use the same identifier for different TOU schedules.
Note: EA_MS will not allow you to delete a TOU schedule that has meters assigned to it.
To delete an existing TOU schedule: 1. From the Actions menu, select TOU > Delete. A listing of all TOU schedules displays. 2. Select the TOU schedule.
Figure 10-8. Deleting a TOU Schedule
265
10. TOU Schedules
3. Click Submit to delete the selected TOU schedule. The Remove TOU Schedule form displays the action results.
Note: After deleting a TOU schedule, Elster recommends that you either force a synchronization (see Forcing a synchronization to a gatekeeper on page 252) or wait until the next schedule has synchronized successfully before creating any new TOU schedules.
266
11. Demand response
11
Demand response
Note: If your utility did not purchase the Demand Response module, you will not see the actions or reports provided for Demand Response. You will need to enable this functionality to use demand response. Contact Elster for more information.
Actions and reports

Depending on the users security profile, the Actions menu allows you to access the following demand response actions: Actions HAD management Remove HAD from meter Actions using CIS Import: Create New HAD Assign HAD to Meter Create Demand Response Groups Assigned HAD listing Unassigned HAD listing Commissioned/Decommissioned reports Confirmed by Device Unconfirmed by Device History by Meter Reports
Pricing [ZigBee_NIC] Create Pricing Modify Pricing Clear Pricing Assign Pricing to meter HAN Pricing reports All Confirmed Unconfirmed Home Area Network Events report Emergency Management Create/Assign Emergency Event to meter Cancel Emergency Event Emergency management reports Confirmed by Device Unconfirmed by Device Overridden By User
Messaging Create Message Cancel Message Messaging reports Unconfirmed by User Pending Cancel
267
11. Demand response
Legacy support
EA_MS provides support to the following legacy HAD functions Elster Pricing [legacy devices] Creating Elster Pricing Energy Conservation (EC) Create EC Event Assign EC event to TOU Schedule using CIS Import Assign EC event to meter Energy conservation event listing Energy conservation event listing Elster Pricing Configuration report Elster Pricing Synchronization report
About demand response

Demand response (DR) allows utilities use to control consumer load across the system. Demand response uses a variety of methods: TOU schedules are used to encourage consumers to use less electricity during peak time where the cost is higher; consumers shift their usage to off peak times where the cost is lower (see About TOU Schedules on page 254 for details). Load control allows the utility to control consumers appliances such as water heaters and heat/air conditioners; utilities can turn off appliances on a TOU schedule or emergency time. in-home displays provide information on pricing, demand, and consumption to the consumer allowing them to actively conserve energy One of the available option boards for the REX2 meter is a ZigBee Smart Energy Profile (SEP) network interface card (NIC). This NIC allows the REX2 meter to communicate with a variety of ZigBee SEP-enabled home area devices (HAD), for example, programmable communicative thermostats (PCTs), in-home displays, and load control (LC) devices.
Figure 11-1. EnergyAxis and the home area network
268
11. Demand response
Elsters demand response solution supports the following key functions: Managing home area devices (HAD) facilitates the inventory, commissioning and decommissioning of home area devices Pricing - time-of-use rates that utilities charge the consumer based on the time of day that electricity is used Messaging - allows a utility-defined message to be transmitted over the EnergyAxis EA_LAN to the homes HAN and displayed on a specific consumers in-home display or thermostat that supports messaging Emergency management - load control (LCE) or emergency management (EM) events allow the utility one-time, direct control of the consumers usage via thermostats or load control devices based on a specific time Critical tier overrides (CTO) - critical peak pricing and control EA_MS also supports the following legacy functions: Energy conservation (EC) - allows the utility direct control of the consumers usage via thermostats or load control devices based on either TOU or CTO Creating Elster Pricing - Elster Pricing provides rate protection from time-of use variation of electricity for consumers using legacy HAN devices
About demand response groups

To improve the efficiency of demand response actions, EA_MS implements demand response groups. The groups can include the following demand response actions: Demand Response Pricing Program (DR Pricing) Demand Response Message Groups (DR Messaging) Utility Enrollment Group (UEG) A meters home area network can only be associated with only one DR Pricing group and up to 4 DR Messaging groups. The UEG group is limited to ZigBee devices associated with the meter. Caution: EnergyAxis Management System does not provide reports on which meter or device is associated with which Area, Feeder, DR Pricing Program, or DR Message Groups. Elster recommends maintaining a listing of meters and HADs and their associated DR groups.
Demand response groups can specify the Area and the Feeder data for the meter premise. Demand response groups have the following limits: Item Area Descriptions The area that the premise is associated with: range of 0 - 65534 default value = 65535 [blocked] The feeder within a substation that the premise is associated with: range of 0 - 254 default value = 255 [blocked] The Demand Response Pricing Program the premise is associated with: range of 0 - 254 default value = 255 [blocked] The DR Message groups the premise is associated with: range of 0 - 255 default = 255 [blocked] value = 0 [all messages accepted]
Feeder
DR Program
DemandResponseMessageTextGroup_1 DemandResponseMessageTextGroup_2 DemandResponseMessageTextGroup_3 DemandResponseMessageTextGroup_4
270
11. Demand response
Commissioning HADs
To commission a home area device (HAD): 1. Purchase home area device and enter into inventory. Each HAD has a set of information associated with it which is stored in a file similar to the marriage file for REX meters. You use the Import CIS File action (see Adding a new HAD on page 270). When this action is complete the devices stage is Imported.
Note: You can also use Web Services to perform the Import CIS File actions.
The Unassigned HAD listing displays a listing of HADs that are in inventory and have not been assigned to a REX2 meter. 2. Create your demand response (DR) groups using the Import CIS File action (see Creating a Demand Response Group on page 271) and assign the REX2 meter to the specified DR groups. 3. Assign device to REX2 meter. Once an HAD has been imported and installed, it needs to be associated with or assigned to a REX2 meter (or home area network). You use the Import CIS File action (see Assigning a HAD to a meter on page 271). When this action is complete the devices stage is Assigned. The Assigned HAD listing displays a listing of HADs that have been assigned to a REX2 meter. EA_MS automatically synchronizes the HAD assignment to the meter. When this action is complete the devicess stage is Active. The Commissioned/Decommissioned reports - Unconfirmed by Device displays a listing of commissioned HADs that have not yet been confirmed by the device. 4. The HAD joins the REX2 meters HAN generating a Commissioning Status Event (CSE) in the meter. The Home Area Network Events report (event type = Commissioning Status Event) displays a list of meters with CSEs.
Decommissioning HADs
To decommission a HAD: 1. Unassign device from REX2 meter. Use Removing a HAD from a meter or the Import CIS File action. When this action is complete the devicess stage is Removal Pending. 2. EA_MS automatically removes the HAD association with the meter. Once the HAD has been unassigned from a REX2 meter, you need to synchronize the association using the Advanced Metering Functions action and selecting Commission/decommission in-home devices. When this action is complete the devicess stage is Removed. The Unassigned HAD listing displays a listing of HADs with status Inventoried. Use Actions > Meter > On Request Read, Read home area network status to view a report of HAN status and events from meters. The Home Area Network Events report (event type = Decommissioning Status Event) displays a list of meters with DSEs. Commissioned/Decommissioned reports - History by Meter
Adding a new HAD

Upon purchase of HAD, add the device to EA_MS using the CIS Import (see Importing a CIS file on page 136). EA_MS supports the creation of a new HAD using the system API and importing a CIS Import file. For example, the CIS import file would look like the following:
<HANDevice DeviceClass="HVAC or Furnace"
EA_MS Release 7.6 User Guide DeviceName="Thermostat1" CommunicationId="113344556a7b" CommunicationType=ZigBee LinkKeyAlgorithm="Elster" />
271
11. Demand response
The newly created devices can be viewed using the Unassigned HAD listing report.
Creating a Demand Response Group

Prior to installing HAD devices, you must create a Demand Response Group to which you assign the meter which will have associated HAD. Using CIS Import (see Importing a CIS file on page 136) import a CIS import file the defines the Demand Response Group and associates the group with the meter. For example, the CIS import file would look like the following:
<MeterDemandResponseGroup MeterName="KW_REX2_11118185_3938371" Area="1" Feeder="1" Timezone="-20" DemandResponsePricingProgram="22" DemandResponseMessageTextGroup_1="1" DemandResponseMessageTextGroup_2="2" DemandResponseMessageTextGroup_3="3" DemandResponseMessageTextGroup_4="4" />
See About demand response groups on page 268 for details about demand response groups.
Assigning a HAD to a meter

Prior to installing HAD devices at customer premises, the REX2 meter on the premise should be installed and operating as part of an EnergyAxis network being read and managed by EA_MS. Once a customer enrolls in a demand response program, the devices selected for installation at the premise should be assigned to the meter prior to installing the physical devices in the field. This function is also called provisioning or commissioning. This process authorizes the REX2 meters ZigBee NIC to allow the HAD devices to join the home area network when the devices are installed in the field. EA_MS supports the assignment of up to 8 home area devices to a REX2 meter using the system Web Services and by importing a CIS import file (see Importing a CIS file on page 136). For example, the CIS import file would look like the following:
<ProvisiononHANDevice DeviceName="KWSMAPP171" CommunicationId="001BC5007000014D" LinkKey="8126834FE2B74D2CD6232E9217766DE4" LinkKeyAlgorithm="SmartEnergy" StartRandomizationMinutes="20" StopRandomizationMinutes="30" MaxTimeInMinutesToJoin="10" TimeToStartJoining="now" UtilityEnrollmentGroup="22" CommunicationId="113344556a7b" <DeviceClass Name="HVAC or Furnace"/> </ProvisionHANDevice>
If the HAD is being installed on a premise with a newly installed REX2 meter, Elster recommends that you verify associations by:
272
11. Demand response
Use View Meter to ensure REX2 meter is associated with TOU Schedule. Use an On Request Read to ensure REX2 meter is associated with a gatekeeper. Perform a synchronization to each gatekeeper to add each HAD to the appropriate REX2 meter (see Performing advanced metering functions on page 111). The newly associated devices can now be viewed using the Assigned HAD listing report. After the home area network device is installed, and events from the HAN have been read, the Commissioning reports to verify status.
Removing a HAD from a meter

Prior to removing a home area device from service or removing a meter from a premise that supports a HAN, you must remove (or decommission) the home area device. To remove one or more HADs from a meter: 1. From the Actions menu, select HAN > HAD > Remove HAD from a meter. The Remove HADs from Meter form displays.
2. In the Meter Name text box enter the search characters in the text box. Or Click Display Meters to view a list of all meters.
Note: You can use % as a wildcard when entering search string.

3. Select the Meter Name from the Meter Listing. 4. Click Lookup HADs.
273
11. Demand response
5. Drag the specific Device Name from the Available HADs List and drop the device in the Selected HADs List. Or Check Select/Deselect All to select all devices and drag and drop them in the Selected HADs List.
Note: Click Remove to remove a selected Device Name from the Selected HADs List.
6. Click Submit. Decommissioned devices can be viewed using the Unassigned HAD listing report. Perform a synchronization to each gatekeeper to remove each HAD from the appropriate REX2 meter (see Performing advanced metering functions on page 111). A variety of commissioning/decommissioning reports are available to verify status.
Removing a HAD from a meter using CIS Import

EA_MS supports the removal of a home area device to a meter using the system API and by importing a CIS import file (see Importing a CIS file on page 136). For example, the CIS import file would look like the following:
<ProvisiononHANDevice MeterName="Meter2929 " CommunicationId="113344556a7b" IsActive=0 />
After importing the CIS file, the HAD status shows as Removal Pending.
274
11. Demand response
Assigned HAD listing

The Assigned HAD Listing report lists home area devices that are assigned to REX2-EA meters with ZigBee option board. 1. From the Reports menu, select HAN > Assigned HAD Listing. The Assigned HAD Listing Report form displays.
2. Select the From and To dates and times that the CIS Import File was submitted to EA_MS. 3. Click Submit.
See Customizing a report layout on page 371 for details on changing the report layout. The Assigned HAD Listing report displays the following information: Item Name Communication ID State Description The 10 character DeviceName for the device. The hexadecimal MAC address of the device. Indicates the state of the device: Active - has been synchronized (commissioned) Assigned - has not been synchronized Indicates the DeviceClass of the HAD. Indicates the HAD device CommunicationType. Indicates the date and time submitted to EA_MS. Indicates the name of the meter to which the HAD is assigned. Indicates the utility enrollment group for the device.
Device Class (Type) Communication Type Imported Date Meter Name Utility Enrollment Group
275
11. Demand response
Unassigned HAD listing

The Unassigned HAD Listing report displays a list of home area devices that have been submitted to EA_MS but are not assigned to a REX meter. 1. From the Reports menu, select HAN > Unassigned HAD Listing. The Unassigned HAD Listing Report displays.
The Unassigned HAD Listing Report displays the following information: Item Name Communication ID State Device Class Communication Type Imported Date Description DeviceName of the HAD. The MAC address of the device. Indicates the state of the device: Inventoried Indicates the DeviceClass of the HAD. Indicates the HAD device CommunicationType. Date and time the CIS Import file was imported into EA_MS.
Pricing
Pricing provides rate protection from time-of use variation of electricity for consumers using HAN enabled devices. Pricing, like TOU rates, helps a utility recover costs associated with time-of use of high energy appliances like HVAC, water heaters, etc. Creating a Price Creating Elster Pricing Pricing allows the consumer to monitor their energy costs. EA_MS allows a utility to setup a pricing configuration for a specific TOU schedule that includes different energy prices for different tiers and different seasons. A pricing configuration can also include a fixed monthly charge and allow the ability to charge based on a breakpoint (number of cents per kWh below breakpoint and number of cents per kWh above breakpoint). A utility may choose to populate one or more of the available fields. This is determined solely by the rate structure approved by their utility commission: 1. If they have TOU rates they can enter values for each TOU rate. 2. Whether or not they use TOU rates, the other values (such as, flat monthly, fuel and volumetric values) can be used.
276
11. Demand response
Creating a Price
To create a Price for HAD equipped with ZigBee_NIC: 1. From the Actions menu, select Home Area Network (HAN) > Pricing > Create Pricing. The Create Pricing form displays.
2. Enter a Pricing Name (maximum of 50 characters). 3. Enter the Provider ID (set by the utility). 4. Configure the Tier Mapping: a. Check the appropriate meter TOU Rate (A, B, C, or D). b. Select the Tier from the drop list. c. Enter the Tier Label .
Note: You must configure at least one Tier.

5. If you intend to broadcast the Pricing, configure Broadcast Details: a. Check to Use Broadcast. b. Enter the appropriate Area (use 0 to send to all areas). c. Enter the appropriate Feeder (use 0 to send to all feeders). d. Enter the appropriate DR Program (use 0 to send to all DR Programs).
Note: Elster recommends that you never configure all zeros for a broadcast because all HADs will be contacted with the new Pricing information.
6. Enter the Start Date and Time. Or Check Now for the new Pricing to take effect immediately. 7. Enter the Duration (in minutes) for the new Pricing.
Note: Elster recommends using a duration that is at least 15 minutes to allow the HAD time to properly activate the Pricing.
8. If needed, check to keep Pricing in effect Until Changed. 9. For each Tier mapped: a. Select the relevant Tier (A, B, C, or D).
277
11. Demand response
b. Enter the Price that is in effect. 10.Enter the Price Ratio (range of 1 to 254). Or Enter the Generation Price. Or Enter the Generation Ratio (range of 1 to 254). Or Enter the Alternate Cost Delivered.
Caution:
Not all home area devices may support all or any of the following pricing parameters. Verify device capabilities before making selection.
Note: All prices should be expressed in dollars as follows .xxxx.

11. Click Submit. EA_MS includes the following Pricing reports: HAN Pricing reports Elster Pricing reports
Modify Pricing
To modify an existing Pricing definition: 1. From the Actions menu, select Home Area Network (HAN) > Pricing > Modify Pricing. The Modify Pricing form displays.
278
11. Demand response
2. Enter a New Pricing Name (maximum of 50 characters). 3. Select the old Pricing Name from the drop list. 4. Enter the Provider ID (set by the utility). 5. Configure the Tier Mapping: a. Check the appropriate meter TOU Rate (A, B, C, or D). b. Select the Tier from the drop list. c. Enter the Tier Label .
Note: You must configure at least one Tier.

6. If you intend to broadcast the Pricing, configure Broadcast Details: a. Check to Use Broadcast. b. Enter the appropriate Area (use 0 to send to all areas). c. Enter the appropriate Feeder (use 0 to send to all feeders). d. Enter the appropriate DR Program (use 0 to send to all DR Programs).
Note: Elster recommends that you never configure all zeros for a broadcast because all HADs will be contacted with the new Pricing information.
7. Enter the Start Date and Time. Or Check Now for the new Pricing to take effect immediately. 8. Enter the Duration (in minutes) for the new Pricing.
Note: Elster recommends using a duration that is at least 15 minutes to allow the HAD time to properly activate the Pricing.
9. If needed, check to keep Pricing in effect Until Changed. 10.For each Tier mapped: a. Select the relevant Tier (A, B, C, or D). b. Enter the Price that is in effect. 11. Enter the Price Ratio (range of 1 to 254).
279
11. Demand response
Or Enter the Generation Price. Or Enter the Generation Ratio (range of 1 to 254). Or Enter the Alternate Cost Delivered.
12.Click Submit. EA_MS changes the selected Pricing definition.
Clear Pricing
To clear an existing Pricing definition: 1. From the Actions menu, select Home Area Network (HAN) > Pricing > Clear Pricing. The Clear Pricing form displays.
2. Enter search parameters for the Pricing Name. Or
280
11. Demand response
Enter the Start Date and Time. Or Enter the End Date and Time. 3. Click Display Pricing. The Pricing definitions that meet the specified criteria displays. 4. Select the desired Pricing from the Price Listing. 5. Click Submit. The selected Pricing is cleared.
Assign Pricing to meter

To assign an existing Pricing definition to a meter: 1. From the Actions menu, select Home Area Network (HAN) > Pricing > Assign Pricing To Meter. The Assign Pricing to Meters form displays.
2. Select the Pricing Name from the drop list. 3. Enter the search parameters for the meters to be assigned to the Pricing definition. 4. Click Go to search for the meters. A list of meters matching the search criteria displays. 5. From the Available Meter list, select the meters to be assigned to the Pricing definition. Or Check Select/Deselect All to select all meters in the listing. 6. Drag-and-drop the selected meters to the Selected Meter List. 7. To remove a meter from the Selected Meter List, select the meter and click Remove. 8. Once all the meters have been added to the Selected Meter List, click Submit. Or To reset the form, click Reset.
HAN Pricing reports

EA_MS includes the following HAN Pricing reports for ZigBee SEP devices: All Confirmed
281
11. Demand response
Unconfirmed To view a report on ZigBee pricing: 1. From the Reports menu, select Reports > Home Area Network (HAN) > HAN Pricing. The Demand Response Reports form displays.
2. Select Pricing from the drop list. 3. Enter the Start and End Dates and Times. 4. If needed, enter a Meter Name search wildcard. 5. If needed, enter a Price Name search wildcard. 6. Select the type of report from the Filters: All - view all Pricings Confirmed - view only Pricing that has been confirmed by the meter Unconfirmed - view only Pricing that is unconfirmed 7. Click Submit. The HAN Pricing reports display. The Pricing Reports display the following information: Item Pricing Name Season Name Flat Monthly Charge Base kWh Breakpoint Base Prior to Breakpoint Base After Breakpoint Fuel Factor Tier A, B, C, D Price Definition Indicates the name of the TOU schedule affected by the pricing definition. Indicates the seasons affected by the pricing definition. Indicates the flat monthly charge expressed in cents. Indicates the breakpoint for volumetric pricing. Indicates the price for energy use before volumetric breakpoint. Indicates the price for energy use after reaching volumetric breakpoint. Indicates the fuel factor. Indicates the price (in cents) for energy usage for each tier: Tier A Tier B Tier C Tier D
282
11. Demand response
Item Meters on Schedule Pending synchronizations
Definition Indicates the number of meters on the affected schedule. Indicates the number of meters waiting to receive the TOU pricing.
All
Confirmed
283
11. Demand response
Unconfirmed
Messaging
When a utility needs to communicate important information to a customer such as a generation shortage, the messaging function allows a utility-defined message to be transmitted over the EnergyAxis network to the home's HAN and displayed on a customer's in-home display or thermostat that supports such messaging capabilities. When a message is created, EA_MS sends the message to the specified meter.
Creating a message
To create a message for displaying on a HAD: 1. From the Actions menu, select HAN > Messaging > Create. The Create Message form displays.
284
11. Demand response
2. Enter a descriptive Message Name. 3. Select the Start Date and Time for the message to display. 4. Check Now if the message is to display immediately. 5. Enter the Duration time (in minutes) that the message should display (range of 1 to 65534). 6. Check Until Changed if the message is to display continuously until another message is sent. 7. Check if message delivery Confirmation Required (that is, indicating whether the HAD should require the user to acknowledge the message). If delivery confirmation is required, the HAD displays the message and prompts the customer to acknowledge the message. 8. Enter the Message (maximum length is 90 ASCII characters). 9. Select the Priority from the drop list: Low Medium High Critical 10.From the Target Device drop list select whether to: Use Broadcast - sends broadcast to all meters based on Area, Feeder, or DR Program Send to Devices - sends to specified devices 11. If you selected Send to Devices, from the meter selection drop list select whether the Meter Name Starts With or Contains the search characters.
285
11. Demand response

12.From the Available Meter List, select the Meter Name and drag to the Selected Meter List. Or Select to Send to Devices to send the message to selected meters. If you select to Send to Devices, the Select Meters pane displays allowing you to specify the devices to receive the message.
286
11. Demand response
13.Enter the search characters in the text box. 14.Select the Meter Name from the list and click the right arrow to add it to the Selected Meter list. 15.If you selected to Use Broadcast, the Broadcast Details pane displays allowing you to enter the group broadcast parameters: a. Area - Integer, range of 0 to 65534, default= Blocked [65535] b. Feeder - Integer, range of 0 to 254, default=Blocked [255] c. DR Program - Integer, range of 0 to 254, default=Blocked [255]
Note: Selecting Use Broadcast will result in communication to EA_Gatekeepers that have registered meters that are in the specified Group at message creation time. Note: If any one of the broadcast parameters is set to Blocked, then the command will be blocked for all devices.
16.Click Submit. This message will be transmitted at the next scheduled gatekeeper synchronization. Alternatively, perform an on request synchronization to the gatekeeper for the appropriate REX2 meter (see Performing advanced metering functions on page 111). 17. Repeat for additional meters or broadcast groups if required. View the Messaging reports for further information.
Cancelling a message
To cancel a message: 1. From the Actions menu, select HAN > Messaging > Cancel. The Cancel Message form displays. 2. Select whether the Message Name Starts With or Contains the search characters. 3. Enter the From Date. 4. Enter the To Date. 5. Click Display Messages to view of list of all messages with the specified parameters. 6. Select the Message Name from the Message Listing. 7. Select the cancel Priority: Low Medium High
287
11. Demand response
Critical 8. Check if Confirmation Required to acknowledge the message cancellation.
9. Click Submit.
Messaging reports
All messaging reports are created from one form. 1. From the Reports menu, select Home Area Network (HAN) > HAN Messaging. The Demand Response Reports form displays.
2. Select Messaging from the drop list. 3. Enter the Start Date and Time. 4. Enter the End Date and Time. 5. Enter a search string for the Meter Name.
288
11. Demand response
Or Leave wildcard to view all meters. 6. Enter a search string for the Message Name. Or Leave wildcard to view all messages. 7. Select the type of report from the Filters: All - displays all messages Delivered - displays a listing of all delivered messages Undelivered - displays a listing of all undelivered messages Confirmed by User - displays a listing of all messages that are confirmed by the user Unconfirmed by User - displays a listing of all messages that are unconfirmed by the user Pending Cancel - displays a listing of messages that have a clear (or cancel) pending 8. Click Submit. The Messaging report displays in the right pane. The Messages reports display the following information: Item Name Text Creatiion Time Meter Start Time Duration Priority Conf. Reqd (confirmation required) Synchronized Time Deliver Time Definition Name of the message. The message to display on the HAD. Indicates the date and time the message was submitted to EA_MS. Indicates the name of the meter to which the HAD is assigned. Indicates the date and time the message should appear on the HAD. Indicates the length of time the message will appear on the HAD display. Indicates the priority selected when the message was created in EA_MS. Indicates if customer acknowledgement of the message is required. Indicates the date and time the meter received the message from a synchronization to the meter. Indicates the date and time the message was cancelled in EA_MS (if such an action was submitted).
See Customizing a report layout on page 371 for details on changing the report layout.
289
11. Demand response
All
Delivered
290
11. Demand response
Undelivered
Confirmed by User
291
11. Demand response
Unconfirmed by User
Pending Cancel
Controlling HAD devices

EA_MS provides functions that assists the utility in managing or controlling home area devices such as thermostats or load control devices installed on hot water heaters, pool pumps, etc. These functions are typically driven by third party demand response software using EA_MS's API but these functions can also be demonstrated as illustrated within this section: Elster supports two methods of controlling home area network devices;
292
11. Demand response
Emergency management events (EM or LCE) or time based events which are defined by a specific start time and duration (see Creating and assigning an EM or LCE event on page 292) Energy conservation events (EC) or time-of-use based events which are defined by the start and end of a specified time of use period
Note: Not all devices support both types of control. Verify the suitability of function for the selected home area device.
Emergency management
Unlike critical tier override, emergency management (EM) allows the utility to control demand response equipment (for example, thermostats, load control (LC) devices, etc.) starting at a utility-defined start time and continuing for a utility-specified duration without regard to cost of energy or TOU schedule.
Note: Emergency management allows the customer to override the EM or LCE event.
Creating and assigning an EM or LCE event

To create and assign an Emergency Management (EM) event or a load control event (LCE) to a meter: 1. From the Actions menu, select HAN > Emergency Management > Create/Assign LCE to Meters. The Emergency Management Events form displays.
2. Enter the Load Control Event Name. 3. Select the Start Date and time.
293
11. Demand response
Or Check Now to have the event occur immediately. 4. Enter the Duration (in minutes) to have the event occur this number of minutes after the Start Time. 5. Select one or more Device Class: None HVAC or Furnace Strip Heat Water Heater Pool Pump/Spa/Jacuzzi Smart Appliances Irrigation Pump Managed Loads Simple Loads Exterior Lighting Interior Lighting Electric Vehicle Generation Systems
6. From the drop list, select the Severity (indicates the priority of the event): Override allowed Green Level 1 Level 2 Level 3 Level 4 Level 5 No override allowed Emergency Planned Outage Service Disconnect
7. Enter the Utiity Enrollment Group. 8. Check to Broadcast the event using the gatekeepers broadcast. 9. Enter the following information: Item Load Adjustment (%) Description For load control devices, indicates the percent of the load to adjust the device: 100 %
Note: Leave blank to ignore.

Duty Cycle (%) For devices that support this feature, indicates the percentage of time the device should be controlled during the event: value is in range 0 % to 100 %

Randomize Start Time Check to enable the use of randomization when starting the LCE to help manage the stress on the grid which may occur when devices are controlled.
Note: If enabled, Randomize Start Time may impact the Duration, that is, if the Duration is 15 minutes and Randomize Start Time is enabled the actual duration of the event may be less than the specified duration.
Randomize End Time Check to enable the use of randomization for the end time of the load control event to help manage the stress on the grid which may occur when devices come on.
Note: If enabled, Randomize End Time may impact the Duration, that is, if the Duration is 15 minutes and Randomize End Time is enabled the actual duration of the event may be less than the specified duration.
294
11. Demand response
Item Thermostat attributes Offset/Setpoint Unit
Description
Indicates the units used by the thermostat: Fahrenheit Celsius For HVAC or Furnace, indicates the desired number of degrees to offset cooling set point programmed in the thermostat. Fahrenheit - range of 0 to 10 degrees Celsius - range of 0 to 5.55 degrees
Cooling Offset (range of 1 to 20)

Heating Offset (range of 1 to 20) For HVAC or Furnace, indicates the desired number of degrees to offset heating set point programmed in the thermostat. Fahrenheit - range of 0 to 10 degrees Celsius - range of 0 to 5.55 degrees

Cooling Setpoint For HVAC or Furnace, indicates the desired cooling setpoint. Fahrenheit - range of 50 to 90 degrees Celsius - range of 10 to 32.22 degrees

Heating Setpoint For HVAC or Furnace, indicates the desired heating setpoint. Fahrenheit - range of 50 to 90 degrees Celsius - range of 10 to 32.22 degrees
Note: Leave blank to ignore. Note: When using both offsets and setpoints, the device determines the parameter that provides the best energy savings and uses that setting for managing the event.
10.From the meter selection drop list select whether the Meter Name Starts With or Contains the search characters.

11. Enter the search characters in the text box. 12.Click Go to view a list of meters matching the search criteria. 13.Select the Meter Name from the Meters to Assign list and click the right arrow to add it to the Meters Assigned list. Or Check Select/Deselect All to select all meters listed. 14.Drag-and-drop the selected meters from the Available Meters List to the Selected Meters List. Caution: 15.Click Submit. After the task is submitted, a form displays the Status of the task and lists the Meter Names and Execution Times for the EM or LCE event. To view a list of devices that did not receive the event, use Emergency management reports, Unconfirmed by Device. After the event occurs: Use Emergency management reports, Overridden By User to view a list of devices where the EM or LCE event was overridden by the customer. Use Emergency management reports, Confirmed by Device to view a list of devices whose meters have received notification of the event. Emergency Management events are synchronized immediately to the meter after you click Submit.
295
11. Demand response
Cancelling an EM or LCE event

To cancel an Emergency Management (EM) event or a Load Control Event (LCE): 1. From the Actions menu, select HAN > Emergency Management > Cancel. The Emergency Management Events form displays.
Figure 11-3.
2. Enter the LCE Event Name in the search text box. 3. Select the From Date and Time. 4. Select the To Date and Time. 5. Click Display LCEs to view a list of LC events matching the criteria. 6. Select the LCE Name from the Load Control Events Listing. 7. Enter the Cancel Attributes: a. Cancellation Date and Time. Or Check Now to have the cancellation take effect immediately. b. Check Randomize to use the HADs randomization feature. Caution: 8. Click Submit. After the task is submitted, a form displays the Status of the task and lists the Meter Names and Execution Times. Emergency Management events are synchronized immediately to the meter after you click Submit.
Item Meter Name Status
Description Indicates the name of the meter associated with the device. Indicates the status of the Cancel command: Success Fail Indicates the date and time the meter received the Cancel command.
Execution Time
296
11. Demand response
Emergency management reports

Confirmed by Device Unconfirmed by Device Overridden By User
Confirmed by Device
The EM Confirmed by Device report lists EM and LCE events whose assigned meters have received notification of the event. To view a report on meters with EM or LCE events that are confirmed: 1. From the Reports menu, select HAN > Emergency Management > Confirmed by Device. The Emergency Management> Confirmed by Device report form displays.
2. Select the From and To dates and times. 3. Click Submit. The Emergency Management - Confirmed by Device report displays.
The Emergency Management> Confirmed by Device report displays the following information: Item LCE Meter Name Device Name Synchronization Time Meter Received Time Device Received Time Definition Indicates the EM or LCE event name. Indicates the name of the meter associated with the device. Indicates the name of the HAD the event affects. Indicates the date and time EA_MS synchronized the event to the meter. Indicates the date and time the meter received the event. Indicates the date and time the HAD received the event from its assigned meter.
297
11. Demand response
Additionally, the Home Area Network Events report lists EM and LCE events.
Unconfirmed by Device
The EM Unconfirmed by Device report displays a list of EM or LCE events that have been sent to meters but have not been verified. To view a report on meters with EM or LCE events that are unconfirmed: 1. From the Reports menu, select HAN > Emergency Management > Unconfirmed by Device. The Emergency Management> Unconfirmed by Device report displays.
2. Enter the From and To dates and times. 3. Click Submit.
The Emergency Management> Unconfirmed by Device report displays the following information: Item LCE Meter Name Device Name Synchronization Time Definition Indicates the event name. Indicates the name of the meter to which the HAD is assigned. Indicates the name for the device. Indicates the date and time the event was synchronized to the meter.
Overridden By User
To view a report on meters with EM and LCE events that have been overridden by the customer: 1. From the Reports menu, select HAN > Emergency Management > Overridden by User. 2. Enter the From and To dates and times.
298
11. Demand response
3. Click Submit. The Emergency Management > Overridden by User report displays.
The Emergency Management> Overridden by User report displays the following information: Item LCE Meter Name Device Name Override Time Definition Indicates the event name. Indicates the name of the meter to which the HAD is assigned. Indicates the name for the device. Indicates the date and time the event was overridden by the customer.
Home Area Network Events report

The HAN Events Listing report displays a selection of events generated by HAD.
Note: On request reads or schedules reads of the HAD are relayed through the REX meter to the HAD is assigned to the meter. The data is stored in the ZigBee NIC of the REX meter.
To read the days HAN events, you can also perform an On Request Read on the REX meter selecting the data component Read home area network status. See Performing an on request read of a meter on page 95 for details. To create a HAN Events Listing report: 1. From the Reports menu, select HAN > Events Listing. The Home Area Network Events Report form displays.
299
11. Demand response
Figure 11-4. HAN Events report form

2. Select the To and From Dates.
Note: The To date cannot be in the future or before the From date.
3. Select the Event Type from the drop list: Commissioning status event Decommissioning status event Display message event Energy conservation event General event Home area network event Load control event Time of use event
Note: Events displayed on the report depend on the HAD capabilities.

4. Click Submit. The report displays the selected information.
300
11. Demand response
Figure 11-5. Home Area Network Events report

See Customizing a report layout on page 371 for details on changing the report layout. The table below describes the information that the report displays: Item Event Type Description Indicates the type of event: CSE - commissioning status event DSE - decommissioning status event DME - display message event ECE - energy conservation event HAN - home area network event LCE - load control event TOU - time of use event (including CTO events) Indicates the subtype of event. Indicates the name of the meter to which the HAD is assigned. Indicates the account number for the meter. Indicates the home area device name. Indicates the MAC address for the HAD. Indicates the date and time that EA_MS read the event. Indicates the date and time the meter received the event.
Event SubType Meter Account Number Device Device Comm ID Event Logged Time Meter Received Time
301
11. Demand response
Item Device Received Time Schedule Start Time Device Start Time User Input Time
Description Indicates the date and time the device received the event from the meter. Indicates the date and time the event was scheduled to begin. Indicates the date and time the device started the event. Indicates the date and time the event ended normally or was overidden by the customer (either acknowledged or override the event). Indicates the date and time the event ended, either the normal ending at the end of the event or because it was cancelled by the utility or overridden by the customer. For Emergency Management and Messaging commands: COMPLETED - event completed normally PARTIAL COMPLETE OPTOUT overridden by user (Emergency Management only) SUPERCEDED command overlapped by another event ACKNOWLEDGED acknowledged by User (Message only) REJECTED - rejected by the device INVALID NOT TERMINATED For Commissioning/Decommissioning commands: COMPLETED - event completed normally CANCELLED - event cancelled SUPERCEDED command overlapped by another event REJECTED rejected by the device INVALID NOT TERMINATED For TOU commands: NOT TERMINATED
Termination Time
Termination Reason
Terminated Reason
Terminated Reason
Exporting to PDF file

To export a report to a PDF file: Click on the PDF icon in the upper right of the report window. The selected report displays as a PDF in a browser window. You can save the file to any location.
302
11. Demand response
Exporting to CSV file

To export a report to a CSV (comma separated value) file: 1. Click on the Excel icon in the upper right of the report window. 2. Select to either Save or Open the file. If you select Open, the selected CSV report opens in a browser window.
303
11. Demand response
Commissioned/Decommissioned reports
Confirmed by Device
To view a list of confirmed commissioned and decommissioned HADs: 1. From the Reports menu, select HAN > Commission/Decommission > Confirmed. The Confirm Commissioned/Decommission Report form displays. 2. Select the From and To dates and time for the report.
304
11. Demand response
3. Click Submit. The Confirmed Commissioned/Decommission Report displays.
The Confirm Commissioned/Decommission Report - Confirmed by Device displays the following information: Item Device Name Meter Name Account Number Activity Name of the HAD. Indicates the name of the meter to which the HAD is assigned. Account number of the meter. Indicates the activity performed on the device: Commission Decommission Date and Time the request was received by the REX2 meter. Date and Time the HAD received the request. Description
Meter Received Time Device Received Time
305
11. Demand response
Item Device Terminated Reason
Description For Commissioning/Decommissioning commands: COMPLETED - event completed normally CANCELLED - event cancelled SUPERCEDED command overlapped by another event REJECTED rejected by the device INVALID NOT TERMINATED
Unconfirmed by Device
To view a list of unconfirmed commissioned and decommissioned HADs: 1. From the Reports menu, select HAN > Commission/Decommission > Unconfirmed. The Unconfirmed Commissioned/Decommission Report form displays. 2. Select the From and To dates and time for the report.
3. Click Submit. The Unconfirmed Commissioned/Decommission Report displays.
The Unconfirmed Commissioned/Decommission Report - Unconfirmed by Device displays the following information: Item Device Name Meter Name Account Number Activity Name of the HAD. Indicates the name of the meter to which the HAD is assigned. Account number of the meter. Indicates the action performed on the device: Commission Decommission Date and Time the request was sent by the REX2 meter. Description
Transmitted to Meter Time
306
11. Demand response
History by Meter
To view a list of commissioned HADs by meter: 1. From the Reports menu, select HAN > Commission/Decommission > By meter. The HAN Commissioned by Meter Report form displays. 2. Enter the From and To date and time. 3. Search for the meter.
4. Select the meter. The Commissioned Activity by Meter Report displays.
The Commissioned Activity by Meter Report displays the following information: Item Device Name Meter Name Name of the HAD. Indicates the name of the meter to which the HAD is assigned. Description
307
11. Demand response
Item Account Number Activity Transmitted to Meter Time Meter Received Time Device Received Time Device Terminated Reason
Description Account number of the meter. Commission Decommission Date and Time the event was transmitted by the REX2 meter. Indicates the date and time the meter received the event. Date and Time the HAD received the event. For Commissioning/Decommissioning commands: COMPLETED - event completed normally CANCELLED - event cancelled SUPERCEDED command overlapped by another event REJECTED rejected by the device INVALID NOT TERMINATED
Legacy support
EA_MS provides legacy support for the following functionality: Elster Pricing Energy conservation
Creating Elster Pricing

Elster Pricing (formerly known as TOU Pricing) provides rate protection from time-of use variation of electricity for consumers using legacy HAN devices. See Pricing on page 275 for the ZigBee alternative to Elster Pricing. To create an Elster Pricing: 1. From the Actions menu, select Home Area Network (HAN) > Elster Pricing > Create. The Create Elster Pricing form displays.
2. Select a TOU Schedule from the list. A listing of available season pricing items displays.
308
11. Demand response
3. Enter the Elster Pricing structure in the text boxes provided. Caution: Not all home area devices may support all or any of the following pricing parameters. Verify device capabilities before making selection. Item Flat Monthly Charge (cents) Base kWh Breakpoint (kWh) Base Prior to Breakpoint (cents) Base After Breakpoint (cents) Fuel Factor (cents) Rate Per kWh TOU A (cents) Rate Per kWh TOU B Rate Per kWh TOU C Rate Per kWh TOU D Description Indicates the flat monthly charge (in cents). Indicates the breakpoint for volumetric pricing (in kWh). Indicates the price for energy use before volumetric breakpoint (in cents). Indicates the price for energy use after reaching volumetric breakpoint (in cents). Indicates the fuel factor (in cents). The price for energy usage in TOU A (in cents). The price for energy usage in TOU B (in cents). The price for energy usage in TOU C (in cents). The price for energy usage in TOU D (in cents).
4. Click Submit.
Elster Pricing reports

Elster Pricing Configuration report Elster Pricing Synchronization report
Elster Pricing Configuration report
309
11. Demand response
Figure 11-6.
Elster Pricing Synchronization report
310
11. Demand response
Energy conservation
Energy Conservation (EC) events are utility commands that control demand response equipment (for example, thermostats, load control devices, pool pumps, etc.) based on a TOU schedule. For thermostats, an EC event may be defined by any of the following: heating and cooling offsets heating and cooling setpoints critical tier temperature (Fahrenheit or Celsius) Other types of control devices can be defined by average load adjustment (in percent) or duty cycle (in percent). Unlike emergency management events which are non-repeatable by nature (that is, they begin at the specified start time and end after the specified duration), energy conservation events are designed to be repetitive enabling devices to be controlled each time a specific time-of-use (TOU) period occurs. For example, if control is desired during peak energy costs (TOU B), an energy conservation event may be defined specifying control parameters in TOU B (peak) but with no control parameters in TOU C (off peak). Once the energy conservation event is synchronized, the specified home area devices will be controlled each time the meter enters TOU B. As such, energy conservation events are defined for a specific TOU schedule and are synchronized to all meters on that TOU schedule when a home area device is commissioned (see Assigning a HAD to a meter on page 271). A special type of energy conservation event is a CPP (or critical peak pricing) event which is often implemented in conjunction with the Critical tier overrides to control home area devices.
Creating an energy conservation event

If you specify an EC event with offsets and a duty cycle, and selected device types of HVAC/ Furnace, pool pump, and water heater, the specified devices that support offsets would use the offsets and the devices that support duty cycle would use the duty cycle to conserve energy. To create an energy conservation event: 1. From the Actions menu, select Home Area Network (HAN) > Energy Conservation (EC) > Create. The Create Energy Conservation (EC) form displays.
311
11. Demand response
2. Enter a Name for the event.
Note: The Name of the EC event cannot contain special characters or spaces.
3. Select one or more Device Class from the listing: HVAC or Furnace Strip Heat Water Heater Pool Pump/Spa/Jacuzzi Smart Appliances Irrigation Pump Managed Loads Simple Loads Exterior Lighting Interior Lighting Electric Vehicle Generation Systems
4. Select the Thermostat Setpoint/Offset Unit: Fahrenheit Celsius 5. Check Allow Customer Override to allow the customer to override the event. 6. For each tier (TOU A, TOU B, TOU C or TOU D) enter the following information: Item Critical Peak Tier Cooling Offset Description Check to indicate tier is critical peak. For HVAC or Furnace, indicates the desired number of degrees to offset cooling set point programmed in the thermostat. Fahrenheit - range of 0 to 10 degrees Celsius - range of 0 to 5.55 degrees

Heating Offset For HVAC or Furnace, indicates the desired number of degrees to offset heating set point programmed in the thermostat. Fahrenheit - range of 0 to 10 degrees Celsius - range of 0 to 5.55 degrees
312
11. Demand response
Item Cooling Setpoint
Description For HVAC or Furnace, indicates the desired cooling setpoint. Fahrenheit - range of 50 to 90 degrees Celsius - range of 10 to 32.22 degrees

Heating Setpoint For HVAC or Furnace, indicates the desired heating setpoint. Fahrenheit - range of 50 to 90 degrees Celsius - range of 10 to 32.22 degrees

Load Adjustment (%) For load control devices, indicates the percent of the load to adjust the device: 100 %

Duty Cycle (%) For devices that support this feature, indicates the percentage of time the device should be controlled during the event: value is in range 0 % to 100 %

7. Click Submit to create the event.
Assigning an EC event to a TOU schedule

Caution: A TOU schedule can only have one EC event assigned to it. If you assign an EC event to a TOU schedule that already has an EC event assigned to it, the first EC event will be overridden by the second EC event.
By assigning an EC to a TOU schedule all of the meters currently assigned to the TOU schedule will be affected by the EC event. Meters are assigned to the TOU schedule after the assignment of the EC to the schedule will not be affected by the EC event. To assign an energy conservation event to a TOU schedule: 1. From the Actions menu, select HAN > Assign EC to TOU Schedule. The Assign Energy Conservation to TOU Schedule form displays.
2. Select the EC Name event from the list. 3. Select the TOU Schedule from the list. 4. Click Submit. After the EC is created, it will be synchronized at the next scheduled time to all meters on the TOU schedule.
313
11. Demand response
Note: You can perform an Advanced Metering Function to synchronize the EC to meters assigned to the TOU schedule.
Assigning an EC event to a meter

EA_MS supports the assignment of an EC event to a meter using the system API and by importing a CIS import file (see Importing a CIS file on page 136). For example, the CIS import file would look like the following:
<ThermosrarConfigToMeter MeterName="meterName" ThermostatConfiguration="ConfigName" />
After importing the CIS import file, perform an Advanced Metering Function to synchronize the assignment to the meter.
Energy conservation event listing

To view a listing of EC events: 1. From the Reports menu, select HAN > EC Listing. The EC Listing Report displays.
The EC Listing Report displays the following information: Item Name Creation Time Target Device Class Tier Details Description Name of the EC event. The date and time the event was created in EA_MS. Indicates the Device Type the event is targeted. Indicates the event settings for each tier. Click on View to see the event settings for the tiers.
Viewing EC event settings

Clicking on the View link in the EC Listing Report displays the settings for the selected event.
314
11. Demand response
315
12. Critical tier overrides
12
Critical tier overrides
Actions and reports

Depending on the users security profile, you may access the following CTO action and report: Create Critical Tier Override Reports > Home Area Network (HAN) CTO listing
Critical tier overrides

For utilities that offer critical peak pricing (CPP) or critical peak rebate (CPR) programs, energy efficiency and conservation are the goal. These programs allow a utility to charge more during critical periods by accumulating usage and demand in a different TOU tier. CPP and CPR customers then have the ability to change their energy usage for that day and time thereby reducing their energy charges. For days where there is a CPP event, the utility defines a critical tier override (CTO) event for a specific date and time and with a set duration. The customers HAD alerts the customer of the CTO using color-coded LEDs on the thermostat. For example, an Energate thermostat uses the following color-coded LEDs (in order of precedence): 1. Red - one or more events are currently in effect 1. Blue - one or more events have been overridden today 2. Yellow1 - one or more events scheduled for today 3. Green - one or more events have completed today
Note: Only one LED will appear lit at any one time.
Refer to the manufacturers user instructions for details on operating a particular HAD. Additionally, the utility can communicate this information to its customers who are on a CPP or CPR program using a HAN Message (see Creating a message on page 283).
Creating a critical tier override

A critical tier override must be created at least 24 hours before the event is to occur.
Note: If TOU pricing is assigned to the meters TOU schedule, the thermostat may display different pricing and costs for the critical tier. Note: If an EC event is assigned to the meters TOU schedule, the thermostat can be adjusted automatically during the CTO and the EC event may or may not allow the customer to override the temperature settings specified for the CTO tier.
To create a critical tier override: 1. From the Actions menu, select Critical Tier Override (CTO) > Create.
1. If an event completed within the past 60 minutes but no event is scheduled within the next 60 minutes, the green LED has precedence over the yellow LED.
316
The Create Critical Tier Override form displays.
2. Select the From date and time for the CTO to begin (must be a future date that is at least 24 hours after the current date). 3. Select the Duration (in a multiple of 15 minutes) for the CTO (for example, 15, 30, 45, 60, etc.). 4. Select the TOU Schedule which the CTO affects. 5. Select a Tier where the CTO usage data will accumulate.
Note: A CTO cannot be cancelled or deleted once it has been created.

6. Click Submit.
Note: The CTO is automatically synchronized as part of the normal synchronization schedule.
CTO listing
The Critical tier override (CTO) listing report displays a list of all CTO events. 1. From the Reports menu, select Home Area Network (HAN) > CTO Listing.
Figure 12-1. CTO listing report form

2. Select the To and From dates and times in which the CTO events occurred.
Note: From and To dates can include future dates and times.
3. Click Submit. The CTO Listing Report displays.
317
Item Start time Duration TOU Schedule Tier
Description Indicates the Start date and time for the CTO event. Indicates the length of time for the CTO event. Indicates the name of the TOU schedule affected by the CTO event. Indicates the tier where the CTO usage data accumulates.
See Home Area Network Events report on page 298 for additional information on CTO events. The Home Area Network Events report indicates when the CTO started, when it completed and if the CTO event was overridden by the customer.
318
13. Configuring elements
13
Configuring elements
About element configuration

With the release of REX2 meter with FW v2.0 and A3 ALPHA meter with FW v4.2, EA_MS supported minimum and maximum voltage thresholds. To ensure voltage monitoring setup is efficient and easy, EA_MS Rel. 7.5 implemented Voltage Min/Max Configuration Profiles. After creating the needed configuration profiles, the meters are assigned to the appropriate configuration profile. Once assigned, the selected meters will perform voltage monitoring using the configured profile settings.
Supported devices
A3 ALPHA meter FW v 4.2 with EA_Gatekeeper module FW v 5.2, 6.2, 7.0: ITM FW 4.x, 5.x, 6.0, 6.2, 7.0 ACB (Ethernet) FW v4.x, 5.2, 6.0, 6.2, 7.0 W-WIC (CDMA) FW v 1.3 E-WIC (Ethernet) FW v 3.5 REX2 FW v 2.0, 2.3, 3.0, 4.0
Note: Minimum and maximum voltage thresholds apply only to REX2 meters with FW v 2.0 or higher.
Actions and reports

Depending on the users profile, you may access the following element configuration actions and reporst: Actions Add/Remove Config Profile Assign Config Profile Reports View All Config Profiles Config Profies On Meter Meters On Config Profile
Adding a configuration profile

Note: Once a Configuration Profile has been assigned to any meter, it cannot be removed, it can only be replaced.
To create a new configuration profile: 1. From the Actions menu, select Element Configuration > Add/Remove Config Profile. The Add/Remove Configuration Profile form displays.
319
Figure 13-1.
2. From the drop list, select the Configuration Profile Type: REX2 Voltage Alarm Thresholds 120v REX2 Voltage Alarm Thresholds 240v REX2 Voltage Alarm Thresholds 480v REX2 Voltage Alarm Thresholds 600v 3. If you wish to copy from an existing template, from the Configuration Profile Templates drop list, select a template (lists all defined configuration profiles for the select profile type).
Note: If no configuration profiles are defined for the selected Configuration Profile Type the Configuration Profile Template drop list will be empty.
4. Enter the Profile Name (max. of 50 characters). 5. Enter the parameter values to be used in the template: Configuration Profile Type Configuration Profile Parameters Minimum Threshold (volts) Minimum Duration (secs) Maximum Threshold (volts) Maximum Duration (secs) 120v 90 - 118.8 V 0 - 127 sec 121.2 - 144 V 0 - 127 sec 240v 180 - 237.6 V 0 - 127 sec 242.4 - 288 V 0 - 127 sec 480v 275.2 - 360 V 0 - 127 sec 484.8 - 576 V 0 - 127 sec 600v 450 - 594 V 0 - 127 sec 606 - 720 V 0 - 127 sec
6. Check to Enable Alarms for either of the following: Minimum Threshold Maximum Threshold 7. Enter a Description for the configuration profile (range of 1 to 150 characters).
320
Figure 13-2.
8. Click Add. The configuration profile is added to EA_MS.
Assign a configuration profile

To assign a configuration profile to a meter: 1. From the Actions menu, select Element Configuration > Assign Config Profile. The Assign Configuration Profile form displays.
321
Figure 13-3.
2. From the Configuration Profile Types drop list, select a type. 3. From the Configuration Profile Templates, select a template. The form displays the Configuration Profile Details.
322
Figure 13-4.
4. Enter a Starts With string (using % wildcard). Or Enter a Contains string (using % wildcard). 5. Click Go to view a list of meters with the specified string. 6. Select the Meter Name from the Available Meter List. 7. Drag-and-drop the selected meter to the Selected Meter List. 8. Repeat for each meter. 9. Once all meters are selected, click Assign. The specified meters will be assigned to the selected configuration profile.
Removing a configuration profile

To remove a configuration profile from a meter: 1. From the Actions menu, select Element Configuration > Add/Remove Config Profile. The Add/Remove Configuration Profile form displays.
323
Figure 13-5.
2. From the drop list, select the Configuration Profile Type: REX2 Voltage Alarm Thresholds 120v REX2 Voltage Alarm Thresholds 240v REX2 Voltage Alarm Thresholds 480v REX2 Voltage Alarm Thresholds 600v
Note: If no configuration profiles are defined for the selected Configuration Profile Type the Configuration Profile Template drop list will be empty.
3. From the drop list, select the Configuration Profile Template. 4. Click Remove. The specified Configuration Profile is removed from EA_MS.
Reports
EA_MS includes the following reports for Element Configurations: View All Config Profiles Config Profies On Meter Meters On Config Profile
Viewing all configuration profiles

To view a report of all the configuration profiles defined in EA_MS: 1. From the Reports menu, select Element Configuration > View All Config Profiles. The View All Configuration Profiles report displays.
324
Figure 13-6.
2. Use the procedures described in Customizing a report layout on page 371 to customize the report.
Viewing configuration profiles on a meter

To view a report of all the configuration profiles defined in EA_MS: 1. From the Reports menu, select Element Configuration > Config Profiles On Meter. 2. Enter the Meter name in the text box. 3. Click Show Profiles to list all the profiles a meter is assigned. The Configuration Profiles On Meter report displays.
Figure 13-7.
Viewing meters on configuration profile

To view a report of all the configuration profiles defined in EA_MS: 1. From the Reports menu, select Element Configuration > Meters On Config Profile. The Meters On Configuration Profile report displays.
325
Figure 13-8.
2. Select the Profile Type from the drop list. 3. Select the Profile from the drop list. The Meters On Configuration Profile report displays.
Figure 13-9.
326
14. Reports
14
Reports
Reports
The Reports menu allows you access EA_MS the following operational reports: Communication Meter Communication Summary Report Gatekeeper LAN Protocol Report Residential Communication Associated Nodes Report for Gatekeeper Troubleshooting REX Meters: Unknown REX Meters Report Registered REX Meters Report Orphaned REX Meter Report Synchronization Summary Report Node Jumping History Report REX Communication Report Pending Synchronization Report LAN Information Report LAN Performance Threshold Network Capacity F/W Upgrade Firmware Version Summary report Firmware Upgrade Job Listing Report Firmware Upgrade History Report Firmware Upgrade Failure History
Audit User Audit Report CIS Import Audit Report Marriage File Import Audit Report
See Also
Meter View Meter Report on page 71 Meter List Report on page 168 Meter Readings Report on page 138 Meter Inventoried Report on page 164 Meter Installed Report on page 166 Meters Not Read Report on page 155 Meter Events Report on page 156 Meter Alarms Report on page 159 Meter Statuses Report on page 161 Component Mismatch Report on page 170 Meters Disconnected Report on page 170
327
14. Reports
HAN Home Area Network Events report on page 298 CTO listing on page 316 Assigned HAD listing on page 274 Unassigned HAD listing on page 275 Energy conservation event listing on page 313 Commissioned/Decommissioned reports on page 303 Elster Pricing reports on page 308 Emergency management reports on page 296 Messaging reports on page 287 Water Meter Viewing the unknown water nodes report on page 173 Viewing a gatekeepers water nodes report on page 175 Viewing a gatekeepers water meters reading history on page 177 Viewing the Water Interval Threshold report on page 178 Viewing the Water Leak report on page 180 Viewing a water meters readings on page 173 Gas Meter Viewing a gas meters readings on page 184 Viewing the unknown gas nodes report on page 186 Viewing a gatekeepers gas nodes report on page 188 Viewing a gatekeepers gas meters reading history on page 190 Schedule Viewing a list of all schedules on page 206 Using the Schedule Explorer on page 232 View Schedule Information Report on page 210 Performance Report on page 213 Voltage Reading Performance reports on page 221 Element Configuration Viewing all configuration profiles on page 323 Viewing configuration profiles on a meter on page 324 Viewing meters on configuration profile on page 324
Meter Communication Summary Report

Note: This action is available for A3 ALPHA meters and A3 ALPHA gatekeepers only. Communications initiated to a REX meter, A3 ALPHA node, or water meter will show as a communication session to its gatekeeper.
This report provides information about EA_MS-to-meter communication sessions, times, etc.
328
14. Reports
There are two options for communications reports available: summary option - a summarized report of all communications within a time range can be obtained by leaving the meter name as a wildcard specific meter option - a detailed report of communications to a particular meter (including individual sessions) can be obtained by selecting a specific meter name To view a report of meter communication: 1. From the Reports menu, select Communication > Meters. 2. From the Search for drop list, select one of the following options: Not LAN Nodes - default A3 ALPHA Meters Gatekeepers 3. For a specific meter, select a Meter Name by clicking the Search button; Or For a summary report, enter a wildcard (like % or *) to view a summary report of communications with all meters. 4. Enter the From and To dates and times.
Figure 14-1. Meter Communication Summary form

5. Click Submit to create the report. For the summary report, the Meter Communication Summary report displays all the communication information for all meters for the specified date and time range.
Figure 14-2. Meter Communication Summary report (%)
329
14. Reports
Figure 14-3. Meter Communication Summary report (comm. port summary)
Figure 14-4. Meter Communication Summary report (meter comm summary)
Figure 14-5. Meter Communication Summary report (meter comm detail)

If you specified a meter name, the Meter Communication Summary report displays the communication information for the selected meter for the specified date and time range. The table below describes the information displayed by the Meter Communication Summary report. Item Date Range Overall Communication Summary (summary report only) Description The From and To date and time range of communications specified for the report. Provides a summary, by Meter Type, of the following: Comm Mode, # of Success, # of Attempts, % Success, Dial Time, Comm Time, Total Session Time (including dial time), Avg Session Time (including dial time), Bytes Sent, and Bytes Received.
330
14. Reports
Item Communication Port Summary (summary report only)
Description Provides a summary, by Comm Port, of the following: Down time, Comm Mode, Comm Type (Comm Template), # of Success, # of Attempts, % Success, Dial Time, Comm Time, Total Session Time, Avg Session Time, Bytes Sent, and Bytes Received. For each meter, indicates Meter Name, Meter Type, Comm Mode, Comm Type (Comm Template), # of Success, # of Attempts, % Success, Dial Time, Comm Time, Total Session Time (including dial time), Avg Session Time (including dial time), Bytes Sent, and Bytes Received. Meter Name, Port No, (the port used for the call), Time Stamp (when the call was initiated), Read Reason (on request or schedule), Dial Time, Comm Time, Total Session Time, Bytes Sent, Bytes Received, and Error Message (if the reading failed).
Meter Comm Summary
Meter Comm Detail (single meter report only)
Note: A communication session is considered successful if EA_MS has connected to the meter.
The Communication Dashboard allows you to view charts and tables of meter communication summary information.
Figure 14-6. Communication Dashboard

Note: For E-WIC and W-WIC nodes and gatekeepers, the Success/Failed Packets always equals 0/0 (zero/zero) because WICs do not collect this data.
331
14. Reports
Gatekeeper LAN Protocol Report

To view a report of a gatekeepers LAN Protocol communications: 1. From the Reports menu, select Communications > LAN Communication. The Gatekeeper LAN Protocol Report form displays.
Figure 14-7. Gatekeeper LAN Protocol Report form

2. To find the gatekeeper for the report, enter either of the following: Meter Name Account Number Serial Number Or Click Search to pick the gatekeeper from a list.
332
14. Reports
Figure 14-8. Gatekeeper LAN Protocol Report

3. Select the specific gatekeeper from the list. 4. Click Submit. The Gatekeeper LAN Protocol Report displays the information for the selected gatekeeper.
Figure 14-9. Gatekeeper LAN Protocol Report

The table below describes the information displayed by the Gatekeeper LAN Protocol Report:
Item Gatekeeper
Description Indicates the Name for the selected gatekeeper; Firmware Detail expands to show details on the gatekeepers firmware version and revision. Indicates the Serial Number for the gatekeeper. Indicates whether LAN Mode 2 is enabled in the gatekeeper.
Serial Number LAN Mode 2 Enabled
333
14. Reports
Item All / True / False
Description Selecting from the drop list refreshes the list to show the gatekeepers with EA_LAN2 either Enabled (true) or Disabled (false) or All. Indicates whether a pending change to the gatekeepers LAN Mode 2 setting exists.
LAN2 Change Pending
Figure 14-10. Gatekeeper LAN Protocol Report - firmware version and revision
Associated Nodes Report for Gatekeeper

Note: This action is available for gatekeepers only.
This report lists all REX meters that are currently registered to the selected gatekeeper. Additionally, this report also shows information about the gatekeeper network configuration as well as the synchronization statuses. To keep this report as up-to-date as possible, information used to create this report is read during every communication session with the gatekeeper and the most recent values are stored by EA_MS.
Note: To get the most current state of the network, you may need to perform an on demand read from the gatekeeper.
To view a listing of all REX meters associated with a particular gatekeeper: 1. From the Reports menu, select Residential Communication > Associated Nodes. The Associated Nodes Report for Gatekeeper form displays.
334
14. Reports
Figure 14-11. Associated Nodes Report for Gatekeeper form

2. Click Search to locate the gatekeeper name. 3. Select the appropriate Gatekeeper Name from the listing.
Note: The listing is filtered to display only gatekeepers.

4. Click Submit to create the report The selected report displays.
335
14. Reports
Figure 14-12. Associated Nodes Report for Gatekeeper

The table below describes the information displayed by the Associated Nodes Report. Item For each REX meter listed Meter Name Meter Type LAN ID Serial Number Installation Date Registration Date Last Read Date Last Modified Date The Meter Name (hyperlink to Viewing a meters information) The Meter Type for the registered meter. The LAN ID for the meter. The meters Serial Number. The installation date and time. The date and time the node registered with the gatekeeper. The date and time the meters register readings were last read. The most recent date and time the meter was last modified for any purpose that would require a synchronization (such as changing the meter's TOU schedule, billing schedule etc.). Description
336
14. Reports
Item Requires Synchronization Pending Synchronization
Description Actions have occurred in EA_MS that require a synchronization to the gatekeeper. Indicates that a synchronization of a TOU schedule from the gatekeeper to the node is scheduled.
Clicking on the Gatekeeper LAN Summary tab displays the Gatekeeper LAN Summary report.
Figure 14-13. Associated Nodes - Gatekeeper LAN Summary

The Gatekeeper LAN Summary report displays the following information about the selected gatekeeper: Item Name Last Connect Date Description The Meter Name of the gatekeeper (hyperlink to Viewing a meters information). The date and time of most recent communication session with gatekeeper; indicative of the freshness of the report.
337
14. Reports
Item LAN Last Optimized
Description The last date and time that the local area network under the gatekeeper was optimized from EA_MS. Field will be blank if it was never optimized using the Optimizing a gatekeepers LAN command from EA_MS or if the qualification thresholds were never changed from factory defaults. The last date and time of the last change with synchronization implications made to gatekeeper (for example, addition/ deletion of TOU schedules, billing schedules etc. will affect this field). The number of nodes registered to the gatekeeper as reported by the gatekeeper.
Last Changed
# of Nodes
Note: This value may differ from what EA_MS reports as nodes associated with gatekeeper because EA_MS only reports a node as registered after the first register read of the node by the gatekeeper. Consequently, this may not be equal to the number of rows of registered nodes in the Associated Nodes Report for Gatekeeper.
# of One Way Nodes # of Repeaters
Reserved for future use.

The number or REX or A3 ALPHA nodes that are relaying meter data from downstream meters up to the gatekeeper. The date and time that the gatekeeper started its most recent scan/read of current TOU read of load profile data from its registered nodes respectively. The date and time that the gatekeeper completed its most recent scan/read of current TOU/read of load profile data from its registered nodes respectively. The date and time of the last synchronization to gatekeeper.
Start of Last Node Scan Last Meter Read Last Profile Read End of Last Node Scan Last Meter Read Last Profile Read Last Synchronization
Note: If this time stamp is earlier than the last changed synchronization, it implies that there are changes in the system that need to be synchronized to the gatekeeper (either through the next scheduled synchronization or an on request synchronization).
Gatekeeper Configuration Indicates current LAN configuration based on qualification thresholds (can be Unoptimized, Sparse, Dense or Normal).
Note: If this value is Unoptimized, it indicates that the network has not been optimized through EA_MS and the Last Optimized field will be blank.
Troubleshooting REX Meters

These reports apply to the residential network and provides information on the status of the REX nodes in the 900 MHz network.
338
14. Reports
To view a report of node registration status, unknown, orphaned, or registered nodes: 1. From the Reports menu, select Residential Communication > Troubleshooting REX Meters. 2. Select the type of report to create from the drop list: Unknown REX Meters (Unknown REX Meters Report) Orphaned REX Meters (Orphaned REX Meter Report) Registered REX Meters (Registered REX Meters Report) 3. If you selected: a. Unknown REX Meters or Registered REX Meters as the report type, enter the Meter Name of the gatekeeper; Or Enter a wildcard string (using % or *) and click Search to find a specific gatekeeper. Or Enter a wildcard string (using % or *) to view a list of all REX meters that are unknown or registered. b. For the Unknown REX Meters Report enter the From and To date and time. 4. Click Submit to view the report: Unknown REX Meters Report Registered REX Meters Report
Unknown REX Meters Report

This report lists the REX meters that were reported by a gatekeeper but whose marriage file has not yet been imported into EA_MS.
Figure 14-14. Unknown Node report - wildcard search

Note: The report displays every instance when the node was reported by the gatekeeper during the specified time range.
339
14. Reports
The table below describes the information displayed by the Unknown Node report. Item Gatekeeper Name Discovered At Unknown LAN ID Description The Meter Name for the gatekeeper (hyperlink to Viewing a meters information). The date and time the unknown node was discovered by EA_MS. The LAN ID for the unknown node.
Registered REX Meters Report

This report lists all REX and A3 ALPHA node meters that are registered to a gatekeeper but are not assigned to any schedule.
Note: The Registered Nodes Report displays only currently installed nodes that are registered to a gatekeeper but are not explicitly assigned to a collection schedule. Removed nodes that are in the process of unregistering in EA_MS will not be displayed.
Figure 14-15. Registered Node Report - wildcard search
Figure 14-16. Registered Node Report - specific gatekeeper

The table below describes the information displayed by the Registered Node report. Item for each A3 ALPHA gatekeeper Gatekeeper Name Last Read Date The Meter Name of the gatekeeper to which the meters are registered. The date and time the gatekeepers data readings were last read by EA_MS. Description
for each REX and A3 ALPHA node meter
340
14. Reports
Item Meter Name Type/Descriptor Serial Number Installation Date Node Registration Date Last Read Date Last Connect Date
Description The Meter Name for the REX meters (hyperlink to Viewing a meters information). The Meter Type of the meter. The meters Serial Number. The installation date and time. The date and time the node registered with the A3 ALPHA gatekeeper. The date and time the meters register readings were last read. The most recent date and time the meter was last communicated with for any purpose.
Orphaned REX Meter Report

This report lists all REX meters that are installed in EA_MS (with or without an Field Install Date) and are not registered to any gatekeeper as of the time the report was generated. A gatekeeper maintains a list of its registered nodes. Whenever EA_MS communicates with the gatekeeper, EA_MS reads this list and compares it with the list EA_MS has from the previous read. The nodes that are missing from the gatekeeper but they are in the EA_MS list are unregistered. These meters are reported as orphans and will be included in this list until EA_MS shows they have registered with a gatekeeper. The nodes that are in the gatekeepers registered nodes list but were not in EA_MS are newly registered. These meters will not be reported as orphans. To view the Orphaned REX Meter report: From the Reports > Residential Communication > Troubleshooting REX Meters > Orphan REX Meters. The Orphaned REX Meter Report displays.
341
14. Reports
Figure 14-17. Orphaned Nodes Report

The table below describes the information displayed by the Orphaned Node report. Item Meter Name Meter Type Serial Number Installation Date Orphaned As Of Description The Meter Name (hyperlink to Viewing a meters information). The Meter Type of meter (for example, REX/REX or A3_ILN/A3D). The meters Serial Number. The installation date and time. The date and time the node unregistered from the gatekeeper (if it was ever registered), that is, the time when EA_MS discovered that the node does not belong to that gatekeeper anymore. The date and time the meters register readings were last read. The most recent date and time the meter was last communicated with for any purpose. The LAN ID for the REX meter.
Last Read Date Last Connect Date LAN ID
342
14. Reports
Note: While the Associated Nodes Report for Gatekeeper will identify any nodes that are registered to gatekeepers that need synchronization, nodes that are orphaned but require synchronization are not identified in any specific report. Elster recommends that you verify that none of the nodes with configuration changes (such as assignment to a new TOU schedule) are in an orphaned state prior to making the next set of configuration changes. Ideally, the utility should troubleshoot and resolve issues with any nodes that show up as orphaned prior to making any configuration changes that affect that node.
Synchronization Summary Report

This report provides a summary of the configuration changes made in the system that require synchronizing the gatekeeper with EA_MS. The report consists of three parts: Synchronization Summary - a listing of all the gatekeepers in EA_MS and their respective synchronization states TOU Program - a listing of all the TOU schedules in EA_MS and their synchronization states Billing Schedule - a listing of all the billing schedules in EA_MS and their synchronization states To view the summary: 1. From the Reports menu, select Residential Communication > Synchronization Summary. The Synchronization Summary Report displays.
Figure 14-18. Synchronization Summary report - gatekeeper summary
343
14. Reports
Figure 14-19. Synchronization Summary report - TOU program summary
Figure 14-20. Synchronization Summary report - billing schedule summary

The table below describes the information displayed by the Synchronization Summary report. Item Gatekeeper Synchronization Summary Gatekeeper The Meter Name (hyperlink to Viewing a meters information). Description
344
14. Reports
Item Last Changed
Description The date and time of the last change to the gatekeeper having synchronization implications.
Note: Not all changes have synchronization implications.

Is on Synchronization Schedule Indicates if the gatekeeper is assigned to any synchronization schedule.
Note: Every gatekeeper should be on a synchronization schedule (that is, should be checked).
Last Synchronization Associated Nodes Requires Synchronization The last date and time the gatekeeper received a synchronization. Provides a hyperlink to the Associated Nodes Report for Gatekeeper report. Indicates if the Last Synchronization date and time is prior to the Last Changed date and time which implies that the gatekeeper needs a synchronization.
Note: The Requires Synchronization flag is not set if a node required synchronization. See Associated Nodes Report for Gatekeeper for a list of nodes requiring synchronization. Note: The Requires Synchronization flag of a Billing or TOU schedule will be cleared only if every gatekeeper in the system has been updated with the change.
TOU Program TOU Program Last Imported On The TOU Schedule name (hyperlink to View Schedule Information Report). The date and time that the TOU schedule was last imported in EA_MS (Actions > TOU > Importing TOU schedules). Indicates if any gatekeeper in the system requires a synchronization for this TOU schedule.
Requires Synchronization Billing Schedule Billing Schedule Modified On
The Schedule Name (hyperlink to View Schedule Information Report). The last date and time that the schedule was changed. This field is affected by the following: a user modifies a schedule that requires a synchronization to a gatekeeper (for example, changing the next execution date) execution of a billing schedule (to mark the next billing date as requiring synchronization to a gatekeeper) Indicates if any gatekeeper in the system requires a synchronization for this billing schedule.
Requires Synchronization
345
14. Reports
Node Jumping History Report

Meters functioning as nodes in a gatekeeper network have the ability to jump (that is, communicate through any gatekeeper within range of their radio). If a particular node loses its connection with the gatekeeper it is currently registered with, the node will attempt to reregister to the gatekeeper using a different repeater path or will attempt to register with a different gatekeeper. Typically the network is configured so that a node will look for an alternate path if it has not communicated with the gatekeeper in 18 hours. A history of frequent node jumps may be an indication of radio frequency holes in a particular area and may identify a need for additional gatekeepers. The Node Jumping History Report allows you to view the history of gatekeepers that a particular node registered to and unregistered from within a specified time range. The report indicates both registration and unregistration activity.
Note: There is no way to know the exact time a node unregistered from a gatekeeper therefore, the unregistration date is not indicated.
To view a report of a nodes jumping history: 1. From the Reports menu, select Residential Communication > Node Jumping History. The Node Jumping History form displays. 2. Select the Search for meter type (REX or A3_ILN) and click Search button. Or Select other criteria such as Account Number, Serial Number, etc. For a summary report, enter a wildcard (like % or *) to view registrations and unregistrations within the entire network. 3. Enter the From and To dates and times. Caution: Elster recommends using care when selecting From and To dates. Too wide a range may yield too much data that would lock up critical system resources; too small a range may not yield any data.
Figure 14-21. Node Jumping History form
346
14. Reports
4. Click Submit to create the report. The Node Jumping History report displays the jumping history for the selected REX meter node in chronological order.
Note: The report displays each date and time the node registered with a gatekeeper (whether the same or different). Consecutive registrations to the same gatekeeper may indicate re-registrations through alternate repeater paths. Note: Elster does not recommend using a search pattern that consists of wildcards only. For large system installations the returned results would be too large to easily select a meter.
Figure 14-22. Node Jumping History report

The table below describes the information displayed by the Node Jumping History report. Item Date Range Node Name Gatekeeper Name Activity Type Description The From and To dates and times for which the report was generated. The Meter Name for the REX or A3 ALPHA node (hyperlink to Viewing a meters information). The Meter Name for the gatekeeper (hyperlink to Viewing a meters information). Indicates whether the meter registered or unregistered from the gatekeeper.
347
14. Reports
Item Registration Date Detection Date
Description The date and time the node registered with the indicated A3 ALPHA gatekeeper. The date and time the registration/unregistration event was detected by EA_MS.
REX Communication Report

The REX Communication Report displays communication performance history for a specific REX meter or A3 ALPHA node for a specified date and time range. Information used in this report is read during every communication session with the gatekeeper and the most recent values are stored by EA_MS.
Note: You may need to do an on-demand read from the gatekeeper to get the most current state of the network.
This report is primarily intended as a diagnostic report to identify problems in communications that are likely to affect scheduled data collection. To view the most recent communication performance for a gatekeeper or a specific node, use the LAN Information Report. Typically a gatekeeper reads TOU data from the nodes 6 times per day1 (the default configuration) and also has retry algorithms configured to handle failed reads. These communication statistics indicate how often a gatekeeper is able to communicate with a node on a scheduled basis and are a predictor of expected performance on scheduled reads (such as the likelihood of getting data that meets freshness criteria for billing). To view a report of a nodes LAN performance: 1. From the Reports menu, select Residential Communication >REX Communication. The REX Communication Report form displays.
1. The number of read attempts is factory configurable and must be specified at the time of ordering.
348
14. Reports
Figure 14-23. REX Communication Report form

2. Select the Search for meter type (REX or A3_ILN) and click Search button. Or Select other criteria such as Account Number, Serial Number, etc. 3. Enter the From and To dates and times. 4. Click Submit to create the report. The REX Communication Report displays the success rate for the selected node.
349
14. Reports
Figure 14-24. REX Communication Report

The table below describes the information displayed by the REX Communication Report. Item Meter Name Type Serial Number LAN ID Gatekeeper Name Time Stamp Read Attempts Read Responses Success Rate % Description The Meter Name for the meter (hyperlink to Viewing a meters information). The Meter Type of the meter. The meters Serial Number. The LAN ID of the indicated meter. The Meter Name for all of the meters registered gatekeepers. The reading date and time. The number of times the A3 ALPHA gatekeeper attempted to read the node. The number of times the meter responded to the A3 ALPHA gatekeepers communication. The percentage of success for the meter to A3 ALPHA gatekeeper communications.
350
14. Reports
Pending Synchronization Report

The Pending Synchronization Report displays a listing of REX meters and A3 ALPHA nodes that have not received synchronized information from their registered gatekeeper. To view a report of a nodes or a gatekeepers pending synchronization: 1. From the Reports menu, select Residential Communication >Pending Synchronization. The Pending Synchronization Report form displays.
Figure 14-25. Pending Synchronization Report form

2. Enter the known information for the gatekeeper to be found. 3. Select the gatekeeper from the list. 4. Click Submit.
Figure 14-26. Pending Synchronization Report- single gatekeeper
351
14. Reports
The table below describes the information displayed by the Pending Synchronization Report. Item for the gatekeeper Gatekeeper Name The Meter Name for the indicated REX meters A3 ALPHA gatekeeper (hyperlink to Viewing a meters information). The orientation, Direction (meter), for the meter installation site. Indicates the number of meters below the specified node or gatekeeper. Date and time the gatekeeper started the last node scan. Date and time the gatekeeper completed the last node scan. The number of meters acting as repeaters at levels higher that the selected meter. Description
Direction Number of Descendents Last Read Start Time Last Read End Time Number of repeater descendents Most Recent LAN Performance Communication Path LAN Mode 2 Enabled for each node Meter Name
Indicated whether the gatekeeper is using EA_LAN or EA_LAN Mode 2.
The Meter Name for the meters that registered to the gatekeeper (hyperlink to Viewing a meters information). The orientation, Direction (meter), for the meter installation site. Indicates the meters level (that is, the repeater level from the gatekeeper). The number of meters at levels higher that the selected meter. Indicates the number of meters below the specified meter that are repeaters. Indicates the percent success rate for the most recent gatekeeper-to-meter communication. Date and time of the last TOU read by the gatekeeper. Indicates the repeaters Meter Name (maximum of eight) for each hop up to the gatekeeper.
Direction Node Level Number of Descendents Number of Repeater Descendents Most Recent LAN Performance Last TOU Read Date Time Communication Path
LAN Information Report

The LAN Information Report displays LAN information (that is, network configuration) either for a selected node or for all the nodes for a selected gatekeeper. This report provides a table of information about each nodes path, its number of descendants, number of repeater descendants, node levels, most recent communication performance etc. You can use this report not only to troubleshoot communications problems, but also to support network planning activities.
352
14. Reports
Information used in this report is read during every communication session with the gatekeeper and the most recent values are stored by EA_MS.
Note: You may need to do an on demand read from the gatekeeper to get the most current state of the network.
To view a report of a nodes or a gatekeepers LAN Information: 1. From the Reports menu, select Residential Communication > LAN Information. The LAN Information Report form displays. 2. Select the Search for meter type (REX or A3_ILN) and click Search button.
Figure 14-27. LAN Information form - Gatekeeper
Figure 14-28. LAN Information form - REX meter
353
14. Reports
3. Click Submit to create the report. The LAN Information Report - Gatekeeper displays the communication path and other network information for every node in its network.
Figure 14-29. LAN Information Report - Gatekeeper

The table below describes the information displayed by the LAN Information - Gatekeeper report. Item for the gatekeeper Gatekeeper Name The Meter Name for the indicated REX meters A3 ALPHA gatekeeper (hyperlink to Viewing a meters information). The orientation, Direction (meter), for the meter installation site. Indicates the number of meters below the specified node or gatekeeper. Date and time the last reading began. Indicates the number of meters below the specified node or gatekeeper that are repeaters. Date and time the last reading ended. Indicates the most recent LAN performance for the specified meter. Indicates the repeaters the specified meter uses to communicate with its registered gatekeeper. Clicking the magnifying glass - displays the LAN Visualizer. See the EnergyAxis LAN Visualizer (PG42-1024) for details on using the LAN Visualizer. LAN Mode 2 Enabled for each node Indicates whether the gatekeeper support EA_LAN or EA_LAN Mode 2. Description
Direction Number of Descendents Last Read Start Time Number of Repeater Descendents Last Read End Time Most Recent LAN Performance Communication Path
354
14. Reports
Item Meter Name
Description The Meter Name for the REX meters that registered to the A3 ALPHA gatekeeper (hyperlink to Viewing a meters information). Indicates the meters level (that is, the repeater level from the gatekeeper). Indicates the number of meters below the specified node or gatekeeper. Indicates the number of meters below the specified meter that are repeaters. Indicates the percent success rate for the most recent gatekeeper-to-meter communication. Date and time of the last TOU read by the gatekeeper. Indicates the repeaters Meter Name (maximum of eight) for each hop up to the gatekeeper.
Node Level Number of Descendents Number of Repeater Descendents Most Recent LAN Performance Last TOU Read Date Time Communication Path
The LAN Information Report displays the success rate for the selected node.
Figure 14-30. LAN Information Report - REX meter

The table below describes the information displayed by the LAN Information - REX report. Item Meter Name Node Level Direction Description The Meter Name for the REX meter (hyperlink to Viewing a meters information). Indicates the meters level (that is, the repeater level from the gatekeeper). The orientation, Direction (meter), for the meter installation site.
355
14. Reports
Item Number of Descendents Last TOU Read Date Time Number of Repeater Descendents Most Recent LAN Performance % Communication Path
Description Indicates the number of meters below the specified node or gatekeeper. Date and time of the last TOU read by the gatekeeper. Indicates the number of meters below the specified meter that are repeaters. The percentage of success for the REX meter to A3 ALPHA gatekeeper communications. Indicates the repeaters Meter Name (maximum of eight) for each hop up to the gatekeeper.
LAN Performance Threshold

the LAN Performance Threshold report shows the communication threshold information for the 900 MHz LAN. 1. From the Reports menu, select Residential Communication > LAN Performance Threshold. The LAN Performance Threshold form displays the current settings for the thresholds.
Figure 14-31. LAN Performance Threshold report

2. Click Submit. The LAN Performance Threshold report displays.
Figure 14-32. LAN Performance Threshold report
356
14. Reports
Network Capacity
The Network Capacity report provides an indication of how loaded the 900 MHz LAN is, and how gatekeepers are configured in terms of memory allocation amongst short format nodes, long format nodes, interval data entries, one-way nodes, etc. The information provided can be used in determining gatekeeper placement and configuration as well as node meter configuration to ensure network efficiency. 1. From the Reports menu, select Residential Communication > Network Capacity. The Network Capacity Report displays the Gatekeeper Status.
The Network Capacity Report Gatekeeper Status displays the following information: Item Gatekeepers Last Read Date Max Total # Nodes Used Total # Nodes Max # A3 ILN Nodes Used # A3 ILN Nodes Max # Water/Gas Nodes Used # Water/Gas Nodes Max # Repeaters # Repeaters Description The Meter Name for the gatekeeper meter (hyperlink to Viewing a meters information). The last date and time the gatekeeper was read. The capacity of the system to support nodes. The total number of nodes of the system. The capacity of the system to support A3 ALPHA nodes. The total number of A3 ALPHA nodes in the system. The capacity of the system to support water and gas meters. The total number of water and gas meters in the system. The capacity of the system to support repeaters. The total number of repeaters in the system.
357
14. Reports
User Audit Report

The User Audit report allows you to view your actions within a specified time range (default is past 7 days). The system administrator can generate the report for all users or a specific user. Additionally, EA_MS includes the following querying capabilities: ability to perform a regular expression search on an object name (such as a meter name, schedule name etc.) to report all the activities performed on objects matching the specified pattern ability to search for one or more user activity by selecting items from a list ability to include (or exclude) report activities in the audit report. By default they are excluded Each of the line item activities in the report can now be expanded to see the individual workitems and their statuses. While most of this information is intended for troubleshooting purposes and is of interest only to administrators and Elster personnel, the column Display Parameters lists the input parameters to the activity and would be of interest to all users. In addition, the Status field for each workitem displays any informational and /or error messages generated during the activity. To view a report of your EA_MS sessions: 1. From the Reports menu, select Audit > User Actions. The User Audit Report form displays.
Note: Because of the potentially large number of activities, Elster recommends that you narrow the search criteria as much as possible (for example, using Activity or Object criteria). Running the audit report without criteria may require a long time to create the report.
2. Select the User ID (User Logon) from the drop list (default is All). 3. Select the Status from the drop list (default is All). 4. Enter a search pattern for an Object name (for example, %<Meter>%). 5. From the listing, check the activities you wish to audit: Add New Meter Add New Schedule Assign/Remove Schedules to/from a Meter Associated Nodes Report Change User Password Connect REX Meter Define a Data Set Delete a Data Set Delete a Meter Delete a Schedule Meter Communication Summary Report Meter Events Report Meter Readings Report Meter Status Report Modify a Meter Modify a Schedule REX Communication Report Read Meter Time Read a Meter Registered Nodes Report
358
14. Reports
Display Meter Readings Edit User Account Exchange Schedules Exchange a TOU Schedule Import CIS File Import a Marriage File Import/Overwrite TOU Schedule Inventoried Meters Report LAN Information Report List of Meters Report List of Meters Report (Current) Meter Alarms Report
Remove a Meter Resubmit a Schedule Schedule Execution Summary Schedule Performance Report Schedule Readings Report Schedule Run List Report TOU Schedule Listing Report User Audit Report View Data Sets Report View Meter View Schedule Information Report View Schedules Report View TOU Schedule Report
6. Enter the From and To dates and times. 7. If desired, check to Include Reports (that is, to view a listing of all reports created within the specified parameters.
Figure 14-33. User Audit Report form

8. Click Submit to create the report. The User Audit report displays the selected users activities for the selected date range and status. The list is chronological and organized by user ID.
359
14. Reports
Figure 14-34. User Audit Report

The table below describes the information displayed by the User Audit report. Item for each user ID User Name Number of Tasks for each task Description Workflow ID State The activity attempted. The workflow ID for the activity. The completion state of the activity (Succeeded, Executing, Failed, Waiting to Execute, Waiting on User, or Waiting on System) The date and time the activity was initiated (in user local time). The date and time the activity was submitted to the system (in user local time). The date and time the activity completed (in user local time). The users full name. The total number of tasks found for this user. Description
Started Submitted Completed
360
14. Reports
Item Elapsed
Description The total number of hours, minutes, and seconds required to complete the activity (end time - start time). No. of workitems in the activity.
Count for each action (expanded) Activity State
The action attempted. The completion state of the activity (Succeeded, Executing, Failed, Waiting to Execute, Waiting on User, or Waiting on System) The date and time the activity completed. Indicates any status or error messages for the activity / workitem. The status of the last workitem will indicate final status of activity. The input parameters entered for the activity (varies according to the action).
Timestamp Status
Display Parameters
CIS Import Audit Report

The CIS Import Audit report allows administrators to view a list of all CIS file import actions (Meter >Importing a CIS file) that have occurred. Refer to the EA_MS AMRDEF Reference for details on the status and error reporting for the importing of CIS files. To view a report of all CIS importations: 1. From the Reports menu, select Audit > CIS Import. The CIS Import report lists all of the CIS files (most recent files listed first), the file size (bytes) and the date and time the file was last modified.
361
14. Reports
Figure 14-35. CIS Import report

2. Click on the path and file name of a CIS file to display the contents and results of the CIS Import action.
362
14. Reports
Figure 14-36. CIS Import Audit report

3. Click to expand an Import Action to view the parameters of the action or click to expand the Import Data Summary to view the results of the CIS Import File action (number of meters, success rate, etc.).
Note: The Result:Outcome indicates whether the action failed or succeeded.
363
14. Reports
Figure 14-37. CIS Import Audit report (expanded)
Marriage File Import Audit Report

The Marriage File Import Audit report allows administrators to view a list of all marriage file import actions (Meter >Importing a marriage file) that have occurred. To view a report of all marriage file importations: 1. From the Reports menu, select Audit > Marriage File Import. The Marriage File Import report lists all of the marriage files, the status (for example, fail-no meters imported, success-all meters imported, warning-not every meter imported) and the date and time the file was imported.
364
14. Reports
Figure 14-38. Marriage File Import report

2. Click on the path and file name of a marriage file to display the contents and results of the Marriage File Import action.
365
14. Reports
Figure 14-39. Marriage File Import Audit report - success
Figure 14-40.
366
14. Reports
Figure 14-41. Marriage File Import Audit report - failed
Firmware Version Summary report

The System Administrator has the ability to view Firmware Version Summary report that lists all firmware upgrade jobs. To view the Firmware Version Summary report: 1. From the Reports menu, select F/W Upgrade > Version Listing. The Firmware Version Summary report displays.
367
14. Reports
Figure 14-42. Firmware Version Summary report

The Firmware Version Summary report displays the following information: Item Firmware Image Type Description Lists the name of the firmware image file that is imported into EA_MS. For example, REX2 Meter 2.0 HW indicates the firmware is for the REX2 meter hardware. Indicates the firmware version.revision contained in the firmware image file. For example, 3.6 indicates a version 3 revision 6 firmware for the REX meter. Indicates the number of devices the specific firmware image file was used to upgrade.
Firmware Version/Revision
Device Count
Firmware Upgrade Job Listing Report

The System Administrator has the ability to view Firmware Upgrade Job Listing Report that lists all firmware upgrade jobs. To view the Firmware Version Summary report: 1. From the Reports menu, select F/W Upgrade > Job Summary. The Firmware Job Listing Report displays.
368
14. Reports
Figure 14-43. Firmware Upgrade Job Listing Report

The Firmware Upgrade Job Listing Report displays the following information: Item Name Device Type Firmware Version/Revision Description Indicates the name for the firmware upgrade job. Indicates the device type the upgrade job is intended for. Indicates the firmware version.revision contained in the firmware image file. For example, 3.6 indicates a version 3 revision 6 firmware for the REX meter. Indicates the state for the specified firmware upgrade job: Synchronization Pending Active Cancelled Cancel Pending Completed Indicates the date and time the state of the specified job was last updated.
State
State Update Time
Firmware Upgrade History Report

The System Administrator has the ability to view Firmware Upgrade History Report that lists all firmware upgrade jobs. To view the Firmware Version Summary report: 1. From the Reports menu, select F/W Upgrade > Upgrade History. The Firmware Upgrade History Report displays.
369
14. Reports
Figure 14-44. Firmware Upgrade History Report form

2. Select the From and To date range and times that the report should include. 3. From the Status drop list, select the job status to be included in the report: Synchronization Pending Active Cancelled Cancel Pending Completed 4. Click Submit.
Figure 14-45. Firmware Upgrade report

The Firmware Upgrade report displays the following information: Item Job Name Request Date Description Indicates the name for the firmware upgrade job. Indicates the date and time the job was created.
370
14. Reports
Item Device Type Version/Revision
Description Indicates the device type the upgrade job is intended for. Indicates the firmware version.revision contained in the firmware image file. For example, 3.6 indicates a version 3 revision 6 firmware for the REX meter. Indicates the number of devices the specific firmware image file was used to upgrade. Indicates the state for the specified firmware upgrade job: Download Pending Active Cancelled Cancel Pending Completed
Number of Devices Status
Firmware Upgrade Failure History

The System Administrator has the ability to view Firmware Upgrade Failure History report that lists all firmware upgrade jobs. To view the Firmware Upgrade Failure History report: 1. From the Reports menu, select F/W Upgrade > Upgrade Failure History. The Historical Firmware Upgrade Failures displays.
Figure 14-46. Historical Firmware Upgrade Failures Report form

2. Select the From and To date range and times that the report should include. 3. From the Gatekeeper drop list, select the gatekeeper whose failed register meters should be included in the report. 4. Click Submit. The Historical Firmware Upgrade Failures Report displays.
371
14. Reports
Figure 14-47. Historical Firmware Upgrade Failures Report

The Historical Firmware Upgrade Failures Report displays the following information: Item Job Name Gatekeeper Description Indicates the name for the firmware upgrade job. Indicates the name of the gatekeeper to which the failed device was registered at the time of the job run. Indicates the number of devices that failed to be upgraded by the firmware job.
Failure Count
Customizing a report layout

Some reports (those implemented using Flex) allow you to customize the report to allows ease of viewing specific data. These reports allow you to Using column selection for hiding unecessary data Using column data filters for viewing specific data
Using column selection

To customize the report to display a subset of columns: 1. On the report, select the column button, , located in the top right of the report (between the Export to Excel button and the Search button). The Select Columns dialog displays allowing you to check or uncheck the columns available for display.
372
14. Reports
Figure 14-48. Selecting columns to display

2. Check the columns to display. Or Uncheck the columns to hide. The customized report displays.
Figure 14-49. Home Area Network Events report (customized)
373
14. Reports
Using column data filters

To use a column data filter: 1. From the desired column to be filtered, click the funnel icon .
Figure 14-50. Entering filter criteria

2. Enter the data filter string (use * or X as wildcard). The table is filtered to display entries matching the data filter criteria.
Figure 14-51. Report filtered by criteria

Columns containing a data filter string appear with a red filter icon To remove a column data filter: 1. Click the red filter icon. 2. Delete the data filter string from the text box. The report displays without the column data filter. .
374
15. Administration
15
Administration
Administration
The Administration menu allows you to access the following user administrative actions: Users - System Administrators Only View All New Additional Actions (toolbar based) Users - System Administrators Only Deleting a User Creating a user based on another users profile Network - System Administrators Only Optimize LAN Other Administrators Security Administrator All Users Editing Your Account All Users Change Password View My Account
Viewing a list of all users

Note: This command is only available for system administrators.
System administrators are allowed to create, edit, and delete users, disabling and enabling users, changing passwords, deleting workitems from the Activity Monitor for any user, and viewing all users activities on the Activity Monitor. System Administrators are also allowed to perform operational and reporting actions available in EA_MS with the exception of those activities reserved for Security Administrator. To view a listing of all users: From the Administration menu, select Users > View All. The Users report displays a listing of all users and their associated privileges.
375
15. Administration
Figure 15-1. View All report

The table below describes the information displayed by the View All Users report. Item radio button Description Allows you to select the user logon in the list (for use with the Activity Monitors buttons). See Using buttons on page 48. The users User Logon. The First Name and Last Name of the user associated with this logon ID. The users employee ID. The security profile used to create this user logon (Meter Services, Billing and CIS Services, or Report Only User). Indicates whether the user logon is active or inactive. Indicates is LDAP login is enabled or disabled. The most recent date that the users logon Password was changed. The date the users logon Password is set to expire.
User Logon User Name Employee ID User Security Profile
Account Enabled Network Login Last Password Change Expiration Date
376
15. Administration
Changing a Users Information

1. From the View All report click the radio button for the User Logon you wish to change. 2. Click Edit. The Edit User form displays allowing you to edit the user information. See Adding a new user on page 376 for details on the items on the form. 3. Edit the user information as needed. 4. Click Submit to complete your changes.
Adding a new user

Any user created in EA_MS shows up as a User Template in the drop list on the Profile Information page. If you select a user template, the new user will have the same settings except security privileges (which must be explicitly selected for each individual user).
Note: EA_MS can be configured to use LDAP for user authentication allowing users to use their network logon ID to log in to EA_MS.
To add a new user: 1. From the Administration menu, select Users > New.
Note: Alternatively, from the View All Users report, from the User Actions toolbar, click Create to view the Create User form.
The Create User form displays a blank form.
Figure 15-2. Create User - User Information form

2. Enter the users User Logon (if you are using LDAP, you must enter the users network logon ID).
Note: The users EA_MS logon ID must match exactly the users network logon ID for LDAP authentication to work correctly.
3. Check Use Network Logon to enable user authentication by the LDAP server.
Note: If you are using LDAP for user authentication, the Password text box is not available.
377
15. Administration
4. If you are not using LDAP, enter the users Password. 5. Enter the users First Name. 6. Enter the users Middle Initial. 7. Enter the users Last Name. 8. Enter the users Employee ID. 9. Check Account Enabled to activate the user logon. 10.Enter the Days to Expire (if set to 0, the password will never expire). 11. Check those Companies for whom the user will perform actions. 12.Select the Profile Information page.
Figure 15-3. Create User - Profile Information form

13.Select the User Template.
Note: If you select a user template, the remaining parameters will be set to values defined in the user template; the only exception is security profile, which you must explicitly select.
14.Select the Default Company. 15.Select the users Time Zone (must be specified if no template is selected). 16.Enter the number of Items per Page (range of 1-30). 17. Enter Maximum Pages (must be specified if no template is selected; range of 1-10, default is 10). 18.Check to Show Time Zone in Time Stamp1 (default is unchecked). 19.Check to Show Time Stamp Offsets1 (for DST) (default is unchecked). 20.Select the Locale (must be specified if no template is selected; default is English (United States)). 21.Enter the Session Timeout (in minutes) (must be specified if no template is selected; range of 30-600; default is 120). Caution: If the users browser is set on the Activity Monitor the session will not time out because of the Activity Monitor Refresh Interval.
378
15. Administration
22.Enter the Dashboard Refresh Interval (in seconds) (must be specified if no template is selected; range 0 - 300 (0 = no refresh), default is 30). 23.Enter the Active Workitem Limit (range 1 - 100). 24.Select the User Security Profile (required). See User Profile Access on page 379 for details on user profile access.
Note: User Security Profile applies only to users that are not based on the AMR System Administrator AfterInstall User Template.
Figure 15-4. Create User - Dashboard form

25.Select the Dashboard page. 26.To configure Favorites, see Configuring EA_MS favorites list on page 61. 27.For Upcoming Schedules, enter the number of Days to Look Ahead. 28.For Dashboard Preferences, select the Default Tab (that is, the page the Dashboard displays after it refreshes): System Activities User Activities
379
15. Administration
Figure 15-5. Create User - Notifications form

29.Select the Notifications page. 30.To enable the user to receive email notifications: a. Enter the Email Address that is to receive the messages for the user. b. Check to Enable Meter Alarms Notifications sending to the email address. c. Check to Enable Schedule Completion Notifications sending to the email address. 31.Check those Event Categories to be monitored. 32.Click Submit to add the new user.
Note: The EA_MS System Administrator has the ability to enable and disable the notification for all users and must configure additional data to determine the mail server and authentication. See the EA_MS Installation and Administration Guide for details. Note: Schedule performance threshold value is configured by setting a registry entry. Refer to the EA_MS Installation and Administration Guide for details on configuring the threshold value.
User Profile Access

Report Only Billing and CIS User Services Level 1 Action Meter Level 2 Meter Services Level 3 System Admin Level 4 Security Admin Level 5
Menu
Action
380
15. Administration
Menu
Action
Report Only Billing and CIS User Services Level 1 Level 2 Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y
Meter Services Level 3 Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y
System Admin Level 4 Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y
Security Admin Level 5 N N N N N N N N N N N N N N N N N N N
View Modify Assign/ Remove Schedules New Remove Delete Ping On Request Read Read Time Read Configuration Set Meter Time Advanced Metering Functions Special Read for Billing Connect Service Disconnect Service Import Marriage File Import CIS File Import WIC Activation File Grouped Operations - Power Status Check Schedule View All Resubmit Modify Information Exchange New Delete Data Set View All New Exchange Delete TOU View All Exchange Import / Overwrite Delete Activity Monitor
Y N N N N N N N N N N N N N N N N N N
Y N N N N N
Y Y Y N Y N
Y Y Y Y Y Y
Y Y Y Y Y Y
N N N N N N
Y N N N
Y Y N N
Y Y Y Y
Y Y Y Y
N N N N
N N N N
Y N N N
Y Y Y Y
Y Y Y Y
N N N N
381
15. Administration
Menu
Action
Report Only Billing and CIS User Services Level 1 Level 2
Meter Services Level 3
System Admin Level 4
Security Admin Level 5
System Activities User Actions Y Limited to users activities N Y Limited to users activities N Y Limited to users activities Y Y All activities Y
Alarm Conditions
Reports Meter Listing Readings Inventoried Installed Not Read Events Alarms Statuses Component Mismatch Disconnected Schedule View All Communications Meter LAN Communication Residential Communications Associated Nodes Troubleshoot REX meters For all underlying options Unknown REX Meters Orphaned REX Meters Registered REX Meters Synchronization Summary Node Jumping History REX Communication Pending Synchronization LAN Information LAN Performance Threshold Network Capacity FW Upgrade Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y
382
15. Administration
Menu
Action
Report Only Billing and CIS User Services Level 1 Level 2 N N N N
Meter Services Level 3 N N N N
System Admin Level 4 N Y Y Y
Security Admin Level 5 N N N N
Version Listing Job Summary Upgrade History Upgrade Failure History
N N N N
Audit User Actions CIS Import Marriage File Import Administration Users View All New Delete Change Password View My Account Network Optimize LAN Security Console WAN Security - Actions Create Utility Delete Utility Create WAN Seed Delete WAN seed Set WAN Security for Device Create ACL Delete ACL Assign ACL to Device WAN Security - Reports Device Security Listing WAN Seed Listing Pending WAN Seed Changes Associated Devices for ACL Pending ACL synchronizations LAN Security - Actions Set LAN Security for Device N N N N Y N N N N N N N N N N N N N N N N N N N N Y Y Y Y Y N N N N N N N N N N N N N N N N N N N N N N N N N N N N N N N N Y Y Y Y Y Y Y Y N N Y Y N N N Y Y N N N Y Y N N N Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y
383
15. Administration
Menu
Action
Report Only Billing and CIS User Services Level 1 Level 2
Meter Services Level 3
System Admin Level 4
Security Admin Level 5
LAN Security - Reports LAN Security Listing N N N N Y
Changing a user password

Note: This option does not apply if EA_MS is using LDAP for user authentication. Note: This option is available to all EA_MS users.
To change your user logon password: 1. From the Administration menu, select Users > Change Password. The Change Password for User form displays a blank form.
Figure 15-6. Change Password for User form

2. Enter your Current Password. 3. Enter the New Password. 4. To Confirm the New Password, re-enter the new password. 5. Click Submit to change the password. The new password will take effect the next time you log on to EA_MS.
Viewing your account information

Note: This option is available to all EA_MS users.
To view your user account information: From the Administration menu, select Users > View My Account. The User Account form displays your information.
384
15. Administration
Figure 15-7. User Account User Information
Figure 15-8. User Account Profile Information
385
15. Administration
Figure 15-9. User Account Dashboard
Figure 15-10. SysAdmin Notifications
Editing Your Account

Each user may change the default settings on his user account. To change your settings: 1. From the Administration menu, select Users > View My Account. The User Account form displays your information. 2. From the User Actions toolbar, click Edit.
386
15. Administration
An Edit User form displays allowing you to make the necessary changes. See Adding a new user on page 376 for detailed information on user account settings. 3. After making your changes, click Submit to complete the action.
Deleting a User
To delete a user: 1. From the Administration menu, select Users > View All.
Figure 15-11. View all users report

2. Select the user to delete by clicking the radio button by the users Logon. 3. From the User Actions toolbar, click Delete. The selected user is deleted from EA_MS.
Creating a user based on another users profile

To create a new user using another users profile: 1. From the Administration menu, select Users > View All. A report displays all users by Logon. 2. Select the user to delete by clicking the radio button by the users Logon. 3. From the User Actions toolbar, click Copy. A new user form displays based on the selected users profile.
387
15. Administration
4. Edit the new user form as needed (for example, change the user name, etc.). 5. Click Submit to complete the action.
Security Administrator
In EA_MS, the Security Console allows the authorized Security Administrator to manage WAN (wide area network) and LAN (local area network) security. In EnergyAxis, WAN communications are controlled by the WAN interface card (WIC) in the gatekeeper and LAN communications are managed by the EA_LAN network interface card (EA_NIC). To ensure security at the WAN and LAN levels, EA_MS allows utilities to manage encryption (128-bit AES) at the WAN and the LAN level. Refer to the EA_MS Installation and Administration Guide for details on using the Security Console.
388
16. Network Management
16
Network Management
Optimizing a gatekeepers LAN

In addition to using the various reports created by EA_MS, administrators of the system can improve the LAN performance by using the Optimize LAN action.
Note: This action is available for A3 ALPHA gatekeepers only.

This action allows the system administrator to optimize a particular gatekeepers LAN. Execution of this action will unregister all nodes from the gatekeeper, sets the qualification threshold (that is, the percentage of successful transmissions with a node required for registration) appropriate to the selected configuration, and initiates a new full node scan. For example, an apartment complex would be expected to have a dense LAN configuration and a qualification threshold of 80% would be easily achieved. Areas with a less dense configuration that are configured with a threshold of 80% may not be able to register every node; however, with a threshold of 50%, the chances of every node being registered increases. Refer to the EA_MS Installation and Administration Guide, Ch. 7 Installing and Configuring the EA_MS Software for details on changing the default qualification threshold.
Note: The gatekeeper does not clear out its registration information or data for the nodes (that is, the count of registered nodes in the gatekeeper does not go to zero and then rebuild back up). The gatekeeper tells the nodes they are unregistered and does a node scan so the nodes can find a better communication path.
After executing this action, if a node re-registers to a different gatekeeper, it will still appear registered to the old gatekeeper. EA_MS will schedule an unregister for the old gatekeeper when it discovers the node on the new gatekeeper, but this action will not execute until the next synchronization schedule. This means that there is a brief period of time where two gatekeepers both think the meter is registered to them and EA_MS can read both gatekeepers. EA_MS compares the time stamp on the data to the most recent time stamp seen from that meter and will not report the data for the older reading. The correct data will be available in the data file. To optimize a gatekeepers LAN: 1. From the Administration menu, select Network > Optimize LAN. 2. Retrieve the particular gatekeeper. 3. Click Submit. The Optimize LAN for Gatekeeper displays the LAN configuration for the selected gatekeeper.
389
16. Network Management
Figure 16-1. Optimize LAN for Gatekeeper form

4. From the New LAN Configuration select the appropriate configuration (Sparse (50%), Intermediate (70%), or Dense (80%)). 5. Click Submit to begin the optimization.
390
A. Glossary
Glossary
1xRTT Also known as CDMA; a wireless communication standard for transmitting data. A3 ALPHA meter quality flags Individual intervals of load profile data are marked with quality flags that apply to that specific intervals reading. The table below shows what quality flags are used for A3 ALPHA load profile data. Most of the flags correspond exactly to status bits stored by the meter. Quality Flag PowerFail Description Supplied by the meter for each interval. The meter sets this bit in all intervals where the power either failed or was restored. EA_MS sets this flag for all intervals it inserts to fill the gap created by an outage at the meter. The meter can indicate that the meters clock was set forward or backward during the interval. EA_MS sets this flag if the meter reports that the clock was set forward or backward during the interval. Supplied by the meter for each interval. Supplied by the meter for each interval. Supplied by the meter for each interval. Supplied by the meter for each interval. Supplied by the meter for each interval. Supplied by the meter for each interval. Supplied by the meter for each interval. Supplied by the meter for each interval.
ChangedTime
Overflow DST ClockSetForward ClockSetBackward PartialInterval LongInterval SkippedInterval TestMode
A3 ALPHA meter event types See A3 ALPHA Meter Events on page 463. A3 ALPHA meter status types See A3 ALPHA Meter Statuses on page 459. A3 ALPHA meter ILN1 status types See A3 ALPHA meter with EA_NIC Statuses on page 473. A3 Firmware Revision The firmware revision (that is, minor release) number for the A3 ALPHA node. For example, 02.04 where 02 is the version and 04 is the revision. A3 Firmware Version The firmware version (that is, major release) number for the A3 ALPHA node. For example, 02.04 where 02 is the version and 04 is the revision. Account Enabled Indicates if the account is allowed to access EA_MS. Account Name Alphanumeric descriptor (maximum of 50 characters) to provide more information on an account number (for example, the customers name). Account No. Alphanumeric identifier for the customer at the meter installation site.
391
A. Glossary
Alternate Cost Delivered Alternative cost of energy consumed. Assignment Date The date and time the cancellation of the event is to go into effect. billing data Metered quantities used for billing. Billing Password Password (maximum of 20 characters) required for performing a billing read of a meter (as well as a demand reset and time synchronization). Billing Registers The measured quantities, tiers, units of measure, direction (delivered or received), and quadrants (Q1, Q2, Q3, Q4) collected by the specified meter. call in Indicates that the meter is configured to call into EA_MS. EA_MS cannot call meters configured as call in (that is, you cannot perform on request reads). call out Indicates that the meter is configured to receive calls from EA_MS. coincident The recording of a specified demand and power factor (if available) at the time of another specified maximum demand. For example, coincident kVAR Demand is the kVAR Demand occurring during the interval of maximum kW Demand. Comm Media Media use for communicating with the meter (for example, telephone, 900 MHz, etc.). Comm Mode Mode the meter uses for communicating with EA_MS (either call in or call out). Comm Number Telephone number, modem telephone number, IP address, etc. (maximum of 40 characters) or LAN ID (900 MHz network, etc.). Comm Template Template used to communicate with specified meter (std_phone, std_ip or cell_phone). commission Command to add a HAN device to the Trusted list of devices that are allowed to join a ZigBee network at a particular premise. CommunicationId Hexadecimal MAC address of the HAD device. CommunicationType Indicates the type of HAN communication used by the HAD device; valid values are ZigBee or EA 900MHz. communicative The meters communications option board is connected and capable of communicating. Companies List of companies for whom the user will perform EA_MS actions. CT Ratio Current transformer (CT) ratio; the ratio of the primary current to the secondary current of a current transformer. For example, 400A to 5A would have a current transformer ratio of 400:5 or 80:1. This value is programmable in the field by meter support software (not for REX meters), and it is used by the meter to convert instrumentation values to primary values. cumulative Increasing by successive additions. Used to describe a method for storing and display Demand data. For example, upon Demand reset, the present Maximum Demand is added to the sum of the previous maximum billing period Demand values. This technique provides a security feature indicating if unauthorized Demand resets have occurred. Customer Serial Number The serial number specified by the customer at order entry for the meter (may be the same number as the Utility Serial Number).
392
A. Glossary
Dashboard Refresh Interval The rate at which the Activity Monitor list refreshes; must be an integer between 0 and 60 seconds. Data Set Name String identifier for a data set (minimum length is 1 character and maximum length is 255); can consist of the following characters: 0-9, A-Z, a-z, -, _, . and spaces (leading and trailing spaces are not allowed). daylight saving time The practice of adjusting the clock one hour (forward in spring and backward in fall) to make better use of daylight hours. Also known as DST. Days to Expire The number of days that must pass before the logon password expires; must be an integer between 0 to 30 days. decommission Command to remove a HAN device from the Trusted list of devices that are allowed to join a ZigBee network at a particular premise. default path The default path is specified during system installation and configuration. Refer to the EA_MS Installation and Administration Guide for details. delivered Used to specify the energy delivered (provided) to an electric service. demand The average power (kWh) computed over a specific time. Demand Forgiveness Time The time during which demand is not calculated or stored after a power failure. The demand forgiveness is specified at the time of ordering and may be set to a number between zero (disabled) and 255 minutes. Demand Interval The time period over which Demand is calculated. Demand interval must be evenly divisible into 60 minutes. demand reset The act of resetting the present Maximum Demand to zero. demand reset count The total number of Demand resets since the meter was last programmed. demand reset date The date of the last Demand reset. Demand Subinterval Subintervals are used to calculate rolling demand and also contain an end of interval boundary. The demand interval must be evenly divisible by the demand subinterval. A maximum of 15 subintervals is allowed. The default value is 15 minutes. Block interval demand is calculated only if the subinterval size equals the interval size. Demand Threshold The present value of Demand which when reached initiates a relay closure or other programmed action. Description User determined description (maximum of 80 characters). DeviceClass Indicates the class of the HAD; valid values are: HVAC or Furnace, Strip Heat, Water Heater, Pool Pump/Spa/Jacuzzi, Smart Appliances, Irrigation Pump, Managed Loads, Simple Loads, Exterior Lighting, Interior Lighting, Electric Vehicle, and Generation Systems. DeviceName Device identifier for the HAD; consists of alphanumeric characters and period, hyphen and underscore characters. Device Number Device identifier for the meter; usually to designate the meter with the RS-485 option in modem sharing unit type installations.
393
A. Glossary
Dial Time Length of time to establish a communication connection with the meter. Direction (meter) Indicates the orientation in which the meter is installed: north, northeast, east, southeast, south, southwest, west, or northwest. Direction (metered quantity) Indicates the flow of electricity: delivered, received, etc. See also four quadrant metering. Disconnectable Indicates the presence of a service disconnect switch in the REX meter. DR Program Indicates the name for the program the utility uses to distinguish different residential pricing programs. DST See daylight saving time. Employee ID Employees unique identifier. End Period The date and time of the ending. Field Install Date The date (usually displayed in the user interface in the users time zone) the meter was installed in the field. Field Removal Date The date (usually displayed in the user interface in the users time zone) the meter was removed from the field. File Location Folder and filename for the file resulting from the scheduled readings. Firmware Revision The firmware revision of the meter. Firmware Version The firmware version of the meter. First Name Users first name. four quadrant metering The figure below illustrates energy relationships for delivered and received real power (kW), apparent power (kVA), and reactive power (kVAR).
394
A. Glossary
From and To The range of date-and-times in Month Day, Year HH:mm:ss AM/PM format. See Selecting a date and time on page 51. Gatekeeper Gatekeeper name to which the specified meter is registered. GPRS A mobile data communication standard for transmitting data wirelessly. interval data Also known as interval or load profiling, load profile records energy usage per a specific time interval while the meter is energized. Load profile data provides an interval-byinterval record of energy usage for each day of the tariff period. IsActive Indicates whether the device is active (1) or inactive (0). Kh A meter constant representing the watt-hours per output pulse on the optical port. Historically, Kh represents the energy equivalent to one revolution of an electromechanical meter. LAN Encryption Enabled Indicates whether C12.22 encryption is enabled (true or false) in the meter. LAN ID A unique number of up to ten digits (maximum value is 2147483647) used to identify meters in the 900 MHz network. This number is assigned to each meter at the time of manufacturing. Lan Level Indicates the number of hops to the meters registered gatekeeper. LAN Mode 2 Enabled Indicates whether LAN Mode 2 is enabled in the gatekeeper. LAN OB Revision The revision (that is, minor release) number for the internal LAN node option board (ILN1). For example, 255.12 where 255 is the version and 12 is the revision. LAN OB Version The version (that is, major release) number for the internal LAN node option board (ILN1). For example, 255.12 where 255 is the version and 12 is the revision. LAN Utility ID A unique number that identifies the network; this ID is unique to a customer. The number is assigned by Elster and prevents neighboring utilities from reading each other meters. Last Changed On Date and time the gatekeeper last synchronized with EA_MS. Last Connect Time Last time the meter was communicated with for any purpose. For REX meters, this is usually the same as the last read time. last logout time The date and time (in the format: since YYYY-MM-dd HH:mm:ss time zone) represented by last logout is calculated based on the last time you logged out of EA_MS before today. In the event that you allowed your login sessions to expire rather than manually logging out, the logout time will be based on the automatic expiration time of your session. The last logout date and time will only extend back for a maximum of three days. Last Name Users last name. Last Programmed Date and time the meter was last programmed using meter support software. Last Registered Date and time the meter last registered with the specified gatekeeper. Last Service Disconnect Indicates the date and time the service was last disconnected to this REX meter.
395
A. Glossary
LinkKeyAlgorithm Indicates the key algorithm used by the specified device; valid values are: Elster, SmartEnergy, ElsterRiga, and None. LP Interval Specifies the length of the profiling interval; zero (0) disables interval data recording. Load Profile Divisor The load profiling divisor (also known as Pulse Divisor) used to scale Kh pulses of the metered quantity (divisor is specified at the time of ordering). Locale Setting to determine localization parameters (such as, time and date display, currency, etc.). EA_MS only supports English (United States). MACAddress Address code for home area devices. Max Days for LP The maximum number of days of load profile data the meter can store before the data begins wrapping. Max Resubmits The number of times EA_MS will automatically resubmit a schedule if the schedule does not succeed the first time. Maximum Pages Must be an integer between 1 and 10. Measurement Period Indicates whether the period is: Period Current Previous Previous Season Current period Previous billing period, at time of last demand reset Previous season period, at time of last season change Description
Meter Name String identifier for meter (minimum length is 1 character and maximum length is 64); can consist of the following characters: 0-9, A-Z, a-z, -, _, . and spaces (leading and trailing spaces are not allowed). Meter Type The network type followed by a descriptor. For example, REX / REX designates a networked meter (that is, a REX-like meter) of type REX; REX / REX-D designates a REX meter with a service disconnect switch; A3_ILN / A3X designates a networked meter of type A3 ALPHA node; and A3 Gatekeeper designates the networked gatekeeper. Meter Reading The value of the data collected. Middle Initial Users middle initial (optional). Model The manufacturers full meter designation for a particular meter type (for example, A3RLQ) read from the meter and displayed in View Meter report. MSU Modem Sharing Unit. Net Delivered quantity Received quantity. Node A point of communication on a network (for example, REX meter on the 900MHz network). Node Gatekeeper Associations Report on nodes associated with the specified gatekeeper. Node Level Indicates the number of communication hops between the meter and its registered gatekeeper.
396
A. Glossary
nonrecurring dates Holidays or other special dates that do not occur on the same date every year or in a repeatable pattern (for example, Easter, Passover, or Eid ul-Fitr). Operating Territory Applies to EnergyAxis System which includes one or more A3 ALPHA gatekeepers and a proportionate number of REX meters are installed. These territories might coincide with regulatory agencies, geographical locations (network coverage), operation territory of utilities, etc. Orphan REX Meters Nodes that are not presently registered with a gatekeeper. Owner Name The name of the utility that owns the meter. Password Character string required to logon to EA_MS; must be a minimum of 5 characters. Performance Indicates the percentage of meters or gatekeepers on the schedule that successfully completed (includes resubmits). Priority A number between 1 - 64,000 where the higher the number the higher the priority. For example, a billing schedule with priority of 10 will be performed before a billing schedule with a priority of 1. program change date The date when the meter program was last changed. Pulse Divisor Also known as scaling factor or interval scaling factor; the divisor used to scale down interval-by-interval input pulses for storage in the meter. pulse ratio (P/R) The number of pulses per equivalent disk revolution; on Elster ALPHA meters, 1 revolution is equal to 1 Kh period. Radio Firmware Version The firmware version (that is, major release) number for the EA_NIC. For example, 02.60 where 02 is the version and 60 is the revision. Read Window Two digit time range (in seconds, minutes, hours, or days) measured from the schedule Start Time, that indicates how long after the start time that the schedule is allowed to attempt to read all meters associated with the schedule (that is, the time allotted for the schedule to initiate calls to its associated gatekeepers and meters). If this time is not specified, the schedule continues to try to read all associated meters until all retries have been exhausted or all meters have been read. Calls that have been initiated within the Read Window are permitted to remain open to completion or until they are terminated at the end of the systems configurable schedule termination window. No calls are permitted to be initiated outside of the Read Window. received Used to specify the energy received by the utility at an electric service. recurring dates Holidays or other special dates that occur on a the same date every year or in a repeatable pattern (for example, New Years Day); recurring days include season change days, and daylight saving time (DST) adjustment days. Registered REX Meters Nodes that are installed in the field and registered to gatekeepers but for which the work order information is not completed in the system yet (that is, the meter is not assigned to any schedule for data collection). Resubmit Frequency The length of time between schedule resubmits. Resubmit Threshold The percentage of meters assigned to the selected schedule that must be read before automatic resubmits will cease; default is 100%.
397
A. Glossary
Retry Count The total number of attempts EA_MS will make to read a meter for a session within the specified tolerance of the schedule. EA_MS will retry a session that has failed. Between each retry operation EA_MS will wait for the duration value of Retry Interval. Retry Interval The length of time between schedule submits. REX Firmware Version The firmware version (that is, major release) number for the REX or REX2 meter. For example, 02.04 where 02 is the version and 04 is the revision. REX meter event types See REX/REX2 Meter Events on page 469. REX meter quality flags Individual intervals of load profile data are marked with quality flags that apply to that specific intervals reading. The table below shows what quality flags are used for REX meter load profile data. Most of the flags correspond exactly to status bits stored by the meter. Quality Flag PowerFail Description Supplied by the meter for each interval. The meter sets this bit in all intervals where the power either failed or was restored. EA_MS sets this flag for all intervals it inserts to fill the gap created by an outage at the meter. The meter can indicate that the meters clock was set forward or backward during the interval. EA_MS sets this flag if the meter reports that the clock was set forward or backward during the interval. Supplied by the meter for each interval. Supplied by the meter for each interval. Supplied by the meter for each interval. Supplied by the meter for each interval.
ChangedTime
ClockSetForward ClockSetBackward PartialInterval LongInterval
REX meter status types See REX/REX2 Meter Statuses on page 467. Run Date Indicates the date and time the schedule started. Run Duration Specifies when a schedule stops running (this has nothing to do with tolerance). Run Duration applies to hourly and minute frequency period schedules only. Default value for this field is zero (indicates the schedule never stops running). Schedule Date Non-periodic (nonrecurring dates) dates for the schedules readings to be collected from the assigned meters. Schedule Dates Periodic (recurring dates) time frames for the schedules readings to be collected from the assigned meters. Schedule Name String identifier for a schedule (minimum length is 1 character and maximum length is 128); can consist of the following characters: 0-9, A-Z, a-z, -, _, . and spaces (leading and trailing spaces are not allowed). Schedule Run Duration Specifies the maximum length of time the schedule may run (in minutes in the range of 0 to 1440); default is 600 minutes.
398
A. Glossary
Schedule Type Either periodic (also known as recurring dates) or non-periodic (also known as nonrecurring dates). Serial Number Utility-specified identifier (maximum of 40 characters) configured at the time of meter manufacture; if no special requests were made at the time of manufacture, this number will be equal to the manufacturer serial number. For gatekeepers and A3 ALPHA meters this number corresponds to Site ID label #2 in Metercat. For REX, water and A3 ALPHA nodes this number is the customer serial number contained in the marriage file. Service Disconnect Status Indicates whether the service is currently connected or disconnected (per EA_MS) to the REX meter (Unknown, Disconnected, or Connected). Session Timeout The number of minutes of inactivity before the current session will expire; must be an integer between 30 and 7200 minutes. Show Time Stamp Offsets Indicates whether or not the hourly offset from GMT (for example, GMT-05:00 for the Eastern Time (US & Canada) is displayed as part of the time stamp. Show Time Zone in Time Stamp Indicates whether or not the time zone is displayed as part of the time stamp. Site ID Also known as service delivery point (SDP); identifies a location where service is provided; a unique, permanent number (maximum of 50 characters) used to facilitate communication of data in deregulated markets. Typically, it is assigned by a utility distribution company (UDC) at the socket level for customers that choose alternate energy suppliers. Site Location Descriptor (maximum of 80 characters) for location of the meter at a site. special characters Includes: ~, !, @, #, $, %, ^, &, *, (, ), _, +, =, -, <, >, ?,. Elster recommends that you not use | (pipe), \ (back slash), and / (forward slash) in identification numbers because they are reserved characters for most operating system. special dates Listing of defined recurring and nonrecurring dates. Stale Applies to readings. Status The workitems current state: Succeeded, Executing, Failed, Waiting Execution, Waiting System, or Waiting User. Style Number Style number of meter as originally built by manufacturer. Sum Delivered quantity + Received quantity. Tier Indicates whether the data was collected in Tier A, B, C, or D. Tier Label The label that appears on the home area device during the active Pricing. Tier Mapping Provides the link between the meters TOU rate and the price. timeofuse (TOU) A billing rate that records energy usage and demand data related to specific times during the day; may also use season changes and special dates (for example, holidays). Time stamp The date and time of the data. Time Zone MS Windows time zone in which the meter is installed (for example (GMT - 05:00) Eastern Time (US and Canada)).
399
A. Glossary
TOU Schedule Schedule name for time-of-use schedule. Unknown REX Meters Nodes that have never been associated with a gatekeeper since they were last installed. Unrestricted Password Password (maximum of 20 characters) required for programming a meter and making changes to a meters configuration, clearing logs, and entering test mode. UOM Unit of measure. User Logon Logon name for user. User Security Profile Consists of Meter Services, Billing and CIS Services, and Report Only User. User Template List of templates created during system configuration that define the standard preferences for users. VT Ratio Voltage transformer ratio; the ratio of primary voltage to secondary voltage of a transformer. For example, 12,000 V to 120 V would have a voltage transformer ratio of 100:1. This value is programmable in the field by meter support software (not for REX meters), and it is used by the meter to convert instrumentation values to primary values. This value is not used directly by the meter to compute energy values, but it is used to compute Adjusted Ke in primary metering applications. WAN seed Wide area network (WAN) data encryption method for generating secret encryption keys used for wireless security. WIC Wide area network (WAN) interface card (WIC); communications card found in the gatekeeper that allows it to communicate with EA_MS over WAN IP connections.
400
B. Sample Files
Sample Files
Warning:
The following files are provided for reference only. Refer to the most recent version of the EA_MS AMRDEF Reference for the most current version of the XML files.
Sample Marriage files Sample WIC activation file Example CIS files Warning: Do not use the contents of this appendix to create CIS import files for use with EA_MS. Refer to the most recent version of the EA_MS AMRDEF Reference for the most current version of the XML format.
Sample Marriage files

Note: These are sample files only.
REX meter
Marriage File Version 2.0 Metered Quantity,Kh,Demand Interval,Demand 1 Type,Demand 2 Type,Relay Divisor,Digits Displayed,Display Hold Time,Display LCD Test,Display Status,Display Voltage,Display Total kWh,Display Tier A kWh,Display Tier B kWh,Display Tier C kWh,Display Tier D kWh,Display Tier E kWh,Display Demand 1,Display Demand 2,Display Lan Registration Status,Display kWh Received,Send Outage Exc. Msg.,Send Restoration Exc. Msg.,Elster Serial Number,Customer Serial Number,Lan ID,Lan Utility ID,Style Number,Firmware Version,Firmware Revision,Demand Forgiveness Time,Demand Threshold,Demand Threshold Penalty,Service Disconnect Tripped When Dmd Threshold Exceeded,Load Profile Interval Length,Load Profile Divisor,Detect Switch Closed Error,Send Dmd Threshold Exc. Msg.,Send Node Scan Request Exc. Msg.,Send Load Side Voltage Set Exc. Msg.,Send Load Side Voltage Clear Exc. Msg. kWh sum (del + recvd),1,15,Total kW,Tier A kW,1,5,6,False,True,False,True,False,False,False,False,False,True,False,True,False,False,False,04748766,04 748766,0000003378,32 ,ZCC32A00000,2,0,0,9999.99,0,False,15,50,False,False,True,False,False kWh sum (del + recvd),1,15,Tier A kW,Total kW,1,5,6,False,True,False,True,False,False,False,False,False,True,False,True,False,False,False,04759580,04 759580,0000003440,32 ,ZCC32000000,2,0,0,9999.99,0,False,15,50,False,False,True,False,False
A3 ALPHA node
A3 Node Marriage File Version 1.0 Elster Serial Number,Customer Serial Number,LAN ID,LAN Utility ID,Style Number,A3 Meter Type,LANOB SSpec,LANOB Firmware Version,LANOB Firmware Revision,A3 SSpec,A3 Firmware Version,A3 Firmware Revision,Factory Ke,Demand 1 Type,Demand 2 Type,Send Outage Exc. Msg.,Send Restoration Exc. Msg.,Send Dmd Threshold Exc. Msg.,Send Node Scan Request Exc. Msg. 05217334,05217334,45280,89,ZAC32000000,A3Q,1,1,1,1,1,1,1,Tier C kW,Tier D kW,True,True,True,True
REX meter
Marriage File Version 1.0 Metered Quantity,Kh,Demand Interval,Demand 1 Type,Demand 2 Type,Relay Divisor,Digits Displayed,Display Time,Display LCD Test,Display Status,Display Voltage,Display Total kWh,Display Tier A kWh,Display Tier B kWh,Display Tier C kWh,Display Tier D kWh,Display Tier E kWh,Display Demand 1,Display Demand 2,Display Lan Registration Status,Display kWh Received,Send Outage Exc. Msg.,Send Restoration Exc. Msg.,Elster Serial Number,Customer Serial Number,Lan ID,Lan Utility ID,Style Number,Firmware Version,Firmware Revision,Demand Forgiveness Time,Demand Threshold,Demand Threshold Penalty,Service Disconnect Tripped When Dmd Threshold Exceeded,Load Profile Interval Length,Load Profile Divisor
401
B. Sample Files
kWh Delivered,1,15,Total kW,Total kW,1,5,6,False,True,False,True,False,False,False,False,False,True,False,True,False,False,False,04552664,04 552664,0000000989,1 ,ZCC32000000,255,100,0,9999.99,0,False,15,50
REX2-EA meter
Marriage File Version 3.0 Primary Energy Source,Kh,Demand Interval,Demand 1 Type,Demand 2 Type,Demand 3 Type,Relay Divisor,Digits Displayed,Display Hold Time,Display LCD Test,Display Status #1,Display Status #2,Display Status #3,Display Time and Rate,Display Primary Energy,Display Tier A Energy,Display Tier B Energy,Display Tier C Energy,Display Tier D Energy,Display Demand 1,Display Demand 2,Display Demand 3,Display Lan Registration Status,Display Secondary Energy,Display Meter FW Version,Display Radio FW Version,Display Instantaneous Demand,Send Outage Exc. Msg.,Send Restoration Exc. Msg.,Send Dmd Threshold Exc. Msg.,Send Node Scan Request Exc. Msg.,Send Reverse Energy Exc. Msg.,Send Table Access Exc. Msg.,Send Tilt Warning Exc. Msg,Send Demand Limit Lockout Exc. Msg,Elster Serial Number,Customer Serial Number,Lan ID,Lan Utility ID,Style Number,Meter Firmware Version,Meter Firmware Revision,Radio Firmware Version,Radio Firmware Revision,Demand Forgiveness Time,Demand Threshold,Demand Threshold Penalty,Load Profile Interval Length,Load Profile Divisor,Secondary Energy Source,Alternate Energy Selection,Demand Source,Num Demand Subintervals,Num Profile Channels,Max Momentary Outage Seconds,IHD Transmit Period,Power Restoration Tx Delay,Num Outage Timeslots,Num Outage Attempts,Reverse Energy Threshold,Enable Demand Limiting_Tier_A,Enable Demand Limiting_Tier_B,Enable Demand Limiting_Tier_C,Enable Demand Limiting_Tier_D,Demand Limit Lockout Count,Demand Limit Lockout Period,Minimum Voltage Threshold,Maximum Voltage Threshold,Minimum Voltage Duration,Maximum Voltage Duration,Voltage Snapshot Time kWh delivered,1.000,15,Total,Tier A,Tier C,1,5,5,True,True,True,True,False,True,False,False,False,False,True,False,False,True,False,False,False,Fal se,False,False,False,True,False,False,False,False,07693153,07693153,1458301,32,ZFCWJ000000,63,1C,FF,20,0,0 .00,0,60,10,kWh received,kVAh,kWh delivered,0,1,5,0,64,20,2,10,False,False,False,False,0,24,216,264,30,30,43200
Water module
EAWater Module Marriage File Version 1.0 Metered Quantity, Multiplier, Load Profile Divisor, Load Profile Interval, Digits Displayed, Elster Serial Number, Customer Serial Number, Manufacturer Module Serial Number, Customer Module Serial Number, Lan ID, LAN Utility ID, Water Company ID, Style Number, Firmware Version, Firmware Revision gallons,1,1,60,6,1800118,1800118,1800118,1800118,1800118,31,1,W000000,255,8
Gas module
EA Gas Module Marriage File Version 1.0 Gas Meter Serial Number,Gas Meter Model,Lan ID,LAN Utility ID,Firmware Version,Firmware Revision,Gas Module Serial Number,Gas Module Style Number,Predivisor,Pressure Compensation Numerator, Pressure Compensation Denominator,Interval Data Divisor,Interval Length,Unit of Measure,Snapshot Time,Module Mode,Multiplier,Digits Displayed,Gas Company ID, Customer Serial Number,GPS Latitude,GPS Longitude 74720286,1-ft Res - no PCF,74720286,89,255,54,74720286,1,50,1,1,20,60,CCF,01:00,Fixed Network,1.0,4,1,74720286,,
EA_Repeater
Marriage File Version 3.0 Primary Energy Source,Kh,Demand Interval,Demand 1 Type,Demand 2 Type,Demand 3 Type,Relay Divisor,Digits Displayed,Display Hold Time,Display LCD Test,Display Status #1,Display Status #2,Display Status #3,Display Time and Rate,Display Primary Energy,Display Tier A Energy,Display Tier B Energy,Display Tier C Energy,Display Tier D Energy,Display Demand 1,Display Demand 2,Display Demand 3,Display Lan Registration Status,Display Secondary Energy,Display Meter FW Version,Display Radio FW Version,Display Instantaneous Demand,Send Outage Exc. Msg.,Send Restoration Exc. Msg.,Send Dmd Threshold Exc. Msg.,Send Node Scan Request Exc. Msg.,Send Reverse Energy Exc. Msg.,Send Table Access Exc. Msg.,Send Tilt Warning Exc. Msg,Send Demand Limit Lockout Exc. Msg,Elster Serial Number,Customer Serial Number,Lan ID,Lan Utility ID,Style Number,Meter Firmware Version,Meter Firmware Revision,Radio Firmware Version,Radio Firmware Revision,Demand Forgiveness Time,Demand Threshold,Demand Threshold Penalty,Load Profile Interval Length,Load Profile Divisor,Secondary Energy Source,Alternate Energy Selection,Demand Source,Num Demand Subintervals,Num Profile Channels,Max Momentary Outage Time,IHD Transmit Period,Power Restoration Tx Delay,Num Outage Timeslots,Num Outage Attempts,Reverse Energy Threshold,Enable Demand Limiting_Tier_A,Enable Demand Limiting_Tier_B,Enable Demand Limiting_Tier_C,Enable Demand Limiting_Tier_D,Demand Limit Lockout Count,Demand Limit Lockout Period,Minimum Voltage Threshold,Maximum Voltage Threshold,Minimum Voltage Duration,Maximum Voltage
402
B. Sample Files
Duration,Voltage Snapshot Time kWh delivered,1.000,15,Total,Tier A,Tier B,1,5,5,True,False,False,False,False,True,False,False,False,False,False,False,False,True,False,False,False ,False,True,True,False,True,False,False,False,False,11232105,11232105,4061819,121,ZGA72000000,2,3,2,6,0,0. 000,0,60,10,kWh received,kVARh,kWh delivered,1,1,120,0,128,20,2,10,False,False,False,False,0,1,112.8,127.2,60,60,64800 kWh delivered,1.000,15,Total,Tier A,Tier B,1,5,5,True,False,False,False,False,True,False,False,False,False,False,False,False,True,False,False,False ,False,True,True,False,True,False,False,False,False,11232106,11232106,4061820,121,ZGA72000000,2,3,2,6,0,0. 000,0,60,10,kWh received,kVARh,kWh delivered,1,1,120,0,128,20,2,10,False,False,False,False,0,1,112.8,127.2,60,60,64800
Sample WIC activation file

<?xml version='1.0'?> <WIC_ACTIVATION_FILE> <VERSION>1</VERSION> <WIC> <ST5>10180594</ST5> <APTITLE>2.16.840.1.114223.156.5454</APTITLE> <UTILITY_ID>127</UTILITY_ID> <STYLENUMBER>ZA3F00</STYLENUMBER> <MFG_SERIAL_NUMBER>10180594</MFG_SERIAL_NUMBER> </WIC> </WIC_ACTIVATION_FILE>
Example CIS files

Example 1
<AMRDEF> <ImportDataInput> <Sequence>    <Task> <Meter MeterType="A3" SerialNumber="00021635" Overwrite="1" Owner="MASQA2" MeterName="KWA300021635"
404
B. Sample Files
SDPID="KWA300021635SI" AccountName="KWA300021635ANA" AccountNumber="KWA300021635ANU" BillingPassword="00000000000000000000" UnrestrictedPassword="00000000000000000000" SiteLocation="KWA300021635SL" Description="KWA300021635D" CommAddress="5649" CommMediaType="Telephone" CommTemplate="std_phone" CallMode="CallOut" DeviceNumber="1" OperatingTerritory="MASQA2" TimeZone="(GMT - 05:00) Eastern Time (US and Canada)" TimeZoneID="11" ObservesDST="1" Latitude="11.111" Longitude="-11.111" Direction="East" IsActive="1" InstallationDate="2009-03-01 01:01:01"/> </Task> <Task> <Meter MeterType="A3" SerialNumber="00021636" Overwrite="1" Owner="MASQA2" MeterName="KWA300021636" SDPID="KWA300021636SI" AccountName="KWA300021636ANA" AccountNumber="KWA300021636ANU" BillingPassword="00000000000000000000" UnrestrictedPassword="00000000000000000000" SiteLocation="KWA300021636SL" Description="KWA300021636D" CommAddress="5643" CommMediaType="Telephone" CommTemplate="std_phone" CallMode="CallOut" DeviceNumber="1" OperatingTerritory="MASQA2" TimeZone="(GMT - 05:00) Eastern Time (US and Canada)" TimeZoneID="11" ObservesDST="1" Latitude="11.111" Longitude="-11.111" Direction="East" IsActive="1" InstallationDate="2009-03-01 01:02:02"/> </Task>  <Task> <Meter MeterType="A3_Collector" SerialNumber="08813639" Overwrite="1" Owner="MASQA2" MeterName="KWA3C08813639" SDPID="KWA3C08813639SI" AccountName="KWA3C08813639ANA"
405
B. Sample Files
AccountNumber="KWA3C08813639ANU" BillingPassword="00000000000000000000" UnrestrictedPassword="00000000000000000000" SiteLocation="KWA3C08813639SL" Description="KWA3C08813639D" CommAddress="5657" CommMediaType="Telephone" CommTemplate="std_phone" CallMode="CallOut" DeviceNumber="1" OperatingTerritory="MASQA2" TimeZone="(GMT - 05:00) Eastern Time (US and Canada)" TimeZoneID="11" ObservesDST="1" Latitude="11.111" Longitude="-11.111" Direction="East" IsActive="1" InstallationDate="2009-03-01 01:03:03"/> </Task> <Task> <Meter MeterType="A3_Collector" SerialNumber="04836520" Overwrite="1" Owner="MASQA2" MeterName="KWA3C04836520" SDPID="KWA3C04836520SI" AccountName="KWA3C04836520ANA" AccountNumber="KWA3C04836520ANU" BillingPassword="00000000000000000000" UnrestrictedPassword="00000000000000000000" SiteLocation="KWA3C04836520SL" Description="KWA3C04836520D" CommAddress="5644" CommMediaType="Telephone" CommTemplate="std_phone" CallMode="CallOut" DeviceNumber="1" OperatingTerritory="MASQA2" TimeZone="(GMT - 05:00) Eastern Time (US and Canada)" TimeZoneID="11" ObservesDST="1" Latitude="12.222" Longitude="-12.222" Direction="East" IsActive="1" InstallationDate="2009-03-01 01:04:04"/> </Task>   <Task> <Meter MeterType="REX" SerialNumber="07316677" Overwrite="1" Owner="MASQA2" MeterName="KWREXD07316677" SDPID="KWREXD07316677SI" AccountName="KWREXD07316677ANA" AccountNumber="KWREXD07316677ANU" Description="KWREXD07316677D" SiteLocation="KWREXD07316677SL" Latitude="14.444" Longitude="-14.444" IsActive="1" Direction="East" TOUSchedule="Total Energy Only" InstallationDate="2009-03-01 01:07:07"/> </Task> <Task> <Meter MeterType="REX" SerialNumber="08609027" Overwrite="1" Owner="MASQA2" MeterName="KW2REXD08609027" SDPID="KW2REXD08609027SI" AccountName="KW2REXD08609027ANA" AccountNumber="KW2REXD08609027ANU" Description="KW2REXD08609027D" SiteLocation="KW2REXD08609027SL" Latitude="14.444" Longitude="-14.444" IsActive="1" Direction="East" TOUSchedule="Total Energy Only" InstallationDate="2009-03-01 01:08:08"/> </Task>  <Task> <Meter MeterType="REX" SerialNumber="04925545" Overwrite="1" Owner="MASQA2" MeterName="KWREX04925545" SDPID="KWREX04925545SI" AccountName="KWREX04925545ANA"
the Install Date of a Single the Customer Serial Number
Date for Five new REX Meters the Customer Serial Number
407 AccountNumber="KWREX04925545ANU" Description="KWREX04925545D" SiteLocation="KWREX04925545SL" Latitude="15.555" Longitude="-15.555" IsActive="1" Direction="East" TOUSchedule="Total Energy Only" InstallationDate="2009-03-01 01:09:09"/>
B. Sample Files
</Task> <Task> <Meter MeterType="REX" SerialNumber="04925546" Overwrite="1" Owner="MASQA2" MeterName="KWREX04925546" SDPID="KWREX04925546SI" AccountName="KWREX04925546ANA" AccountNumber="KWREX04925546ANU" Description="KWREX04925546D" SiteLocation="KWREX04925546SL" Latitude="16.666" Longitude="-16.666" IsActive="1" Direction="East" TOUSchedule="Total Energy Only" InstallationDate="2009-03-01 01:10:10"/> </Task> <Task> <Meter MeterType="REX" SerialNumber="07316682" Overwrite="1" Owner="MASQA2" MeterName="KWREX07316682" SDPID="KWREX07316682SI" AccountName="KWREX07316682ANA" AccountNumber="KWREX07316682ANU" Description="KWREX07316682D" SiteLocation="KWREX07316682SL" Latitude="16.666" Longitude="-16.666" IsActive="1" Direction="East" TOUSchedule="Total Energy Only" InstallationDate="2009-03-01 01:11:11"/> </Task>  <Task> <Meter MeterType="REX" SerialNumber="07671562" Overwrite="1" Owner="MASQA2" MeterName="KW2REX07671562" SDPID="KW2REX07671562SI" AccountName="KW2REX07671562ANA" AccountNumber="KW2REX07671562ANU" Description="KW2REX07671562D"
408 SiteLocation="KW2REX07671562SL" Latitude="16.666" Longitude="-16.666" IsActive="1" Direction="East" InstallationDate="2009-03-01 01:12:12"/>
B. Sample Files
</Task> <Task> <Meter MeterType="REX" SerialNumber="07693154" Overwrite="1" Owner="MASQA2" MeterName="KW2REX07693154" SDPID="KW2REX07693154SI" AccountName="KW2REX07693154ANA" AccountNumber="KW2REX07693154ANU" Description="KW2REX07693154D" SiteLocation="KW2REX07693154SL" Latitude="16.666" Longitude="-16.666" IsActive="1" Direction="East" InstallationDate="2009-03-01 01:13:13"/> </Task> <Task> <Meter MeterType="REX" SerialNumber="07972136" Overwrite="1" Owner="MASQA2" MeterName="KW2REX07972136" SDPID="KW2REX07972136SI" AccountName="KW2REX07972136ANA" AccountNumber="KW2REX07972136ANU" Description="KW2REX07972136D" SiteLocation="KW2REX07972136SL" Latitude="16.666" Longitude="-16.666" IsActive="1" Direction="East" InstallationDate="2009-03-01 01:14:14"/> </Task> <Task> <Meter MeterType="REX" SerialNumber="08302271" Overwrite="1" Owner="MASQA2" MeterName="KW2REX08302271" SDPID="KW2REX08302271SI" AccountName="KW2REX08302271ANA" AccountNumber="KW2REX08302271ANU" Description="KW2REX08302271D" SiteLocation="KW2REX08302271SL" Latitude="16.666" Longitude="-16.666" IsActive="1" Direction="East" InstallationDate="2009-03-01 01:15:15"/> </Task>  <Task> <Meter MeterType="EAWater" SerialNumber="01800065" Overwrite="1" Owner="MASQA2" MeterName="KWWATER01800065" SDPID="KWWATER01800065SI" AccountName="KWWATER01800065ANA" AccountNumber="KWWATER01800065ANU" Description="KWWATER01800065D" SiteLocation="KWWATER01800065SL" Latitude="17.777" Longitude="-17.777" IsActive="1" Direction="East" InstallationDate="2009-03-01 01:16:16"/> </Task> <Task> <Meter MeterType="EAWater" SerialNumber="73622040" Overwrite="1" Owner="MASQA2" MeterName="KWWATER73622040" SDPID="KWWATER73622040SI" AccountName="KWWATER73622040ANA" AccountNumber="KWWATER73622040ANU" Description="KWWATER73622040D" SiteLocation="KWWATER73622040SL" Latitude="17.777" Longitude="-17.777" IsActive="1" Direction="East" InstallationDate="2009-03-01 01:17:17"/> </Task> <Task> <Meter MeterType="EAWater" SerialNumber="73621701" Overwrite="1" Owner="MASQA2" MeterName="KWWATER73621701" SDPID="KWWATER73621701SI" AccountName="KWWATER73621701ANA" AccountNumber="KWWATER73621701ANU" Description="KWWATER73621701D" SiteLocation="KWWATER73621701SL" Latitude="17.777" Longitude="-17.777" IsActive="1" Direction="East" InstallationDate="2009-03-01 01:17:17"/> </Task>  <Task> <Meter MeterType="EAGas"
410 SerialNumber="3081803317" Overwrite="1" Owner="MASQA2" MeterName="KWGAS3081803317" SDPID="KWGAS3081803317SI" AccountName="KWGAS3081803317ANA" AccountNumber="KWGAS3081803317ANU" Description="KWGAS3081803317D" SiteLocation="KWGAS3081803317SL" Latitude="17.777" Longitude="-17.777" IsActive="1" Direction="East" InstallationDate="2009-03-01 01:18:18"/>
B. Sample Files
</Task> <Task> <Meter MeterType="EAGas" SerialNumber="8074720323" Overwrite="1" Owner="MASQA2" MeterName="KWGAS8074720323" SDPID="KWGAS8074720323SI" AccountName="KWGAS8074720323ANA" AccountNumber="KWGAS8074720323ANU" Description="KWGAS8074720323D" SiteLocation="KWGAS8074720323SL" Latitude="17.777" Longitude="-17.777" IsActive="1" Direction="East" InstallationDate="2009-03-01 01:19:19"/> </Task>  <Task> <DataSet Name="KW Registers Only" IsActive="1"> <Component Name="Registers"/> </DataSet> </Task> <Task> <DataSet Name="KW Load Profile Only" IsActive="1"> <Component Name="LoadProfile"/> </DataSet> </Task> <Task> <DataSet Name="KW Events and Exceptions Only" IsActive="1"> <Component Name="EventsandExceptions"/> </DataSet> </Task> <Task> <DataSet Name="KW Reset Events and Exceptions Only" IsActive="1"> <Component Name="ResetEventsandExceptions"/> </DataSet> </Task> <Task>
EA_MS Release 7.6 User Guide <DataSet
411
B. Sample Files
Name="KW LAN Performance Only" IsActive="1"> <Component Name="LANPerformance"/> </DataSet> </Task> <Task> <DataSet Name="KW Reset Communications statistics Only" IsActive="1"> <Component Name="ResetCommunicationstatistics"/> </DataSet> </Task> <Task> <DataSet Name="KW REX Registers from Collector Only" IsActive="1"> <Component Name="REXRegistersfromCollector"/> </DataSet> </Task> <Task> <DataSet Name="KW Water Registers From Collector Only" IsActive="1"> <Component Name="WaterRegistersFromCollector"/> </DataSet> </Task> <Task> <DataSet Name="KW Gas Registers From Collector Only" IsActive="1"> <Component Name="GasRegistersFromCollector"/> </DataSet> </Task> <Task> <DataSet Name="KW Load Profile from Collector Only" IsActive="1"> <Component Name="LoadProfilefromCollector"/> </DataSet> </Task> <Task> <DataSet Name="KW Demand Reset Only" IsActive="1"> <Component Name="DemandReset"/> </DataSet> </Task> <Task> <DataSet Name="KW A3ILN LP" IsActive="1"> <Component Name="DemandReset"/> <Component Name="LoadProfile"/> <Component Name="REXRegistersfromCollector"/> </DataSet> </Task> <Task> <DataSet Name="KW A3ILN" IsActive="1"> <Component Name="DemandReset"/> <Component Name="REXRegistersfromCollector"/>
EA_MS Release 7.6 User Guide </DataSet> </Task> <Task> <DataSet
412
B. Sample Files
Name="KW A3Meter LP" IsActive="1"> <Component Name="Registers"/> <Component Name="LoadProfile"/> <Component Name="EventsandExceptions"/> </DataSet> </Task> <Task> <DataSet Name="KW A3Meter" IsActive="1"> <Component Name="Registers"/> <Component Name="EventsandExceptions"/> </DataSet> </Task> <Task> <DataSet Name="KW REX LP" IsActive="1"> <Component Name="DemandReset"/> <Component Name="LoadProfilefromCollector"/> <Component Name="REXRegistersfromCollector"/> </DataSet> </Task> <Task> <DataSet Name="KW REX" IsActive="1"> <Component Name="DemandReset"/> <Component Name="REXRegistersfromCollector"/> </DataSet> </Task> <Task> <DataSet Name="KW A3Collector" IsActive="1"> <Component Name="DemandReset"/> <Component Name="EventsandExceptions"/> <Component Name="LANPerformance"/> <Component Name="REXRegistersfromCollector"/> <Component Name="WaterRegistersFromCollector"/> <Component Name="GasRegistersFromCollector"/> </DataSet> </Task>  <Task> <Schedule IsActive="1" Name="KW_PD_Schedule" TimeZoneId="11" ReadWindow="600" ReadWindowType="Seconds" StartTime="2009-03-10 04:15:00" UsedFor="Synchronization" Description="Daily Periodic Synchronization Schedule 1115 PM EST"> <PeriodicSchedule Length="1" Frequency="Days"/> </Schedule> </Task>
EA_MS Release 7.6 User Guide <Task> <Schedule
413
B. Sample Files
IsActive="1" Name="KW_Inactive_PD_Schedule" TimeZoneId="11" ReadWindow="600" ReadWindowType="Seconds" StartTime="2009-03-10 04:15:00" UsedFor="Synchronization" Description="Daily Periodic Synchronization Schedule 1115 PM EST"> <PeriodicSchedule Length="1" Frequency="Days"/> </Schedule> </Task> <Task> <Schedule IsActive="1" Name="KW_Terminated_PD_Schedule" TimeZoneId="11" ReadWindow="600" ReadWindowType="Seconds" StartTime="2009-03-10 04:15:00" UsedFor="Synchronization" Description="Terminated PD Schedule 1115 PM EST"> <PeriodicSchedule Length="1" Frequency="Days"/> </Schedule> </Task> <Task> <Schedule IsActive="0" Name="KW_Terminated_PD_Schedule" TimeZoneId="11" ReadWindow="600" ReadWindowType="Seconds" StartTime="2009-03-10 04:15:00" UsedFor="Synchronization" Description="Terminated PD Schedule 1115 PM EST"> <PeriodicSchedule Length="1" Frequency="Days"/> </Schedule> </Task> <Task> <Schedule IsActive="1" Name="KW_PB_Schedule" TimeZoneId="11" ReadWindow="600" ReadWindowType="Seconds" StartTime="2009-03-10 09:15:00" UsedFor="Billing" Description="Daily Periodic Billing Schedule 415 AM EST"> <PeriodicSchedule Length="1" Frequency="Days"/> </Schedule> </Task> <Task> <Schedule IsActive="1" Name="KW_Inactive_PB_Schedule" TimeZoneId="11" ReadWindow="600" ReadWindowType="Seconds" StartTime="2009-03-10 09:15:00" UsedFor="Billing" Description="Daily Periodic Billing Schedule 415 AM EST"> <PeriodicSchedule Length="1" Frequency="Days"/>
EA_MS Release 7.6 User Guide </Schedule> </Task> <Task> <Schedule
414
B. Sample Files
IsActive="1" Name="KW_Terminated_PB_Schedule" TimeZoneId="11" ReadWindow="600" ReadWindowType="Seconds" StartTime="2009-03-10 09:15:00" UsedFor="Billing" Description="Terminated PB Schedule 415 AM EST"> <PeriodicSchedule Length="1" Frequency="Days"/> </Schedule> </Task> <Task> <Schedule IsActive="0" Name="KW_Terminated_PB_Schedule" TimeZoneId="11" ReadWindow="600" ReadWindowType="Seconds" StartTime="2009-03-10 09:15:00" UsedFor="Billing" Description="Terminated PB Schedule 415 AM EST"> <PeriodicSchedule Length="1" Frequency="Days"/> </Schedule> </Task> <Task> <Schedule IsActive="1" Name="KW_PLP_Schedule" TimeZoneId="11" ReadWindow="600" ReadWindowType="Seconds" StartTime="2009-03-10 14:15:00" UsedFor="Billing" Description="Daily Periodic LP Schedule 915 AM EST"> <PeriodicSchedule Length="1" Frequency="Days"/> </Schedule> </Task> <Task> <Schedule IsActive="1" Name="KW_Inactive_PLP_Schedule" TimeZoneId="11" ReadWindow="600" ReadWindowType="Seconds" StartTime="2009-03-10 14:15:00" UsedFor="Billing" Description="Daily Periodic LP Schedule 915 AM EST"> <PeriodicSchedule Length="1" Frequency="Days"/> </Schedule> </Task> <Task> <Schedule IsActive="1" Name="KW_Terminated_PLP_Schedule" TimeZoneId="11" ReadWindow="600" ReadWindowType="Seconds" StartTime="2009-03-10 14:15:00" UsedFor="Billing"
415
B. Sample Files
Description="Terminated PLP Schedule 915 AM EST"> <PeriodicSchedule Length="1" Frequency="Days"/> </Schedule> </Task> <Task> <Schedule IsActive="0" Name="KW_Terminated_PLP_Schedule" TimeZoneId="11" ReadWindow="600" ReadWindowType="Seconds" StartTime="2009-03-10 14:15:00" UsedFor="Billing" Description="Terminated PLP Schedule 915 AM EST"> <PeriodicSchedule Length="1" Frequency="Days"/> </Schedule> </Task> <Task> <Schedule IsActive="1" Name="KW_PNB_Schedule" TimeZoneId="11" ReadWindow="600" ReadWindowType="Seconds" StartTime="2009-03-10 02:15:00" UsedFor="NotBilling" Description="Daily Periodic Non Billing Schedule 915 PM EST"> <PeriodicSchedule Length="1" Frequency="Days"/> </Schedule> </Task> <Task> <Schedule IsActive="1" Name="KW_Inactive_PNB_Schedule" TimeZoneId="11" ReadWindow="600" ReadWindowType="Seconds" StartTime="2009-03-10 02:15:00" UsedFor="NotBilling" Description="Daily Periodic Non Billing Schedule 915 PM EST"> <PeriodicSchedule Length="1" Frequency="Days"/> </Schedule> </Task> <Task> <Schedule IsActive="1" Name="KW_Terminated_PNB_Schedule" TimeZoneId="11" ReadWindow="600" ReadWindowType="Seconds" StartTime="2009-03-10 02:15:00" UsedFor="NotBilling" Description="Terminated PNB Schedule 915 PM EST"> <PeriodicSchedule Length="1" Frequency="Days"/> </Schedule> </Task> <Task> <Schedule IsActive="0" Name="KW_Terminated_PNB_Schedule" TimeZoneId="11" ReadWindow="600" ReadWindowType="Seconds"
416
B. Sample Files
StartTime="2009-03-10 02:15:00" UsedFor="NotBilling" Description="Terminated PNB Schedule 915 PM EST"> <PeriodicSchedule Length="1" Frequency="Days"/> </Schedule> </Task>  <Task> <Schedule IsActive="1" Name="KW_NPB_Schedule" TimeZoneId="11" ReadWindow="600" ReadWindowType="Seconds" StartTime="2009-03-10 19:15:00" UsedFor="Billing" Description="Non Periodic Billing Schedule 215 PM EST"> <ListSchedule> <ExecutionTime date="2009-03-10 20:15:31"/> <ExecutionTime date="2009-03-11 20:15:31"/> <ExecutionTime date="2009-03-12 20:15:31"/> <ExecutionTime date="2009-03-13 20:15:31"/> <ExecutionTime date="2009-03-14 20:15:31"/> </ListSchedule> </Schedule> </Task> <Task> <Schedule IsActive="1" Name="KW_Inactive_NPB_Schedule" TimeZoneId="11" ReadWindow="600" ReadWindowType="Seconds" StartTime="2009-03-10 19:15:00" UsedFor="Billing" Description="Non Periodic Billing Schedule 215 PM EST"> <ListSchedule> <ExecutionTime date="2009-03-10 20:15:31"/> <ExecutionTime date="2009-03-11 20:15:31"/> <ExecutionTime date="2009-03-12 20:15:31"/> <ExecutionTime date="2009-03-13 20:15:31"/> <ExecutionTime date="2009-03-14 20:15:31"/> </ListSchedule> </Schedule> </Task> <Task> <Schedule IsActive="1" Name="KW_Terminated_NPB_Schedule" TimeZoneId="11" ReadWindow="600" ReadWindowType="Seconds" StartTime="2009-03-10 19:15:00" UsedFor="Billing" Description="Terminated NPB Schedule 215 PM EST"> <ListSchedule> <ExecutionTime date="2009-03-10 20:15:31"/> <ExecutionTime date="2009-03-11 20:15:31"/> <ExecutionTime date="2009-03-12 20:15:31"/> <ExecutionTime date="2009-03-13 20:15:31"/> <ExecutionTime date="2009-03-14 20:15:31"/> </ListSchedule>
EA_MS Release 7.6 User Guide </Schedule> </Task> <Task> <Schedule
417
B. Sample Files
IsActive="0" Name="KW_Terminated_NPB_Schedule" TimeZoneId="11" ReadWindow="600" ReadWindowType="Seconds" StartTime="2009-03-10 19:15:00" UsedFor="Billing" Description="Terminated NPB Schedule 215 PM EST"> <ListSchedule> <ExecutionTime date="2009-03-10 20:15:31"/> <ExecutionTime date="2009-03-11 20:15:31"/> <ExecutionTime date="2009-03-12 20:15:31"/> <ExecutionTime date="2009-03-13 20:15:31"/> <ExecutionTime date="2009-03-14 20:15:31"/> </ListSchedule> </Schedule> </Task> <Task> <Schedule IsActive="1" Name="KW_NPNB_Schedule" TimeZoneId="11" ReadWindow="600" ReadWindowType="Seconds" StartTime="2009-03-10 23:15:00" UsedFor="NotBilling" Description="Non Periodic Non Billing Schedule <ListSchedule> <ExecutionTime date="2009-03-10 <ExecutionTime date="2009-03-11 <ExecutionTime date="2009-03-12 <ExecutionTime date="2009-03-13 <ExecutionTime date="2009-03-14 </ListSchedule> </Schedule> </Task> <Task> <Schedule IsActive="1" Name="KW_Inactive_NPNB_Schedule" TimeZoneId="11" ReadWindow="600" ReadWindowType="Seconds" StartTime="2009-03-10 23:15:00" UsedFor="NotBilling" Description="Non Periodic Non Billing Schedule <ListSchedule> <ExecutionTime date="2009-03-10 <ExecutionTime date="2009-03-11 <ExecutionTime date="2009-03-12 <ExecutionTime date="2009-03-13 <ExecutionTime date="2009-03-14 </ListSchedule> </Schedule> </Task> <Task> <Schedule IsActive="1" Name="KW_Terminated_NPNB_Schedule"
615 PM EST"> 20:15:31"/> 20:15:31"/> 20:15:31"/> 20:15:31"/> 20:15:31"/>
615 PM EST"> 20:15:31"/> 20:15:31"/> 20:15:31"/> 20:15:31"/> 20:15:31"/>
418
B. Sample Files
TimeZoneId="11" ReadWindow="600" ReadWindowType="Seconds" StartTime="2009-03-10 23:15:00" UsedFor="NotBilling" Description="Terminated NPNB Schedule 615 PM EST"> <ListSchedule> <ExecutionTime date="2009-03-10 20:15:31"/> <ExecutionTime date="2009-03-11 20:15:31"/> <ExecutionTime date="2009-03-12 20:15:31"/> <ExecutionTime date="2009-03-13 20:15:31"/> <ExecutionTime date="2009-03-14 20:15:31"/> </ListSchedule> </Schedule> </Task> <Task> <Schedule IsActive="0" Name="KW_Terminated_NPNB_Schedule" TimeZoneId="11" ReadWindow="600" ReadWindowType="Seconds" StartTime="2009-03-10 23:15:00" UsedFor="NotBilling" Description="Terminated NPNB Schedule 615 PM EST"> <ListSchedule> <ExecutionTime date="2009-03-10 20:15:31"/> <ExecutionTime date="2009-03-11 20:15:31"/> <ExecutionTime date="2009-03-12 20:15:31"/> <ExecutionTime date="2009-03-13 20:15:31"/> <ExecutionTime date="2009-03-14 20:15:31"/> </ListSchedule> </Schedule> </Task>   <Task> <ReadMeter NumReadAttempts="2" MeterName="KWA3C08813639" ReturnReadings="1"> <Component Name="Registers"/> <Component Name="EventsandExceptions"/> <Component Name="ResetEventsandExceptions"/> <Component Name="LANPerformance"/>
419
B. Sample Files
<Component Name="ResetCommunicationstatistics"/> <Component Name="REXRegistersfromCollector"/> <Component Name="WaterRegistersFromCollector"/> </ReadMeter> </Task> <Task> <ReadMeter NumReadAttempts="3" MeterName="KWA3C04836520" ReturnReadings="1"> <Component Name="Registers"/> <Component Name="EventsandExceptions"/> <Component Name="ResetEventsandExceptions" /> <Component Name="LANPerformance"/> <Component Name="ResetCommunicationstatistics"/> <Component Name="REXRegistersfromCollector"/> <Component Name="WaterRegistersFromCollector"/> </ReadMeter> </Task>     <Task> <Meter MeterType="A3" SerialNumber="00021635" Overwrite="1" Owner="MASQA2" MeterName="KWA300021635" SDPID="KWA300021635 at Telephone Pole" AccountName="KW300021635 ANA536120003" AccountNumber="KWA3000216355361ANU" BillingPassword="00000000000000000000" UnrestrictedPassword="00000000000000000000" SiteLocation="New Hope Road Raleigh NC" Description="KWA3 Meter with no 900mhz radio" CommAddress="5649" CommMediaType="Telephone" CommTemplate="std_phone" CallMode="CallOut" DeviceNumber="1" OperatingTerritory="MASQA2" TimeZone="(GMT - 05:00) Eastern Time (US and Canada)" TimeZoneID="11" ObservesDST="1" Latitude="11.111" Longitude="-11.111" Direction="East"
421 IsActive="1" InstallationDate="2009-03-01 01:01:01"/>
B. Sample Files
</Task> <Task> <Meter MeterType="A3" SerialNumber="00021636" Overwrite="1" Owner="MASQA2" MeterName="KWA300021636" SDPID="KWA300021636 at Light Pole" AccountName="KWA300021636 ANA636120003" AccountNumber="KWA3000216366361ANU" BillingPassword="00000000000000000000" UnrestrictedPassword="00000000000000000000" SiteLocation="Spring Forest Road Raleigh NC" Description="KWA3 Meter with no 900mhz radio" CommAddress="5643" CommMediaType="Telephone" CommTemplate="std_phone" CallMode="CallOut" DeviceNumber="1" OperatingTerritory="MASQA2" TimeZone="(GMT - 05:00) Eastern Time (US and Canada)" TimeZoneID="11" ObservesDST="1" Latitude="11.111" Longitude="-11.111" Direction="East" IsActive="1" InstallationDate="2009-03-01 01:02:02"/> </Task>  <Task> <Meter MeterType="A3_Collector" SerialNumber="08813639" Overwrite="1" Owner="MASQA2" MeterName="KWA3C08813639" SDPID="KWA3C08813639 at Utility Box" AccountName="KWA3C08813639 ANA93631880" AccountNumber="KWA3C088136399363ANU" BillingPassword="00000000000000000000" UnrestrictedPassword="00000000000000000000" SiteLocation="Main Street Raleigh NC" Description="KWA3 Collector modem based" CommAddress="5657" CommMediaType="Telephone" CommTemplate="std_phone" CallMode="CallOut" DeviceNumber="1" OperatingTerritory="MASQA2" TimeZone="(GMT - 05:00) Eastern Time (US and Canada)" TimeZoneID="11" ObservesDST="1" Latitude="11.111" Longitude="-11.111" Direction="East" IsActive="1" InstallationDate="2009-03-01 01:03:03"/> </Task> <Task>
EA_MS Release 7.6 User Guide <Meter
422
B. Sample Files
MeterType="A3_Collector" SerialNumber="04836520" Overwrite="1" Owner="MASQA2" MeterName="KWA3C04836520" SDPID="KWA3C04836520 at Garage" AccountName="KWA3C04836520 ANA02563840" AccountNumber="KWA3C048365200256ANU" BillingPassword="00000000000000000000" UnrestrictedPassword="00000000000000000000" SiteLocation="Garden Drive Raleigh NC" Description="KWA3 Collector modem based" CommAddress="5644" CommMediaType="Telephone" CommTemplate="std_phone" CallMode="CallOut" DeviceNumber="1" OperatingTerritory="MASQA2" TimeZone="(GMT - 05:00) Eastern Time (US and Canada)" TimeZoneID="11" ObservesDST="1" Latitude="12.222" Longitude="-12.222" Direction="East" IsActive="1" InstallationDate="2009-03-01 01:04:04"/> </Task>  <Task> <Meter MeterType="A3_ILN" SerialNumber="08450728" Overwrite="1" Owner="MASQA2" MeterName="KWA3ILN08450728" SDPID="KWA3ILN08450728 at Deck" AccountName="KWA3ILN08450728 ANA82705480" AccountNumber="KWA3ILN084507288270ANU" Description="KWA3 ILN Meter 900mhz" SiteLocation="Maple Avenue Raleigh NC" Latitude="13.333" Longitude="-13.333" IsActive="1" Direction="East" InstallationDate="2009-03-01 01:06:06"/> </Task>  <Task> <Meter MeterType="REX" SerialNumber="07316677" Overwrite="1" Owner="MASQA2" MeterName="KWREXD07316677" SDPID="KWREXD07316677 at Patio" AccountName="KWREXD07316677 ANA77661370" AccountNumber="KWREXD073166777766ANU" Description="KWREX Disconnect 900mhz" SiteLocation="Raleigh Boulevard Raleigh NC" Latitude="14.444" Longitude="-14.444" IsActive="1"
423 Direction="East" TOUSchedule="Total Energy Only" InstallationDate="2009-03-01 01:07:07"/>
B. Sample Files
</Task> <Task> <Meter MeterType="REX" SerialNumber="08609027" Overwrite="1" Owner="MASQA2" MeterName="KW2REXD08609027" SDPID="KW2REXD08609027 at Storage Building" AccountName="KW2REXD08609027 ANA72090680" AccountNumber="KW2REXD086090277209ANU" Description="KWREX2 Disconnect 900mhz" SiteLocation="Green Street Raleigh NC" Latitude="14.444" Longitude="-14.444" IsActive="1" Direction="East" TOUSchedule="Total Energy Only" InstallationDate="2009-03-01 01:08:08"/> </Task>  <Task> <Meter MeterType="REX" SerialNumber="04925545" Overwrite="1" Owner="MASQA2" MeterName="KWREX04925545" SDPID="KWREX04925545 at Telephone Pole" AccountName="KWREX04925545 ANA54552940" AccountNumber="KWREX049255455455ANU" Description="KWREX Meter 900mhz" SiteLocation="Hidden Trail Raleigh NC" Latitude="15.555" Longitude="-15.555" IsActive="1" Direction="East" TOUSchedule="Total Energy Only" InstallationDate="2009-03-01 01:09:09"/> </Task> <Task> <Meter MeterType="REX" SerialNumber="04925546" Overwrite="1" Owner="MASQA2" MeterName="KWREX04925546" SDPID="KWREX04925546 at Light Pole" AccountName="KWREX04925546 ANA64552940" AccountNumber="KWREX049255466455ANU" Description="KWREX Meter 900mhz" SiteLocation="Rosemont Drive Raleigh NC" Latitude="16.666" Longitude="-16.666" IsActive="1" Direction="East" TOUSchedule="Total Energy Only" InstallationDate="2009-03-01 01:10:10"/> </Task> <Task>
EA_MS Release 7.6 User Guide <Meter
424
B. Sample Files
MeterType="REX" SerialNumber="07316682" Overwrite="1" Owner="MASQA2" MeterName="KWREX07316682" SDPID="KWREX07316682 at Utility Box" AccountName="KWREX07316682 ANA28661370" AccountNumber="KWREX073166822866ANU" Description="KWREX Meter 900mhz" SiteLocation="Anderson Place Raleigh NC" Latitude="16.666" Longitude="-16.666" IsActive="1" Direction="East" TOUSchedule="Total Energy Only" InstallationDate="2009-03-01 01:11:11"/> </Task>  <Task> <Meter MeterType="REX" SerialNumber="07671562" Overwrite="1" Owner="MASQA2" MeterName="KW2REX07671562" SDPID="KW2REX07671562 at Garage" AccountName="KW2REX07671562 ANA26517670" AccountNumber="KW2REX076715622651ANU" Description="KWREX2 Meter 900mhz" SiteLocation="Historic Lane Raleigh NC" Latitude="16.666" Longitude="-16.666" IsActive="1" Direction="East" InstallationDate="2009-03-01 01:12:12"/> </Task> <Task> <Meter MeterType="REX" SerialNumber="07693154" Overwrite="1" Owner="MASQA2" MeterName="KW2REX07693154" SDPID="KW2REX07693154 in Deck" AccountName="KW2REX07693154 ANA45139670" AccountNumber="KW2REX076931544513ANU" Description="KWREX2 Meter 900mhz" SiteLocation="Joyful Hill Raleigh NC" Latitude="16.666" Longitude="-16.666" IsActive="1" Direction="East" InstallationDate="2009-03-01 01:13:13"/> </Task> <Task> <Meter MeterType="REX" SerialNumber="07972136" Overwrite="1" Owner="MASQA2" MeterName="KW2REX07972136" SDPID="KW2REX07972136 at Patio"
425 AccountName="KW2REX07972136 ANA63127970" AccountNumber="KW2REX079721366312ANU" Description="KWREX2 Meter with ZOB 900mhz" SiteLocation="Dream Court Raleigh NC" Latitude="16.666" Longitude="-16.666" IsActive="1" Direction="East" InstallationDate="2009-03-01 01:14:14"/>
B. Sample Files
</Task> <Task> <Meter MeterType="REX" SerialNumber="08302271" Overwrite="1" Owner="MASQA2" MeterName="KW2REX08302271" SDPID="KW2REX08302271 at Storage Building" AccountName="KW2REX08302271 ANA17220380" AccountNumber="KW2REX083022711722ANU" Description="KWREX2 Meter with ZOB 900mhz" SiteLocation="Township Way Raleigh NC" Latitude="16.666" Longitude="-16.666" IsActive="1" Direction="East" InstallationDate="2009-03-01 01:15:15"/> </Task>  <Task> <Meter MeterType="EAWater" SerialNumber="01800065" Overwrite="1" Owner="MASQA2" MeterName="KWWATER01800065" SDPID="KWWATER01800065 at Telephone Pole" AccountName="KWWATER01800065 ANA56000810" AccountNumber="KWWATER018000655600ANU" Description="KWWATER Module 900mhz" SiteLocation="Front Street Raleigh NC" Latitude="17.777" Longitude="-17.777" IsActive="1" Direction="East" InstallationDate="2009-03-01 01:16:16"/> </Task> <Task> <Meter MeterType="EAWater" SerialNumber="73622040" Overwrite="1" Owner="MASQA2" MeterName="KWWATER73622040" SDPID="KWWATER73622040 at Light Pole" AccountName="KWWATER73622040 ANA04022637" AccountNumber="KWWATER736220400402ANU" Description="KWWATER Module 900mhz" SiteLocation="White Oak Drive Raleigh NC" Latitude="17.777" Longitude="-17.777" IsActive="1" Direction="East"
426 InstallationDate="2009-03-01 01:17:17"/>
B. Sample Files
</Task> <Task> <Meter MeterType="EAWater" SerialNumber="73621701" Overwrite="1" Owner="MASQA2" MeterName="KWWATER73621701" SDPID="KWWATER73621701 at Utility Box" AccountName="KWWATER73621701 ANA10712637" AccountNumber="KWWATER736217011071ANU" Description="KWWATER Module 900mhz" SiteLocation="Linville Lane Raleigh NC" Latitude="17.777" Longitude="-17.777" IsActive="1" Direction="East" InstallationDate="2009-03-01 01:18:18"/> </Task>  <Task> <Meter MeterType="EAGas" SerialNumber="3081803317" Overwrite="1" Owner="MASQA2" MeterName="KWGAS3081803317" SDPID="KWGAS3081803317 at Garage" AccountName="KWGAS3081803317 ANA7133081803" AccountNumber="KWGAS30818033177133ANU" Description="KWGAS Module 900mhz" SiteLocation="Escape Drive Raleigh NC" Latitude="17.777" Longitude="-17.777" IsActive="1" Direction="East" InstallationDate="2009-03-01 01:19:19"/> </Task> <Task> <Meter MeterType="EAGas" SerialNumber="8074720323" Overwrite="1" Owner="MASQA2" MeterName="KWGAS8074720323" SDPID="KWGAS8074720323 at Deck" AccountName="KWGAS8074720323 ANA3230274708" AccountNumber="KWGAS80747203233230ANU" Description="KWGAS Module 900mhz" SiteLocation="Home Court Raleigh NC" Latitude="17.777" Longitude="-17.777" IsActive="1" Direction="East" InstallationDate="2009-03-01 01:20:20"/> </Task>  <Task> <Meter MeterType="REX" SerialNumber="07316677"
427 Overwrite="1" Owner="MASQA2" MeterName="KWREXD07316677" AccountName="KWREXD07316677 ANA77661370" AccountNumber="KWREXD07316677766ANU" Description="KWREX Disconnect 900mhz" Latitude="14.444" Longitude="-14.444" IsActive="1" Direction="East" TOUSchedule="KW TOU Schedule" InstallationDate="2009-03-01 01:21:21"/>
B. Sample Files
</Task>  <Task> <Meter MeterType="REX" SerialNumber="04925545" Overwrite="1" Owner="MASQA2" MeterName="KWREX04925545" AccountName="KWREX04925545 ANA54552940" AccountNumber="KWREX049255455455ANU" Description="KWREX Meter 900mhz" Latitude="15.555" Longitude="-15.555" IsActive="1" Direction="East" TOUSchedule="KW TOU Schedule" InstallationDate="2009-03-01 01:22:22"/> </Task> <Task> <Meter MeterType="REX" SerialNumber="04925546" Overwrite="1" Owner="MASQA2" MeterName="KWREX04925546" AccountName="KWREX04925546 ANA64552940" AccountNumber="KWREX049255466455ANU" Description="KWREX Meter 900mhz" Latitude="16.666" Longitude="-16.666" IsActive="1" Direction="East" TOUSchedule="KW TOU Schedule" InstallationDate="2009-03-01 01:23:23"/> </Task> <Task> <Meter MeterType="REX" SerialNumber="07316682" Overwrite="1" Owner="MASQA2" MeterName="KWREX07316682" AccountName="KWREX07316682 ANA28661370" AccountNumber="KWREX073166822866ANU" Description="KWREX Meter 900mhz" Latitude="16.666" Longitude="-16.666" IsActive="1" Direction="East"
428 TOUSchedule="KW TOU Schedule" InstallationDate="2009-03-01 01:24:24"/>
B. Sample Files
</Task> <Task> <Meter MeterType="REX" SerialNumber="07671562" Overwrite="1" Owner="MASQA2" MeterName="KW2REX07671562" AccountName="KW2REX07671562 ANA26517670" AccountNumber="KW2REX076715622651ANU" Description="KWREX2 Meter 900mhz" Latitude="16.666" Longitude="-16.666" IsActive="1" Direction="East" TOUSchedule="KW TOU Schedule" InstallationDate="2009-03-01 01:25:25"/> </Task> <Task> <Meter MeterType="REX" SerialNumber="07693154" Overwrite="1" Owner="MASQA2" MeterName="KW2REX07693154" AccountName="KW2REX07693154 ANA45139670" AccountNumber="KW2REX076931544513ANU" Description="KWREX2 Meter 900mhz" Latitude="16.666" Longitude="-16.666" IsActive="1" Direction="East" TOUSchedule="KW TOU Schedule" InstallationDate="2009-03-01 01:26:26"/> </Task> <Task> <Meter MeterType="REX" SerialNumber="07972136" Overwrite="1" Owner="MASQA2" MeterName="KW2REX07972136" AccountName="KW2REX07972136 ANA63127970" AccountNumber="KW2REX079721366312ANU" Description="KWREX2 Meter with ZOB 900mhz" Latitude="16.666" Longitude="-16.666" IsActive="1" Direction="East" TOUSchedule="KW TOU Schedule" InstallationDate="2009-03-01 01:27:27"/> </Task> <Task> <Meter MeterType="REX" SerialNumber="08302271" Overwrite="1" Owner="MASQA2" MeterName="KW2REX08302271" AccountName="KW2REX08302271 ANA17220380" AccountNumber="KW2REX083022711722ANU"
429 Description="KWREX2 Meter with ZOB 900mhz" Latitude="16.666" Longitude="-16.666" IsActive="1" Direction="East" TOUSchedule="KW TOU Schedule" InstallationDate="2009-03-01 01:27:27"/>
B. Sample Files
</Task>  <Task> <MeterBilling MeterName="KWA3C08813639" IsActive="1" Schedule="KW_PD_Schedule" ComponentGroup="KW A3Collector"/> </Task> <Task> <MeterBilling MeterName="KWA3C04836520" IsActive="1" Schedule="KW_PD_Schedule" ComponentGroup="KW A3Collector"/> </Task>  <Task> <MeterBilling MeterName="KWA3C08813639" IsActive="1" Schedule="KW_PB_Schedule" ComponentGroup="KW A3Collector"/> </Task> <Task> <MeterBilling MeterName="KWREX04925545" IsActive="1" Schedule="KW_PB_Schedule" ComponentGroup="KW REX"/> </Task> <Task> <MeterBilling MeterName="KW2REX07671562" IsActive="1" Schedule="KW_PB_Schedule" ComponentGroup="KW REX"/> </Task> <Task> <MeterBilling MeterName="KW2REX07693154" IsActive="1" Schedule="KW_PB_Schedule" ComponentGroup="KW REX"/> </Task> <Task> <MeterBilling MeterName="KWA300021635" IsActive="1" Schedule="KW_PB_Schedule" ComponentGroup="KW A3Meter"/> </Task> 
EA_MS Release 7.6 User Guide <Task> <MeterBilling
430
B. Sample Files
MeterName="KWA3C08813639" IsActive="1" Schedule="KW_PLP_Schedule" ComponentGroup="KW A3Collector"/> </Task> <Task> <MeterBilling MeterName="KWREX07316682" IsActive="1" Schedule="KW_PLP_Schedule" ComponentGroup="KW REX LP"/> </Task> <Task> <MeterBilling MeterName="KW2REX08302271" IsActive="1" Schedule="KW_PLP_Schedule" ComponentGroup="KW REX LP"/> </Task> <Task> <MeterBilling MeterName="KW2REXD08609027" IsActive="1" Schedule="KW_PLP_Schedule" ComponentGroup="KW REX LP"/> <!-</Task> <Task> <MeterBilling MeterName="KWA3ILN08450728" IsActive="1" Schedule="KW_PLP_Schedule" ComponentGroup="KW A3ILN LP"/> </Task>--> <Task> <MeterBilling MeterName="KWA3C04836520" IsActive="1" Schedule="KW_PLP_Schedule" ComponentGroup="KW Registers Only"/> </Task> <Task> <MeterBilling MeterName="KWA300021636" IsActive="1" Schedule="KW_PLP_Schedule" ComponentGroup="KW A3Meter LP"/> </Task>  <Task> <MeterBilling MeterName="KWREX04925546" IsActive="1" Schedule="KW_NPB_Schedule" ComponentGroup="KW REX"/> </Task> <Task> <MeterBilling MeterName="KW2REX07972136" IsActive="1" Schedule="KW_NPB_Schedule"
431 ComponentGroup="KW REX"/>
B. Sample Files
</Task> <Task> <MeterBilling MeterName="KWREXD07316677" IsActive="1" Schedule="KW_NPB_Schedule" ComponentGroup="KW REX"/> </Task>  <Task> <MeterBilling MeterName="KWA3C04836520" IsActive="1" Schedule="KW_NPNB_Schedule" ComponentGroup="KW A3Meter"/> </Task> <Task> <MeterBilling MeterName="KWA3C08813639" IsActive="1" Schedule="KW_NPNB_Schedule" ComponentGroup="KW A3Collector"/> </Task> <Task> <MeterBilling MeterName="KWREX04925545" IsActive="1" Schedule="KW_NPNB_Schedule" ComponentGroup="KW REX"/> </Task> <Task> <MeterBilling MeterName="KWREX04925546" IsActive="1" Schedule="KW_NPNB_Schedule" ComponentGroup="KW REX"/> </Task> <Task> <MeterBilling MeterName="KWREX07316682" IsActive="1" Schedule="KW_NPNB_Schedule" ComponentGroup="KW REX"/> </Task> <Task> <MeterBilling MeterName="KW2REX07671562" IsActive="1" Schedule="KW_NPNB_Schedule" ComponentGroup="KW REX"/> </Task> <Task> <MeterBilling MeterName="KW2REX07693154" IsActive="1" Schedule="KW_NPNB_Schedule" ComponentGroup="KW REX"/> </Task> <Task> <MeterBilling MeterName="KW2REX07972136"
432 IsActive="1" Schedule="KW_NPNB_Schedule" ComponentGroup="KW REX"/>
B. Sample Files
</Task> <Task> <MeterBilling MeterName="KW2REX08302271" IsActive="1" Schedule="KW_NPNB_Schedule" ComponentGroup="KW REX"/> </Task> <Task> <MeterBilling MeterName="KW2REXD08609027" IsActive="1" Schedule="KW_NPNB_Schedule" ComponentGroup="KW REX"/> </Task> <Task> <MeterBilling MeterName="KWREXD07316677" IsActive="1" Schedule="KW_NPNB_Schedule" ComponentGroup="KW REX"/> <!-</Task> <Task> <MeterBilling MeterName="KWA3ILN08450728" IsActive="1" Schedule="KW_NPNB_Schedule" ComponentGroup="KW A3ILN"/> </Task>--> <Task> <MeterBilling MeterName="KWA300021635" IsActive="1" Schedule="KW_NPNB_Schedule" ComponentGroup="KW A3Meter"/> </Task> <Task> <MeterBilling MeterName="KWA300021636" IsActive="1" Schedule="KW_NPNB_Schedule" ComponentGroup="KW A3Meter"/> </Task>  <Task> <MeterBilling MeterName="KWA3C04836520" IsActive="1" Schedule="KW_PNB_Schedule" ComponentGroup="KW A3Meter"/> </Task> <Task> <MeterBilling MeterName="KWA3C08813639" IsActive="1" Schedule="KW_PNB_Schedule" ComponentGroup="KW A3Collector"/> </Task> <Task>
EA_MS Release 7.6 User Guide <MeterBilling
433
B. Sample Files
MeterName="KWREX04925545" IsActive="1" Schedule="KW_PNB_Schedule" ComponentGroup="KW REX"/> </Task> <Task> <MeterBilling MeterName="KWREX04925546" IsActive="1" Schedule="KW_PNB_Schedule" ComponentGroup="KW REX"/> </Task> <Task> <MeterBilling MeterName="KWREX07316682" IsActive="1" Schedule="KW_PNB_Schedule" ComponentGroup="KW REX"/> </Task> <Task> <MeterBilling MeterName="KW2REX07671562" IsActive="1" Schedule="KW_PNB_Schedule" ComponentGroup="KW REX"/> </Task> <Task> <MeterBilling MeterName="KW2REX07693154" IsActive="1" Schedule="KW_PNB_Schedule" ComponentGroup="KW REX"/> </Task> <Task> <MeterBilling MeterName="KW2REX07972136" IsActive="1" Schedule="KW_PNB_Schedule" ComponentGroup="KW REX"/> </Task> <Task> <MeterBilling MeterName="KW2REX08302271" IsActive="1" Schedule="KW_PNB_Schedule" ComponentGroup="KW REX"/> </Task> <Task> <MeterBilling MeterName="KW2REXD08609027" IsActive="1" Schedule="KW_PNB_Schedule" ComponentGroup="KW REX"/> </Task> <Task> <MeterBilling MeterName="KWREXD07316677" IsActive="1" Schedule="KW_PNB_Schedule" ComponentGroup="KW REX"/> <!-</Task> <Task>
EA_MS Release 7.6 User Guide <MeterBilling
434
B. Sample Files
MeterName="KWA3ILN08450728" IsActive="1" Schedule="KW_PNB_Schedule" ComponentGroup="KW A3ILN"/> </Task>--> <Task> <MeterBilling MeterName="KWA300021635" IsActive="1" Schedule="KW_PNB_Schedule" ComponentGroup="KW A3Meter"/> </Task> <Task> <MeterBilling MeterName="KWA300021636" IsActive="1" Schedule="KW_PNB_Schedule" ComponentGroup="KW A3Meter"/> </Task>  <Task> <EnergyConservation Name="KW_EC_1" > <TierConfig Tier="A" CoolingOffset="2" HeatingOffset="2" DutyCyclePercentage="50" TransmitToEndDevice="1" AllowCustomerOverride="0" IsIncrementingOffset="0" IsCriticalPeakTier="1" MessageId="0"/> <TierConfig Tier="B" CoolingOffset="2" HeatingOffset="2" TransmitToEndDevice="1" AllowCustomerOverride="0" IsIncrementingOffset="0" IsCriticalPeakTier="0" MessageId="0"/> <TierConfig Tier="C" TransmitToEndDevice="1" AllowCustomerOverride="0" IsIncrementingOffset="0" IsCriticalPeakTier="0" MessageId="0"/> <TierConfig Tier="D" CoolingOffset="2" HeatingOffset="2" AverageLoadAdjustmentPercentage="0" DutyCyclePercentage="50" TransmitToEndDevice="1" AllowCustomerOverride="0" IsIncrementingOffset="0" IsCriticalPeakTier="0" MessageId="0"/> <DeviceClass Name="HVAC or Furnace"/>
435 <DeviceClass Name="Pool Pump/Spa/Jacuzzi"/> </EnergyConservation>
B. Sample Files
</Task> <Task> <EnergyConservation Name="KW_EC_2" > <TierConfig Tier="A" CoolingOffset="2" HeatingOffset="2" AverageLoadAdjustmentPercentage="50" TransmitToEndDevice="1" AllowCustomerOverride="1" IsIncrementingOffset="0" IsCriticalPeakTier="1" MessageId="0"/> <TierConfig Tier="B" CoolingOffset="2" HeatingOffset="2" TransmitToEndDevice="1" AllowCustomerOverride="1" IsIncrementingOffset="0" IsCriticalPeakTier="0" MessageId="0"/> <TierConfig Tier="C" TransmitToEndDevice="1" AllowCustomerOverride="1" IsIncrementingOffset="0" IsCriticalPeakTier="0" MessageId="0"/> <TierConfig Tier="D" CoolingOffset="2" HeatingOffset="2" AverageLoadAdjustmentPercentage="0" DutyCyclePercentage="50" TransmitToEndDevice="1" AllowCustomerOverride="1" IsIncrementingOffset="0" IsCriticalPeakTier="0" MessageId="0"/> <DeviceClass Name="HVAC or Furnace"/> <DeviceClass Name="Pool Pump/Spa/Jacuzzi"/> </EnergyConservation> </Task> <Task> <EnergyConservation Name="KW_EC_3" > <TierConfig Tier="A" CoolingOffset="2" HeatingOffset="2" DutyCyclePercentage="50" AverageLoadAdjustmentPercentage="25" TransmitToEndDevice="1" AllowCustomerOverride="0" IsIncrementingOffset="0" IsCriticalPeakTier="1" MessageId="0"/> <TierConfig Tier="B"
436 CoolingOffset="2" HeatingOffset="2" TransmitToEndDevice="1" AllowCustomerOverride="0" IsIncrementingOffset="0" IsCriticalPeakTier="0" MessageId="0"/> <TierConfig Tier="C" TransmitToEndDevice="1" AllowCustomerOverride="0" IsIncrementingOffset="0" IsCriticalPeakTier="0" MessageId="0"/> <TierConfig Tier="D" CoolingOffset="2" HeatingOffset="2" AverageLoadAdjustmentPercentage="50" DutyCyclePercentage="50" TransmitToEndDevice="1" AllowCustomerOverride="0" IsIncrementingOffset="0" IsCriticalPeakTier="0" MessageId="0"/> <DeviceClass Name="HVAC or Furnace"/> <DeviceClass Name="Strip Heat"/> <DeviceClass Name="Water Heater"/> <DeviceClass Name="Pool Pump/Spa/Jacuzzi"/> <DeviceClass Name="Smart Appliances"/> <DeviceClass Name="Irrigation Pump"/> <DeviceClass Name="Managed Loads"/> <DeviceClass Name="Simple Loads"/> <DeviceClass Name="Exterior Lighting"/> <DeviceClass Name="Interior Lighting"/> <DeviceClass Name="Electric Vehicle"/> <DeviceClass Name="Generation Systems"/> </EnergyConservation>
B. Sample Files
</Task> <Task> <EnergyConservation Name="KW_EC_4" > <TierConfig Tier="A" CoolingOffset="2" HeatingOffset="2" DutyCyclePercentage="50" AverageLoadAdjustmentPercentage="0" TransmitToEndDevice="1" AllowCustomerOverride="0" IsIncrementingOffset="0" IsCriticalPeakTier="1" MessageId="0"/> <TierConfig Tier="B" CoolingOffset="2" HeatingOffset="2" TransmitToEndDevice="1" AllowCustomerOverride="0" IsIncrementingOffset="0" IsCriticalPeakTier="0" MessageId="0"/> <TierConfig
437 Tier="C" CoolingOffset="2" HeatingOffset="2" CoolingSetpoint="20" HeatingSetpoint="20" TransmitToEndDevice="1" AllowCustomerOverride="0" IsIncrementingOffset="0" IsCriticalPeakTier="0" MessageId="0"/> <TierConfig Tier="D" CoolingOffset="2" HeatingOffset="2" AverageLoadAdjustmentPercentage="50" DutyCyclePercentage="50" TransmitToEndDevice="1" AllowCustomerOverride="0" IsIncrementingOffset="0" IsCriticalPeakTier="0" MessageId="0"/> <DeviceClass Name="HVAC or Furnace"/> <DeviceClass Name="Pool Pump/Spa/Jacuzzi"/> </EnergyConservation>
B. Sample Files
</Task> <Task> <EnergyConservation Name="KW_EC_5" > <TierConfig Tier="A" CoolingOffset="2" HeatingOffset="2" DutyCyclePercentage="50" TransmitToEndDevice="1" AllowCustomerOverride="0" IsIncrementingOffset="0" IsCriticalPeakTier="1" MessageId="0"/> <TierConfig Tier="B" CoolingOffset="2" HeatingOffset="2" TransmitToEndDevice="1" AllowCustomerOverride="0" IsIncrementingOffset="0" IsCriticalPeakTier="0" MessageId="0"/> <TierConfig Tier="C" TransmitToEndDevice="1" AllowCustomerOverride="0" IsIncrementingOffset="0" IsCriticalPeakTier="0" MessageId="0"/> <TierConfig Tier="D" CoolingOffset="2" HeatingOffset="2" AverageLoadAdjustmentPercentage="0" DutyCyclePercentage="50" TransmitToEndDevice="1" AllowCustomerOverride="0" IsIncrementingOffset="0"
438 IsCriticalPeakTier="0" MessageId="0"/> <DeviceClass Name="HVAC or Furnace"/> <DeviceClass Name="Pool Pump/Spa/Jacuzzi"/> </EnergyConservation>
B. Sample Files
</Task> <Task> <EnergyConservation Name="KW_EC_6" > <TierConfig Tier="A" CoolingOffset="2" HeatingOffset="2" DutyCyclePercentage="50" TransmitToEndDevice="1" AllowCustomerOverride="0" IsIncrementingOffset="0" IsCriticalPeakTier="1" MessageId="0"/> <TierConfig Tier="B" CoolingOffset="2" HeatingOffset="2" TransmitToEndDevice="1" AllowCustomerOverride="0" IsIncrementingOffset="0" IsCriticalPeakTier="0" MessageId="0"/> <TierConfig Tier="C" TransmitToEndDevice="1" AllowCustomerOverride="0" IsIncrementingOffset="0" IsCriticalPeakTier="0" MessageId="0"/> <TierConfig Tier="D" CoolingOffset="2" HeatingOffset="2" AverageLoadAdjustmentPercentage="0" DutyCyclePercentage="50" TransmitToEndDevice="1" AllowCustomerOverride="0" IsIncrementingOffset="0" IsCriticalPeakTier="0" MessageId="0"/> <DeviceClass Name="HVAC or Furnace"/> <DeviceClass Name="Pool Pump/Spa/Jacuzzi"/> </EnergyConservation> </Task> <Task> <EnergyConservation Name="KW_EC_7" > <TierConfig Tier="A" CoolingOffset="2" HeatingOffset="2" DutyCyclePercentage="50" TransmitToEndDevice="1" AllowCustomerOverride="0" IsIncrementingOffset="0" IsCriticalPeakTier="1" MessageId="0"/>
439 <TierConfig Tier="B" CoolingOffset="2" HeatingOffset="2" TransmitToEndDevice="1" AllowCustomerOverride="0" IsIncrementingOffset="0" IsCriticalPeakTier="0" MessageId="0"/> <TierConfig Tier="C" TransmitToEndDevice="1" AllowCustomerOverride="0" IsIncrementingOffset="0" IsCriticalPeakTier="0" MessageId="0"/> <TierConfig Tier="D" CoolingOffset="2" HeatingOffset="2" AverageLoadAdjustmentPercentage="0" DutyCyclePercentage="50" TransmitToEndDevice="1" AllowCustomerOverride="0" IsIncrementingOffset="0" IsCriticalPeakTier="0" MessageId="0"/> <DeviceClass Name="HVAC or Furnace"/> <DeviceClass Name="Pool Pump/Spa/Jacuzzi"/> </EnergyConservation>
B. Sample Files
</Task> <Task> <EnergyConservation Name="KW_EC_8" > <TierConfig Tier="A" CoolingOffset="2" HeatingOffset="2" DutyCyclePercentage="50" TransmitToEndDevice="1" AllowCustomerOverride="0" IsIncrementingOffset="0" IsCriticalPeakTier="1" MessageId="0"/> <TierConfig Tier="B" CoolingOffset="2" HeatingOffset="2" TransmitToEndDevice="1" AllowCustomerOverride="0" IsIncrementingOffset="0" IsCriticalPeakTier="0" MessageId="0"/> <TierConfig Tier="C" TransmitToEndDevice="1" AllowCustomerOverride="0" IsIncrementingOffset="0" IsCriticalPeakTier="0" MessageId="0"/> <TierConfig Tier="D" CoolingOffset="2"
440 HeatingOffset="2" AverageLoadAdjustmentPercentage="0" DutyCyclePercentage="50" TransmitToEndDevice="1" AllowCustomerOverride="0" IsIncrementingOffset="0" IsCriticalPeakTier="0" MessageId="0"/> <DeviceClass Name="HVAC or Furnace"/> <DeviceClass Name="Strip Heat"/> <DeviceClass Name="Water Heater"/> <DeviceClass Name="Pool Pump/Spa/Jacuzzi"/> <DeviceClass Name="Smart Appliances"/> <DeviceClass Name="Irrigation Pump"/> <DeviceClass Name="Managed Loads"/> <DeviceClass Name="Simple Loads"/> <DeviceClass Name="Exterior Lighting"/> <DeviceClass Name="Interior Lighting"/> <DeviceClass Name="Electric Vehicle"/> <DeviceClass Name="Generation Systems"/> </EnergyConservation>
B. Sample Files
</Task> <Task> <EnergyConservation Name="KW_EC_9" > <TierConfig Tier="A" CoolingOffset="2" HeatingOffset="2" DutyCyclePercentage="50" TransmitToEndDevice="1" AllowCustomerOverride="0" IsIncrementingOffset="0" IsCriticalPeakTier="1" MessageId="0"/> <TierConfig Tier="B" CoolingOffset="2" HeatingOffset="2" TransmitToEndDevice="1" AllowCustomerOverride="0" IsIncrementingOffset="0" IsCriticalPeakTier="0" MessageId="0"/> <TierConfig Tier="C" TransmitToEndDevice="1" AllowCustomerOverride="0" IsIncrementingOffset="0" IsCriticalPeakTier="0" MessageId="0"/> <TierConfig Tier="D" CoolingOffset="2" HeatingOffset="2" AverageLoadAdjustmentPercentage="0" DutyCyclePercentage="50" TransmitToEndDevice="1" AllowCustomerOverride="0" IsIncrementingOffset="0" IsCriticalPeakTier="0" MessageId="0"/> <DeviceClass Name="HVAC or Furnace"/>
441 <DeviceClass Name="Strip Heat"/> <DeviceClass Name="Water Heater"/> <DeviceClass Name="Pool Pump/Spa/Jacuzzi"/> <DeviceClass Name="Smart Appliances"/> <DeviceClass Name="Irrigation Pump"/> <DeviceClass Name="Managed Loads"/> <DeviceClass Name="Simple Loads"/> <DeviceClass Name="Exterior Lighting"/> <DeviceClass Name="Interior Lighting"/> <DeviceClass Name="Electric Vehicle"/> <DeviceClass Name="Generation Systems"/> </EnergyConservation>
B. Sample Files
</Task> <Task> <EnergyConservation Name="KW_EC_10" > <TierConfig Tier="A" CoolingOffset="2" HeatingOffset="2" DutyCyclePercentage="50" TransmitToEndDevice="1" AllowCustomerOverride="0" IsIncrementingOffset="0" IsCriticalPeakTier="1" MessageId="0"/> <TierConfig Tier="B" CoolingOffset="2" HeatingOffset="2" TransmitToEndDevice="1" AllowCustomerOverride="0" IsIncrementingOffset="0" IsCriticalPeakTier="0" MessageId="0"/> <TierConfig Tier="C" TransmitToEndDevice="1" AllowCustomerOverride="0" IsIncrementingOffset="0" IsCriticalPeakTier="0" MessageId="0"/> <TierConfig Tier="D" CoolingOffset="2" HeatingOffset="2" AverageLoadAdjustmentPercentage="0" DutyCyclePercentage="50" TransmitToEndDevice="1" AllowCustomerOverride="0" IsIncrementingOffset="0" IsCriticalPeakTier="0" MessageId="0"/> <DeviceClass Name="HVAC or Furnace"/> <DeviceClass Name="Strip Heat"/> <DeviceClass Name="Water Heater"/> <DeviceClass Name="Pool Pump/Spa/Jacuzzi"/> <DeviceClass Name="Smart Appliances"/> <DeviceClass Name="Irrigation Pump"/> <DeviceClass Name="Managed Loads"/> <DeviceClass Name="Simple Loads"/> <DeviceClass Name="Exterior Lighting"/> <DeviceClass Name="Interior Lighting"/>
442 <DeviceClass Name="Electric Vehicle"/> <DeviceClass Name="Generation Systems"/> </EnergyConservation>
B. Sample Files
</Task>  <Task> <ThermostatConfigToTOUSchedule TOUSchedule="KW TOU Schedule" ThermostatConfiguration="KW_EC_1"/> </Task>   <Task> <HANDevice DeviceClass="HVAC or Furnace" DeviceName="KWHVACF" CommunicationId="000d6f000011AF37" CommunicationType="Zigbee" LinkKeyAlgorithm="Elster"/> </Task> <Task> <HANDevice DeviceClass="HVAC or Furnace" DeviceName="KWHVACF2" CommunicationId="000d6f000023F99A" CommunicationType="Zigbee" LinkKeyAlgorithm="Elster"/> </Task>  <Task> <HANDevice DeviceClass="Pool Pump/Spa/Jacuzzi" DeviceName="KWPOOLPLCD" CommunicationId="000d6f0000117D11" CommunicationType="Zigbee" LinkKeyAlgorithm="Elster"/> </Task>  <Task> <HANDevice DeviceClass="Pool Pump/Spa/Jacuzzi" DeviceName="KWPOOLPUMP22" CommunicationId="000d6f0000227D22" CommunicationType="Zigbee" LinkKeyAlgorithm="Elster"/> </Task> <Task> <HANDevice DeviceClass="HVAC or Furnace" DeviceName="KWHVACF33" CommunicationId="000d6f0000337D33" CommunicationType="Zigbee" LinkKeyAlgorithm="Elster"/> </Task>
EA_MS Release 7.6 User Guide <Task>
443
B. Sample Files
<HANDevice DeviceClass="Strip Heat" DeviceName="KWSTRIPHEAT44" CommunicationId="000d6f0000447D44" CommunicationType="Zigbee" LinkKeyAlgorithm="Elster"/> </Task> <Task> <HANDevice DeviceClass="Water Heater" DeviceName="KWWATERHEATER55" CommunicationId="000d6f0000557D55" CommunicationType="Zigbee" LinkKeyAlgorithm="Elster"/> <!-</Task> <Task> <HANDevice DeviceClass="Smart Appliances" DeviceName="KWSMARTAPPLIANCES66" CommunicationId="000d6f0000667D66" CommunicationType="Zigbee" LinkKeyAlgorithm="Elster"/> </Task> <Task> <HANDevice DeviceClass="Irrigation Pump" DeviceName="KWIRRIGATIONPUMP77" CommunicationId="000d6f0000777D77" CommunicationType="Zigbee" LinkKeyAlgorithm="Elster"/> </Task> <Task> <HANDevice DeviceClass="Managed Loads" DeviceName="KWMANAGEDLOADS88" CommunicationId="000d6f0000887D88" CommunicationType="Zigbee" LinkKeyAlgorithm="Elster"/> </Task> <Task> <HANDevice DeviceClass="Simple Loads" DeviceName="KWSIMPLELOADS99" CommunicationId="000d6f0000997D99" CommunicationType="Zigbee" LinkKeyAlgorithm="Elster"/> </Task> <Task> <HANDevice DeviceClass="Exterior Lighting" DeviceName="KWEXTERIORLIGHTING10" CommunicationId="000d6f0010447D44" CommunicationType="Zigbee" LinkKeyAlgorithm="Elster"/> </Task> <Task> <HANDevice DeviceClass="Exterior Lighting" DeviceName="KWEXTERIORLIGHTING11" CommunicationId="000d6f0011447D44" CommunicationType="Zigbee" LinkKeyAlgorithm="Elster"/>
EA_MS Release 7.6 User Guide </Task> <Task>
444
B. Sample Files
<HANDevice DeviceClass="Interior Lighting" DeviceName="KWINTERIORLIGHTING12" CommunicationId="000d6f0012447D44" CommunicationType="Zigbee" LinkKeyAlgorithm="Elster"/> </Task> <Task> <HANDevice DeviceClass="Electric Vehicle" DeviceName="KWELECTRICVEHICLE13" CommunicationId="000d6f0013447D44" CommunicationType="Zigbee" LinkKeyAlgorithm="Elster"/> </Task> <Task> <HANDevice DeviceClass="Generation Systems" DeviceName="KWGENERATIONSYSTEMS14" CommunicationId="000d6f0011447D44" CommunicationType="Zigbee" LinkKeyAlgorithm="Elster"/> </Task>-->  <Task> <ProvisionHANDevice MeterName="KW2REX08302271" CommunicationId="000d6f000011AF37"/> </Task> <Task> <ProvisionHANDevice MeterName="KW2REX08302271" CommunicationId="000d6f000023F99A"/> </Task>  <Task> <ProvisionHANDevice MeterName="KW2REX08302271" CommunicationId="000d6f0000117D11"/> </Task>  <Task> <CriticalTierOverride TOUSchedule="KW TOU Schedule" StartDate="2009-03-10 08:00:00" Duration="15" Tier="A"/> </Task> <Task> <CriticalTierOverride TOUSchedule="KW TOU Schedule" StartDate="2009-03-10 13:00:00" Duration="30" Tier="A"/> </Task> <Task> <CriticalTierOverride TOUSchedule="KW TOU Schedule"
445 StartDate="2009-03-11 08:00:00" Duration="45" Tier="A"/>
B. Sample Files
</Task> <Task> <CriticalTierOverride TOUSchedule="KW TOU Schedule" StartDate="2009-03-11 13:00:00" Duration="60" Tier="A"/> </Task> <Task> <CriticalTierOverride TOUSchedule="KW TOU Schedule" StartDate="2009-03-12 08:00:00" Duration="75" Tier="A"/> </Task> <Task> <CriticalTierOverride TOUSchedule="KW TOU Schedule" StartDate="2009-03-12 13:00:00" Duration="90" Tier="A"/> </Task> <Task> <CriticalTierOverride TOUSchedule="KW TOU Schedule" StartDate="2009-03-13 08:00:00" Duration="105" Tier="A"/> </Task> <Task> <CriticalTierOverride TOUSchedule="KW TOU Schedule" StartDate="2009-03-13 13:00:00" Duration="120" Tier="A"/> </Task> <Task> <CriticalTierOverride TOUSchedule="KW TOU Schedule" StartDate="2009-03-14 08:00:00" Duration="120" Tier="A"/> </Task> <Task> <CriticalTierOverride TOUSchedule="KW TOU Schedule" StartDate="2009-03-14 13:00:00" Duration="120" Tier="A"/> </Task>  <Task> <EmergencyManagementEvent Name="KWPOOLPLCD16" StartAt="2009-03-16 13:05:05" Duration="10" Criticality="Emergency" CoolingOffset="2" HeatingOffset="2"
446 DutyCycle="75"> <DeviceClass Name="Pool Pump/Spa/Jacuzzi"/> <AssignMeter Name="KW2REX08302271"/> </EmergencyManagementEvent>
B. Sample Files
</Task> <Task> <EmergencyManagementEvent Name="KWPOOLPLCD17" StartAt="2009-03-17 13:05:05" Duration="30" Criticality="Emergency" CoolingOffset="2" HeatingOffset="2" DutyCycle="50"> <DeviceClass Name="Pool Pump/Spa/Jacuzzi"/> <AssignMeter Name="KW2REX08302271"/> </EmergencyManagementEvent> </Task> <Task> <EmergencyManagementEvent Name="KWPOOLPLCD18" StartAt="2009-03-18 13:05:05" Duration="45" Criticality="Emergency" CoolingOffset="2" HeatingOffset="2" DutyCycle="50"> <DeviceClass Name="Pool Pump/Spa/Jacuzzi"/> <AssignMeter Name="KW2REX08302271"/> </EmergencyManagementEvent> </Task> <Task> <EmergencyManagementEvent Name="KWPOOLPLCD19" StartAt="2009-03-19 13:05:05" Duration="60" Criticality="Emergency" CoolingOffset="2" HeatingOffset="2" DutyCycle="50"> <DeviceClass Name="Pool Pump/Spa/Jacuzzi"/> <AssignMeter Name="KW2REX08302271"/> </EmergencyManagementEvent> </Task> <Task> <EmergencyManagementEvent Name="KWPOOLPLCD20" StartAt="2009-03-20 13:05:05" Duration="75" Criticality="Emergency" CoolingOffset="2" HeatingOffset="2" DutyCycle="50"> <DeviceClass Name="Pool Pump/Spa/Jacuzzi"/> <AssignMeter Name="KW2REX08302271"/> </EmergencyManagementEvent> </Task> <Task> <EmergencyManagementEvent Name="KWPOOLPLCD21" StartAt="2009-03-21 13:05:05" Duration="90" Criticality="Emergency"
447 CoolingOffset="2" HeatingOffset="2" DutyCycle="50"> <DeviceClass Name="Pool Pump/Spa/Jacuzzi"/> <AssignMeter Name="KW2REX08302271"/> </EmergencyManagementEvent>
B. Sample Files
</Task> <Task> <EmergencyManagementEvent Name="KWPOOLPLCD22" StartAt="2009-03-22 13:05:05" Duration="105" Criticality="Emergency" CoolingOffset="2" HeatingOffset="2" DutyCycle="50"> <DeviceClass Name="Pool Pump/Spa/Jacuzzi"/> <AssignMeter Name="KW2REX08302271"/> </EmergencyManagementEvent> </Task> <Task> <EmergencyManagementEvent Name="KWPOOLPLCD23" StartAt="2009-03-23 13:05:05" Duration="120" Criticality="Emergency" CoolingOffset="2" HeatingOffset="2" DutyCycle="50"> <DeviceClass Name="Pool Pump/Spa/Jacuzzi"/> <AssignMeter Name="KW2REX08302271"/> </EmergencyManagementEvent> </Task> <Task> <EmergencyManagementEvent Name="KWPOOLPLCD24" StartAt="2009-03-24 13:05:05" Duration="120" Criticality="Emergency" CoolingOffset="2" HeatingOffset="2" DutyCycle="50"> <DeviceClass Name="Pool Pump/Spa/Jacuzzi"/> <AssignMeter Name="KW2REX08302271"/> </EmergencyManagementEvent> </Task> <Task> <EmergencyManagementEvent Name="KWPOOLPLCD25" StartAt="2009-03-25 13:05:05" Duration="120" Criticality="Emergency" CoolingOffset="2" HeatingOffset="2" DutyCycle="50"> <DeviceClass Name="Pool Pump/Spa/Jacuzzi"/> <AssignMeter Name="KW2REX08302271"/> </EmergencyManagementEvent> </Task>   <Task> <ReadMeter MeterName="KW2REX08302271" NumReadAttempts="2" ReturnReadings="1" > <Component Name="commission/decommissioninhomedevices" /> </ReadMeter> </Task> <Task> <ReadMeter MeterName="KW2REX08302271" NumReadAttempts="2" ReturnReadings="1" > <Component Name="commission/decommissioninhomedevices" /> </ReadMeter> </Task>
449
B. Sample Files
 <Task> <DisconnectMeter MeterName="KWREXD07316677" /> </Task> <Task> <Sleep InSeconds="240" /> </Task>  <Task> <ConnectMeter MeterName="KWREXD07316677" /> </Task>  <Task> <DisconnectMeter MeterName="KW2REXD08609027" /> </Task> <Task> <Sleep InSeconds="240" /> </Task>  <Task> <ConnectMeter MeterName="KW2REXD08609027" /> </Task> </Sequence> </ImportDataInput> </AMRDEF>
Example 2
<?xml version="1.0" standalone="no"?> <AMRDEF>  <Meter IsActive = "1" MeterType="REX" SerialNumber="100001" MeterName="dg-rexmeter-1" SDPId="dg-site-100001" AccountName="dg-account-100001" AccountNumber="100001" SiteLocation="Elster" Description="description is modified..." /> <Meter IsActive = "1" MeterType="REX" SerialNumber="100002" MeterName="dg-rexmeter-2" SDPId="dg-site-100002" AccountName="dg-account-100002"
450
B. Sample Files
AccountNumber="100002" SiteLocation="Elster" Description="description is modified..." />  <MeterBilling MeterName="dg-rexmeter-1" Schedule="dg-2Hour-dcg" ComponentGroup="reg-lp-event-set" /> <MeterBilling MeterName="dg-rexmeter-2" Schedule="dg-2Hour-dcg" ComponentGroup="reg-lp-event-set" />  <MeterBilling IsActive = "0" MeterName="dg-rexmeter-1" Schedule="dg-2Hour-dcg" ComponentGroup="reg-lp-event-set" /> <MeterBilling IsActive = "0" MeterName="dg-rexmeter-2" Schedule="dg-2Hour-dcg" ComponentGroup="reg-lp-event-set" />  <Meter IsActive = "1" MeterType="REX" SerialNumber="100001" MeterName="dg-rexmeter-1" SDPId="dg-site-100001" AccountName="dg-account-100001" AccountNumber="100001" SiteLocation="Elster" Description="description is modified..." RemovalDate="2003-06-15 11:00:00" />  <Meter IsActive = "0" MeterType="REX" SerialNumber="100001" MeterName="dg-rexmeter-1" SDPId="dg-site-100001" AccountName="dg-accout-100001" AccountNumber="100001" SiteLocation="Elster" Description="description is modified..." /> <Meter IsActive = "0" MeterType="REX" SerialNumber="100002" MeterName="dg-rexmeter-2" SDPId="dg-site-100002" AccountName="dg-accout-100002" AccountNumber="100002" SiteLocation="Elster" Description="description is modified..." />  <Task>
451 <HANDevice DeviceClass="HVAC or Furnace" CommunicationType="Zigbee" CommunicationId="000d6f000023f995" LinkKeyAlgorithm="Elster" DeviceName="Thrm4072" />
B. Sample Files
</Task>

<Task> <ProvisionHANDevice MeterName="MB REX2 4072" CommunicationId="000d6f000023f995" /> </Task> 
<Task> <ProvisionHANDevice MeterName="MB REX2 4072" CommunicationId="000d6f000023f995" IsActive="0" /> </Task>

<Task> <ThermostatConfigToTOUSchedule ThermostatConfiguration="mbec4072" TOUSchedule="MBTOU4072" /> </Task>
 <ThermostatConfigToMeter MeterName="krex2" ThermostatConfiguration=Sample TC" />  <Task> <HANDevice DeviceClass="HVAC or Furnace" CommunicationType="Zigbee" CommunicationId="000d6f000023f995" LinkKeyAlgorithm="Elster" DeviceName="Thrm4072" /> </Task>  <Task> <ProvisionHANDevice MeterName="MB REX2 4072" CommunicationId="000d6f000023f995" />
EA_MS Release 7.6 User Guide </Task>
452
B. Sample Files
 <Task> <TOUPricing TOUScheduleName="MBTOU4072" > <PerSeasonPricing SeasonName="Spring" FlatMonthlyCharge="484.441" FuelFactor="7.03" RatePerKWHTOUA="6.233" RatePerKWHTOUB="5.854" RatePerKWHTOUC="4.5" /> <PerSeasonPricing SeasonName="Summer" FlatMonthlyCharge="484.441" FuelFactor="7.03" RatePerKWHTOUA="5.626" RatePerKWHTOUB="4.428" RatePerKWHTOUC="3.185" /> <PerSeasonPricing SeasonName="Winter" FlatMonthlyCharge="484.441" BaseKWHBreakpoint="500" BasePriorToBreakpoint="3.881" BaseAfterBreakpoint="4.624" FuelFactor="7.03" /> </TOUPricing> </Task>  <Task> <DataSet Name="MB HAN Events Dataset" IsActive="1" > <Component Name="ReadHomeAreaNetworkStatus" /> </DataSet> </Task> 
453
B. Sample Files
<Task> <MeterBilling MeterName="MB REX2 4072" IsActive="1" Schedule="MB HAN Event Schedule" ComponentGroup="MB HAN Events Dataset" /> </Task>  <Task> <EnergyConservation Name="mbec4072" > <TierConfig Tier="A" CoolingOffset="3" HeatingOffset="3" DutyCyclePercentage="50" TransmitToEndDevice="1" AllowCustomerOverride="1" IsIncrementingOffset="0" IsCriticalPeakTier="1" /> <TierConfig Tier="B" CoolingOffset="1" HeatingOffset="1" DutyCyclePercentage="0" TransmitToEndDevice="1" AllowCustomerOverride="1" IsIncrementingOffset="0" IsCriticalPeakTier="0" /> <TierConfig Tier="C" CoolingSetpoint="28" HeatingSetpoint="19" DutyCyclePercentage="100" TransmitToEndDevice="1" AllowCustomerOverride="1" IsIncrementingOffset="0" IsCriticalPeakTier="0" /> <TierConfig Tier="D" TransmitToEndDevice="1" AllowCustomerOverride="1" IsIncrementingOffset="0" IsCriticalPeakTier="0" /> <DeviceClass Name="HVAC or Furnace"/> <DeviceClass Name="Pool Pump/Spa/Jacuzzi"/> </EnergyConservation>
</Task>

454
B. Sample Files
<Task> <CriticalTierOverride TOUSchedule="MBTOU4072" StartDate="2009-03-07 03:00:00" Duration="60" Tier="A" /> </Task> <Task> <CriticalTierOverride TOUSchedule="MBTOU4072" StartDate="2009-03-07 07:00:00" Duration="120" Tier="A" /> </Task>
 <Task> <ReadMeter MeterName="MB REX2 4072" NumReadAttempts="2" ReturnReadings="1" > <Component Name="commission/decommissioninhomedevices" /> </ReadMeter> </Task>
 <Task> <EmergencyManagementEvent Name="MBEME" StartAt="2008-12-03 01:02:03" Duration="15" Criticality="Emergency" CoolingOffset="5" HeatingOffset="5" CoolingSetpoint="70" HeatingSetpoint="65" LoadAdjust="75" DutyCycle="75"> <DeviceClass Name="HVAC or Furnace"/> <AssignMeter Name="MB REX2-D 2275" /> <AssignMeter Name="MB REX2 4072" /> </EmergencyManagementEvent> </Task>  <Task> <MessageToHANDevice MeterName="MB REX2 4072" StartAt="2009-01-06 08:30:00" DurationInMinutes="60" Criticality="Low"
455
B. Sample Files
ConfirmationRequired="0" LanguageId="0" Message="Today is 01 06 2009-3mW." /> </Task>  <Task> <ReadMeter MeterName="MB REX2 4072" NumReadAttempts="2" ReturnReadings="1" > <Component Name="ReadHomeAreaNetworkStatus" /> </ReadMeter> </Task>  <Task> <CancelEmergencyManagementEvent Name="mblce-7" EffectiveDate="now+2"> <AssignMeter Name="MB REX2 4072" />
</CancelEmergencyManagementEvent> </Task>
<Task> <CancelMessageToHANDevice MeterName="MB REX2-D 2275" StartAt="2009-03-06 19:00:00" /> </Task> </AMRDEF>
About InHomeDevice object

The InHomeDevice object is described below: DeviceClass must be HVAC or Furnace DeviceName helps you identify the HAD, up to 10 characters CommunicationId is the MAC address of the thermostat PAN_ID, LinkKey - although they are not presently used, should be as shown above CommunicationType must be Zigbee
About ProvisionInHomeDevice object

The ProvisionInHomeDevice object is described below: MeterName is name of the REX2 meter to which this HAD should be assigned CommunicationId is the MAC address of the thermostat
456
B. Sample Files
About ThermostatConfigToMeter object

The ThermostatConfigToMeter object is described below: MeterName is name of the REX2 meter to which this configuration should be assigned ThermostatConfiguration is the name of the configuration to be synchronized to the HAD contains information for Critical Tier Override including temperature offsets and whether the customer allowed to override
EA_MS Release 7.6 457 C. Events and statuses
Events and statuses
A3 ALPHA Meter Statuses A3 ALPHA Meter Events REX/REX2 Meter Statuses REX/REX2 Meter Events EA_Water Meter Statuses EA_Water Meter Events EA_Gas meter statuses and events A3 ALPHA meter with EA_NIC Statuses A3 ALPHA meter with EA_NIC Events WIC Statuses WIC Events A3 ALPHA meter and gatekeeper status descriptions REX/REX2 status descriptions
Note: Events are categorized into broad groups based on general area of relevance. Individual users can configure their user profile Favorites tab to select Monitored Event Categories viewed on the System Dashboard.
Events and statuses

EA_MS supports alarms, events and other status conditions that are reported by a meter. EA_MS uses the following distinctions: status event error warning the current condition of the meter (may includes errors and warnings); if an abnormal value occurs, EA_MS will generate an event an abnormal status condition exists in the meter; EA_MS will also generate an event from reading a meters event log a condition in the meter exists that could affect billing data integrity condition exists in the meter that could result in the imminent failure of the meter or in an error in the near future (that is, affect billing data integrity). Billing data recorded up to this point is valid. EA_MS detects the occurrence of an event that has been configured for alarm notification through the browser (see the Installation and Administration Guide for details on configuring alarm notification)
alarm
Note: Refer to the manufacturers meter technical manual for details on the events, errors, warnings, and alarms supported by a particular meter.
Common Meter Statuses

ID 60000 60001 60002 60003 60004 60005 60006 Category Service Service Tamper Alert Tamper Alert Tamper Alert Meter Health Tamper Alert Name Old Outage Count New Outage Count Demand Reset Count Old Reverse Energy New Reverse Energy Clock Failed Configuration Changed Type int int int real real bool bool Quality Flag Meter Health Meter Health Tamper Alert Tamper Alert Tamper Alert Meter Health Tamper Alert AMRDEF error section error section tamper section tamper section tamper section error section tamper section Report No No Yes Yes Yes Yes Yes Raise Event never never never never never never if_true 80000007 Event ID
Common Meter Events

ID 80000000 80000001 80000002 Miscellaneous Tamper Alert Miscellaneous Category Outage Count Increment Reverse Energy Flow Time Changed by EA_MS Currently, we have a common Miscellaneous event Time changed by EA_MS which occurs when EA_MS synchs the meter time. This is passed up as a Miscellaneous event and reported as such. When the EA_MS synchs the time an event record is placed in the meters event log. When the meter is read the next time, this Miscellaneous event in the event log is then recorded as a Meter event > Tamper Alert - Time Changed by EA_MS. Even though it was the same miscellaneous event that we just got thru initiating by the lim synch action. Both events are then shown with like TS on the event report. Transient Alarm Outage call-in Restoration call-in Demand Reset Meter Configuration Change Detected IP Address Changed Check-in event Thermal Normal to Restricted Check-in event Thermal Restricted Check-in event Name
80000003 80000004 80000005 80000006 80000007 80000010 80000011 80000012
Miscellaneous Full Power Outage / Restoration Full Power Outage / Restoration Miscellaneous Tamper Alert WAN WAN WAN
Common Meter Events

ID 80000013 80000014 WAN WAN Category Name Thermal Power Off to Restricted Check-in event Thermal Restricted to Normal Check-in event
A3 ALPHA meter events and statuses

A3 ALPHA Meter Statuses
ID 1 2 4 6 7 9 10 11 13 14 15 19 20 21 22 23 24 Category Tamper Alert Meter Health Meter Health Meter Health Meter Health Meter Health Service Service Tamper Alert Tamper Alert Meter Health Tamper Alert Tamper Alert Meter Health Meter Health Meter Health Meter Health Name Meter in Test Mode Configuration error RAM failure Registered memory error Clock error Low battery warning Type bool bool bool bool bool bool Quality Flag Tamper Alert Meter Health Meter Health Meter Health Meter Health none none none Tamper Alert Tamper Alert Meter Health Tamper Alert Tamper Alert Meter Health Meter Health Meter Health Meter Health AMRDEF tamper section error section error section error section error section never never never tamper section tamper section error section tamper section tamper section error section error section error section error section Report Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Raise Event if_true if_true if_true if_true if_true if_true if_true if_true if_true if_true if_true if_true if_true if_true if_true if_true if_true 8 18 20 22 23 25 26 27 29 80000001 33 108 109 36 37 38 39 Event ID
Potential Indicator Warning bool Demand overload Tamper detected Reverse rotation Crystal oscillator error bool bool bool bool
Button press demand reset bool Button press clear data EEPROM access error Internal Communication / I2C error Tariff EE write error Tariff EE read error bool bool bool bool bool

ID 25 26 28 29 31 32 36 37 38 40 41 42 43 44 45 46 47 48 82 83 84 85 86 87 88 89 90 91 92 93 Category Meter Health Meter Health Service Meter Health Tamper Alert Tamper Alert Miscellaneous Service Service Service Service Service Service Service Service Service Service Service Tamper Alert Meter Health Meter Health Meter Health Meter Health Meter Health Meter Health Meter Health Power Quality Meter Health Service Service Name DSP download error Table CRC Error Line frequency warning End of calendar warning Billing data write warning Canadian tables unlocked Demand threshold exceeded Service voltage test failure Service current test failure Phase A missing Phase B missing Phase C missing Phase A sag Phase B sag Phase C sag Partial Outage - Phase A Partial Outage - Phase B Partial Outage - Phase C Tier override warning Bad item in display list Warning locked on display Outage modem battery low Outage modem checksum error Outage modem self test error Outage modem missing XMB expected but missing One or more PQM Tests Failed Internal meter warning (latched) Phase A Sag Timer Phase A Cumulative Sag Count Type bool bool bool bool bool bool bool bool bool bool bool bool bool bool bool bool bool bool bool bool bool bool bool bool bool bool bool bool real int Quality Flag Meter Health Meter Health none none Tamper Alert Tamper Alert none none none none none none none none none none none none Tamper Alert none none none none none none none none Meter Health none none AMRDEF error section error section never never tamper section tamper section if_true never never never never never never never never never never never tamper section never never never never never never never never error section always always Report Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Raise Event if_true if_true if_true if_true if_true if_true if_true if_true if_true if_true if_true if_true if_true if_true if_true if_true if_true if_true if_true if_true if_true if_true if_true if_true if_true if_true if_true if_true never never Event ID 40 24 43 44 46 47 51 52 53 55 56 57 58 59 60 61 62 63 97 98 99 100 101 102 103 104 105 106

ID 94 95 96 97 98 99 100 201 212 213 214 215 216 217 218 219 220 221 Category Service Service Service Service Service Service Service General Security Security Security Security Security Security Security Security Security Communications Name Phase A Cumulative Sag Timer Phase B Sag Timer Phase B Cumulative Sag Count Phase B Cumulative Sag Timer Phase C Sag Timer Phase C Cumulative Sag Count Phase C Cumulative Sag Timer Cumulative Power Outage Time Number of logons port 0 Number of configuration sessions port 0 Number of security failures port 0 Number of logons port 1 Number of configuration sessions port 1 Number of security failures port 1 Number of manual demand resets Days since last demand reset Days since last pulse Elapsed Time, in Milliseconds, on Arrival at Primary Address Elapsed Time, in Milliseconds, on Arrival at Secondary Address Number of Hops on Arrival at Primary Address Number of Hops on Arrival at Secondary Address IP Statistics - Packets Received IP Statistics - Bytes Received IP Statistics - Unicast Packets Received Type real real int real real int real int int int int int int int int int int int Quality Flag none none none none none none none none none none none none none none none none none none AMRDEF always always always always always always always never never never never never never never never never never always Report Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes No Raise Event never never never never never never never never never never never never never never never never never never Event ID
222
Communications
int
none
always
No
never
223 224 225 226 227
Communications Communications Communications Communications Communications
int int int int int
none none none none none
always always always always always
No No Yes Yes Yes
never never never never never

ID 228 Category Communications Name IP Statistics - Net Directed Broadcast Packets Received IP Statistics - Transmit Errors IP Statistics - Packets Transmitted IP Statistics - Bytes Transmitted IP Statistics - Unicast Packets Transmitted IP Statistics - Net Directed Broadcast Packets Transmitted IP Statistics - IP Packets Received IP Statistics - IP Fragments IP Statistics - IP Checksum Errors IP Statistics - IP Packets Dropped IP Statistics - IP Packets Routed IP Statistics - IP Options IP Statistics - Unknown Protocol WIC Option Board ROM Checksum Error WIC Option Board Configuration Error WIC Option Board EEPROM CRC Error WIC Option Board Hardware Failure WIC Option Board Network Failure WIC Option Board Protocol Failure WIC Option Board C12 Master Failure WIC Option Board Database Failure WIC Option Board Protocol Table Failure WIC Option Board Table Error Type int Quality Flag none AMRDEF always Report Yes Raise Event never Event ID
229 230 231 232 233
Communications Communications Communications Communications Communications
int int int int int
none none none none none
always always always always always
Yes Yes Yes Yes Yes
never never never never never
234 235 236 237 238 239 240 241 242 243 244 245 246 247 248 249 250
Communications Communications Communications Communications Communications Communications Communications Meter Health Meter Health Meter Health Meter Health Meter Health Meter Health Meter Health Meter Health Meter Health Meter Health
int int int int int int int bool bool bool bool bool bool bool bool bool bool
none none none none none none none none none none none none none none none none none
always always always always always always always always always always always always always always always always always
Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes
never never never never never never never if_true if_true if_true if_true if_true if_true if_true if_true if_true if_true 164 165 166 167 168 169 170 171 172 173

ID 251 252 253 254 255 256 257 258 301 302 303 304 305 306 Category Meter Health Meter Health Meter Health Meter Health Meter Health Meter Health Meter Health Meter Health WAN WAN WAN WAN WAN WAN Name ILC Profile Error ILC Power Down Error ILC Shared Memory Error ILC Configuration Error ILC CRC Error ILC Holdover Error ILC Clock Error ILC Shut Down Cell Signal Strength Cell Signal Bit Error Cell Tower Info Temperature Capacitor Voltage Current Use Type bool bool bool bool bool bool bool bool bool bool bool bool bool bool Quality Flag none none none none none none none none none none none none none none AMRDEF always always always always always always always always always always always always always always Report Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Raise Event if_true if_true if_true if_true if_true if_true if_true if_true never never never never never never Event ID 142 143 144 145 146 147 148 149
A3 ALPHA Meter Events

A3 ALPHA Meter Events ID 1 2 3 6 7 8 9 10 11 12 13 14 18 20 22 23 24 25 Category Full Power Outage / Restoration Full Power Outage / Restoration Tamper Alert Tamper Alert Tamper Alert Tamper Alert Tamper Alert Tamper Alert Miscellaneous Miscellaneous Miscellaneous Miscellaneous Meter Health Meter Health Meter Health Meter Health Meter Health Meter Health Power Outage Detected Power Restoration Detected Time Changed Test Mode Started Test Mode Stopped Meter in Test Mode Table Written Procedure Executed Self Read Begin Daylight Saving Time End Daylight Saving Time Season Changed Configuration Error Carryover Error Registered Memory Error Clock Error Table CRC Error Low Battery Warning Name
A3 ALPHA Meter Events ID 26 27 29 31 32 33 36 37 38 39 40 43 44 46 47 51 52 53 55 56 57 58 59 60 61 Service Service Tamper Alert Miscellaneous Miscellaneous Meter Health Meter Health Meter Health Meter Health Meter Health Meter Health Service Meter Health Tamper Alert Tamper Alert Miscellaneous Service Service Service Service Service Service Service Service Service Category Name Potential Indicator Warning Demand Threshold Exceeded Tamper Detected Enter Tier Override Exit Tier Override Crystal Oscillator Error EEPROM Access Error Internal Communication Error /I2C Error Tariff EE Write Error Tariff EE Read Error DSP Download Error Line Frequency Warning End Of Calendar Warning Billing Data Write Warning Canadian Tables Unlocked Demand Threshold Exceeded Service Voltage Test Failure Service Current Test Failure Phase A Missing Phase A Voltage Below Threshold Phase B Missing Phase B Voltage Below Threshold Phase C Missing Phase C Voltage Below Threshold Phase A Sag Phase A Voltage Below Threshold Phase B Sag Phase B Voltage Below Threshold Phase C Sag Phase C Voltage Below Threshold Partial Outage - Phase A Phase A Voltage Below Threshold for more than maximum sag time Partial Outage - Phase B Phase B Voltage Below Threshold for more than maximum sag time Partial Outage - Phase C Phase C Voltage Below Threshold for more than maximum sag time Tier Override Warning Bad Item in Display List Warning Locked on Display
62
Service
63
Service
97 98 99
Tamper Alert Meter Health Meter Health
A3 ALPHA Meter Events ID 100 101 102 103 104 105 106 108 109 112 116 117 118 119 120 121 122 123 124 125 126 127 128 129 130 131 132 133 134 135 136 137 138 139 140 141 142 143 Meter Health Meter Health Meter Health Meter Health Meter Health Power Quality Meter Health Tamper Alert Tamper Alert Miscellaneous Miscellaneous Miscellaneous Audit Log Audit Log Audit Log Audit Log Audit Log Audit Log Audit Log Audit Log Audit Log Audit Log Audit Log Audit Log Audit Log Audit Log Audit Log Audit Log Audit Log Audit Log Audit Log Audit Log Miscellaneous Miscellaneous Voltage Reading Voltage Reading Meter Health Meter Health Category Name Outage Modem Battery Low Outage Modem Checksum Error Outage Modem Self Test Error Outage Modem Missing XMB Expected but Missing One or More PQM Tests Failed Internal Meter Warning Button Press Demand Reset Button Press Clear Data Pending Table Activated LAN Performance Statistics Reset Unknown LAN node discovered Network Node Scan Single Node Scan Get Time from A3 Meter Read Time Broadcast Unregister All Nodes Unregister Lan Branch Mark All Nodes as Unregistered Profile Read Recover From EE Failed EE Recovery Re-write EE Backup Brute Force Read Network Ping Fixed repeater path Optimize Network Update configuration OTA Flash Scheduled Read Generic Job Max number of nodes reached A3 Node Overflow Max Number of Voltage Reading Nodes per Gatekeeper Exceeded Voltage Reading Time Exceeded ILC Profile Error ILC Power Down Error
A3 ALPHA Meter Events ID 144 145 146 147 148 149 150 151 164 165 166 167 168 169 170 171 172 173 174 175 176 177 178 179 180 181 182 183 184 185 186 187 188 Meter Health Meter Health Meter Health Meter Health Meter Health Meter Health Network Network Meter Health Meter Health Meter Health Meter Health Meter Health Meter Health Meter Health Meter Health Meter Health Meter Health Voltage Reading Disconnect Disconnect Security Security Security Meter Health Security Meter Health Meter Health Meter Health Security Security Security Meter Health Category ILC Shared Memory Error ILC Configuration Error ILC CRC Error ILC Holdover Error ILC Clock Error ILC Shut Down ICMP Traceroute Change Detected Failover to Secondary Comm. Address WIC Option Board ROM Checksum Error WIC Option Board Configuration Error WIC Option Board EEPROM CRC Error WIC Option Board Hardware Failure WIC Option Board Network Failure WIC Option Board Protocol Failure WIC Option Board C12 Master Failure WIC Option Board Database Failure WIC Option Board Protocol Table Failure WIC Option Board Table Error Voltage Reading schedule in GK not complete Service Disconnected Service Connected EA LAN Encryption Seed Changed by EA MS EA LAN Encryption Disabled by EA MS EA LAN Encruption Enabled by EA MS A3 Standard Statuses Cleared by EA MS Missing EA LAN encryption seed A3 Sag Statuses Cleared by EA MS A3 Battery Test Failed Gatekeeper Module Statuses Cleared by EA MS WAN Encryption Enabled by EA MS WAN Encryption Disabled by EA MS WAN Encryption Seed Changed by EA MS A3 Manufacturers Statuses Cleared by EA MS Name
REX/REX2 meter events and statuses

REX/REX2 Meter Statuses
ID 1 2 3 9 10 11 12 21 Category LAN Performance LAN Performance LAN Performance REX Network REX Network REX Network REX Network Service Name Number Of Read Attempts Number Of Read Responses Total Read Success Rate Node Repeater Id Node Level Descendants Repeater Descendants Load Side Voltage Present (Latched value) - Before Switch Operation No Voltage Detected with Disconnect Closed Before Switch Operation Demand Threshold Exceeded Load Side Voltage Present - Before Switch Operation Disconnect Relay Open Before Switch Operation ROM Checksum Error Registered Memory Error Configuration Error Table CRC Error EEPROM Access Error Meter Chip Error Permanent State of Disconnect is Open Before Switch Operation Change Pending - Before Switch Operation Open Pending - Before Switch Operation Forced Change - Before Switch Operation Type int int real int int int int bool Quality Flag none none none none none none none none AMRDEF always always always never never never never never Report No No No No No No No No Raise Event Event ID never never never never never never never never
22
Service
bool
none
never
No
never
23 24 26 29 30 31 32 33 34 41
Miscellaneous Service Service Meter Health Meter Health Meter Health Meter Health Meter Health Meter Health Service
bool bool bool bool bool bool bool bool bool bool
none none none Meter Health Meter Health Meter Health Meter Health Meter Health Meter Health none
if_true never never error section error section error section error section error section error section never
Yes No No Yes Yes Yes Yes Yes Yes No
if_true never never if_true if_true if_true if_true if_true if_true never
26
11 12 13 14 15 16
42 43 44
Service Service Service
bool bool bool
none none none
never never never
No No No
never never never

ID 45 Category Service Name Load Side Voltage Present (Raw) - Before Switch Operation Remaining Charge Time Before Switch Operation Load Side Voltage Present (Latched value) - After Switch Operation No Voltage Detected with Disconnect Closed - After Switch Operation Load Side Voltage Present - After Switch Operation Disconnect Relay Open After Switch Operation Permanent State of Disconnect is Open - After Switch Operation Change Pending - After Switch Operation Open Pending - After Switch Operation Forced Change - After Switch Operation Load Side Voltage Present (Raw) - After Switch Operation Remaining Charge Time After Switch Operation Communication Problem Load Side Voltage Present Disconnect Relay Open No Voltage Detected with Disconnect Closed Type bool Quality Flag none AMRDEF never Report No Raise Event Event ID never
46 47
Service Service
int bool
none none
never if_true
No No
never never
48
Service
bool
none
if_true
No
never
49 50 51
bool bool bool
none none none
never always never
No No No
never never never
52 53 54 55
Service Service Service Service
bool bool bool bool
none none none none
never never never always
No No No No
never never never never
56 57 59 60 61 62 63 64 65 66 67 68
Service Meter Communication Service Service Service
int bool bool bool bool bool bool bool bool bool bool bool
none none none none none none none
never never if_true always always always always never never
No Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes
never never if_true never if_true never never never never if_true if_true if_true 57 58 61 55 54
Power Status Check Power Status Confirmed (Restoration) Power Status Check Power Status Unknown (Possible Outage) Meter Health Meter Health Service Service Tamper Alert Meter Health DSP Stop Counter Warning Meter Health DSP Stop Count Exceeded Error Phase A Low Potential Phase C Low Potential Tilt Warning
none none Tamper Alert
if_true if_true tamper section

ID 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 Category Tamper Alert Tamper Alert Tamper Alert Meter Health Service Service Service Service Miscellaneous Service Service Miscellaneous Miscellaneous Miscellaneous Communications Name Reverse Power Warning Table Access Warning Config Table Write Warning Radio Config Error Momentary Outage Count Sustained Outage Count Sustained Outage Duration (secs) Latched Load Side Voltage Present Armed for Demand Reset Voltage Monitoring Max Event Voltage Monitoring Min Event Demand Limit Lockout Flash Transfer Pending External Operation Pending Elapsed time for passthrough operation (msec) Type bool bool bool bool int int int bool bool bool bool bool bool bool int Tamper Alert Meter Health none none none none none none none none none none none Quality Flag Tamper Alert AMRDEF tamper section if_true if_true error section always always always error section if_true if_true if_true if_true if_true if_true always Report Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes No Raise Event Event ID never if_true if_true if_true never never never Yes Yes Yes Yes Yes Yes Yes No if_true never if_true if_true if_true never never never 59 60 56
REX/REX2 Meter Events

ID 1 2 3 5 6 11 12 13 14 15 16 21 Category Miscellaneous Full Power Outage / Restoration Full Power Outage / Restoration Service Service Meter Health Meter Health Meter Health Meter Health Meter Health Meter Health Miscellaneous Name Node Scan Request Power Outage Detected Power Restoration Detected Uncontrolled Service Connect /Disconnect Detected Partial Outage - Phase C ROM Checksum Error Registered Memory / Power Fail Data Save Error Configuration Error Table CRC Error EEPROM Access Error Improper Meter Engine Operation Error Gatekeeper Reports Node Registration Description

ID 22 23 24 25 26 35 54 55 56 57 58 59 60 61 62 63 64 65 Service Miscellaneous Miscellaneous Miscellaneous Miscellaneous Service Service Service Meter Health Service Service Tamper Alert Tamper Alert Tamper Alert Service Service Miscellaneous Full Power Outage Restoration Category Name No voltage after connection of service Network Node Unregistration Detected Full Network Ping Finished Network Node Registration Detected Demand Threshold Exceeded Node LAN Performance Lower Than Threshold Meter Reports Load Side Voltage Detected With Disconnected Service No Voltage Detected with Disconnect Closed Radio Config Error Phase A Low Potential Phase C Low Potential Table Access Warning Config Table Write Warning Tilt Warning Voltage Monitoring Max Event Voltage Monitoring Min Event Demand Limit Lockout Outage Outage detected in outage log (REX2A3 Node last gasp, newer than threshold, no tamper) Restoration detected in outage log (REX2A3 Node last gasp, newer than threshold) Meter removed (REX2 last gasp with tamper, stale threshold not applicable) Old outage detected in outage log (REX2A3 Node last gasp, older than threshold, no tamper) Old restoration detected in outage log (REX2A3 Node last gasp, older than threshold) Outage detected from LP data (REX2, threshold not applicable) Restoration detected from LP data (REX2, threshold not applicable) Outage detected in exception log (REX1, no threshold applicable) Restoration detected in exception log (REX1, no threshold applicable) Description
66
Full Power Outage Restoration
Restoration
67
Meter Removal
68
Stale Outage Data Detected
69
Stale Restoration Data Detected
70 71 72 73
Full Power Outage Restoration Full Power Outage Restoration Full Power Outage Restoration Full Power Outage Restoration
Outage Detected from LP Data Restoration Detected from LP Data Outage Detected in exception log Restoration Detected in exception log

ID 74 Category Firmware Upgrade Name Firmware upgraded Description This event is generated when Meter Firmware Version or Revision is upgraded This event is generated when there is a gap between Load Profile readings
75
Miscellaneous
Possible Load Profile Gap detected
76 77
Tamper Alert Miscellaneous
Reverse Energy Flow Time Change has occurred This event is generated when there is a TimeChange record in Load Profile readings. This event is generated when the tier sum does not match the actual value reported.
78
Miscellaneous
Tier Sum does not match actual value
79 80 82 83 84 85 87 88 89 90 91 92 93 94 95 96
Tamper Alert Tamper Alert Miscellaneous Miscellaneous Miscellaneous Miscellaneous Tamper Alert Tamper Alert Service Service Service Service Service Service Service Disconnect
Reset List Pointers Event Log Cleared Phase A Off Phase C Off Phase A On Phase C On Password Changed Encryption Key Changed Disconnect Switch Opened Disconnect Switch Closed Auxillary Relay Opened Auxillary Relay Closed Voltage Monitoring Minimum Voltage Threshold Voltage Monitoring Maximum Voltage Threshold Voltage Monitoring Voltage Returned to Normal Service Disconnected Generated when the service disconnect switch has been successfully opened by EA_MS. Generated when the service disconnect switch has been successfully closed by EA_MS.
97
Disconnect
Service Connected
180
Security
EA LAN Element Stranded
EA_Water meter events and statuses

EA_Water Meter Statuses
ID 1 2 3 4 6 7 8 9 10 11 12 Category Tamper Meter Health Meter Health Miscellaneous Tamper Alert Tamper Alert Tamper Alert Meter Health Meter Health Meter Health Miscellaneous Name Tamper Detected Bad Digit in Reading Type bool bool Quality Flag Tamper Alert Meter Health Meter Health none Tamper Alert Tamper Alert Tamper Alert Meter Health Meter Health Meter Health AMDEF tamper section error section error section never tamper section tamper section tamper section error section error section error section Report Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Raise Event if_true if_true if_true if_true if_true if_true if_true if_true if_true if_true if_true 1 2 3 4 6 7 8 9 10 11 12 Event ID
No Reading from Register bool Leak Suspected Reset Error Tilt Tamper Switch Tamper Low Battery Back Flow Over Limit Module Error bool bool bool bool bool bool bool bool
Miscellaneo error us section
EA_Water Meter Events

ID ID 1 2 3 4 5 6 7 8 9 10 11 12 Category Tamper Alert Meter Health Meter Health Miscellaneous Miscellaneous Tamper Alert Tamper Alert Tamper Alert Meter Health Miscellaneous Miscellaneous Miscellaneous Category Name Tamper Detected Bad Digit in Reading No Reading from Register Leak Suspected Interval Threshold Exceeded Reset Error Tilt Tamper Switch Tamper Low Battery Back Flow Over Limit Module Error Name
EA_Gas meter statuses and events

EA_Gas Meter Statuses
ID 1 2 3 4 5 6 7 Category Tamper Alert Tamper Alert Tamper Alert Meter Health Meter Health Meter Health Miscellaneous Name Tamper Detected Tilt_Tamper Switch_Tamper Low Battery Config Error CRC Error EEPROM Error Type bool bool bool bool bool bool bool Quality Flag Tamper Alert Tamper Alert Tamper Alert Meter Health Meter Health Meter Health AMDEF tamper section tamper section tamper section error section error section error section Report Yes Yes Yes Yes Yes Yes Yes Raise Event if_true if_true if_true if_true if_true if_true if_true 1 2 3 4 5 6 7 Event ID
Miscellaneo error us section
EA_Gas Meter Events

ID 1 2 3 4 5 6 7 Tamper Alert Tamper Alert Tamper Alert Meter Health Miscellaneous Miscellaneous Meter Health Category Reset Error Tilt Tamper Switch Tamper Low Battery Back Flow Over Limit Module Error Name
A3 ALPHA meter with EA_NIC events and statuses

A3 ALPHA meter with EA_NIC Statuses
ID 1 2 3 6 Category LAN Performance LAN Performance LAN Performance Service Name Type Quality Flag AMRDEF none none none none always always always if_true Report No No No Yes Raise Event never never never if_true 20 Event ID Number Of Read Attempts int Number Of Read Responses Total Read Success Rate Demand Overload int real bool

ID 7 8 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 Category Miscellaneous Tamper Alert Meter Health Service Service Meter Health Tamper Alert Tamper Alert Meter Health Meter Health Meter Health Meter Health Meter Health Meter Health Service Tamper Alert Tamper Alert Meter Health Meter Health Meter Health Meter Health Meter Health Meter Health Meter Health Name Demand Threshold Exceeded Reverse Rotation Low Battery Warning Service Voltage Test Failure Type bool bool bool bool Quality Flag AMRDEF none Tamper Alert none none none Meter Health Tamper Alert Tamper Alert Meter Health Meter Health Meter Health Meter Health Meter Health Meter Health none Tamper Alert Tamper Alert Meter Health Meter Health Meter Health Meter Health Meter Health Meter Health Meter Health if_true tamper section if_true if_true if_true error section tamper section tamper section error section error section error section error section error section error section never tamper section tamper section error section error section error section error section error section error section error section Report Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Raise Event if_true if_true if_true if_true if_true if_true if_true if_true if_true if_true if_true never if_true if_true if_true if_true if_true if_true if_true if_true if_true if_true if_true if_true 38 39 53 40 41 42 52 43 44 45 46 47 Event ID 26 80000001 28 29 30 31 32 33 34 36 37
Service Current Test Failure bool ILC Configuration Error Meter in Test Mode Tamper Detected Meter Error Configuration Error RAM Failure ROM Error Registered Memory Error Clock Error Potential Indicator Warning Button Press Demand Reset Button Clear Data EEPROM Access Error Internal Communication / I2C Error Tariff EE Write Error Tariff EE Read Error Crystal Oscillator Error Table CRC Error DSP Download Error bool bool bool bool bool bool bool bool bool bool bool bool bool bool bool bool bool bool bool

ID 35 36 37 38 40 41 57 59 60 61 62 63 76 83 84 Category Service Meter Health Tamper Alert Meter Health Meter Health Meter Health Meter Communication Service Service Service Power Status Check Power Status Check Service Communications Service Name Line Frequency Warning End of Calendar Warning Billing Data Write Warning Internal Meter Warning ILC Shared Memory Error ILC Power Fail Save Fail Communication Problem Load Side Voltage Present Disconnect Relay Open No Voltage Detected with Disconnect Closed Power Status Confirmed (Restoration) Power Status Unknown (Possible Outage) Latched Load Side Voltage Present Elapsed time for pass through operation (msec) Load Side Voltage Present (Latched) - Before Switch Operation No Voltage Detected with Disconnect Closed Before Switch Operation Load Side Voltage Preset Before Switch Operation Disconnect Relay Open Before Switch Operation Permanent State of Disconnect is Open Before Switch Operation Change Pending - Before Switch Operation Open Pending - Before Switch Operation Forced Change - Before Switch Operation Load Side Voltage Present (Raw) - Before Switch Operation Type bool bool bool bool bool bool bool bool bool bool bool bool bool int bool Quality Flag AMRDEF none none Tamper Alert Meter Health Meter Health Meter Health none none none none none none none none none never never tamper section error section error section error section never if_true always always always always error section always never Report Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes No No Raise Event if_true if_true if_true if_true never never never if_true never if_true never never if_true never never 54 55 54 Event ID 48 49 50 51
85
Service
bool
none
never
No
never
86 87 88
bool bool bool
none none none
never never never
No No No
never never never
89 90 91 92
Service Services Service Service
bool bool bool bool
none none none none
No No No No

ID 93 94 Category Service Service Name Remaining Charge Time Before Switch Operation Load Side Voltage Present (Latched) - After Switch Operation No Voltage Detected with Disconnect Closed - After Switch Operation Load Side Voltage Detected with disconnect Closed - After Switch Operation Disconnect Relay Open After Switch Operation Permanent State of Disconnect is Open - After Switch Operation Change Pending - After Switch Operation Open Pending - After Switch operation Forced Change - After Switch Operation Load Side Voltage Present (Raw) - After Switch Operation Remaining Charge Time After Switch Operation Type int bool Quality Flag AMRDEF none none never if_true Report No No Raise Event never never Event ID
95
Service
bool
none
if_true
No
never
96
Service
bool
none
never
No
never
97 98
Service Service
bool bool
none none
always never
No No
never never
99 100 101 102
Service Service Service Service
bool bool bool bool
none none none none
never never never always
No No No No
103
Service
int
none
never
No
never
A3 ALPHA meter with EA_NIC Events

ID 1 2 3 9 20 21 23 24 25 26 Category Miscellaneous Full Power Outage / Restoration Full Power Outage / Restoration Meter Health Service Miscellaneous Miscellaneous Miscellaneous Miscellaneous Miscellaneous Name Node Scan Request Power Outage Detected Power Restoration Detected Backup Battery Low Demand Overload Gatekeeper Reports Node Registration Network Node Unregistration Detected Full Network Ping Finished Network Node Registration Detected Demand Threshold Exceeded Description

ID 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 Meter Health Service Service Meter Health Tamper Alert Tamper Alert Service Service Meter Health Meter Health Meter Health Meter Health Tamper Alert Tamper Alert Meter Health Meter Health Meter Health Meter Health Meter Health Meter Health Service Meter Health Tamper Alert Meter Health Meter Health Service Service Category Name Low Battery Warning Service Voltage Test Failure Service Current Test Failure ILC Configuration Error Meter in Test Mode Tamper Detected Meter Error Node LAN Performance Lower Than Threshold Configuration Error Carryover Error Registered Memory Error Clock Error Button Press Demand Reset Button Press Clear Data EEPROM Access Error Tariff EE Write Error Tariff EE Read Error Crystal Oscillator Error Table CRC Error DSP Download Error Line Frequency Warning End of Calendar Warning Billing Data Write Warning Internal Meter Warning Internal Communication /I2C Error Potential Indicator Warning Meter Reports Load Side Voltage Detected With Disconnected Service No Voltage Detected with Disconnect Closed Outage This event is generated by status 61, which is sent during normal reads of current period data. Outage detected in outage log (REX2/A3 Node last gasp, newer than threshold, no tamper) Restoration detected in outage log (REX2/ A3 Node last gasp, newer than threshold) Meter removed (REX2 last gasp with tamper, stale threshold not applicable) Description
55
Service
65
Full Power Outage / Restoration
66 67
Full Power Outage / Restoration Full Power Outage / Restoration
Restoration Meter Removal

ID 68 Category Full Power Outage / Restoration Name Stale Outage Data Detected Description Old outage detected in outage log (REX2/ A3 Node last gasp, older than threshold, no tamper) Old restoration detected in outage log (REX2/A3 Node last gasp, older than threshold) Outage detected from LP data (REX2, threshold not applicable) Restoration detected from LP data (REX2, threshold not applicable) Outage detected in exception log (REX1, no threshold applicable) Restoration detected in exception log (REX1, no threshold applicable) This event is generated when Meter Firmware Version or Revision is upgraded This event is generated when there is a gap between Load Profile readings
69
Full Power Outage / Restoration
Stale Restoration Data Detected
70 71 72 73 74 75 76 96
Full Power Outage / Restoration Full Power Outage / Restoration Full Power Outage / Restoration Full Power Outage / Restoration Firmware Upgrade Miscellaneous Tamper Alert Disconnect
Outage Detected from LP Data Restoration Detected from LP Data Outage Detected in exception log Restoration Detected in exception log Firmware upgraded Possible Load Profile Gap detected Reverse Energy Flow Detected Service Disconnected
Generated when the service disconnect switch has been successfully opened by EA_MS. Generated when the service disconnect switch has been successfully closed by EA_MS.
97
Disconnect
Service Connected
180
Security
EA LAN Element Stranded
WIC Statuses and Events

WIC Statuses
Status Cell Signal Strength Cell Signal Bit Error Rate Cell Tower Info Temperature Capacitor Voltage Current Use Degrees Celsius in Volts in milliAmps Description Meter Type A3 ALPHA meter with WIC Gatekeeper with WIC A3 ALPHA meter with WIC Gatekeeper with WIC A3 ALPHA meter with WIC Gatekeeper with WIC A3 ALPHA meter with WIC Gatekeeper with WIC A3 ALPHA meter with WIC Gatekeeper with WIC A3 ALPHA meter with WIC Gatekeeper with WIC
WIC Events
Category Security Security Security Security Security Security Security Security Security Security Security Interval Data Meter Health Meter Health WAN Name Security configuration change MSG rec'd does not meet security requirements MSG rec'd not unique Failed to authenticate/decrypt rec'd MSG Promotion of pending seed to active Copy of active seed to pending Re-seed action occurred Set Factory Seed action Activate Factory Seed action Access Control List was modified Program flash update occurred Missing Interval Data Thermal Shutdown Thermal Shutdown Cleared Primary Communication Address Changed Meter Type A3 ALPHA meter with WIC Gatekeeper with WIC A3 ALPHA meter with WIC Gatekeeper with WIC A3 ALPHA meter with WIC Gatekeeper with WIC A3 ALPHA meter with WIC Gatekeeper with WIC A3 ALPHA meter with WIC Gatekeeper with WIC A3 ALPHA meter with WIC Gatekeeper with WIC A3 ALPHA meter with WIC Gatekeeper with WIC A3 ALPHA meter with WIC Gatekeeper with WIC A3 ALPHA meter with WIC Gatekeeper with WIC A3 ALPHA meter with WIC Gatekeeper with WIC A3 ALPHA meter with WIC Gatekeeper with WIC REX meter A3 ALPHA with EA_NIC A3 ALPHA meter with WIC Gatekeeper with WIC A3 ALPHA meter with WIC Gatekeeper with WIC A3 ALPHA meter with WIC Gatekeeper with WIC
A3 ALPHA meter and gatekeeper status descriptions
A3 ALPHA meter and gatekeeper Status Name - EA_MS Display locked by warning
Description This code indicates that one or more warning codes has locked the display. The A3 ALPHA meter can be programmed to lock the display if a warning condition is present. Elster Solutions meter support software is used to select the individual warnings that will cause this error code to display. If the condition causing the warning clears, the error code will also clear.
DSP Download Error
There was an error downloading the DSP. Only set after all retries are exhausted. The current state of the flag will be cleared after the DSP has been successfully downloaded. ONLY APPLIES TO IP COMMUNICATION ONLY APPLIES TO IP COMMUNICATION This code indicates a CRC error is present in the meters ANSI C12.19 encryption key configuration table. Encryption keys are used for secure access to the meters data and configuration through the remote communication port. Contact Elster Solutions if this error is displayed on the LCD. FROM DAYLIGHT SAVINGS TIME OFF IN A3 HISTORY LOG This code indicates that the meter calendar has expired or is about to expire. The date at which this code appears is configurable using Elster Solutions meter support software. Program a new calendar using Elster Solutions meter support software. start time when the current TOU rate is overridden by the alternate TOU rate schedule stop time when the current TOU rate is overridden by the alternate TOU rate schedule This code indicates an incomplete attempt to flash the meter firmware. This code will exist on the meter if Elster Solutions firmware flash software did not complete the upgrade process. All meter functionality is halted until this error is resolved. Contact Elster Solutions to attempt repair. If this fails, the meter must be returned to the factory for repair or replacement. This code indicates an error is present in the meters security configuration. Contact Elster Solutions if this error is displayed on the LCD.
Elapsed Time, in Milliseconds, on Arrival at Primary Address Elapsed Time, in Milliseconds, on Arrival at Secondary Address Encryption key table CRC error
End Daylight Saving Time End Of Calendar Warning
Enter Tier Override Exit Tier Override ROM fail error
Security configuration error
Billing Data Write Warning Change Pending - After Switch Operation
Sean has to weigh in, Verify if this is also an artifact for REX2 .. May only be applicable for A3 IS THIS VALID ANYMORE SINCE EA_MS DOES NOT GO AHEAD AND SEND THE SWITCH COMMAND IF THE CAP IS STILL CHARGING? This is possibly an artifact as well as MAS does not send the command if cap is still charging
A3 ALPHA meter and gatekeeper Status Name - EA_MS Change Pending - Before Switch Operation
Description IS THIS VALID ANYMORE SINCE EA_MS DOES NOT GO AHEAD AND SEND THE SWITCH COMMAND IF THE CAP IS STILL CHARGING? Possibly an artifact - see comment above Returned only from short data format A3 ILNs (A3Ds). Maps to A3_STATUS.METER_ERROR in data format 3 and 5 and is a combination of A3 statuses compiled by the ILN board. The GK has reached the limit of the number of A3_ILNs it may register. Doesn't affect Rex; Just A3 Indicates that an item in a display list is invalid.
Meter Error
A3 Node Overflow Backup Battery Low Bad item in display list
Begin Daylight Saving Time Brute Force Read Button Press Clear Data
FROM DAYLIHGT SAVINGS TIME ON IN A3 HISTORY LOG FROM GK AUDIT LOG Button press clear data occurred.
Low Battery Warning
This warning code indicates a low battery voltage or missing battery. A3 ALPHA meters having a realtime clock require a battery to maintain date and time over an extended power outage. The meter should be deenergized and the battery should be replaced. Once the new battery has been installed and the meter is energized, the code is automatically cleared. FROM GK AUDIT LOG ? A GK has registered the maximum number of electric nodes it is configured to support? More than the system default number of nodes are assigned to a voltage read schedule on a single GK. Button press demand reset occurred.
Mark All Nodes as Unregistered Max number of nodes reached Max Number of Voltage Reading Nodes per Gatekeeper Exceeded Button Press Demand Reset
Canadian Tables Unlocked
For meters that are write protected, this indicates that the meter tables are temporarily unlocked.
DSP stop count exceeded error Meter in Test Mode
These only apply to REX meters, not REX2. I don't have a definition. Indicates the latched historical state of the test mode button. Intended to indicate tampering.
Meter Read
FROM GK AUDIT LOG
A3 ALPHA meter and gatekeeper Status Name - EA_MS Carryover Error
Description This code indicates a failure of a RAM checksum test on data stored in the meters volatile RAM during a power outage. When a loss of line voltage occurs, the meters RAM is maintained by the super capacitor and an optional battery. If both of these fail, the data stored in RAM is lost. Billing data is stored in nonvolatile memory and will still be available. A carryover error affects only the clock on meters that do not use the extended memory option. If extended memory is used, all load profiling and instrumentation profiling data (which is stored in extended memory) would be lost as the result of a carryover area. This code indicates that the Gatekeeper option boards batterybacked RAM was not maintained during a power failure. When there is a power failure, batterybacked RAM on the Gatekeeper option board is maintained by the A3 ALPHA meters super capacitor or battery. If both of these fail, the data stored in RAM is lost. Upon a subsequent power restoration, the Gatekeeper option board will rebuild the current billing data for all REX meters in the network. All previous billing data will be lost.
Carryover Error
Clock Error
This code indicates an error with the meters timekeeping ability. TOU features cannot be performed when time is lost. Billing data accumulated after this error occurs is stored in the default rate. This code indicates an error with the timekeeping ability of the Gatekeeper option board. The Gatekeeper option board can lose its real time clock if the A3 ALPHA meter has lost its timekeeping capability or if the Gatekeeper option board cannot communicate with the A3 ALPHA meter. When this condition is present, the Gatekeeper option board ceases LAN communications (modem communication, however, is still possible) and sets an Gatekeeper option board clock error.
Clock Error
Network Node Scan Configuration Error
FROM GK AUDIT LOG This code indicates a problem with the meters configuration or program. The meter can usually be reprogrammed using Elster Solutions meter support software to correct the errors. Can we say Metercat - that would be clearer to the customer? FROM GK AUDIT LOG This codes indicates a problem with the crystal oscillator. The A3 ALPHA meter must be returned to the factory for repair or replacement. CAN'T FIND IN ANY ORR FOR ANY A3 CAN'T FIND IN ANY ORR FOR ANY A3 CAN'T FIND IN ANY ORR FOR ANY A3
Network Ping Crystal Oscillator Error
Cumulative Power Outage Time Days since last demand reset Days since last pulse
A3 ALPHA meter and gatekeeper Status Name - EA_MS Demand Overload
Description This code indicates that the demand value exceeded the programmed overload value since the last demand reset. It is generally intended to inform a utility when the installation is requiring more power than the service equipment was originally designed to handle. If the demand overload value has been set lower than appropriate for the installation, the A3 ALPHA meter may be reprogrammed with a higher threshold value. This code indicates that the demand has exceeded one of the programmed demand thresholds. This warning follows the state of any relay programmed for demand threshold operation. It is set once the demand threshold has been exceeded and only cleared after one complete demand interval during which the threshold is not exceeded. FROM GK AUDIT LOG
Demand Threshold Exceeded
Failed EE Recovery
Failover to Secondary Comm. Address
DON'T THINK THIS IS IN 7.0???
Fixed repeater path Full Network Ping Finished Gatekeeper operation
FROM GK AUDIT LOG FROM GK AUDIT LOG This code indicates that the A3 ALPHA meter is operating as a Gatekeeper. While operating as a Gatekeeper, the A3 ALPHA meter is collecting and storing REX meter data using the Gatekeeper option board. This code indicates a problem with the Gatekeeper option boards configuration or program. Contact Elster Solutions if this error code is displayed on the LCD. GK auditlog FROM GK AUDIT LOG ICMP Traceroute initiated to WAN endpoint & route was different from previous. This flag is set whenever the collector cannot read the time from the A3, or there is a time error in the A3. This error will effectively shut down the lan, as the collector will not transmit when it has a time error. This error is a current state error, and will go away if the condition that caused it is fixed. Indicates a problem with the configuration in one or more tables. Indicates a crc error on one or more of the eeprom tables. This is an indication of the current state, and will be cleaed when the condition is cleaerd. This flag indicates that the battery backed up ram has been lost at some point. The registration information would have been recovered from eeprom, but all meter data would have been lost. This is a latched error that can be cleared by a clear lanob status (SF8) or a clear data (SF3). This indicates that there was a power up without a full power down. This is a latched error. It does not prevent anything from working, but could indicate a possible hardware problem, and a potential for data corruption. This indicates that there was a power up without a full power down. This is a latched error. It does not prevent anything from working, but could indicate a possible hardware problem, and a potential for data corruption
General configuration error
Generic Job Get Time from A3 ICMP Traceroute Change Detected ILC Clock Error
ILC Configuration Error ILC CRC Error
ILC Holdover Error
ILC Power Down Error
ILC Power Fail Save Fail
A3 ALPHA meter and gatekeeper Status Name - EA_MS ILC Profile Error ILC Shared Memory Error
Description This error indicates that there is either a memory config error (see shared memory error) or a profile config error that prevents load profile from running. This indicates that there is either a config that does not fit in shaerd memory, or that the shared memory configuration has changed without a clear data. In this state, the lan is shut down until the error is cleared. This indicates that the operation mode is not set to normal (it could be load tables, or comm only). The operational mode should only change during a flash upgrade operation. This code indicates that the meter engine program may be corrupt or is not executing correctly. This warning condition is typically triggered when the microcontroller reinitializes the meter engine. An unstable or noisy electrical environment at the A3 ALPHA meter installation can interfere with this operation. If the meter engine is successfully reinitialized, then the warning code will be automatically cleared from the LCD. If the code continues to be displayed on the LCD, the A3 ALPHA meter should be returned to the factory for repair or replacement. This code indicates the meter had an internal communication error. The A3 ALPHA meter must be returned to the factory for repair or replacement.
ILC Shut Down
Improper meter engine operation warning
Internal Communication /I2C Error
Internal Meter Warning Internal meter warning (latched) IP Statistics - Bytes Received IP Statistics - Bytes Transmitted IP Statistics - IP Checksum Errors IP Statistics - IP Fragments IP Statistics - IP Options IP Statistics - IP Packets Dropped IP Statistics - IP Packets Received IP Statistics - IP Packets Routed IP Statistics - Net Directed Broadcast Packets Received IP Statistics - Net Directed Broadcast Packets Transmitted IP Statistics - Packets Received IP Statistics - Packets Transmitted IP Statistics - Transmit Errors IP Statistics - Unicast Packets Received IP Statistics - Unicast Packets Transmitted IP Statistics - Unknown Protocol
Support note: Cause RMA. Set if stack overflow (FW has overrun bounds of memory). Support note: Cause RMA. Set if stack overflow (FW has overrun bounds of memory).
A3 ALPHA meter and gatekeeper Status Name - EA_MS LAN Performance Statistics Reset Line Frequency Warning
Description EA_MS sent a command to a GK to reset the lan performance statistics for all its nodes. If a meter is configured to use the line frequency instead of the crystal oscillator as the time base, this code indicates that the line frequency is off by 5% of its programmed setting. When this condition occurs, the meter switches timekeeping to the crystal oscillator.
Node Scan Request Number of configuration sessions port 0 Number of configuration sessions port 1 Number of Hops on Arrival at Primary Address Number of Hops on Arrival at Secondary Address Number of logons port 0 Number of logons port 1 Number of manual demand resets
FROM GK AUDIT LOG Running statistics on the A3 itself. WAN Running statistics on the A3 itself. LANOB Data returned from TRACEROUTE (?) Data returned from TRACEROUTE (?) Running statistics on the A3 itself. WAN Running statistics on the A3 itself. LANOB Total number of demand resets performed by push button or by execution of a Reset Demand task or by a calendar event (Special Dates component). This value is reset to zero by executing a Clear Data task. Invalid password for function or just invalid password. WAN Invalid password for function or just invalid password. LANOB ?) Sean for clarification. This code indicates that one or more PQM tests have detected a value outside the programmed thresholds. Use the meter system instrumentation displays or Elster Solutions meter support software to gain additional information on the specific PQM test causing the problem. When EA_MS sends command to optimize network. EA_MS sends command to start OTA; GK logs the action Only applies to A3s or GKs with ITM outage modems. Indicates the battery used to initiate an outage call-in is low and needs to be replaced.
Number of security failures port 0 Number of security failures port 1 One or More PQM Tests Failed
Optimize Network OTA Flash Outage Modem Battery Low
Outage Modem Checksum Error
Only applies to A3s or GKs with ITM outage modems. Indicates ???
Procedure Executed Profile Read Outage Modem Missing
Check with Sean; Don't think it applies to Rex FROM GK AUDIT LOG. Profile is being read. Only applies to A3s or GKs with ITM outage modems. Indicates ???
RAM Failure
Error can be cleared w/ reprogramming, but RMAing is recommended
A3 ALPHA meter and gatekeeper Status Name - EA_MS Recover From EE Registered Memory Error Outage Modem Self Test Error
Description FROM GK AUDIT LOG. EE copy pushed into RAM. Error can be cleared w/ reprogramming, but RMAing is recommended Only applies to A3s or GKs with ITM outage modems. Indicates ???
Partial Outage - Phase A Partial Outage - Phase B Partial Outage - Phase C Password table CRC error
Phase voltage error. Indicates that a recognized phase voltage is below its low voltage threshold. Phase voltage error. Indicates that a recognized phase voltage is below its low voltage threshold. Phase voltage error. Indicates that a recognized phase voltage is below its low voltage threshold. This code indicates a CRC error is present in the meters ANSI C12.19 password configuration table. Contact Elster Solutions Metering if this error is displayed on the LCD. A pending table change, such as Calendar or TOU, activated. Indicates the total number of times there was a qualifying sag event for each phase Indicates the total amount of time there was a qualifying sag event for each phase Status. No voltage on Phase A. On NMGKs with battery backup, this will be set when line is lost. This warning code indicates that reverse energy flow has been detected equivalent to twice the Kh in a single demand interval since the last demand reset. It may be an indication of tampering with the A3 ALPHA meter installation. If reverse energy flow is expected, then this warning code can be disabled through Elster Solutions meter support software. If the service being metered is not expected to return energy to the utility, further investigation is required. In some cases, it may be necessary to return the A3 ALPHA meter to the factory for repair or replacement. FROM GK AUDIT LOG. RAM copy putting back into EE. Part of Upgrade or troubleshooting exercise. This code indicates a problem with the meters program. If this code is displayed on the LCD, the REX meter should be returned to the factory for repair or replacement.
Pending Table Activated Phase A Cumulative Sag Count Phase A Cumulative Sag Timer Phase A Missing Reverse Rotation
Re-write EE Backup ROM checksum error
Phase A Sag Phase A Sag Timer Phase B Cumulative Sag Count Phase B Cumulative Sag Timer Phase B Missing Phase B Sag Phase B Sag Timer Indicates the total number of times there was a qualifying sag event for each phase Indicates the total amount of time there was a qualifying sag event for each phase
A3 ALPHA meter and gatekeeper Status Name - EA_MS Phase C Cumulative Sag Count Phase C Cumulative Sag Timer Phase C Missing Phase C Sag Phase C Sag Timer Potential Indicator Warning
Description Indicates the total number of times there was a qualifying sag event for each phase Indicates the total amount of time there was a qualifying sag event for each phase
This code indicates that one or more of the phase potentials are missing or below the defined phase indicator threshold. This code will display at the same time as one or more of the potential indicators blink. This code indicates that the data saved in the nonvolatile EEPROM during a power fail may be invalid. This error will be displayed when power is restored to the meter, and a self check has discovered an error with the EEPROM data. The A3 ALPHA meter must be returned to the factory for repair or replacement. This code indicates a possible error in the A3 ALPHA meters programming. This code might appear if a communications interruption occurs during meter programming. Depending on which area of the meter is affected, billing data may not be reliably accumulated while this error condition exists. The push buttons and optical port will continue to function normally.
Power fail data save error
Table CRC Error
Table Written Tamper Detected Indicates possible tampering with the meter because of the number of attempts to communicate with the meter using an invalid password
Tariff EE Read Error Tariff EE Write Error Indicates possible corruption of the tariff data. This may occur if a communication session is abnormally terminated while writing data to the billing registers (for example, register edit).
Test Mode Started Test Mode Stopped Tier Override Warning Power fail data save error
The meter was put into test mode. The meter was taken out of test mode.
This code indicates that the data saved in the Gatekeeper option boards nonvolatile memory during a power failure may be invalid. This error will be displayed when power is restored to the meter if a self check has discovered an error with the Gatekeeper option board's memory. Contact Elster Solutions if this error code continues to be displayed on the LCD. FROM GK AUDIT LOG
Time Broadcast
A3 ALPHA meter and gatekeeper Status Name - EA_MS Time Changed Power Outage Detected
Description A time change occurred in the meter. A3 outage read from A3 event log
Power Restoration Detected
A3 restoration read from A3 event log
Remaining Charge Time - After Switch Operation
The REX meter with disconnect has a capacitor that is used to power the disconnect switch. After a switch operation or power up, it takes the capacitor 4 minutes to charge so that the switch can be operated. This is what the time left is on the 3rd communication of a disconnect/connect command. The REX meter with disconnect has a capacitor that is used to power the disconnect switch. After a switch operation or power up, it takes the capacitor 4 minutes to charge so that the switch can be operated. If you try to connect or disconnect the meter before the capacitor is charged, this value let's you know how much time is remaining before the capacitor will be charged and you can control the switch. This is read on the 1st communication in a connect/ disconnect. This event is read from the GK Module audit log and indicates that the GK started a scheduled read. Season change occurred.
Remaining Charge Time - Before Switch Operation
Scheduled Read Season Changed
Self Read Service Current Test Failure
Self Read Occurred This code indicates that the most recently performed service current test has failed.
Service Voltage Test Failure
Indicates the last occurrence of service voltage test failed.
Shared memory error Single Node Scan Table CRC Error Unknown LAN node discovered Unregister All Nodes
This code indicates a problem exists in the shared memory area. Contact Elster Solutions if this error code is displayed on the LCD. FROM GK AUDIT LOG This code indicates an error in the Gatekeeper option boards programming. Contact Elster Solutions if this error code is displayed on the LCD. FROM GK AUDIT LOG FROM GK AUDIT LOG
A3 ALPHA meter and gatekeeper Status Name - EA_MS Unregister Lan Branch Update configuration Voltage Reading schedule in GK not complete Voltage Reading Time Exceeded FROM GK AUDIT LOG FROM GK AUDIT LOG
Description
The GK has not finished reading voltage from its meters by the time the EA_MS voltage schedule reads the GK. If this happens consistently, you need to modify the EA_MS voltage schedule to run later and allow the GK more time to complete its voltage reads. Indicates that the display is locked by a warning condition.
Warning Locked on Display WIC Option Board C12 Master Failure WIC Option Board Configuration Error WIC Option Board Database Failure WIC Option Board EEPROM CRC Error WIC Option Board Hardware Failure WIC Option Board Network Failure WIC Option Board Protocol Failure WIC Option Board Protocol Failure WIC Option Board Protocol Table Failure WIC Option Board Protocol Table Failure WIC Option Board ROM Checksum Error WIC Option Board ROM Checksum Error WIC Option Board Table Error WIC Option Board Table Error XMB Expected but Missing
Indicates the extended memory option board is expected but the meter can no longer communicate with it.
REX/REX2 status descriptions
REX/REX2 Status Name Armed for Demand Reset
Description This code indicates that the meter has been scheduled to perform a demand reset at the next midnight crossing. This code is displayed when it receives a command to perform a demand reset from the network. This code remains on the display until the next mi This code indicates that a specified meter configuration table within the meter has been written, indicating possible tampering with the meter programming. This code is cleared by a demand reset, clear status, clear billing data, or clear data command.
config table write warning
REX/REX2 Status Name Configuration Error
Description This code indicates a problem with the meters configuration. If the error continues after reprogramming, the meter should be returned to the factory for repair or replacement. This flag is set if the demand limiting lockout condition has been detected. The number of demand limiting operations has met or exceeded the number allowed for a given period of time. The service disconnect switch is opened permanently and requires a clo This code indicates that the demand has exceeded the programmed demand threshold. It is displayed once the demand threshold has been exceeded and is cleared by a demand reset, clear status, clear billing data, or clear data command. If a node in the EA_LAN is a repeater, this is the number of other nodes that depend on it for communication with the GK. This code indicates that the service control switch is open. The service control switch can be opened when either of the following occurs: the REX2 meter has received a command to disconnect the service or the meter is configured to open the switch when t Same as Disconnect Relay Open, but it was read after a disconnect or reconnect operation - a disconnect/reconnect is 3 communications from EA_MS to the meter 1 to check status, 2 to send the switch command, 3 to read status again and get meter reading. This code indicates the meter had a problem accessing its nonvolatile EEPROM. Generated by all meters
demand limit lockout
Demand Threshold Exceeded
descendants Disconnect Relay Open
Disconnect Relay Open - After Switch Operation
EEPROM Access Error
elapsed time for pass-through operation (msec)
This code indicates the meter had a problem accessing its nonvolatile EEPROM. Generated by all meters This flag is set if the meter has an encryption key or flash image to be transferred to an external 900 MHz device (gas module, water module, in-home EA device, etc.). The flag is cleared when the transfer has completed successfully. The meter firmware has been updated - it is at a new version. This flag is set if the meter has a firmware image to be transferred to an external 900 MHz device (gas, water, or in-home device) or to an option board. The flag is cleared when the transfer has successfully completed This code indicates that the meter engine program or radio microprocessor may be corrupt or is not executing correctly. If the code is displayed on the LCD, the REX2 meter should be returned to the factory for repair or replacement. This flag is only set when the disconnect switch is open and the disconnect switch option board indicates that there is voltage present on the load side of the switch. This flag contains the latched status, indicating if voltage has been present anytime s This flag is only set when the disconnect switch is open and the disconnect switch option board indicates that there is voltage present on the load side of the switch. This flag contains the current status. If this flag is set, the meter will not close th
external operation pending
Firmware upgraded flash transfer pending
Improper meter engine operation error
Latched Load Side Voltage Present
Load Side Voltage Present
REX/REX2 Status Name Load Side Voltage Present - After Switch Operation
Description same as load side voltage present, but it was read after a disconnect or reconnect operation - a disconnect/reconnect is 3 communications from EA_MS to the meter 1 to check status, 2 to send the switch command, 3 to read status again and get meter readi same as load side voltage present latched), but it was read after a disconnect or reconnect operation - a disconnect/reconnect is 3 communications from EA_MS to the meter - 1 to check status, 2 to send the switch command, 3 to read status again and get me This is the current status of load side voltage after EA_MS sent a service connect or disconnect command to the meter, regardless of the state of the switch. a disconnect/reconnect is 3 communications from EA_MS to the meter - 1 to check status, 2 to send This is the current status of load side voltage before EA_MS sent a service connect or disconnect command to the meter, regardless of the state of the switch. a disconnect/reconnect is 3 communications from EA_MS to the meter - 1 to check status, 2 to sen - Metering engine error - The meter was unable to successfully write one or more registers into the meter chip. REX2 meter removed (REX2 last gasp with tamper flag set) This code indicates that there is load side voltage present when the service control switch is open. This code can indicate that one of the following conditions exist:a malfunction occurred in the service control switch or the load side is receiving volta The number of momentary outages a REX2 has experienced.. The value rolls over at 255. A momentary outage is one that is <= than the Momentary Outage Time on the REX Meter Programming Form. EA_MS detects a new node registered to a GK. EA_MS reads the GK and determines a node that used to be registered to that GK is no longer registered to that GK. same as no voltage detected with disconnect closed This code indicates that there is no load side voltage present when the service control switch is supposedly closed. This code can indicate a malfunction with the service control switch. If this code is displayed, contact Elster. No load side voltage when service control switch is closed - this flag is set while the meter detects no load side voltage on the disconnect switch with the disconnect switch in the closed state. This flag is current, not latched. - it was read after a d When EA_MS reads LAN performance from a GK, it generates this event if any node's performance is lower than a configurable threshold in EA_MS. Default threshold is 80%. The level of a node on the EA_LAN - the number of "hops" to its GK. Internal identifier used within the EA_LAN for a repeater The number of times the gatekeeper has tried to read registers from this node since LAN communications performance was reset. This is typically incremented every 4 hours when the GK reads registers from all its nodes. The number of times the gatekeeper was able to read registers from this node since LAN communications performance was reset.
Load Side Voltage Present (Latched) - After Switch Operation
Load Side Voltage Present (Raw) - After Switch Operation
Load Side Voltage Present (Raw) - Before Switch Operation
meter chip error Meter Removal Meter Reports Load Side Voltage Detected With Disconnected Service
momentary outage count
Network Node Registration Detected Network Node Unregistration Detected No voltage after connection of service No Voltage Detected with Disconnect Closed
No Voltage Detected with Disconnect Closed After Switch Operation
Node LAN Performance Lower Than Threshold
node level node repeater id Number Of Read Attempts
Number Of Read Responses
REX/REX2 Status Name Outage
Description GK FW 6.x. Outage detected in GK outage table from REX/A3_ILN last gasp. Time stamp is newer than threshold. REX2 does not have tamper (tilt) flag set.
Outage Detected from LP Data Outage Detected in exception log phase A low potential phase C low potential Possible Load Profile Gap detected Power Status Confirmed (Restoration)
Outage detected from LP data in REX2. Could also be from event only LP. REX outage detected in GK exception log (GK 5.x or less), or outage detected for a meter not registered to that GK (GK 6.x or higher) This flag is set if a phase A voltage is below the configurable phase voltage threshold. This flag is set if a phase C voltage is below the configurable phase voltage threshold. EA_MS has detected a gap in the LP data between scheduled reads. This is the result of the most recent successful Power Status Check run from EA_MS that included this meter. The meter communicated, so it has power. This is the result of the most recent unsuccessful Power Status Check run from EA_MS that included this meter. The meter did not communicate, so EA_MS does not know if the meter has power or not. If there is a conflict in the radio configuration settings this bit will be True. Examples include: If either the LAN or IN HOME DISPLAY is set for HIGH BAND and the CHANNEL LIST contains a channel above 31. True if registered memory has a CRC error on power restoration This code indicates that the data saved in nonvolatile EEPROM during a power fail may be invalid. This error will be displayed when power is restored to the meter and then a self check has detected an error with the EEPROM data after a power fail data sav If a node in the EA_LAN is a repeater, this is the number of other nodes that depend on it for communication with the GK that are also repeaters Restoration detected in GK outage table from REX/A3_ILN restoration exception. Time stamp is newer than threshold. Restoration detected from REX2 LP data. Could also be from event only LP. Restoration detected in GK exception log (GK 5.x or less), or restoration detected for a meter not registered to that GK (GK 6.x or higher) This code indicates that reverse energy flow has been detected that is equal to or greater than the programmed reverse energy threshold. If reverse energy flow is expected, then this warning can be disabled. If the service being metered is not expected to Old outage detected in outage log (REX2/A3 Node last gasp, older than threshold, no tamper) Old restoration detected in outage log (REX2/A3 Node last gasp, older than threshold) The number of sustained outages a REX2 has experienced. The value rolls over at 255. A sustained outage is one that is > than the Momentary Outage Time on the REX Meter Programming Form. Cumulative time of sustained outages
Power Status Unknown (Possible Outage)
radio config error
Registered Memory Error registered memory/power fail data save error
repeater descendants Restoration Restoration Detected from LP Data Restoration Detected in exception log reverse power warning
Stale Outage Data Detected Stale Restoration Data Detected sustained outage count
sustained outage duration (secs)
REX/REX2 Status Name table access warning
Description This code indicates possible tampering with the meter because a specified number of invalid optical passwords or invalid LAN encryption keys were received by the meter. The meter has separate counters for the optical port and the radio: if either count ex This code indicates a possible error in the REX2 meters programming. Depending on which area of the meter is affected, billing data may not be reliably accumulated while this error condition exists. The REX2 meter should be returned to the factory for re This code indicates that the meter detected a tilt condition (vibration) in conjunction with a power outage. This code is cleared by a demand reset, clear status, clear billing data, or clear data command. The communication performance success percentage. Number Of Read Responses / Number Of Read Attempts This code indicates that the TOU schedule stored in the REX2 meter is out-of-date. When the gatekeeper detects this status code, the gatekeeper will re-send the current TOU schedule to the REX2 meter. This code is cleared automatically when the meter rece
Table CRC Error
Tilt warning
Total Read Success Rate TOU schedule out-of-date
uncontrolled service connect/disconnect detected EA_MS generates this when it reads the registers from a meter (which includes the disconnect switch state), and the disconnect switch is not in the state (open or closed) that EA_MS expects. This could occur if someone had used Metercat or EA_Inspector i voltage monitoring max event This code indicates that the meter has detected a voltage that exceeds a programmable maximum voltage threshold for a duration greater than or equal to a programmable maximum voltage time. This code indicates that the meter has detected a voltage that drops below the minimum voltage threshold for a duration greater than or equal to a programmable minimum voltage time. This code is cleared by a demand reset, clear data, or clear status comma
voltage monitoring min event
494
D. Voltage reading statuses
Voltage reading statuses
Figure D-1. Voltage Reading Performance - by meter

When viewing the Voltage Reading Performance report by meter, select a meters read performance to view the Gatekeepers Read table. The Status column can display the following statuses: Voltage Reading Performance report Status Other
Condition no voltage readings in gatekeeper
Reason gatekeeper has not started collecting voltage data possibly because voltage reading schedule ran before gatekeeper was synchronized with EA_MS gatekeeper is still reading voltage data from the meters gatekeeper has not read the meters voltage data possibly because the meter is an orphan.
Voltage Pending LAN Communication Lost
voltage reading is pending in gatekeeper LAN communication is lost
495
D. Voltage reading statuses
Voltage Reading Performance report Status Old Data
Condition Read window in gatekeeper does not match voltage reading schedule
Reason gatekeeper voltage schedule has completed but EA_MS voltage reading schedule is still running gatekeeper is not synchronized with EA_MS to update voltage schedule configuration options (see EA_MS Installation and Administration Guide) voltage reading is only supported by gatekeepers with FW 6.0 or higher EA_MS has the meter as orphan meter exception reading voltage table in gatekeeper
Incompatible gatekeeper
meter on voltage reading schedule is registered to a gatekeeper with FW ver. prior to 6.0 orphaned meter failure to read voltage table in gatekeeper
Orphaned meter WAN Communication Lost Success
node jumped to another gatekeeper FW 6.0 If at least one meter on the new gatekeeper is on voltage reading schedule, then if node jumps before gatekeeper voltage reading schedule runs, voltage data will be collected successfully voltage reading schedule start time is before gatekeeper schedule start time If the gatekeepers voltage reading schedule is delayed due to another overlapping schedule run, then all nodes will report status as delayed
Voltage Read Schedule Delayed
496
E. Reading components
Reading components
See Table 8-1 on page 196 for details on specific components.
Registers
497
Load Profile
HTML report of Load Profile
499
Events and Exceptions
501
LAN Performance
502
Reset Communication statistics
Registers from Gatekeeper
503
Read and Clear Water Data from Gatekeeper
Read and Clear Gas Data from Gatekeeper
504
Load Profile from Gatekeeper
HTML report of Load Profile from Gatekeeper
505
Clear A3 Statuses
Clear Sag Statuses
506
Load Profile (last 24 hrs)
HTML report of Load Profile (last 24 hours)
507
Sag Log
508
Sag Log Counter
Load Profile (last one week)
509
HTML report of Load Profile (last one week)
ICMP Ping
510
Present Values
511
Health Check A3
Health Check ILC
512
Health Check WIC
513
ICMP Ping
ICMP Traceroute
514
Index
Index
Symbols
# Meters 209 # of Attempts 329, 330 # of Success 329, 330 % Meters Read 212 % Success 214, 329, 330
Numerics
1xRTT WIC 89 900 MHz 89 900 MHz network 337
A
account defined 28 Account Enabled 377 Account Name 71, 79, 88, 159, 170, 214, 215, 231, 232 Account No. 71, 79, 88, 118, 148, 150, 170, 251 Account Number 214, 215, 231, 232 action buttons 49 Activity completed 46 Activity monitor 47 copy button 49 removing an activity 49 viewing an activity 48 Activity Monitor Refresh Interval 378 Actual Reads 214 adding to schedule 239 Advanced Metering Functions 111 Alarm Conditions 48 alarm, def. 457 Alternate Cost Delivered 277, 279 AMR System Administrator AfterInstall 378 AMRDEF XML 16 Area 276, 278 assigning schedule 82 Audit user 357 Avg Session Time 329, 330
Billing Registers 72 Billing Schedule 79, 88 billing schedule impact on synchronization schedule 249 block interval demand 392 body area 41 Broadcast Details 276, 278 Button calendar 51 copy 49 button Cancel 49 Copy 49 Create 49, 50 Delete 49, 50 Edit 49 Bytes Received 329, 330 Bytes Sent 329, 330
connecting service troubleshooting 129, 130 contact phone number 60 technical support 60 Copy button 47, 49 Correcting errors 47 Count 360 Create button 49, 50 creating data set 195 multiple meters 90 schedule 245 user 376 cumulative maximum demand 31 Customer Serial Number 72
D
Dashboard Preferences Favorites configuration 62 Data Components 95, 112, 121, 195 Data Set 79, 88 data set creating 195 defined 30 Delete 203, 264 deleting 203 New 195 retrieving 192 view 193, 256 View All 193, 256 Data Set Name 72 date and time selecting 51 Date Range 329 Default Company 377 default TOU schedule changing 262 overwriting 263 Delete 49 data set 203, 264 meter 92 schedule 252 Delete button 49, 50 deleting data set 203 schedule 252 Demand Forgiveness Time 72 Demand Interval 71 demand reset 32, 111 demand reset count 32 demand response 17
C
calendar 51 Cancel button 49 CDMA WIC 89 Change Password user 383 changing assigned data set 239 default TOU schedule 262 meter information 79 password 383 schedule 237 TOU schedule 263 user information 376 Chart button 225 CIS file 136 Clear Date/Time button 51 Clock 119, 148, 151 coincident demand 31 Comm Media 71, 79, 89, 170 Comm Mode 71, 79, 89, 170, 329, 330 Comm Number 71, 79, 89, 170 Comm Template 71, 79, 89, 330 communication Meter 328 Communication Port Summary 330 Companies 377 Completed 359 configuring multiple meters 90 connect errors 129
B
batch import 90 Billing 209 billing data 30 Billing Password 71, 79, 86 billing read 121
515
Index
Demand Subinterval 71 Demand Threshold 72 Demand Threshold Penalty 72 Description 71, 79, 89, 148, 150, 195, 209, 212, 231, 246, 251 Detecting errors 47 Detecting problems 47 Device Number 71, 89 Dial Time 329, 330 Direction 79, 125, 148, 351, 353 disconnect errors 133 Discovered At 175, 188, 339 Display Calendar button 51 Display Parameters 360 DR Program 276, 278 DST 23, 71 Duration 276, 278
Filename 141, 231 Firmware Revision 72 Firmware Version 72 First Name 377 forcing synchronization schedule 252
G
Gas Meter Read History Report 191 Gatekeeper Gas Nodes Report 189 Gatekeeper Name 175, 176, 187, 189, 339, 346, 349, 351, 353 Gatekeeper Water Nodes Report 176 Generation Price 277, 279 Generation Ratio 277, 279 GMT 51 GPRS WIC 89 Greenwich Mean Time 51
E
EA_MS how to use 26 operation overview 26 starting 38 EAGas 86 EAWater 86 Edit 49 Edit button 49 editing user information 376 Elapsed 360 email technical support 60 Employee ID 377 EnergyAxis Broadcast 96, 113, 198 EnergyAxis Technical Support 60 Error 47, 232 Error detection 47 Error messages 53 error, def. 457 Ethernet WIC 89 event, def. 457 Events and Exceptions 96, 113 exchanging TOU schedules 259 Executing the activity 46 Execution Summary 214
H
Health Check A3 97, 105, 113, 199 Health Check ILC 97, 105, 113, 199 Health Check WIC 97, 105, 113, 200 Help menu 55 Hourly offset 51
Last Read Date 156, 167, 177, 190, 335, 340, 341 Last TOU Read Date Time 355 Latitude 79 LDAP 25, 376, 383 life cycle meter 33 line voltage 22 load control device 17 load profile viewing data 148 Load Profile Divisor 72 Load Profile Summary 151 load voltage present 129 Locale 377 Location 214, 215 logon name 38 logon password 383 changing 383 Longitude 79 LP Channels 72 LP Interval 71
M
marriage file 36, 85, 134 Max Days for LP 71 maximum demand 31 Maximum Pages 377 Measurement Period 125, 148 menu bar 40 message Page has Expired 39 Message type symbols 47 error 47 information 47 warning 47 Messages error 53 Meter communication 328 meter Assign 82 defined 26 Delete 92 Installed 166 Inventoried 165 life cycle 33 Modify 79 New 86 Not Read 155 On Request Read 95 read and reset 111 Read Configuration 108 Read Time 107 Readings 138 Remove 82 removing from field 90 removing, field 90 retrieving 68 Set Time 110 View 72 viewing 71
I
ICMP Ping 97, 113, 200 ICMP Traceroute 97, 114, 200 ILC Audit Log 97, 114 ILC audit log 198 Import CIS File 136 Import Marriage File 135 Import WC Activation File 137 Information symbol 47 in-home display 17 Installation Date 156, 167, 177, 190, 335, 340, 341 Installed 35, 166 instrumentation values 33 Internet Explorer 16 interval data 30 Inventoried 34, 35, 165 IP 89
K
Kh 72
F
failed, meter busy 101 failed, meter reading 101 Favorites configuring 61 Dashboard Preferences 62 Monitored Event Categories 62 Upcoming Schedules 62 Feeder 276, 278 Field Install Date 71, 79, 89, 156 Field Removal Date 71, 170 File Creation Date 231 File Location 212, 246
L
LAN ID 71, 156, 165, 167, 349 LAN Information 352 LAN Information Report - Gatekeeper 353 LAN Information Report - REX 354 LAN Performance 97, 114 Last Connect Date 335, 340, 341 Last Connect Time 71 Last Execution 209, 212 last gasp 19 Last Name 377 Last Programmed 71
516
Index
meter alarms 23 meter busy 101 Meter Comm Summary 330 Meter Communication Summary report 328, 329 meter local time 53 Meter Name 71, 79, 86, 118, 139, 156, 159, 165, 167, 170, 176, 189, 214, 215, 231, 232, 237, 328, 335, 340, 341, 349, 351, 354 Meter Reading 125, 148 Meter Readings 231 meter readings report 230 Meter Statuses Report 161 Meter Time 119, 148, 151, 251 Meter Type 71, 86, 118, 148, 150, 156, 165, 170, 176, 189, 251, 329, 340, 341 Metercat TOU schedule 28 Meters 213 meters supported 27 Meters Not Read 214 meters not read report 230 Middle Initial 377 Model 71 Modify 237 meter 79 schedule 237 modifying meter information 79 Most Recent LAN Performance 355 multiple meters 90
O
Observes DST 119, 148, 151, 251 On Request Read 95 Operating Territory 71, 79, 89 optimize LAN 111 Orphaned As Of 341 Orphaned Node report 341 outage notification 19 Overall Summary 329 overwriting default TOU schedule 263 Owner Name 72
P
Password 377 password 38, 383 changing logon 383 Password Expiration 377 PDF report 54 Pending Synchronization Report 350 Performance 209 performance schedule 213 Performance report 213, 237 Power Status Check 21 Present Values 98, 115, 199 Price 277, 278 Price Ratio 277, 278 Problem indicators 47 programmable thermostat 17 Provider ID 276, 278
meter statuses 161 Meters Installed 167 Meters Inventoried 165 Meters Not Read 156 meters not read 230 PDF 54 selecting item 50 Report buttons 209 requirement Internet Explorer 16 reset event log 111 reset exception log 111 reset LAN performance statistics 111 Reset LANOB Events 99, 116, 199 Resubmit 236 schedule 235 Resubmit report 237 resubmitting schedule 235 retrieving data set 192 meter 68 schedule 204 REX Communication Report 347 REX meter 134, 346 time of use rates in 18
S
Sag Log 100, 116, 198 sample marriage file 400 schedule Assign 82 changing 237 creating 245 defined 28 Delete 252 Modify 237 New 245 performance 213 Remove 82 Resubmit 236 resubmitting 235 retrieving 204 synchronization, about 29 View All 207 viewing 212 Schedule Date 246 Schedule Dates 212, 246 Schedule Information 212 Schedule List 209 Schedule Name 72, 83, 212, 231, 245 Schedule Run List report 213, 231 schedule time 53 Schedule Type 245 screen resolution 16 season change 32 Security Profile 378 selecting date and time 51 Serial Number 71, 86, 156, 165, 167, 177, 189, 214, 215, 231, 232, 335, 340, 341, 349
Q
Quality Flags 119, 120
N
Name 209 data set 195, 262 navigation bar 40 network logon 376 New 195 data set 195 schedule 245 user 376 new meter 86 Next Execution 209 node previous season and TOU schedules 244 status 337 Node Gatekeeper Association 71 Node Jumping History 345 Node Jumping History report 346 Node LAN Performance Report 348 Node Registration Date 335, 340 node registration status 338 Not Read 155 Number of Meters 231 Number of Meters Read 214
R
Read Attempts 349 Read Configuration 108 Read home area network status 99, 115 Read Responses 349 Read Status 237 Read Time meter 107 Read Window 212, 245 Readable 35 Reading Properties 148 Readings 138 Refresh Interval 378 Registered Node report 339 Registered Nodes 338 registration status 337 Registration Date 156, 167 removing from schedule 239 meter 90 removing schedule 82 report Events 156, 160, 161 meter readings 230
517
Index
Server Time 119, 148, 151, 251 server time 53 service control switch 14 Session Timeout 377 Set Time 110 Show Time Stamp Offsets 377 Show Time Zone 377 Show Time Zone in Time Stamp 377 Site ID 71, 79, 88, 148, 150, 214, 215, 231, 232, 251 Site Location 71, 79, 88, 231, 232 Special Read for Billing 121 Start Date 231 Start Time 359 starting EA_MS 38 State 359 States work status indicator 46 Status 360 status node 337 status, def. 457 Style Number 72 Submitted 359 Success Rate % 349 supported meters 27 switching TOU schedules 259 Symbols message types 47 synchronization forcing 252 schedules 29 summary report 249 synchronization schedule file 250 impact of billing schedules 249 synchronization, on request 111 Synchronize changes with EA_MS 252 synchronize, on request 111
Time stamp 125, 148 time synchronization 23 Time Zone 71, 79, 89, 212, 246, 377 Time zone 51 time zone 23, 53 tool bar user actions 49 workitem actions 48 Total Session Time 329, 330 TOU in REX meter 18 TOU data and previous season node 244 TOU Schedule 71, 79 TOU schedule 28 changing 263 defined 28 Metercat 28 troubleshooting connecting service 129, 130 Type 167, 335, 349
V
values instrumentation 33 View meter 71 schedule 212 view PDF report 54 View All 207 data set 193, 256 data sets 193, 256 schedules 207 users 374 View Latest Performance Report 237 View My Account 383 user 383 View Schedule Information 214 View Schedule report 212 View Schedule Runs 212 viewing all system users 374 meter information 72 schedule 212 schedule run list 231 synchronization schedule file 250 your user information 383 Voltage 100, 116, 198 VT Ratio 71
U
Unknown Gas Node Report 187 Unknown LAN ID 175, 188, 339 Unknown Node report 339 Unknown Nodes 338 Unknown Water Node Report 175 Unrestricted Password 71, 79, 86 UOM 125, 148 user actions, buttons 49 Change Password 383 creating 376 New 376 View My Account 383 User Actions Copy 386 Create 376 Delete 386 Edit 385 User Audit report 357, 358 user authentication 376 user information changing 376 viewing 383 User Logon 376 User Template 377 user time 53 users View All 374 Users report 374 using Back button 39 calendar 51 Forward button 39
W
Waiting for user input 46 Waiting on the system 46 Warning 47 warning, def. 457 Water Meter Read History Report 178 Work Status Indicator 46 Work status indicator 47 activity completed 46 states 46 waiting on the system 46 work status indicator waiting for user input 46 Workflow ID 359 Working status indicator executing the activity 46 workitem actions, buttons 48
T
Terminated 36 Termination date 208 three-way association 26 Tier 125, 148 Tier Mapping 276, 278 time meter local 53 schedule 53 server 53 user 53 time management 23 Time Stamp 349
X
XML 22 AMRDEF 16
Z
ZigBee 14
About Elster
Elster (NYSE: ELT) is one of the world's largest electricity, gas and water measurement and control providers. Our offerings include distribution monitoring and control, advanced smart metering, demand response, networking and software solutions, and numerous related communications and services - key components for enabling consumer choice, operational efficiency and conservation. Our products and solutions are widely used by utilities in the traditional and emerging Smart Grid markets. Elster has one of the most extensive installed revenue measurement bases in the world, with more than 200 million metering devices deployed over the course of the last 10 years. It sells its products and services in more than 130 countries across electricity, gas, water and multi-utility applications for residential, commercial and industrial, and transmission and distribution applications.
ALPHA, ALPHA Plus, REX, TRACE and EnergyAxis are registered trademarks of Elster. AlphaPlus, REX2, REX2-EA, Route Manager, IP AxisLink, AGInode and Metercat are trademarks of Elster. Other products may be trademarks and/or registered trademarks of their respective owners.
Elster 208 S Rogers Lane Raleigh, NC 27610-2144 United States Technical Support T +1 800 338 5251 (US toll free) +1 919 212 5068
energyaxis.support@us.elster.com www.elster.com
2011 by Elster. All rights reserved. No part of this software or documentation may be reproduced, transmitted, processed or recorded by any means or form, electronic, mechanical, photographic or otherwise, translated to another language, or be released to any third party without the express written consent of the Elster. 15.July.2011

Ea MS

Загружено:

Сведения о документе

Оригинальное название

Авторское право

Доступные форматы

Поделиться этим документом

Поделиться или встроить документ

Параметры публикации

Этот документ был вам полезен?

Это неприемлемый материал?

Авторское право:

Доступные форматы

Ea MS

Загружено:

Авторское право:

Доступные форматы

EnergyAxis Management System Release 7.

EA_MS Release 7.6 User Guide

New features in Rel. 7.6 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11

EA_MS Release 7.6 User Guide

EA_MS Release 7.6 User Guide

EA_MS Release 7.6 User Guide

Viewing a gatekeepers gas meters reading history . . . . . .190

EA_MS Release 7.6 User Guide

All . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 282 Confirmed . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 282 Unconfirmed . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 283

EA_MS Release 7.6 User Guide

322 323 323 324 324

16 Network Management. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 388 Optimizing a gatekeepers LAN . . . . . . . . . . . . . . . . . . . . . . 388

EA_MS Release 7.6 User Guide

D Voltage reading statuses . . . . . . . . . . . . . . . . . . . . . . . . . . . . 494

EA_MS Release 7.6 User Guide

EA_MS Release 7.6 User Guide

New features in Rel. 7.6

New in Rel. 7.6

EA_MS Release 7.6 User Guide

EA_MS Release 7.6 User Guide

About evaluation features

EA_MS Release 7.6 User Guide

What is the EnergyAxis System?

EA_MS Release 7.6 User Guide

Figure 1-1. EnergyAxis System

EA_MS Release 7.6 User Guide

EA_MS Release 7.6 User Guide

Home area network

Optimizing the 900 MHz network

Support for static IP addresses

Email notification of alarms

EA_MS Release 7.6 User Guide

long data format

REX and REX2 meters

EA_MS Release 7.6 User Guide

REX and REX2 meters

Total demand for REX meters

REX and REX2 meters

Outage and restoration

EA_MS Release 7.6 User Guide

Meter data collection and reporting

EA_MS Release 7.6 User Guide

Reading previous registers

Configuration change data

Reading and reporting operational information

EA_MS Release 7.6 User Guide

Line voltage data

Reading and reporting meter data

Data export and XML schema

EA_MS Release 7.6 User Guide

Time management in gatekeepers

Time synchronization in A3 ALPHA meters

Multiple time zones and DST

Meter events, alarms and logs

EA_MS Release 7.6 User Guide

Disconnecting and reconnecting service

EA_MS data file partitioning

EA_MS Release 7.6 User Guide

EA_MS Release 7.6 User Guide

Figure 2-1. Three-way Association (MeterScheduleData Set)

EA_MS Release 7.6 User Guide

LAN Comm options Gatekeeper module (ILC)

1.4 1.3 1.0 - 1.2 2.x 1.2 & 1.3