e-tagging issue work group raymond r. vojdani, p.e

E-Tagging Issue E-Tagging Issue Work GroupWork Group

Raymond R. Vojdani, P.E.Raymond R. Vojdani, P.E.

2

E-Tagging Issues Work E-Tagging Issues Work GroupGroup

History: Ad Hoc Work GroupHistory: Ad Hoc Work Group

Known as BMW ClubKnown as BMW Club MetamorphismMetamorphism

3


BMW Club

E-Tagging Issues Work Group

====

4


Goal:Goal:

To research and facilitate resolution To research and facilitate resolution to identified tagging problems, if to identified tagging problems, if

possible.possible.

5


Start with an E-Tagging Issue Referred to the Start with an E-Tagging Issue Referred to the WGWG

Research the issue, collect data, and gather Research the issue, collect data, and gather necessary information. necessary information.

Research existing policies and guidelines Research existing policies and guidelines relating to the issue.relating to the issue.

Provide direction for a solution of the problem Provide direction for a solution of the problem based on existing policies.based on existing policies.

If no policies exist for the problem, determine If no policies exist for the problem, determine extent of problem and refer to appropriate extent of problem and refer to appropriate work group (i.e. Real Time or Business work group (i.e. Real Time or Business Practice workgroups).Practice workgroups).

6


Log all issues discussed and track Log all issues discussed and track the resolution presented.the resolution presented.

Present the Issues to the ISAS Present the Issues to the ISAS members at their next meeting for members at their next meeting for Lesson Learned and Best Practices.Lesson Learned and Best Practices.

Develop and Maintain the WECC Develop and Maintain the WECC ISAS E-tag template Database. ISAS E-tag template Database.

7


Work Group Members:Work Group Members: Kathee Downey (PACW – Reliability)Kathee Downey (PACW – Reliability) John Dake (WALC – Reliability)John Dake (WALC – Reliability) Al Gulutzan (AESO, Reliability)Al Gulutzan (AESO, Reliability) Raymond Vojdani (WACM, Reliability)Raymond Vojdani (WACM, Reliability) Kathy Crane (WAPA, Merchant)Kathy Crane (WAPA, Merchant) Demetrios Fotiou (PWX, Merchant)Demetrios Fotiou (PWX, Merchant) Jim Thomas (PNM, Merchant)Jim Thomas (PNM, Merchant) Ryan Cline (Xcel, Merchant)Ryan Cline (Xcel, Merchant)

8


ISSUESISSUES

9

E-Tagging Issue Work E-Tagging Issue Work GroupGroup

Sink Control Area Approval OverrideSink Control Area Approval Override Eastern Interconnections E-Tag Upload Eastern Interconnections E-Tag Upload

IssueIssue Late Tag Approval Late Tag Approval Verbal Coordination of CurtailmentVerbal Coordination of Curtailment Transactions Starting Mid-HourTransactions Starting Mid-Hour E-Tagging TemplatesE-Tagging Templates

10


Issue 1:Issue 1: Sink Control Area A used their e-tagging Sink Control Area A used their e-tagging

over-ride capability and approved a tag on over-ride capability and approved a tag on behalf of another approving authority (TP and behalf of another approving authority (TP and CA). CA).

Each approval entity needs to approve their Each approval entity needs to approve their section of the tag. Each sink control area has section of the tag. Each sink control area has the capability to approve for other approval the capability to approve for other approval entities should those approval entities run entities should those approval entities run into communication problems. The key is the into communication problems. The key is the Sink CA needs to be asked. Sink CA needs to be asked.

11


Control Area A’s (Sink Control Area) explanation Control Area A’s (Sink Control Area) explanation for Using Approval Override? for Using Approval Override?

A.A. The tag in question was a replacement of another The tag in question was a replacement of another tagtag

B.B. B. The time was running out before the tag diesB. The time was running out before the tag dies

Resolution Status:Resolution Status:

Control Area A acknowledged that they should not Control Area A acknowledged that they should not have done that even if their intentions were pure.have done that even if their intentions were pure.

12


Issue 2:Issue 2: Control Area A is located in the Western Control Area A is located in the Western

Interconnection. They curtailed tag XYZ Interconnection. They curtailed tag XYZ due to transmission constraints. A due to transmission constraints. A Reliability Coordinator in the Eastern Reliability Coordinator in the Eastern Interconnection Reloaded this tag. It Interconnection Reloaded this tag. It has been identified that it is an has been identified that it is an “automated” process with the IDC in the “automated” process with the IDC in the Eastern Interconnection and continues Eastern Interconnection and continues to cause concern for WECC members.to cause concern for WECC members.

13


Resolution Status:Resolution Status:

TheThe NERC IDC Work Group was NERC IDC Work Group was contacted and made aware of the contacted and made aware of the problem. The IDC WG has problem. The IDC WG has scheduled a software fix for this scheduled a software fix for this problem in Dec. 2004, with problem in Dec. 2004, with completion date of Jan. 2005.completion date of Jan. 2005.

14


Issue 3:Issue 3: Control Area A Denies a Tag because the tag did not pass Control Area A Denies a Tag because the tag did not pass

OASIS validation.OASIS validation. The PSE contacts the Control Area A, and identify the The PSE contacts the Control Area A, and identify the

problem.problem. The Control Area A acknowledges the error and blames the The Control Area A acknowledges the error and blames the

OASIS software for behaving badly. OASIS software for behaving badly. PSE is asked to submit a new tag and Control Area A PSE is asked to submit a new tag and Control Area A

commits to coordinate it with the intermediary Control commits to coordinate it with the intermediary Control Areas (B).Areas (B).

By now, the new tag is very late (12 minutes past the hour).By now, the new tag is very late (12 minutes past the hour). The Intermediary Control Area denies the tag for being The Intermediary Control Area denies the tag for being

late.late. PSE feels cheated and submits a complaint to our work PSE feels cheated and submits a complaint to our work

group.group.

15


Who do you think is at fault here? PSE, Who do you think is at fault here? PSE, Control Area A, Control Area B?Control Area A, Control Area B?

Nobody is at fault, this is an unfortunate Nobody is at fault, this is an unfortunate situationsituation

Resolution Status:Resolution Status:One positive outcome was the control area B One positive outcome was the control area B stated their position that they would have let stated their position that they would have let the tag flowed had it been identified as the tag flowed had it been identified as Emergency or Reliability IssueEmergency or Reliability Issue

16


Issue 4:Issue 4: Control Area A (source CA) Curtail a couple of tags due to Control Area A (source CA) Curtail a couple of tags due to

transmission constraintstransmission constraints According to B.P. #13, the Source Control Area Needs to According to B.P. #13, the Source Control Area Needs to

Coordinate the Curtailment with the Sink Control Area.Coordinate the Curtailment with the Sink Control Area. The Curtailments are implemented by all involved entities. The Curtailments are implemented by all involved entities.

Thus, Control Area A does not see a need for Verbal Thus, Control Area A does not see a need for Verbal CommunicationsCommunications

Control Area B feels that they should have been notified by Control Area B feels that they should have been notified by phone and file a complaint to the Work Groupphone and file a complaint to the Work Group

Resolution Status:Resolution Status:Control Area A, acknowledged their Error and will follow Control Area A, acknowledged their Error and will follow the B.P. #13, until such a time when E-tagging becomes a the B.P. #13, until such a time when E-tagging becomes a primary mode of notificationprimary mode of notification

17


Issue 5:Issue 5: XYZ PSE asks Control Area A to allow Mid-Hour ScheduleXYZ PSE asks Control Area A to allow Mid-Hour Schedule Control Area A will not allow Mid-Hour Scheduling due to Control Area A will not allow Mid-Hour Scheduling due to

all the complications it causes.all the complications it causes. What are some of the complications: What are some of the complications:

Large CAs with many neighbors, already having difficulties Large CAs with many neighbors, already having difficulties checking out once an hour.checking out once an hour.

Tags with partial hour do not show Integrated MWh. This Tags with partial hour do not show Integrated MWh. This causes problems for systems who are tag drivencauses problems for systems who are tag driven

Ramping issues and limitation of AGCRamping issues and limitation of AGC Distraction form doing what needs to be done for next hourDistraction form doing what needs to be done for next hour

XYZ PSE states that some CAs do accommodate Mid-Hour XYZ PSE states that some CAs do accommodate Mid-Hour schedulingscheduling

18


Resolution Status:Resolution Status:The Work Group acknowledges the The Work Group acknowledges the challenges of Mid-Hour Scheduling. challenges of Mid-Hour Scheduling. There is no mandate to force CAs to There is no mandate to force CAs to accommodate Mid-Hour Scheduling. accommodate Mid-Hour Scheduling. Until such a time, when the tools gets Until such a time, when the tools gets better, we are stuck with the our better, we are stuck with the our current systems and it limitations. current systems and it limitations. Perhaps, implementation of WIT will Perhaps, implementation of WIT will take care of this issue.take care of this issue.

19


E-Tagging Templates:E-Tagging Templates: Issues & Driving Force Behind itIssues & Driving Force Behind it There will be Grouped into 4 RegionsThere will be Grouped into 4 Regions

Rocky MountainRocky Mountain Desert SouthwestDesert Southwest NorthwestNorthwest CaliforniaCalifornia

Where Would these Template ResideWhere Would these Template Reside WECC ISAS WebsiteWECC ISAS Website Common Western OASIS (webttrans.net)Common Western OASIS (webttrans.net)

Future Use: WITFuture Use: WIT

20


Send your issues to Raymond Send your issues to Raymond Vojdani Vojdani

Please CC Bob SchwermannPlease CC Bob Schwermann E-mail address: E-mail address:

[email protected]

[email protected] Phone Number (970) 461-7379Phone Number (970) 461-7379

21


Questions?Questions?

e-tagging issue work group raymond r. vojdani, p.e

Documents

issues work group issues

issues work group control

issues work group history

issues work group goal

issue work group raymond

issues work group bmw

appropriate work group

templates e