Caiso MRTU implementation workshop nov 2008

MRTU Implementation Workshop
November 13, 2008

California ISO Confidential. Do not release outside the California ISO.
Agenda—November 13, 2008
Jim PricePartial Loop Network Configuration2:20 – 2:50
Jami LongStructure and Plans for Cutover Plan
Walkthrough
 Detailed Walkthrough Scheduled for
November 20, 2008
2:00 – 2:20
Jason IacobucciContinued Discussion of IMS Plans1:00 – 2:00
Lunch12:00 – 1:00
Jason IacobucciMRTU Business Implementation
 Business Implementation Schedule
 Parallel Operations Testing
10:00 – 12:00
PresenterTopicTime

MRTU Business Implementation Schedule
November 13, 2008

Background
 Major remaining tasks:
 Completion of Update 2
 Commencement of Pre-Production phase of Program
 Objectives
 Complete functional phases of Market Simulation
 Build ISO and Market Participant confidence in cutover activities
and MRTU production business processes
 Prepare for Go-Live

Definitions
 For the purposes of this presentation, the following terms
are used:
 Pre-Production
 Testing phase focuses on preparing people, process, and technology for
MRTU market launch. Includes elements of Parallel Operations, Cutover
/Reversion testing, and ultimately cutover and Go-Live
 Parallel Operations
 Activities comprised of defined test cycles where some aspect of the MRTU
simulation parallels Production Business and/ or Technical processes (e.g.
RT Operational Support, following Production Load Forecast, etc.)
 Cutover / Reversion
 Testing and execution activities intended to prepare CAISO and Market
Participants for MRTU Go-Live, including a series of Open-Loop tests

Sep 2008 Oct 2008 Nov 2008 Dec 2008 Jan 2009
MRTUProgramSchedule
Target U2 Exit
Criteria Met
•Scenario Testing Priority1
•9/8-9/26
Go-Live
2/1/09
FERC 60 Day
Certification Filing
Production
Environment and
Network Model
Upgrades
`
MRTU Release Management
10/1 – Go-live
Desktop Cutover/
Reversion Plan
Walkthrough with
MPs
Market Participant Testing Pre-Production/ Cutover
•Scenario Testing
Priority2
•10/6-10/17
Downtime
10/18-10/25
Market Participant Testing
Downtime
12/20-12/27
`Cutover/ Reversion Planning
` CRR Allocation
LECG Final Report
9/26 Tier 1
Results
MP Final Readiness
Assessments
FERC 30 Day
Readiness
Filing
10/13 Tier 2
Results
10/28 Long-
term Results
11/11 Tier 3
Results
12/2 Annual
Auction
Results
`CRR Auction
MP Readiness
Assessment
•11/
3-
11/
7

Sep 2008 Oct 2008 Nov 2008 Dec 2008 Jan 2009
MRTUProgramSchedule
Go-Live
2/1/09
9/14
2 Week Master File Publishing
Schedule
Weekly Master File Publishing
Schedule
Daily Master File Publishing
Schedule
9/28 10/12 11/2 11/9
Downtime
10/18-10/25
Downtime
12/20-12/27
10/26
12/28
Network Model
Update
Network Model
Update – Go Live
DB23 DB32 DB 32++DB32+

MRTU Parallel Operations Testing
November 13, 2008

Agenda
 Introduction
 Objectives
 Proposed Test Cycles
 Open Loop Test 1 (OL-1)
 Simulated Closed Loop Test 2 (SCL-2)
 Open Loop Tests 3 (OL-3) and 4 (OL-4)
 Proposed Schedule

Parallel Ops Test
Objectives
 Establish confidence in the operational processes and systems
associated with the MRTU implementation
 Demonstrate the infrastructure required for the California ISO to
support MRTU Pre-Production functions
 Demonstrate the infrastructure required for the California ISO to
support the Cutover/Reversion Plan
 Provide Market Participants with mock/test versions of the Pre-
Production and Cutover phases

Proposed Test Cycles
 CAISO proposes four test cycles during Parallel Ops, reflecting two
general categories:
 Open Loop testing, where pre-MRTU Production EMS communicates
directly with market systems in the MRTU environment
 Simulated Closed Loop testing, involving a simulated EMS State
Estimator solution and telemetry
Test Cycle
ID
Description Duration Test Circuit-
Resource
Feedback Loop
SE Solution Load Forecast Outages
(SLIC)
Intertie
Schedules
(OATI)
Bidsets
(SIBR)
Dispatch
Instructions
(ADS)
OL-1 Open loop testing with a single SC for a single resource.
Production EMS will feed MRTU Market Simulation
environment only.
30 minutes Open EMS Production MRTU MRTU MRTU Production
SCL-2 Simulation of all MRTU business processes and systems with
24x7 inputs from Market Participants. Current Production
Load Forecast is fed into MRTU ALFS in order to more
accurately simulate transition between operating days. ISO
provides 24x7 Grid Operations support.
60 days Simulated Closed GOTS 1. Summer week
(pre-DB37)
2. Production (post-
DB37)
MRTU
(Open)
MRTU
(Open)
MRTU
(Follow
Production
Load
Forecast)
MRTU
OL-3 Open loop test, where the MRTU environment shadows
Production as closely as possible but units do not adhere to
MRTU dispatches (therefore EMS feeds back in do not mirror
MRTU results). Network model descprepencies will be
handled on a case-by-case basis
30 minutes Open EMS Production MRTU
(Shadow
Production)
MRTU
(Shadow
Production)
MRTU
(Shadow
Production)
Production
OL-4 Synchronize network model with Production 60 minutes Open EMS Production MRTU
(Shadow
Production)
MRTU
(Shadow
Production)
MRTU
(Shadow
Production)
Production

Open Loop Test 1
 Description
 Open loop testing with a single SC for a single resource
 Production EMS will feed MRTU Market Simulation environment
only
 Objective
 Test the integration of Production EMS with the MRTU market
systems
 Expected result
 Integration successful: communication established between
Production EMS for one unit with MRTU market systems

Open Loop Test 1
 MRTU Data Feeds
 SE Solution/Telemetry: Production EMS
 Load Forecast: Production
 Outages: MRTU (Not mirroring Production)
 Intertie Schedules: MRTU (Not mirroring Production)
 Bidsets: MRTU (Not mirroring Production)
 Dispatch Instructions: MRTU (No dispatches to real units)

Simulated Closed Loop Test 2
 Description
 Simulation of all MRTU business processes and systems with 24x7
inputs from Market Participants
 Current Production Load Forecast is fed into MRTU ALFS in order to
more accurately simulate transition between operating days
 ISO provides 24x7 Grid Operations support
 Objectives
 Provide Market Participants with as close to Production-like Business
Processes as possible.
 Specifically, during this test CAISO will rely on Market Participants to
provide all of the same inputs – from bids and schedules through
dispatch acceptance and meter data – that they would in MRTU
Production

Simulated Closed Loop Test 2
 MRTU Data Feeds
 SE Solution/Telemetry: GOTS (Simulated EMS)
 Load Forecast: Summer week (pre-DB37)
Production (after DB37 deployed)
 Outages: MRTU (Open)
 Intertie Schedules: MRTU (Open)
 Bidsets: MRTU (Follow Production Load
Forecast)

Open Loop Tests 3 and 4
 Description
 Prepare both the ISO and Market Participants for the short
overlap time during Go-Live where current Production must
mirror MRTU
 OL-4 provides a longer duration than OL-3
 Objectives
 Simulate the cutover period by having Market Participants mirror
Production as closely as possible, including matching bidding to
balanced schedules
 Production outages and intertie schedules are reflected in RTM
results, do not cause major issues with RTM solutions

Open Loop Tests 3 and 4
 Data Feeds
 SE Solution/Telemetry: EMS
 Load Forecast: Production
 Outages: MRTU (Shadow Production*)
 Intertie Schedules: MRTU (Shadow Production)
 Bidsets: MRTU (Shadow Production)
* CAISO will facilitate shadowing production by providing a matrix to map pre-MRTU Production inputs
to MRTU inputs

Parallel Ops Test
Proposed Schedule
 In the proposed schedule below:
 SCL-2 will be supported by Grid Operations on an ongoing, 24x7
basis over a long duration
 Multiple iterations of OL-1, OL-2, and OL-3 may be run on single
dates throughout the testing period

Parallel Ops Test
Proposed Schedule
 Grid Operations Ramp-Up
 Grid Operations support will be phased in over the final two weeks of
November:
 11/17 – 11/21
6AM to 6PM daily support of SLIC Outages and ADS dispatches; ADS auto-approve
script is disabled
 11/24 – 11/26
6AM to 6PM daily support of SLIC Outages, ADS dispatches, and CAS eTags (intertie
schedules); ADS auto-accept script is disabled, CAS schedule-creation script is
disabled
 12/1 – 12/20
24x7 support for SLIC Outages, ADS dispatches, and CAS eTags
 SCL-2 will be supported by Grid Operations on an ongoing, 24x7 basis
over a long duration
 RT Operations contact numbers will be provided by end of week

Questions / Feedback

CAISO MRTU Cutover & Reversion
C&R Planning Overview
November 13, 2008
Jami Long, Manager, Operations Information
Technology

Agenda
 Phases & Deliverables
 Planning Phase - Internal
 Planning Phase – External
 Preparation
 Transition
 Closure
 Review Approach
 System Access Approach

C&R Planning Phase - Internal
 Planning Phase includes all artifacts required to execute
Preparation and Transition phases
 Internal Deliverables Include:
 Communication Plan
 Detailed Application C&R Plans
 Detailed Cutover Schedule
 Detailed Reversion Schedule
 Support Plan

Cutover Planning Phase - External
 External deliverables include:
 C&R External Overview
 Cutover Timeline
 Detailed External Cutover Schedule
 Detailed External Reversion Schedule
 C&R Plan Validation will occur during Parallel
Operations

Cutover Preparation Phase
 Preparation includes system readiness activities that will
occur throughout the Parallel Operation and Pre-
Production windows
 Data Migration
 Data Purging Preparation
 System Access Validation
 Finalize Support Plan

Cutover Transition Phase
 Transition is the execution of tasks to prepare data and
begin using systems for production purposes
 Data Migration True-up
 Data Purge
 Cutover Scripts/Tasks
 Transition begins TD-15

Cutover Closure Phase
 Closure is the phase following the reversion window.
This phase includes:
 Legacy System Plan Execution
 Lessons Learned

Cutover & Reversion Review Approach
 11/20
 Review Cutover External Overview Updates
 Walkthrough Detailed Cutover Schedule
 Communications and Support Plan Overview
 12/04
 Review Reversion External Overview Updates
 Walkthrough Detailed Reversion Schedule
 12/18
 Walkthrough Final Changes
 Follow Up on Open Items

System Access
 MRTU Production Access Requests Form (ARF) allows submission
of all users for an application or set of applications on a single form.
 11/15 – Production access requests are due back from POCs.
 12/1 – All production user access permissions are configured in both
market simulation and Folsom production.
 12/14 – All external non-production access will be removed from
Folsom production. This will allow us to identify any “missed”
people or systems.
 New production users without market simulation access must submit
an MRTU production ARF.

System Access
 Existing market simulation users that require production access:
 Must submit a production ARF for SIBR, CMRI, BAPI and CRN
 Must submit production ARF for legacy systems (ADS, SLIC, PIRP, and
OMAR) IF you do not have production access today. If you already have
production access, you do not need to request access.
 New certificates are not required as production certificates are currently
in use.
 Existing market simulation users that require test/market simulation
access only will no longer have access to MRTU Folsom production
effective 12/14. Access/certificates will be carried over to the new
market simulation environment when Folsom production access is
eliminated.

Implementation of “Partial Loop” Intertie
Network Configuration
Jim Price
Lead Engineering Specialist
Market & Product Development
November 13, 2008

Topics of Discussion
Extension of MRTU modeling of external areas other than
Integrated Balancing Authority Areas, for more accurate
congestion management and LMPs:
 Market simulation results have showed needs for
expanding the Full Network Model outside the ISO. ISO is
adding external lines in DB37 model.
Presentation:
 Background of previous modeling of “New PTO” and
“partial loop” networks
 Addition of transmission lines outside California, as “partial
loop” model
 Plans for further improvement in modeling of external
transmission systems

The “New PTO” network consists of “Converted Rights” on
transmission outside the CAISO area. The “New PTO” area in
Southern California, Nevada, and Arizona is documented in the
Full Network Model BPM (section 4.2.4.3), and in a 8/25/2006
white paper at http://www.caiso.com/185d/185db75028b00.pdf.
Operating Procedure S-326 will provide further detail.
MRTU Transmission Model Includes “New PTO”
Network

“New PTO” Modeling Introduced External Loops of
500 kV Lines in Original MRTU Market FNM
MOENKOPI
WESTWING
PALO VERDE
MEAD
McCULLOUGH
MIDWAY
ADELANTO
VALLEY
DEVERS
SERRANO
LUGO
MIRA LOMA
ELDORADO
MARKETPLAC
E
VINCENT
HASSAYAMPA
TO FOUR
CORNERS
MIGUEL IMPERIAL
VALLEY
NORTH
GILA
MOHAVEVICTORVILLE
West
of
River East of
River
500 kV line
C
alifornia
N
evada
N evada
Arizona
Arizona
California
Original MRTU Market FNM consisted of ISO Controlled Grid and “open loop”
interties, New PTO network, embedded and adjacent control area concepts, and
external branch group connections.

Early Testing Experience Showed Problems with
“Open Loop” Intertie Model
 Simulations in LMP Studies and CRR Dry Run identified
mismatches between modeled flows and actual flows
measured by telemetry, using original “open loop” model:
 Excessive modeled flow on Palo Verde – Devers 500 kV line
caused adverse LMP impacts in LMP Study (discussed in 4/20/07
LMP Study Update and 1/8/08 IBAA stakeholder meeting)
 LMP Studies 3A and 3C showed significant congestion at Miguel substation
from August 2003, when new generators started operation, to December
2004, when transmission upgrades were complete.
 Since December 2004, new generators operate at higher output, and original
“open loop” model showed congestion on Palo Verde to Devers 500 kV line.
 Unrealistic binding constraint on El Dorado – Lugo 500 kV line, in
CRR Dry Run results

Revised MRTU Market FNM Added 500 kV Lines
in Arizona, to Improve Power flow Modeling
MOENKOPI
WESTWING
YAVAPAI
PALO VERDE
MEAD
McCULLOUGH
MIDWAY
ADELANTO
VALLEY
DEVERS
SERRANO
LUGO
MIRA LOMA
ELDORADO
MARKETPLAC
E
VINCENT
HASSAYAMPA
TO FOUR
CORNERS
MIGUEL IMPERIAL
VALLEY
NORTH
GILA
MOHAVEVICTORVILLE
West
of
River East of
River
500 kV line
C
alifornia
N
evada
N
evada
Arizona
Arizona
California
 Addition of initial “partial loop” FNM added Palo Verde-Westwing and
Westwing-Yavapai-Moenkopi lines.

Additional Testing Experience Has Showed Needs
for Expanding the External Network Model
 Example: Hinds to Mirage 230 kV line binding in many hours of
market simulation in August-September, with high impact on LMPs
 Impacts in “MRTU Market Simulation Results Review for Week of
8/18/08 thru 8/24/08” (http://www.caiso.com/202f/202fc075dad0.pdf)
 Cause of impact was contingency of loss of Victorville-Lugo 500 kV line,
but (1) base case flow on Hinds-Mirage significantly exceeded actual
flow, and (2) impact of contingency significantly exceeded its impact
using a complete network model.
 Using a more complete external network results in more accurate
results.
 Additional external network modeling also addresses stakeholder
requests
 Example: Distribution of flow from sources near Imperial Valley
substation by adding network through Imperial Irrigation District.

ISO is Adding External Lines to FNM in DB37 to
Address the Identified Issues
 Additions to FNM in Arizona, Southern Nevada, and
Imperial Irrigation District include:
 500 kV and 345 kV branches,
 Connections of all Southern California Scheduling Points to the
500/345 kV grid, except where capacity under ISO operational
control is export-only (i.e., Laughlin intertie), and
 Equivalent lines as needed to represent parallel 230 kV and
lower voltage transmission grid.
 Additions consist of:
 14 new 500 kV buses, 22 new 345 kV buses, 45 new buses at
230 kV or lower
 211 new lines and transformers
 Additions do not change any Scheduling Points.

Additions to FNM in DB37 Nearly Complete the
500 kV Grid in the Southwest
This revised FNM has been used in annual CRR process for
2009 CRRs, and in subsequent Update 2 testing.

Eventually, FNM May Match Physical Model
N AV A JO
M O E N KO PI
W E ST W IN G
Y A VA PA I
P AL O VE R D E
M E AD
M cC U LLO U G H
C R YS TA L
M ID W AY
AD ELA N T O
V A LLE Y
D EV E R S
S ER R A N O
LU G O
M IR A LO M A
E LD O R A D O
M A R KE TP LA C
E
VIN C EN T
R IN ALD I
TO L U C A
G ILA R IVE R
H A R Q U A H A LA
H AS SA Y AM P A
R U D D
JO JO B A
TO KY R E N E
TO FO U R
C O R N ER S
M IG U E L IM P ER IA L
V ALL EY
N O R T H
G ILA
P E R KIN S
M O H AV EV IC TO R VILL E
H A R R Y
A LLE N
W est
of
R iver E ast of
R iver
Ph ase S hifter
500 kV line
C
a
liforn
ia
N
eva
d
a
N e v a d a
A riz o n a
Arizona
California
• The complete 500 kV transmission system near the ISO includes lines
operated by LADWP as well as APS, Nevada Power, and WAPA.
• Modeling issues include DC lines and phase shifters, as well as loop flow.
Physical model also has loops to Pacific Northwest

Why Not Do More Now?
 As stated in 7/21/03 Amended Comprehensive Market Design Proposal,
ISO will ultimately use a FNM that models the external WECC grid.
 However, regional flows are complex, with no consistent daily pattern. At
CA-OR border, variation exceeds the average unscheduled (loop) flow.
Actual Unscheduled Flow at Calif.-Oregon Border (S-N)
-1000
-800
-600
-400
-200
0
200
400
600
800
1000
5/1/20060:00
5/16/20060:00
5/31/20060:00
6/15/20060:00
6/30/20060:00
7/15/20060:00
7/30/20060:00
8/14/20060:00
8/29/20060:00
9/13/20060:00
9/28/20060:00
Time
MW
Mean = -53.6, Standard Deviation = 284.0

Simplistic Modeling of Closed Loop Would Not
Produce Correct Results
 LMP Study 3A used a closed loop WECC model, without data on
external schedules. Modeled unscheduled flow is difference between
COI schedules and modeled flows on COI branch group.
 Result: Poor correlation with actual loop flow (R=0.17). Error in model
of unscheduled flow sometimes exceeds the actual unscheduled flow.
Result of Simplistic Unscheduled Flow Model at
Malin (South to North)
-600
-400
-200
0
200
400
600
8/3/20030:00
8/3/200312:00
8/4/20030:00
8/4/200312:00
8/5/20030:00
8/5/200312:00
8/6/20030:00
8/6/200312:00
8/7/20030:00
8/7/200312:00
8/8/20030:00
8/8/200312:00
8/9/20030:00
8/9/200312:00
8/10/20030:00
Time
MW
Actual Modeled CAISO External Flow
Correlation: R = 0.1706

Plans for further improvement in modeling of
external transmission systems
 ISO developed Integrated Balancing Authority Area (IBAA)
modeling of SMUD and TID BAAs using schedules in ISO
Markets, to improve the ISO’s congestion management.
 ISO encourages WECC-wide coordination of congestion
management and data exchange, through WECC Seams
Issues Subcommittee (SIS).
 In parallel with larger regional effort, ISO will develop
improved BAA modeling using existing data sources:
 ISO Market Schedules and e-tags
 WECC planning models and Extra High Voltage (EHV) data pool,
subject to WECC confidentiality provisions

Caiso MRTU implementation workshop nov 2008

Recommended

Recommended

More Related Content

Similar to Caiso MRTU implementation workshop nov 2008

Similar to Caiso MRTU implementation workshop nov 2008 (20)

More from Kevin Forbes

More from Kevin Forbes (7)

Recently uploaded

Recently uploaded (20)

Caiso MRTU implementation workshop nov 2008