METER DATA MANAGEMENT (MDM) SYSTEM UPGRADE

Transcription

1 METER DATA MANAGEMENT (MDM) SYSTEM UPGRADE Richard Zaworski Manager, Meter Data Management June 9, 2015

2 Overview MDM testing and market trials is nearing completion. We are currently in the final planning stages for deployment to production. A go-live date has not been established at this time. IESO will be providing participants a minimum of 4 weeks advanced notice of the go-live date. Deployment to production will be a hard cutover from MV-STAR/MV-WEB to Oracle LPS/MDD (i.e. there will not be parallel system operations). 2

3 Overview For a limited time, MV-STAR/MV-WEB will still be available post go-live for participant access to historical data. Oracle LPS/MDD will include 3 months of historical data. New data will only exist in Oracle LPS/MDD. There will be an opportunity for participants to perform parallel calculation comparison between both systems for the 3 month historical period available in both systems. Details will be provided as part of IESO s MDM golive communication to participants. 3

4 Overview The Oracle LPS MDM system includes new functionality. Some functionality will be available at golive while other functionality will be released post golive. New functionality available at go-live includes: Date effectiveness (MV-STAR) versus date/time effectiveness (Oracle LPS) of meter and totalization table attributes. Enhanced VEE processes. Directional MEC and Fixed Factor Losses (TLF). Ability to manage registration changes to compliance aggregation/meter disaggregation models. Post final calculations. Calculation methods. 4

5 Overview Additional functionality will be available post golive. This includes: Loss precedence methods Loss distribution methods Dynamic loss allocation Rollout of this functionality will be done via IESO s baseline change management process (TBD). 5

6 Calculation Design Differences between two systems For assumed method for Method 1 SSLA with service type Delta ; MV-Star uses a divisor of 3 when calculating per phase voltage and current Oracle LPS uses a divisor of 3 when calculating per phase voltage and current When calculating Method 1 SSLA; MV-Star uses 83 (1000/12) Oracle LPS uses (1000/12) When calculating Method 2 SSLA and meter data has 0 VAR values; MV-Star uses assumed method (kva=kw*pf) Oracle LPS uses actual quantities (i.e. kva=kw) When calculating Method 1 SSLA and flow exists on directional channels; MV-STAR calculates current (I) by directional flow Oracle LPS calculates current (I) by total flow These calculation design differences yield slightly different results (i.e. they are not exact in both systems). Differences are negligible from a Settlement perspective. 6

7 Conversion/Transformation Impacts In some instances, MV-Star master data was transformed during conversion to Oracle LPS. Transformation differences include: Voltage Codes and Loss Codes have been renamed in some cases. Summary Meter with a. in the name has been transformed with a. Totalization tables where a meter is mapped directly to a delivery point has been transformed with an intermediary summary meter (i.e. MP to SM to DP) Compliance Aggregation and Meter Disaggregation Models include Ratio Meter which is used to calculate apportionment ratio of dispatch instructions. These transformation differences will be reflected in the Site Registration Report (SRR). 7

8 Site Registration Report IESO will be issuing go-live SRR from Oracle LPS, one week prior to go-live. New SRR has same look and feel as existing SRR. Includes additional attributes and parameters based on system functionality (i.e. date/time effectiveness, MEC direction, ratio meter structure, etc.) 8

9 Meter Data Distribution (MDD) Publishing of meter data reports will be managed thru Online IESO and the new reporting web site. Reports will be pushed to participants based on role Profile. Participants also have the ability to submit ad-hoc requests. Meter data reports published using existing EDI-867 file format. Please refer to SE-113 Working Group for more details. 9

10 Go Live Activities Preparation of system for go-live is a 7 day pre go-live effort. IESO will be working with MSP s to implement Registration Freeze 7 days pre go-live and 3 days post go-live. This will be included as part of go-live communication to participants. 10

11 Summary Go-live planning is still underway Communication will be issued to participants once go-live date has been set. IESO will work with MSP s to coordinate Registration Freeze 11