The Relationship Between Metered Measurement Cycles and Bill Cycles
As you can deduce, a service point's measurement cycle is related to an account's bill cycle.
The following table is an example of how you would set up the various dates on the various schedules that control meter reading and billing.
|
Measurement Cycle |
Download Date |
Expected Work Date |
Bill Cycle |
Bill Window |
Estimation Date |
|
|
1 |
28-May-99 |
31-May-99 |
1 |
31-May-99 to 2-Jun-99 |
2-Jun-99 |
|
|
2 |
31-May-99 |
1-Jun-99 |
2 |
1-Jun-99 to 3-Jun-99 |
3-Jun-99 |
|
|
3 |
1-Jun-99 |
2-Jun-99 |
3 |
2-Jun-99 to 4-Jun-99 |
4-Jun-99 |
|
|
4 |
2-Jun-99 |
3-Jun-99 |
4 |
3-Jun-99 to 7-Jun-99 |
7-Jun-99 |
|
|
Etc. |
Notice the following about this example:
- The bill cycle code is the same as the measurement cycle. This is not necessary, it's just good practice.
- The bill window starts on the first date on which a meter read could be uploaded.
- The bill window ends on the day after the last possible day a read could be uploaded for the bill cycle.
- Oracle Utilities Meter Data Management only estimates consumption on the last day of the bill window.
Fastpath:
For more information about the bill cycle schedule, refer to Setting Up Bill Cycles.