1. Project Nexus Workgroup
Resynchronisation – Transitional Arrangements
04/05/2019

2. Background No current concept of resynchronisation on an NDM site
No difference between eyeball and derived reads
An eyeball read after a sequence of derived reads – any rec dealt with in latest period
In future, want to recognise drift and where significant, apportion over period since last resynch
Transitional business rules required to deal with the first resynchronisation

3. Options for Transitional NDM Rec
After implementation treat the first resynch read as normal rec OR
Write business rules to spread first resynch back across an assumed period

4. Option 1 – start from first resynch
Implementation date
Meter index
Subsequent resynchs can be apportioned back to first flagged eyeball read
First resynch difference dealt with in latest period
Time
Derived reads
Appears workable for periodic rec
May be inequitable for Process 3 (Daily Rec) sites
Eyeball reads = Resynch

5. Option 2 – Apply a “resynch start date”
Implementation date
Meter index
Subsequent resynchs can be apportioned back to first flagged eyeball read
First resynch difference applied back to closest read to implementation
Time
Option 2a – “Resynch start date” is closest read to implementation date (before or after)
Derived reads
Eyeball reads = Resynch

6. Option 2 – Apply a “resynch start date”
Implementation date
Meter index
Subsequent resynchs can be apportioned back to first flagged eyeball read
First resynch difference applied back to closest read to [12m] ago
Time
Option 2b – “Resynch start date” is closest read to [12] months before 1st resynch (before or after)
Derived reads
Eyeball reads = Resynch

7. All Options - Change of Shipper During Period
Implementation date
Change of Shipper
Meter index
Time
Derived reads
Suggested rule – first resynch can go back no further than last change of Shipper
Eyeball reads

8. First Resynch – Process 3 sites
Daily reconciled sites – some options could result in first resynch being adjusted on one day
Special rule required for Process 3
Suggested rule – spread first resynch energy back to last NDM read (or Shipper transfer read if later

9. Process 3 – Daily Read Sites
Implementation date
Change of Shipper
Meter index
First resynch difference applied back to last NDM read or Change of Shipper if later
Time
Derived reads
Suggested rule – first resynch goes back to last NDM read or last change of Shipper if later
Daily reads – Process 3
Eyeball reads