description of 24 hour clock in MDMS PRODUCTS

1. 24 Hour Clock -- Overview
1
1:00
AM
00:00
3:00
AM
2:00
AM
5:00
AM
4:00
AM
7:00
AM
6:00
AM
9:00
AM
8:00
AM
11:00
AM
10:00
AM
1:00
PM
12:00
PM
3:00
PM
2:00
PM
5:00
PM
4:00
PM
7:00
PM
6:00
PM
8:00
PM
10:00
PM
9:00
PM
12:00
AM
11:00
PM
DSE
Iterative Processing
Meter Data, Validation, MRA EOD
Validation, Estimation, Reports, NPM
Post EOD
TOU Bin Estimation, Billing Extracts
Iterative Processing
Meter Data, Validation, MRA
Nightly
Hand Held Reads
Iterative Processing
Meter Data, Validation
MRA

2. Sample Daily Processing Schedule
2

3. © Landis+Gyr
MDMS Daily Processing
 Modular and component-based to facilitate building a processing
schedule that will fit the objectives required.
 The primary objective is to operate the MDMS in a continuous
fashion to publish data in the quickest manner possible (example:
billing determinants and customer presentment).
 A key driver in determining the schedule is the billing cut-off time.
 The schedule should also provide time for users to resolve critical
VEE exceptions in time for billing.
3

4. © Landis+Gyr
24-hour Clock
4
1:00
AM
00:00
3:00
AM
2:00
AM
5:00
AM
4:00
AM
7:00
AM
6:00
AM
9:00
AM
8:00
AM
11:00
AM
10:00
AM
1:00
PM
12:00
PM
3:00
PM
2:00
PM
5:00
PM
4:00
PM
7:00
PM
6:00
PM
8:00
PM
10:00
PM
9:00
PM
12:00
AM
11:00
PM
DSE
Iterative Processing
Meter Data, Validation, MRA
EOD
Meter Data, Validation,
MRA, Reports, NPM
Post EOD
TOU Bin Estimation, Billing Cycle Usage
Iterative Processing
Meter Data, Validation, MRA
HH MRA
Iterative Processing
Meter Data, Validation, MRA

5. © Landis+Gyr
MDMS Core Processes
Data Synchronization Engine Components:
Consist of jobs that run to update the MDMS with Master data (i.e.
current account and meter information) and with other systems (i.e.
SAP)
 MAINT: Daily updates/changes to meters and modules based on
updates provided from other systems (i.e. CIS).
− Adds, updates, deletes
 SYNC: Weekly sync for audit logging purposes only.
− Entire population
5

6. © Landis+Gyr
Published Reading Service (PRS)
Published Reading Service
– Meter Installation
− The IN reading is used by the Meter Exchange logic within the DSE Process to
set the starting “first good read” for the meter deployment.
– Meter Removal
− Transaction latency will result in missing reads for a number of days, which will
be estimated by the MDMS.
− Estimated usage beyond the removal date/time of the meter is obviously not
correct.
− When the transaction is received, the removal read(s) are used to “true up” the
estimated reads back to the point of removal, and straight-line the post-
removal estimates at 0 (zero) usage.
− Implied removals will be processed without a removal read(s) (Sync Mode
Only).
6

7. © Landis+Gyr
24-hour Clock - Optimization
24-hour Clock optimization is installation specific
Optimization is achieved as an iterative process of experimentation with respect
given to:
 Business Rules
 CIS timing requirements
 Hours when VEE exceptions are manually cleared
 Head end capability
You must find the optimal read/VEE schedule to:
 Minimize the daily VEE exception workload by eliminating unnecessary
exceptions
 Eliminate recovery reads that negate exception workload/efforts
 Ensure that best data set is presented daily to billing function
7

8. © Landis+Gyr
Breakdown of an End of Day Read
Check reads count
(checks consumption
effectiveness)
EMED/Create Missing WAVE
LP Sync Complete iWAVE
Exception
Management
MRA meter read
fact processing
8

9. © Landis+Gyr
Dashboard
9

10. © Landis+Gyr
Dashboard
10

11. © Landis+Gyr
Reports
11