oasis overview transmission customer forum may 8-9, 2008 jim viikinsalo may 8-9, 2008 jim viikinsalo
TRANSCRIPT
OASIS OverviewOASIS Overview
Transmission Customer ForumTransmission Customer Forum
May 8-9, 2008
Jim Viikinsalo
May 8-9, 2008
Jim Viikinsalo
the bridge we
are crossing first attempt
at packing
last attempt
at packing
Some Perspective
OASIS – The 3 “W’s”• Where… is the information I am looking for?• When… will my request get answered?• Why… did ATC change, etc.?
Where… (OASIS Data Posting Requirements)• ATC/TTC values on each posted path:
– at least 13 months of Monthly service– at least 30 days of Daily service– at least 168 hours of Hourly service
• 82 paths posted on the Southern Company OASIS• Result – an “ocean” of data, with most customers
searching for their specific “bucket”
Where… (Other Information Posted on OASIS)• Schedules• Interruptions and Curtailments• Planned Transmission Outage Schedule• Significant Transmission Outages• Tariff and Rate Summaries• System Impact Studies and Facilities Studies• Interconnection Requests and Information• See “General Information” page for details
Where… (Significant Transmission Outages)
Tornado Damage at Plant Bowen, March 2008
Tornado Damage at McIntosh (GA), March 2008
Where… (General Information section)Additional pages
When… (Daily Study Process)• Near-term studies update Daily and Hourly TTC
postings closer to the start of service– System conditions for a given day are not known 30 days in
advance, so Monthly TTC value is used initially– 2 Days Ahead, a forecast is developed based upon real-
time conditions; Daily/Hourly TTCs updated on OASIS– 1 Day Ahead, the forecast assumptions are reviewed and
Daily/Hourly TTCs are updated as necessary
When… (Daily Request Processing)• 0600-0700 M-F: Begin answering next-day requests
– Query TTC in System Data to view the time of last update– Note Section 13.2 in the OATT (conditional acceptance)
• Redirect activity makes ATC more volatile– Initial request may be refused, but a subsequent redirect
may allow a similar request queued later to be accepted (non-discriminatory for both responses)
– Capacity made available as a result of redirects is offered on a first-come, first served basis
When… (Request Processing Duties)• Bulk Power Operations (BPO):
– service period from next hour through 12 months– may request assistance from Transmission Planning
• Transmission Planning (TP):– service beyond 12 months (may require extensive studies)
• Transmission Policy and Services:– coordinates between BPO and TP for answer
to all long-term service requests, per tariff
When… (Request Volume)
0
10000
20000
30000
40000
50000
2005 2006 2007 2008 (YTD)
Total Requests
Confirmed
Many requests are
approved, but not
confirmed by customers
Why… (Following the OASIS Audit Trail)• Users can view changes in offerings and reservations• Follow the “Audit Templates” link from the Customer
Menu page– uses the FERC Standards & Communications Protocol– Service Offerings audit trail – via transofferingaudit– Reservation Status audit trail – via transstatusaudit
• Follow the “System Data” link to see TTC/ATC timestamps
Data, such as ATC, changes very
frequently when customer activity is
high
Audit Query - Example Input• follow link to Audit Templates
from Menu page• input is case-sensitive• can query by different sets of
input parameters (Path, Seller, POR,POD, etc.)
• yyyymmddhhmmssTZ is the required format
Audit Query – Example Output
• Results are sorted from latest to earliest updates• ATC can vary significantly as reservations are confirmed,
redirects away are granted, and schedules are approved• Results can be viewed inside Web browser (html)
or downloaded as a CSV text file (data)
Why… (Service Priorities)
NE
RC
C
urt
ailm
ent
Pri
ori
ty
Type of Service
Pos
ting
Req
uire
men
t
Ear
liest
req
uest
ca
n be
mad
e
Late
st r
eque
st
can
be m
ade
Cus
tom
er m
ust
conf
irm w
ithin
Res
erva
tio
n
Pri
ori
ty
Con
ditio
nal
requ
ests
bec
ome
firm
(ca
nnot
be
pre-
empt
ed)
Res
ella
ble/
R
eass
igna
ble
Sch
edul
e D
eadl
ine
LTF7 Yearly/Firm/Network n/a n/a 15 d 1 n/a No 10a db7 Yearly/Firm/Point-to-Point n/a n/a 60 d 15 d 1 n/a Yes 10a db
7 Yearly/Firm/Recallable n/a n/a 60 d 15 d 1 n/a Yes 10a db7 Monthly/Firm/Network n/a 13m 2 n/a No 10a db7 Weekly/Firm/Network n/a 13w 3 n/a No 10a db7 Daily/Firm/Network n/a 30d 4 n/a No 10a db
STF
7 Monthly/Firm/Point-to-Point 13m 13m 4 d 5 1 m Yes 10a db
7 Weekly/Firm/Point-to-Point 13w 13w 48 h 6 1 w Yes 10a db
7 Daily/Firm/Point-to-Point 30 d 30 d noon db 24 h 7 1 d Yes 10a dbNon-firm
6 Daily/Secondary/Network n/a 30 d 2p db 8 n/a No 2p db6 Hourly/Secondary/Network n/a 168h 20 m 9 n/a No 2p db5 Monthly/Non-Firm/Point-to-Point 13m 60 d 24 h 10 n/a 2p db
4 Weekly/Non-Firm/Point-to-Point 13w 14 d 24 h 11 n/a 2p db
3 Daily/Non-Firm/Point-to-Point 30d 2 d 2p db 2 h 12 n/a 2p db
2 Hourly/Non-Firm/Point-to-Point 168h Noon db 20 m 30 m 13 n/a 2p db1 Hourly/Secondary/Point-to-Point 168h 14 n/a 2p db
Per OATT 13.2
Why… (ATC Graphical Query)
Top ATC includes ACCEPTED &
COUNTEROFFER, Bottom ATC
includes CONFIRMED
Why… (Maintaining Reliability)• Interruption – A pre-emption of lower priority service when
ATC is needed to grant requests for higher-priority service– Usually implemented in advance of a schedule start– Example: Hourly non-firm request bumps Hourly redirect request
• Curtailment – A reduction in net schedules for reliability to relieve a transmission constraint– Usually happens after a schedule begins– Non-firm curtailed by economics (value of service)
and Last in First Out (LIFO)– All firm curtailed pro-rata
OATT 14.7
OATT 13.6
OASIS – The 3 “W’s”• Where… is the information I am looking for?
– Offerings, Reservations, General Information• When… will my request get answered?
– Next-day requests beginning at 0600– Longer term requests dependent on several factors
• Why… did ATC change, etc.?– Maintain reliability– Query audit templates for details
Thank Goodness We Didn’t Heed This Advice…
