Daily System Measurement. Implementation Plan

(1)

Daily System Measurement

Implementation Plan

Discussion Paper

V5.0

Final Version

November 15th, 2005

(2)

The intent of this paper is to put forth a complete implementation plan for a standard transaction to be used by industry to report System Level Measurement Data, as defined in the ISO Rules. This has been a living document, and has gone through several iterations before an acceptable final implementation plan was developed that is reasonable for all stakeholders.

1.2 - Overview

System Level Measurement Data is currently defined as data for points of delivery, points of supply, points of provincial interchange, distribution interchange, distributed generation, and border customer consumption that are needed to describe the total energy flow on the AIES at the transmission level and the inputs and outputs to each and every distribution load settlement zone. Historically this data has been used for two very distinct purposes, and therefore treated in two distinct ways.

The first area that this data is used for is Transmission Tariff Billing. Data is collected in order to bill for DTS and STS contracts, as well as for provincial interchange. All generation information is included, in order to pass on to the Energy Market for payment. All points that are reported on have had their parameters defined by a Measurement Point Definition Record (MPDR), or have an MPDR currently under development by the AESO. All data is reported to the AESO in a defined format, the ITF transaction.

The second area that this data is used for is Load Settlement. Data is collected in order to calculate zone totals for each distribution load settlement zone. All distributed generation information is collected, as well as transmission loads and distribution interchange imports and exports. Historically this data was usually collected by an MDM and passed to an LSA that were within the same WSP, and as such the format and transfer of data was left as an internal decision of the WSP.

The majority of data that is used for Load Settlement is also used for Transmission Tariff Billing. As such, data that is received at the AESO should be exactly the same as data received at the LSA. However, it has been demonstrated in the past that because of the different methods of processing and transferring the data, discrepancies do develop. As well, the industry is moving more and more towards MDMs that are not contained within the same WSP as the LSA to whom they are sending data. This has resulted in complications when an MDM has to send data to multiple LSAs that are using different formats.

(4)

Because of the above problems, along with the need for compliance monitoring and auditability by the AESO, it was generally agreed that a standard transaction for System Level Measurement Data was a requirement, and needed to be addressed. Several meetings were held with stakeholders, and papers issued for discussion. It was agreed that a standard transaction would be generally beneficial for the industry, as it would allow for:

• Easier auditability through uniform formats and practices

• Standards to allow for compliance monitoring

• A single enforceable rule within the ISO Rules

• Completeness of data being sent to the AESO

• A formalized relationship between the MDM and LSA for this data

• Portability of the data between different LSAs

• Uniform data processes for MDMs not within the LSA WSP

• Control over all points through the MPDR process

• General consistency within the ISO Rules

In order to implement a standard transaction for System Level Measurement Data, two major changes need to be made; 1) Distribution Interchange points need to be included in the data submission to the AESO for completeness, and 2) the standard transaction that was developed with the stakeholders, the Daily System Measurement (DSM) transaction, needs to be universally accepted and used in the industry.

Through consultation with stakeholders, it was decided that a paper should be developed that would give an overall picture of the implementation of a standard transaction for System Level Measurement Data, and that the merits of this paper would then be discussed to come up with an implementation plan that was reasonable with respect to cost and timing. Following are the backgrounds and steps that need to be taken to accomplish these two changes.

2.0 - Distribution Interchange 2.1 - Overview

System Level Measurement Points are defined to include all points that are needed to describe

1) the total energy flow on the AIES at the transmission level, as well as all generation that is included in the Energy Market (Transmission & Market Points), and;

2) the inputs and outputs to each and every distribution load settlement zone (Distribution Points).

The points included in the set of Transmission & Market Points are all currently defined by Measurement Point Definition Records and are sent to the AESO in

(5)

the ITF format. The points included in the set of Distribution Points are all a subset of Transmission & Market Points, with the exception of Distribution Interchange points.

Distribution Interchange is energy transferred from one distribution load settlement zone to another. In order to calculate correct zone totals, this energy must be added to the zone when imported, and subtracted from the zone when exported. The Meter Data Manger for a Distribution Interchange point provides data as an export to the Load Settlement Agent for the supplying zone, and as an import to the Load Settlement Agent for the receiving zone. The naming convention of these points, as well as the data format and transfer mechanism, is left as a decision between the Meter Data Manager and the Load Settlement Agents.

In order to move towards a standard format for all System Level Measurement Data, Distribution Interchange points must be formalized by way of Measurement Point Definition Record, a standard approach to naming conventions and treatment of the data flows must be adopted, and the data must be sent to the AESO in the same standard as the rest of the System Level Measurement Data, in accordance with the format and timings set out in the ISO Rules and the Measurement System Standard.

2.2 - Data Flows:

The following diagram shows a distribution interchange point between two distribution load settlement zones. Energy flows in one direction through the point, and is viewed as an export by one zone and viewed as an import by the other.

Supplier Zone Receiver Zone

Distribution Export Distribution Import

Figure 2.2.1 – Distribution Interchange Point

The following diagram shows the current data flow for Distribution Interchange points. Data for the Distribution Interchange point is collected by the MDM and is provided to the Receiver LSA as Import data, and to the Supplier LSA as Export data. This data is then supplied to the AESO from each LSA in non-standard files such as the LOD and PDR files. The naming convention of the points is

(6)

currently decided on by each LSA, and typically the ID for one LSA has no relationship to the ID for the same point for the other LSA. The transfer method for this data is currently decided on between the MDM and each LSA.

Data as Import Data as Import Receiver LSA

MDM _AESO

Supplier LSA

Data as Export Data as Export

Figure 2.2.2 – Current Data Flow For Distribution Interchange Data

Initially the AESO will collect the required technical information about each Distribution Interchange point from the WSPs and develop Measurement Point IDs and Definition Records. These will be reviewed with the appropriate stakeholders, and final versions will be developed and issued as the basis for this data. A rule change will be written and submitted through the standard ISO rules changes process to incorporate the Distribution Interchange points.

The following diagram shows the final data flow for Distribution Interchange points. The MDM will provide the data to the Receiver LSA, the Supplier LSA, and the AESO in the DSM format and using Drop Chute. The LSAs will no longer send the Distribution Interchange data to the AESO. All data will comply with the standards and timings laid out in the ISO Rules and the Measurement System Standard, as with all other System Level Measurement Data.

<Name>IMP as Import (DSM) Receiver LSA <Name>IMP as Import (DSM) MDM AESO <Name>EXP as Export (DSM) Supplier LSA <Name>EXP as Export (DSM)

(7)

In this way the AESO receives the data directly from the MDM, as is the case for all other System Level Measurement Data, and provincial reconciliation may be performed. Points will be identified with a standard naming convention (to be determined through consultation), that will include an IMP or EXP qualifier depending on the data type. This allows for corresponding points to be easily identified in both zones.

In order to minimize the impact to internal processes in the WSP, in cases where the LSA and the MDM are contained within the same WSP, the data format and transfer method will remain the decision of the WSP. If all WSPs decide that they prefer to receive internal data in the DSM format, then this may be formalized in the ISO Rules, as determined through the established method for rule changes, and with input from the Load Settlement Business Advisory Committee regarding requirements. The AESO encourages the LSA to use the DSM for internal transactions, but will not make this a requirement at this time.

2.3 – Steps and Timelines

Steps and timelines for including Distribution Interchange points in the System Level Measurement Data transfer are as follows:

1) The target date for submitting the rule change is November 15th, 2005. The rule change will be submitted through the standard ISO Rules Change Process, and a letter describing the rule change process and schedule to incorporate the implementation of Distribution Interchange points will be issued shortly thereafter.

2) The target date for provision of Distribution Interchange point descriptive information is November 18th_{, 2005. This data is supplied to the AESO by}

the WSPs who hold the MDM responsibility for the point. This includes single line diagrams, land locations, line numbers, and/or any information that can be used to identify the points. A formal request for this information was sent out on October 7th, 2005.

3) The target date for initial issuing of the MPDRs is December 2nd, 2005. Measurement Point Definition Records will be developed by the AESO for all Distribution Interchange points. This will include a naming convention proposed by the AESO, based on the point information that has been received. The MPDRs will be issued to the WSPs, MDMs and LSAs for discussion and feedback.

4) The target date for final issuing of the MPDRs is December 30th_{, 2005.}

Measurement Point Definition Records will be revised based on feedback, agreed upon by all parties, and issued in advance for system preparations.

(8)

5) The target date for provision of Distribution Interchange data to the AESO in DSM format is February 1st, 2006. Distribution Interchange points are provided to the AESO in the DSM format via Drop Chute from the MDM, using the ID defined in the MPDR. Transfers between the MDM and the LSA must occur in the DSM format when not contained in the same WSP. The format for data between an MDM and LSA within the same WSP remains the decision of the WSP. The LSA will no longer be required to send Distribution Interchange data to the AESO. This is the final state for Distribution Interchange data.

3.0 - Daily System Measurement Transaction 3.1 - Overview

As previously stated, System Level Measurement Points are made up of Transmission & Market Points, and a subset of that, Distribution Points (currently excluding Distribution Interchange points). Transmission & Market Points are currently sent to the AESO by the MDM in the ITF format. Distribution Points are currently sent to the appropriate LSA by the MDM in a format that has been agreed upon between the LSA and the MDM.

Through consultation with stakeholders it was determined that it would beneficial to the industry to have a standard transaction that would be used to report the data for all System Level Measurement Points. The format that was developed for this purpose was the Daily System Measurement transaction (DSM). This transaction is a variation of the ITF transaction that is currently used to report the data for the Transmission Points. By keeping the DSM similar in structure to the ITF, the impact to stakeholders was determined to be minimal.

The format of the ITF transaction that is currently used for reporting data for Transmission Points is as follows:

Table 3.1.1 – ITF Transaction Format

Data Field DataType/Size Description

Type Char (3) Description: Metering data transaction type

Format: GEN, LOD, IMP, EXP, DAT (upper case only) Example: GEN

Date Number (8) Description: Metering data reading date

Format: yyyymmdd

Example: 20040520 = May 20, 2004

Hour Number (2) Description: Metering data reading hour

Format: hh where hh is hour ending 01 to 25 Example: 01 = 00:00 to 01:00

Interval Number (2) Description: Metering data reading interval

Format: ii where ii is interval ending 01 to 04

Examples: 01 = XX:00 to XX:15, 03 = XX:30 to XX:45

Owner Cha r(10) Description: Metering data owner company

Format: Alphanumeric characters

(9)

Measurement Point

Char (10) Description: Measurement point identifier

Format: Alphanumeric characters

Examples: RD14S, 366S001, 0000021401, ADEC…

MWh Number (14,4) Description: Net active energy transferred in the interval

Format: XXXXX.XXXX (unsigned values only) Example: 22222.1234

MWh Source Char (1) Description: Net active energy source flag

Format: M = Metered, E = Estimated Example: M

MVARh Number (14,4) Description: Net reactive energy transferred in the interval

Format: XXXXX.XXXX (signed values allowed) Example: -22222.1234

MVARh Source Char (1) Description: Net reactive energy source flag

Format: M = Metered, E = Estimated Example: E

The file naming convention for the ITF format is:

<Metering Data Provider Company Code>_<Company Filename Convention>.csv Example: AML_20050315.csv

The format of the DSM transaction that will be used to report all System Level Measurement Data has been discussed in numerous stakeholder meetings and papers. The transaction has now been finalized and is no longer open to alterations. The format of the DSM transaction is as follows:

(10)

Table 3.1.2 – DSM Transaction Format

Transaction (Abbreviation)

Element (in

sequence) DataType/Size Description

Daily System Measurement

(DSM)

Transaction Abbreviation

‘DSM’ Description: Abbreviation for the transaction name Format: DSM (upper case only)

Example: DSM

Data Type Char (3) Description: Metering data transaction type

Format: GEN:

Transmission Generation – generation connected to the transmission system

Distributed Generation – generation connected to the distribution system

Isolated Generation – generation providing energy to isolated communities that are not connected to the AIES

Border Supply – energy supplied by an extra-provincial supplier to customers in Alberta not connected to the AIES Reversing Loads – energy flow from the distribution system into

the transmission system due to distributed generation LOD:

Transmission Loads – points of delivery to the distribution system from the transmission system

Isolated Loads – points of delivery to isolated communities from isolated generation

IMP:

Provincial Imports – energy supplied by an extra-provincial transmission system to the AIES

Zone Imports – energy that is transferred into one load settlement zone from another load settlement zone EXP:

Provincial Exports – energy supplied to an extra-provincial transmission system from the AIES

Zone Exports – energy that is transferred out of one load settlement zone to another load settlement zone POT:

Duplication Avoidance Transfers – energy that is transferred between customer generation and load facilities, wheeled across the AIES

Example: GEN

Data Date Number (8) Description: Date of energy flow of metering data Format: yyyymmdd

(11)

Data Hour Number (2) Description: Hour of energy flow of metering data Format: hh where hh is hour ending:

01 to 25 for the day of the Fall time change 01 to 23 for the day of the Spring time change 01 to 24 for all other days

Example: 01 = 00:00 to 01:00

Data Interval Number (2) Description: Interval of energy flow of metering data Format: ii where ii is interval ending 01 to 04 Examples: 01 = XX:00 to XX:15, 03 = XX:30 to XX:45 Measurement

Point ID

Char (10) Description: Measurement point identifier Format: Alphanumeric characters

Examples: RD14S, 366S001, 0000021401, ADEC… MWh Number (12,7) Description: Net active energy transferred in the interval

Format: XXXXX.XXXXXXX (unsigned values only) Examples: 22222.1234567, 48.3

MWh Source Char (1) Description: Net active energy source flag Format: M = Metered, E = Estimated Example: M

MVARh Number (12,7) Description: Net reactive energy transferred in the interval Format: XXXXX.XXXXXXX (signed values allowed) Examples: -22222.1234567, 19.4

MVARh Source

Char (1) Description: Net reactive energy source flag Format: M = Metered, E = Estimated Example: E

The file naming convention for the DSM format is:

<Transaction Abbreviation>_<MDM ID>_<Recipient ID>_<Transaction Datetime>.csv Example: DSM_2020_3000_20050315120000.csv

The format of the transactions currently used to report the data for Distribution Points between the MDM and LSA is decided on by the MDM and LSA, and is therefore generally unique for each LSA, and is not practical to describe here.

(12)

3.2 - Transaction Flows

The following diagram shows the current flow of data for System Level Measurement Data. All MDMs report data to the AESO in the ITF format via FTP. All MDMs report data to the appropriate LSA in a format and transfer method decided on by the MDM and LSA.

ITF Format AESO FTP Transfer MDM ? Format LSA ? Transfer

Figure 3.2.1 – Current Data Flow For System Level Measurement Data

The following diagram shows the final data flows for System Level Measurement Data. All MDMs will report data to the AESO using the DSM format and DropChute. MDMs that are not contained within the same WSP as the LSA will send data to the LSA in the DSM format. All LSAs must be able to accept the DSM format. Timing for the data will remain consistent with the ISO Rules and the Measurement System Standard. Procedures surrounding revision of data will remain consistent with current practices for System Level Measurement Data sent to the AESO, with corrections older than Initial Monthly Settlement timing requiring notification and explanation to the AESO at the time of submission.

(13)

DSM Format LSA2 DropChute WSP ? Format MDM LSA1 ? Transfer DSM Format AESO DropChute

Figure 3.2.3 – Final Data Flow For System Level Measurement Data

In order to minimize the impact to internal processes in the WSP, in cases where the LSA and the MDM are contained within the same WSP, the data format and transfer method will remain the decision of the WSP. If all WSPs decide that they prefer to receive internal data in the DSM format, then this may be formalized in the ISO Rules, as determined through the established method for rule changes, and with input from the Load Settlement Business Advisory Committee regarding requirements. The AESO encourages the LSA to use the DSM for internal transactions, but will not make this a requirement at this time.

3.3 – Steps & Timelines

Steps and timelines for moving to a standard DSM transaction for all System Level Measurement Data are as follows:

1) The target date for a final implementation plan is November 15th_{, 2005.}

This plan has been submitted to stakeholders for feedback and agreed to by all parties.

2) The target date for submitting the required rule change is November 15th, 2005. The rule change will be submitted through the standard ISO Rules Change Process, and a letter describing the rule change process and schedule to incorporate the implementation of the DSM transaction will be issued shortly thereafter.

(14)

3) The target date for final implementation of the DSM format is February 1st_,

2006. As of this date, all MDMs must report System Level Measurement Data to the AESO in the DSM format, via DropChute. The AESO will be capable of accepting the DSM format through DropChute, and will no longer accept ITF files. LSA’s must be able to accept the DSM transaction from the MDMs, and MDMs must send data to the LSA in that format when not contained within the same WSP. The format for data between an MDM and LSA within the same WSP remains the decision of the WSP. The LSA will no longer send System Level Measurement data to the AESO in any form.

4.0 - Stakeholder Feedback

Please direct any comments or questions about this paper to Chris Connoly at [email protected].

Daily System Measurement. Implementation Plan