Market Operations and Development (MOD) System Upgrade Project Customer Information Session #2 April...

42
Market Operations and Development (MOD) System Upgrade Project Customer Information Session #2 April 9, 2010

Transcript of Market Operations and Development (MOD) System Upgrade Project Customer Information Session #2 April...

Page 1: Market Operations and Development (MOD) System Upgrade Project Customer Information Session #2 April 9, 2010.

Market Operations and Development (MOD)System Upgrade Project

Customer Information Session #2April 9, 2010

Page 2: Market Operations and Development (MOD) System Upgrade Project Customer Information Session #2 April 9, 2010.

2

AgendaWelcome & Introduction

1. MOD Project Update2. Contract Path Model

LUNCH3. Purchasing Timelines for Transmission Service4. Recall/Reduction of Transmission Capacity5. Customer Reports/Portal 6. Physical Self-Supply of Losses7. Q&A

Page 3: Market Operations and Development (MOD) System Upgrade Project Customer Information Session #2 April 9, 2010.

3

Purpose of the Information Session

• BCTC has previously indicated at customer meetings that we would like to gather feedback from our customers on the MOD Project.

• This meeting is one of several feedback sessions that will give customers the opportunity to provide feedback on the project.

• As part of this session, BCTC will be presenting various topics.• BCTC considers this to be an information sharing session, where

customers are welcome to provide suggestions and comments throughout the session and in writing as well.

Page 4: Market Operations and Development (MOD) System Upgrade Project Customer Information Session #2 April 9, 2010.

4

Tentative Future Sessions

• Session on web portal allowing access to customer information • Consultation on the Business Practices related to MOD Project

implementation • Both sessions are tentatively scheduled for late summer

Page 5: Market Operations and Development (MOD) System Upgrade Project Customer Information Session #2 April 9, 2010.

5

1. MOD Project Update

Page 6: Market Operations and Development (MOD) System Upgrade Project Customer Information Session #2 April 9, 2010.

6

What is the MOD Project ?

• The MOD System Upgrade Project will implement a full replacement of BCTC’s existing suite of aging and disparate transmission market systems with a single and fully integrated system.

• The new state-of-the-art system will enable BCTC to provide better market access and services for the benefit of its customers. The system will provide full redundancy for critical services, which will ensure a highly available system with minimal downtime.

• The new system will consolidate current MOD business functions including:

• Scheduling• Settlements & Billing• Pricing• Workflow and Customer Content Management• Reporting

Page 7: Market Operations and Development (MOD) System Upgrade Project Customer Information Session #2 April 9, 2010.

7

Project UpdateThe MOD Project will be implemented in five phases. Below is the anticipated roll-out schedule for the MOD Project (subject to change):

• The Project is currently near the end of its build stage (Phase II) and will be transitioning to its test stage (Phase III) this month.

• Anticipated Go-Live tentatively scheduled for Dec 1, 2010

Design

Phase I Phase II Phase III

(July - Nov 09) (Oct - April 10) (April – Aug 10) (Sept – Nov 10) (Dec 10 & beyond)

Sustain Implement TestBuild

Phase IV Phase V

Page 8: Market Operations and Development (MOD) System Upgrade Project Customer Information Session #2 April 9, 2010.

8

2. Contract Path Model

Page 9: Market Operations and Development (MOD) System Upgrade Project Customer Information Session #2 April 9, 2010.

9

Changes to BCTC Contract Path Names• Current Path Model does not incorporate POR-POD pairs into the contract

path name.• Due to the constraint of not having POR-POD combinations included in the

path name, BCTC cannot post ATC values for each POR-POD combinations.• Currently BCTC only posts ATC information for a default POR/POD for each

path.• Customers have expressed concern that ATC offerings do not auto populate

the TSR entry screen, and customers must change POR-POD, leading to incorrect submissions if they forget to do so.

• The new path model has been modified to now incorporate each POR/POD combination within the path name.

• Now all transmission offerings will be posted for each POR/POD on OASIS.

Page 10: Market Operations and Development (MOD) System Upgrade Project Customer Information Session #2 April 9, 2010.

10

• BCTC has also modified and created new POR/POD that provide greater clarity.

- BCTC.Network was being used as a POR/POD for general export/import from BC, as well as the POD for loss purposes.

- BCTC.Network point has now been changed to BCTC.INT.SYS for export/import purposes.

- BCTC also decided to create a new POD for the purposes of purchasing transmission for physical loss delivery. The new POD is BCTC.Losses.

- Fortis based POR/POD are prefixed with FBC (eg. A.A.Lambert is now FBC.Lambert, Princeton is FBC.Princetn).

Changes to BCTC Contract Path Names

Page 11: Market Operations and Development (MOD) System Upgrade Project Customer Information Session #2 April 9, 2010.

11

New Path List with POR/POD combinationsPath Name POR POD

W/BCTC/BCTC - BPAT/KI – BC.US.BORDER/ KI BC.US.BORDER

W/BCTC/BCTC - BPAT/GMS.MCA.REV – BC.US.BORDER/ GMS.MCA.REV BC.US.BORDER

W/BCTC/BCTC - BPAT/BCTC.INT.SYS - BC.US.BORDER/ BCTC.INT.SYS BC.US.BORDER

W/BCTC/LM - BPAT/BCTC.LM.SYS – BC.US.BORDER/ BCTC.LM.SYS BC.US.BORDER

W/BCTC/LM - BPAT/POWELL.RIVER – BC.US.BORDER/ POWELL.RIVER BC.US.BORDER

W/BCTC/BCTC - AESO/KI - AB.BC/ KI AB.BC

W/BCTC/BCTC - AESO/GMS.MCA.REV – AB.BC/ GMS.MCA.REV AB.BC

W/BCTC/BCTC - AESO/POWELL.RIVER – AB.BC/ POWELL.RIVER AB.BC

W/BCTC/BCTC - AESO/BCTC.INT.SYS – AB.BC/ BCTC.INT.SYS AB.BC

W/BCTC/BCTC - AESO/BCTC.LM.SYS – AB.BC/ BCTC.LM.SYS AB.BC

W/BCTC/AESO - BPAT/AB.BC – BC.US.BORDER/ AB.BC BC.US.BORDER

W/BCTC/AESO - BCTC/AB.BC – KI/ AB.BC KI

W/BCTC/AESO - BCTC/AB.BC – FBC.OK.LD/ AB.BC FBC.OK.LD

W/BCTC/AESO - BCTC/AB.BC – FBC.LAMBERT/ AB.BC FBC.LAMBERT

W/BCTC/AESO - BCTC/AB.BC – BCTC.NTWK.LD/ AB.BC BCTC.NTKW.LD

W/BCTC/AESO - BCTC/AB.BC – BCTC.SEL.LD/ AB.BC BCTC.SEL.LD

Page 12: Market Operations and Development (MOD) System Upgrade Project Customer Information Session #2 April 9, 2010.

12

New Path List continued..Path Name POR POD

W/BCTC/AESO - BCTC/AB.BC – BCTC.INT.SYS/ AB.BC BCTC.INT.SYS

W/BCTC/AESO - BCTC/AB.BC – BCTC.LOSSES/ AB.BC BCTC.LOSSES

W/BCTC/AESO - BCTC/AB.BC – FBC.PRINCETN/ AB.BC FBC.PRINCETN

W/BCTC/BPAT - BCTC/BC.US.BORDER - KI/ BC.US.BORDER KI

W/BCTC/BPAT - BCTC/BC.US.BORDER – BCTC.INT.SYS/ BC.US.BORDER BCTC.INT.SYS

W/BCTC/BPAT - BCTC/BC.US.BORDER – BCTC.NTWK.LD/ BC.US.BORDER BCTC.NTWK.LD

W/BCTC/BPAT - BCTC/BC.US.BORDER – BCTC.LOSSES/ BC.US.BORDER BCTC.LOSSES

W/BCTC/BPAT - AESO/BC.US.BORDER – AB.BC/ BC.US.BORDER AB.BC

W/BCTC/BCTC - BCTC/KI – FBC.OK.LD/ KI FBC.OK.LD

W/BCTC/BCTC – BCTC/KI – FBC.LAMBERT/ KI FBC.LAMBERT

W/BCTC/BCTC - BCTC/KI - BCTC.NTWK.LD/ KI BCTC.NTWK.LD

W/BCTC/BCTC - BCTC/KI - BCTC.INT.SYS/ KI BCTC.INT.SYS

W/BCTC/BCTC - BCTC/KI - BCTC.LOSSES/ KI BCTC.LOSSES

W/BCTC/BCTC - BCTC/BCTC.INT.SYS – KI/ BCTC.INT.SYS KI

W/BCTC/BCTC - BCTC/GMS.MCA.REV – KI/ GMS.MCA.REV KI

W/BCTC/BCTC - BCTC/POWELL.RIVER – KI/ POWELL.RIVER KI

Page 13: Market Operations and Development (MOD) System Upgrade Project Customer Information Session #2 April 9, 2010.

13

Page 14: Market Operations and Development (MOD) System Upgrade Project Customer Information Session #2 April 9, 2010.

14

Page 15: Market Operations and Development (MOD) System Upgrade Project Customer Information Session #2 April 9, 2010.

15

Page 16: Market Operations and Development (MOD) System Upgrade Project Customer Information Session #2 April 9, 2010.

16

Page 17: Market Operations and Development (MOD) System Upgrade Project Customer Information Session #2 April 9, 2010.

17

3. Purchasing Timelines for Transmission Service

Page 18: Market Operations and Development (MOD) System Upgrade Project Customer Information Session #2 April 9, 2010.

18

Transmission Service ModificationsThe following changes in BCTC practices will be adopted once the MOD Project is operational:

• Five minute simultaneous submission window for midnight bidding

• Ability to purchase transmission for Preschedule after office is closed. The following rule from Section 5.3 of BCTC’s Business Practices is no longer applicable:

– **Due to automation, transmission requests will be processed up to 16:59:59. Hourly requests received for Day +1 during the switch-over time (17:00:00 to checkout) from Pre-schedule to Real-time will be processed. Daily, Weekly, Monthly OASIS requests are considered Pre-schedule requests and will be INVALID if received at 17:00:00.

– ***Same timelines as Non-Firm.

• Transmission service offerings will now require bid price to be submitted based on the appropriate discount / non-discount rate for the service.

– Eg. Bid price for daily service that is discounted can be $56/MW per day– Bid Price for weekly TSR will be entered as $962.77/MW per week and monthly

TSR as $4172/MW per month

Page 19: Market Operations and Development (MOD) System Upgrade Project Customer Information Session #2 April 9, 2010.

19

Reservation Priority –Simultaneous Submission Window (SSW)

• In general, Transmission Providers will propose a window within which all transmission service requests the transmission provider received will be deemed to have been submitted simultaneously. BCTC has been approved for a 5 minute window.

- This a change to the current first-come, first-served policy

• Firm and non-firm transmission services will be subject to the window

• BCTC has a pre-determined method for allocating transmission capacity if sufficient capacity is not available to meet all requests submitted within the specified time period. Example to come.

• BCTC will treat all transmission service requests received within a 5 minute window as having been received simultaneously.

• Requests submitted within this window will not be publicly available until the window has closed in order to prevent competitors from requesting the same service simply to disrupt the transmission service procurement process.

Page 20: Market Operations and Development (MOD) System Upgrade Project Customer Information Session #2 April 9, 2010.

SSW - ExampleStage 1: 5 Minute Window: Hourly Firm Service

Request # CustomerDuration (hours)

Pre-confirmed?

Price ($/MWh)

MW

1 A 8 Yes Max 50

2 A 4 Yes Max 50

3 A 8 Yes Max 150

4 A 4 No Max 50

5 A 4 No $0.00 50

6 A 8 Yes Max 100

7 B 8 Yes Max 100

8 B 4 No $0.00 100

9 B 4 Yes Max 100

10 C 4 Yes Max 25

11 C 8 Yes Max 25

12 C 4 No Max 25

Sum of ATC 825

Stage 2: Sort Requests into Priority Buckets based on Duration, Pre-Confirmation Status and Price

Priority Determinants

Priority Bucket 1 Priority Bucket 2 Priority Bucket 3 Priority Bucket 4

Duration (hours) 8 4 4 4

Pre-confirmed? Yes Yes No No

Price ($/MWh) Max Max Max $0.00

Request # Customer MW Request # Customer MW Request # Customer MW Request # Customer MW

1 A 50 2 A 50 4 A 50 5 A 50

3 A 150 9 B 100 12 C 25 8 B 100

6 A 100 10 C 25

7 B 100

11 C 25

Window opens during the first 5 minutes of the earliest request time for Hourly Firm Service: 1 working day before the start of service (subject to extended windows)

Page 21: Market Operations and Development (MOD) System Upgrade Project Customer Information Session #2 April 9, 2010.

21

SSW - Example – continued…Stage 5: Allocate ATC to requests - (Assumes Option 1c from Stage 4)

Scenario 1 2 3

Total ATC (MW) 850 650 450

Allocation (in Priority Sequence) Request # Customer MW Request # Customer MW Request # Customer MW

7 B 100 7 B 100 7 B 100

6 A 100 6 A 100 6 A 100

11 C 25 11 C 25 11 C 25

1 A 50 1 A 50 1 A 50

3 A 150 3 A 150 3 A 150

10 C 25 10 C 25 10 C 25

9 B 100 9 B 100

2 A 50 2 A 50

12 C 25 12 C 25

4 A 50 4 A 25

8 B 100

5 A 50

Total 825 650 450

Scenario 4a - Option 1a 4b - Option 1b 4c - Option 1c

Total ATC (MW) 250 250 250

Allocation (in Priority Sequence) Request # Customer MW Request # Customer MW Request # Customer MW

7 B 100 7 B 100 7 B 100

1 A 50 3 A 150 6 A 100

11 C 25 11 C 25

6 A 75 1 A 25

Total 250 250 250

Note: CounterOffer - shaded blue

Assume that random customer pick order is: B, A, C

Page 22: Market Operations and Development (MOD) System Upgrade Project Customer Information Session #2 April 9, 2010.

22

4. Recall/Reduction of Transmission Capacity

Page 23: Market Operations and Development (MOD) System Upgrade Project Customer Information Session #2 April 9, 2010.

23

Recall of Capacity on OASIS

• Recall is a type of request that can be submitted on OASIS to indicate confirmed modifications to the capacity granted on an Original CONFIRMED OASIS reservation.

• Recalls of capacity will occur in the case of unscheduled Network Economy.

• A Recall will be a new TSR that is confirmed on OASIS, but linked to the Original reservation.

• BCTC does not intend to have the customer recall capacity.• Currently BCTC does not post recall information of transmission

service reservations.

Page 24: Market Operations and Development (MOD) System Upgrade Project Customer Information Session #2 April 9, 2010.

24

Example of a Reservation Queue on OASIS

Page 25: Market Operations and Development (MOD) System Upgrade Project Customer Information Session #2 April 9, 2010.

25

Page 26: Market Operations and Development (MOD) System Upgrade Project Customer Information Session #2 April 9, 2010.

26

Page 27: Market Operations and Development (MOD) System Upgrade Project Customer Information Session #2 April 9, 2010.

27

Reduction of Capacity on OASIS

• Reduction is a confirmed action or modification to the capacity granted on an Original CONFIRMED OASIS reservation.

• Reductions of capacity will occur in the case of Redirects, Resales, Transfers and Curtailment Limits.

• Any Recalls will also be shown as a reduction in granted capacity.• Currently BCTC does not post reduction information for any of its

transmission service reservations.• BCTC intends to provide customers real time information on

reliability limits to transmission service reservations.

Page 28: Market Operations and Development (MOD) System Upgrade Project Customer Information Session #2 April 9, 2010.

28

Page 29: Market Operations and Development (MOD) System Upgrade Project Customer Information Session #2 April 9, 2010.

29

Page 30: Market Operations and Development (MOD) System Upgrade Project Customer Information Session #2 April 9, 2010.

30

5. Reporting/Portal

Page 31: Market Operations and Development (MOD) System Upgrade Project Customer Information Session #2 April 9, 2010.

31

New Reports and Formats• At the last customer session, BCTC stated that it would provide

further details on the customer reports included in the new system.

• BCTC had been hoping to finalize the build of all reports and show samples to customers; however, that task has not been completed.

• BCTC has an example of Draft Daily/Monthly Transaction Report that it will be presenting today.

• BCTC anticipates that most of the report formats currently seen for Transmission Settlements and Billing will remain similar to today with minor changes. The reports will now be available in file formats other than PDF, including CSV.

Page 32: Market Operations and Development (MOD) System Upgrade Project Customer Information Session #2 April 9, 2010.

32

Example of a New Report for Customers

Page 33: Market Operations and Development (MOD) System Upgrade Project Customer Information Session #2 April 9, 2010.

33

Example: New Customer Report

Page 34: Market Operations and Development (MOD) System Upgrade Project Customer Information Session #2 April 9, 2010.

34

Example: New Customer Report

Page 35: Market Operations and Development (MOD) System Upgrade Project Customer Information Session #2 April 9, 2010.

35

BCTC Customer Portal for the Wholesale Market• BCTC is developing a simple information sharing portal for customers to

provide an enhanced customer experience.• As part of the MOD Project a website portal will be an integral part to allow

customers to perform tasks, and view information.• BCTC is currently in its design phase for the portal and is exploring how to

provide better customer service by allowing customers to:– Provide a safe and secure mechanism to access confidential customer

information– Register as a new Wholesale Customer for Long Term and Short Term service– Enter key customer contact information and update the information as required– Upload supporting documents to their registration– Upload additional documents (eg. new Letters of Credit) to BCTC – Review current umbrella agreements, documents and reports provided by BCTC

for the customer– View and download Daily and Monthly Invoices and transaction information– Enter an issue or question for BCTC

Page 36: Market Operations and Development (MOD) System Upgrade Project Customer Information Session #2 April 9, 2010.

36

Example of Draft Portal Displays

Page 37: Market Operations and Development (MOD) System Upgrade Project Customer Information Session #2 April 9, 2010.

37

Page 38: Market Operations and Development (MOD) System Upgrade Project Customer Information Session #2 April 9, 2010.

38

Page 39: Market Operations and Development (MOD) System Upgrade Project Customer Information Session #2 April 9, 2010.

39

• This screen provides customers ability to select a pre-developed report to be executed, and receive the report back in the format specified.

• The reports that BCTC envisions for this feature would be Daily Transaction and Monthly Transaction Reports shown in the previous slides.

• The Time Period drop down will be a limited feature where the user would be able to select one of the pre-defined time periods. (e.g.. Today, Yesterday, This Month).

Page 40: Market Operations and Development (MOD) System Upgrade Project Customer Information Session #2 April 9, 2010.

40

6. Physical Self-Supply of Losses

Page 41: Market Operations and Development (MOD) System Upgrade Project Customer Information Session #2 April 9, 2010.

41

Customers that use Physical Loss Supply

• Due to the changes in the POD for transmission requests, a customer that chooses to physically supply losses must purchase transmission to the POD BCTC.Losses.

• If a customer incorrectly purchases transmission to the POD BCTC.Losses then they must redirect their purchased service to another POD because a Normal Type eTag will be rejected if placed on Transmission for Loss purposes.

• Only a Loss type eTag will be accepted on a transmission service request to the POD BCTC.Losses.

Page 42: Market Operations and Development (MOD) System Upgrade Project Customer Information Session #2 April 9, 2010.

42

7. Questions ?